Agree on the accounting map first
Before exporting, confirm the company, ledger names, sales accounts, tax ledgers, units and voucher type expected in the destination setup. Different Tally configurations can require different mappings. Ask the accountant to approve the map with a small test set.
Export finalized records
A draft invoice may still change. Restrict exports to records that have passed the business’s final review, and retain a clear marker for the export batch. If an invoice changes later, use the agreed correction process rather than silently exporting a second version.
Clean the source data
- Use consistent customer names and unique customer references.
- Keep invoice numbers unique and in the approved series.
- Validate dates, taxable values, tax rates and rounding.
- Separate discounts, additional charges and credit adjustments.
- Do not export cancelled or incomplete invoices as normal sales.
Reconcile totals, not just record counts
Compare the number of invoices, gross sales, taxable values, tax amounts, discounts and final totals between the billing system and the imported vouchers. Equal record counts can still conceal a mapping error.
Keep an export trail
Record the batch date, invoice range, file name, person who exported it and import result. This makes it possible to answer whether an invoice was omitted, rejected or imported twice.
Treat XML as a transfer format
An XML file carries structured data; it does not decide whether the accounting treatment is correct. The business and its accountant remain responsible for reviewing ledger and tax configuration. Onbops export availability and compatibility depend on the supported product version and destination setup.