The TSA liability cap decides who pays for failure.

Section 01

Why the cap matters more than it looks.

A TSA is a short service contract, but the harm a failure can cause is out of proportion to the modest fees the seller earns. If seller payroll runs late, if a finance system is unavailable at period close, or if a migration slips past a deadline, the cost to the buyer can dwarf a few months of service charges. The liability cap decides how much of that cost the seller actually carries.

Sellers almost always propose a cap tied to fees paid under the TSA, sometimes a single month or the total over the term. From the seller view this is reasonable, because the service is low margin and the seller does not want open ended exposure for a function it is exiting. From the buyer view, a cap set at one month of fees can leave the seller indifferent to a failure that costs the buyer far more.

The negotiation is therefore about closing the gap between the fees the seller earns and the harm a failure can cause. The buyer does not need unlimited liability across the board, but it needs the cap high enough that the seller has a real incentive to perform, and it needs the most damaging failures placed outside the cap entirely.

A buyer approaches the clause with a clear view of which failures would actually hurt, then negotiates the cap and the carve-outs to match that risk rather than accepting a number disconnected from the consequences.

Section 02

Setting the cap at the right level.

The starting question is what the cap is a multiple of. A cap expressed as total fees paid over the TSA term gives more headroom than one month of fees, and a cap expressed as an absolute amount avoids the problem of a low fee service carrying a low cap despite high underlying risk. The buyer pushes for whichever basis produces a meaningful number for the services that matter most.

Different services warrant different treatment. A payroll service whose failure can trigger employee and regulatory consequences justifies a higher cap than a low risk administrative service. The buyer can negotiate service specific caps rather than one blanket figure that flatters the riskiest functions.

The buyer also watches how the cap interacts with service credits. A seller may argue that service credits are the buyer sole remedy for performance failures, which can leave the buyer with a small credit against a large loss. The buyer keeps service credits as a minimum, not as a ceiling that displaces the right to claim.

The aim is a cap that is realistic for a service business to accept yet high enough that the seller treats the buyer deadlines as real obligations rather than soft targets it can miss without consequence.

Section 03

The carve-outs that belong outside the cap.

The most important buyer protections are the categories of liability that sit outside the cap altogether. A breach of confidentiality, a failure of data security, infringement of intellectual property, and loss caused by fraud, gross negligence, or wilful misconduct are commonly excluded from the cap because the harm and the culpability are both high.

Data and security carve-outs deserve particular attention in a TSA, because the seller is processing the buyer data in shared systems during the very period when the buyer cannot yet defend it alone. A buyer that lets a data breach sit under a low fee based cap has accepted that the most damaging realistic failure is also the least compensated.

A buyer can also negotiate a higher separate cap for data and security incidents rather than a full exclusion, which gives the seller a known ceiling while still sizing the protection to the risk. The choice between a carve-out and a higher sub cap is a negotiation, but leaving these categories under the general cap is rarely acceptable.

The buyer lists the carve-outs deliberately and resists a seller draft that quietly folds data, confidentiality, or IP back under the general cap, because that is where the real exposure lives.

Section 04

Indirect loss and the exclusion clause.

Alongside the cap, sellers exclude categories of loss entirely, typically indirect or consequential loss and sometimes specific heads such as lost profit or business interruption. The buyer reads these exclusions closely because a broad exclusion of consequential loss can strip out much of the harm a separation failure actually causes.

The drafting matters because the line between direct and indirect loss is not always obvious. A buyer ensures that the losses it most fears, such as the cost of standing up a replacement service quickly or the cost of a missed migration deadline, are treated as recoverable direct loss rather than excluded as consequential.

The interaction with the indemnities also needs care. If the TSA contains indemnities for matters such as data breach or third-party claims, the buyer confirms whether those indemnities sit inside or outside the cap and the exclusions, because an indemnity that is then capped and stripped of consequential loss may deliver far less than it appears to promise.

Reading the cap, the exclusions, and the indemnities together is the only way to know what protection the buyer actually holds. Each clause limits the others, and a strong number in one can be undone by a quiet limitation in another.

Section 05

Getting the clause right before signing.

Liability terms are far easier to fix before signing than after. While the deal is live the buyer has leverage, because the seller wants the transaction to close. Once the TSA is signed the buyer is asking for a concession with nothing to trade, so the limitation of liability belongs on the pre-signing checklist, not the post-close wish list.

The buyer approaches the clause as a package. It sizes the cap to the services that matter, keeps service credits as a floor rather than a ceiling, places data, confidentiality, IP, and wilful misconduct outside the cap, and protects the direct losses it most fears from a broad consequential loss exclusion.

None of this requires the seller to accept unlimited liability for a service it is exiting. It requires the cap and the carve-outs to reflect the real distribution of risk, so the party best placed to prevent a failure carries its consequences.

A disciplined buyer settles these terms as part of a pre-signing review, alongside scope and pricing, while it still holds the leverage to move the numbers.

FAQ

Questions buyers ask about the cap.

Where should a TSA liability cap be set?

Push for a cap expressed as total fees over the term or as an absolute amount rather than a single month of fees, and negotiate higher caps for high risk services such as payroll. The cap should be high enough that the seller treats the buyer deadlines as real obligations.

What should sit outside the liability cap?

Confidentiality breaches, data security failures, intellectual property infringement, and loss from fraud, gross negligence, or wilful misconduct are commonly carved out of the cap. Data and security in particular warrant a carve-out or a higher separate sub cap because the harm is large.

Are service credits the buyer only remedy?

They should not be. Sellers may argue service credits are the sole remedy for performance failures, which can leave a small credit against a large loss. The buyer keeps service credits as a minimum and preserves the right to claim beyond them.

Why negotiate the cap before signing?

Before signing the buyer has leverage because the seller wants the deal to close. After signing the buyer is asking for a concession with nothing to trade. The limitation of liability belongs on the pre-signing checklist alongside scope and pricing.

Related Reading

More on TSA clause negotiation.