The ITC mismatch problem: what crore-scale losses look like in a Tally-vs-SAP world.

Walk into the finance function of any mid-cap Indian business with multi-state operations and ask a simple question: how much input tax credit are we losing to mismatch, time bar, and supplier non-compliance in a typical year? Most CFOs do not know the answer. Some will give a number that turns out, on examination, to be a small fraction of the real figure. A few will know precisely, because their finance team has already had the conversation that follows.

ITC mismatch is the single largest category of avoidable indirect-tax loss in Indian businesses today. In organisations running Tally at branch level with SAP at head office, or running multiple ERP instances across legal entities, or running operations across ten or more states with separate GSTINs and separate supply chains, the loss is typically in the range of fifty to two hundred basis points of revenue, per year. For a business at the ₹500 crore revenue mark, that is ₹2.5 to ₹10 crore of credit not claimed, not recovered, or not reconciled, sitting permanently outside the P&L.

The reason this loss persists is structural. The current GST architecture — Section 16(2)(aa) read with Rule 36(4), effective from 1 January 2022 — makes ITC available only when the supplier’s invoice has been furnished in GSTR-1 and communicated to the recipient through GSTR-2B. The 5% provisional ITC under the old Rule 36(4) is gone. The current law is binary: the invoice is in GSTR-2B and the credit is available, or it is not and the credit is lost — subject to a strict time bar under Section 16(4). The Invoice Management System (IMS), now operational, adds an accept/reject layer before GSTR-2B is finalised, which provides a further opportunity to act — or, in undisciplined hands, a further place to lose credit.

What follows is the framework I work from when a CFO asks the firm to look at this seriously. Six recurring categories of ITC loss. None of them is technically difficult to address. All of them require the discipline, the systems, and the partner-led attention that mid-cap finance functions typically cannot sustain on their own.

1 · The GSTR-2B-versus-purchase-register gap

Where most of the loss sits, month after month, until someone runs the reconciliation.

The first and largest category of ITC loss is the ordinary monthly mismatch between GSTR-2B (the legal basis for ITC under Section 16(2)(aa)) and the purchase register in the company’s books. The pattern is consistent. The purchase register contains invoices entered by the accounts payable team as they are received. GSTR-2B contains invoices furnished by suppliers in their GSTR-1. The two should agree. They almost never do.

Five sub-patterns recur. First, invoices in the books but not in GSTR-2B — because the supplier has not filed GSTR-1, has filed late, or has filed with errors. Second, invoices in GSTR-2B but not in the books — because the invoice was received and entered against a different GSTIN, or accounted to a wrong period, or simply missed by the AP team. Third, amount mismatches between the two — arising from rounding, foreign-exchange differences, debit/credit notes, or supplier amendments through GSTR-1A. Fourth, GSTIN mismatches where the supplier has invoiced to the wrong registered office of a multi-state business. Fifth, place-of-supply errors that move the credit between SGST/CGST and IGST in ways the recipient does not catch.

Each of these is recoverable if surfaced in the current month. None of them is recoverable if surfaced eighteen months later. The discipline that matters is monthly reconciliation, performed before GSTR-3B is filed, with documented follow-up on every mismatch. The IMS has made this easier for invoices the supplier has filed but the recipient wishes to reject — but it has also added a layer that, if mishandled, lets credits slip through unreviewed. The CFO who is not seeing a monthly GSTR-2B-to-purchase-register reconciliation report, with action items on every line, is losing money that will not come back.

2 · The Section 16(4) time-bar trap

The credit you forgot to claim by November of the next year is gone forever.

Section 16(4) of the CGST Act imposes a strict time bar on ITC claims. The credit must be claimed by the earlier of (a) the due date of GSTR-3B for the month of October of the following financial year, or (b) the date of filing the annual return in GSTR-9. For invoices in FY 2024-25, the practical bar was 30 November 2025. For invoices in FY 2025-26, the bar will be around 30 November 2026, depending on filing dates.

