Latent licensing exposure does not stay off the model. It surfaces as a post close audit and lands on enterprise value, working capital, or the indemnity. Here is how buyers price it before they sign.
Understanding how software risk affects deal valuation starts with a simple fact: latent licensing exposure does not stay off the model. It surfaces after close, usually as a publisher audit, and it lands somewhere in the deal economics, on enterprise value, on working capital, or on the indemnity. Inherited and unquantified licensing exposure is exactly the kind of latent liability that standard due diligence misses, and the buyer who has not priced it carries it alone. This page sets out the channels through which that risk reaches the valuation, so it can be quantified before signing.
Software risk reaches the valuation through several distinct channels, and each is a path from an unquantified licensing position to a number in the model. Latent under licensing becomes a cost to cure when an audit converts it into a true up demand. Indirect access, where systems that are not directly licensed connect to and use licensed software, generates usage that a publisher can count and bill. Change of control terms can trigger consent, termination, or repricing, raising the run rate cost the buyer inherits. Lapsed or non transferable support becomes a reinstatement cost.
What these channels share is invisibility until counted. The financials of the target will not show the exposure, because nothing has crystallised it yet. The buyer who relies on the reported numbers is valuing the business as if the latent position did not exist, which is precisely the assumption a post close audit overturns. Mapping the channels is the work of software spend diligence, and it is what converts a hidden risk into a line in the model.
Once the channels are identified, each exposure has to be quantified as a cost to cure, the amount it would take to bring the estate into a compliant, defensible position. That number is what enters the valuation. The method for building it is set out in quantifying cost to cure for the deal model, and it is the bridge between a licensing finding and a valuation impact. Without a defensible number, the risk stays a footnote that the model ignores.
The treatment depends on the channel. Under licensing and over deployment are priced as a cost to cure against enterprise value. Change of control repricing is a run rate increase that flows through the earnings the buyer pays a multiple on. The deeper effect on value is set out in latent liability and enterprise value impact. The table below summarises how each channel typically shows up and is treated.
| Channel | How it shows up | Valuation treatment |
|---|---|---|
| Latent under licensing | Audit true up demand after close | Cost to cure against enterprise value |
| Indirect access | Connected systems generate licensable usage | Quantified exposure, often disputed |
| Change of control repricing | Consent, termination or higher pricing | Run rate cost increase in the model |
| Maintenance and support gaps | Lapsed or non transferable support | Reinstatement cost to cure |
| Over deployment | Usage beyond entitlement | Either license up or remediate, both priced |
Standard financial and legal due diligence is built to examine what has been recorded, and latent licensing exposure has not been recorded. It is a gap between contractual entitlement and actual deployment that only a specialist reconciliation reveals. This is why software risk so often reaches valuation as a post close surprise rather than a pre close adjustment: the diligence that priced the rest of the deal was not designed to find it. The exposure also affects the quality of earnings, as set out in software risk in the quality of earnings analysis.
The fix is to commission the software dimension as its own workstream, on the buyer's side, before signing. That workstream reconciles entitlement against deployment, tests the change of control and indirect access positions, and returns a quantified exposure the deal team can act on. It is independent and buyer aligned by design, paid only by the acquirer, with no affiliation to any publisher or reseller.
The scale of inherited software exposure is not hypothetical. 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. Demands at that level do not simply dent a return, they can break an investment case, which is why a buyer treats the software position as material to valuation rather than a compliance afterthought.
The buyers who protect their returns treat the question of how software risk affects deal valuation as a pre close discipline. They quantify the exposure, decide whether it hits price, structure, or the indemnity, and reflect it in the model so the return they underwrite survives the audit that follows. The allocation of that risk into the deal terms is covered in negotiating software risk allocation in the SPA. This is commercial and licensing advisory, not legal advice, so engage your own counsel on the interpretation of any clause.
How software risk affects deal valuation is the foundation of the software in deal valuation cluster, which then covers pricing the exposure in, quantifying the cure cost, and allocating the risk. 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