GSTR-2B vs GSTR-2A: Which One Actually Governs Your ITC Claim

GSTR-2A and GSTR-2B both do the same basic job on the surface: they show you, invoice by invoice, what your suppliers have reported against your GSTIN in their own GST filings. Because they're built from the same underlying data, it's tempting to treat them as interchangeable, especially when accounting software surfaces both on the same dashboard without explaining which one actually matters. They are not interchangeable, and the difference isn't cosmetic. GSTR-2A keeps changing after the period it covers has technically closed. GSTR-2B does not. That single behavioural difference is why current GST practice treats GSTR-2B, not GSTR-2A, as the statement your eligible input tax credit for a period is actually measured against, and why reconciling against the wrong one produces ITC numbers that don't hold up once anyone checks them closely. This post is about that mechanical difference and the reconciliation workflow it drives. The underlying ITC eligibility conditions, Section 16, blocked credits, and the rest, are covered in full in our guide to input tax credit rules and mistakes.

Two Statements Built From the Same Supplier Data

Both GSTR-2A and GSTR-2B are auto-generated statements. You don't file either one yourself, and neither involves any manual data entry on your end. Both compile invoices your suppliers have uploaded and reported through their own GSTR-1, or the Invoice Furnishing Facility if they're on the QRMP scheme, for supplies made against your GSTIN. In that sense they're pulling from the same well: your suppliers' filings, not your own books. Where they diverge completely is in how that underlying data actually reaches you, and whether it stays put once it does. GSTR-2A is built to reflect supplier filings as they happen, continuously. GSTR-2B is built to freeze a version of that same data at a fixed point each period. That one design choice is what the rest of this comes down to, and it sits right in the middle of the monthly cycle this site covers in our guide to the GSTR-1 and GSTR-3B filing cycle: GSTR-1 is what your suppliers file, GSTR-2A or GSTR-2B is what you see of it, and GSTR-3B is where you act on it.

GSTR-2A Is Dynamic: The Same Period Can Look Different Every Time You Check

GSTR-2A updates in near real time. The moment a supplier uploads an invoice or files their GSTR-1, it generally reflects in your GSTR-2A almost immediately, without waiting for any fixed cut-off. That sounds convenient until you notice what it means for a period that's supposedly already closed: if a supplier files their GSTR-1 late, weeks or months after the original due date, that invoice still lands in your GSTR-2A against the original invoice period once they finally file. Worse, if a supplier later amends or deletes an invoice they'd already reported, even one belonging to several periods back, that change flows straight into GSTR-2A and quietly rewrites what it shows for that earlier period. Pull your GSTR-2A for a given month today, then pull it again for that same month three months from now, and you can get two different sets of numbers, both technically accurate at the moment you pulled them.

That cuts both ways for anyone using GSTR-2A to work out a period's ITC claim. Check too early, before a slow supplier has actually filed, and you understate your eligible credit for the period, missing something that would have shown up a few weeks later. Check again after the fact, once a supplier has gone back and amended an invoice from an earlier period, and you risk claiming the same credit twice: once against whatever you originally recorded, and again against the amended entry that quietly replaced it in GSTR-2A. Neither error is exotic. Both are a direct, mechanical consequence of reconciling against a statement that was never meant to hold still.

GSTR-2B Is Static: Generated Once, and It Doesn't Move After That

GSTR-2B breaks that cycle by design. For each return period, it's generated exactly once, compiling whatever your suppliers had filed up to a fixed cut-off, generated on the 14th of the following month. Once GSTR-2B is generated for a period, it does not change again, no matter what your suppliers do afterward. If a supplier files their GSTR-1 late, after that cut-off has passed, the invoice does not retroactively appear in the earlier period's already-generated GSTR-2B. It shows up in the following period's GSTR-2B instead. If a supplier amends an invoice that belongs to an earlier period, that amendment flows into the GSTR-2B for whichever period the amendment itself was filed in, not into the original period's statement, which stays exactly as it was when it was first generated. That's the entire point of calling it static: it hands you one number, locked at a known point in time, that you can reconcile a period's ITC claim against without worrying that it'll look different if you check again next month. It's also why current return-filing practice ties eligible ITC specifically to what appears in GSTR-2B for a period or an earlier one, a rule our guide to ITC conditions and mistakes covers in more depth.

GSTR-2A vs GSTR-2B at a Glance

Once the dynamic-versus-static distinction is clear, most of the practical differences follow from it directly. Here's how the two compare on the points that actually decide which one you should be working from.

The Reconciliation Workflow: Matching Your Purchase Register Against GSTR-2B

Once GSTR-2B is generated for a period, the actual reconciliation work is a straightforward match: line up your purchase register against GSTR-2B for that period, invoice by invoice, not just by total value. Two kinds of mismatch turn up, and they mean different things. An invoice sitting in your purchase register that's missing from GSTR-2B usually means your supplier hasn't uploaded or filed it yet, or filed it after the cut-off for this period. That credit generally isn't available to claim this period. It needs supplier follow-up, and it becomes claimable once it actually appears in a later period's GSTR-2B. An invoice sitting in GSTR-2B that you can't find in your own purchase register cuts the other way: either it's a genuine purchase your books haven't captured yet, in which case you've likely been under-claiming credit you're entitled to, or a supplier has wrongly quoted your GSTIN against an invoice that isn't actually yours, which needs to be flagged rather than claimed.

• Wait for GSTR-2B to generate for the period before finalising your ITC claim, rather than working off GSTR-2A or the purchase register alone.
• Match every invoice in your purchase register against GSTR-2B line by line, not just by comparing totals.
• For invoices in your purchase register that are missing from GSTR-2B, hold off claiming that credit this period and follow up with the supplier directly.
• For invoices in GSTR-2B that you can't trace in your purchase register, check whether it's a genuine credit you missed booking or an invoice wrongly reported against your GSTIN.
• Log which suppliers show up late or missing in GSTR-2B more than once. A repeat pattern is worth raising directly, not chasing fresh every month.
• Treat this reconciliation as a recurring task ahead of every GSTR-3B filing, not an exercise you only run after a mismatch notice forces it.

A supplier who's occasionally a few days late filing is a minor irritation you absorb and move on from. A supplier who shows up late, or missing altogether, in GSTR-2B month after month is a different kind of problem: it's a recurring drag on your own cash flow, since that credit sits unavailable to you for as long as they delay, however good their reasons are. It's worth tracking this by vendor over a few months rather than treating each month's gap as a one-off surprise, and worth raising directly, in commercial terms if needed, with the suppliers who show the pattern repeatedly. Their filing discipline is, in effect, being funded by your working capital until they fix it.