Three moving parts. You only ever install one.
Paste a token into the connector once. Everything after that is automatic — and your books keep working even when the Tally machine is switched off. Nothing is migrated, nothing is re-keyed, and TallyPrime stays the ledger of record on the machine your accountant already uses.
How a sync runs
Connector on the Tally PC
A signed Windows service reads TallyPrime over its own XML gateway on localhost:9000. Read-only by default. It auto-updates, auto-recovers and shows its own sync health.
- Masters, vouchers, outstanding and stock
- Incremental cursor and idempotent batches
- No typed-in serial — possession of the token proves the licence
- No admin rights needed to install it
Secure multi-tenant cloud
Per-company sync key, argon2id password hashing, JWT with rotation, and the tenant pinned from the verified token only. Every row carries its tenant and its company.
- Data stored in India, DPDP-ready
- A semantic layer over your Tally facts
- Audit log and role permissions
- Enterprise can have a database per tenant
Mobile and BI, together
The same numbers on Android and in the browser. Owners get the dashboard, accountants get the reports, your CA gets a read-only seat on the company you invited them to.
- Multi-company switcher everywhere
- Push, email and WhatsApp alerts
- Write selected entries back into Tally
- The same last-sync time in all three places
Install the connector, paste your token, pick your companies. The first sync usually finishes before your chai does.
Every batch received, and what it did.
The console lists each batch your connector sent — what came in, what was upserted, what was skipped and why. A partial batch names the reason rather than failing silently.
— ok 1,000 1,000 0
— ok 2,000 1,998 2
— ok 2,000 2,000 0
26 rows missing unit partial 2,000 1,974 26
Silent staleness is the enemy. That is why the last-sync time appears in three places and why a skipped row carries its reason rather than disappearing.
The boring part, done properly.
Reliability is the feature people switch for. Nobody moves tools because of a nicer chart — they move because the last one quietly stopped syncing on a Tuesday and nothing said so. Here is exactly what runs.
Incremental, idempotent sync
Per-entity cursors and replay-safe batch keys — not date-window re-pushes. If a batch fails halfway and is sent again, the second attempt lands on the same keys: it cannot post a voucher twice or inflate a ledger.
Live sync status everywhere
The connector, the web console and the phone all show the same last-sync time and per-entity health. Data Sync Logs list every batch received and what it upserted; the Data Inspector shows the rows that actually arrived.
Per-company sync key
The connector authenticates with a hashed, peppered key scoped to one company. A leaked key can write to nothing else, and you can rotate it without touching the other companies on the account.
Tenant isolation by construction
The tenant is pinned from the verified token only — never a header, a body field or a URL. A cross-tenant read returns 404 rather than an empty list. Every row carries its tenant and company.
Data in India, DPDP-ready
Indian data residency, argon2id password hashing, JWT with rotation and audit logging throughout. Enterprise can have a database per tenant and a dedicated analytics store.
Read-only roles for the people who only look
Owner, accountant, viewer and read-only CA, each scoped per company rather than per account. Your CA gets one company at quarter end and sees nothing else.
It reads by default. It writes only when you say so.
Raise a receipt, invoice or payment from the console or the phone. It joins a push queue and posts into Tally when the connector next polls — and until you enable write-back for that company, the connector holds no write permission at all.
raised on the phone · 18:38POSTED
raised in the console · 18:41QUEUED
raised in the console · 18:42QUEUED
What you do once, and what happens after.
Once, on the Tally PC
- Install the connector — no admin rights needed
- Switch Tally’s own gateway on: F1 → Settings → Connectivity → Client/Server, set to Both, port 9000
- Paste the token from your account
- Pick the companies to sync
- Allow the connector through the firewall if one blocks it
What syncs
- Masters — ledgers, accounts and parties
- Voucher types and vouchers
- Voucher entries, the dr/cr lines
- Inventory entries and stock items
- Outstanding bills
- Cost centres
After that, automatically
- Incremental batches on per-entity cursors
- Auto-update and auto-recover after a restart
- Per-entity health in the connector window
- Data Sync Logs in the console
- Push when the sync goes stale
Nothing is exposed to the internet by the connector: it reads Tally over the local gateway on the same machine. Windows SmartScreen may warn on first run — the download page publishes the SHA-256 so you can check you have the right file.
The things that go wrong, and the fix.
My numbers look old, or the app says the sync is stale
Almost always the connector. On the PC that runs TallyPrime, check three things in order: TallyPrime is open, the connector window is running and shows a recent last sync, and the PC is awake. The apps deliberately keep showing the last synced figures with an “as of” time rather than an empty screen, so a stopped connector looks like stale data, not an error.
The connector cannot reach TallyPrime
Tally’s own gateway has to be switched on: in TallyPrime press F1 → Settings → Connectivity → Client/Server, set it to Both and the port to 9000. The connector reads Tally over that local gateway on the same machine — nothing is exposed to the internet by it. If a firewall or antivirus is blocking it, allow the connector executable.
Windows warns about the download
SmartScreen may warn on first run. Choose More info → Run anyway, and check the file against the SHA-256 published on the download page if you want to be certain you have the right file.
Do I have to change how I use Tally?
No. You keep working in TallyPrime exactly as you do today. The connector reads Tally through its own XML gateway and is read-only unless you explicitly enable write-back.
Does my PC need to stay on?
Only for syncing. Your data lives in the cloud, so the apps keep working — with the last synced figures and a clear “as of” time — when the Tally machine is off.
Can a retry double-count a voucher?
No. Sync runs on per-entity cursors with replay-safe batch keys, so a batch sent twice lands on the same keys. That is the difference between this and a date-window re-push, which is where double-counting usually comes from.
What if a sync key leaked?
The connector authenticates with a hashed, peppered key scoped to a single company, so a key that leaks can write to nothing else. Rotate it without touching the other companies on the account. Separately, the tenant is pinned from the verified token, so no request can reach another tenant’s rows.
Which machine should I install it on?
The machine running TallyPrime. If you run Tally on more than one machine, install it on each — the connector is free and the licence lives with the token, not with the device.
Start with Comsky TallyBridge.
Grow into the ecosystem.
One account opens every Comsky product — and one invoice covers them, however many you run.