Liability Cap Clause in India

Why liability caps matter

Business contracts create obligations. If those obligations are breached, the other party may claim losses. In Indian contract law, compensation for breach is generally connected to losses arising naturally from the breach or losses that the parties knew were likely when the contract was made. However, in real disputes, the claimed loss may be much higher than the contract value. For example, a marketing agency may miss a campaign deadline. A software vendor may delay a feature release. A consultant may provide incorrect implementation support. A SaaS provider may suffer downtime. A logistics vendor may lose goods. A contractor may disclose confidential information. A client may claim not only the fee paid but also lost revenue, lost customers, reputational damage, replacement costs, internal time, and consequential losses. A liability cap helps avoid open-ended exposure. It tells the parties in advance that liability is limited to a defined amount, such as fees paid under the contract, fees paid in the preceding six or twelve months, a fixed amount, the value of the affected SOW, or insurance proceeds. The cap gives commercial certainty and allows pricing to reflect risk.

Common types of liability caps

The most common cap is a fee-based cap. For example, liability may be limited to the amount paid under the agreement in the six months or twelve months preceding the claim. This works well for ongoing service relationships because the cap adjusts with the commercial value of the engagement. Another option is a fixed rupee cap. This may be useful where the contract value is clear and the parties want certainty. For project-specific work, the cap may be linked to the fees payable under the relevant Statement of Work rather than the entire master agreement. Some contracts use a multiple of fees, such as one times, two times, or three times the amount paid. This may be appropriate where the client wants greater protection and the service provider can price that risk. Some contracts also align liability with insurance coverage, although this should be used carefully because insurance exclusions may not match contractual obligations.

Direct, indirect, and consequential losses

A liability clause should address the type of damages being limited or excluded. Many contracts exclude indirect, consequential, incidental, special, punitive, or exemplary damages. These terms are often copied from international templates without thinking about how they will be argued in an Indian dispute. The better approach is to make the clause commercially clear. If the parties do not intend to cover lost profits, loss of business, loss of goodwill, loss of anticipated savings, loss of data, loss of revenue, business interruption, or reputational harm, the clause should say so. If some of these losses should be recoverable for specific breaches, such as confidentiality or data misuse, the clause should create exceptions. The drafting should also avoid contradiction. A contract cannot say that all indirect losses are excluded, then elsewhere say that the indemnity covers all losses without limitation, unless that is intentional and clearly structured.

What should be excluded from the cap

Not every liability should be capped. Clients often ask for uncapped liability for fraud, wilful misconduct, intentional breach, gross negligence, breach of confidentiality, IP infringement, data protection breaches, payment obligations, and indemnity claims. Service providers often resist broad exclusions because they can swallow the cap entirely. The right exclusions depend on the transaction. In a software development agreement, IP infringement and confidentiality may deserve stronger protection. In a SaaS agreement, data security and privacy may be major concerns. In a consulting agreement, professional negligence and reliance may matter. In a vendor agreement, injury, property damage, statutory violation, or third-party claims may be important. A good clause distinguishes between ordinary service failure and serious misconduct or protected-risk categories. The cap should not be so narrow that the service provider remains exposed for everything. It should not be so broad that the client has no meaningful remedy for serious harm.

Relationship with indemnity

Liability caps and indemnity clauses must be read together. Indemnity usually deals with specific claims, often third-party claims or defined losses. A liability cap decides the maximum financial exposure. If the contract says indemnity is uncapped, the liability cap may not protect the indemnifying party for those indemnity claims. If the contract says all claims including indemnity are capped, the client may have limited recovery even for third-party IP claims. This is why the drafting should expressly state whether the cap applies to indemnity. It should also state whether some indemnities are uncapped and others are capped. For example, tax indemnity, confidentiality breach, and IP infringement may be treated differently from ordinary service breach.

Indian legal context

The Indian Contract Act, 1872 is central to damages and breach analysis. Section 73 deals with compensation for loss or damage caused by breach of contract. Section 74 deals with compensation where the contract names a sum to be paid for breach or contains a penalty-like stipulation. Indian courts have considered the difference between genuine pre-estimates, reasonable compensation, and penalties in several cases. A liability cap is not exactly the same as a liquidated damages clause. A liquidated damages clause pre-estimates what the breaching party must pay. A liability cap sets the ceiling on liability. However, both clauses relate to monetary consequences of breach and should be drafted with care. A cap should be reasonable in context, transparent, and not hidden in a way that creates unfair surprise. In business-to-business contracts, courts generally respect commercial allocation of risk when the parties are competent and the contract is clear. But unclear clauses invite interpretation disputes. If the cap is scattered across multiple clauses, contradicted by the indemnity, or inconsistent with the SOW, the protection may become uncertain.

Liability caps in SaaS and technology contracts

Technology contracts need special attention. SaaS providers often cap liability at subscription fees paid in the preceding twelve months. They may exclude downtime losses, lost data, lost profits, and business interruption. Clients may request higher caps for data breach, confidentiality, IP infringement, and security obligations. The contract should also address service credits. If downtime occurs, are service credits the sole remedy, or can the client also claim damages? If service credits are the exclusive remedy, the clause should be clear. If major breaches allow termination or damages, that should also be stated. For software development contracts, the liability clause should be connected to acceptance testing, warranties, bug-fix obligations, third-party libraries, open-source components, and handover responsibilities. A simple generic cap may not be enough.

Liability caps in agency and consulting contracts

Agencies and consultants often operate on limited fees but face broad expectations. A client may blame a consultant for business failure or a campaign result that depends on many variables outside the consultant's control. The liability clause should make clear that the service provider is responsible for agreed services, but not for guaranteed commercial outcomes unless expressly promised. For marketing, branding, design, financial consulting, HR consulting, and strategic advisory work, the contract should avoid open-ended warranties. It should also include client responsibility for approvals, legal compliance of claims, platform policies, budgets, and implementation decisions.

Common drafting mistakes

Common mistakes include using a cap without exclusions, excluding too many claims from the cap, failing to say whether indemnity is capped, using a cap that conflicts with insurance, excluding consequential losses while also promising broad indemnity, applying one cap to all SOWs without thinking about project value, and failing to define the time period for calculating fees. Another mistake is using a liability cap that is commercially unrealistic. A cap of INR 10,000 in a high-risk technology contract may not be acceptable. Unlimited liability for a small consulting fee may also be unrealistic. The clause should reflect negotiation, not blind copying.

How Inamdar Legal can assist

Inamdar Legal assists with drafting and reviewing liability cap clauses in service agreements, MSAs, SaaS contracts, vendor agreements, software contracts, consulting agreements, logistics terms, and agency agreements. We identify whether the cap protects the right party, whether exclusions are appropriate, whether indemnity conflicts with the cap, and whether the clause is commercially aligned with the transaction.

When to Review This

• Overall and claim-specific liability caps
• Exclusions for fraud, IP, confidentiality, and data misuse
• Direct, indirect, and consequential loss wording
• Risk allocation for Indian commercial contracts