Most Tally sync questions come down to one of three things: nothing has started a run, the connector cannot see Tally, or a run started and stopped at a particular step. This page walks each one, and quotes back what the screens actually tell you.
What we have not been able to test
This lane has never been run against a licensed TallyPrime installation. The wire format follows Tally’s published integration documentation and is exercised against generated files; a dozen specific behaviours remain unconfirmed. Where that is true, Finocket takes the cautious branch rather than the convenient one, which you may notice as slowness rather than as an error:
- Deletions are found by comparing full listings, not by asking Tally for deleted records. The cheaper request exists in Tally’s documentation but its exact spelling is unconfirmed, so it stays switched off. Big companies therefore take longer on the listing step.
- A locked Windows session is assumed to cut Tally off. Whether it really does is the single most valuable thing we cannot yet check. Until it is checked, plan on leaving the machine signed in, and treat unattended overnight syncing as unproven.
- A voucher naming a ledger Tally does not have is never relied on to auto-create it. Masters are always sent first.
- An empty reply from Tally is never read as success. That is Tally’s way of saying no company is open, and reading it as “nothing changed” is how a sync would mark records as handled that it never saw.
Connection states, and what each one means
Connect Tally shows one of these for each paired machine. They have completely different fixes, which is why they are never flattened into one “something went wrong”. Only the first is a working state.
- Connected — the connector checked in recently and TallyPrime answered with the paired company open. Nothing to do.
- Paired, but never heard from — not a single voucher has been read. Check the connector is installed and running on that PC and that the key was pasted into it.
- Silent since it was last heard from — the connector checks in at least hourly even when idle, so more than an hour of silence means something stopped. Wake the PC, sign in, check the tray.
- The connector is not running — start it from the Windows system tray. Nothing syncs while it is closed.
- Nothing is listening on the Tally port — open TallyPrime, and set
F1 → Settings → Connectivityto act as a server on the port shown. If Tally is running with a company open and this persists, a firewall or endpoint-protection product is blocking a local connection. On a hosted desktop, each user gets their own port — use the one you were given. - No company is open in Tally — load the company and leave it open. Sync resumes on the next check-in, unprompted.
- That Windows session is locked — sign back in and leave it signed in. Do not close a remote desktop with Sign out.
- The TallyPrime licence is not active — expired, surrendered or in Educational mode. Educational mode cannot serve the gateway at all, and Finocket will not retry until it is reactivated.
- That TallyPrime is too old — update it. Delete detection and the edit log depend on newer builds, and the GST field layout changed in 3.0.
- Tally has a different company open — nothing is written while this shows, and that is the point of the check: it is what stops one customer’s vouchers landing in another’s books. Open the paired company, or pair the one that is open.
- Tally did not answer in time — usually a very large export, or Tally sitting on a modal dialog on that desktop. Dismiss it and let the next cycle retry. Repeated timeouts during a first full pull are expected.
- Finocket could not tell what went wrong — the fail-closed default. It never means “probably fine”: no marker advances and nothing is recorded as synced while it shows.
A run that started and stopped
Sync runs shows every run newest first, and for the one you pick, its steps in the order they happen: checking what changed, listing everything Tally holds, reading your masters, reading the vouchers, checking voucher numbers, and matching the totals. Each step reads Done, In progress, Stuck, Failed here, Not started yet or Never reached — so you can see exactly where it stopped rather than inferring it.
- In progress means it is waiting on your Tally connector. A big book can take several minutes on one step.
- Stuck means nothing has answered past the deadline — usually the connector on the shop PC is closed, or cannot reach Finocket.
- Failed here carries the error word for word, as Tally or the sync reported it. Forward that text exactly as it stands to your accountant or to support; rewriting it loses the detail that identifies the problem.
Why a run is refused rather than committed
- Your books have no start date. A sync has nothing to check itself against. Run the migration first.
- The plan changed since you read it. Committing re-derives the plan from the payload the run stored. If a ledger was mapped or a period locked in the meantime, the commit is refused — start a fresh run and read that one.
- Vouchers disagree with your cut-over date, or two vouchers in one payload share an identity. Both hold the whole run: one would silently overwrite the other.
- The payload carries more vouchers than one run can review. Sync a shorter period.
- The run has already been rolled back. It can never be committed again.
Push says it could not send anything
That is the expected answer today, not a fault to chase: Finocket has no live route to a Tally running on your PC, so the push refuses by name, marks nothing as sent, and leaves both sides unchanged. The connector is what would carry it. See Two-way Tally sync.
Still stuck
Send the exact wording from the screen — not a paraphrase — through Support & requests, along with the run and the step it stopped at.
Related: Two-way Tally sync, The Tally connector for Windows, Answer the Tally mapping queue, Undo a Tally sync.