The trap is that ITC missed in this window is permanently lost. There is no second chance, no appeal, no “we will fix it at year-end.” A finance function running on a quarterly close cadence, or on an under-resourced GST team that only catches up at year-end audit, is structurally at risk of this loss. The classic case is the invoice received and accounted in March of one year, properly available in the supplier’s GSTR-1 by April, but missed in the recipient’s monthly reconciliation because the AP team was focused on year-end. Eighteen months later, the year-end statutory audit surfaces it. The credit is past the Section 16(4) bar. The loss is permanent.

The remedy is procedural, not technological. Every invoice in the books must be tracked against its GSTR-2B reflection until the credit is claimed in GSTR-3B. Where the supplier has not filed in time, the recipient must follow up actively. Where follow-up fails, the recipient must make a commercial decision — chase the supplier harder, withhold payment until they file, or accept the loss. None of those decisions is acceptable to make accidentally, by inaction, in October of the following year.

3 · Section 17(5) blocked credits taken in error

The credit you claimed and should not have — the mirror image of categories 1 and 2.

ITC loss is not only credit unclaimed. It also includes credit improperly claimed that the department will reverse on examination — with interest at 24 percent per annum under Section 50 and penalties under Section 73 or 74. Section 17(5) of the CGST Act enumerates the categories of blocked credits: certain motor vehicles, food and beverages provided to employees, rent-a-cab, club memberships, life and health insurance (with limited exceptions), works contracts for immovable property construction, goods and services used for personal consumption, and several others.

In well-run finance functions, this is governed by an exhaustive chart-of-accounts-to-GST mapping that flags Section 17(5) categories at the point of accounting. In less well-run functions, the mapping is partial, the AP team applies judgment inconsistently, and credits get claimed on transactions where they should have been blocked. The exposure compounds quietly until a departmental audit surfaces the entire pattern.

The cost of an error in this category is asymmetric and worth quantifying. A ₹10 lakh ITC claim that should have been blocked, sitting unreversed for three years, attracts ₹7.2 lakh of interest at 24 percent (assuming Section 73 applies), plus potential penalty of up to ₹10 lakh under Section 74 if the department contends suppression. A pattern of such errors across a multi-state business can run into materially significant exposures. The remedy is a properly configured ERP GST mapping, periodic Section 17(5) review by a qualified team, and a documented position taken on borderline categories — not a hopeful interpretation that may not survive scrutiny.

4 · Rule 37A — supplier non-payment of tax

The credit you claimed in good faith that the department later reverses because your supplier did not pay.

Rule 37A creates an additional condition for the recipient: where the supplier has filed GSTR-1 but has not paid the corresponding tax through GSTR-3B by 30 September of the following financial year, the recipient is obliged to reverse the ITC by 30 November of that following year — with the right to re-avail it when the supplier eventually files and pays.

The practical consequence is that a recipient’s ITC position depends not only on the supplier’s GSTR-1 filing (which gets the invoice into GSTR-2B) but also on the supplier’s GSTR-3B filing and tax payment. In a business with several thousand suppliers, monitoring this is non-trivial. Most finance functions do not do it. The exposure builds up silently and surfaces when the department issues a notice asking for reversal of credits taken against non-compliant suppliers.

The remedy is to extend the monthly reconciliation discipline. The GSTR-2B-versus-purchase-register match is not enough; the recipient must also monitor whether the relevant suppliers are filing GSTR-3B in time. For the largest suppliers — typically the top fifty by spend — this monitoring should be active. For smaller suppliers, a quarterly check is usually sufficient. The exposure category that ought to alarm a CFO is the supplier who is large, late in filing GSTR-3B, and showing other signs of distress. That is a credit exposure as well as a working-capital exposure.

5 · The Tally-versus-SAP reconciliation problem

Where multi-ERP environments produce ITC loss that no single system surfaces.

Many mid-cap and growing businesses operate in a hybrid ERP environment: SAP or another major ERP at head office and listed-entity level, with Tally or similar at smaller branches, subsidiaries, or recently-acquired operations. This is, in practice, the most fertile ground for ITC loss in Indian businesses today.

The patterns are predictable. Invoices entered in Tally at a branch never appear in the consolidated SAP GST workings at HO, because the data reconciliation is incomplete. ITC on capital goods purchased at a project site, accounted in a project-specific subledger, never gets included in the entity-level GSTR-3B. Inter-branch transactions between two GSTINs of the same legal entity get accounted in books but never invoiced for GST, losing the credit at the receiving branch. Joint-venture and shared-cost arrangements get billed in one entity’s books and consumed by another, with the GST sitting in the wrong place.

