Tally XML, TDL and ODBC: what each integration route involves

Tally’s help pages describe two roles. When Tally acts as a server, an outside program pushes requests in, for example a mobile app sending sales. When Tally acts as a client, Tally starts the exchange and pulls from another system.

Start with the question of who should be in control. If an event elsewhere should create a voucher, Tally is the server. If an accountant wants to fetch data on demand, Tally is the client.

Most small projects use the first role.

The XML integration page says you enable the HTTP server in Tally’s advanced configuration, and external programs post XML to the machine’s address on port 9000 by default.

A request names a type, import, export or execute, and an ID such as a report or collection. Import carries data, for example a voucher. Export can return a report, a collection or an object.

Responses carry a status, with a code and description on failure. The page does not state rate or size limits, so test with your own volume.

TDL is the language Tally uses for customisation. Tally’s integration pages say it can define requests that Tally sends out. One example is an HTTP POST to a system with an endpoint, with reports for success and error.

The same overview says JSON and ODBC links go through TDL customisation. If your plan needs JSON, check which TallyPrime release you run and read the current help page for it.

TDL code lives inside the company, so it needs an owner. Our guide to unmaintained TDL add-ons covers keeping, rewriting or replacing them.

Tally’s overview lists ODBC for pulls from external databases and for real-time dashboards and Excel queries. It is the usual route for reports that read Tally data.

Tally lists ODBC as read and write through TDL, but treat writing carefully. Test any write on a copy of the company and ask an accountant to review the vouchers.

Tally Solutions’ site also lists ODBC as an optional server in the same configuration screen.

For pushing sales, purchases or receipts into Tally, XML over HTTP is the common starting point. For dashboards, ODBC or exports feed a reporting tool. For behaviour inside Tally screens, TDL.

Whatever you pick, test on a copy of the company, keep a log of every request and compare totals daily for the first month.

Expect middleware when the other system speaks REST and JSON. Tally’s help states that it does not use SOAP natively, and a wrapper can add it when needed.