What Is Latent Licensing Liability?

What is latent licensing liability? Latent licensing liability is the software exposure a buyer inherits that no one has measured: a shortfall against an entitlement, an indirect access claim, or a contract term that repriced on change of ownership. It is latent because standard due diligence does not reconcile entitlement against usage, so the liability sits unseen on the balance sheet of risk until a publisher audit makes it real. In software M&A it is the single most common source of an eight figure surprise after a deal closes.

Why latent licensing liability is dangerous in M&A

The danger is timing. The liability is invisible at signing and arrives after close, when the buyer owns it in full and has the least leverage. Publishers know that a change of ownership is the moment to audit, because the new owner has not yet built a defensible position. Two public proof points show the scale. As of June 2026, SAP pursued Anheuser Busch InBev for a reported 600 million dollars, and in SAP UK Ltd v Diageo Great Britain Ltd, 2017 EWHC 189 (TCC), the dispute over indirect access carried a reported 60 million exposure. Both illustrate inherited and disputed licensing surfacing as a claim.

Where latent licensing liability comes from

It comes from the gap between what a target is entitled to and what it actually runs, and from contract clauses that bite on a transaction. Common sources are deployment that exceeds entitlement, indirect or digital access that was never licensed, change of control clauses that allow repricing or termination, and unmerged duplicate agreements after an earlier acquisition. Each is quantifiable, but only if someone reconciles the position before the publisher does.

Turning latent liability into a known number

The remedy is to build the effective license position during diligence, size each gap for its worst case and likely settlement, and price the result into the deal or the protections. What was latent becomes a managed line item. This work is commercial and licensing advisory, not legal advice.

Common sources of latent licensing liability
Source	How it hides	When it surfaces
Deployment over entitlement	Never reconciled	Change of ownership audit
Indirect access	Usage through other systems	Publisher claim
Change of control clause	Buried in contract	On signing or close
Unmerged duplicate agreements	Legacy from prior deal	First renewal

Key takeaways

Latent licensing liability is inherited software exposure no one has quantified.
It stays hidden through standard diligence and surfaces as a post close audit.
Public proof points include a reported 600 million SAP claim against AB InBev as of June 2026.
It becomes manageable once the effective license position is built and each gap is priced.

Recommendations for buyers

Assume it exists. Treat every target as carrying unquantified licensing liability until reconciled.
Reconcile before signing. Build the effective license position so latent exposure becomes a known number.
Price or protect. Reflect the exposure in price, escrow holdback or indemnity rather than absorbing it after close.
Watch the tier one names. Oracle, SAP, Microsoft and IBM drive most change of ownership audits.

Related reading: see the M&A software glossary hub, plus indirect access and effective license position.

Frequently asked questions

What is the difference between latent and known licensing liability?

Known liability has been measured and priced. Latent licensing liability has not been quantified and sits hidden until an audit, which is why it carries the most deal risk.

Why do audits follow a change of ownership?

Publishers see new ownership as the moment a buyer is least prepared and most likely to settle, so a change of control often triggers an audit within the first year or two.

Can latent licensing liability be insured?

Representations and warranties insurance can cover some inherited claims, but only liabilities that have been identified and disclosed. Latent exposure that was never reconciled is typically excluded.

How large can latent licensing liability be?

Public disputes show the range. As of June 2026 SAP sought a reported 600 million dollars from AB InBev and a reported 60 million from Diageo over inherited and disputed licensing.

Request a confidential software M&A risk assessment.

Map and quantify the licensing exposure in your target or portfolio before it becomes a post close audit. Independent, buyer side, paid only by the acquirer.

Talk to a software M&A advisor