The remedy is a designed reconciliation between every ERP instance and the consolidated GST workings, performed monthly, by someone with both system knowledge and GST knowledge. This is a partner-led exercise. Most in-house finance teams do not have the cross-system fluency to do it well. The firm’s own GST Recon Pro tool, used in client engagements, automates much of this reconciliation against the canonical GSTR-2B data — but the underlying discipline matters more than the tooling.

6 · Place-of-supply and inter-state allocation errors

The credit that is technically claimed but trapped in the wrong state.

The sixth category is more subtle and often missed: ITC that has been technically claimed but is trapped in the wrong state, where the recipient cannot effectively utilise it. This happens when a supplier in one state invoices a recipient’s GSTIN in a state where the recipient has little or no outward supply — producing an SGST/CGST credit balance in a state that cannot offset it against output liability.

The result is a credit that sits indefinitely on the balance sheet of one branch, unable to be used, while another branch (with output liability) pays out cash GST. The credit is not lost in the Section 16 sense — it remains on the books — but it represents working-capital trapped indefinitely, often at significant levels for businesses with concentrated supply chains and dispersed selling operations.

The remedy lies in active management of the place-of-supply at the procurement stage, with intercompany or inter-branch billing arrangements designed to move credits to where output liability sits, and with periodic review of accumulated state-wise ITC balances to identify trapped credit. This is a category where structural change — in vendor selection, in billing GSTIN choice, in inter-branch contracting — produces durable improvement.

How a CFO should sequence the work.

For a CFO of a mid-cap or listed business who recognises some of these categories in their own operations, the path forward is sequential.

Begin with a one-time diagnostic against the past three financial years. The objective is to quantify the recoverable ITC still within the Section 16(4) bar, the irrecoverable ITC already lost, the Section 17(5) errors that need reversal before they compound under interest, and the Rule 37A exposures sitting against non-compliant suppliers. This diagnostic typically takes four to six weeks and produces a defensible number that the audit committee will want to see.

From the diagnostic, two streams of work follow. The first is recovery — chasing suppliers for late GSTR-1 filings, filing amendments where eligible, and reclaiming credits before time-bar expiry. The second is system redesign — configuring the ERP and the procurement workflow so that the categories above are addressed structurally, not chased episodically. The first stream pays for the engagement many times over. The second stream prevents the problem from recurring.

For multi-ERP environments — the Tally-versus-SAP world — a third stream is reconciliation tooling. The firm operates a proprietary GST reconciliation engine (GST Recon Pro) developed specifically for the Indian multi-state, multi-ERP environment. It runs against GSTR-2B downloads and consolidated purchase data from any combination of ERP systems and produces month-end reconciliations with documented action items. The point of mentioning it here is not to sell the tool but to make a different argument: the work cannot reliably be done manually at scale, and the choice is between purpose-built tooling and persistent loss.

The cumulative effect of doing this work properly is the recovery of fifty to two hundred basis points of revenue annually, run-rate, with the largest gains concentrated in the first two years and a stable defensible compliance posture thereafter. For a ₹1,000 crore business, that is ₹5 to ₹20 crore of recovered margin, year after year, against an engagement cost that is a small fraction of any single year’s recovery.

The honest summary.

ITC loss is the largest avoidable indirect-tax exposure in Indian mid-cap and listed businesses today, and it persists because the discipline required to prevent it sits between the AP function and the indirect-tax function, in a space that neither typically owns end-to-end. A CFO who has not seen a quantified ITC-loss diagnostic for their business in the past two years is almost certainly carrying a recovery opportunity in the crore range, plus exposure to interest and penalty for credits taken in error.

The technical work of recovering ITC is not glamorous. It is line-by-line reconciliation, supplier follow-up, ERP configuration, and patient discipline applied month after month. The savings it produces are real, the exposure it prevents is real, and the audit-committee position it underpins — that the firm’s indirect-tax compliance is defensible under CARO 2020 Clause 9 and any future departmental scrutiny — is real. Few categories of finance work return as cleanly to the bottom line.

That, in a sentence, is the work the firm does.