GSTR-2A vs GSTR-2B: What's the Difference and Which Should You Use?

GSTR-2A and GSTR-2B are both auto-generated, auto-populated GST statements that show the input tax credit (ITC) available to a business based on what its suppliers have reported — but they're built differently, updated differently, and used for genuinely different purposes, which is exactly why confusing them leads to real ITC reconciliation errors. Understanding the distinction matters for any GST-registered business that wants to claim ITC correctly and avoid a mismatch during filing or a later compliance query.

GSTR-2A — a dynamic, continuously-updating statement

GSTR-2A is a dynamic statement that reflects, in real time, every invoice your suppliers have reported against your GSTIN across their GSTR-1 (regular suppliers), GSTR-5 (non-resident suppliers), GSTR-6 (input service distributors), GSTR-7 (TDS deductors) and GSTR-8 (e-commerce operators) filings — and critically, it keeps changing after the fact, since a supplier who files their GSTR-1 late, or files an amendment to a previously-reported invoice, causes your GSTR-2A for that period to update retroactively, even well after the period has technically closed. This makes GSTR-2A useful as an ongoing, informational reference of what's been reported against you, but genuinely unreliable as a fixed number to reconcile ITC against for a specific filing period, since the figure you see today for a past month may not match what you saw when you actually filed that month's return.

GSTR-2B — a static, once-a-month snapshot

GSTR-2B, introduced specifically to solve GSTR-2A's instability problem, is a static statement generated once a month (typically on a fixed date, generally the 14th of the following month) that draws on supplier filings made up to a specific cut-off date — once generated, a given month's GSTR-2B does not change afterward, regardless of what suppliers file later. This fixed-in-time property is exactly why GSTR-2B, not GSTR-2A, is the statement GST rules specify as the actual basis for ITC reconciliation and eligibility determination when filing GSTR-3B — it gives a business a stable, unchanging number to reconcile its own purchase records against for that specific period.

Why the distinction was introduced in the first place

Before GSTR-2B existed, businesses reconciling ITC against GSTR-2A faced a genuine, recurring problem: the ITC figure they'd reconciled against and claimed in one month's return could later differ from what GSTR-2A showed for that same month once late-filing suppliers eventually reported their invoices, creating a moving target that was genuinely difficult to reconcile cleanly and consistently. GSTR-2B's fixed, once-a-month snapshot design directly addresses this — a business always has a stable, unchanging figure to reconcile against for each specific period, with any subsequently-reported invoices simply flowing into the *next* month's GSTR-2B rather than retroactively altering a period that's already been filed and closed.

What information each statement actually contains

• Both show: invoice-level details of purchases (invoice number, date, taxable value, tax amount) as reported by suppliers, categorized by whether the ITC is eligible or ineligible under specific GST rules.
• GSTR-2B additionally shows: a clear, categorized summary specifically designed for direct reconciliation against GSTR-3B — ITC available, ITC not available (with the specific reason), and a document-wise breakdown organized to match how GSTR-3B itself is structured.
• GSTR-2A additionally shows: real-time visibility into exactly when and how a supplier's filing changed, useful for tracking down a specific discrepancy or following up with a specific supplier about a missing or delayed invoice.

Reconciling your purchase records against GSTR-2B

