Supplier GST Cancelled Retrospectively: Is Your ITC Safe?

You verified the vendor. The GSTIN was active, the legal name matched the invoice, you paid by bank transfer, the goods arrived and the credit appeared in your GSTR-2B. Two years later a notice arrives saying that vendor's registration was cancelled with effect from a date before your invoice, and the credit you claimed is being demanded back with interest and penalty. This is one of the most common input-tax-credit disputes in the GST system, and the uncomfortable part is that everything you did was correct at the time.

What retrospective cancellation does to your ledger

A cancellation order carries an effective date, and that date does not have to be the date of the order. Where the department concludes that a registration should never have continued from some earlier point — the business had already stopped operating, the premises were found non-existent, returns had not been filed for an extended period — it can cancel with effect from that earlier date.

For the taxpayer being cancelled, that is their problem to contest. For you, as a buyer, it silently rewrites the history of every invoice you received after the new effective date. On the department's reading, those supplies were made by a person not registered under GST, so no tax was validly charged, so no credit was validly available. The demand that follows is for the credit taken, plus interest, and frequently a penalty.

What makes it feel unjust is the timing asymmetry. On the day you transacted, the portal showed the supplier as active — because the cancellation order did not exist yet. There was no signal available to you, at any price, from any source, that would have prevented this. Understanding that clearly is important, because it tells you where to spend effort: not on trying to predict the unpredictable, but on being able to prove what the record said and that the transaction was real.

Why departments cancel with a backdated effect

Retrospective cancellation is not usually aimed at the buyer at all. It is a tool for dealing with registrations that have stopped being genuine — non-filers, businesses that have shut down without surrendering registration, and at the sharp end, entities set up to issue invoices without supplying anything. In that last category the whole point of the registration is to generate credit downstream, and cancelling only prospectively would leave the credit already generated untouched.

The common grounds, in rough order of how often buyers encounter them:

• Continuous non-filing of returns for the period specified in the rules.
• Physical verification failure — the registered premises do not exist or the business is not found operating there.
• Registration obtained by fraud, wilful misstatement or suppression of facts.
• Invoices without supply — the entity is found to have issued tax invoices without an underlying supply of goods or services.
• Voluntary applications where the taxpayer themselves sought an earlier effective date on closing the business.

The distinction that matters to you is between a supplier who was a real business that failed and a supplier who was never a real business. Both produce the same notice, but the facts you can marshal in response are very different, and so are your odds. Our explainers on GST cancellation and revocation and what suspended status means cover the mechanics from the registered person's side.

The legal hook: Section 16(2)(c)

Section 16(2) sets the conditions a recipient must satisfy to take credit, and clause (c) is the one that carries this dispute: the tax charged on the supply must actually have been paid to the government, in cash or through utilisation of credit. Read literally, it makes your credit contingent on someone else's conduct, over which you have no control and limited visibility.

That literal reading has been contested since GST began, and the buyer's argument is essentially one of proportionality: a recipient who transacted in good faith with a registered supplier, paid the invoice including tax through banking channels, and received the goods or services should not bear the loss when the supplier defaults or is later found to have been non-genuine. The department's answer is that the statute is clear and the recipient's remedy lies against the supplier.

Alongside 16(2)(c) sits clause (aa), which requires the invoice to have been furnished by the supplier and communicated to you — in practice, to appear in your GSTR-2B. Where a supplier reported an invoice but never paid the tax, Rule 37A now gives you a defined date and a mechanism to reverse the credit yourself. Retrospective cancellation is the harder case, because it can reach transactions where every visible condition was satisfied at the time.

What the notice looks like when it arrives

Typically it does not begin as a demand. The usual sequence is an intimation or a scrutiny communication asking you to explain credit taken against a specific GSTIN for specific periods, often generated from a departmental list of cancelled or non-genuine registrations. If the reply does not satisfy the officer, it escalates to a formal show-cause notice and then an order.

