Reconciling named user and device licenses after a merger is where two clean license positions become one messy one. Before the deal, each company counted its own users and devices against its own contracts. After close, the combined entity inherits both counts, and the two rarely add up the way the contracts assume. Reconciling named user and device licenses after a merger means deduplicating the people and machines that now appear in both estates, mapping each to the right entitlement, and proving the combined count is licensed before a publisher counts it for you. Get this wrong and the same person can be counted twice, or a shared device can be licensed in two places, and the gap becomes a true up at the next audit.
This guide sets out how to reconcile user based and device based metrics across a merged estate. It is a core workstream in post close license reconciliation and depends on a complete inventory and a single view of identity, without which the count cannot be trusted.
Reconciling named user and device licenses after a merger: the double count trap
The first risk is double counting people. When two companies merge, the same individual can hold accounts in both directories, especially contractors, executives, and anyone who worked across both organisations before the deal. A naive count adds the two user lists together and concludes the combined entity needs more licenses than it does. The opposite error is just as costly: deduplicating too aggressively and assuming one person needs one license when the publisher's metric counts named users per product or per environment. The reconciliation has to match the count to the exact definition in each contract, because named user does not mean the same thing across Oracle, SAP, and Microsoft.
Device based metrics carry their own trap. A device license follows the machine, not the person, so a shared workstation, a kiosk, or a virtual desktop pool can be licensed differently from a one to one user assignment. After a merger, device estates overlap where both companies issued hardware to the same locations or used the same virtual desktop infrastructure. Counting devices without resolving which estate owns each one produces the same double count in a different form.
Building one identity view before counting
No reconciliation of user based metrics is reliable until the combined entity has a single view of identity. That means resolving the two directories into one authoritative list of distinct people, flagging duplicates, and retiring dormant accounts that no longer represent an active user. Dormant accounts are a quiet source of over licensing, because a publisher metric that counts provisioned named users will include a leaver who was never deprovisioned. Cleaning identity first is the single highest leverage step, because every later count rests on it. This is the same discipline that supports building the combined entity license position across every metric, not just users.
For device based licensing, the equivalent step is a clean asset register that resolves which entity owns each machine and how it is used. A device assigned to a leaver, a decommissioned server still showing in discovery, or a virtual machine cloned during integration all distort the count. The register has to reflect reality on the ground, not the sum of two stale inventories.
Key takeaways
- Merging two estates double counts people and devices unless identities and assets are deduplicated first.
- Named user does not mean the same thing across publishers, so match every count to the exact contract definition.
- Dormant accounts inflate user counts and are a quiet source of over licensing.
- Device licensing follows the machine, so shared devices and virtual desktop pools need explicit resolution.
- A single identity view and a clean asset register are the foundation every count rests on.
Matching the reconciled count to the contract metric
Once identity and assets are clean, the count has to be matched to the precise metric each contract uses. A Microsoft agreement may license on a per user basis with rights that travel across devices, while an Oracle or SAP agreement may count named users per environment or per module. Reconciling Microsoft estates after a merger is its own discipline, covered in reconciling Microsoft agreements after a merger, because the metric and the migration rights differ from other publishers. The reconciliation reads each contract literally and counts to its definition rather than to a generic notion of a user.
The same care applies where users and subscriptions overlap. A named user on a perpetual license may also hold a SaaS subscription for the same capability after the merger, which is both a double count and an overlap to rationalise. Reconciling the two together avoids paying twice, which is why this workstream connects to reconciling SaaS subscriptions across two companies.
Proving the count before a publisher tests it
The goal of the reconciliation is a count the combined entity can prove, not just assert. That means documenting how each number was derived, which source it came from, and how duplicates were resolved, so the position withstands a publisher's challenge. A buyer that can show its working settles an audit on its own evidence. A buyer that cannot is left arguing against the publisher's measurement, which always reads in the publisher's favour. The reconciliation produces both the number and the evidence behind it.
Recommendations for buyers
- Build one authoritative identity view across both directories before counting any user metric.
- Retire dormant and duplicate accounts so the count reflects active users only.
- Resolve device ownership and virtual desktop pools in a clean asset register.
- Read each contract literally and count to its exact named user or device definition.
- Reconcile overlapping perpetual users and SaaS subscriptions together to avoid paying twice.
- Document how every number was derived so the position survives a publisher challenge.
Why an independent advisor reconciles the count
Counting users and devices across a merged estate is exact work that a publisher would rather do for you, on its own terms. An independent, buyer side advisor reconciles the count to each contract's true definition, deduplicates identity and assets without a stake in any renewal, and documents the result so the combined entity can defend it. That independence turns a fragile assumption into a count the buyer can stand behind.