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.
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.
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.
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 show | GSTR-2B shows | Why matching fails | Fix |
|---|---|---|---|
| INV-001 | INV/001 | Different separator | Remove hyphens, slashes and spaces |
| KT/184 | KT/00184 | Leading zeros | Strip leading zeros from the number part |
| 184/26-27 | 184 | Year suffix added by supplier or clerk | Remove the year suffix |
| ₹1,18,000.40 | ₹1,18,000 | Rounding | Allow a ₹1 to ₹2 tolerance |
| ₹1,18,000 total | ₹1,00,000 taxable, ₹18,000 tax | Total vs taxable value | Compare taxable to taxable, tax to tax |
| 31 March | 1 April | Date entered differently | Check dates separately; they change the financial year |
| 27AABCK1234M1Z5 | 27AABCK1234M1Z6 | GSTIN typo in vendor master | Correct 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?
- Supplier GSTIN. The portal validates it, so it is the most reliable key.
- Cleaned invoice number. After removing separators, spaces, leading zeros and year suffixes.
- Taxable value and tax amount. Within a small tolerance.
- 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:
- Number rule: strip the slash and leading zeros. KT/184 becomes KT184. KT/00184 becomes KT184. Match.
- 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.
What to read next
- Next in this series: Why does the same invoice appear twice in my GSTR-2B?
- Setting tolerances well: tolerance matching in reconciliation
- The full monthly match: three-way ITC reconciliation in Excel
- Matching at volume: GST reconciliation software
Inward GST matching (GSTR-2A, GSTR-2B, ITC and IMS) is on the TransactIG roadmap.