Post merger true up risk and how to avoid it

Post merger true up risk is the exposure that builds quietly when a combined entity deploys more software than its contracts entitle it to, then lands as a bill when the publisher audits. It is one of the most common and most avoidable ways an integration erodes the value a buyer underwrote, and avoiding it is largely a matter of measuring before you act.

What post merger true up risk is and why it lands

A true up is the publisher mechanism for charging you for usage above your entitlement. In a single company it is a routine annual reconciliation. After a merger it becomes a risk because integration tends to push deployment up while entitlement stays static. Target employees are granted access to acquirer systems. Applications are connected so they read from a licensed platform, creating indirect access. Two estates licensed on different metrics are merged without anyone re measuring against the survivor contract. Each of these quietly lifts consumption above the line, and the gap accrues until a vendor review converts it into a demand.

The risk is amplified by ownership change itself. A change of control is a common trigger for publisher audits, so the combined entity is more likely to be reviewed precisely when its position is least reconciled. The public record shows how large inherited and disputed licensing claims can become. As of June 2026, reporting on the disputes records that SAP pursued Anheuser Busch InBev for a reported 600 million dollars and Diageo for a reported 60 million pounds over disputed and inherited licensing, including indirect access established in Diageo Great Britain Ltd v SAP UK Ltd [2017] EWHC 189 (TCC).

How buyers avoid the true up gap

Avoiding a true up is not about freezing the business. It is about reconciling the combined position before integration actions push deployment past the entitlement ceiling. The four most common triggers, shared access, indirect access, metric mismatch and edition creep, can each be managed if they are identified before the access is granted rather than discovered in an audit.

The practical sequence is to build the combined effective license position early, model how planned integration steps will move consumption, and either align entitlement to the new level or stage the integration so it stays within the contract. Where a gap is unavoidable, it is far cheaper to negotiate the additional entitlement proactively than to settle it under audit pressure. This reconciliation discipline is the heart of post close license reconciliation and connects directly to the risk of accidental over deployment during integration.

True up risk is one thread of the broader post merger software integration programme. For the wider audit exposure that follows a transaction, see M&A software audit defense, and engage your own counsel for legal interpretation of any contract or claim.

What a post merger true up settlement actually costs

The headline of a true up demand is rarely the whole bill. When a publisher establishes that the combined entity has deployed beyond entitlement, the settlement typically combines the cost of the additional licenses at or near list price, back maintenance for the period of unlicensed use, and in some cases penalties or a forced migration to a more expensive edition or metric. Because integration tends to push deployment up steadily after close, the unlicensed period can be a year or more by the time a review lands, which multiplies the back maintenance component.

The negotiating dynamic is unfavourable when the gap is discovered by the publisher rather than disclosed by the buyer. A vendor that has found the exposure holds the leverage, sets the timeline, and prices to its own list rather than to the discount the combined volume would otherwise command. The same shortfall, identified proactively and addressed at a renewal, is usually bought at a negotiated rate without back maintenance or penalty. The difference between the two outcomes on the same underlying gap can be several multiples.

This is why the economics favour measurement over hope so heavily. The cost of building the combined effective license position early is small against the cost of settling an established true up under audit pressure. For buyers, the lesson is that the true up is not an unavoidable tax on integration. It is the price of not having reconciled, and it is almost entirely controllable by acting before deployment drifts past the entitlement ceiling.

Reconciling before the audit notice arrives

The single most effective control against a true up is to reconcile the combined position before a publisher does. A change of control routinely prompts a review, so the buyer should assume one is coming and prepare accordingly rather than waiting for the notice. An independent measurement of deployment against entitlement, built in the first hundred days, gives the combined entity a defensible position and the time to remediate quietly on its own terms.

That preparation also changes the response if a notice does arrive. A buyer who already holds an accurate, independent license position responds from strength, controls the scope, and settles any genuine gap at a negotiated rate. A buyer who has not reconciled is reacting to the publisher numbers, on the publisher timeline, at the publisher price. The work to avoid that outcome is modest and entirely within the buyer control.