Indemnity, Liability Caps, and Liquidated Damages: Fixing Risk Allocation in Corporate Contracts (India)

Risk allocation clauses are the number one source of friction and surprise liability in Indian corporate contracts, especially around indemnity scope, liability caps, and liquidated damages. [3][1]

Quick Navigation

Why this hurts corporates

Vendors push broad indemnities with low caps, while buyers expect full indemnity with carve-outs from limitations, creating a structural standoff that delays deals and increases exposure. [5][3] Ambiguity over “consequential losses” and penalty-versus-liquidated-damages under Sections 73–74 leads to mispriced risk and post-breach disputes. [6][7][3] Indian law recognizes indemnity and damages distinctly, so mixing them in drafting without precision results in unenforceable remedies or unintended liability. [1][3]

Indemnity under Indian law (Sections 124–125)

Section 124 defines a contract of indemnity as a promise to save another from loss caused by the promisor or by any other person, setting the statutory baseline for indemnity scope. [8][9][1] Section 125 gives the indemnity-holder the right to recover damages paid in suits, costs reasonably incurred, and sums paid under compromise when acted prudently and within authority. [10][1] Unlike broader common law practice, Indian commentary notes Section 124 is narrower and focuses on loss caused by human conduct unless expanded by contract wording. [5]

  • Drafting tip: Expand indemnity to third-party IP claims, data breaches, and regulatory fines “to the extent caused by” the indemnifier’s acts or omissions.
  • [1]
  • Preserve indemnity despite liability caps for core risks like IP infringement, confidentiality breach, and wilful misconduct.
  • [1]
  • Add defense and settlement control: indemnifier to defend, indemnified to approve settlements that admit liability or impose ongoing obligations.
  • [1]

Limitation of liability: caps and exclusions

A liability cap limits monetary exposure (for example, fees paid in the last 12 months), but carve-outs are standard for indemnity, confidentiality, data protection, IP infringement, and wilful misconduct. [7][3] Exclusions of consequential, special, incidental, or indirect damages are common, yet parties often dispute whether lost profits or data loss are “consequential” or “direct,” so precise definitions are essential. [3][6][7] To avoid nullifying negotiated risk, state that the cap does not apply to specified carve-outs, while other claims remain subject to the aggregate cap and agreed exclusions. [7][3]

[3][7]

Liquidated damages and penalties (Sections 73–74)

Section 73 provides for compensation for losses that arise naturally or were contemplated by the parties, which are assessed by the court if not pre-agreed. [6][3] Section 74 allows reasonable compensation not exceeding the stipulated sum when a contract specifies liquidated damages or a penalty, without strict proof of actual loss but subject to judicial scrutiny. [11][7][3] Practical drafting should tie pre-estimates to measurable business metrics and remove punitive language to enhance enforceability under Section 74. [11][3]

  • Use evidence‑backed pre‑estimates for SLAs and delivery delays to fit within “reasonable compensation” under Section 74.
  • [11][3]
  • Avoid duplicative remedies: clarify that liquidated damages are exclusive for SLA breaches but do not limit indemnity for third‑party claims.
  • [3]
  • State that LDs count toward the aggregate cap unless expressly carved out, to prevent unintended unlimited exposure.
  • [7][3]

Negotiation playbook: balanced risk allocation

[fusion_accordion_item title=”1) Indemnity scope and triggers” open=”yes”]

Define triggers (IP, data breach, confidentiality, regulatory fines), fault standard (“to the extent caused by”), and process (defense, tender of claim, settlement control).

[5][1] [/fusion_accordion_item] [fusion_accordion_item title=”2) Cap, carve‑outs, and exclusions” open=”no”]

Set a commercially grounded cap, carve out indemnity and wilful misconduct, and define excluded damages with examples to avoid interpretive gaps.

[7][3] [/fusion_accordion_item] [fusion_accordion_item title=”3) LDs vs actual damages” open=”no”]

Use liquidated damages for SLA breaches with reasonable pre‑estimates under Section 74, and preserve Section 73 claims for other breaches if LDs are inapplicable.

[6][11][3] [/fusion_accordion_item] [fusion_accordion_item title=”4) Interface of clauses” open=”no”]

Clarify that indemnity recoveries may include certain lost profits or data restoration costs even if “consequential” elsewhere, if the parties so intend.

[3][7] [/fusion_accordion_item]

FAQs

Not by default; state expressly that indemnity obligations are uncapped or subject to a higher super‑cap, while ordinary breach claims stay within the aggregate cap.

[7][3]

Courts can award reasonable compensation not exceeding the stipulated sum even without strict proof of actual loss under Section 74, but the amount must be a genuine pre‑estimate.

[11][3][7]

Commentary notes Section 124 focuses on loss caused by the promisor or other persons, so extend scope by drafting if you want coverage for events like system failures or force majeure‑adjacent risks.

[5]

Need a risk‑balanced contract?

Get a redline‑ready playbook for indemnity, caps, exclusions, and LDs tailored to your deal type and industry, aligned to the Indian Contract Act framework. [1][3] Use the anchor buttons above to jump to any section, or add anchors to your menu for one‑page navigation in Avada. [4][12][2]

[/fusion_builder_column]
Published On: October 30th, 2025 / Categories: Contract Law /

Subscribe To Receive The Latest News

Join 500+ business professionals receiving expert legal insights directly in their inbox.

Read our Privacy Policy here.