Figuring out how to fix a GST mismatch starts with figuring out which mismatch you actually have, because the term covers at least three different problems that get fixed in completely different ways: numbers that don't match between your own returns, numbers that don't match between the portal's data and your purchase books, and numbers that don't match between what you sold and what you reported.
This guide separates those three, gives you a way to tell a genuine error from a timing difference before you spend hours chasing a non-issue, and works through a fix playbook for each type with a short example.
Identify Which Mismatch You're Actually Looking At
| Mismatch type | Where it shows up | What it usually means |
|---|---|---|
| GSTR-1 vs GSTR-3B | Outward tax liability declared in GSTR-1 doesn't match the summary liability declared in GSTR-3B | A period's sales were reported in one return but not carried through consistently to the other |
| GSTR-2B vs purchase register | Input tax credit auto-populated in GSTR-2B doesn't match what your purchase books expect to claim | A supplier hasn't filed, filed late, or reported your purchase incorrectly on their end |
| Sales register vs GSTR-1 | Your internal books show a different sales figure than what was actually filed in GSTR-1 | Data wasn't fully imported, a transaction was missed, or a duplicate was filed |
Is It a Timing Difference or a Real Error?
Before treating any mismatch as an error to correct, check whether it could simply be a timing gap. An invoice raised on the last day of a month but reported by the buyer's supplier the following month, a credit note issued after the original return was already filed, or a supplier who files their GSTR-1 late relative to when you check your GSTR-2B are all timing differences that typically resolve on their own within a filing cycle or two. Genuine errors, in contrast, persist across periods and involve a value, GSTIN, or classification that is simply wrong and won't self-correct by waiting.
A practical way to tell them apart: pull the same comparison again after the next return cycle closes. If the gap shrinks or disappears, it was timing. If it stays the same or grows, treat it as an error and start the fix process below.
The Fix Playbook for Each Mismatch Type
GSTR-1 vs GSTR-3B mismatch
- Pull the outward supply summary from both returns for the same period side by side.
- Check whether an amendment made in a later GSTR-1 period was reflected in the corresponding GSTR-3B period, since these can drift if amendments aren't tracked centrally.
- If GSTR-3B understated liability relative to GSTR-1, the shortfall generally needs to be paid with applicable interest in a subsequent period; if GSTR-1 understated relative to what was actually supplied, an amendment in a later GSTR-1 is usually the correct route. Confirm the current correction mechanism on www.gst.gov.in since portal-level processes are updated periodically.
GSTR-2B vs purchase register mismatch
- Identify which specific invoices are missing or differ in value between GSTR-2B and your purchase book.
- Contact the supplier directly; a large share of these mismatches trace back to the supplier not having filed their own GSTR-1 for the period yet, rather than any fault in your records.
- Hold input tax credit on disputed invoices until the supplier's filing catches up, rather than claiming credit that GSTR-2B doesn't yet support.
Sales register vs GSTR-1 mismatch
- Re-run your import from source, whether that's marketplace files, bank-linked sales, or direct invoice entry, and compare transaction counts, not just totals.
- Check for a duplicate or missed upload batch, which is the most common cause when totals differ by a round, suspiciously specific amount.
- Reconcile GSTIN-wise if you operate multiple registrations, since a transaction filed under the wrong GSTIN will show as missing in one register and duplicated in another.
A Worked Example
A seller's GSTR-1 for a month showed outward tax liability of Rs. 4,86,000, but GSTR-3B for the same period showed Rs. 4,52,000, a gap of Rs. 34,000. Checking the GSTR-1 amendment table revealed that Rs. 34,000 worth of sales had been added through a late amendment after the original GSTR-3B for that period was already filed. Because the amendment was never carried into a subsequent GSTR-3B, the liability sat unpaid. The fix was straightforward once identified: declare and pay the difference with applicable interest in the following period's GSTR-3B, and set up a monthly check that compares the two returns before either is finalised, not after.
Stopping the Mismatch From Recurring
Most recurring mismatches share a root cause: two systems or two people maintaining the same data independently instead of one source feeding both. Reconciling GSTR-1 and GSTR-3B from the same underlying sales data, checking GSTR-2B against purchases before finalising input tax credit claims each period, and matching bank credits against sales using the bank statement parser all reduce the chance of a fresh mismatch appearing next month. For marketplace sellers specifically, see e-commerce GST reconciliation for a framework that covers sales, returns, TCS, and settlement together.
When a Mismatch Turns Into a Notice
Most mismatches get resolved quietly through amendments and reconciliation before they attract attention, but a mismatch that persists across several periods, especially a large or growing GSTR-1 vs GSTR-3B gap, is exactly the kind of pattern that can trigger a scrutiny notice from the tax department. If you do receive a notice referencing a mismatch, the response is generally stronger when you can show the specific reconciliation working papers that identify the cause, rather than a general explanation. Keep period-wise comparison sheets, not just the final filed numbers, so you can reconstruct exactly which invoices or amendments caused a given period's gap if asked months later.
Don't wait for the notice to start reconciling
Treat GSTR-1 vs GSTR-3B comparison as a pre-filing step, not a post-notice one. Running the comparison before you file GSTR-3B for a period, using the same sales data that fed GSTR-1, catches the majority of these mismatches before they ever reach the department's radar.
Frequently Asked Questions
What's the difference between a GST mismatch and a GST error?
A mismatch is simply two figures not matching; it can result from a timing difference that resolves on its own, or from a genuine error that needs correction. Confirm which one you have before acting.
How do I know if a mismatch is just a timing difference?
Check the same comparison again after the next filing cycle closes. If the gap shrinks or disappears, it was timing. If it persists, treat it as an error.
My GSTR-1 shows more sales than GSTR-3B. What should I do?
This usually means an amendment or late addition to GSTR-1 was not carried into the corresponding GSTR-3B. The shortfall typically needs to be paid with interest in a subsequent period; verify the current process on the GST portal.
Why is a purchase invoice missing from my GSTR-2B?
Most often because your supplier hasn't filed their GSTR-1 yet for that period, or filed it late. Contact the supplier directly rather than assuming your own records are wrong.
Should I claim input tax credit on an invoice not showing in GSTR-2B?
Generally, credit should be held until GSTR-2B reflects the supplier's filing. Rules around this can be specific, so check current guidance on www.gst.gov.in for your situation.
Can OneBooks GST help identify mismatches automatically?
GSTR-1 preparation includes validation warnings, and Admin > Detailed Reports gives a line-item view you can use to compare periods and sources; always cross-check final figures against the GST portal before filing.
How OneBooks GST fits into this
OneBooks GST is a GST and accounting platform for Indian businesses. It keeps source files and reviewed exports together for a return period, so a reconciliation can be repeated months later.
Because OneBooks GST keeps each GSTIN in its own organisation context, a business registered in several states can work through one registration at a time.
