Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
Tally Prime is the deepest India-localised SME ERP with native GSTR-2B import, TDS challan tracking, and bank reconciliation screens, but its single-user data folders, manual voucher matching, and lack of a true multi-branch console make it impractical for organisations above 2,000 bank lines per month or 5+ branches — especially for CA firms running 80–200 Tally client instances in parallel.
Automate Tally via one of three integration paths: XML API for structured voucher export and import, TallyODBC for read-only BI queries (deprecated from TallyPrime 4.0 onwards), or the Tally Connector HTTP endpoint on port 9000 with TDL-formatted XML payloads. External layer reads ledgers via XML, ingests bank MT940/CSV and GSTR-2B JSON externally, runs multi-pass matching, and posts cleared voucher numbers back to Tally via XML import.
Tally Connector HTTP enabled via F12 configuration, XML API payload templates per TDL schema, per-company data-folder registry for multi-company deployments, GSTR-2B JSON ingestion adapter, bank MT940 and CSV parser, and XML writeback jobs scheduled per CA firm client.
A reconciled Tally ledger across 5+ branches or 80+ CA firm client companies, GSTR-2B matched at invoice level, bank reconciliation statement clean, TDS challans reconciled to Form 26AS, and cleared voucher numbers written back to Tally so the native Tally screens show the true reconciled state.
Tally Prime is the dominant ERP for Indian SMEs and mid-market firms, with licence pricing typically in the ₹18,000–36,000 per user range. Its India-specific depth — GSTR-2B import, TDS challan tracking, Form 26Q generation, bank reconciliation screen — is deeper than any other SME ERP sold in India. Automating reconciliation on top of Tally means working with one of three integration paths.
Tally Prime’s Built-In Reconciliation Capability
Out of the box, Tally Prime 4.0 delivers:
- Bank reconciliation (Banking → Bank Reconciliation) with Excel/CSV import of bank statements
- GSTR-2B reconciliation at invoice level (from TallyPrime 3.0 onwards)
- TDS deduction tracking, challan linkage, and Form 26Q/27Q file generation
- GSTR-1/3B computation from sales and purchase registers
- Voucher-level audit trail (mandatory from April 2023 under CARO 2020)
These cover the SME reconciliation workflow for a single-entity, single-bank organisation with fewer than ~500 monthly transactions. Beyond that scale, automation becomes necessary.
Three Integration Paths to Tally
XML Import/Export API
Tally’s XML API is the most complete integration surface. A request is a TDL (Tally Definition Language) payload over HTTP to port 9000 (when the Tally Connector is enabled) or a file drop into a watched folder. Responses contain voucher, ledger, and report data in XML. Used for extracting Day Book, Purchase Register, and Sales Register on a scheduled basis.
TallyODBC
TallyODBC exposes Tally data to SQL-like queries. It is sufficient for read-only reporting into Power BI or an external BI tool. It is deprecated from TallyPrime 4.0 in favour of the HTTP interface, and compound queries (joins across companies) are not supported. Acceptable for simple extracts, not recommended for bidirectional sync.
Tally Connector HTTP
The Tally Connector exposes the XML API over HTTP for remote access. External reconciliation tools POST queries and receive XML responses. The connector must be running on the Tally host and cannot be used during Tally data maintenance (Ctrl+Alt+R rewrite operations).
Integration Comparison
| Integration path | Read | Write | Best for | Limitation |
|---|---|---|---|---|
| XML Import/Export (file) | Yes | Yes | Scheduled bulk extract | Requires file watcher |
| Tally Connector HTTP | Yes | Yes | Real-time queries | Single-user concurrency |
| TallyODBC | Yes | No | BI / reporting only | Deprecated from 4.0 |
| CSV export from reports | Yes | No | Ad-hoc reconciliation | Manual export step |
For multi-branch consolidation, the typical pattern is scheduled XML export from each branch’s Tally instance to a shared SFTP location, followed by ingestion into an external reconciliation software India layer that handles cross-branch TDS, GST, and bank matching. GSTR-2B reconciliation at portfolio scale is handled by dedicated GST reconciliation software that reads the Tally purchase register via XML and the GSTR-2B JSON from the GST portal.
India-Specific Considerations
Tally’s GSTR-2B reconciliation enforces GSTIN validation but accepts supplier invoice numbers as free text, which is where most of the matching exceptions originate. Tally’s TDS module writes challan numbers to the voucher-level TDS analysis, but does not verify challan-level acknowledgement against TRACES. Both gaps are addressed by an external layer that treats Tally as the source of truth for the ledger and the external portals as the source of truth for compliance. The reconciliation in SAP, Oracle and Tally India guide covers the same gap pattern across other ERPs, and the GSTR-2B reconciliation guide details the matching logic that runs on top. Tally’s full integration documentation is at the Tally Solutions Help Portal.
The FAQ below covers specific Tally automation questions from Indian finance teams.