All terms

Glossary

Limitation Of Liability Clause: What is limitation of liability clause?

A limitation of liability clause caps or excludes the damages one party can recover from the other after a breach.

A limitation of liability clause caps how much one party can be required to pay the other if something goes wrong under the contract. It is the most-negotiated term in enterprise contracts globally, and has held that position for over a decade.

#1
Most-negotiated contract term globally for over 10 years. The most common cap is 1x annual fees paid; only 1% of enterprise contracts have unlimited liability, and 20-30% include an elevated 'super cap' of 2-5x for high-risk breaches.
World Commerce & Contracting Most Negotiated Terms 2024 (937 respondents); industry research on enterprise SaaS contract caps.
TL;DR
  • Caps how much one party can be required to pay the other if something goes wrong.
  • 1x annual fees is the most common cap; 20-30% of contracts include a 2-5x 'super cap' for specific high-risk breaches.
  • Carve-outs (IP indemnity, data breach, willful misconduct, payment) are often excluded from the cap.
  • Vallor reads every contract and flags any cap, carve-out, or exclusion that diverges from your playbook.

Anatomy of limitation of liability clause

Sample clause — enterprise services agreement
7. LIMITATION OF LIABILITY. (a) GENERAL CAP. Each party's aggregate liability under this Agreement shall not exceed 1the fees paid or payable in the twelve (12) months preceding the claim. (b) SUPER CAP. The cap in (a) shall be increased to 2three times (3x) the fees for claims arising from 3breach of confidentiality, data security obligations, or gross negligence. (c) EXCLUSIONS. The caps in (a) and (b) shall not apply to 4IP indemnification, payment obligations, or willful misconduct. (d) DAMAGES. 5Consequential, indirect, and lost-profits damages are excluded except for breach of confidentiality.
1
General capUsually 1x annual fees in enterprise SaaS. Watch the language: 'paid' vs 'payable' matters.
2
Super capHigher cap (typically 2-5x) for specific high-risk breaches. 20-30% of contracts have one.
3
Super cap triggersMost common: confidentiality, data security, gross negligence. Defines when the bigger cap applies.
4
ExclusionsCommon carve-outs: IP indemnification, payment, willful misconduct. These have no cap at all.
5
Damages exclusionConsequential and lost-profits are usually excluded. Carve-outs reciprocally apply to confidentiality breaches.

How Vallor handles limitation of liability clause

1
Extract the full cap structure from every contractVallor pulls general cap, super cap, triggers, carve-outs, and damages exclusions into structured fields, with the source language cited.
2
Compare each contract to your playbookVallor flags any cap or carve-out that diverges from your preferred position, with the gap explained in plain language.
3
Surface the portfolio risk profileAggregate view: which contracts have the highest exposure, which lack super caps for data breach, which exclude payment obligations from the cap.
4
Pre-negotiation brief at renewalBefore any renewal, Vallor shows the current cap position, the playbook delta, and recommended renegotiation targets.

Where teams trip up

Cap calibrated to one year of fees but multi-year obligationsA 1x annual cap on a 5-year contract creates lopsided exposure. Multi-year deals often need explicit anchoring.
Forgetting reciprocityBuyer-side teams sometimes accept asymmetric caps without realizing it. Symmetric caps protect both directions.
Mixing up 'paid' and 'payable'Two different numbers in a year-one breach scenario. The vendor prefers 'paid'; the buyer prefers 'payable'.
Ignoring the damages exclusionCapping liability is one thing. Excluding consequential damages can leave the buyer with no remedy for downstream harm.

See also

FAQ

What is a 'super cap' in a limitation of liability clause?

An elevated cap that applies to specific high-risk categories, typically 2-5x the general cap. Common triggers include data breach, confidentiality, and gross negligence. 20-30% of enterprise contracts include one.

Should the cap be on fees 'paid' or 'payable'?

Vendor-side prefers 'paid' (only what has actually been invoiced). Buyer-side prefers 'payable' (total contract value). The numbers diverge significantly in year-one breach scenarios.

Are IP indemnification claims subject to the liability cap?

Usually no. IP indemnification is the most common carve-out from the cap, meaning IP-related claims can exceed the cap amount. Negotiating this is a top-five MSA discussion.

What is the most common liability cap structure in enterprise SaaS?

1x annual fees as the general cap, with a 2-5x super cap for specific categories (data breach, confidentiality, gross negligence) and uncapped exposure for IP indemnification, payment obligations, and willful misconduct.

How does Vallor help with liability caps?

Vallor extracts the full cap structure from every contract in your portfolio, compares each to your playbook, and surfaces the highest-exposure contracts and the most common gaps to your preferred position.

Last updated: 2026-05-21. Part of Vallor's contract intelligence glossary.