GSTR-2B vs Purchase Register Reconciliation: Monthly Workflow for Indian Buyers

GSTR-2B is the static, auto-drafted input tax credit statement that the GST portal publishes on the 14th of every month. For an Indian buyer, it is no longer a reference document — it is the legal gate for input tax credit. Under Section 16(2)(aa) of the CGST Act, no ITC can be claimed unless the invoice appears in 2B. Rule 36(4)‘s old 10 percent provisional cushion was withdrawn from 1 January 2022, and the Invoice Management System has, since October 2025, given buyers explicit accept-reject-pending control over what flows into their 2B.

This article walks through the monthly reconciliation cycle that finance teams now run between their purchase register and GSTR-2B — what to download, how to match, where to bucket gaps, when to chase suppliers, and how to land a defensible Table 4 ITC claim before the 20th.

Quick reference: the monthly 2B cycle

Why GSTR-2B replaced GSTR-2A as the source of truth

GSTR-2A is dynamic — it keeps updating as suppliers file or amend. That made it impossible to use as a legal claim basis, because the same period’s ITC could change retrospectively. GSTR-2B fixes a snapshot: invoices filed by suppliers between the 12th of the prior month and the 11th of the current month flow into the 2B that publishes on the 14th. Anything supplier-filed after the 11th cut-off rolls forward to the next month’s 2B.

Section 16(2)(aa), inserted by the Finance Act 2021 and effective from 1 January 2022, made this snapshot decisive. ITC is conditional on the invoice being communicated to the recipient under Section 37, and 2B is the operative communication. No 2B line, no ITC — full stop.

What is Section 16(2)(aa) and how does it constrain monthly ITC

Section 16(2)(aa) layers an additional condition over the four existing 16(2) conditions for ITC claim — possession of tax invoice, receipt of goods or services, tax actually paid by supplier, and return furnished. The new condition is that the supplier must have furnished the invoice details under Section 37 and they must have been communicated to the recipient. The mechanism for that communication is GSTR-2B.

Practically this means three things for the monthly cycle:

• Any invoice in the purchase register that does not appear in the corresponding 2B cannot be claimed in that month’s 3B, even if the buyer holds a valid tax invoice and has received the goods.
• The buyer cannot self-certify or provisionally claim — the old Rule 36(4) buffer of 10 percent, then 5 percent, then zero, is gone.
• An ITC claim taken in 3B that exceeds the 2B figure by the threshold prescribed under Rule 88D triggers a system-generated DRC-01C intimation requiring the buyer to explain the excess or pay it back with interest.

What is the IMS overlay and how does it change the workflow

Invoice Management System went live in October 2024 and became the default 2B generation mechanism from October 2025. Before IMS, 2B was a passive auto-population of whatever suppliers filed. With IMS, every supplier-uploaded invoice lands on the buyer’s IMS dashboard with three possible actions:

• Accept — the invoice flows into the next 2B and becomes eligible ITC, subject to other Section 16 conditions.
• Reject — the invoice is dropped, the supplier’s tax liability stands, and the buyer cannot claim ITC. The supplier sees the rejection and can correct through GSTR-1A or amendment.
• Pending — the invoice is held over to a future tax period. Useful when goods have not yet been received or when the buyer wants to verify before action.

If no action is taken, the invoice is deemed accepted. The IMS action is locked at the 14th when 2B is generated. This shifts part of the reconciliation work from the post-14th window into the through-the-month period, because actions taken earlier reduce the size of the 14th-day workload.

The match keys: how to align 2B and purchase register lines

A clean match between 2B and the purchase register needs at least four keys to be consistent:

1. Supplier GSTIN — 15-character string, case-insensitive, but must be exact. PR entries often carry stale GSTINs for suppliers who migrated states or restructured.
2. Invoice number — normalize for leading zeros, prefixes such as INV/ or 2026-27/, and case. Many ERP exports pad invoice numbers; many supplier filings strip them.
3. Invoice date — must fall in the supplier’s filing tax period for the invoice to be in this month’s 2B.
4. Taxable value and tax components — CGST, SGST, IGST, cess. A two-rupee mismatch is usually rounding; a 200-rupee mismatch is a rate or quantity error worth investigating.

A robust reconciliation also handles credit notes, debit notes, and amendments as separate document types — netting them silently into the invoice line is a common source of disputed audit findings.

A worked example: 2,400 monthly invoices

Consider a mid-market manufacturer with 2,400 supplier invoices in May 2026’s purchase register, total taxable value ₹ 48 crore, total ITC at stake ₹ 8.64 crore (assume 18 percent blended GST). On the 14th of June, 2B is downloaded. After matching, the breakdown looks like this:

• 2,100 invoices matched cleanly — same GSTIN, invoice number, date, and amounts within ₹ 5 tolerance. ITC: ₹ 7.56 crore. These flow straight into Table 4(A)(5) of June’s 3B.
• 180 invoices in 2B but not in PR — ITC value approximately ₹ 64.8 lakh. These need internal investigation: goods received but invoice not booked, invoice booked in a different cost centre, or duplicate supplier code in the ERP. Each must be either booked into PR before claim or flagged as unauthorised.
• 90 invoices in PR but not in 2B — ITC value approximately ₹ 32.4 lakh. This is blocked under Section 16(2)(aa). The team triggers supplier follow-up: 50 are suppliers who filed late and will appear in July’s 2B, 30 are filed against wrong GSTIN and need amendment, 10 are non-filers with credit at risk under Section 16(4).
• 30 invoices with amount mismatch — ITC delta approximately ₹ 11 lakh. Twelve are rounding within ₹ 10, fifteen are rate misclassifications by the supplier, three are quantity disputes that go back to procurement.

