Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
A CFO at a mid-size IT services company receives a GST demand notice for ₹18 lakh — excess ITC claimed over 6 months, with 18% interest. The CFO’s first response: “why wasn’t this caught in the monthly close?”
The controller’s answer: “we reconcile GSTR-2B manually — it takes 4 days, and by then GSTR-3B is already filed.”
This is not a process failure at the analyst level. It is a CFO-level misconception: that once-a-month reconciliation is adequate for a company filing monthly GST returns. It is not.
Misconception 1: ERP Handles It All
The most expensive misconception. SAP, Oracle, and Tally handle the internal accounting layer — recording transactions, generating reports, maintaining ledgers. None of them connect natively to:
- TRACES (for Form 26AS TDS matching)
- GSTN (for GSTR-2B ITC matching)
- Bank portals (for bank statement vs ledger verification)
- Payment gateway settlement APIs (for MDR and TCS reconciliation)
Every Indian organisation using SAP, Oracle, or Tally has a reconciliation gap between its internal books and these external sources. The gap is filled either by a reconciliation layer or by manual spreadsheet work — rarely by the ERP itself.
Misconception 2: Once-a-Month Is Enough
| Reconciliation type | Why monthly timing fails |
|---|---|
| GSTR-2B matching | GSTR-3B due 20th — only 6 days after GSTR-2B is generated on 14th |
| NACH bounces | Bounce must update LMS same day for retry logic |
| Platform settlements | MDR errors compound daily if not caught early |
| Bank reconciliation | Large unreconciled items distort month-end cash position |
| TDS receivable | Late TRACES matches push correction requests past quarter deadline |
Misconception 3: It Is Purely a Back-Office Task
Reconciliation failures have direct P&L consequences:
- Unclaimed TDS credits: direct reduction in advance tax offset — cash impact
- ITC leakage: increases effective input cost — margin impact
- Section 50 interest (18% on excess ITC): direct P&L charge
- Audit qualifications: increased audit cost, management time, and reputational impact with lenders
A CFO who treats reconciliation as back-office administration is making the same error as a CFO who treats working capital management as back-office. Both have direct cash and margin consequences.
Misconception 4: Any Tool Will Do
Not all reconciliation tools are built for India’s tax-at-source framework. A generic bank reconciliation tool does not understand that a bank credit of ₹90,000 against an invoice of ₹1,00,000 is a TDS match — not an amount mismatch. It will flag the ₹10,000 difference as an exception, requiring manual intervention on every professional services payment received.
India-specific reconciliation requires: TDS section-level matching logic, GSTR-2B native matching, NACH batch disaggregation, and platform settlement unpacking. Generic tools require manual workarounds for each of these.
Misconception 5: Manual Review Is More Accurate
Manual review is more accurate than automation for genuine exceptions — where context and judgment matter. It is not more accurate than automation for the matching phase — where rules must be applied consistently across thousands of transactions.
A senior analyst applying Section 194J matching rules to 300 invoices per month will make 3–5 errors due to fatigue, distraction, and formula errors. An automated rule applied to the same 300 invoices will make 0 errors — and flag the 5–10 items that require genuine judgment. The analyst’s effort is better spent on those 10 items, not the 300.
Misconception 6: Reconciliation Debt Is Manageable
Reconciliation debt is not manageable over time — it is recoverable only up to the point where regulatory deadlines have not passed. ITC unclaimed beyond the September return of the following year is permanently lost. TDS unclaimed beyond the ITR assessment window may require additional documentation.
An organisation with ₹15 lakh in reconciliation backlog that defers cleanup for 6 months may find that ₹5 lakh has become unrecoverable.
Misconception 7: It Is Just a Data Problem
Reconciliation is a process problem, not a data problem. The data exists in Form 26AS, GSTR-2B, and bank statements. The problem is the matching logic — connecting the right internal record to the right external record using the right matching criterion — and the exception management workflow that resolves what the logic cannot.
Adding more analysts to a broken matching process produces more errors, not fewer. The correct intervention is a structured matching engine with named exception classification.
Reconciliation software India that addresses all seven misconceptions — connecting to TRACES, GSTN, and bank APIs; running continuously rather than monthly; applying India-specific matching logic; and generating a named exception queue — eliminates the structural conditions that make each misconception costly.
TDS reconciliation software that handles the net-of-TDS matching without manual intervention is the single highest-value fix for IT services, staffing, and professional services firms where TDS misconceptions generate the largest backlog.
The Institute of Chartered Accountants of India publishes guidance on CFO responsibilities for internal controls — which includes the reconciliation function as a core internal control activity, not a back-office administrative task.