An Enterprise Agreement true up is hard enough when the company stays the same shape all year. When the company changes shape, through an acquisition, a merger, or the sale of a division, the true up becomes a far more demanding exercise. You are no longer counting the growth of one estate. You are reconciling entitlements and deployments across organizations that ran different agreements, used different products, and kept records to different standards. Get it right and you absorb a new business without paying twice for licenses you already hold. Get it wrong and the true up either overstates badly, because nobody netted the two sets of rights, or understates in a way that surfaces later as exposure. This article sets out how to defend the count when the corporate structure itself has moved.
For the wider picture of how Microsoft verifies and bills licensing across audits and agreements, the Microsoft Audit Survival Guide covers the full landscape. Here we focus on the two events that change the corporate boundary and what they do to the true up.
Why a transaction breaks the routine count
A normal true up assumes continuity. You start from a known baseline, you add the net new units deployed during the year, and you price the difference. A transaction removes that continuity. After an acquisition there is a second estate that was never in your baseline, with its own servers, its own users, and its own licenses, some of which may transfer to you and some of which may not. After a divestiture there is a slice of your estate that has left, but the licenses tied to it may still sit on your agreement, quietly counted as yours. In both cases the simple arithmetic of last year plus additions no longer describes reality, and a report run as if it did will produce a figure that bears little relation to what you actually owe.
A transaction breaks the one assumption a routine true up depends on, that this year is last year plus growth. After a deal it is two histories that have to be reconciled.
The acquisition problem: entitlements that may already cover you
When you acquire a business, you may also acquire its licenses. Whether you do, and on what terms, depends on the agreements involved and how the transaction was structured. This matters enormously at true up, because the acquired company's deployments can often be covered, in whole or in part, by entitlements that came with the deal. A true up that counts the acquired estate as brand new additions, without first testing what rights transferred, pays full price for licenses the group already holds.
The defense is to establish, before you count, exactly which entitlements moved with the acquisition and which did not. That means reading the transaction documents, identifying the licensing agreements on both sides, and confirming the assignment or transfer rights. Only once you know what the group genuinely owns can you work out what the true up should actually add. The acquired deployments are then netted against the transferred rights, and you report the real shortfall rather than the gross headcount.
- Identify every licensing agreement held by the acquired business, not only the obvious ones
- Confirm which entitlements transferred under the transaction and on what terms
- Map the acquired deployments to products and editions actually in use
- Net the transferred rights against those deployments before pricing any addition
- Reconcile the combined position against the telemetry Microsoft already holds for both entities
The divestiture problem: paying for an estate that has left
A divestiture creates the opposite risk. When a division is sold, its servers and users leave the group, but the licenses associated with them may remain on your Enterprise Agreement unless they are formally removed or transferred. An Enterprise Agreement true up reports additions, not reductions, so a routine true up will not surface the fact that you are still carrying licenses for a business you no longer own. The result is a baseline that is too high, and you keep paying for it cycle after cycle until someone reconciles the agreement against the smaller estate.
The defense here is to treat the divestiture as a trigger to re examine the baseline itself, not just the additions. That means confirming which entitlements should have left with the divested business, whether they were assigned to the buyer, and whether your agreement baseline was adjusted to reflect the smaller organization. Where the baseline was not adjusted, that is a conversation to have deliberately, because an inflated baseline compounds every year it goes unchallenged.
A worked illustration
Consider a group that acquired a mid sized business during the year and ran a standard true up afterward. The figures here are indicative and used only to show the mechanics.
| Step | Units to true up | What changed |
|---|---|---|
| Standard combined report | 900 | Acquired estate counted as all new |
| Apply transferred entitlements | 560 | 340 covered by rights that moved with the deal |
| Remove decommissioned overlap | 470 | 90 duplicate systems retired after integration |
| Net group held rights | 400 | 70 covered by existing group entitlements |
The same combined estate produces a true up of 400 units rather than 900 once the transferred rights and the integration cleanup are taken into account. The 500 unit difference is licenses the group either already owned or no longer ran. None of this is visible in the standard report, because the report counts deployments, not the rights and the history behind them.
How a buyer side defense runs a transactional true up
Defending a true up through a transaction adds a reconciliation layer on top of the normal discipline. The sequence matters, because each step depends on the one before it.
Why the timing of the deal matters
Where a transaction falls relative to your true up date and your renewal shapes how much room you have to get the reconciliation right. A deal that closes well before the true up gives time to integrate, retire overlap, and establish what transferred. A deal that closes days before the deadline leaves you reporting a combined estate you have not yet untangled. Where possible, sequence the true up so the reconciliation happens with room to breathe, and where the timing cannot be changed, document the position clearly so the count can be corrected rather than locked in at an inflated figure.
Where this leaves you
A merger or a divestiture is exactly the moment when a true up run on autopilot does the most damage. An acquisition counted as all new pays twice for rights that came with the deal. A divestiture left unreconciled keeps a departed estate on the bill for years. Treated as a deliberate reconciliation, the transactional true up becomes a chance to clean the baseline, capture the rights you are owed, and report only the genuine shortfall. The work is detailed, but the saving is proportional to the size of the deal, and the alternative is paying for the same licenses twice.
If a transaction is reshaping your estate and a true up is approaching, the reconciliation should be planned, not improvised. Book a Strategy Call to walk through your specific position and the moves available before the deadline locks the figure in.
If you would rather not face that alone, our EA true up defense service checks every line before you sign.