When a publisher audit lands after close, the indemnity decides who pays. Here is how buyers structure software licensing indemnities so an inherited true up demand falls back on the seller, not the return.
Software licensing indemnities explained comes down to one question: when a publisher audit lands after close, who pays? An indemnity is the seller's contractual promise to cover the buyer for defined software licensing losses, such as an inherited true up settlement, so the cost of pre close exposure does not fall on the buyer and the return. But an indemnity is only as useful as its trigger, scope, limits, and survival, and each of those has to line up with how a licensing demand actually arrives. A well drafted indemnity protects the deal; a poorly drafted one protects only on paper.
A licensing indemnity has to do four things to be useful. It needs a trigger that matches how the loss arises, a scope that covers the full cost, limits sized to the exposure, and a survival period long enough to outlast the risk. Get any one wrong and the indemnity can exist while still leaving the buyer carrying the demand. Because inherited licensing exposure is usually latent and unquantified, surfacing as an audit after close, the indemnity is often the buyer's main recourse for a risk that diligence flagged but could not eliminate.
The trigger is where many indemnities fail the buyer. If cover only activates on a final court judgment, it is largely useless, because most licensing exposure resolves through negotiated settlement with the publisher, not litigation. The buyer wants the trigger to include a publisher audit demand or a settlement, so the indemnity responds to the event that actually happens. This is the single most important term to get right, because it determines whether the indemnity ever pays at all.
Scope determines what counts as a covered loss. The real cost of a true up extends well beyond the headline licence price to include the settlement, back maintenance, additional licence fees, and associated costs, so the indemnity should be scoped to the full cost to cure rather than the list price alone. The method for sizing that cure cost is set out in quantifying cost to cure for the deal model, and the indemnity should be drafted to match it.
Caps, baskets, and survival then decide how much is actually recoverable. A cap below the quantified exposure leaves the excess with the buyer. A high basket, the threshold a claim must exceed before anything is recoverable, can absorb a real demand entirely, so for a known exposure the buyer presses for a low or zero basket. Survival, the period the indemnity remains in force, must outlast the audit window, because a change of control can prompt a review months after close. The table sets out the terms and the buyer's position on each.
| Term | What to watch | Buyer position |
|---|---|---|
| Trigger | What event activates cover | Audit demand, not just a court judgment |
| Scope of loss | Settlement, back maintenance, fees | Cover the full cost to cure |
| Cap | Maximum recoverable | Sized to the quantified exposure |
| Basket | Threshold before any claim | Low or zero for known exposure |
| Survival | How long cover lasts | Long enough to outlast the audit window |
For a known, identified exposure, a specific indemnity protects the buyer far better than reliance on a general one. A general indemnity covers a broad class of losses but is more easily capped, qualified, or disputed when a particular demand arrives. A specific indemnity, tailored to the identified licensing exposure with a low or zero basket, removes the ambiguity and gives a clean path to recovery. The relationship between indemnities and the underlying warranties is set out in reps and warranties for software licensing.
The choice of indemnity also interacts with how the risk is allocated across the whole agreement. Where the exposure is large or uncertain, an indemnity may sit alongside an escrow or a holdback, so funds are available to meet a claim, as covered in escrow and holdbacks for licensing risk. The overall allocation is negotiated in the agreement, as set out in negotiating software risk allocation in the SPA.
The effort that goes into a licensing indemnity is justified by the size of what it protects against. In publicly reported disputes SAP pursued AB InBev for a reported 600 million dollars and Diageo for a reported 60 million over disputed and inherited licensing, as of June 2026. An indemnity that fails to respond to a demand of that order, because its trigger was too narrow or its survival too short, leaves the buyer absorbing a loss large enough to break the deal. The negotiation over a few words in the trigger clause can be worth more than the rest of the agreement combined.
Because indemnities are contractual instruments, their drafting and interpretation are legal questions. This page is commercial and licensing advisory on what the buyer should secure in the software dimension, informed by a quantified view of the exposure, not legal advice. Engage your own counsel to draft and negotiate the indemnity, and consider whether warranty and indemnity insurance, covered in warranty and indemnity insurance and software risk, should sit over the top. The quantified findings come from software spend diligence.
Software licensing indemnities explained sits within software in deal valuation, alongside reps and warranties, escrow and holdbacks, and risk allocation in the agreement. Engage your own counsel for legal interpretation of any contract, clause, or claim.
Tell us where the deal stands. We respond within one business day with a scoped, buyer side engagement that protects the value you underwrote.
Book a confidential call