Home/Software in Deal Valuation/Reps and Warranties
Software in Deal Valuation

Reps and warranties for software licensing

A licensing warranty is only as good as the disclosure behind it and the indemnity beside it. Here is how buyers use reps and warranties to allocate inherited software risk to the party that created it.

Reps and warranties for software licensing are how a buyer allocates inherited software risk to the party that created it, but only within the limits the buyer negotiates. A licensing warranty is a statement by the seller that the estate is properly licensed, not under audit, and transferable, backed by a remedy if it proves untrue. That protection is only as good as the disclosure behind it and the indemnity beside it. A warranty hollowed out by qualifiers, or undercut by broad disclosure, can leave the buyer carrying the very exposure it was meant to cover.

What reps and warranties for software licensing cover

The core licensing protections are a handful of specific provisions. A compliance warranty states that the estate is licensed for its actual use. A no audit warranty states that no publisher audit is pending or threatened. A transferability warranty states that the licences survive the deal structure, which matters because change of control and anti assignment clauses can trigger consent, termination, or repricing depending on whether the deal is a stock purchase, asset purchase, merger, or carve out. Together they put the seller on record about the software position.

The protection these warranties offer depends entirely on their breadth and qualifiers. A clean, unqualified compliance warranty is strong. The same warranty narrowed by a knowledge qualifier, so it only bites if the seller actually knew of the breach, or by a materiality threshold, is far weaker. Buyers press for breadth precisely because inherited licensing exposure is usually latent and unquantified, which means the seller may genuinely not know of it, and a knowledge qualifier would then leave the buyer unprotected against exactly the risk that matters most.

How a licensing warranty protects the buyerFlow diagram showing the licensing warranty, the disclosure schedule, the indemnity and the cap and survival period combining into allocated software risk.How a licensing warranty protects the buyerLicensing compliance warrantyDisclosure scheduleSpecific indemnityCap and survival periodRisk allocatedto the seller
A licensing warranty works with the disclosure schedule and indemnity. Together they allocate inherited software risk to the seller within agreed limits.

Why the disclosure schedule decides the protection

The disclosure schedule is where warranties are quietly undone. Anything the seller discloses against a warranty is carved out of it, becoming risk the buyer is treated as having accepted. A seller who discloses a known licensing issue has shifted that issue onto the buyer even though the warranty appears to cover it. This is why the disclosure schedule deserves as much scrutiny as the warranties themselves, tested against the buyer's own independent findings from software spend diligence.

The practical discipline is to reconcile what the seller discloses against what the buyer has found. Where the buyer's diligence has surfaced an exposure the seller has not disclosed, the warranty should cover it. Where the seller discloses an issue the buyer had not found, that disclosure is a flag to quantify the exposure and price it in, as covered in negotiating software risk allocation in the SPA. The table summarises the provisions and where the buyer should focus.

Reps and warranties that address software licensing
ProvisionWhat it coversBuyer focus
Compliance warrantyEstate is licensed for its useBreadth and knowledge qualifiers
No audit warrantyNo pending or threatened auditDisclosure of vendor contact
Transferability warrantyLicences survive the deal structureChange of control and assignment
Disclosure scheduleKnown issues carved outScrutinise what is disclosed away
Specific indemnityIdentified exposure coveredDollar one cover, no basket

When a specific indemnity does more than a warranty

Where a specific exposure is already identified, a general warranty is rarely the best protection. A warranty gives a remedy for breach, but the remedy may be capped, subject to a basket, qualified by knowledge, or disputed when the claim arrives. A specific indemnity tailored to the identified exposure, ideally with dollar one cover and no basket, gives the buyer a cleaner path to recovery. The mechanics of indemnities are set out in software licensing indemnities explained.

The choice between relying on a warranty and securing a specific indemnity turns on certainty. For unknown, latent risk a broad warranty is the right tool, because it covers what diligence has not yet found. For a known, quantified exposure a specific indemnity is stronger, because it removes the qualifiers and caps that a general warranty might carry. Many deals use both, and some layer warranty and indemnity insurance over the top, as covered in warranty and indemnity insurance and software risk.

The transferability warranty deserves particular attention in the software context, because deal structure changes which clauses bite. Change of control and anti assignment clauses can trigger consent, termination, or repricing, and whether they do depends on whether the transaction is a stock purchase, an asset purchase, a merger, or a carve out. A warranty that the licences survive the deal is only meaningful if it is tested against the actual structure and the actual contracts, which is why the buyer pairs the warranty with a review of the key agreements rather than relying on the statement alone.

The stakes behind the drafting

The reason this drafting matters is the scale of what a licensing warranty is protecting 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. A warranty that fails to bite on an exposure of that order, because of a knowledge qualifier or a broad disclosure, leaves the buyer exposed to a claim that can break the deal economics. The drafting is not a formality; it is the line between recourse and absorption.

Because reps, warranties, and indemnities are contractual instruments, their drafting, caps, baskets, and survival periods are legal questions. This page is commercial and licensing advisory on what the buyer should look for in the software dimension, not legal advice. Engage your own counsel to interpret and negotiate the provisions, supported by the quantified software findings the diligence provides, so the legal protections are built on an accurate picture of the exposure.

Key takeaways

  • Reps and warranties for software licensing allocate inherited software risk to the seller, but only within the limits the buyer negotiates.
  • A warranty is only as strong as its breadth and the knowledge qualifiers that narrow it.
  • Anything disclosed in the disclosure schedule is carved out of the warranty, so disclosure deserves close scrutiny.
  • Where a specific exposure is known, a specific indemnity with dollar one cover protects better than a general warranty.

Recommendations for buyers

  1. Press for broad, unqualified warranties. Resist knowledge and materiality qualifiers that hollow out a licensing compliance warranty.
  2. Scrutinise the disclosure schedule. Anything disclosed is risk the buyer accepts, so test each disclosure against your own findings.
  3. Use specific indemnities for known issues. A general warranty rarely covers an identified exposure as well as a tailored indemnity does.
  4. Engage your own counsel. Warranty drafting, caps and survival are legal questions, so have your counsel interpret and negotiate them.

Reps and warranties for software licensing sit within software in deal valuation, alongside indemnities, risk allocation in the SPA, and warranty and indemnity insurance. Engage your own counsel for legal interpretation of any contract, clause, or claim.

Frequently asked questions

What are reps and warranties for software licensing?
They are contractual statements by the seller about the software estate, such as that it is properly licensed, not under audit, and transferable, backed by a remedy if they prove untrue. They allocate inherited software risk between buyer and seller.
How strong is a licensing compliance warranty?
Only as strong as its breadth and qualifiers. A warranty narrowed by knowledge and materiality qualifiers, or undercut by broad disclosure, offers far less protection than a clean, unqualified statement backed by indemnity.
Why does the disclosure schedule matter?
Because anything the seller discloses is carved out of the warranties, so it becomes risk the buyer accepts. Scrutinising the disclosure schedule against independent findings is essential to know what protection actually remains.
When is a specific indemnity better than a warranty?
When a particular exposure is already identified, a specific indemnity, ideally with dollar one cover and no basket, protects the buyer more reliably than a general warranty that may be capped, qualified, or disputed.
Is this legal advice?
No. This is commercial and licensing advisory. Warranty drafting, caps, survival periods and indemnities are legal questions, so engage your own counsel for interpretation and negotiation of any provision.

Request a confidential software M&A risk assessment

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