An ITC mismatch shows up the moment you line up your purchase register against GSTR-2B and the numbers refuse to agree. Sometimes it is a small rounding difference; sometimes an entire invoice is missing because a vendor forgot to file. Either way, chasing down the gap is unavoidable if you want to claim the credit you are actually entitled to without risking a reversal later. This is a practical, step-by-step process for working through mismatches methodically instead of re-checking the same spreadsheet five times.
Why Mismatches Happen
Before fixing anything, it helps to know the usual culprits:
- Supplier has not filed their GSTR-1 for the period yet, or filed it after the GSTR-2B cut-off
- Supplier entered your GSTIN incorrectly, so the invoice lands against a different taxpayer
- Invoice value, tax amount, or invoice number was typed differently on their side vs. your books
- You recorded a purchase in one month, but the supplier reported it in an adjoining month
- Duplicate entries on either side
- A genuine invoice was simply never uploaded by the supplier
Step 1: Get Both Sides of the Data in One Place
Download your GSTR-2B for the period from the GST portal (in Excel or JSON), and export your purchase register from your accounting records for the same period. Both need to be at the invoice level — supplier GSTIN, invoice number, invoice date, taxable value, and tax amount — not just monthly totals, since totals can match by coincidence while individual invoices are wrong.
Step 2: Match Line by Line
Sort both lists by supplier GSTIN and invoice number, then match each entry. Every invoice will fall into one of four buckets:
| Bucket | Description | Typical action |
|---|---|---|
| Fully matched | Same GSTIN, invoice number, value, and tax on both sides | No action — claim as-is |
| Value mismatch | Invoice exists on both sides but taxable value or tax amount differs | Verify the correct figure and follow up with the supplier if their filing is wrong |
| In books, not in GSTR-2B | You have the invoice, supplier has not reported it (or reported it late) | Do not claim yet; follow up with supplier to file or amend |
| In GSTR-2B, not in books | Supplier reported an invoice you have no record of | Check for a missed purchase entry, or flag as an incorrect GSTIN entry by the supplier |
Step 3: Categorize by Likely Cause, Not Just Symptom
Once you have a list of mismatches, it is worth spending a few minutes tagging why each one likely happened — late filing, wrong GSTIN, timing difference, duplicate, or genuine omission. This matters because the fix is different in each case: a timing difference usually resolves itself next month with no action needed, while a wrong-GSTIN entry needs an amendment from the supplier before it will ever show correctly.
Step 4: Follow Up With Vendors, With a Clear Ask
Vague reminders ("please check your GST filing") rarely move fast. A more effective follow-up names the exact invoice number, date, and amount, and states clearly what you need — file the missing invoice, correct the GSTIN, or amend the value — and by when, ideally before the next GSTR-2B cut-off so the correction reflects promptly. Keeping a simple tracker of open follow-ups (vendor, invoice, issue, date raised, status) prevents the same gap from being chased twice or forgotten entirely.
Step 5: Decide What to Claim This Month
As a general rule, claim ITC to the extent it appears correctly in GSTR-2B for the period. For invoices genuinely in your books but missing from GSTR-2B, hold off claiming until they appear in a later GSTR-2B, rather than claiming provisionally — provisional claim treatment has changed over recent years, so check current guidance on the GST portal or with your GST advisor before assuming any credit outside GSTR-2B is claimable.
Worked Example
Your purchase register shows an invoice from Vendor A dated 12th June for ₹85,000 plus ₹15,300 GST. In GSTR-2B for June, the same invoice appears but with a taxable value of ₹80,000 and tax of ₹14,400 — a ₹4,900 difference. On checking, you find the vendor issued the invoice at ₹85,000 but under-reported the value in their GSTR-1. You claim ITC only to the extent reflected in GSTR-2B (₹14,400) for June, flag the ₹900 tax gap to the vendor for correction, and track it until it is amended and shows up correctly in a later period.
Step 6: Document Everything
Keep a record of every mismatch you identified, the follow-up sent, and how it was eventually resolved. This is useful not just for your own monthly close but also if a GST officer later questions why a particular month's ITC claim was lower than the purchase register suggests — you can show it was a deliberate, documented decision rather than an oversight.
Assigning Ownership So Follow-Ups Do Not Fall Through
In many small accounting teams, ITC mismatch resolution has no single owner — the person preparing GSTR-3B notices the gap, sends one email, and then moves on to the filing deadline without a way to track whether the vendor actually responded. It helps to name one person as the owner of the mismatch tracker each month, even if the team is small, and to review open items at a fixed point in the cycle (for instance, a week before the GSTR-3B due date) rather than only when someone happens to remember. Over a few months, this also builds a useful picture of which vendors are consistently late or careless with their filings, which is worth factoring into vendor selection or payment terms going forward.
Making This a Repeatable Monthly Habit
ITC mismatch work is far less painful when it is done on a fixed monthly schedule rather than in a scramble before the GSTR-3B due date. Many teams pair this with a broader reconciliation routine covering GSTR-2A vs GSTR-2B differences and ITC reversal checks in the same sitting, since they draw on the same purchase data. On the outward-supply side, filing your own GSTR-1 accurately and on time reduces the number of mismatches your buyers have to chase you for — OneBooks GST's GSTR-1 automation includes validation warnings that catch common data issues before you file. If your reconciliation routine also involves confirming which invoices were actually paid, the bank statement parser can help match payments against your purchase register without manual line-by-line checking. For anything you cannot resolve on your own, our support team can help point you in the right direction.
Frequently asked questions
Should I claim ITC based on my purchase register if GSTR-2B is incomplete?
Generally, credit is expected to be claimed to the extent it reflects in GSTR-2B for the period. If an invoice is missing from GSTR-2B, the safer approach is to follow up with the supplier and claim once it appears, rather than claiming ahead of the statement.
How often should I run ITC reconciliation?
Monthly, ideally right after GSTR-2B is generated and before you finalize GSTR-3B for that period, so any follow-up with vendors has time to happen before the next cycle.
What if a vendor refuses to correct a mismatched invoice?
Keep written records of your follow-up attempts. If a correction genuinely will not happen, you may need to treat that portion of credit as not claimable and consult a GST professional on how to handle it in your books and returns.
Can small rounding differences be ignored?
Minor rounding differences arising from decimal handling are common and usually not worth chasing individually, but it is worth setting an internal threshold and being consistent about applying it, rather than deciding case by case.
Does ITC mismatch affect my GST return filing deadline?
No, mismatch resolution does not extend your filing deadline. It is a parallel workstream you run against your own timeline so that, by the time you file, your claimed ITC is as accurate as possible.
Using OneBooks GST for this workflow
This is where tooling earns its place: OneBooks GST parses bank statements into ledger-mapped rows and imports sales data, so both sides of an ITC comparison have evidence behind them.
OneBooks GST keeps source data, reviewed output and exports as separate records, so a figure can be traced back rather than reconstructed.
