How latent under licensing becomes an eight figure claim is the question that explains why software risk belongs in every deal, because the journey from a quiet, unpriced gap to a nine figure demand is short and predictable. Latent under licensing is the mismatch between what an organisation has deployed and what it is entitled to use, sitting unmeasured in the estate. On its own it costs nothing and shows up nowhere, which is why standard financial diligence walks past it. But it does not stay quiet. A trigger, usually a deal, brings it to a publisher's attention, and then it compounds through a series of multipliers that turn a modest base into a very large number. This page sets out that compounding, as a child of the cluster on M&A software audit risk.
How latent under licensing becomes an eight figure claim through compounding
The reason a small gap becomes a large claim is that publisher claims are not calculated the way a buyer would price a shortfall. A buyer thinks in terms of the discounted rate it would have paid to license the extra usage. A publisher claim is built in layers, each of which multiplies the base. First, the shortfall is valued at list price, not the discount the customer might have negotiated in a normal purchase. Second, back maintenance is added, covering the years the gap existed, on the logic that the customer was consuming support and updates it had not paid for. Third, penalties or interest may be applied. Fourth, the publisher often insists the settlement include a forward looking subscription or migration, converting a one time gap into an ongoing cost. By the time these layers stack, a base shortfall worth a few hundred thousand at the discounted rate can present as a multi million demand, and on a large estate the same arithmetic reaches eight figures.
Why the gap stays invisible until a deal
Latent under licensing survives undetected because nothing in the normal run of business measures it. The deployment lives in the configuration of servers and the activity of users, not in a contract or an invoice, so the finance function never sees it. The procurement team tracks what was bought, not what is used. The IT team manages systems, not entitlements. The gap can therefore persist for years while the organisation operates in apparent compliance. A deal changes everything, because it gives the publisher both a reason to look and a moment of maximum advantage. The publisher learns of the ownership change, infers that the estate is moving and the new owner is distracted, and opens a review. Consolidation onto shared infrastructure, undertaken to deliver synergies, frequently widens the gap at the same time. The latent position that was invisible to the target becomes a priced claim to the buyer, which is why it must be surfaced during diligence rather than after close, a point developed in inherited software audit liability explained.
| Layer | What the publisher applies | Effect on the number |
|---|---|---|
| Base shortfall | Quantity deployed over entitlement | Starting point, often modest |
| List price | Full rate, not the customer discount | Multiplies the base |
| Back maintenance | Support fees for years of the gap | Often equals the license cost |
| Penalties or interest | Charges for the period of non compliance | Adds a further layer |
| Forward subscription | Ongoing commitment in settlement | Converts one time into recurring |
Key takeaways
- Latent under licensing is an unmeasured gap between deployment and entitlement that costs nothing until a publisher prices it.
- The gap compounds through list price valuation, back maintenance, penalties, and a forward subscription.
- Back maintenance alone often equals or exceeds the license cost, a major reason claims reach eight figures.
- A deal supplies both the trigger and the publisher's moment of maximum advantage, and consolidation widens the gap.
- Measuring the position before signing lets a buyer price it into the deal or recover it from the seller.
Consolidation is the accelerant
The integration that follows a deal does not just expose the latent gap, it often enlarges it. The same consolidation moves that create synergies, pooling servers, sharing infrastructure, merging user directories, and migrating to the cloud, frequently increase the licensable footprint under the major publishers' counting rules. Oracle counts more processors when databases move onto shared clusters. SAP counts more when new systems read its data. Microsoft counts more when access spreads through merged directories. A gap that was a fixed size while the target operated independently can grow during integration, so the buyer is not only inheriting the original shortfall but adding to it. This is why the consolidation plan and the licensing analysis have to run together, and why a buyer that integrates first and measures later pays for the difference. The way these claims are sized for decision makers is set out in quantifying audit exposure for an investment committee.
The public proof points
The scale these claims reach is not theoretical. As of mid 2025, SAP pursued AB InBev for a reported 600 million dollars and Diageo for a reported 60 million over disputed and inherited licensing. Whatever the eventual outcome of any particular case, the figures show what the compounding mechanics can produce when a large estate carries a latent position and a publisher decides to price it. These are not penalties for deliberate piracy. They are the arithmetic of list price, back maintenance, and indirect or inherited usage applied to estates that believed themselves compliant. For a buyer, the lesson is that the gap does not announce itself and the claim does not arrive gradually. It surfaces as a number, already compounded, in a letter. The only defense is to have measured the position first, which is the discipline behind quantifying exposure before it crystallises.
How a buyer interrupts the compounding
The compounding is only inevitable if the gap is discovered by the publisher rather than the buyer. An independent technical license review, conducted during diligence, measures deployment against entitlement across the estate and surfaces the latent position while the buyer still has options. Measured before signing, the gap can be priced into the consideration, held in escrow, covered by warranty and indemnity, or closed by remediation before a publisher ever looks. Measured after a notice arrives, the same gap is already compounding and the buyer is negotiating from behind. The difference between the two outcomes is timing, and timing is the one variable the buyer controls. The full cost of letting the gap run to a claim is set out in the true cost of a failed software audit post acquisition.
Recommendations for buyers
- Measure deployment against entitlement before signing. Surface the latent gap while pricing and recovery options remain open.
- Model the compounding, not just the base. Price the gap at list plus back maintenance, the way a publisher would.
- Run consolidation and licensing together. Stop integration from enlarging the gap before it is measured.
- Use the deal documents. Allocate the priced exposure to the seller through reps, indemnity, or escrow.
- Remediate where you can. Close avoidable gaps before a publisher has a reason to look.
Why the finance function never sees it coming
The reason latent under licensing repeatedly surprises sophisticated buyers is that it is invisible to the people whose job is to find risk. A finance team reading a target's accounts sees the software it pays for, recorded as license fees and maintenance, and it sees no liability because none has been booked. A legal team reviewing the contracts sees agreements that appear to be in force, with no notice of dispute attached. Neither has any way to see the gap, because the gap lives in the configuration of servers and the activity of users, not in any document a data room contains. This is the precise sense in which the exposure is latent: it is real, it is quantifiable, and it is entirely absent from the records diligence normally examines. A buyer that relies on financial and legal diligence alone is not assessing software risk, it is assuming it away. The only way to surface the position is a technical license review that measures deployment against entitlement directly, conducted alongside the financial and legal work rather than in place of it. That review is what converts an invisible liability into a number the buyer can price, escrow, or recover, before the publisher converts it into a claim the buyer must pay.
How latent under licensing becomes an eight figure claim, in one line
How latent under licensing becomes an eight figure claim comes down to compounding. A small, invisible gap is valued at list price, multiplied by years of back maintenance, loaded with penalties, and converted into a forward subscription, while consolidation quietly enlarges the base. A buyer that measures the position before a publisher does interrupts the whole sequence and keeps the number proportionate. We quantify that latent exposure on the buyer side only, paid solely by the acquirer.