Key takeaways
- GSTR-2B is static and therefore auditable; GSTR-2A changes continuously. Only the static statement can serve as the control document for a signed-off reconciliation.
- Match in tiers - exact, near match on value, near match on reference, missing on either side - because the tier determines the action and allows follow-up to be automated.
- Separate the ledger accounts: credit availed, credit parked pending supplier reporting, temporary reversals expected to be re-availed, and credit written off. Age the parked balance monthly.
- Permanent and temporary reversals must be reported separately in Table 4 of GSTR-3B, and the 180-day payment rule interacts with any payment-hold policy applied to suppliers.
- Credit has an outer availment deadline. A mismatch found in month two is administrative; the same mismatch found in month fourteen is a write-off.
Input tax credit stopped being an accounting entry and became a cash flow risk the day provisional credit was withdrawn. Under the current framework, a growing business can only claim what its suppliers have actually reported. The gap between the credit a company believes it has earned and the credit the GST system will allow is, in practice, a working capital leak that widens quietly across the year and then surfaces in a departmental notice.
The remedy is not more effort at year end. It is a monthly control framework built into the close, with defined matching logic, defined tolerances, defined owners and a ledger structure that makes unclaimed credit visible on the balance sheet rather than buried in expense.
GSTR-2B is the control document
GSTR-2A and GSTR-2B are frequently used interchangeably and should not be. GSTR-2A is a dynamic statement that updates continuously as suppliers file, so the same period viewed on two dates shows two different figures. GSTR-2B is static: it is auto-drafted once for a return period, covering documents furnished by suppliers within a defined window, and it does not change afterwards. Because it is fixed, it is the only version that can serve as an auditable control document — you can reconcile to it, sign it off, and reproduce the same result twelve months later during an audit.
Eligibility flags are a starting point, not a conclusion
GSTR-2B also carries eligibility flags at document level, distinguishing credit available from credit unavailable — for example where the place of supply and the recipient’s state make the credit unusable, or where the document falls outside the period permitted for availment. Those flags are a starting point for classification, not a conclusion; the ineligibility tests under Section 17(5) are the recipient’s responsibility and cannot be delegated to the portal.
The legal basis for the reconciliation
Section 16(2) of the CGST Act sets out cumulative conditions for availing input tax credit. In substance the recipient must hold a tax invoice or prescribed document; the details of that document must have been furnished by the supplier and communicated to the recipient — the clause that converts GSTR-2B from an information tool into a statutory gate; the recipient must have received the goods or services; the tax must have actually been paid to the government; and the recipient must have furnished the relevant return.
Two further provisions shape the monthly discipline. Credit availed on an invoice not paid to the supplier within one hundred and eighty days must be reversed with interest, and re-availed on payment. And there is an outer time limit for availing credit for a financial year, tied to the November return of the following year or the filing of the annual return, whichever is earlier — after which unreconciled credit is simply lost. That deadline is why a mismatch discovered in month two is an administrative task and the same mismatch discovered in month fourteen is a write-off.
The reporting structure in Table 4 of GSTR-3B follows the same logic, separating credit availed, reversals that are permanent in nature from those that are temporary and re-claimable, and ineligible credit. A reconciliation process that does not distinguish permanent from temporary reversals will not produce a correct GSTR-3B, and will make the annual reconciliation in GSTR-9 and GSTR-9C considerably harder.
Why mismatches happen
Five families of difference
Almost all differences fall into five families. Categorising them at the point of identification is what allows the follow-up to be automated later.
- Supplier-side timing. The supplier filed GSTR-1 late, or reported the invoice in a later period. The credit is not lost; it appears in a subsequent GSTR-2B. This is the largest category by volume and the least serious.
- Supplier-side non-compliance. The supplier has not filed at all, has reported the invoice against a different GSTIN, or has reported it as B2C. Credit is at genuine risk and the exposure grows with the supplier’s deterioration.
- Data quality on either side. Invoice number captured with different prefixes, leading zeros, slashes or spacing; invoice date entered as the receipt date; taxable value differing because of rounding, discount treatment or freight; wrong tax head — IGST recorded where the supplier charged CGST and SGST, or the reverse.
- Structural differences. Import IGST flowing through the bill of entry, credit distributed by an input service distributor, reverse charge liabilities that do not appear as supplier documents at all, credit notes and amendments landing in a different period from the original invoice.
- Recipient-side process gaps. Invoices booked in the wrong period, goods received but invoice not booked, or invoices booked against the wrong GSTIN in a multi-state registration structure.
The matching logic
A reconciliation engine, whether a tool or a well-built workbook, should apply matching in tiers and label the outcome. The tier is what determines the action.
| Tier | Match basis | Treatment |
|---|---|---|
| Exact | Supplier GSTIN, document type, document number, document date, taxable value and each tax head all agree | Claim. No further action. |
| Near match — value | Key fields agree; taxable value or tax differs within a defined tolerance | Claim the lower of the two; log the difference for supplier follow-up if it recurs. |
| Near match — reference | Document number differs only after normalisation (case, spaces, slashes, leading zeros); other fields agree | Claim. Fix the master data or the capture rule that caused it. |
| In books, not in 2B | Purchase recorded; no corresponding document in the statement | Do not claim. Park the credit, age it, and open supplier follow-up. |
| In 2B, not in books | Supplier has reported a document the recipient has not recorded | Investigate. Either a missing purchase entry, a wrongly addressed invoice, or a fraudulent document reported against your GSTIN. |
| Period difference | Document matched to a prior or subsequent period’s statement | Claim in the period it appears; maintain a bridge so the annual reconciliation ties. |
| Ineligible | Blocked under Section 17(5), or attributable to exempt or personal use under Rules 42 and 43 | Do not claim; charge to cost or reverse with the correct classification in Table 4. |
Setting the tolerance
Set the value tolerance explicitly — a small absolute amount per document, not a percentage, works better at high volume — and document it as a policy. An undocumented tolerance applied by a preparer is an audit finding waiting to happen.
The monthly control calendar
Fit the reconciliation to the statutory rhythm rather than treating it as a separate exercise.
- Through the month. Purchase invoices are captured with GSTIN, document number, date and tax heads validated at entry. Vendor master GSTINs are verified at onboarding and re-validated periodically for registration status.
- Working day one to three of the following month. Purchase register closed and locked for the period. Reverse charge liabilities identified. Import documents and ISD credits assembled.
- Once GSTR-2B is generated for the period. Download and run the match. Produce the tiered exception report.
- Before the GSTR-3B due date. Classify each exception, determine what is claimed, what is parked and what is reversed. Prepare the Table 4 workings with permanent and temporary reversals separated. Obtain review sign-off from someone other than the preparer.
- Within the following week. Issue supplier follow-up on unmatched items, escalating by ageing bucket. Update the parked credit ledger.
- Quarterly. Review ageing of parked credit, run the 180-day payment test under Rule 37, and identify items approaching the availment deadline.
- Annually. Reconcile books, GSTR-3B, GSTR-2B and GSTR-9 with a documented bridge before filing GSTR-9C.
Make the exposure visible in the ledger
The single change that most improves behaviour is separating the credit accounts. Rather than one input tax account, maintain at minimum: credit availed and reflected in the electronic credit ledger; credit parked pending supplier reporting; credit reversed temporarily and expected to be re-availed; and credit written off as unrecoverable. The parked balance, aged in buckets, becomes a standing item in the month-end pack. When it appears next to receivables and inventory in a management review, it gets managed. When it sits inside a single input tax account, it does not.
Commercial levers with suppliers
Reconciliation alone does not recover credit; supplier behaviour does. The practical levers are contractual and procedural.
- A purchase contract clause making the supplier responsible for correct and timely reporting, and permitting recovery of credit lost through their default.
- A payment-hold policy for the tax component where an invoice remains unreported beyond an agreed window, applied consistently and communicated at onboarding rather than invoked as a surprise.
- A vendor compliance rating maintained alongside the vendor master, refreshed with filing status, and used in sourcing decisions.
- A single escalation template with the document details attached, so the supplier’s finance team can act without a second exchange.
Care is needed on payment holds: the 180-day rule cuts the other way, so withholding payment beyond that window on an invoice where credit has been availed triggers a reversal of your own. The two policies must be designed together.
Automation, in the right order
Sequencing matters more than tool selection. Clean the vendor master and the invoice capture rules first; a reconciliation engine fed inconsistent document numbers produces a large exception list and no benefit. Then automate retrieval and matching. Options range from GST suite tools that connect through the GST Suvidha Provider network, to ERP add-ons that match inside the purchase ledger, to a maintained internal pipeline where volumes and data science capability justify it. The Invoice Management System on the GST portal, which allows recipients to accept, reject or keep documents pending before they flow into GSTR-2B, changes the workflow further by shifting part of the exception handling upstream. the operational rules and effective dates for the Invoice Management System as they apply to the entity’s registration type on the date of filing
Whatever the tool, retain three things: the downloaded statement as filed, the matching output, and the reviewer’s sign-off. Reproducibility is what a departmental audit tests.
Metrics worth reporting
- Match rate by value and by document count, monthly.
- Parked credit balance, aged, as a percentage of monthly credit availed.
- Credit at risk of lapsing within the next two quarters.
- Number of suppliers responsible for the top eighty per cent of unmatched value.
- Temporary reversals outstanding under Rule 37 and their expected re-availment date.
- Difference between credit as per books and the electronic credit ledger, explained in full.
Artham Fintech runs GSTR-2B and purchase-register reconciliation as a managed monthly control for growing businesses, including exception categorisation, supplier follow-up and the ledger design that keeps parked credit visible. If your unmatched credit balance has not been aged recently, that is usually the place to start.