Post Merger License Reconciliation: The Complete Guide

Post merger license reconciliation is what turns two separate software estates into one accurate, compliant and lower cost estate after a deal closes. It is the post close counterpart to due diligence. Where diligence prices the exposure before signing, reconciliation resolves it afterward by establishing what the combined entity is genuinely entitled to, what it actually deploys, and where the two diverge. This guide explains the method, the sequence, the risks unique to a combined entity, and links to every detailed page in the cluster.

The need is created by the deal itself. A change of ownership and the entity consolidation that follows can break licenses that were tied to a named legal entity, collapse volume discounts, and expose the under licensing that was latent in the target. A publisher reads a merger as a prompt to measure. Reconciliation gets there first, building a defensible position and closing gaps on the buyer's terms rather than the vendor's.

What post merger license reconciliation involves

Reconciliation starts with inventory and ends with a single combined license position. Between those points it deduplicates entitlements, resolves conflicts where two agreements cover the same software on different terms, fixes under licensing before it becomes a claim, and removes duplicate spend at the right contractual moments. The work spans on premises and cloud, named user and device metrics, maintenance and support contracts, and the inherited audit settlements that sometimes come with a target.

The foundation is the combined entity license position, covered in building the combined entity license position. Without it, every consolidation move is a guess. With it, each move can be validated against the contract before execution.

Why entity consolidation creates license risk

The single most overlooked risk in reconciliation is that the act of combining entities can itself breach a license. Many enterprise agreements are written against a specific legal entity and a specific affiliate definition. When the acquired entity is merged, renamed or folded into the buyer, software that was correctly licensed before can fall outside the agreement after. Volume tiers tied to the seller's broader relationship can also fall away, raising unit prices on the remainder. The page on how entity consolidation triggers license breaches works through the mechanism.

This is why reconciliation is not a finance exercise. Public disputes show the cost of getting inherited licensing wrong. As of 2024, SAP pursued AB InBev for a reported 600 million dollars and Diageo for a reported 60 million over disputed and inherited licensing, per contemporaneous reporting. Reconciliation exists to make sure those questions are answered on the buyer's terms.

The first 90 days after close

The early window matters because it is when integration decisions are made and when audit letters tend to arrive. A disciplined first 90 days inventories both estates, stands up the combined position for the high risk publishers first, and identifies the duplicate spend that can be removed at upcoming break points. Moving fast on inventory while moving carefully on cuts is the balance. The page on the first 90 days reconciling software after close sets out the plan.

Fixing under licensing before a publisher finds it

Where reconciliation finds the combined entity is under licensed, the buyer has a choice that the seller never offers a publisher: remediate quietly and on commercial terms, or wait to be audited and remediate under penalty. Fixing first is almost always cheaper, because it removes the back maintenance, the penalties and the leverage a vendor holds during an audit. The trick is to remediate without signalling the gap, which is a commercial skill as much as a technical one. See fixing under licensing before a publisher finds it and post close license true up risk.

Removing duplicate spend safely

The combined entity almost always pays twice for something: two collaboration suites, two security stacks, overlapping enterprise agreements, maintenance on systems integration will retire. Removing this spend is valuable and recurring, but it follows the same rule as cost optimization everywhere on this site. Cancel at contractual break points, not mid term. Merge agreements at the right renewal so combined volume improves pricing. Validate every cut against the combined position first. The table below sets out the common reconciliation moves.

Sequencing remediation against the deal calendar

Reconciliation does not happen in a vacuum. It competes for attention with every other integration workstream in the first year, and it has to be sequenced so the highest risk and highest value items are resolved while the team still has the data fresh and the mandate strong. The practical order is to stabilise first, fixing anything that creates immediate audit exposure, then optimise, removing duplicate spend at the break points as they arrive, then institutionalise, handing a clean and documented position to the software asset management function that will run it for the life of the asset. Trying to do all three at once usually means none is done well. The pages on post close license true up risk and who owns license reconciliation after close describe how to phase the work and where accountability sits.

For an acquirer that buys repeatedly, the discipline compounds. A roll up that reconciles every acquisition the same way builds a reusable method, a known baseline for the common publishers, and a negotiating position that grows with each deal. The page on post close reconciliation for roll up acquirers sets out how to turn a one time exercise into a repeatable capability, and what post close license reconciliation is gives the foundational definition for teams new to the work. The frequently asked questions buyers raise are gathered in the post close license reconciliation FAQ.