The team’s claim in June’s 3B Table 4(A) is ₹ 7.56 crore plus the cleanly matched portion of mismatches that the supplier corrects by the 19th — call it ₹ 7.61 crore. ₹ 32.4 lakh moves to a tracker for July 2B, and ₹ 64.8 lakh of 2B-only entries either gets booked or rejected through IMS.

Want to size this exposure for your own ledger before running it manually? The ITC Leakage Calculator estimates locked ITC by invoice volume and supplier-mix risk in under two minutes.

How does Section 16(4) cap the time available to fix gaps

Section 16(4) sets a hard outer limit. ITC on any invoice of a financial year must be claimed by the earlier of:

• The 30th of November of the following financial year, or
• The date of filing the annual return for that financial year.

For an invoice dated April 2026, the ITC window closes on 30 November 2027. For one dated March 2026, the window closes on 30 November 2026 — under eight months. Every PR-only entry that sits unresolved through monthly cycles is consuming this clock. By month six of unresolved status, an invoice should be on a recovery-or-write-off decision path.

What is Rule 88D and why does it matter for the 3B filing

Rule 88D, introduced in 2023, is the automated mismatch enforcement mechanism. If the ITC claimed in Table 4(A) of GSTR-3B exceeds the ITC available in the corresponding 2B by more than the prescribed threshold — currently 20 percent and ₹ 25 lakh — the portal issues a DRC-01C intimation. The buyer must, within seven days, either pay the differential with interest through DRC-03 or reply explaining the variance.

This makes the 2B-to-3B linkage a hard reconciliation, not a target. A defensible monthly close needs the Table 4 figures to tie back, line by line, to either a 2B entry or a documented exception such as reclaimed ITC, import IGST, or RCM credit, none of which appear in 2B.

How does Section 17(5) interact with the 2B match

Section 17(5) lists blocked credits — motor vehicles, food and beverages, club memberships, construction of immovable property, personal consumption, and others. These invoices may appear correctly in 2B but cannot be claimed. The monthly workflow must therefore include a 17(5) screening pass on the 2B-matched bucket before computing Table 4(A)(5). The reversal flows through Table 4(B)(1).

A clean ITC ledger separates four buckets in 3B Table 4: gross ITC available from 2B, ITC reversed under Rule 42 and 43 for exempt and personal use, ITC reversed under Section 17(5) for blocked credits, and ITC reclaimed under Rule 37 after payment to suppliers within 180 days.

What does a supplier follow-up workflow look like

For the 90 PR-only invoices in the worked example, the follow-up is not a single email. A structured cycle looks like:

• Day 14 to 15 — system-generated supplier statement with the missing invoice list, sent through a supplier portal or email with the GSTIN, invoice number, date, and amount.
• Day 16 to 17 — phone follow-up on the top 20 by ITC value, which usually covers 70 to 80 percent of the rupee exposure.
• Day 18 — escalation to procurement or the supplier-relationship owner for non-responsive suppliers.
• Month-end — payment hold workflow for suppliers whose ITC has been missing for two consecutive cycles, often automated through Section 16(2)(c) clauses in the supplier agreement.

A buyer with strong purchase-side leverage can recover most month-one gaps within the same filing window. A buyer without that leverage runs a rolling tracker and absorbs the working-capital cost of locked ITC.

Closing the loop into GSTR-3B Table 4 and the audit trail

The final step of the cycle is computing Table 4 of GSTR-3B. The reconciled figure is:

• Table 4(A)(5) all-other ITC — the cleanly matched 2B figure plus inward supplies under reverse charge plus import IGST from ICEGATE.
• Table 4(B)(1) — Section 17(5) reversals plus Rule 42 and 43 reversals.
• Table 4(B)(2) — temporary reversals such as 180-day non-payment under Rule 37 and ineligible ITC under Rule 38.
• Table 4(D)(1) — ITC reclaimed that was previously reversed.

Every figure should trace back to a documented line. For audit defence — whether a Section 65 audit, a Section 66 special audit, or a DRC-01 dispute — the buyer needs to show the 2B line, the PR line, the IMS action, and the reconciliation working for each material item. Storing the 2B JSON, the PR export, and the matched output as immutable monthly artefacts is the simplest way to preserve that trail.

Where this fits in the broader GST reconciliation stack

Monthly 2B-to-PR matching is one of five reconciliations a GST-compliant buyer runs through the year. The others are GSTR-1 to sales register on the outward side, GSTR-3B to books on the liability side, annual GSTR-9 to books on consolidation, and GSTR-9C reconciliation statement at audit. The 2B workflow described here is the highest-frequency and highest-rupee-volume of the five, and it sets the quality bar for the rest.

Teams running this manually in Excel can hold quality at 500 to 800 invoices per month with discipline. Beyond that, the work pattern needs system support — for fuzzy invoice-number matching, for IMS action staging, for supplier-follow-up tracking, and for the audit-trail archive. See the GST reconciliation software overview for what that support looks like in production, and the reconciliation software India page for the broader category context covering GST alongside bank, TDS, and platform-settlement reconciliations.