This post close license reconciliation FAQ collects the questions deal teams, CFOs, and integration leads ask us most once a deal has closed and two software estates have to become one. The answers are written from the buyer's side, plainly, with the exposure framed honestly rather than minimised. For the full method, start with the pillar on post close license reconciliation; this page is the quick reference that sits beside it.
What this post close license reconciliation FAQ covers
Reconciliation after a deal is the work of combining two licensed estates into a single, accurate, defensible position, then acting on what that position reveals: duplicate spend to remove, shortfalls to remediate, and inherited obligations to honour. The questions below move from the basics of what it is and who owns it, through timing and cost, to the harder issues of audit risk and how the value is measured. Each answer links to the deeper page where the topic is treated in full, so this FAQ works as a map of the cluster as well as a set of direct answers.
What is post close license reconciliation?
It is the process of merging two companies' software entitlements and deployments into one accurate effective license position after a deal closes, then acting on the gaps. It removes duplicate and surplus spend, remediates shortfalls before a publisher prices them, and folds inherited obligations into the combined estate. The full definition sits on what is post close license reconciliation.
When should reconciliation start?
Immediately at close, and ideally with the groundwork laid before signing. The first ninety days matter most, because integration moves like consolidating servers or standardising tools can trigger breaches before anyone has built the combined position. The timeline is set out in the first 90 days reconciling software after close.
Who owns reconciliation after close?
Someone must be named, or it falls between IT, procurement, and finance and nobody does it. The accountable owner needs authority over contracts and the integration plan. Ownership is covered in who owns license reconciliation after close.
| Question | Short answer | Full page |
|---|---|---|
| Where do we start? | A combined software inventory | Post close software inventory |
| How do breaches happen? | Consolidation crosses a license boundary | How entity consolidation triggers breaches |
| What about the TSA? | Shared licenses need separating | Reconciliation and the TSA |
| How is the value proven? | Cash saved plus exposure removed | Measuring savings and risk reduction |
Key takeaways
- Post close license reconciliation merges two estates into one defensible position and acts on the gaps it reveals.
- Start at close and prioritise the first ninety days, before integration moves can trigger a breach.
- Name an accountable owner with authority over contracts and the integration plan, or the work falls through the cracks.
- The largest exposures, indirect access and inherited settlements, are invisible to tools and need advisory judgment.
- Value is two sided: realised cash from removing duplicate spend and avoided cost from closing exposure.
What does reconciliation cost, and is it worth it?
The cost is modest against the exposure it removes. Reconciliation pays for itself through duplicate spend cancelled and audit settlements avoided, and the return is measured as recurring run rate reduction plus exposure removed. The framing is in measuring reconciliation savings and risk reduction. To calibrate the downside it protects against: as of mid 2025, SAP pursued AB InBev for a reported 600 million dollars and Diageo for a reported 60 million over disputed and inherited licensing.
Does a deal really increase audit risk?
Yes. Publishers monitor corporate filings, and a change of ownership signals that an estate has changed, which is a common trigger for an audit. The acquired entity is a known, often soft target. This is the central theme of the audit risk cluster, starting with why publisher audits follow M&A deals.
What are the most expensive surprises?
Two recur. Indirect access, where a system or person reads data from a licensed platform without a direct login, which tools cannot see. And inherited audit settlements, where a target's prior settlement carries forward obligations the buyer breaches during integration. The second is covered in reconciling inherited audit settlements and obligations.
Do we need tools, or people?
Both, in that order of dependence. Tools discover what is deployed quickly across two estates. People apply the publisher specific counting rules and resolve the gaps tools cannot see. The balance is explained in license reconciliation tooling and methods.
Recommendations for buyers
- Start before integration moves. Build the combined position first so consolidation does not trigger a breach.
- Name one accountable owner. Give them authority over contracts and the integration plan.
- Pull every settlement and side letter. Inherited obligations are the surprises that hurt most.
- Use tools for reach, judgment for risk. Let people handle indirect access and disputed metrics.
- Measure both returns. Report cash saved and exposure removed so the work reads as the return it is.
Use this post close license reconciliation FAQ as your starting map
This post close license reconciliation FAQ answers the questions deal teams ask first and points to the deeper pages for each one. The throughline is consistent: build an accurate combined position before you act, start early, name an owner, treat the invisible exposures as the real risk, and measure both the cash and the risk you removed. If your question is not here, it is usually because it is specific to your deal, which is exactly the conversation we have on the buyer's side, paid solely by the acquirer.