What is post close license reconciliation? It is the work of taking two software estates that have just become one and producing a single, defensible record of what the combined entity is entitled to use and what it actually deploys. The moment a deal closes, two sets of contracts, two install bases, and two consumption histories collide under one owner. Post close license reconciliation is how that collision is turned into a controlled position rather than a latent liability waiting for the first publisher audit. Without it, the combined entity is exposed to exactly the inherited licensing risk that diligence was meant to contain.
This guide defines the work, sets out its steps, and shows where it sits in the wider post close license reconciliation effort. It follows directly from software due diligence, which prices the exposure before signing, and feeds building the combined entity license position after close.
What is post close license reconciliation, precisely
Post close license reconciliation is the structured comparison of entitlement against deployment across the newly combined estate, publisher by publisher, to find where the two no longer match. Before the deal, each company managed its own licences against its own usage. After close, the entities consolidate, users move between systems, agreements overlap, and the careful balance each side maintained breaks. Reconciliation rebuilds that balance for the combined entity, identifying under licensing that creates audit exposure and over licensing that wastes spend, and producing one record both the buyer and any publisher can be shown.
The steps in a post close reconciliation
The work follows a consistent sequence. It starts with a complete inventory of both estates, the subject of where to start a post close software inventory. It then assembles the full entitlement record from both companies contracts, measures actual deployment across the combined environment, and compares the two to find every gap. Each gap is classified as under licensing, which is audit exposure, or over licensing, which is recoverable spend. The table sets out the steps, their purpose, and the owner who should drive each.
Key takeaways
- Post close license reconciliation turns two colliding software estates into one defensible, priced position.
- It compares entitlement against deployment publisher by publisher to find every gap the merger created.
- Gaps split into under licensing, which is audit exposure, and over licensing, which is recoverable spend.
- It is the post close counterpart to diligence: diligence prices the risk, reconciliation resolves it.
- Done early, it lets the buyer fix under licensing on its own terms rather than under audit pressure.
Why reconciliation cannot wait
The combined entity is most exposed in the months right after close, when consumption has changed but the contracts have not caught up. Subscriptions auto renew on their old terms, users gain access to systems they were never licensed for, and the publishers that audit most aggressively, namely Oracle, SAP, Microsoft, and IBM, with Broadcom for VMware rising as of June 2026, have a clear incentive to look at a freshly merged customer. Public disputes show the stakes: SAP pursued AB InBev for a reported 600 million dollars and Diageo for a reported 60 million over disputed and inherited licensing, as reported in those cases as of June 2026. Reconciliation done in the first 90 days after close closes the window before a publisher exploits it.
Recommendations for buyers
- Begin reconciliation immediately at close, while consumption is changing and exposure is highest.
- Build one entitlement record and one deployment measurement before drawing any conclusions.
- Classify every gap as under licensing or over licensing so each gets the right treatment.
- Prioritise the aggressive auditors, since a freshly merged customer is a visible audit target.
- Carry the diligence findings straight in, so nothing priced before signing is lost after close.
How reconciliation protects the value the deal was priced on
Reconciliation is often filed under integration housekeeping, but it is closer to value protection. The price a buyer paid assumed a certain cost base, and an unreconciled software estate hides costs in two directions. Under licensing is a contingent liability that lands as an audit settlement, and over licensing is a recurring overspend that erodes the synergy case. Both sit invisibly in the combined estate until reconciliation surfaces them. The exercise that produces the combined entity position is therefore not administrative. It is the work that confirms whether the cost assumptions behind the deal still hold once the two estates are actually merged.
The timing of the work also shapes how much value it protects. A gap found in the first weeks after close can be remediated on the buyer terms, often folded into a renewal where there is leverage. The same gap found a year later, after consumption has grown and a publisher has opened an audit, is settled at list with back maintenance. Reconciliation done early therefore protects more value per gap than the same work done late, which is why the discipline of starting at close, rather than waiting for the estate to settle, matters so much to the eventual return.
There is also a defensive dividend. A combined entity that holds a complete, reconciled position is a far less attractive audit target than one that visibly does not know its own footprint. Publishers prioritise audits where they expect to find shortfall, and a buyer that can produce a clean, documented position on request signals that an audit is unlikely to be worth the publisher effort. Reconciliation, done properly, does not just resolve the exposure that exists. It reduces the probability that the publisher comes looking in the first place.
Why an independent advisor leads the reconciliation
Reconciliation done by a party that earns on the outcome is not reconciliation, it is a sales motion. An independent, buyer side advisor with no affiliation to any publisher or reseller builds the combined entity position against the evidence, classifies the gaps without a stake in the answer, and remediates under licensing on the buyer terms rather than the publisher schedule. That independence is what makes the resulting position defensible if a publisher ever asks to see it.