TallyPrime Integration Guide: ODBC & XML APIs

TallyPrime is the accounting backbone for millions of Indian businesses. As enterprises grow, they need their Tally data to talk to other systems — CRM platforms, e-commerce backends, HRMS tools, custom MIS dashboards, and government compliance portals. Without integration, the same data must be re-entered in multiple systems, creating inconsistencies and consuming accountant time.

TallyPrime provides two built-in local interfaces for developers: the XML HTTP Interface and the ODBC Interface. Additionally, cloud-based Tally integrations use middleware bridge utilities to overcome Tally's desktop-first architecture. This guide covers the complete technical setup for each integration type.

Understanding Tally's Architecture

Before diving into integration, it's essential to understand that TallyPrime is a desktop application with a local SQL-style database stored in .900 data files. Unlike cloud ERP platforms, Tally runs on a local machine (or server) and does not expose REST APIs over the internet.

All integrations therefore happen locally. Your integration code must run on the same machine (or LAN network) as TallyPrime, communicating via local ports. Cloud-to-Tally integrations require a local agent service that polls the cloud and pushes data into Tally via the local interface.

Method 1: XML HTTP Interface (Read & Write)

TallyPrime features a built-in HTTP server that listens on a local port (default is 9000). External applications can send XML envelopes via HTTP POST requests to:

First, configure Tally to act as a server: F1 → Help → Settings → Connectivity. Set "TallyPrime acts as" to "Server" or "Both" and set the port. Below is a sample XML request to create a new Ledger Master:

<VOUCHER VCHTYPE="Purchase" ACTION="Create">
  <DATE>20260710</DATE>
  <VOUCHERNUMBER>PV-001</VOUCHERNUMBER>
  <NARRATION>Purchase from Apex Enterprises</NARRATION>
  <ALLLEDGERENTRIES.LIST>
    <LEDGERNAME>Apex Enterprises</LEDGERNAME>
    <AMOUNT>-11800</AMOUNT>
  </ALLLEDGERENTRIES.LIST>
  <ALLLEDGERENTRIES.LIST>
    <LEDGERNAME>Purchase Account</LEDGERNAME>
    <AMOUNT>10000</AMOUNT>
  </ALLLEDGERENTRIES.LIST>
  <ALLLEDGERENTRIES.LIST>
    <LEDGERNAME>Input IGST</LEDGERNAME>
    <AMOUNT>1800</AMOUNT>
  </ALLLEDGERENTRIES.LIST>
</VOUCHER>

Method 2: ODBC Interface (Read-Only SQL)

If your integration only requires reading Tally data (e.g., generating reports in Excel, Power BI, or feeding MIS dashboards), use the ODBC interface:

1. Enable ODBC in Tally: F1 → Settings → Connectivity → Enable ODBC on port 9000.
2. Open your reporting tool and create a new ODBC data source using the TallyODBC driver.
3. Write SQL SELECT queries to pull data. Example for retrieving all Sundry Debtors:

Note: ODBC is read-only. You cannot create or modify Tally records via ODBC SQL. Use XML HTTP for write operations.

Common Use Cases for Tally Third-Party Integrations

Purchase Invoice Automation Without Custom API Coding

While building custom XML/ODBC integrations is powerful, maintaining them requires dedicated developer resources and local infrastructure. If your primary goal is to automate vendor bill logging — extracting data from purchase invoices and pushing it into Tally — you can skip the complex API setups using TrulyInvoice.

TrulyInvoice uses layout-aware OCR to extract line items, quantities, HSN codes, and tax splits from supplier invoice PDFs. It then maps this data and syncs formatted F9 purchase vouchers directly into Tally Prime via the XML HTTP interface on port 9000. There is no custom coding required. You simply upload vendor invoices and TrulyInvoice handles the Tally communication automatically — for a flat subscription of plans starting at ₹399/month.