Tally GSTR-2B reconciliation not matching? 7 fixes that solve 95% of cases

If Tally's GSTR-2B reconciliation is throwing mismatches you know are wrong, the cause is almost never the tax data — it's how the two sides wrote the same invoice differently.

You imported the 2B JSON, ran reconciliation, and half your genuine purchases show red. Before you re-enter anything, walk this list — it's ordered by how often each one is the culprit.

Fix 1: Invoice number format (the #1 cause)

Your voucher says 001; the supplier's GSTR-1 says INV-001; Tally sees two different invoices. Prefixes, slashes, leading zeros, financial-year suffixes (247/25-26) — any difference breaks exact matching.

Fix: enter purchase vouchers with the invoice number exactly as printed on the supplier's bill. For existing mismatches, correct the voucher's supplier invoice number field, not the bill.

Fix 2: Wrong date field

The 2B carries the supplier's invoice date. If your voucher was entered with the receipt/voucher date in the supplier-invoice-date field, dates disagree and matching fails.

Fix: in the purchase voucher, keep voucher date (your books) and supplier invoice number/date (their bill) as separate fields — Tally provides both; use both.

Fix 3: Rounding differences of ₹1–2

Suppliers who compute tax line-wise and you who compute it invoice-wise will disagree by paise, which rounds into ₹1 differences that strict matching flags.

Fix: treat differences up to ₹2 as matched; claim per the 2B figure. Chasing paise costs more than it saves.

Fix 4: GSTIN typo in your supplier ledger

One transposed character in the supplier master and every invoice from that supplier looks unmatched — the 2B entries sit under the correct GSTIN with nothing on your side to pair with.

Fix: validate every supplier master GSTIN once (checksum catches typos — free checker), then lock the masters.

Fix 5: The supplier reported it B2C

If the supplier billed without your GSTIN, the invoice went into GSTR-1's B2C section — it will never appear in your 2B, however long you wait. In Tally it shows as "not in 2B" forever.

Fix: supplier amends B2C→B2B with your GSTIN in the next GSTR-1. Prevention: GSTIN printed on every bill at purchase time. (Full diagnosis: why ITC isn't showing in 2B.)

Fix 6: Period mismatch — it's in next month's 2B

The supplier filed after the 13th cutoff, so your June invoice sits in the July 2B while you reconcile June. Not lost — just late.

Fix: reconcile each new 2B against all open invoices, not just the current month's purchases. Keep an "awaiting 2B" bucket that rolls forward. (And remind suppliers before the 11th so this stops happening.)

Fix 7: Duplicate or split vouchers on your side

The same bill entered twice (once from the delivery copy, once from the file copy), or one invoice split across two vouchers, leaves an orphan that matches nothing.

Fix: search the supplier + amount for duplicates before assuming the 2B is wrong; merge split vouchers to mirror the invoice.

When it's genuinely not you

Everything clean and the invoice still isn't there? Then it's the supplier — not filed, filed wrong, or worse. That's not a Tally fix; that's the supplier escalation playbook.

The part Tally can't do

Tally can match what you imported — it can't fetch 2B itself, label why each invoice is missing, or WhatsApp the supplier. GST Sathe does exactly that loop monthly (fuzzy matching included, so INV-001 vs 001 never bothers you again) and hands your CA the reconciled bundle. Tally stays your books; GST Sathe becomes the reconciliation layer on top.

Sources

• Rule 60 (GSTR-2B), Rule 59 (GSTR-1 B2B/B2C tables), CGST Rules
• GSTN GSTR-2B JSON schema documentation