Rule 86A GST: When an Officer Blocks Your Input Tax Credit

You open the GST portal to file GSTR-3B and the credit you were counting on is there in the ledger, but the return will not let you use it. No demand has been raised, no order passed, and there may have been no hearing. The credit has been blocked under Rule 86A of the CGST Rules, and until the block is lifted or lapses, your tax has to be paid in cash. This post explains what the rule allows, what it does not, and what a business can do before and after it happens.

What Rule 86A says

Rule 86A sits in the part of the CGST Rules that deals with the electronic credit ledger. It gives the Commissioner, or an officer authorised by him not below the rank of Assistant Commissioner, a power to not allow debit of an amount equivalent to credit in a taxpayer's ledger. Debit is how credit gets used: to discharge output tax under Section 49, or to claim a refund of unutilised credit. Stopping the debit stops both.

The design is deliberate. Recovering wrongly availed credit through a show cause notice and an order takes time, and by the end of that process fraudulent credit has usually been passed on or utilised. Rule 86A lets the department hold the credit where it is while the question is examined. It was introduced in late 2019, at a time when fake-invoice networks were a major enforcement focus, and that context explains its shape.

The grounds an officer can rely on

The power is not open-ended. The officer must have reasons to believe the credit was fraudulently availed or is ineligible because of one of the situations the rule lists. In plain terms:

The third column is the uncomfortable part. Two of the five grounds can be triggered entirely by what a supplier did or failed to do, and they are also the grounds used most often in practice. A departmental investigation into a supplier often ends with blocks applied to the ledgers of every buyer who claimed credit on that supplier's invoices.

Reasons to believe, recorded in writing

Two phrases in the rule do most of the protective work. The officer must have reasons to believe, and those reasons must be recorded in writing. Together they mean the block must rest on material the officer has actually considered, such as an investigation report or a physical verification of the supplier's premises. Suspicion or a general risk score is not enough, and the officer has to write the reasons down before acting.

Departmental guidance has repeated the same point: the power is meant to be used carefully, on evidence, with the reasons written down, and not as a routine recovery tool. It has also clarified that the amount blocked cannot exceed the credit actually in the ledger. That became necessary because early practice sometimes created negative balances, a problem covered in our explainer on the electronic credit and cash ledgers.

For a taxpayer, this matters because the written reasons are what you respond to. A block you cannot explain is hard to contest. A block whose recorded reasons name one supplier and one period tells you exactly what evidence to gather.

How a block shows up on the portal

A Rule 86A block shows up in your own ledger, not in anyone else's. On the GST portal, the blocked amount is shown separately from the credit available for use, and the ledger records when an amount was blocked and when it was unblocked. When you file GSTR-3B, the utilisation screen offers only the unblocked balance, so any liability the blocked credit would have covered has to be paid from the cash ledger.

The block is visible only to the taxpayer whose ledger is restricted and to the department. A supplier's block is invisible to its buyers, which is why the search for a GST blacklist does not get very far. What buyers can see are the signals that tend to appear around the same time: a supplier's registration being suspended or cancelled, or its returns stopping.

The one-year lapse

The rule builds in its own time limit. A restriction ceases to have effect on the expiry of one year from the date it was imposed. After that, the credit is usable again unless something else prevents it. Separately, the officer may lift the block earlier, once satisfied that the conditions for imposing it no longer exist.

Two practical points follow. First, record the date of every block, because the one-year period runs from that date and not from when you noticed it. Second, the lapse only ends the block. It does not settle whether the credit was valid, and the department can still question the credit through the normal demand process within the applicable time limits.

What you can do about a block

The response is usually the same whatever the ground, and it is largely about evidence.

1. Identify exactly what was blocked. The amount, the tax heads, the date, and the suppliers or invoices it relates to. Notices do not always match the blocked amount precisely.
2. Obtain the recorded reasons. The rule requires them to exist. If they have not been shared, ask for them in writing, because you cannot answer grounds you have not seen.
3. Assemble the transaction file. For each affected invoice: the tax invoice, purchase order, proof of payment through banking channels, e-way bills or transport documents, goods receipt or service evidence, the GSTR-2B in which it appeared, and the supplier's registration status on the date you dealt with them.
4. Make a written representation to the officer who imposed the block, asking for it to be lifted and showing why the recorded grounds do not apply to your transactions.
5. Escalate with advice. Rule 86A does not set out a dedicated appeal route of its own. Where a block is imposed without proper reasons, outside the listed grounds, or kept in place beyond its life, taxpayers have in principle sought relief from the High Court through a writ petition. Whether that is the right course is a question for a professional who has seen the order and the facts.

If the matter moves to a formal demand, the process changes. That is covered in our guides to show cause notices under Sections 73 and 74 and the GST appeal process.

Rule 86A is not Rule 86B, Section 16 or Rule 37A

Several provisions restrict credit, and they are easy to confuse. They work in different ways.

The key difference is that Rule 86A is a holding measure. Section 16 and Rule 37A decide whether credit is available at all, and a failure under either leads to reversal with interest. Rule 86A decides nothing about entitlement. It keeps the credit in place while an officer finds out. Rule 86B is different again: it does not suggest anything about a particular invoice, it simply applies to taxpayers above a threshold unless an exception applies. The wider set of conditions is in input tax credit rules explained.

Preventing the block in the first place

Most Rule 86A blocks against genuine businesses begin with a supplier: one that turns out to be non-existent, non-operating, or not paying the tax it collects. You cannot see a block on a supplier's ledger, but you can see much of what leads up to one, and you can keep evidence that you checked.

1. Verify at onboarding. Confirm the GSTIN is active, that the legal name matches the entity you are contracting with, and that the registered address is plausible for the business. Store the full response with a timestamp. The pattern is in GST verification for vendor onboarding, and how to check a fake GST number covers the warning signs.
2. Re-check before paying. Status changes between onboarding and payment. A check in the payment run catches a suspended or cancelled supplier before the credit is claimed. See vendor GST verification for accounts payable.
3. Watch filing history, not just status. A supplier that stops filing GSTR-3B is the one most likely to be behind on paying tax. Our guide to checking supplier return filing status explains how to read it, and automated vendor GSTIN monitoring covers running the check on a schedule.
4. Keep the records when you create them. The portal shows what a GSTIN looks like today, not what it looked like when you transacted. If a supplier is later cancelled with retrospective effect, your stored verification result is the only proof of what the public record showed at the time.

Frequently asked questions