GSTR-1 vs GSTR-3B Mismatch: How to Fix It
GSTR-1 and GSTR-3B don't match? Here's why it happens, how to reconcile them, and a notice-reply template if you've already been flagged.
Words by
Nimisha Chanda
A GST mismatch notice starts with an automated flag when the number you declared in GSTR-1 doesn't match what you paid in GSTR-3B. That gap can suspend a GSTIN, block your next return filing, and hand your customers a reason to hold back payment until you sort it out. Most finance teams treat this as bookkeeping noise. It isn't. Here's why the mismatch happens, how to reconcile it, and exactly what to file if a notice has already landed.
Why GSTR-1 and GSTR-3B Don’t Match
GSTR-1 and GSTR-3B report the same underlying sales, but they report it differently and that is the biggest mismatch.
GSTR-1 is invoice-level. Every outward supply - B2B, B2C large, B2C small, exports, credit and debit notes, amendments to prior periods. GSTR-3B is summary-level. One consolidated tax liability number, filed monthly, used to actually pay the tax.
Here are four causes that account for most of what shows up as a mismatch.
Wrong Reporting. An invoice reported correctly in GSTR-1 gets clubbed under the wrong head in GSTR-3B’s Table 3.1, most commonly B2B supplies reported as B2C or vice versa. The total tax can be identical and the system still flags a mismatch, because it’s comparing table-wise.
Amendments without a matching payment. GSTR-1 lets you amend an invoice from an earlier period in the current month’s filing. If the tax on that amendment isn’t reflected in the same month’s GSTR-3B, the two returns diverge for that period even though nothing is actually wrong.
Timing gaps. An invoice dated in one month sometimes gets its tax paid in the next month’s GSTR-3B, particularly around month-end. GSTR-1 reflects the invoice date; GSTR-3B reflects when the return was actually filed. Over a single period, that’s a mismatch. Over a quarter, it usually nets out.
Credit and debit notes. A credit note reduces taxable turnover in GSTR-1 for that period. If the corresponding reduction isn’t carried through to GSTR-3B in the same period, the outward supply value no longer lines up.
None of these mean fraud. Most are reporting-period mechanics. But the GST system doesn’t distinguish intent from error, it just compares two numbers and flags the gap.
What a Mismatch Actually Puts at Risk
Three things happen once the gap crosses the system’s threshold.
GSTIN suspension. Since reconciliation between GSTR-1 and GSTR-3B became a compliance trigger, sustained divergence between the two returns is grounds for suspending the registration itself and not just flagging it.
ITC denial. Your customer’s ITC claim traces back to what you reported in GSTR-1. If your GSTR-3B tax payment doesn’t support that liability, the mismatch becomes their problem too, and it shows up as a blocked or reversed credit on their side, not yours.
Compounding across periods. An unresolved mismatch in one month doesn’t reset the next month. It carries forward as an open item, and repeated intimations on the same taxpayer read very differently to a scrutiny officer than a single isolated gap.
The operational fix and the notice-response are two different problems. Fixing the reconciliation prevents the next one. Responding to a notice you’ve already received requires a different, faster process, covered below.
How to Reconcile GSTR-1 Against GSTR-3B
Reconciliation means comparing outward supply value in GSTR-1 against taxable value in GSTR-3B, table by table.
Build the comparison across at least three categories: B2B, B2C large/small, and exports, including any zero-rated supplies under LUT, which get flagged disproportionately often because gross platform-reported turnover doesn’t distinguish taxable from zero-rated. Pull the GSTR-1 summary for the period, pull GSTR-3B Table 3.1, and lay them side by side.
Here’s a worked example for a single tax period.
Category | GSTR-1 Outward Supply Value (₹) | GSTR-3B Taxable Value (₹) | Variance (₹) | Likely Cause |
|---|---|---|---|---|
B2B | 84,20,000 | 81,60,000 | 2,60,000 | Two invoices amended in GSTR-1 for the prior period; tax not yet reflected in this month’s GSTR-3B |
B2C Large | 12,40,000 | 12,40,000 | 0 | - |
B2C Small | 6,15,000 | 5,70,000 | 45,000 | Credit note issued mid-month, reduced GSTR-1 turnover but not carried into GSTR-3B Table 3.1 |
Exports (LUT) | 18,90,000 | 22,00,000 | (3,10,000) | Export turnover reported gross in GSTR-3B, without netting the LUT zero-rating correctly |
Total | 1,21,65,000 | 1,21,70,000 | (5,000) | Net variance is small, but table-wise gaps would each independently trigger scrutiny |
Note the total variance here is negligible, five thousand rupees against a base of over a crore. On an aggregate basis, this return looks clean. Table-wise, it isn’t: three of the four categories carry a gap, and each one is a plausible independent trigger for an automated intimation, because the system compares category-level data, not just the total.
Once you’ve isolated the variance, trace each line back to its source. An amendment traces to the GSTR-1 amendment table for that invoice. A credit note traces to the note number and the period it was issued in. A classification error traces to which head the invoice was originally booked under. Write down the cause against each variance line before you touch a filing correction, because that same reconciliation sheet becomes your evidence if a notice does arrive.
If You’ve Already Received a Mismatch Notice
The GSTR-1 vs GSTR-3B mismatch reaches you in one of two ways, and they are not the same process.
Form DRC-01B, under Rule 88C. This is the one you’ll see first for a straightforward liability mismatch. It’s system-generated: the portal compares your GSTR-1 tax payable against your GSTR-3B tax paid for the period, and if the gap crosses a prescribed threshold, Part A of DRC-01B is issued automatically to your portal dashboard and registered email. You get seven days. In that window you either pay the differential through Form DRC-03 and record it in Part B, or file an explanation in Part B without payment. Miss the window, or file an explanation the officer doesn’t accept, and your next GSTR-1 or IFF filing gets blocked under Rule 59(6), with recovery proceedings under Section 79 following.
Form ASMT-10, under Section 61. This is broader officer-led scrutiny and not limited to the GSTR-1/3B liability gap; it can cover ITC mismatches against GSTR-2B, HSN errors, or unreported turnover alongside it. You get thirty days to respond, via Form ASMT-11. If the officer accepts your reconciliation, scrutiny closes in Form ASMT-12. If not, it escalates toward a Section 73 or 74 show-cause notice.
Seven days is not much runway if you’re reconciling from scratch after the fact, which is the actual reason this notice type catches finance teams off guard. Start with the same table-wise reconciliation sheet from the previous section, isolate each variance line, and attach the supporting document for each: the amended invoice, the credit note, the export documentation under LUT. Vague, unreconciled statements, “timing difference, will correct next period,” without a line-by-line breakdown, are the most common reasons an explanation gets rejected.
Here’s a reply template for Part B of DRC-01B, adaptable to an ASMT-11 reply by swapping the header references.
Reference: [DRC-01B reference number / ASMT-10 notice number]
GSTIN: [your GSTIN]
Tax period: [period covered by the intimation]
We refer to the intimation dated [date] regarding a difference of ₹[amount] between the tax liability declared in GSTR-1/IFF and the tax paid in GSTR-3B for the above period.
On reconciliation, the variance is explained as follows:
- [Category, e.g. B2B]: ₹[amount] - [cause, e.g. Invoices [invoice numbers] amended in GSTR-1 for [prior period]; tax liability for the amendment reflected in GSTR-3B for [period], not the period under intimation. Amendment and corresponding GSTR-3B payment attached as Annexure A.]
- [Category]: ₹[amount] - [cause]. [Supporting document reference.]
[If any part of the variance represents genuine short payment:] An amount of ₹[amount] has been paid vide Form DRC-03, ARN [ARN number], dated [date], along with applicable interest under Section 50.
The remaining variance of ₹[amount] does not represent additional tax liability for the reasons stated above. We request the intimation be closed accordingly, or scrutiny dropped under Form ASMT-12 as applicable.
Attachments: reconciliation statement, invoice-wise variance schedule, amendment records, credit/debit note copies, Form DRC-03 payment proof (where applicable).
Adapt every bracket before filing. The reconciliation table from the previous section is what Annexure A should look like in practice: category, GSTR-1 value, GSTR-3B value, variance, cause, each row traceable to a document.
Can You File GSTR-1 Without Filing GSTR-3B First?
No. Under Rule 59(6), the portal blocks GSTR-1 or IFF filing for the current period if GSTR-3B for the prior period is outstanding. This isn’t specific to mismatch cases, it applies universally, and it’s the practical reason mismatches compound is when a business that falls behind on GSTR-3B can’t simply keep filing clean GSTR-1s to stay current with customers waiting on ITC.
The sequencing implication matters more than the rule itself. Filing GSTR-1 first, ahead of GSTR-3B, is standard practice precisely because it populates your buyers’ GSTR-2B and lets them claim ITC on schedule. But GSTR-1 alone doesn’t discharge your tax liability, and if GSTR-3B for that same or an earlier period slips, the block cuts off your ability to file GSTR-1 too, stalling your customers’ credit chain along with your own filing status.
Preventing This at Scale
Reconciliation between GSTR-1 and GSTR-3B is a manageable, five-minute check at low invoice volume. Above a few hundred invoices a month, table-wise reconciliation across B2B, B2C, exports, and every amendment and credit note stops being something a finance team can eyeball at month-end.
The failure pattern is consistent. Reconciliation happens after both returns are filed, because building the comparison sheet by hand takes longer than the filing deadline allows. By the time the gap surfaces, it’s already a DRC-01B intimation with a seven-day clock attached.
The fix isn’t more headcount on reconciliation, it’s matching the two returns before either one is filed. That means the same category-wise, invoice-level comparison covered above, run automatically against every GSTR-1 entry before the corresponding GSTR-3B is submitted, so a table-wise gap surfaces as a pre-filing exception rather than a post-filing notice. For a finance team managing GST compliance alongside accounts payable and vendor reconciliation, that’s the same 3-way match discipline applied one step earlier in the return cycle.
Nova builds this matching into the reconciliation layer for finance teams handling GST compliance at volume, so table-wise gaps surface as an exception queue before filing rather than a notice afterward.
If your finance team is still reconciling GSTR-1 against GSTR-3B by hand each month, the notice you’re trying to avoid is usually already three periods behind.
