GST Notice Uploaded After the Deadline Is Time-Barred: Delhi High Court

Court: Delhi High Court (Justices Anil Kshetarpal & Bharat Parashar)
The ruling: SCN uploaded after the deadline is time-barred
Why: "Awaiting GSTN confirmation", no CRN = not validly issued
Outcome: Show-cause notice and demand order quashed

The short version

The Delhi High Court has held that a GST show-cause notice (SCN) generated within the time limit but uploaded on the portal after the deadline is time-barred — and quashed both the notice and the demand order built on it.
The notice sat on the department's internal system marked "awaiting GSTN confirmation" with no Common Reference Number (CRN). The Court said a notice that is unconfirmed, lacks a CRN and is not communicated to the taxpayer cannot be said to have been "issued" in the eyes of law.
A technical glitch during the department's system migration was no excuse: Section 73(2) must be read with Section 169 (modes of service), and the department hadn't tried registered post, speed post or email despite knowing of the problem.
The principle that matters for taxpayers: limitation fixed by Parliament cannot be extended by an administrative lapse, and the officer has no power to extend the Section 73(2) deadline. The notice's internal generation date can't give it retrospective validity.

Here's a question that decides a surprising number of GST disputes: when is a show-cause notice actually "issued" — the moment an officer creates it on an internal system, or the moment it reaches the taxpayer on the portal? The Delhi High Court has given a clear, taxpayer-friendly answer. In a case involving a Hyundai dealership, it held that a notice generated in time but uploaded and communicated after the limitation deadline is time-barred — and quashed the entire demand. For any business sitting on a late-served SCN, this is an important precedent.

What happened

The petitioner, Sikka Motors Pvt. Ltd., challenged a show-cause notice dated 30 May 2024 that was actually uploaded on the GST portal only on 8 August 2024, along with the consequential demand order dated 23 August 2024. The dispute arose from scrutiny of the company's returns for FY 2019-20, where the department alleged wrongful input tax credit of ₹10,57,392 (from suppliers whose registrations were later cancelled retrospectively) and ₹5,57,720 (from suppliers who hadn't filed GSTR-3B).

The company's case was simple: even after the extended limitation period under the CBIC notification, the SCN for FY 2019-20 had to be issued by 31 May 2024. Since it only became available on the portal on 8 August 2024, it was beyond limitation.

The department argued the notice had been generated and uploaded on its internal "AIO" system on 30 May 2024 — within time — but a technical glitch during migration to the GST back-office portal meant it couldn't integrate with the GST Network (GSTN), and it was re-uploaded on 8 August 2024.

What the Court held — "generated" is not "issued"

The High Court rejected the department's defence. Its reasoning runs along a clear line:

Section 73(2) must be read with Section 169. The statutory timeline for issuing an SCN can't be separated from the modes of service prescribed in Section 169. Issuance implies communication, not mere internal creation.
No CRN, no valid issuance. The portal entry showed the notice as "awaiting GSTN confirmation" and carried no Common Reference Number (CRN) — meaning it had not been integrated with the common portal or communicated to the taxpayer. "A notice that remains on an internal system, unconfirmed and without a CRN, cannot be said to have been issued in the eyes of law."
An internal date can't confer retrospective validity. The remark on the re-uploaded notice, or its date of generation, cannot give it retrospective effect — no statutory provision empowers the officer to extend the limit under Section 73(2).
The glitch was the department's problem, not the taxpayer's. The authorities made no attempt to serve the notice by alternative modes — registered post, speed post or email — despite knowing of the technical issue. Consequences of administrative lapses can't be visited on the taxpayer, nor can such lapses extend a limitation period fixed by Parliament.

On that basis, the Court quashed both the show-cause notice and the demand order.

The law behind it: why timing is everything under Section 73

For non-fraud cases, Section 73 of the CGST Act sets a hard limitation structure. The adjudication order must be passed within three years of the due date for the annual return of the relevant year, and the show-cause notice must be issued at least three months before that order deadline. For FY 2019-20, those dates were extended by CBIC notification — which is why the effective last date to issue the SCN worked out to 31 May 2024.

