Skip to main content
Symptom · 6 min read

Why Won't My Invoices Match Between My Purchase Register and GSTR-2B?

Two records of the same supplier invoice often fail to match because the invoice number is written differently, the date or year differs, the GSTIN has a typo, or the amounts differ by a rupee of rounding. A few clean-up rules and a sensible match order fix most cases.

Terra Insight
Terra Insight Editorial Team Reconciliation Infrastructure

Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →

Published 14 October 2026
Domain expertise
TDS Reconciliation GST Input Credit Platform Settlements NACH Batch Matching Bank Reconciliation Form 26AS Matching ERP Integrations Enterprise Finance Ops
Knowledge Card
Problem

Supplier invoices that clearly refer to the same purchase do not match between the purchase register and GSTR-2B, leaving a long unmatched list every month.

How It's Resolved

Exact matching fails on formatting differences in invoice numbers, date and year differences, GSTIN typos, small rounding gaps and tax-inclusive amounts. Cleaning fields and matching in a fixed order resolves most of them.

Configuration

Clean invoice numbers by removing spaces, hyphens, slashes and leading zeros; match on GSTIN, cleaned number, taxable value and tax within a ₹1 to ₹2 tolerance; review date differences separately.

Output

A short unmatched list containing only real gaps, such as missing or duplicate invoices, instead of formatting noise.

Invoices that look identical to you still fail to match because a computer compares them character by character. Different invoice number formats (INV-001, INV/001, 1), date or year differences, GSTIN typos, a rupee of rounding, and amounts that include or exclude tax are the usual reasons. A few clean-up rules fix most of them.

What are the likely causes?

Books showGSTR-2B showsWhy matching failsFix
INV-001INV/001Different separatorRemove hyphens, slashes and spaces
KT/184KT/00184Leading zerosStrip leading zeros from the number part
184/26-27184Year suffix added by supplier or clerkRemove the year suffix
₹1,18,000.40₹1,18,000RoundingAllow a ₹1 to ₹2 tolerance
₹1,18,000 total₹1,00,000 taxable, ₹18,000 taxTotal vs taxable valueCompare taxable to taxable, tax to tax
31 March1 AprilDate entered differentlyCheck dates separately; they change the financial year
27AABCK1234M1Z527AABCK1234M1Z6GSTIN typo in vendor masterCorrect the vendor master

A GSTIN has 15 characters. One wrong character means a different taxpayer, so fix the vendor master rather than forcing a match.

Which fields should matching use, and in what order?

  1. Supplier GSTIN. The portal validates it, so it is the most reliable key.
  2. Cleaned invoice number. After removing separators, spaces, leading zeros and year suffixes.
  3. Taxable value and tax amount. Within a small tolerance.
  4. Invoice date. Used to confirm, and to catch period and year problems.

Under Rule 46 of the CGST Rules, 2017, a supplier’s invoice number can be up to 16 characters and must be unique for the financial year. That is why the same number can legitimately repeat in a new year, and why the date matters as a final check.

How much rounding difference can safely be ignored?

A rupee or two per invoice is normal. Suppliers often round tax to the nearest rupee while your system keeps paise. Set a small tolerance on tax amount, say ₹1 or ₹2. Do not set it wide. A ₹100 tolerance on a ₹1,000 tax line is 10 percent and would hide real errors.

Worked example

The books show invoice KT/184 from a Surat supplier for ₹1,18,000.40, posted as a total. GSTR-2B shows KT/00184 with taxable value ₹1,00,000 and IGST at 18 percent of ₹18,000.

Two clean-up rules make the pair match:

  1. Number rule: strip the slash and leading zeros. KT/184 becomes KT184. KT/00184 becomes KT184. Match.
  2. Amount rule: split the books total into taxable ₹1,00,000.34 and tax ₹18,000.06, then allow ₹1 tolerance. Taxable ₹1,00,000.34 against ₹1,00,000 is a 34 paise gap; tax ₹18,000.06 against ₹18,000 is a 6 paise gap. Both are inside ₹1. Match.

Check: ₹1,00,000.34 + ₹18,000.06 = ₹1,18,000.40. The ₹18,000 credit can now be claimed with confidence.

Inward GST matching (GSTR-2A, GSTR-2B, ITC and IMS) is on the TransactIG roadmap.

Terra Insight
Terra Insight Editorial Team Reconciliation Infrastructure

Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →

Published Invalid Date
Domain expertise
TDS Reconciliation GST Input Credit Platform Settlements NACH Batch Matching Bank Reconciliation Form 26AS Matching ERP Integrations Enterprise Finance Ops
Primary reference: CBIC GST — which publishes Rule 46 of the CGST Rules, 2017, setting the fields every tax invoice must carry, including a serial number of up to 16 characters..

Frequently Asked Questions

Why does INV-001 not match INV/001?
A spreadsheet or matching tool compares text exactly. A hyphen, slash, space or leading zero makes two numbers look different to the computer. Remove those before matching.
Which fields should I match on?
Supplier GSTIN first, then cleaned invoice number, then taxable value and tax amount, then invoice date. GSTIN is the most reliable field because the portal validates it.
How much rounding difference can I ignore?
A rupee or two per invoice is normal from rounding. Set a small tolerance, such as ₹1 or ₹2 on tax amount, and review anything larger.
My register shows the amount including GST. Is that a problem?
Yes. GSTR-2B shows taxable value and tax separately. Compare taxable value to taxable value and tax to tax, not a total against a taxable value.
Can a wrong invoice date stop a match?
Yes, especially near month end or year end. A date of 31 March in one record and 1 April in the other puts the invoice in different periods and even different financial years.

See how TransactIG handles reconciliation for your industry

Configuration takes 2–4 weeks. No code development required. ISO 27001:2022 certified.