Your GSTR-2B VLOOKUP keeps flagging real matches as mismatches. Here's what one lookup column can't see
A plain VLOOKUP on invoice number alone breaks because GSTR-2B matching needs more than text equality — even GSTN's own Matching Offline Tool checks GSTIN, document type, date and value together, not the invoice number in isolation. Build a normalised GSTIN-plus-invoice-number key, match credit notes as their own document type netted per GSTIN rather than to one invoice, watch for amendments that revise the invoice number itself, and keep a running list for invoices your books have that 2B doesn't yet.
The generic "download 2B, VLOOKUP against your purchase register" tutorial works for the clean part of a purchase register and quietly breaks on the rest. Four specific patterns — a reformatted invoice number, a duplicate number from a different vendor, an amendment row, a credit note — are exactly what a single-column lookup cannot tell apart, and why GSTN's own offline matching tool checks seven parameters, not one.
Why a single lookup column can't do this match
Most Excel walkthroughs for GSTR-2B reconciliation teach one formula: VLOOKUP (or XLOOKUP) the invoice number from your purchase register into the 2B export, flag what doesn't come back. It works, right up until it doesn't — and when it fails, it fails silently, returning a "not found" for an invoice that is genuinely sitting in your 2B two rows down, formatted slightly differently, or bundled with a credit note the lookup never accounts for.
GSTN's own Matching Offline Tool — the government's free desktop utility for exactly this comparison — doesn't rely on invoice number alone either. Its user manual defines an Exact Match as agreement across seven parameters together: GSTIN, document type, document number, document date, total taxable value, total tax amount, and tax amount head-wise (IGST/CGST/SGST/CESS). A Partial Match requires GSTIN and document type to agree, with only one of the other five parameters off. A Probable Match is the mirror case — GSTIN or document type is the one that's off, and the other five agree. Unmatched is its own category, not a catch-all: GSTIN, document type, document number and date all agree, but a value — taxable value, tax amount or a tax head — disagrees beyond the tolerance you've set. Two further categories sit outside all of that: In GSTR-2B not in PR and In PR not in GSTR-2B, for records that don't pair with anything on the other side at all. Six categories, not two collapsed into one binary found/not-found on a single field — which is exactly what a one-column VLOOKUP does, and why it flags real matches as mismatches. The four cases below are the ones that trip it up most often, each with the Excel fix.
Hard case 1: the invoice number never matches character-for-character
Your books carry INV-4587. The supplier's GSTR-1 — and therefore your GSTR-2B — carries 4587, or INV/4587, or inv-04587. Same invoice, same amount, same date; a text-equality lookup sees four different strings and returns nothing for three of them. GSTN's own tool hits the identical problem and solves it with what its manual calls "approximation logic … on the document number" — a configurable fuzzy-match step you apply after the exact pass, separate from the tolerance setting it uses for tax amounts (adjustable 0–10 on each tax head, applied to the individual figure, not the consolidated total).
Excel has no built-in approximation toggle, so build the equivalent as a normalised key instead of matching the raw field:
- Add a helper column on both sides:
=UPPER(SUBSTITUTE(SUBSTITUTE(SUBSTITUTE(TRIM(A2),"-",""),"/",""),".",""))— strips hyphens, slashes and full stops, trims whitespace, and forces case, soINV-4587,inv/4587andINV.4587collapse to the same key. - Left-pad or strip leading zeros consistently on both sides (
=IFERROR(TEXT(VALUE(cell),"0"),cell)— theIFERRORfalls back to the original text for keys that keep a letter prefix, likeINV4587, whichVALUE()can't parse) so004587and4587also collapse together — but only after confirming neither side's numbering scheme actually depends on the leading digits (some sequences do). - Match on the normalised column, not the original. Keep the original two columns visible alongside the match result so a reviewer can eyeball what the normalisation actually did before trusting it.
This closes most single-difference cases. Two differences stacked at once — a missing digit and a different separator — will still need a human eye; even a fuzzy-matched document number is only one of the seven parameters GSTN's own tool checks, and a bad match on it can still leave a record in Partial or Probable rather than Exact.
Hard case 2: the same invoice number, from two different vendors
Invoice numbering isn't unique across your whole purchase register — it's only unique per supplier. If Vendor A and Vendor B both happen to issue a 1001, a lookup keyed on invoice number alone will happily return whichever row Excel finds first, silently matching your Vendor A bill against Vendor B's 2B line. The result looks reconciled and is wrong.
The fix: never match on invoice number alone — GSTIN has to be part of the key too, the same way it's one of the seven parameters GSTN's own tool checks rather than being derived from document number. Build a composite key that concatenates the normalised GSTIN and the normalised invoice number from hard case 1 — =A2&"|"&normalised_invoice — and match on that concatenation instead. A duplicate invoice number from two different suppliers now produces two distinct keys, because the GSTIN half differs, and the lookup can no longer cross-match them.
Run a quick sanity check before you trust any composite-key match: COUNTIF the composite-key column against itself in both the purchase register and the 2B export. Any count above 1 on either side needs a look by eye — it can be a genuine duplicate document, or, on the 2B side, the original invoice sitting alongside its own amendment record where the revised invoice number happens to match the original. An amendment that changes the invoice number itself won't share a key with the original at all — that's the next case.
Hard case 3: an amendment can change the very invoice number you're matching on
When a supplier corrects an invoice they already reported in an earlier GSTR-1, the correction doesn't overwrite the original filing — it's entered through GSTR-1's dedicated "9A – Amended B2B Invoice" tile. Per GSTN's own GSTR-1 filing guide, the supplier first looks the original invoice up by its original invoice number, then enters a "Revised Invoice No." and a "Revised Date" — both of which can differ from the original. The corresponding table in your GSTR-2B is named B2BA in GSTN's own portal documentation, and it carries auto-drafted amendments to inward supplies from registered persons — but nothing in that guide says the revised fields are constrained to match the original, so don't build a matching rule that assumes they do.
That means your composite key from hard case 2 is not guaranteed to survive an amendment: if the revision only touched date or value, the GSTIN-plus-invoice-number key still pairs the B2BA row to your register correctly. If the revision touched the invoice number itself, it won't — the amended row's key is now built from a different number than the one in your books. The reliable match point is the original invoice number the supplier looked up to start the amendment, not necessarily the number the B2BA row now carries — and per GSTN's own GSTR-2B FAQ, the B2BA record itself "display[s] revised details with reference to the original document," so where your export carries that original-document reference, build the composite key from it rather than from the revised number. Where it doesn't come through cleanly, match first on your normal composite key, and for anything that lands In GSTR-2B not in PR, check by eye whether it's actually a revised version of an invoice you already matched under its original number before treating it as missing. One more trap in the same FAQ: amendment summary figures show only the differential — "Amended – Original," the delta, not a fresh total — so don't add a B2BA summary line to the corresponding B2B total as if it were a separate invoice; that double-counts the value on both sides.
Hard case 4: in GSTR-2B a credit note isn't keyed to the invoice it corrects — don't try to net it by invoice number
It's tempting to treat a credit note as an edit to the original invoice row and net the two against each other on a shared key. Don't — GSTR-1's credit/debit note table (9B, entered by GSTIN, note number and note date, with its own "Note Type" of Debit or Credit) has no original-invoice field, and Section 34(1) of the CGST Act itself is written for "one or more credit notes for supplies made in a financial year" — plural, and not tied to a single invoice number. The paper credit note itself must still cite the invoice(s) it relates to, under Rule 53(1A)(g) of the CGST Rules, and possibly more than one — but that reference never reaches the 9B/CDNR record, so it can't be your 2B match key. A credit note's own document number will essentially never equal the invoice number it's correcting, so a GSTIN-plus-invoice-number composite key built for hard cases 1–3 will never match a credit note to anything, however you normalise it.
Match credit notes as their own class of document instead: pull them from 2B's CDNR table by GSTIN and note number, against a credit-note column in your own purchase register (most purchase registers already log these separately from invoices — if yours doesn't, that's worth fixing before the reconciliation, not during it). Then net the ITC impact at GSTIN, per period — sum invoice-side taxable value and tax against credit-note-side taxable value and tax for the same supplier in the same month — rather than trying to pair one specific credit note to one specific invoice line. Read the sign off the "Note Type" field on each row rather than assuming your export's sign convention; don't hard-code a positive or negative default.
There's a condition sitting behind the supplier's side of this, too, which is why a credit note can look "stuck": under Section 34(2)'s proviso (substituted by s.126 of the Finance Act 2025, in force 1 October 2025 via Notification 16/2025-CT), a supplier can't reduce its own output tax on a credit note unless you, the registered recipient, have reversed the ITC attributable to it — if you ever availed it in the first place. On the portal, that reversal runs through IMS: per GSTN's FAQ on the changes effective from the October 2025 tax period, accepting a credit note sends it to your GSTR-2B carrying the "Amount of ITC to be reduced" you yourself declare — NIL if you never claimed the original credit or had already reversed it. You can hold a credit note Pending for one further tax period; past that, no action means it's deemed accepted (position as of 30 September 2026). If a credit note you expect isn't showing up as a reduction in your GSTR-2B, check IMS before assuming it's missing — it may simply be sitting Pending.
The gap a monthly snapshot can't show: 2A moves, 2B doesn't — until it does
One more pattern that looks like a reconciliation failure and isn't: a supplier files on the 15th, after your 2B for the period has already drafted. The invoice appears in GSTR-2A almost immediately, because 2A updates continuously as suppliers file — but per GSTN's own GSTR-2B FAQ, a document filed after your 2B for a period has drafted "reflect[s] in the next open Form GSTR-2B of the recipient irrespective of supplier's … date of filing" — it doesn't reach your GSTR-2B until the following period's statement, because 2B is generated per tax period and only draws on what suppliers had filed by its own cut-off. Comparing this month's purchase register against this month's 2B will correctly show the invoice as absent — it hasn't arrived yet — and comparing against 2A instead would show it as present, which is the wrong document to be claiming credit against: under Rule 36(4)(b) of the CGST Rules, read with Section 16(2)(aa) and Rule 60(7), ordinary vendor credit is gated on the invoice being communicated to you in GSTR-2B specifically — 2A plays no role in that condition.
The Excel fix is a running list, not a smarter formula: keep a separate "still open" tab of every invoice your books carry that hasn't yet appeared in any 2B, carried forward month to month rather than re-investigated from zero each period. When an open invoice finally lands in a later 2B, close it out and claim the credit in that period; if it's still open after a couple of cycles, that's the point to go ask the vendor directly rather than keep waiting. Age the list against Section 16(4)'s own deadline, not just your own patience: credit on an invoice is barred once 30 November following the end of that financial year passes (or your annual return is filed, if earlier), so an invoice sitting open into October or November of the following year needs escalating, not another month of waiting. 2A earns its keep here as a diagnostic — checking whether a stuck invoice has at least reached 2A tells you whether the supplier has filed at all, before you pick up the phone.
Video walkthrough by CA Kapil Sachdev — embedded with credit; the guide above is our own.
Where the spreadsheet stops scaling
None of the four fixes above is hard on its own. What's hard is running all four together, every month, against a purchase register that keeps growing — a composite GSTIN-plus-invoice key, a running carryforward tab for what hasn't landed in 2B yet, a separate GSTIN-level net for every credit note, and a manual eyeball pass on every amendment that might have changed the very number you matched on. Recoup's own rule of thumb puts the tipping point at 30–40 vendors, whatever your team's size — the point past which that stack of helper columns and side tabs stops being something one person maintains reliably every close, and starts being the reason month-end slips. That's the point where invoice-by-invoice automated matching earns back the time a spreadsheet was costing.
How Recoup handles the same reconciliation
Recoup connects read-only to your books (Zoho Books or Tally), your bank and the GST portal, and matches invoices across all three — books, IMS and GSTR-2B — invoice by invoice rather than as period totals, without a helper-column sheet to maintain. On each invoice it decides a verdict (matched, mismatch, unfiled or ineligible) and, where something's still open, names the specific vendor behind it instead of leaving you a row number to chase down yourself.
Stop rebuilding the same helper columns every month
Recoup matches your books against GSTR-2B and IMS invoice by invoice, decides a verdict on each line, and names the vendor behind whatever's still open.
Book a demo →Related guides
GST reconciliation: the 2026 guide for finance teams
The invoice-by-invoice match this Excel workflow is one manual way to run.
GSTR-2B
Why this is the statement your ITC actually depends on, not GSTR-2A.
GSTR-2A
The dynamic statement that's useful for tracing a late filer, but not for claiming credit.
Reconciling GSTR-2B in TallyPrime
The same match, run inside Tally's built-in reconciliation report instead of a spreadsheet.