Why "service", not "generation", is the test

A notice exists, in law, only when it is communicated to the person it's meant for. Section 169 lists the valid modes — including making it available on the common portal. Until the SCN is actually served through one of those modes (reflected by a CRN on the portal, or a post/email record), the limitation clock has not been met, no matter when the officer typed it up internally. This is the crux: a demand built on a notice that was never validly served within time collapses at the threshold, without the merits ever being reached.

What this means for taxpayers

This ruling gives businesses a concrete, checkable defence — but it has to be used correctly.

Check the actual date the SCN was served/uploaded, not just its printed date. On the portal, note when the notice appeared and whether it carries a CRN. A gap between the "notice date" and the upload date can be decisive.
Map it against the limitation deadline. Work out the last date the SCN could lawfully be issued for that financial year under Section 73 (with any CBIC extensions). If service happened after that date, limitation is squarely in play.
Preserve the evidence. Screenshot the portal status ("awaiting GSTN confirmation", missing CRN, upload date). That record is what the Court relied on.
Raise limitation at the earliest stage. A time-bar goes to jurisdiction — flag it in your reply and, where appropriate, by writ, rather than only arguing the merits of the ITC dispute.
Don't assume every late notice is dead. The facts matter — the date of service, the CBIC extensions and whether any valid mode of service was used. Get the specific timeline assessed before relying on this.

A note of caution — this is a High Court ruling on specific facts

This is a decision of the Delhi High Court on the facts before it, and the department could seek to appeal or distinguish it. It is strong, persuasive authority — especially on the principle that administrative or technical lapses can't extend a Parliament-fixed limitation — but outcomes turn on the exact dates and mode of service in your case. Treat it as a basis to examine your notice carefully, not as an automatic quashing of every late-uploaded SCN.

Frequently asked

Is a GST notice "issued" when it's created or when it's served?

Per this Delhi High Court ruling, issuance has to be read with the modes of service in Section 169 — a notice merely generated on an internal system, without a CRN and not communicated to the taxpayer, is not validly "issued." Service, not internal creation, is the test for limitation.

What is a CRN and why did it matter here?

A Common Reference Number is generated when a notice is integrated with the GST common portal and communicated to the taxpayer. The absence of a CRN (the entry showed "awaiting GSTN confirmation") indicated the notice had not been validly served within the limitation period.

Can a technical glitch extend the time limit to issue an SCN?

No. The Court held that administrative or technical lapses cannot extend a limitation period fixed by Parliament, and the officer has no power to extend the Section 73(2) deadline. The department should have used alternative service modes (post/email) if the portal failed.

What is the limitation period for a Section 73 show-cause notice?

For non-fraud cases, the adjudication order must be passed within three years of the annual return due date, and the SCN must be issued at least three months before that — subject to any CBIC extensions for the relevant year (as applied to FY 2019-20 here).

I've received a notice that looks late — can I get it quashed?

Possibly, if it was served after the limitation deadline. It depends on the exact dates, the applicable CBIC extensions and whether any valid mode of service was used in time. Get the specific timeline reviewed before acting — limitation is best raised early.

Received a GST notice that may be time-barred?

efiletax reviews the service date, CRN status and limitation position of your GST notices and demand orders — and builds the right reply or challenge, so you don't pay on a notice that was never validly issued.

Get your notice reviewed

Disclaimer: This article summarises a reported judgment of the Delhi High Court quashing a GST show-cause notice and demand order on the ground that a notice generated within time but uploaded/served on the common portal after the limitation deadline is time-barred, and is based on publicly reported information current as at the date of publication. It is a decision on its specific facts and may be subject to appeal or differing views in other cases; it is provided for general understanding and is not legal advice. The limitation position in any matter depends on the exact dates, applicable notifications and mode of service — please consult a qualified professional before acting. Talk to efiletax if you need help.