GSTR-1 vs GSTR-3B Mismatch Notices: What Startups & SMEs Must Do Before Responding
Why this article, and why now
In February 2026, the Goods and Services Tax Appellate Tribunal (GSTAT), Principal Bench, delivered its first landmark judgment in M/s Sterling & Wilson Pvt. Ltd. v. Commissioner, Odisha. The Tribunal held that a mere arithmetic mismatch between GSTR-1 and GSTR-3B cannot, by itself, justify proceedings under Section 74 of the CGST Act, 2017. The ruling sits alongside the 2024 Delhi High Court decision in Xiaomi Technology India Pvt. Ltd. v. Additional Commissioner, CGST Delhi West, which laid down the same principle at the High Court level.
For chartered accountants and finance teams advising startups and SMEs, this is significant. Section 74 notices carry a 100% penalty, a five-year limitation window, and the operational stigma of an alleged “fraud, wilful misstatement or suppression of facts” charge. Receiving one is not a minor compliance event. Until the GSTAT ruling, taxpayers had limited appellate clarity on whether the department could route routine reconciliation differences through the harshest penal provision in the statute.
This article walks through the practical anatomy of a GSTR-1/3B mismatch notice — why the differences arise, what the show cause notice typically looks like, how the recent jurisprudence reshapes the response, and how a working CA should structure the reply. It closes with a monthly reconciliation protocol that prevents most mismatches from escalating in the first place.
Why GSTR-1 and GSTR-3B diverge in the first place
The two returns measure different things, despite being routinely treated as a single dataset. GSTR-1 is the outward supplies return — invoice-level data, filed monthly or quarterly depending on turnover. GSTR-3B is the summary return — aggregate output tax and input tax credit consolidated at a tax-period level, with tax actually paid through cash and credit ledgers.
Five recurring causes account for the vast majority of mismatches we see in client portfolios:
1. Timing differences across return periods. An invoice raised on 30 June reported in June’s GSTR-1 may be matched against July’s GSTR-3B if the GSTR-3B was filed without the GSTR-1 figures being correctly synced. This is particularly common where a finance team relies on two different individuals or two different software tools for GSTR-1 and GSTR-3B preparation.
2. Credit notes issued after the Section 34(2) cut-off. Section 34(2) of the CGST Act caps the time within which a credit note can be issued and reflected in returns at 30 November of the following financial year (or the date of filing of the annual return, whichever is earlier). A credit note issued in the books in March but not reported in GSTR-1, because the recipient has already claimed ITC, creates a structural mismatch.
3. Amendment limitations in early GST years. For FY 2017-18 and FY 2018-19, the GST portal did not allow many of the amendment workflows that exist today. Differences that originated in those years still surface as legacy SCNs in 2026 because the department’s analytics layer continues to pull period-wise comparisons.
4. Debit notes and advance adjustments. Where supplies are subject to tax on advance receipt and the supply is subsequently completed or cancelled, the adjustment chronology between GSTR-1 (invoice level) and GSTR-3B (summary level) does not always sync cleanly.
5. E-invoicing and IRN data flow. For taxpayers above the e-invoicing threshold (currently Rs. 5 crore aggregate turnover), invoices flow into GSTR-1 from the IRN portal. A discrepancy between the IRN-generated invoice and the books — for instance, where a correction was made manually in the accounting system but not on the IRN portal — produces a difference the taxpayer may not see until a notice arrives.
In our practice, roughly 60% of mismatch notices traceable to FY 2018-19 to FY 2020-21 originate in causes 2, 3, and 4 — all documented in the books, fully tax-neutral over the financial year as a whole, and never involving any intent to evade tax. That is precisely the scenario the GSTAT addressed.
What the SCN actually looks like
A typical mismatch SCN begins as an ASMT-10 (a scrutiny notice under Section 61) or a DRC-01A (a pre-SCN intimation). Where the department proceeds to formal adjudication, it issues a DRC-01 — the SCN proper — under either Section 73 (non-fraud) or Section 74 (fraud, wilful misstatement, suppression).
The Section 74 version carries three operational consequences:
- A 100% penalty equal to the tax demanded (versus 10% under Section 73).
- A five-year limitation window from the due date of the annual return (versus three years under Section 73).
- An allegation of suppression that has reputational and bank-financing consequences independent of the final tax outcome.
The Sterling & Wilson facts are instructive. The department noticed a difference of Rs. 27,06,634 between GSTR-1 output tax and GSTR-3B output tax for FY 2018-19. It issued a Section 74 notice and raised a demand of over Rs. 65 lakh including tax, interest, and 100% penalty. The First Appellate Authority found that fraud was not established, but instead converted the proceedings to Section 73 and confirmed the demand. The taxpayer carried the matter to the GSTAT.
What the GSTAT held
The Tribunal made three holdings that directly affect how a CA should now draft a reply to a mismatch SCN.
First: Section 74 is a penal provision and must be strictly construed. A mere arithmetic mismatch — without any positive evidence of intent to evade — does not satisfy the threshold of fraud, wilful misstatement, or suppression of facts. The department must demonstrate intent, not merely deduce it from the existence of a difference.
Second: Where the differences arise from credit notes, debit notes, advance adjustments, or timing items that are duly recorded in the books and reflected in GSTR-9 and GSTR-9C, the taxpayer must be given an opportunity to reconcile rather than face summary confirmation of demand.
Third: An appellate authority cannot itself convert proceedings from Section 74 to Section 73 and quantify the liability. The redetermination of tax under Section 73 must be carried out by the Proper Officer under Section 75(2). This procedural point matters: if the FAA in the original adjudication has already taken the Section 74 route off the table, the demand cannot be sustained merely by repackaging it as Section 73 at the appellate stage.
The earlier Delhi High Court ruling in Xiaomi Technology India laid down a similar principle: Section 74 is invocable only where fraud, wilful misstatement, or suppression is alleged with specific particulars, and a bare averment of mismatch does not meet that standard.
Together, these decisions create a practical shield for bona fide taxpayers — but the shield works only if the reply to the SCN is drafted to affirmatively demonstrate the reconciliation, the books position, and the absence of intent.
Drafting the reply: a five-section structure
A reply to a mismatch SCN should be structured around five sections.
Section 1 — Statement of the impugned demand. Set out the period, the figure in dispute, and the legal basis under which the SCN has been issued. Identify whether the department has invoked Section 73 or Section 74 — and if Section 74, what the alleged suppression is. A surprising number of Section 74 notices fail to identify the suppression with any specificity, and this is the first ground of attack.
Section 2 — Reconciliation statement. Prepare a transaction-level reconciliation between GSTR-1 and GSTR-3B for the period. This is the heart of the reply. The reconciliation should show, line by line, the cause of each difference — credit note dated and identifiable, advance adjustment for a specific supply, timing item that reverses in the next return period, and so on. Each item should be cross-referenced to the books, the relevant ledger account, and where possible the entry in GSTR-9 and GSTR-9C.
Section 3 — Legal grounds. Cite Sterling & Wilson Pvt. Ltd. v. Commissioner, Odisha (GSTAT Principal Bench, February 2026) and Xiaomi Technology India Pvt. Ltd. v. Additional Commissioner, CGST Delhi West (Delhi HC, 2024). Argue that on facts, the Section 74 threshold of fraud or wilful misstatement is not met — there is no positive act of suppression, no element of intent to evade tax, and the entirety of the difference is explainable from contemporaneous books and statutory returns.
Section 4 — Tax neutrality analysis. Demonstrate that, over the financial year as a whole, the cumulative output tax declared in GSTR-1 and the cumulative tax paid through GSTR-3B reconcile to the position reflected in the audited books and GSTR-9. Where there is a residual difference, identify it specifically and offer either an explanation or an undisputed admission with payment of tax and interest under Section 73 — expressly denying the 100% penalty.
Section 5 — Prayer. Seek dropping of the SCN to the extent it invokes Section 74. Where some tax is admittedly payable, offer to discharge it under Section 73 with simple interest, without admitting suppression.
A well-prepared reply with a clean reconciliation typically results in either the SCN being dropped or the matter being converted to Section 73 with a 10% penalty cap. The cost differential between a Section 74 confirmation and a Section 73 conversion can easily be 5x to 10x of the underlying tax — which is why the reply is worth the preparation investment.
When Section 74 is legitimately invoked
The GSTAT ruling does not give blanket protection. Section 74 remains the correct provision where the department can demonstrate, with specific evidence, any of the following:
- Suppressed sales not recorded in books at all (cash sales, off-books invoicing).
- Fake ITC claims using invoices from entities with no underlying supply.
- E-way bill manipulation showing inward movement without corresponding ITC reversal.
- Repeated patterns of mismatch with no contemporaneous reconciliation in books or annual returns.
For these fact patterns, the appropriate response is different — typically a voluntary disclosure under Section 74(5) before the SCN is issued, or a settlement strategy that minimises penalty exposure. Conflating the two scenarios is the most common drafting error we see in mismatch replies prepared without specialist input.
The monthly discipline that prevents the notice
The reply strategy above is the cure. The prevention is a monthly reconciliation protocol that runs in parallel with GSTR-3B filing every period. We run this for our SME and startup clients on Zoho Books, but the discipline is software-agnostic.
The protocol has five steps:
1. GSTR-1 vs books reconciliation: match the period’s GSTR-1 invoice register against the sales register in the books, by invoice number. Identify any timing differences and document them in a register that carries forward each month.
2. GSTR-3B vs books reconciliation: match the period’s outward tax in GSTR-3B against the output tax ledger. Reconcile any difference back to specific invoices or credit notes.
3. GSTR-2B vs purchase register reconciliation: match the period’s GSTR-2B against the purchase register, identifying ITC mismatches at the invoice level. Following up with suppliers on un-reflected invoices is much cheaper at month-end than at notice-stage.
4. Credit note tracker: maintain a separate register of all credit notes issued, their dates, and whether they have been picked up in GSTR-1. Any credit note approaching the Section 34(2) deadline needs to be flagged.
5. Period-end reconciliation summary: a one-page summary, signed off by the engagement partner each month, showing the cumulative position year-to-date and the residual differences carried forward.
A taxpayer who maintains this protocol has the reply to any future mismatch SCN already drafted in their working papers. They do not need to scramble to reconstruct an explanation under the 30-day SCN deadline.
Closing note for founders and CFOs
The Sterling & Wilson ruling and the Xiaomi decision do not eliminate the risk of mismatch SCNs — those will continue, given the department’s reliance on analytics-driven scrutiny. What the rulings do is restore the legal proportionality between the offence and the penalty. A bona fide reconciliation difference, contemporaneously documented in books, cannot now be processed as a fraud case without specific evidence.
For founders and CFOs, the practical lesson is simpler than the legal one. Reconcile monthly. Document credit notes the day they are issued. File GSTR-9 and GSTR-9C with the reconciliation built in. If a notice arrives, get specialist representation early — a well-drafted reply at the SCN stage is materially cheaper than an appellate fight, and the reply quality has a direct effect on the outcome.
*******
About the author: CA Sundram Gupta (FCA) is the Founder of Patron Accounting LLP, a chartered accountancy and company secretarial firm with offices in Pune, Mumbai, Delhi, and Gurugram. Patron advises startups and SMEs on GST, income tax, ROC compliance, and audit, with a focus on proactive monthly reconciliation and litigation-grade compliance documentation.
Author Bio