Two features of these notices catch companies out. First, they arrive in bulk — one list of suspect GSTINs produces communications to every buyer who claimed credit against them, so you may receive several at once covering different vendors and years. Second, the response window is short relative to the age of the transactions: you may have three weeks to produce documentation for invoices from three years ago. Whether you can do that easily is decided long before the notice arrives, by how you filed things at the time.

The procedural route from there — replying to a scrutiny notice, and appealing an adverse order — is covered in our guides to ASMT-10 scrutiny notices and the GST appeal process.

Where the litigation stands

This is an active and unsettled area, and it is worth being honest about that rather than promising an outcome.

Two distinct lines of challenge have developed. The first attacks the cancellation order itself, and has had considerable success: High Courts have repeatedly set aside retrospective cancellations passed without putting the proposed retrospective effect to the taxpayer, without recording reasons, or in terms that mechanically backdate the cancellation without applying any mind to the consequences for third parties. That line of authority is about administrative fairness, and it is largely brought by the cancelled taxpayer rather than by buyers.

The second attacks the denial of credit to a bona fide recipient. Here the picture is more mixed. Several courts have held that where the recipient establishes a genuine transaction — supply received, payment made through banking channels, a supplier registered on the date of the transaction — the department must first proceed against the defaulting supplier rather than recover from the buyer, and some rulings have gone further. Others have applied Section 16(2)(c) strictly. The position varies by High Court, and no single decision settles it nationally.

The evidence that decides your case

Across both lines of argument, the recipients who do well are the ones who can document that the transaction was real and that they behaved reasonably. That evidence is entirely ordinary — it is not exotic, and none of it is expensive to keep. It is simply much harder to assemble two years after the fact than at the time.

The fifth row is the one most companies cannot produce, and it is the only one that becomes impossible to recreate later. The portal shows the current status of a GSTIN, not a history of what it showed on any past date. If you did not record the result when you checked, there is no way to go back and establish it — and "we always check our vendors" is a much weaker submission than a dated record showing that this vendor, this GSTIN, was active on the day the invoice was booked.

Controls that produce that evidence automatically

The goal is not to add a compliance ritual; it is to make the record a by-product of processes you already run. Three points in an ordinary procure-to-pay flow do the work.

1. At vendor onboarding. Verify the GSTIN, confirm the legal name matches the entity you are contracting with, and store the full response — status, legal name, constitution, registration date, jurisdiction — against the vendor record with the date it was retrieved. The pattern is described in GST verification for vendor onboarding.
2. Before each payment run. Re-check status for vendors you are about to pay. This is where you catch a cancellation that has already happened and stop the credit claim before it is made, which is a materially better position than reversing it later. See vendor GST verification for accounts payable.
3. On a schedule, across the master. A monthly sweep of every active vendor catches status changes between transactions and gives you a continuous record rather than isolated snapshots. The scheduling pattern and cost profile are in automated vendor GSTIN monitoring, and if the bill is the objection, cutting verification API costs covers deduplication and caching.

One design detail matters more than the rest: store the response, not a boolean. A column that says the vendor "passed" tells a tax officer nothing three years later. The stored payload with a retrieval timestamp is the document that does the work, and it costs a few hundred bytes per vendor per check.

If a notice has already landed

Working order, assuming the notice names specific GSTINs and periods:

1. Establish the effective date of cancellation for each named supplier, and separate the invoices that fall before it from those that fall after. Only the latter are genuinely in dispute, and notices are not always drawn accurately in this respect.
2. Assemble the transaction file per invoice from the table above. Gaps are better identified now than in the reply.
3. Check whether the cancellation order itself was properly passed, and whether the supplier has challenged it or obtained revocation. A cancellation set aside or revoked removes the foundation of the demand.
4. Reply within the window, in the prescribed form, addressing each invoice rather than the vendor in aggregate. Ask for an extension in writing if the volume genuinely requires it.
5. Get professional representation before the matter escalates to an order. The cost of advice is almost always smaller than the credit at stake, and the appellate route has its own deadlines and pre-deposit requirements.

And separately from the response: fix the control. Nearly every company that receives one of these notices receives another, because the same gap in the vendor master produced both.

Frequently asked questions