Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
Financial reconciliation is the process of confirming that two records of the same money agree. In practice, that means matching your internal books against an external source: a bank statement, a government tax portal, a payment gateway’s settlement report, or a supplier’s invoice.
In India, this process is more structured — and more consequential when it fails — than in most other markets. Here is why.
What Does Reconciliation Actually Mean in Indian Finance
At its core, reconciliation asks one question: does what I recorded match what actually happened?
For an Indian finance team, this question has to be asked separately for at least three different processes running simultaneously:
Bank reconciliation: Does the cash book balance match the bank statement balance? Differences arise from outstanding cheques, deposits in transit, bank charges, and timing of NEFT/RTGS credits.
TDS reconciliation: Does the TDS receivable in the books match the TDS credit in Form 26AS on TRACES? Differences arise because deductors sometimes deposit TDS with the wrong PAN, wrong section code, or wrong amount.
GST reconciliation: Does the ITC claimed in GSTR-3B match the ITC available in GSTR-2B? Differences arise from supplier filing delays, invoice classification errors, and the 2A vs 2B difference introduced in January 2022.
TDS vs GST vs Bank — The Three Layers
| Layer | What is matched | External data source | Regulatory consequence of mismatch |
|---|---|---|---|
| Bank | Cash book vs bank statement | Bank MT940 / statement | Misstated cash position, audit risk |
| TDS | TDS receivable ledger vs Form 26AS | TRACES portal | Lost TDS credit, demand notice |
| GST | Purchase register + ITC claimed vs GSTR-2B | GST portal | ITC reversal + 18% interest |
Each layer runs on a different schedule. Bank statements update daily. Form 26AS updates 3–7 days after the deductor deposits TDS challan. GSTR-2B is generated on the 14th of each month for the prior month’s transactions.
Common Reconciliation Errors Indian CFOs Face
The most common reconciliation failures in Indian organisations share a pattern: the matching process was designed for a lower transaction volume than the business now handles.
A startup processing 200 transactions a month can reconcile in a spreadsheet. At 2,000 transactions, the spreadsheet breaks — partial payments, TDS deductions, GST adjustments, and NACH credits all collide in the same column, and the error rate climbs.
Reconciliation vs Accounting: Key Differences
Accounting records what happened. Reconciliation confirms what happened matches the external record.
You can have perfect accounting and failed reconciliation — if your accountant correctly recorded a payment received but the deductor deposited TDS against the wrong PAN, your books are correct but your Form 26AS will not show the credit. The reconciliation process catches this; accounting alone does not.
Why Generic Tools Fail the Indian Context
Spreadsheet-based reconciliation and generic accounting tools fail at Indian-specific requirements for the same reason: they were not built to handle tax-at-source deductions as a first-class matching dimension.
When a payment of ₹1,00,000 arrives from a client who deducted 10% TDS under Section 194J, the bank credit is ₹90,000. A generic matching tool tries to match ₹90,000 against an invoice of ₹1,00,000 — and fails. The finance team must manually adjust the entry, record the TDS receivable of ₹10,000, and verify it appears in Form 26AS later.
At 100 such invoices per month, this manual adjustment takes 3–5 days. At 1,000 invoices, it becomes the full-time work of 2–3 people.
The reconciliation software India that handles this correctly understands TDS as a deduction pattern — not an exception — and reconciles the gross invoice amount against the net bank credit plus the TDS receivable in a single matching pass.
How Automated Reconciliation Works
Automated reconciliation replaces the spreadsheet matching loop with a rules engine that knows:
- Which payment types carry TDS deductions, and at what rate by section
- That a GSTR-2B ITC entry requires matching against both the purchase invoice and the GSTR-3B claim
- That a NACH batch credit of ₹48,76,450 may represent 200 individual EMI collections
The engine runs multiple matching passes — first trying exact matches, then applying rules for known deduction patterns, then flagging genuine exceptions that require human review.
The outcome: organisations that move from manual to automated matching typically see match rates improve from around 51% (manual, with many items needing human reconciliation) to 88% or higher — with the human effort shifting from matching to exception resolution.
Using dedicated bank reconciliation software alongside TDS and GST matching ensures each layer is covered without maintaining separate processes.
The Income Tax India portal publishes the TDS rates and filing requirements that govern what appears in Form 26AS — the primary external source for TDS reconciliation.