The GST Indemnity Clause Your Vendor Isn't Telling You About
GST5 July 20266 min read

The GST Indemnity Clause Your Vendor Isn't Telling You About

Your supplier's GST registration lapses. Suddenly you're staring at reversed input credits and a ₹50 lakh demand notice. Here's how to write contract clauses that make them, not you, absorb that hit.

Advocate Rajiv Shukla

Published 5 July 2026

You sign a supply contract with a Delhi manufacturer. Three months in, the goods arrive, you pay on time, everything seems fine. Then the GST auditor calls: your vendor's registration was suspended for non-filing. Your input-tax credits on those invoices? Denied. You're now liable for the tax yourself—plus penalty interest.

This isn't theoretical. It happens to in-house counsel and procurement teams constantly. The difference between a smooth recovery and a ₹20-lakh write-off often comes down to one clause in your contract that nobody read carefully.

Why Standard "Indemnity" Language Fails You

Most commercial contracts contain some version of this: "Seller shall indemnify Buyer against all tax liabilities arising from this contract." Sounds protective, right? It isn't.

Here's the problem: that clause is vague on three critical points.

  • What counts as a tax liability? Does it include reversed input credits? Penalty interest? Officer costs? If your contract doesn't say, your vendor's lawyer will argue their way to the narrowest possible reading.
  • When does indemnity kick in? After a demand notice? After an appeal fails? If you've already paid? The longer you wait to trigger the clause, the harder it is to recover.
  • Who proves the vendor's fault? If the GST officer disallows your credits because the invoice itself is non-compliant (say, missing PAN), is that automatically the vendor's breach? Not always. You may need to prove negligence.

A boilerplate indemnity clause leaves all three questions open. Your vendor exploits that ambiguity. Your finance team eats the cost.

Building a Working GST Indemnity: Four Core Protections

Here's what a tighter clause should cover, in plain terms:

1. Strict Liability for Vendor Compliance

Don't rely on proving "negligence." Instead, make compliance a contractual promise:

"Vendor warrants that all invoices issued shall comply with GST Rules 2017 (Notification No. 1/2017-Central Tax), including accurate GSTIN disclosure, correct HSN/SAC codes, and real-time reporting to GSTR-1. Vendor shall be liable for any disallowance of input tax credit arising from Vendor's non-compliance, regardless of Buyer's negligence."

Why this works: You've shifted the burden. The vendor must prove their invoice was correct—not the other way around. And you've made clear that even if your own audit team missed a red flag, the vendor still pays. This is called "strict liability," and it's enforceable in India if clearly stated.

2. Define "GST Liability" to Cover the Whole Cost

Your GST officer disallows ₹1 lakh of input credit. But the real hit is ₹1 lakh (tax) + ₹20,000 (interest at 18% per annum for two years) + ₹10,000 (penalty under Section 122 of the CGST Act) + ₹5,000 (legal fees). That's ₹1.35 lakh total, not ₹1 lakh.

Your indemnity clause must say:

"GST Liability shall mean: (a) the tax amount itself, (b) all interest and penalties imposed by any GST officer, (c) cost of appeal or legal proceedings, and (d) cascading tax on any goods/services supplied downstream using the disallowed credit. Vendor shall indemnify Buyer against the full GST Liability, not just the principal tax."

In practice: You'll recover not just your denied credit, but also the time cost of fighting it.

3. Trigger the Indemnity Early and Clearly

Don't wait for a final demand. The moment you receive a notice questioning your input credit (e.g., a notice under Section 42 of the CGST Act asking you to pay or explain), notify the vendor immediately. Your clause should say:

"Buyer shall notify Vendor within 10 days of receipt of any GST demand, show-cause, or denial of input credit. Vendor shall respond within 20 days with supporting documents. If Vendor fails to respond, or if the response is inadequate, Vendor shall bear 100% of the GST Liability within 30 days of Buyer's written demand."

This creates a tight timeline and removes the excuse of "I didn't know."

4. Cover Cascading Damage

Here's the trap most people miss: if your input credit is reversed, and you've already passed that credit downstream to your own customer, your customer also loses their credit. That's cascading liability. Your vendor should cover it:

"Vendor's indemnity extends to any GST demand raised against Buyer or Buyer's customers that directly results from the Vendor's non-compliant invoice, including any claims or disputes from Buyer's downstream customers."

This prevents the vendor from saying, "Fine, I'll cover your loss, but not your customer's." In a supply chain, that distinction is artificial.

Practical Drafting: Two Real Scenarios

Scenario 1: Bengaluru SaaS Company Buying Cloud Hosting

Your vendor (a US company with an Indian GSTIN) invoices you for ₹25 lakh per quarter. Their GSTIN turns out to be fraudulent. The GST officer disallows your input credit and also slaps you with a ₹5-lakh penalty for "knowingly accepting the fraudulent invoice." A tailored clause would protect you here:

  • Require the vendor to provide proof of GSTIN validity before invoicing (and quarterly thereafter).
  • Make the vendor liable for penalties imposed on you for their fraudulent registration.
  • Include a termination right: if GSTIN is invalid, you can recover the full payment immediately.

Scenario 2: Manufacturing Firm Buying Raw Materials

Your supplier's HSN code is wrong on 30% of invoices (they've used a lower rate, so input credit is understated in their favor). Over a year, you've accumulated ₹12 lakh of incorrect input credits. The auditor flags it, and you face a demand plus interest. The indemnity should:

  • Make the supplier liable for systematically incorrect HSN codes.
  • Allow you to reclaim overpaid tax from the supplier retroactively (e.g., if you've paid tax at a higher rate because their code was wrong).
  • Let you suspend payments to the supplier until they provide corrected invoices and indemnify you.

What to Ask Your Tax Counsel Before Signing

Before you finalize a vendor contract, get your tax lawyer to review the indemnity clause by asking these three questions:

  1. If the vendor's GSTIN is invalid, can I recover the full payment plus interest? If the answer is "you'd have to prove they were negligent," that's not tight enough.
  2. If the GST officer disallows my input credit and also imposes a penalty on me (under Section 122 or 129 of the CGST Act), is the vendor on the hook for both? Any hedging here is a red flag.
  3. How long do I have to claim indemnity after the demand? Insist on a long window (at least 2 years after the demand is finally resolved, including appeals). Indemnity claims can take time.

One Final Reality Check

A brilliant indemnity clause is only as good as the vendor's ability to pay. Before you sign, check:

  • Does the vendor have a solid financial history? (Check MCA filings, credit reports.)
  • Can you build in a security deposit or parent-company guarantee to back the indemnity?
  • If the vendor is a shell or a fly-by-night operator, no clause will save you. Walk away early.

The goal isn't to create a watertight legal weapon (no clause is completely watertight). It's to shift the incentives: make it expensive and embarrassing enough for the vendor to stay compliant in the first place. A ₹50-lakh indemnity liability hanging over their head is a powerful motivator to file GSTR-1 on time and use the right HSN codes.

So the next time you're reviewing a supply contract, don't skip the indemnity section. Spend an extra hour with your counsel drafting it tightly. It could save you ₹20 lakhs and a year of auditor calls.

Found this useful? Share it.