Why independent reconciliation protects the buyer

Reconciliation is most valuable when the firm doing it answers only to the acquirer. A reseller has an interest in selling more licenses, and a publisher's own tooling is built to surface shortfalls, not to find the over licensing and duplication that favour the customer. Independent buyer side reconciliation looks in both directions: it closes the gaps that create audit risk and it recovers the spend that should never have been duplicated. The result is a combined estate that is both compliant and lean, documented well enough to survive a publisher's own measurement and to hand cleanly to the next owner at exit. The pages in this guide describe a method designed for that single allegiance, and the firm behind it is paid only by the buyer, with no publisher or reseller affiliation of any kind.

Reconciling specific publishers after a merger

Each publisher reconciles differently because each measures differently. Oracle reconciliation turns on processor counts and virtualisation, where two merged data centres can suddenly share hosts in ways that change the licensable footprint. The page on reconciling Oracle licensing after a merger covers it. SAP reconciliation turns on named users and digital access, where two user bases merge and duplicate identities, and indirect access multiplies as systems integrate, covered in reconciling SAP licensing after a merger. Microsoft is the most common collision of all, where two enterprise agreements meet and have to be combined onto one set of terms at the right renewal, covered in reconciling Microsoft agreements after a merger and when two enterprise agreements collide.

The metric itself often needs reconciling. Two companies may license the same product on different bases, one by named user and one by device, and the combined base has to be mapped to a single coherent metric before any true up. The page on reconciling named user and device licenses after a merger works through the mapping.

Reconciling cloud and SaaS across two companies

Cloud entitlement does not behave like a perpetual license. Subscriptions auto renew, overage is billed silently, and connector licensing accumulates as integrations multiply. Reconciling cloud across two companies means building a combined view of every subscription, its commitment, its true consumption and its renewal date, then removing the duplication at the break points. The pages on reconciling cloud entitlements across entities and reconciling SaaS subscriptions across two companies cover the method, and deduplicating software spend after an acquisition turns the view into savings.

Maintenance, support and inherited obligations

Maintenance and support contracts are where quiet money leaks. Two companies often carry overlapping support on the same platforms, or pay maintenance on systems that integration will retire. Reconciling them means matching every support contract to a system that is genuinely in production, then cancelling the rest at the right point. The page on reconciling maintenance and support contracts covers it. A target can also bring inherited audit settlements and commitments, ongoing obligations from a prior dispute that bind the combined entity, covered in reconciling inherited audit settlements and obligations.

Reconciliation and the transition services agreement

When an acquisition comes with a transition services agreement, reconciliation and separation run together. The combined entity may be standing up new contracts while still consuming services billed under the transition arrangement, which creates exactly the double payment that has to be sequenced out. The page on reconciliation and the transition services agreement explains how to align the two, and post close reconciliation for roll up acquirers covers the case where the acquirer is folding in target after target.

Measuring savings and proving risk reduction

Reconciliation has to prove its value in two currencies: cost removed and risk closed. Cost removed is the duplicate spend eliminated and the licenses recovered. Risk closed is the under licensing remediated and the exposure that is no longer waiting to be audited. Both belong in the post close value creation report that operating partners and sponsors expect. The pages on measuring reconciliation savings and risk reduction and license reconciliation tooling and methods set out how to measure and how to run the work, and the post close reconciliation project plan sequences it end to end.

Where to start with the combined inventory

Inventory is the unglamorous foundation that everything else rests on. The starting point is not a perfect picture but a fast, prioritised one: the high value and high risk publishers first, the financial records of what is paid, the entitlement records of what is owned, and the deployment data of what is running. The page on post close software inventory and where to start sets out the practical first steps, and reconciling overlapping software agreements handles the conflicts the inventory surfaces.

One further point is worth stating plainly. Reconciliation is not a cost centre, it is a value creation lever that happens to reduce risk at the same time. Every duplicate subscription removed and every under licensed publisher remediated improves the margin of the combined entity and improves the quality of the asset at exit, when a diligent buyer will examine the very position this work created. Treating reconciliation as a strategic part of the integration, resourced and owned accordingly, is what turns it from a compliance chore into one of the more reliable returns available after a deal closes.

Everything in this license reconciliation guide