View and manage Tally syncs
Every pull, export and upload is one batch. The list shows how each went, and opening a batch shows each voucher, why it failed and what to do.
Video coming soon: Tour of Data SyncThe list
Open Utilities › Data Sync. Each row is one batch: an Import or Export tag, the machine name or file name, a status, the time, and count pills for created, updated, conflict, failed and skipped (zeros are hidden). A running batch has a progress bar and updates by itself. Use the page controls for paging.
The strip at the top counts what is synced, pending, in conflicts, failed, cancelled in Tally and to cancel in Tally by hand. Click that last pill to see those documents. With nothing yet it reads "Nothing synced yet".
Filter narrows by Direction (Import, Export) and by status. Clear all resets it. The Upload XML, Pull from Tally and Export to Tally buttons are greyed out without Add/Edit.
Open a batch
Click a row for the side panel: Outcome tiles (Total vouchers, Created, Updated, Conflicts, Failed, Skipped), then Details (Uploaded by, Created, Started, Completed) and, for an uploaded file, Source file.
The full page lists every voucher with its status. Search by voucher, party or type, and filter by status or by sync session. Each failed or skipped row carries its reason in plain words, for example "Skipped: pushed from Bizconnekt as INV-12". A masters batch lists each group, party and item as Created, Already existed, Skipped or Failed.
Map COA accounts
An export row blocked because an account has no Tally ledger says the account needs to be mapped. Click Map COA accounts, type the Tally ledger name exactly as in Tally, and save. When all are mapped, re-export the document from the same window.
Cancel in Tally
When you void or delete a document that is already in Tally, the next export cancels its voucher in Tally. If that cannot be done, the document is marked Cancel in Tally and shows Cancel this voucher in Tally by hand, the Tally company and Why. Cancel it in Tally yourself, or your Tally books will not match. When Tally confirms it, the row reads Cancelled in Tally.
Resolve a conflict
A conflict means the voucher changed in Tally and its document was also edited in Bizconnekt. Open the batch, click the Conflict row, then Compare. Tally is on the left and Bizconnekt on the right.
- Click Accept Tally (left) to overwrite the Bizconnekt document with Tally's version, or Accept BizConnekt (right) to keep yours (this does not stick yet; see Problems and fixes).
- Click Submit.
Tally's version is then applied and shows "Tally version accepted and synced". Keeping yours shows "BizConnekt version kept". Requires Add/Edit.
Status
| Batch status | Means |
|---|---|
| Processing | Still running |
| Completed | Everything went through |
| Completed with errors | Some vouchers failed, were skipped or are in conflict |
| Failed | The run stopped, for example Tally was unreachable |
| Voucher status | Means |
|---|---|
| Pending | Waiting to be handled |
| Created / Updated | A Bizconnekt document was made or changed |
| Skipped | Unchanged, already synced, or left out on purpose |
| Failed | Could not be imported; the reason is on the row |
| Conflict | Both sides changed; resolve it |
| Cancel in Tally / Cancelled in Tally | Needs a hand cancel / confirmed cancelled |
On mobile
There is no Data Sync history on the phone. A document you voided or deleted that is still live in Tally shows the note Cancel this voucher in Tally by hand, and Cancelled in Tally once done. Everything else is on the web. The Android app is on Google Play. The iPhone app is coming soon to the App Store. Same on iPhone and Android.
Problems and fixes
A batch says Completed with errors
Open it and filter to Failed and Conflict. Fix each reason, then run the sync again. Only failed or changed items are sent again.
Nothing came in from a pull of "All documents"
That choice means Tally's current period. Pick Custom range for older vouchers.
Failed: a customer, item or ledger does not exist
Pull masters first, then run the voucher pull again.
The same conflict returns after I kept the Bizconnekt version
Keeping the Bizconnekt version does not stick yet, so a later pull shows the conflict again, whether or not you edit Tally. To settle it, click Accept Tally (left). If you want your version in Tally, make your change again in Bizconnekt and export it. The next pull shows the conflict one more time. Click Accept Tally (left) again: Tally now holds your version, so both sides match and it stays settled. If Tally's version is the one you want, there is nothing more to do.
Skipped: belongs to another GST registration
The Tally company is shared with another business unit, and that voucher sits under the other unit's registration. It is pulled by the other unit.
Tally voucher type is not yet supported
Orders, delivery notes and similar Tally entries have no Bizconnekt counterpart and show Failed in an uploaded file. Pulling by voucher type leaves them out.
Upload says the file is not accepted
Only .xml files exported from Tally, up to 50 MB.