

Indemnity is a risk-allocation arrangement in which one party agrees to compensate another party for specified losses, damages, claims, penalties, legal costs, or liabilities.
In simple terms, it answers one important business question: if something goes wrong because of a defined event, who will bear the financial burden?
In India, indemnity is commonly seen in commercial contracts, vendor agreements, insurance policies, service-level agreements, technology contracts, leases, acquisition documents, and partnership arrangements. The Indian Contract Act, 1872 recognises a contract of indemnity as a promise by one party to save another from loss caused by the conduct of the promisor or another person.
For businesses, indemnity is not just a legal clause hidden at the end of a contract. It is a practical tool for managing commercial risk. A well-written indemnity clause can protect a company from losses arising from events such as breach of confidentiality, intellectual property infringement, tax claims, product defects, negligence, data misuse, third-party claims, or non-compliance by a vendor.
An indemnity clause usually works by defining the parties, the type of loss covered, the event that triggers compensation, and the process for making a claim. The party giving indemnity is often called the indemnifier. The party receiving protection is the indemnified party.
A practical clause should clearly cover:
• Triggering events: breach of contract, fraud, negligence, non-compliance, third-party claims, data breach, IP infringement, tax liability, or product failure.
• Scope of losses: direct losses, damages, penalties, settlement amounts, legal fees, investigation costs, and regulatory fines, if agreed.
• Claim process: how notice must be given, what documents are required, and how disputes will be handled.
• Limits and exclusions: caps on liability, time limits, carve-outs for fraud or wilful misconduct, and excluded indirect losses.
• Control of defence: who handles legal proceedings when a third-party claim is involved.
Without these details, indemnity can become either too broad for the indemnifier or too weak for the party that needs protection.
Suppose a software vendor provides a payment or expense management system to a company. The vendor promises that its software does not infringe any third party's intellectual property. Later, another company files a claim alleging that the software violates its copyright or patent rights. If the contract includes a strong IP indemnity clause, the vendor may have to compensate the buyer for legal costs, settlement amounts, and related losses covered under the contract.
Another common example is vendor non-compliance. If a payroll vendor fails to comply with applicable labour or tax requirements and the client receives a penalty because of the vendor's mistake, an indemnity clause may allow the client to recover the loss from the vendor.
This is why businesses should not treat indemnity as standard boilerplate. The same clause can have very different financial impact depending on whether it covers third-party claims only, direct claims also, legal expenses, regulatory penalties, or consequential losses.
Indemnity matters because it gives businesses clarity before a dispute happens. It helps both parties understand who is responsible for specific risks and prevents every loss from becoming a negotiation after the fact.
Businesses should review indemnity clauses carefully because:
• Overly broad indemnities can create open-ended liability.
• Weak indemnities can leave the business exposed even when the other party caused the loss.
• Unclear wording can lead to disputes over whether a loss is covered.
• Missing caps, exclusions, or timelines can make financial exposure difficult to estimate.
• Indemnity must align with insurance coverage, liability limits, and commercial value of the contract.
A useful way to evaluate indemnity is to ask: what can realistically go wrong in this relationship, who controls that risk, and who should pay if it materialises? The best indemnity clauses follow that logic instead of using generic legal language.