An unquantified licensing gap does not reduce the headline price at signing, but it reduces the value the buyer receives. Here is how latent liability erodes enterprise value, and how buyers protect the number.
Latent liability and enterprise value impact describes the gap between the enterprise value a buyer agrees to pay and the value that survives once inherited software exposure is quantified. Inherited software licensing exposure is usually latent and unquantified in standard due diligence, which means it does not appear in the model, the working capital schedule, or the reps and warranties, yet it sits inside the target ready to surface as a publisher audit after close. When it does, the cost to cure lands directly against the value the buyer underwrote. This page explains how latent liability erodes enterprise value, why it is so often missed, and how the buyer protects the number through pricing, reps and warranties, and indemnity.
Enterprise value rests on a view of normalised earnings and a clean balance sheet. A latent licensing liability undermines both. It is a real obligation that has not yet crystallised, so it does not reduce the headline number at signing, but it reduces the value the buyer actually receives. The publisher holds a contractual right to true up the position, and the buyer inherits that exposure on the day it takes control. A model that treats the target software estate as compliant is overstating enterprise value by the full cost to cure, plus the cost of the disruption an audit brings to management and operations.
The reason the liability stays latent is structural. Standard financial and legal due diligence reviews contracts and spend, but rarely reconciles actual deployment against entitlement at the level the major publishers measure. The shortfall hides between the contract on the shelf and the software running in production. Until someone counts both sides, the exposure is a worry rather than a figure, and a worry never makes it into the enterprise value bridge. The result is a deal model that looks precise but rests on an untested assumption of compliance.
Once control passes, the exposure does not stay still. Change of control and anti assignment clauses can trigger consent, termination, or repricing, and the deal structure decides which clauses bite. A stock purchase carries the agreements across with their existing terms, while an asset purchase or carve out can require fresh consents that the publisher prices on its own terms. Either way, the buyer now owns the gap. The settlement that follows is the cost to cure, and it is paid from the value the buyer thought it had acquired rather than from the seller who has already been paid.
The scale is not theoretical. 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. Those figures show how far a latent position can travel once a publisher pursues it. A buyer that underwrote enterprise value without quantifying that exposure would have overpaid by the full settlement, and would have had no contractual protection in place to recover it from the seller after close.
| Element | Effect on enterprise value | Where it is captured |
|---|---|---|
| Licence shortfall | Direct reduction in value received | Price adjustment or escrow |
| Back maintenance | Compounds over the unlicensed period | Cost to cure model |
| Non compliance uplift | Lifts the settlement above list | Indemnity and reps |
| Audit disruption | Management time and remediation cost | Integration plan |
| Repricing on consent | Higher run rate after close | Synergy and run rate model |
The same quantified figure that reduces the enterprise value bridge also drives the protection. It can be priced into the consideration, as set out in pricing software exposure into the purchase price, supported by reps and warranties for software licensing, and backed by a specific software licensing indemnity. The cure cost itself is built using the method in quantifying cost to cure for the deal model.
Not every software liability is hidden. A disclosed liability, such as a known true up already in negotiation or a documented under deployment the seller has flagged, can be priced cleanly because both sides see it. A latent liability is more dangerous precisely because it is invisible to the model. It carries the same eventual cost but none of the warning, so it tends to surface at the worst time, after integration has begun and the buyer has lost the leverage that signing once gave it. The job of diligence is to convert the latent into the disclosed before the price is fixed.
That conversion changes the negotiation. A seller can wave away a general concern about licensing, but cannot easily dismiss a reconciliation that shows a named publisher, a measured deployment, and a defensible shortfall. The exposure stops being the buyer problem to absorb and becomes a shared issue to allocate. In practice this is where the enterprise value impact is either contained or lost, depending on whether the buyer brought a number or a worry to the table. The earlier the analysis runs, the more of the value the buyer keeps.
Latent liability also interacts with the rest of the valuation. Where the exposure affects normalised run rate spend rather than a one off cure, it belongs in the software licensing and EBITDA adjustments rather than only the purchase price. A clean separation between the one off cost to cure and the recurring run rate impact keeps the model honest and stops the same exposure being double counted or, worse, missed entirely.
The buyer cannot protect value it has not measured. Quantifying latent liability means reconciling deployment against entitlement for the publishers that carry the most audit risk, which are Oracle, SAP, Microsoft, IBM, and increasingly Broadcom for VMware, Salesforce, and ServiceNow. The output is a cost to cure with a central estimate and a range, expressed in the same currency as the deal model so it can be subtracted from enterprise value directly. A number framed this way changes the negotiation, because it converts an abstract risk into a line the seller must address rather than a footnote the buyer quietly absorbs.
Timing matters as much as method. The exposure is cheapest to handle before signing, when the buyer still controls the price and the agreement. After close, the same liability becomes a cost to cure with no counterparty to share it, since the seller has been paid and the publisher sets the terms. Bringing the analysis forward into diligence is the single most effective way to keep latent liability from eroding the enterprise value the buyer worked to model, and it costs a fraction of the exposure it protects against.
Latent liability and enterprise value impact sit within software in deal valuation, alongside pricing, EBITDA adjustments, and indemnity. The deployment and entitlement analysis behind the number comes from software spend diligence. Engage your own counsel for legal interpretation of any agreement 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