The practical monthly workflow most GST-registered businesses follow: maintain your own purchase register (every purchase invoice you've received, whether or not the supplier has yet reported it), then each month compare that register against the newly-generated GSTR-2B to identify three categories of discrepancy — invoices in your register that GSTR-2B doesn't yet show (meaning the supplier hasn't filed, or filed late, past your cut-off), invoices GSTR-2B shows that aren't in your own register (worth double-checking for a genuine purchase you might have missed recording), and matched invoices where the reported tax amount differs from what you actually paid (worth following up with the supplier to correct). Only ITC that appears correctly in GSTR-2B should generally be claimed in that period's GSTR-3B — ITC for an invoice your supplier hasn't yet reported typically needs to wait until it appears in a future month's GSTR-2B, rather than being claimed provisionally based on your own purchase record alone.

What happens when a supplier files late

If a supplier reports an invoice after your GSTR-2B cut-off date for a given month, that invoice simply doesn't appear in that month's GSTR-2B at all — it will instead appear in a later month's GSTR-2B, once the supplier's filing is actually reflected before that later month's cut-off. This means the ITC for that specific invoice becomes claimable in the later period, not the original transaction period, which is a genuinely common and legitimate source of timing mismatch between when a purchase actually happened and when its ITC becomes claimable — not a compliance error on the purchasing business's part, simply a consequence of the supplier's own filing timeline.

Step-by-step: monthly ITC reconciliation using GSTR-2B

1. Maintain an accurate purchase register throughout the month as invoices are received, independent of whether suppliers have filed yet.
2. Once the current month's GSTR-2B is generated, download and compare it line-by-line against your purchase register.
3. Identify matched invoices (in both, tax amounts agree) — this ITC is generally safe to claim in the current GSTR-3B.
4. Flag invoices in your register missing from GSTR-2B — follow up with the relevant supplier about their filing status; don't claim this ITC until it appears in a GSTR-2B.
5. Flag invoices in GSTR-2B not in your register — verify whether this is a genuine purchase you missed recording, or a supplier error worth raising with them.
6. File GSTR-3B claiming only the ITC confirmed through this reconciliation against the current GSTR-2B.

Common mistakes with GSTR-2A and GSTR-2B

• Using GSTR-2A's real-time figure as the basis for claiming ITC in GSTR-3B, then finding it no longer matches once suppliers file later amendments.
• Not reconciling purchase records against GSTR-2B monthly, leading to accumulated, harder-to-untangle mismatches over several periods.
• Claiming ITC for an invoice not yet reflected in any GSTR-2B, based only on the business's own purchase record.
• Not following up promptly with suppliers whose invoices are consistently missing or delayed in GSTR-2B, letting a recoverable ITC amount sit unclaimed longer than necessary.
• Confusing which statement (2A vs 2B) is the actual required basis for ITC eligibility under current GST rules.

How GSTR-2B is organized to match GSTR-3B directly

GSTR-2B's summary section is specifically structured to mirror the exact table layout of GSTR-3B's ITC section — ITC available, split by category (inputs, capital goods, input services), and ITC not available, with the specific reason each item is ineligible (a supplier who opted for the composition scheme, an invoice past its eligibility timeline, a blocked credit category under Section 17(5)) — meaning a business can largely copy the relevant GSTR-2B figures directly into the corresponding GSTR-3B fields rather than needing to independently recompute or re-categorize the same information. This deliberate structural alignment is a large part of why GST rules moved toward using GSTR-2B as the standard reconciliation basis — it turns filing from a manual recomputation exercise into more of a verify-and-confirm exercise against an already-correctly-categorized statement.

What to do about mismatches you can't immediately resolve

Not every mismatch between your purchase register and GSTR-2B can be resolved before a filing deadline — a supplier might be unresponsive, or the discrepancy might need more investigation than the filing window allows. In this situation, the safer general practice is to claim only the ITC that's genuinely confirmed in the current GSTR-2B, holding back the unmatched amount rather than claiming it provisionally based on your own records alone — claiming ITC not yet reflected in GSTR-2B, even when you're confident the underlying purchase and invoice are genuine, creates a mismatch that can trigger a query later, whereas simply claiming that ITC in whichever later month's GSTR-2B it eventually appears in is the compliant path, even though it delays when that credit is actually usable.

The role of e-invoicing in reducing GSTR-2A/2B mismatches

For businesses subject to mandatory e-invoicing (above the applicable turnover threshold), invoices are reported to the government's Invoice Registration Portal at the time of issue, which meaningfully speeds up how quickly a supplier's invoice actually shows up in the recipient's GSTR-2A/2B compared to the older workflow of waiting for the supplier's periodic GSTR-1 filing — e-invoicing has, in practice, reduced the frequency and severity of the "supplier hasn't filed yet" mismatch category specifically for e-invoicing-eligible transactions, since the reporting happens much closer to the actual transaction date rather than being batched into a later periodic return filing.

Automating reconciliation at scale

For a business with a genuinely high volume of monthly purchase invoices, manual line-by-line comparison between a purchase register and GSTR-2B becomes impractical, which is why most mid-size and larger businesses use dedicated GST reconciliation software (or a module within their accounting/ERP system) that automatically downloads GSTR-2B data via API, matches it against the purchase register, and flags discrepancies for review rather than requiring manual comparison — this is worth investing in well before transaction volume makes manual reconciliation genuinely error-prone and time-consuming, rather than waiting until the manual process has already become a real operational bottleneck.

Why the ITC mismatch matters beyond just the current month

Unclaimed or incorrectly claimed ITC doesn't just affect the current period's tax outflow — a pattern of recurring, unresolved mismatches over several months can indicate a genuine, ongoing issue with a specific supplier's compliance (consistently late filing, for instance) that's worth addressing directly with that supplier or reconsidering the relationship over, rather than simply absorbing the recurring reconciliation friction month after month. Tracking mismatch patterns by supplier over time, not just resolving each month's discrepancies in isolation, surfaces this kind of systemic issue in a way a purely month-by-month reconciliation approach can miss.

How this connects to the broader annual GST filing cycle

Monthly GSTR-2B reconciliation feeds directly into the accuracy of the annual GSTR-9 return, which consolidates a full year's GSTR-1 and GSTR-3B data — a business that has reconciled carefully every month against GSTR-2B generally finds the annual return process considerably smoother than one that deferred reconciliation and is now trying to untangle a full year's accumulated mismatches retroactively. Treating GSTR-2B reconciliation as a genuine monthly discipline, not an occasional or year-end catch-up task, is what actually makes the annual filing process manageable rather than a significant, dreaded undertaking each year — the annual return, in effect, becomes a verification and consolidation step rather than the first time a full year's worth of mismatches is actually being confronted. Businesses that instead defer reconciliation until the annual filing deadline routinely find themselves chasing suppliers for old, hard-to-recall invoice details months after the fact, which is meaningfully harder than resolving the same discrepancy while it's still fresh in that month's reconciliation cycle, when the relevant transaction, invoice and context are all still readily available rather than needing to be reconstructed from memory or old correspondence months later, at which point even a cooperative supplier may struggle to quickly locate the specific records needed to resolve the discrepancy, turning what should be a quick fix into a genuinely time-consuming back-and-forth that could have been a five-minute email exchange had it been raised the same month the invoice was actually issued, simply because the relevant details were still top of mind for everyone involved rather than needing to be dug up from old records or painstakingly and slowly reconstructed piece by piece from memory and old correspondence months after the fact.