What is the most common GSTR-2B mismatch?

Invoice number formatting differences are the most common false mismatch. After normalization, tax amount differences and missing portal entries (vendor non-filing) are the most common genuine mismatches.

Should I claim ITC on mismatched invoices?

No. Claim ITC only on fully matched and verified invoices. For tax amount mismatches, claim the lower of book or portal amount until resolved.

How do I handle a ₹1 rounding difference?

Differences of ₹1.00 or less per tax head are typically rounding variances. Most CA firms accept these with documentation of the tolerance policy.

What if a supplier never files the missing invoice?

If the supplier does not file GSTR-1 before the Section 16(4) deadline, the ITC lapses permanently. Document all follow-up attempts.

How long should I wait for a supplier to file?

Start follow-up immediately upon identifying the missing entry. Allow 7–10 business days for the supplier to file. Never wait until the GSTR-3B filing date.

GSTR-2B Mismatch Types: Tax Differences, Missing Invoices, and CDN Handling

GSTR-2B reconciliation rarely produces a clean 100% match. Even well-maintained books typically show 1–5% exceptions — and those exceptions are where ITC is won or lost. For CA firms, understanding every mismatch type and having a resolution playbook for each is the difference between a smooth monthly close and a last-minute scramble before GSTR-3B filing.

This guide breaks down every category of GSTR-2B mismatch, explains why it happens, and gives you a practical resolution workflow. Whether you reconcile in Excel or use ITC reconciliation software, the logic is the same — only the speed changes.

Why GSTR-2B mismatches happen

A mismatch means an invoice exists in one data source (your purchase register or GSTR-2B) but does not cleanly match in the other. Mismatches fall into three broad categories:

Data differences: Same invoice, different values — tax amounts, invoice numbers, or dates do not agree.
Presence differences: Invoice exists in one source but not the other — missing from portal or missing from books.
Compliance differences: Invoice matches but ITC is blocked, pending IMS action, or subject to Rule 37 reversal.

Most CA firms spend 80% of reconciliation time on the remaining 5% of exceptions. The goal is not zero mismatches — it is categorized, documented, and resolved exceptions with a clear ITC impact for each.

Type 1: Invoice number mismatches

The most common false mismatch. Your books record the invoice one way; the supplier filed it differently on GSTR-1.

Common formatting differences

Books: "INV-2024-001" → Portal: "INV/2024/001"
Books: "0001234" → Portal: "1234" (leading zeros)
Books: "PI-456" → Portal: "456" (prefix stripped)
Books: "INV 001" → Portal: "INV001" (spaces)

How to resolve

Before treating an invoice as missing, normalize both sides: strip special characters, remove leading zeros, convert to uppercase. If GSTIN and tax amounts match after normalization, it is the same invoice. Document the normalization rule used. Reconciliation software handles this automatically through multi-tier matching (exact → normalized → fuzzy).

Type 2: Tax amount differences

Invoice appears in both sources with the same number and GSTIN, but CGST, SGST, IGST, or CESS amounts differ. This is a genuine mismatch requiring investigation.

Common causes

Wrong tax rate filed by supplier: Supplier filed 18% GST but invoice was at 12%. Your books have the correct rate; portal has the wrong one.
IGST vs CGST+SGST split: Interstate invoice filed as intrastate (or vice versa). Total tax may match but heads differ.
Partial credit note: Supplier issued a credit note but your books still show the original amount.
Line-item vs header rounding: Tax calculated per line item in books vs per invoice header on portal. Difference is usually under ₹1.00.
Amendment not reflected: Supplier filed an amendment to GSTR-1 but GSTR-2B for the current period still shows the old amount.

Resolution decision tree

Check if the difference is within rounding tolerance (≤ ₹1.00 per tax head)
If larger, pull the original supplier invoice and compare tax calculation
Contact supplier to file amendment if their GSTR-1 is wrong
If your books are wrong, correct the purchase entry before claiming ITC
Claim ITC only on the lower of book amount or portal amount until resolved
Document the mismatch, action taken, and expected resolution timeline

Type 3: Missing from GSTR-2B (vendor non-filing)

Invoice exists in your purchase register but does not appear in GSTR-2B at all. This is the highest-impact mismatch because you cannot claim ITC until the invoice appears on the portal.

Why invoices go missing from GSTR-2B

Supplier has not filed GSTR-1: Most common cause. The supplier recorded the sale in their books but has not filed (or filed late) their GSTR-1 for that period.
Wrong GSTIN on supplier's filing: Supplier filed under a different GSTIN — common for businesses with multiple registrations.
Invoice filed in a different period: Supplier filed the invoice in March instead of February. It will appear in March GSTR-2B, not February.
Invoice rejected in IMS: You or the system rejected the invoice in the Invoice Management System.
Supplier is unregistered or cancelled: GSTIN is inactive on the portal.

Vendor follow-up workflow

For each missing invoice, send the supplier a follow-up with exact details:

Your GSTIN (recipient)
Supplier GSTIN
Invoice number and date
Taxable value and tax amounts (CGST, SGST, IGST)
Return period in which the invoice should appear
Deadline by which you need them to file (before Section 16(4) cutoff)

