Fix GSTR-2B Mismatch: Match Your Purchase Register, Chase Suppliers and Claim the Right Credit
For accountants and GST filers facing a 2B that does not agree with the books: separate real differences from formatting noise, and settle them before GSTR-3B.
To fix GSTR-2B mismatch, first stop counting formatting as a difference. When a supplier files INV/2026/0042 and your clerk typed INV-2026-42, an exact match fails. A report of 400 unmatched lines, 390 of which are the same invoice, is how the real problems get missed.
Once the noise is gone, the remaining lines fall into a few kinds. Each has a clear owner: your team for register errors, the supplier for late or wrong filings.
This page gives the direct fix, an illustrative example from Vadodara, and how Apragya reconciles 2B against the purchase register.
Why GSTR-2B does not match, and the fix
GSTR-2B is the monthly statement of input tax credit built from what your suppliers reported. A mismatch means your purchase register and 2B disagree, and it comes in three kinds that need different fixes.
In books, not in 2B: the supplier filed late, filed under a wrong GSTIN, is a quarterly filer who has not uploaded yet, or never filed. Credit claimed on these can be questioned, so chase the supplier. In 2B, not in books: a bill you never received or never entered. Matched but different values: a typing error on one side, or a credit note on the other.
Invoice numbers written differently, such as INV/0042 and inv-42, cause many false mismatches. Clear those first.
- Download GSTR-2B for the month and take your purchase register for the same period.
- Match on supplier GSTIN, then invoice number ignoring punctuation and leading zeros, then date.
- Separate the results: matched, value mismatch, missing in 2B, missing in books.
- Fix your own errors in the register, such as wrong GSTIN, number or amount.
- Write to suppliers whose bills are missing or different in 2B.
- Book or query bills that appear only in 2B.
- Claim credit in GSTR-3B as the current rules allow, and keep the working.
What an unresolved 2B mismatch costs
Credit left unclaimed
Bills in 2B but not in books mean credit you never took.
Credit at risk
Credit claimed on bills missing from 2B may be reversed with interest.
Filing stress
The mismatch is found in the last two days before GSTR-3B.
Supplier friction
Suppliers are chased late and in a hurry.
An example: a Vadodara chemicals trader
Take an illustrative trader with about 600 purchase bills a month. A first exact match left 212 lines unmatched. The accountant ran the reconciliation in tiers.
The month's reconciliation, in tiers
GSTR-2B reconciliation run
GSTIN, number and date all agree.
Same invoice, number written differently.
Same invoice, different tax amount.
Suppliers late or used a wrong GSTIN.
Bills never received or entered.
Number matches, date far apart.
The nine value mismatches were mostly typing errors on the trader's side and were corrected. The 22 suppliers missing from 2B were written to, and credit on those bills was held back. Four of the bills missing in books turned out to be deliveries still in transit.
How Apragya handles GSTR 2B reconciliation
Step 1 of 5
Import the 2B file
Load the JSON downloaded from the GST portal; every import is kept.
- Import the 2B file: Load the JSON downloaded from the GST portal; every import is kept.
- Match in tiers: Exact, normalised and fuzzy matches, each labelled so you know which is a fact.
- Values compared: Tax differences beyond a small tolerance are shown as mismatches.
- Both directions: Missing in 2B and missing in books are listed separately.
- Into GSTR-3B: GSTR-3B is built from the same records, with reversals recorded.
GSTR-2B vs purchase register: spreadsheet or reconciler
Spreadsheet matching with VLOOKUP breaks on the first invoice number written differently. A reconciler that normalises numbers and labels its confidence gives the filer a short list of real problems.
Spreadsheet reconciliation, against Apragya
| Feature | Spreadsheet lookup | Apragya |
|---|---|---|
| Invoice numbers | Exact text only | Punctuation and zeros ignored |
| Confidence | Not shown | Exact, normalised or fuzzy |
| Value differences | Mixed in with unmatched | Shown as mismatches |
| Earlier imports | Overwritten | Every import kept |
| Return | Retyped into GSTR-3B | Built from the same records |
Checked against public information on 16 September 2026.
What keeps 2B differences small
One purchase record
Bills from purchase and accounts are one register.
GSTIN validated
Supplier GSTINs are checked when the vendor is set up.
Bills read for you
Supplier PDFs are read, so bill numbers are not retyped.
Filed periods lock
A filed return period moves to locked, not back to open.
Audit log
Who changed a bill, and when, is logged.
Human review
Fuzzy matches are suggestions for a person to confirm.
See GSTR-2B reconciliation and the purchase register, and read the GSTR-2B reconciliation guide. If credit is missing altogether, read how to fix input tax credit not reflecting.
Getting started
- Import last month's GSTR-2B.
- Review value mismatches first.
- Write to suppliers missing from 2B.
- Enter or query bills missing in books.
- Repeat each month before GSTR-3B.
The second month is always easier, because supplier and number errors have been fixed at source.
What it costs to start
GSTR-2B mismatch, answered
Can we claim credit on a bill not in GSTR-2B?
Why does the same invoice show as unmatched?
What if the supplier filed a different amount?
Should we reconcile monthly?
What does it cost to start?
Reconcile 2B in minutes, not days
Import a month's GSTR-2B and see which differences are real.