An ERP that works with Tally: what to look for
By Graeon.ai · Updated
Short answer
An ERP that works with Tally keeps TallyPrime as your books while running sales, purchase, stores and production in the ERP. Graeon does this through its own Tally add-on (TDL): documents move both ways, a re-sent voucher never creates a duplicate, and each voucher is filed under the branch whose GSTIN it carries.
Why keep Tally at all?
Many Indian manufacturers and their accountants already run their books in Tally. Replacing it is disruptive. The practical answer is an ERP that runs operations — quotations, orders, GRNs, production, dispatch — and keeps Tally in step.
What should sync, and in which direction
- ERP to Tally: items, parties, sales orders, sales invoices, purchase orders, GRNs, bills, credit and debit notes, manufacturing journals and stock journals
- Tally to ERP: purchase orders, purchase invoices, sales orders, sales invoices, payments, outstanding balances, credit and debit notes and parties
Avoiding duplicates and mismatches
Sync is only useful if it is safe to re-run. In Graeon, a re-sent voucher never creates a second document and a changed voucher updates the existing one. Manufacturing journals and closing stock can be compared between Tally and the ERP from inside Tally.
One Tally company, several GST registrations
Each voucher is filed under the branch whose GSTIN it carries, so one Tally company can serve several registrations.