Handling GSTR-1 vs GSTR-3B Mismatch Notices: A Practical Playbook for Startups & SMEs

Why GSTR-1 / GSTR-3B Mismatch Notices Need Careful Handling

In February 2026, the Goods and Services Tax Appellate Tribunal (GSTAT), Principal Bench, in M/s Sterling & Wilson Pvt. Ltd. v. Commissioner, Odisha delivered a significant ruling for GST litigation. The Tribunal held that a mere numerical difference between GSTR-1 and GSTR-3B cannot, on its own, justify invoking Section 74 of the CGST Act, 2017.

This view is consistent with the earlier 2024 decision of the Delhi High Court in Xiaomi Technology India Pvt. Ltd. v. Additional Commissioner, CGST Delhi West, which had already emphasised that Section 74 demands a higher threshold of proof — namely, fraud, wilful misstatement or suppression of facts.

For startups, SMEs and their CAs, this has very real implications. A notice under Section 74 is not just another GST communication. It carries:

  • A 100% penalty equal to the tax demand
  • An extended limitation period of five years
  • A serious allegation of “fraud, wilful misstatement or suppression of facts”

The combination of monetary risk and reputational impact makes these notices especially sensitive. Before the GSTAT pronouncement, there was limited appellate clarity on whether the department could treat routine GSTR-1 / GSTR-3B reconciliation gaps as grounds for the harsh regime of Section 74.

This article explains:

  • How and why GSTR-1 and GSTR-3B often diverge
  • What a typical mismatch show cause notice (SCN) contains
  • How the decisions in M/s Sterling & Wilson Pvt. Ltd. v. Commissioner, Odisha and Xiaomi Technology India Pvt. Ltd. v. Additional Commissioner, CGST Delhi West shape your legal position
  • How a CA can systematically structure an effective reply
  • A preventive monthly reconciliation framework that sharply reduces the risk of adverse notices

Understanding Why GSTR-1 and GSTR-3B Don’t Always Match

Although both GSTR-1 and GSTR-3B relate to output tax, they are conceptually different returns and are often prepared using different datasets, tools or teams.

  • GSTR-1: Statement of outward supplies, invoice-wise
  • GSTR-3B: Summary return, showing consolidated tax liability and ITC utilisation for the tax period

In actual practice, the following situations repeatedly cause mismatches:

1. Period-wise Timing Differences

Consider an assessee issuing an invoice on 30 June.

  • The invoice is reported in June’s GSTR-1
  • But if July’s GSTR-3B is prepared independently and includes this tax, while June’s GSTR-3B does not, a mismatch will appear in the system

This pattern frequently arises where:

  • One person handles GSTR-1 and another handles GSTR-3B, or
  • Two different software environments are used, and data is not synced in real time

2. Credit Notes Beyond the Section 34(2) Deadline

Section 34(2) of the CGST Act, 2017 restricts the time for reporting credit notes in returns to 30 November of the following financial year (or the date of filing the annual return, whichever is earlier).

A common situation:

  • A credit note is booked in the accounts in March
  • However, the supplier does not reflect it in GSTR-1 because the recipient has already availed ITC and will not reverse it

This leads to a permanent structural variance between the books and the GSTR-1 / GSTR-3B trail, although the underlying transaction is fully documented and visible in financial statements.

3. Legacy Portal Limitations in Early GST Years

For FY 2017-18 and FY 2018-19, the GSTN portal had limited amendment functionalities. Certain corrections that are routine today simply could not be implemented then.

Even in 2026, many mismatch notices can be traced back to those early years, because:

  • The department’s data analytics continues to compare GSTR-1 and GSTR-3B period-wise
  • Historical constraints in amendment workflows often appear as “unreconciled differences” long after the underlying issues have been fully neutralised over the year

4. Debit Notes and Treatment of Advances

Where GST is paid on advances and later adjusted when the actual supply is made or cancelled, the following may occur:

  • The manner in which advances and subsequent invoices are mapped in GSTR-1 (invoice-level)
  • Versus the way they are aggregated in GSTR-3B (summary-level)

If the chronology of adjustments is not aligned identically in both returns, the analytics engine may flag a mismatch even though the books and annual returns are correct overall.

5. E-Invoicing & IRN Data Flow Gaps

Assessees with aggregate turnover exceeding Rs. 5 crore are required to generate e-invoices, which then flow automatically into GSTR-1 from the IRN system.

A mismatch can occur where:

  • A correction is made in the accounting software
  • But the corresponding IRN record is not cancelled/amended as required

The books then reflect one set of figures, while IRN data (and therefore GSTR-1) reflects another. Many assessees only become aware of these differences after receiving departmental communication.

Practical observation: For FY 2018-19 to FY 2020-21, a large proportion of mismatch notices originate from credit/debit note timing, advance adjustments, and legacy-year portal issues — areas where entries are fully recorded in books and the net tax impact for the financial year is neutral, with no element of deliberate evasion.