Skip to main content
GullySystem

Tally Integration: What to Sync, What to Leave Alone, and Common Mistakes

By Ganesh HS, Strategy and Technology, GullySystem

A good Tally integration sends finished events, such as a final invoice or a customer receipt, into Tally as vouchers and keeps ledgers matched on both sides. It does not copy every draft, edit and report back and forth. GullySystem builds these integrations, and its free technology audit first checks whether you need one at all.

Decide Which System Owns Each Record

Most Tally trouble starts because two systems both think they are in charge. Your order or billing software should own orders, and Tally should own the books.

Write down, for each record, who creates it, who may change it, and which way changes flow. Customers, stock items and ledgers need a clear owner too.

When both sides can edit a customer’s GSTIN, the two copies drift apart. Soon the invoice in your app and the one in Tally no longer match.

What Should Sync Into Tally

TallyPrime supports integration through XML and JSON over HTTP, file imports, ODBC, and its own TDL language. The right method depends on where Tally runs and how often data has to move.

  • Sales invoices once they are final, with GST split by rate
  • Customer receipts, including UPI collections and gateway settlements
  • Purchase bills after the goods have been received and checked
  • Credit notes for returns, linked to the original invoice
  • New customers and stock items, created with the same names and codes on both sides

What Should Stay Out of Tally

Quotations, drafts and orders that may still change do not belong in Tally. Send them across only when they become an invoice.

Avoid pushing every small edit as a fresh voucher, which leaves duplicates your accountant has to delete by hand. A correction should go in as a proper credit note or journal.

Reports are better read from Tally than rebuilt elsewhere. If the owner wants a dashboard, read summary figures out of Tally instead of writing numbers back into it.

Common Tally Integration Mistakes

Each of these is cheap to prevent while designing the integration and slow to clean up after a few months of live data.

  • Ledger names that differ by a space or a spelling, so the import creates a second ledger
  • No unique reference on each voucher, so a retry posts the same invoice twice
  • Assuming Tally is always on, when it runs on one office PC that is shut at night
  • GST rates and HSN codes kept in two places and changed in only one
  • No error list, so failed imports are found at month-end

Build in a Queue, an Error List and a Monthly Check

Tally often runs on a desktop in the office, so the integration should queue entries and send them when Tally is reachable. Nothing should be lost because the accountant’s PC was off.

Every failed entry should land on a list someone checks, with the reason in plain words. A monthly comparison of totals on both sides catches anything the list missed.

If your volume is small and your accountant is happy keying in invoices, you may not need an integration at all. GullySystem’s free technology audit looks at how your team uses Tally today and says whether one is worth building.

Tally sync map

A two-column map listing each record type, the system that owns it, and the Tally voucher or master it becomes. It also shows the trigger that sends each record and the unique reference used to stop duplicates, and ends with a monthly checklist for comparing totals.

Frequently asked questions

Can my software post invoices into Tally automatically?

Yes. TallyPrime accepts vouchers through its XML and JSON interfaces and through file imports. Post only final invoices and tag each one with a unique reference, so a retry never creates a duplicate.

Does Tally need to be open for the sync to work?

Yes, for the common HTTP method. Tally’s own integration notes say TallyPrime must be running on its configured port, with at least one company loaded. That is why a good integration queues entries and sends them once Tally is available.

Should we move off Tally to get an integrated system?

Usually not. Most accountants in India know Tally well, and a clean integration lets your operations software and Tally each do their own job. Replace it only when your books need something Tally cannot do.

Sources

Next step

Have a specific situation to work through?

This article covers the general case. Tell us what you’re actually dealing with and we’ll respond directly.

Get a Free Technology Audit