GST Registration Cancellation for Closed or Missing Business Premises: What the Law Actually Says

Introduction: A Growing Crisis for Small Businesses

Across India, countless small and medium-scale businesses are confronting an increasingly alarming administrative reality — their GST registration being abruptly cancelled following a departmental field visit where the inspector found the shutters down or no one present at the premises. For many assessees, this is not merely an inconvenience. It is a business-crippling event that halts operations, strips away legitimacy, and creates cascading compliance complications.

What makes this situation particularly troubling is the speed and finality with which such cancellations are often executed — without a meaningful hearing, without proper inquiry, and frequently on the basis of nothing more than a single unannounced visit to a temporarily closed office or shop. The department's working assumption, all too often, is that a locked door equals a non-existent business.

However, the legal position is far more nuanced and protective of the assessee's rights. Multiple High Courts — including the Bombay High Court and the Allahabad High Court — have stepped in with significant judicial pronouncements to check this administrative overreach and restore fairness in the GST cancellation process.

This article examines the legal framework governing GST registration cancellation, the specific procedural deficiencies that courts have identified and condemned, and the remedies available to businesses unjustly caught in this trap.


The authority to cancel a GST registration is granted to the proper officer under Section 29(2) of the Central Goods and Services Tax Act, 2017. This provision specifies the conditions under which cancellation may be initiated — including situations where registration was obtained through fraud, willful misstatement, or suppression of facts.

Critically, however, Section 29(2) contains a mandatory proviso: no registration shall be cancelled without first giving the concerned person an opportunity of being heard.

This is not a procedural formality. It is a constitutional safeguard rooted in the doctrine of natural justice — specifically, the principle of audi alteram partem (hear the other side). Indian courts have consistently interpreted this requirement strictly, and any departure from it renders the cancellation order legally vulnerable.

Key point: A finding that premises were closed during a surprise inspection does not, by itself, constitute a valid ground for cancellation under Section 29(2). The department must establish a direct and verifiable link between the closure and one of the specified statutory grounds.


Why Field Visit-Based Cancellations Keep Going Wrong

1. Vague and Cryptic Show Cause Notices

One of the most pervasive procedural failures in such cancellation proceedings is the issuance of a Show Cause Notice (SCN) that is non-specific, generic, and effectively meaningless from the assessee's perspective.

An SCN that merely states, in boilerplate language, that "registration was obtained by means of fraud, willful misstatement or suppression of facts" — without identifying the nature of the alleged fraud, the date and time of the field visit, or the contents of the survey report — cannot serve as a lawful foundation for adverse action.

The Hon'ble Bombay High Court in Makersburry India Pvt. Ltd. vs. State of Maharashtra held categorically that a vague SCN which fails to set out clear, specific grounds deprives the assessee of any meaningful opportunity to respond, making the resulting order inherently defective. The assessee cannot be expected to mount a defence against allegations that are never properly stated.

What a valid SCN must contain:

  • Precise allegations forming the basis of proposed cancellation
  • Date, time, and details of the field visit or survey
  • Identity of the inspecting officer
  • Copy of the survey or inspection report
  • Specific ground under Section 29(2) being invoked

2. Complete Disregard for the Assessee's Reply and Evidence