Summary: The article examines the growing practice of retrospectively cancelling GST registrations based on backend NGTP (Non-Genuine Taxpayer) tags and subsequently denying Input Tax Credit (ITC) to bona fide buyers without independent evidence. It argues that risk flags generated through data analytics are often treated as conclusive proof, leading to mechanical cancellation orders under Section 29(2) and ITC reversal proceedings under Sections 73 or 74 without establishing fraud, collusion, or absence of genuine supplies. Relying on recent High Court decisions, including those of the Gauhati, Allahabad, Calcutta, Madras, Himachal Pradesh and Tripura High Courts, the article emphasizes that cancellation orders must be reasoned, based on statutory grounds, and comply with principles of natural justice. It further highlights that retrospective cancellation alone cannot justify denial of ITC where buyers satisfy the conditions of Section 16(2). The article advocates judicial oversight, administrative reforms, and evidence-based enforcement to protect genuine taxpayers from arbitrary action.
Retrospective GST Cancellation and NGTP Tags: Why Buyers Are Punished Without Proof – And What the Courts Are Now Saying
Introduction: When a backend label becomes a weapon
Under GST, cancellation of registration and denial of input tax credit (ITC) should be serious, evidence‑based decisions. In reality, many taxpayers today are facing a different picture. A supplier is suddenly labelled “NGTP / non‑existent” on the backend, registration is cancelled retrospectively with a tick in the portal, and within months buyers receive notices under section 73 or 74, asking them to reverse ITC, pay tax and interest, and even face 100% penalty—all without ever seeing proper proof of non‑existence or fraud.
This article looks at why this is happening, how it misuses section 29(2) and section 16, and how recent High Court decisions are starting to protect genuine buyers.
How NGTP and retrospective cancellation actually operate on the ground
Bulk intelligence and list‑driven action
The starting point is usually not a detailed investigation. It is a list.
Data analytics units and DGGI generate lists of “risky” GSTINs: failed verification, abnormal ITC chains, suspected fake registrations, network flags, NGTP tags. These lists are circulated to State and Central Commissionerate’s, often in bulk, with one‑line labels like “non‑existent”, “failed verification”, “NGTP”. There is usually no full inspection report or consignment‑wise material attached at that stage. The officer in the jurisdiction may see only a summary flag and a direction to “take action”.
What should have been a starting point for investigation ends up becoming treated as conclusive proof.
Portal‑driven checkbox culture
The registration module under GST allows cancellation by choosing a ground under section 29(2) and issuing a standard REG‑19 order. On paper, this is only a format. In practice, it has encouraged a culture of tick‑and‑generate orders.
Many officers simply:
tick “non‑existent / bogus / fraud” under section 29(2),
let the system generate a skeletal order,
and leave the “reasons/facts” box almost blank, or fill it with a single line like “reply not satisfactory”.
Show‑cause notices are often equally vague. They may refer to “non‑existence” or “fake ITC chain” without annexing inspection reports, dates of visit, statements, or any primary material. From the department’s side, this looks like “intelligence‑based action”. From the supplier’s and buyer’s side, it looks like a label without proof.
Why buyers never see the proof behind NGTP and cancellation
Law focused on the registered person, not its customers
Section 29(2) and the registration rules focus on the registered person whose registration is being cancelled. There is no express statutory requirement to share the department’s inspection reports or DGGI intelligence files with downstream buyers. That material is treated as “internal”.
When buyers later receive SCNs under sections 73/74, officers use the fact of supplier cancellation or NGTP tagging as short‑hand “evidence” and do not feel obliged to disclose the basis of that cancellation. The buyer is expected to accept that the supplier is “non‑existent” simply because the portal says so.
Shortcut: label as proof
The practical shortcut in many files looks like this:
“Your supplier’s registration has been cancelled retrospectively / labelled NGTP.”
“Therefore, your ITC is wrong and is liable to be reversed, with tax, interest and penalty.”
No independent examination of invoices, e‑way bills, lorry receipts, weighment slips, bank payments or stock records is undertaken. No attempt is made to prove that goods did not move or that buyer colluded. The NGTP / cancellation label substitutes for actual evidence.
Courts are now saying this shortcut is not legally acceptable.
How this misuses section 29(2) and violates natural justice
Section 29(2) permits cancellation only on specified statutory grounds: non‑filing, non‑commencement, contravention of provisions, fraud / wilful misstatement / suppression, etc. It does not authorise cancellation simply because a GSTIN appears on a risk list.
In many NGTP cases, orders and notices:
merely recite that registration is liable to be cancelled “under section 29(2)” without stating which clause is applied;
contain no facts—no date of inspection, no name of visiting officer, no statement, no basic narrative;
do not disclose what material was actually used to conclude “non‑existence”.
Several High Courts have now directly criticised this style of cancellation.
Gauhati High Court – G.R. Nirmolia
In G.R. Nirmolia, Gauhati High Court quashed a cancellation order where REG‑19 was issued without recorded reasons. The Court held that even if a taxpayer does not reply to the show‑cause notice, the officer is not excused from the duty to pass a reasoned, speaking order. A portal format and checkbox are not enough. An order having serious civil consequences must show application of mind.
Allahabad High Court – “reasons are the heart and soul”
Allahabad High Court, in multiple cases (including Pragati Enterprises and Shree Shyamji Traders), has repeatedly held that:
GST registration cannot be cancelled merely by describing the firm as “bogus” or “non‑existent”;
orders that do not assign reasons, do not refer to specific section 29(2)(a)–(e) grounds, and simply rely on backend labels are invalid;
reasons are the “heart and soul” of any administrative order.
In some of these matters, the Court went further and observed that frequent cancellation of GST registrations without assigning reasons amounts to the “economic death” of businesses, and directed the department to act with greater caution.
The message from these rulings is clear: section 29(2) is being systematically misused in NGTP contexts. The law demands statutory grounds plus reasons. The practice often supplies only a tick and a conclusion.
Impact on ITC: why buyers are punished without proof
The next link in the chain is ITC denial.
Once a supplier is cancelled—often with retrospective effect—many officers treat that cancellation as decisive proof against the buyer. Notices under section 73 or 74 allege wrongful ITC, sometimes classify it as fraud, and seek:
reversal of ITC,
tax on the reversed ITC,
interest, and
100% penalty in section 74 cases.
All of this is based on three sentences: “supplier cancelled; NGTP; therefore, ITC wrong”.
High Courts are now consistently saying that this approach is legally unsustainable.
Courts on retrospective cancellation and ITC
A series of decisions from Calcutta, Madras, Himachal Pradesh and Tripura High Courts have laid down important principles:
Retrospective cancellation alone is not sufficient to deny ITC. ITC cannot be rejected solely because the supplier’s GSTIN was cancelled retrospectively.
Authorities must examine the genuineness of the transaction and section 16(2) compliance.
Was there a proper tax invoice?
Were goods actually received?
Were transport and weighment documents available?
Were payments made through banking channels?
Was the supplier active and registered on the date of supply?
Where these conditions are satisfied, ITC to a bona fide buyer cannot be denied merely because the supplier later failed to file returns or was cancelled.
Tripura High Court, in a widely discussed decision, went even further and read down section 16(2)(c): the Court upheld its validity but held that denial of ITC for supplier default should be confined to non‑bona fide, collusive or fraudulent transactions. For genuine buyers, remedy lies against the supplier, not by punishing the recipient.
This line of jurisprudence directly attacks the departmental practice of using NGTP/cancellation labels as proof against buyers.
Why departments rarely build proper proof against buyers
There are structural reasons:
Bulk NGTP lists and analytics: The initial action is often list‑driven; officers are under pressure to “act” quickly.
Transaction‑wise proof is hard work: Proving that goods did not move, that transport was bogus, or that payments were circular needs time and field verification.
Shortcut seems easier: Using NGTP/cancellation as proxy saves effort in the short term, but it collapses in court because it lacks supporting evidence.
In simple language, the machinery is designed for risk‑flagging, not for careful adjudication. Officers are trying to use a risk flag (NGTP) as if it were fully proved fraud.
When will this problem really be “solved”?
Realistically, three forces will have to work together.
1. Judicial pressure
High Courts are already setting aside checkbox cancellations and ITC demands that rest solely on supplier cancellation or NGTP labels. Some judgments have expressly asked departments to frame norms and follow natural justice.
The Supreme Court has now taken up:
whether ITC can be denied solely because supplier’s registration is cancelled retrospectively;
constitutional and practical challenges to section 16(2)(c), which directly interacts with supplier default.
A strong Supreme Court judgment that:
demands proper use of section 29(2); and
limits ITC denial to prove non‑genuine / collusive transactions,
will force uniform changes in SOPs and training.
2. Administrative reform
CBIC has already issued good instructions on summons, arrest and other coercive powers. A similar, clear instruction is needed for NGTP and registration cancellation, saying in plain terms:
no mechanical NGTP cancellations;
cancellation orders must record facts, reasons, and specific section 29(2) clauses;
ITC cannot be denied solely on retrospective cancellation without independent evidence of bogus supply or collusion.
The GST Council and CBIC together will also have to adjust the portal design so that REG‑19 cannot be issued with an empty “reasons” box—forcing officers to write at least a minimum narrative.
3. Culture change
Ultimately, enforcement culture must move from:
“Risk flag → cancel supplier → deny ITC to buyers → raise 74 demands with 100% penalty”
to:
“Risk flag → investigate supplier properly → pass reasoned cancellation order → if buyer ITC is questioned, examine section 16(2) and prove non‑genuine supply or buyer collusion”.
That culture change will not happen overnight. It will happen because repeated quashings and judicial criticism make mechanical NGTP‑driven orders personally and institutionally costly.
What taxpayers and professionals can do now
Until systemic correction arrives, the only practical path is strong, case‑wise resistance.
For suppliers facing NGTP / retrospective cancellation
Demand copies of:
the show‑cause notice,
inspection reports,
field enquiry notes,
statements recorded,
REG‑19 order.
If the REG‑19 order is checkbox/non‑speaking, rely on G.R. Nirmolia and the Allahabad line to seek revocation or file a writ petition, arguing that:
section 29(2) ground is not specified;
reasons are absent;
natural justice is violated.
For buyers facing ITC denial and section 74 demands
Build a strong factual file:
Tax invoices meeting Rule 46.
E‑way bills, lorry receipts, weighment slips, gate entry registers.
Bank statements showing payments to suppliers.
Stock records and GSTR‑2A/2B snapshots.
Portal evidence that suppliers were active and registered on transaction dates.
In your replies and appeals:
Plead clear compliance with section 16(2).
Cite the Calcutta, Madras, Himachal and Tripura decisions: ITC cannot be denied solely on retrospective cancellation or supplier default; genuineness and collusion must be proved.
Emphasise that NGTP/cancellation is only a label; the department must bring real evidence that no supply occurred or that you were part of a sham chain.
Use burden‑of‑proof logic wherever possible: once you show section 16(2) compliance, the burden shifts to the department to prove that supplies were not genuine.
Document patterns for systemic advocacy
Maintain a dossier of NGTP and retrospective cases showing:
identical portal language;
lack of reasons;
absence of shared material.
This can later support representations to CBIC or, if needed, wider litigation challenging the misuse of section 29(2) and NGTP tagging.
Conclusion: Labels are not proof; backend flags are not a verdict
The present NGTP/retrospective‑cancellation machinery is punishing buyers without proof because it was built for bulk risk‑flag action, not for transaction‑level legal adjudication. Officers are using section 29(2) and supplier cancellation as shorthand to attack ITC instead of doing the harder work of proving non‑existence or fraud.
Courts are now clearly saying this is not acceptable. A cancellation order needs reasons. An ITC denial needs evidence. A label like “NGTP” is a starting point for investigation, not the end of the story.
Until the Supreme Court and CBIC/GST Council push formal reform, the only way to protect bona fide taxpayers is to stand firm on these principles in every case—insisting on proof, insisting on reasons, and insisting that backend flags cannot replace the rule of law.
Author Bio
