Post Close License Reconciliation

Post Close License True Up Risk and How to Manage It

Post close license true up risk and how to manage it is one of the most underestimated exposures a buyer inherits, and the rule is simple: measure your position before the publisher measures it for you.

Post close license true up risk and how to manage it is one of the most underestimated exposures a buyer inherits. A true up is the moment a publisher reconciles what a customer has deployed against what it is entitled to and charges for the difference. After a deal, that difference almost always moves in the publisher's favour, because consolidation increases deployment, merges environments, and changes the entity that holds the contract. Post close license true up risk and how to manage it comes down to one principle: measure your own position before the publisher measures it for you, and control the timing of any reconciliation rather than letting an audit set it. A true up discovered by the buyer is a budget line. A true up discovered by the publisher is a negotiation the buyer enters from behind.

This guide explains why true up risk rises after a deal and how to keep it under control. It is a core workstream in post close license reconciliation and a direct extension of finding under licensing before anyone else does.

Post close license true up risk and how to manage it: why a deal raises the risk

A deal increases true up risk in several ways at once. Consolidation deploys software more widely as the two organisations share systems, which raises usage against fixed entitlements. Merging environments can breach the terms of agreements that were priced for a single entity. Change of control and assignment terms can alter what the contract permits, so a deployment that was compliant under the target's agreement is no longer compliant under the combined entity. And the simple fact of a new, often better resourced owner makes the customer a more attractive audit target. Each of these is a reason a publisher might reconcile, and each moves the true up number upward.

The risk is largest with the publishers that audit most aggressively: Oracle, SAP, Microsoft, and IBM, with Broadcom for VMware an increasing presence. These publishers have the contractual audit rights and the commercial motive to reconcile after a deal. Inherited exposure with any of them is usually latent and unquantified in standard due diligence, and surfaces as an audit once the new owner is known. Quantifying it early is the work of fixing under licensing before a publisher finds it.

How true up risk builds after a dealFive stage timeline showing how post close true up risk builds from deal close, through consolidation and environment merging, to a publisher audit and reconciliation.How true up risk builds after a deal1CloseNew owner known2ConsolidateWider deployment3Merge envsTerms strained4TriggerAudit notice5ReconcileTrue up charged

How publishers measure a true up

A true up is measured by comparing deployment against entitlement, but the detail is where the cost lives. Publishers count to the exact metric in the contract, which may be processors, named users, devices, or environments, and they include deployments the customer may not consider active. Virtualisation is a frequent flashpoint, because some publishers count every host in a cluster where the software could run, not just where it does run. Indirect or digital access is another, where systems that read data from a licensed platform can themselves require licensing. The buyer that measures its own position has to count the same way the publisher will, not the way that feels reasonable, because the gap between the two is the exposure.

Understanding the measurement method is what lets a buyer manage the risk rather than be surprised by it. The reconciliation reproduces the publisher's counting logic on the combined estate, identifies where deployment exceeds entitlement, and quantifies the shortfall before any notice arrives. That number, held privately, is the foundation of every decision that follows.

True up triggers after a deal and how to manage each
TriggerWhy it raises the true upManagement action
Wider deploymentConsolidation shares systemsMeasure combined usage early
Merged environmentsSingle entity terms strainedCheck terms before merging
Change of controlPermitted use changesReview assignment clauses
Virtualisation countingWhole cluster may countReproduce publisher logic
Indirect accessConnected systems need licensingMap data flows to licensed platforms

Key takeaways

  • A true up charges for the gap between deployment and entitlement, and a deal almost always widens that gap.
  • Consolidation, merged environments, and change of control terms each raise true up risk at once.
  • The largest risk sits with Oracle, SAP, Microsoft, IBM, and increasingly Broadcom for VMware.
  • Publishers count to the exact contract metric, including virtualisation and indirect access, so the buyer must count the same way.
  • A true up the buyer measures first is a budget line; one the publisher measures first is a negotiation from behind.

Managing the timing and the negotiation

Once the exposure is quantified, the buyer controls how and when it is resolved. The options include correcting the deployment to fit the entitlement, buying additional licenses on the buyer's timetable rather than under audit pressure, or renegotiating the agreement as part of a consolidation that increases the publisher's overall footprint. What matters is that the buyer chooses the moment rather than reacting to an audit notice, because a reconciliation entered voluntarily is priced very differently from one entered under a formal audit. Sequencing this work is part of the broader post close reconciliation project plan, which assigns the true up workstream an owner and a deadline.

The combined footprint can also be turned into leverage. A buyer that now spends more with a publisher across the merged estate has standing to fold a true up into a renewal on better terms, rather than paying it as a standalone penalty. The reconciliation frames the conversation so the publisher sees a larger, longer customer rather than a one time compliance event.

Documenting the position so it holds

A managed true up rests on evidence. The reconciliation documents how the combined position was measured, which sources fed it, and how each deployment maps to an entitlement, so the buyer can defend the number if the publisher challenges it. A buyer that can show its working settles on its own measurement. A buyer that cannot is left disputing the publisher's count, which always reads in the publisher's favour. The documentation is what converts a quantified exposure into a defensible position.

Recommendations for buyers

  1. Measure the combined position to the publisher's exact counting method before any audit notice arrives.
  2. Review change of control and assignment terms before merging environments that strain single entity agreements.
  3. Reproduce virtualisation and indirect access logic, since these are the most common true up flashpoints.
  4. Choose the timing of any reconciliation rather than letting an audit set it.
  5. Use the larger combined footprint to fold a true up into a renewal on better terms.
  6. Document how the position was measured so it withstands a publisher challenge.

Why an independent advisor manages true up risk

Managing a true up means measuring the combined estate the way a publisher will, then negotiating from that knowledge. An independent, buyer side advisor reproduces the publisher's counting logic, quantifies the exposure before a notice arrives, and frames the resolution on the buyer's timetable with no stake in the publisher relationship. That independence is what keeps a true up a controlled budget line rather than a negotiation entered from behind.

Independent and buyer side. We act only for the acquirer. We hold no affiliation with any software publisher or reseller and are paid solely by you. This page is commercial and licensing guidance, not legal advice. Confirm any contractual interpretation with your own counsel.

Frequently asked questions

What is a post close license true up?

It is the moment a publisher reconciles what the combined entity has deployed against what it is entitled to and charges for the difference. After a deal that difference almost always moves in the publisher's favour because consolidation widens deployment.

Why does a deal raise true up risk?

Because consolidation deploys software more widely, merging environments can breach single entity terms, change of control clauses alter permitted use, and a new owner is a more attractive audit target. Each of these moves the true up number upward.

How do publishers measure a true up?

By counting deployment against the exact contract metric, which may be processors, named users, devices, or environments. Virtualisation and indirect access are frequent flashpoints because connected or potential deployments can count even when not actively used.

How can a buyer stay in control of a true up?

By measuring its own combined position to the publisher's counting method before any audit notice arrives, then choosing the timing of any reconciliation. A true up the buyer measures first is a budget line rather than a negotiation entered from behind.

Can a true up be folded into a renewal?

Often, yes. A buyer that now spends more with a publisher across the merged estate has standing to fold a true up into a renewal on better terms rather than paying it as a standalone penalty.

How do you defend the measured position?

By documenting how it was measured, which sources fed it, and how each deployment maps to an entitlement. A buyer that can show its working settles on its own measurement rather than disputing the publisher's count.

Reconcile the combined estate before a publisher does.

We build the combined entity license position, find the breaches consolidation creates, and fix them on your terms before an audit lands.

Request a confidential reconciliation