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.
GSTR-2A vs GSTR-2B: Key Differences
GSTR-2A and GSTR-2B both contain supplier-reported data, but they serve fundamentally different purposes in the ITC claim process. Confusing the two leads to either over-claiming (resulting in demand notices) or under-claiming (resulting in permanent ITC loss).
GSTR-2A is dynamic. It updates in real time as suppliers file their GSTR-1 returns. If a supplier files an amendment or a late return, your GSTR-2A changes retroactively. This makes GSTR-2A unreliable as a reconciliation anchor — the data you downloaded on the 15th may differ from what appears on the 20th. GSTR-2A is useful as a reference for tracking supplier filing behaviour, but it should not be used as the basis for ITC claims.
GSTR-2B is static. It locks on the 14th of each month based on all GSTR-1 filings received up to the 11th (and IFF filings up to the 13th for quarterly filers). Once generated, GSTR-2B does not change for that period. Any supplier corrections made after the cut-off date flow into the next month's GSTR-2B.
Under Rule 36(4) of the CGST Rules, ITC can only be claimed based on GSTR-2B. The rule eliminated the earlier provisional ITC allowance (which permitted claiming up to 5% over GSTR-2A). This means GSTR-2B is the authoritative source for ITC eligibility, and all reconciliation must be performed against GSTR-2B, not GSTR-2A. GSTR-2A retains value only for monitoring supplier filing patterns and identifying invoices that will appear in future GSTR-2B statements.
Invoice Management System (IMS) and GSTR-2B
The Invoice Management System (IMS), live on the GST portal since October 2024, adds a new layer between supplier filing and GSTR-2B generation. IMS allows recipients to explicitly accept, reject, or keep pending each invoice reported by their suppliers before it flows into GSTR-2B. This changes the reconciliation workflow significantly.
How IMS works: After a supplier files GSTR-1, the invoice appears in the recipient's IMS dashboard. The recipient can take one of three actions: Accept (invoice flows into GSTR-2B as eligible ITC), Reject (invoice is excluded from GSTR-2B and communicated back to the supplier), or No Action (deemed acceptance — the invoice flows into GSTR-2B by default). The deemed acceptance mechanism means that IMS does not create additional work for organisations that do not wish to use it — inaction produces the same result as the pre-IMS system.
Critical operational guidance: Never reject an invoice on IMS unless you are certain it does not belong to you. Once rejected, the invoice is excluded from your GSTR-2B and communicated to the supplier as disputed. If the invoice is legitimate but contains an error (wrong amount, wrong GSTIN), use the Pending action instead and follow up with the supplier for correction. Rejection is irreversible for that period — the corrected invoice can only appear in a future month's GSTR-2B.
With IMS, reconciliation now operates at two levels: first, your purchase register against the GSTR-2B statement (as before), and second, your ITC ledger against the IMS dashboard to verify that acceptance/rejection actions align with your books. Organisations with 500+ purchase invoices per month should integrate IMS review into their pre-GSTR-3B workflow to prevent mismatches between IMS actions and booked ITC. For more on IMS, see our detailed guide on IMS reconciliation.
Rule 88D and DRC-01C: The 7-Day Compliance Clock
Rule 88D of the CGST Rules introduced an automated mismatch detection mechanism. When the ITC claimed in your GSTR-3B exceeds the ITC available in your GSTR-2B by more than a prescribed threshold, the GST portal auto-generates a DRC-01C notice. This notice requires a response within 7 days — a tight window that demands proactive reconciliation rather than reactive correction.
The escalation sequence is severe. If the taxpayer does not respond to DRC-01C within 7 days, the GST portal may block GSTR-1 filing for subsequent periods. Blocked GSTR-1 filing means your outward supply data does not reach your customers' GSTR-2B, cascading the compliance failure downstream. If the mismatch remains unresolved, it triggers a formal demand under Section 73 (for non-fraud cases, with a 3-year limitation) or Section 74 (for fraud/suppression cases, with a 5-year limitation). In extreme cases, persistent non-compliance can lead to registration cancellation under Rule 21(e) — suo motu cancellation by the tax officer.
The response to DRC-01C requires either: (a) paying the differential tax with interest through DRC-03, or (b) providing a detailed explanation for why the excess ITC claim is legitimate (for example, ITC carried forward from a prior period, or ITC on imports not reflected in GSTR-2B). A vague or generic response is treated as non-response.
The practical implication is clear: GSTR-2B reconciliation must be completed before GSTR-3B filing, not after. Organisations that file GSTR-3B based on their books and reconcile later are structurally exposed to DRC-01C notices every month. For a detailed walkthrough of the DRC-01C response process, see our guide on DRC-01C ITC mismatch reconciliation.