What Is License Reconciliation?

What is license reconciliation? It is the work of matching what an organisation is entitled to use against what it actually runs, agreement by agreement, to find where the two do not line up. After a merger or acquisition it becomes critical, because the buyer now holds two estates that were never built to fit together. License reconciliation is how a buyer turns an inherited, unmapped licensing position into a single defensible one before a publisher audit does it instead.

Why license reconciliation matters after a deal

When two companies combine, their software estates combine with them. Each was sized, contracted and deployed independently. The result is duplicate entitlement, overlapping agreements, and usage that no single contract clearly covers. License reconciliation builds one effective license position across the combined estate, identifies where deployment exceeds entitlement, and quantifies the cost to close each gap. Without it, the combined organisation is exposed to exactly the kind of inherited claim that lands as a publisher audit in the first year or two after close.

How license reconciliation works

The process starts by gathering entitlement data from contracts and deployment data from the estate, then reconstructing the position publisher by publisher. Oracle, SAP, Microsoft and IBM usually come first, with Broadcom owned VMware, Salesforce and ServiceNow rising in importance as of June 2026. Each gap is sized for its worst case and likely settlement. The output is a prioritised remediation plan: where to true up, where to resize, where to consolidate duplicate agreements, and where to challenge a publisher position with evidence.

From reconciliation to consolidation

License reconciliation is not only about closing gaps. It is also where the combined organisation finds savings. Duplicate agreements can be consolidated, oversized entitlements resized, and renewals sequenced to capture better terms. The same exercise that defends against an audit also reduces the run rate cost of the combined estate. Done early, it converts the chaos of two merged estates into a single managed position. This work is commercial and licensing advisory, not legal advice.

What license reconciliation produces
Step	What it does	Result for the buyer
Effective license position	Entitlement against usage	One defensible baseline
Gap sizing	Worst case and likely settlement	Quantified exposure
Remediation plan	True up, resize, consolidate	Prioritised actions
Consolidation	Remove duplicate agreements	Lower combined run rate

Key takeaways

License reconciliation matches entitlement to actual usage across a combined estate.
After a deal it turns two unmapped estates into one defensible licensing position.
It both defends against a post close audit and surfaces consolidation savings.
The output is a prioritised plan to true up, resize, consolidate and challenge.

Recommendations for buyers

Start with the tier one publishers. Reconcile Oracle, SAP, Microsoft and IBM first, where audit risk concentrates.
Reuse the diligence baseline. Carry the effective license position from due diligence straight into reconciliation.
Quantify every gap. Size the worst case and likely settlement so remediation is prioritised by exposure.
Capture the savings. Consolidate duplicate agreements and resize oversized entitlements while you reconcile.

Related reading: see the M&A software glossary hub, plus effective license position and software audit.

Frequently asked questions

When should license reconciliation happen?

As soon as possible after close, ideally building on the effective license position from due diligence. The first year or two after a deal is when change of ownership audits are most likely, so the baseline needs to be ready.

How is license reconciliation different from software due diligence?

Due diligence sizes the exposure before signing to inform price and protections. Reconciliation is the post close work of building one defensible position across the combined estate and closing the gaps it finds.

Does license reconciliation save money or just reduce risk?

Both. It defends against an audit and surfaces consolidation savings, because merging two estates usually creates duplicate agreements and oversized entitlements that can be resized.

Which publishers should reconciliation prioritise?

Oracle, SAP, Microsoft and IBM are the long standing audit leaders, with Broadcom owned VMware, Salesforce and ServiceNow increasingly active as of June 2026. These names carry the most audit risk after a change of ownership.

Request a confidential software M&A risk assessment.

Map and quantify the licensing exposure in your target or portfolio before it becomes a post close audit. Independent, buyer side, paid only by the acquirer.

Talk to a software M&A advisor