Building the combined entity license position is the central task of post close reconciliation. It is the act of producing one authoritative record of what the merged organisation is entitled to use, set against what it actually deploys, so the buyer can see its true compliance position rather than two partial views that no longer add up. Building the combined entity license position is where the abstract risk of a merger becomes a concrete, defensible number, and it is the foundation every later decision on remediation, consolidation, and renewal depends on.
This guide sets out how the position is built and why a half built one is worse than none. It is the core deliverable of post close license reconciliation, follows the post close software inventory, and supplies the evidence base for the first 90 days after close.
What building the combined entity license position involves
Building the combined entity license position means merging two entitlement records into one and reconciling it against a single measured deployment. The entitlement side pulls together every contract, amendment, true up, and proof of entitlement from both companies, normalised so an Oracle processor licence from one side and a named user licence from the other can be compared on the same terms. The deployment side captures what is installed and consumed across the whole combined environment. The position is the difference between the two, expressed per publisher and per product, with each gap classified and priced.
Normalising two estates onto one basis
The hardest part of building the position is normalisation, because the two companies almost never licensed the same product the same way. One may have bought Microsoft through an enterprise agreement and the other through a cloud solution provider. One may run Oracle on named user plus while the other runs processor metrics. Until these are expressed on a common basis, the entitlement records cannot be added together honestly. The table shows the kind of normalisation the work requires before any gap can be trusted.
Key takeaways
- The combined entity license position is one authoritative record of entitlement set against measured deployment.
- It turns the abstract risk of a merger into a concrete, priced number the buyer can defend.
- Normalisation comes first: two estates rarely license the same product the same way, so they must share a basis.
- The position is expressed per publisher and per product, with each gap classified and priced.
- Every later decision on remediation, consolidation, and renewal depends on this position being complete.
Why a half built position is dangerous
A partial position gives false comfort. If the entitlement record is complete but deployment is only half measured, the buyer may conclude it is compliant when it is not, exactly the surprise that surfaces as an audit. If deployment is measured but the entitlement record misses a true up buried in a side letter, the buyer may overpay to remediate a gap that does not exist. The position is only useful when both sides are complete and reconciled, which is why it is worth the time it takes. Once built, it drives the remediation in fixing under licensing before a publisher finds it and the savings in deduplicated spend.
Recommendations for buyers
- Assemble every contract, amendment, and true up from both companies before measuring anything.
- Normalise each publisher onto a common metric so the two entitlement records can be added honestly.
- Measure deployment across the whole combined environment, not just the larger legacy estate.
- Classify and price every gap per publisher, separating audit exposure from recoverable spend.
- Do not act on a half built position, since partial data gives false comfort in both directions.
Keeping the position current after it is built
A combined entity license position is a snapshot, and a merging organisation does not stand still. Users keep moving, systems keep consolidating, and renewals keep arriving, so a position that is accurate at close drifts within months unless it is maintained. The discipline that protects the work is to treat the position as a living record rather than a one off deliverable. Each significant consolidation step, each renewal, and each new deployment is reflected back into the entitlement and deployment views, so the buyer always knows where it stands rather than where it stood at close.
Maintenance also closes the loop between the position and the decisions it drives. When the position shows a publisher where deployment is approaching entitlement, that is the signal to remediate before the gap forms, not after. When it shows redundant entitlement after a consolidation, that is the signal to capture the saving at the next renewal. A position that is built once and then left static cannot send these signals, so the value of building it carefully is only realised if it is kept current. The marginal effort of maintenance is small against the cost of letting the position go stale and meeting the next audit blind.
The ownership question matters here too. The position is built during reconciliation, often with an advisor leading, but it has to be handed to a permanent owner inside the combined entity who keeps it current as business as usual. The handover should transfer not just the document but the method, the normalised metrics, and the data feeds that keep it accurate. A position with no permanent owner decays into the same two partial views the merger created, and the combined entity finds itself back where it started, reconciling from scratch the next time a publisher calls.
Why an independent advisor builds the position
Building the combined entity license position demands a party fluent in the metrics of every major publisher and with no stake in the answer. An independent, buyer side advisor with no affiliation to any publisher or reseller normalises the two estates onto a common basis, measures deployment without the optimism a vendor brings, and produces a position the buyer can stand behind in front of any licensor. That neutrality is what makes the position defensible, and a defensible position is the only kind worth building.