Reconciliation for Tally Prime in India — Bank, TDS, GST, Settlement
Tally Prime is the India SMB and mid-market accounting standard. It captures vouchers, runs GST registers, deducts TDS, and supports multi-company groups out of the box. What Tally does not do natively is parse Indian bank statements in MT940 or CIB Excel format at scale, reconcile vendor bills against GSTR-2B at line level, or align TDS deductions with the new payment-code regime against Form 26AS. TransactIG reads Tally via the standard XML or ODBC interface and runs the matching layer alongside Tally without modifying the accounts team's workflow.
What Tally Handles Natively, and Where the India Gap Appears
What Tally does well
Tally Prime is built for Indian accounting. Voucher-level entry, GST registers (GSTR-1, GSTR-3B prep), TDS deduction with section configuration, multi-company under one Tally Vault, e-invoice and e-way bill generation, and bank reconciliation against simple structured statements all run natively. For the SMB segment with single-bank-account, single-GSTIN, and clean reference flows, Tally's built-in BRS is sufficient.
Mid-market customers extend Tally with TDL customisation and Tally Definition Language vouchers; the ODBC interface allows external reporting tools to read Tally directly.
Where the India gap appears
Tally's BRS is a comparison view, not a matching engine. It cannot parse MT940, CAMT.053, CIB Excel, YONO Business, or PDF narration patterns at scale. Multi-bank consolidation across 3 to 5 accounts requires bank-by-bank reconciliation. UPI VPA extraction, NEFT reference fragments, and cheque-clearing narration all route to manual matching.
GSTR-2B reconciliation against Tally purchase vouchers at line level is a manual download-and-VLOOKUP. TDS section-to-payment-code mapping under Sections 393, 394, 413 of the Income Tax Act 2025 has to be maintained externally because Tally's master configuration still works at section level.
TransactIG Plug Points on Tally
Six matching surfaces that sit alongside Tally without modifying the voucher workflow.
Data ingestion
Scheduled XML pulls from Tally's standard gateway, or ODBC queries directly to Tally's data layer. No TDL customisation, no schema changes on the Tally side.
Section 393 TDS handling
Tally TDS vouchers mapped to the new payment codes 1001-1092 under Sections 393, 394, 413 of the Income Tax Act 2025. Reconciled against Form 26AS and AIS at code level.
GSTR-2B and IMS
Tally purchase vouchers matched to GSTR-2B and IMS at GSTIN + invoice + tax-amount level. ITC eligibility and Rule 36(4) provisional credit visible per voucher.
NACH batch matching
Outbound NACH mandate batches reconciled against bank response files; bounce codes mapped, re-presentation tracked at Tally voucher level.
Platform settlements
Razorpay, PayU, Cashfree, Amazon, Flipkart settlement reports disaggregated and matched to Tally sales vouchers and bank receipts.
Bank statement ingestion
MT940, CAMT.053, CIB Excel, YONO Business, and PDF parsed natively; matched to Tally bank ledger vouchers with narration-pattern extraction across HDFC, ICICI, SBI, Axis, Kotak.
Tally Integration Architecture
Each row is a discrete data feed configured during implementation, reading from Tally's documented XML or ODBC interface.
| Tally source | Export method | Sync cadence | Field mapping | Variance codes |
|---|---|---|---|---|
| Bank ledger vouchers | Tally XML pull on bank ledger, or ODBC query on bank vouchers | Daily | Tally bank ledger → TransactIG bank account profile | VOUCHER_UNMATCHED, NARRATION_ONLY, BANK_CHARGE_PENDING |
| Purchase vouchers (vendor bills) | XML purchase voucher pull, or ODBC on Purchase voucher table | Daily | Vendor ledger → counterparty GSTIN | INVOICE_OPEN, 2B_MISSING, ITC_BLOCKED |
| Sales vouchers | XML sales voucher pull, or ODBC on Sales voucher table | Daily | Customer ledger → counterparty | SALES_OPEN, ADVANCE_UNADJUSTED, CREDIT_NOTE_PENDING |
| TDS vouchers | XML TDS deduction pull (Stat Payment vouchers) | Per deduction cycle | Tally section → new payment code (1001-1092) | TDS_NOT_IN_26AS, RATE_MISMATCH, SECTION_RECLASSIFIED |
| GST output (GSTR-1 register) | Tally GSTR-1 export, or ODBC on GST tables | Per GST return cycle | Sales voucher → GSTR-1 row | INVOICE_NOT_IN_GSTR1, AMENDMENT_PENDING |
| Group consolidation (multi-company) | Per-company XML pull, consolidated in TransactIG | Per close cycle | Tally company → entity in TransactIG group | INTERCO_DRIFT, ONE_SIDED_POSTING |
Common Reconciliation Gaps in Tally Deployments
BRS exception backlog
Tally BRS can compare bank lines to voucher lines but cannot extract a UTR from a free-text narration. Manual matching is the default path.
Section to payment code drift
Tally TDS configuration retains legacy section labels; Form 26AS shows the new payment codes. External mapping required for the reconciliation match.
2B vs purchase voucher
Vendor bill booked in Tally; vendor has not filed GSTR-1; line missing from GSTR-2B. ITC is provisional under Rule 36(4) until 2B catches up.
Multi-company intercompany
Tally companies under one group share transactions that should net at group level; drift accumulates from timing or one-sided entry.
Gateway settlement gross vs net
Razorpay credits Tally bank ledger for the net amount after fees; Tally sales voucher was raised at gross. Manual breakup needed without a disaggregation layer.
Cheque ageing and CARO 2020
Long-outstanding unpresented cheques and stale deposits do not surface cleanly in BRS; auditors examine these under CARO 2020 bank reconciliation reporting.
How TransactIG Works with Tally
Ingest
Scheduled XML pulls or ODBC queries read bank, purchase, sales, TDS, and GST data from Tally per company. Bank statements and external feeds (GSTR-2B, 26AS, NACH responses, settlement reports) land alongside.
Match
Tally vouchers matched to external sources. Narration-pattern parsing extracts cheque, UTR, and VPA fragments. TDS section-to-payment-code mapping aligns Tally vouchers to Form 26AS. Multi-company consolidation runs in parallel.
Exception queue
Unmatched items route to a structured queue with variance codes, ageing, and maker-checker workflow. Cleared items can be returned to Tally with reconciliation notes; the accounts team continues working in Tally.
Frequently Asked Questions
How does TransactIG read data from Tally Prime?+
Tally Prime exposes two documented interfaces. The XML interface — Tally's classic gateway — accepts request XML and returns response XML for any voucher, ledger, or master record. The ODBC interface exposes Tally data as queryable tables. TransactIG uses either, configured during implementation. Most customers use scheduled XML pulls to a customer-owned SFTP staging area; mid-market customers with a strong IT presence prefer ODBC for direct query. No Tally Definition Language (TDL) customisation is needed — the integration uses Tally's standard, publicly documented endpoints.
Does TransactIG handle multi-company Tally setups?+
Yes. A typical Indian Tally deployment carries multiple companies under one Tally Vault — group entities, branches, sister concerns. TransactIG pulls data per company, runs reconciliation at the company level, and rolls up to a consolidated view across the group. Intercompany transactions between Tally companies are auto-matched on the amount-and-date pair. The reconciliation output is per-company GSTIN-level, which is what the GST return filing and statutory audit teams need.
How does the Tally TDS module reconcile to Form 26AS?+
Tally Prime's TDS module captures deduction at voucher level with the section, deductee, and rate. The new payment-code regime (1001-1092) under Sections 393, 394, 413 of the Income Tax Act 2025 requires mapping between Tally's section configuration and the codes that appear on Form 26AS. TransactIG reads Tally's TDS vouchers, applies the section-to-payment-code mapping configured during implementation, and reconciles against Form 26AS at code level for both deductor and deductee views.
Can TransactIG handle GSTR-2B reconciliation against Tally vendor bills?+
Yes. Tally captures vendor bills with GSTIN, invoice number, taxable value, and tax break-up. TransactIG ingests bills from Tally via the XML or ODBC interface and matches them line-by-line against the GSTR-2B and IMS feed downloaded from the GSTN portal. ITC eligibility, blocked-credit handling, supplier-not-filed scenarios, and Rule 36(4) provisional-credit lock are all surfaced. The reconciliation output sits alongside Tally — Tally remains the system of record.
Does TransactIG work with Tally on cloud (Tally Connector or remote setups)?+
Yes. Customers who run Tally through TallyPrime on Cloud, Tally on AWS Workspaces, or Tally Server 9 access through a remote desktop layer all integrate the same way. The XML or ODBC interface is exposed from the Tally machine; TransactIG's data connector reads from that endpoint or from a scheduled XML drop to SFTP. The Tally hosting model does not change the integration approach.
How long does Tally integration take?+
2 to 4 weeks for most Tally customers. Week one configures the XML or ODBC interface and establishes the scheduled data flow. Week two maps the chart of accounts, ledger groups, TDS section configuration, and GST registration list (multi-GSTIN setups) to TransactIG's matching schema. Weeks three and four configure narration patterns for Indian bank statements, TDS payment-code mapping, GSTR-2B alignment, and the maker-checker workflow. No custom TDL is written; the customer's accounts team continues working in Tally unchanged.
Reconciliation that fits the way your Tally accounts team already works
No TDL development. No voucher workflow change. 2 to 4 weeks to first reconciled close, ISO 27001:2022 certified, running from AWS Mumbai.