Log every follow-up with date, recipient, and response. If the supplier does not file in time, the ITC may lapse under Section 16(4). Track these in a carry-forward ledger so you can claim ITC in the period when the invoice finally appears in GSTR-2B.

Type 4: Missing from books (unrecorded purchases)

Invoice appears in GSTR-2B but not in your purchase register. This means either the purchase was not recorded in your accounting system, or it was recorded under a different identifier.

Common causes and actions

Purchase not yet recorded: Goods received but invoice not entered in Tally/ERP. Record the purchase and claim ITC.
Recorded under different invoice number: Accounts team used a different reference. Search books by GSTIN and amount.
Capital vs revenue misclassification: Invoice recorded in fixed assets instead of purchases. Reclassify if appropriate.
Duplicate GSTIN entry: Supplier changed GSTIN; old purchases under previous GSTIN not migrated.

Unrecorded portal entries represent unclaimed ITC. For large amounts, this is a direct revenue leak. Run a monthly check for "missing from books" entries — they are often more valuable than missing-from-portal entries because the ITC is already available on the portal.

Type 5: Credit and debit note (CDN) mismatches

CDNs are the most complex mismatch category. A credit note reduces ITC; a debit note increases it. Both must reference the original invoice.

CDN-specific mismatch patterns

Credit note without original invoice link: Supplier filed CDN but did not reference the original invoice number in GSTR-1. Appears as orphan entry.
Credit note in books but not on portal: Supplier issued credit note physically but has not filed it in GSTR-1.
Partial credit note: Books show full invoice amount; portal shows reduced amount after CDN.
Debit note for price revision: Additional tax liability from supplier. Must be recorded and ITC claimed.

CDN resolution steps

Identify the original invoice the CDN relates to
Verify CDN amount matches the difference between books and portal
If CDN is on portal but not in books, record the credit/debit note entry
If CDN is in books but not on portal, ask supplier to file CDN in GSTR-1
Re-run matching after CDN is properly linked on both sides

Type 6: IMS pending entries

Since the introduction of the Invoice Management System (IMS), some invoices require recipient action before they appear in GSTR-2B. These show up as a separate bucket — not standard missing entries.

IMS pending entries need active monitoring. Log into the GST portal, navigate to IMS, and accept or reject pending invoices. Accepted invoices flow into the next GSTR-2B generation. Rejected invoices will not appear. See our complete IMS guide for detailed workflow.

Mismatch resolution priority matrix

Not all mismatches are equal. Prioritize resolution based on ITC impact and time sensitivity:

Priority	Mismatch type	Action
P1 — Urgent	Missing from 2B, high value, near 16(4) deadline	Immediate vendor follow-up, escalate if no response
P2 — High	Tax amount mismatch, large variance	Pull original invoice, contact supplier for amendment
P3 — Medium	IMS pending, missing from books	Accept/reject in IMS; record unbooked purchases
P4 — Low	Rounding difference ≤ ₹1.00, formatting mismatch	Accept with normalization; document tolerance used
P5 — Blocked	Ineligible ITC under Section 17(5)	Exclude from GSTR-3B Table 4; no action needed

How Complytics handles mismatches

Complytics categorizes every exception automatically and gives your team the tools to resolve them efficiently:

Multi-tier matching catches formatting differences before flagging as missing
Tax head-level comparison (CGST, SGST, IGST, CESS) pinpoints exact variance
CDN auto-linking to original invoices reduces orphan entries
Vendor follow-up email drafts with exact invoice details via Vedora AI
Priority sorting by ITC value and Section 16(4) deadline proximity
Immutable audit trail of every accept, reject, and manual adjustment

Your team reviews exceptions only — not thousands of matched rows. The CA makes every final ITC decision; Complytics provides the categorization and documentation.

Frequently asked questions

What is the most common GSTR-2B mismatch?: Invoice number formatting differences are the most common false mismatch — the same invoice recorded differently in books vs portal. After normalization, tax amount differences and missing portal entries (vendor non-filing) are the most common genuine mismatches.
Should I claim ITC on mismatched invoices?: No. Claim ITC only on fully matched and verified invoices. For tax amount mismatches, claim the lower of book or portal amount until resolved. For missing portal entries, you cannot claim ITC until the invoice appears in GSTR-2B.
How do I handle a ₹1 rounding difference?: Differences of ₹1.00 or less per tax head are typically rounding variances from line-item vs header calculation. Most CA firms accept these with documentation of the tolerance policy. Set your tolerance in reconciliation software and bulk-approve rounding matches.
What if a supplier never files the missing invoice?: If the supplier does not file GSTR-1 before the Section 16(4) deadline, the ITC lapses permanently. Document all follow-up attempts. You may have a contractual claim against the supplier for the GST amount, but you cannot claim it as ITC.
How long should I wait for a supplier to file?: Start follow-up immediately upon identifying the missing entry. Allow 7–10 business days for the supplier to file. If unresolved by day 18 of the month, escalate. Never wait until the GSTR-3B filing date — by then it is often too late for the supplier to file in the correct period.

Ready to automate reconciliation across your client portfolio?

Start free trial Explore ITC reconciliation