Key takeaways
- TallyPrime accepts and returns XML over HTTP, which is how most integrations post entries
- Agree ledger, item and tax mapping with your accountant before any code is written
- Every automated entry needs a unique reference so it can never be posted twice
Quick answer
Software usually connects to TallyPrime through its built-in XML interface: Tally runs as a local server, and another program sends XML requests to create masters and vouchers or to read reports. Common automations post sales invoices from an online store, point of sale or ERP, read purchase invoices with document AI, and pull ledger balances into dashboards. The work that decides success is the mapping of ledgers, items and taxes, agreed with your accountant, and a unique reference on every entry so nothing is posted twice.
How software talks to Tally
- XML over HTTP. TallyPrime can be set to act as a server on a port of your choice. A connector sends XML to import ledgers, stock items and vouchers, or to export day books, balances and reports.
- ODBC. Lets reporting tools read Tally data directly, which suits dashboards and reconciliations.
- TDL customisation. Tally Definition Language changes Tally itself, for example new fields or reports. Keep it small, because every customisation must be maintained through Tally upgrades.
- Excel import. Useful for one-off loads, such as opening balances. Repeated manual imports are what automation should replace.
Because Tally usually runs on a computer in your office, the connector often runs on the same machine or network, and sends and receives data from your cloud systems on a schedule.
What is worth automating
- Sales invoices from an e-commerce store, point of sale or field sales app, posted with the right ledgers and GST.
- Purchase invoices read from PDFs and scans with document intelligence, checked against the purchase order, with exceptions sent to a person.
- Receipts and payments matched from bank statements.
- Stock movements from a warehouse system, so Tally and the warehouse agree on quantities.
- Reports such as receivables ageing and daily sales, pulled into a dashboard the owner reads on a phone.
Mapping comes first
Before any code is written, agree with your accountant:
- Ledgers. Which sales, purchase, tax and party ledgers each type of entry uses, and how new customers and suppliers are created.
- Items and units. How product codes in your other systems match stock items in Tally.
- Taxes. GST rates, place of supply rules and how inter-state and intra-state sales are posted.
- Voucher types and numbering. Which voucher types are used, and how numbers are assigned so they never clash with manual entries.
- Exceptions. What happens when a party or item does not exist yet: create it, or stop and ask.
Avoiding duplicate and broken entries
- Give every automated entry a unique reference from the source system, and check for it before posting.
- Post in small batches and read back the response: Tally reports which entries were created and which failed.
- Keep a log of every request and response, so an accountant can trace any entry to its source.
- Lock periods that have been filed for GST, and send corrections as new entries.
- Reconcile totals daily for the first month, then weekly.
GST e-invoicing and e-way bills
If your turnover requires e-invoicing, the IRN and QR code must appear on the invoice. Some setups generate them inside TallyPrime, others in the source system before posting. Decide which system is responsible, and make sure the other one never generates a second IRN. See connecting your software to GST e-invoicing.
How long it takes
A one-way integration posting one or two voucher types typically fits in one 150 hour block, including mapping, testing and a parallel run. At the 2good.dev rate of USD 2 or INR 199 an hour, that is INR 29,850 before tax.
Questions and answers
Do we need to move off Tally to automate?
Usually not. Many trading and service businesses stay on TallyPrime and automate around it. See ERP for an Indian MSME for when a move is worth it.
Can Tally be on the cloud?
Yes, through hosted TallyPrime or a cloud server. The connector then talks to that server, which removes the dependence on an office computer being switched on.
Who checks the automated entries?
Your accounts team, through a daily exception list and reconciliation. Entries the system is unsure about wait for a person to approve them.
Have a question about this guide? Write to us or ask Colony, our AI guide.