Sending
How duplicates are prevented
Each voucher carries a stable AutoBooks identity, so sending it again does not create a second copy.
Updated 10 October 20261 min read
On this page
Every voucher AutoBooks sends carries a unique identity from AutoBooks. If the same voucher is sent again, Tally recognises it and does not create a duplicate.
Before you confirm a send, the preview also warns about likely duplicates already in the Day Book mirror, by the same identity or by the same date and amount.
Reconciliation
Settings, Tally, Reconciliation compares sent rows with the Tally mirror for each client: matched, missing in Tally, and entered only in Tally.
Was this article helpful?
Related articles
- SendingSend vouchers to TallySelect mapped rows in Review, choose Send to Tally, check the preview, and the connector posts them.
- SendingBatch history and Retry failedSee every send with its status and errors, and retry only the vouchers that failed.
- ApprovingDiscrepancy alertsAutoBooks flags missing ledgers, possible duplicate payments, bank fees, and unusual amounts.
Still need help?
Write to us with your workspace name and what you saw. A person reads every message.