Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
What GSTR-2B Is and Why It Drives ITC Claims
GSTR-2B is a static auto-populated statement generated by the GST portal on the 14th of each month. It aggregates the outward supply data filed by your suppliers in their GSTR-1 and GSTR-5 returns and presents it as your available Input Tax Credit for that month. Unlike GSTR-2A (which is dynamic and updates continuously), GSTR-2B is locked once generated — it represents ITC that was available as of the supplier filing cut-off date.
Under Rule 36(4) of the CGST Rules (as amended by the Finance Act 2022), provisional ITC — credit on invoices that appear in your purchase register but not in GSTR-2B — is no longer permissible in most circumstances. This means that your GSTR-3B ITC claim must be anchored in GSTR-2B, not just in your books of accounts. The reconciliation between the two is, therefore, a compliance requirement, not a best practice.
GSTR-2B reconciliation compares two datasets: the GSTR-2B statement (supplier-confirmed ITC) and your purchase register (internally recorded ITC). Discrepancies fall into structured categories, each with a different regulatory implication and resolution path.
What an Unreconciled GSTR-2B Costs You
The financial consequences of skipping GSTR-2B reconciliation are not abstract. They fall into three categories.
ITC reversal with interest
If your GSTR-3B claims ITC that does not appear in your GSTR-2B — because the supplier failed to file, filed incorrectly, or used the wrong GSTIN — the GST portal flags the discrepancy during auto-matching. A demand notice under Section 73 or 74 of the CGST Act follows. The demand includes the ITC amount, interest at 18% per annum from the date of incorrect claim, and a potential penalty of 100% of the tax amount in fraud cases. Even in non-fraud cases, interest alone on a ₹10 lakh ITC dispute over 12 months amounts to ₹1.8 lakhs.
Missed ITC from unrecorded supplier invoices
The reverse problem is equally costly: ITC that appears in GSTR-2B but was not recorded in your purchase register. This happens when a supplier has filed their GSTR-1 for an invoice you have not yet accounted for — a common scenario when GRN processing and accounts payable booking are not aligned. Failing to claim this ITC within the eligible period results in a permanent credit loss.
Year-end bulk reversal
Organisations that skip monthly reconciliation and attempt a year-end catch-up face a compounded problem. Supplier correction windows have closed for older months, making many mismatches unresolvable. The resulting ITC reversal at year-end is a direct cash outflow, often surfacing just as the finance team is managing other year-end obligations. Monthly reconciliation eliminates this by keeping the mismatch inventory current.
The GSTR-2B Reconciliation Process
A structured GSTR-2B reconciliation process runs monthly, between the 14th (when GSTR-2B is generated) and the GSTR-3B filing deadline. The process has five distinct steps.
Step 1 — Download GSTR-2B in JSON format
From the GST portal, download the GSTR-2B statement in JSON format for the relevant month. The JSON export contains structured data for B2B supplies, credit notes, import of goods, and import of services. Extract this into a tabular format with at minimum: supplier GSTIN, invoice number, invoice date, taxable value, IGST/CGST/SGST amounts, and ITC eligibility flag.
Step 2 — Export purchase register from ERP
Extract the purchase register for the same period from your ERP — SAP, Oracle NetSuite, Tally Prime, Zoho Books, or otherwise. The export should include: supplier GSTIN, invoice number as recorded in your system, invoice date, taxable value, GST amount, and the accounting date. The accounting date matters because a January invoice booked in February may appear in February's GSTR-2B, not January's.
Step 3 — Match on GSTIN and invoice number
Match each GSTR-2B entry to the corresponding purchase register entry using supplier GSTIN and invoice number as the primary key. Where both match, compare the taxable value and tax amounts. A difference of more than the configured tolerance (typically ₹1 for amounts over ₹10,000) is classified as an amount mismatch. Where no purchase register entry exists for a GSTR-2B entry, flag as "in GSTR-2B, not in books." Where no GSTR-2B entry exists for a purchase register line, flag as "in books, not in GSTR-2B."
Step 4 — Apply Section 17(5) blocked credit filter
Even if an invoice matches in both GSTR-2B and your purchase register, ITC may be blocked under Section 17(5) of the CGST Act. Common blocked categories include: motor vehicles (with exceptions), food and beverages, health club and fitness services, club memberships, travel benefits to employees, and works contract for immovable property. Apply your blocked credit configuration to identify and segregate ineligible ITC before determining the claimable amount.
Step 5 — Classify exceptions and initiate follow-up
Each mismatch category requires a specific action. Consolidate the exceptions by type, assign supplier follow-up to the accounts payable team for unfiled cases, and make a filing decision on whether to claim the provisional ITC this month or defer to next month once the mismatch is resolved.
GSTR-2B Mismatch Types and Actions
| Mismatch Type | ITC Status | Required Action |
|---|---|---|
| Supplier not filed | Not in GSTR-2B | Follow up with supplier to file GSTR-1; do not claim ITC |
| Amount mismatch | Partial or incorrect in GSTR-2B | Supplier files amendment; claim only confirmed GSTR-2B amount |
| GSTIN mismatch | In GSTR-2B under wrong GSTIN | Supplier correction return; confirm correct recipient GSTIN |
| In books, not in GSTR-2B | Provisional — not auto-populated | Assess Rule 36(4) eligibility; follow up with supplier |
| In GSTR-2B, not in books | Available but unrecorded | Identify supplier and book the purchase; claim ITC |
| Blocked credit (Section 17(5)) | In GSTR-2B but ineligible | Reverse ITC in GSTR-3B; document blocking reason |
Supplier Filing Compliance as a Prerequisite
The most common source of GSTR-2B mismatches — in volume if not in value — is supplier non-compliance. A supplier who files GSTR-1 after the 11th of the month, or files for a prior period, or files an incorrect return, all create mismatches in your GSTR-2B for the current month. Their correction flows into the next month's GSTR-2B.
Operationally, this means that a robust GSTR-2B reconciliation process must include supplier compliance monitoring: tracking which suppliers are consistently late filers, which are using incorrect GSTINs, and which have structural data quality issues (invoice number formats that don't match your purchase order system). For high-value suppliers with recurring mismatches, a standing follow-up protocol is more efficient than case-by-case resolution.
TransactIG's matching engine identifies recurring patterns in supplier mismatches and groups them by supplier for consolidated follow-up, rather than presenting each invoice as an independent exception. See also how GST input credit reconciliation works for retail and e-commerce where supplier volume is highest.
What Automated GSTR-2B Reconciliation Changes
Automated GSTR-2B reconciliation does not eliminate mismatches — supplier non-compliance is outside your control. What it eliminates is the time spent on data preparation, matching, and classification before the actual exception work begins.
Manual GSTR-2B reconciliation for an organisation with 300–500 purchase invoices per month typically takes 2 to 4 staff days. This includes downloading and formatting the GSTR-2B JSON, reformatting the ERP export, performing the VLOOKUP match, filtering Section 17(5) items, and organising the exception list. Automated matching compresses this to the exception review phase only — typically under 3 hours for the same volume.
The secondary benefit of automation is consistency. Manual GSTR-2B reconciliation produces different outputs depending on who does it and what version of the matching logic is in the spreadsheet. A structured reconciliation engine applies the same logic every month, with a documented audit trail that shows exactly which invoices were matched, which were deferred, and why.
For the full capability overview, see the reconciliation software guide covering TDS, GSTR-2B, platform settlements, and NACH in a single framework.