Who owns license reconciliation after close is the question that decides whether a deal turns inherited software risk into savings or into an audit settlement. Reconciliation crosses procurement, IT, software asset management, finance, and the deal team, and when ownership is split across all of them it usually belongs to none of them. Who owns license reconciliation after close has to be answered with a named accountable owner, a defined mandate, and the authority to make decisions across both estates, or the work stalls until a publisher forces it. Inherited licensing exposure is usually latent and unquantified in standard due diligence, and an unowned reconciliation lets that exposure sit until it surfaces as an audit after close.
This guide sets out who should own reconciliation after a deal, what the mandate looks like, and how to structure accountability so the work actually happens. It is a governance workstream within post close license reconciliation and underpins every other task in the cluster.
Who owns license reconciliation after close: the accountability gap
The default failure is diffusion. Procurement assumes IT holds the deployment data, IT assumes procurement holds the contracts, finance sees only the invoices, and the deal team moves on to the next transaction. Each function holds one piece, none holds the whole, and the reconciliation falls into the gap between them. A publisher audit is often the first event that forces the pieces together, by which point the measurement and the timetable belong to the publisher. The fix is to name a single accountable owner before the gap opens, with a mandate that explicitly spans both estates and every function the work touches. The cost of leaving the question unanswered is set out in post close license true up risk.
The case for software asset management as owner
The function best placed to own reconciliation is usually software asset management, because it already sits at the intersection of deployment and entitlement. SAM understands both what is installed and what was bought, speaks the publishers counting logic, and can hold the combined position as a living record rather than a one time exercise. Where a mature SAM function exists in either organisation, giving it the mandate and the authority across both estates is the cleanest answer. Where it does not, the buyer either builds the capability or brings in an independent advisor to hold the position through the integration and hand it to a named internal owner at the end. Either way the principle holds: one owner, one position, one source of truth.
Key takeaways
- Reconciliation crosses procurement, IT, software asset management, finance, and the deal team.
- When ownership is split across every function it usually belongs to none of them.
- A single named accountable owner with a mandate across both estates is the fix.
- Software asset management is usually best placed, sitting across deployment and entitlement.
- An unowned reconciliation lets inherited exposure sit until a publisher audit forces it.
The mandate the owner needs
Naming an owner is not enough without the authority to act. The mandate has to include access to both estates contracts and deployment data, a budget for tooling and advisory support, a seat in the integration governance so reconciliation decisions are sequenced with infrastructure decisions, and the authority to direct procurement and IT on license matters. Without that authority the owner becomes a reporter of problems rather than a resolver of them. The mandate should be set in the first weeks after close, while the integration structure is still being formed, so reconciliation has standing rather than being bolted on late. This sits inside the wider sequencing of the post close reconciliation project plan.
From project owner to standing owner
Reconciliation has two ownership phases. During the integration it is a project with intensive measurement and resolution work, and it needs a project owner with the time and the mandate to drive it. Once the combined position is measured and the gaps are closed, it becomes a standing responsibility that has to be maintained, because an estate drifts back into exposure within a year if no one keeps the position current. The handover from project owner to standing owner is itself a decision the plan should name, so the maintained position has a home after the integration team disbands. Measuring whether the work paid off is covered in measuring reconciliation savings and risk reduction.
Recommendations for buyers
- Name a single accountable owner for reconciliation in the first weeks after close, before the accountability gap opens.
- Give software asset management the mandate where a mature function exists in either organisation.
- Grant the owner authority across both estates, a budget, and a seat in integration governance.
- Use an independent advisor to hold the position through the integration where internal capability is thin.
- Name the handover from project owner to standing owner so the maintained position has a home.
- Set a review cadence so the reconciled position does not drift back into exposure within a year.
Signs the ownership question has not been answered
It is usually easy to tell when no one truly owns reconciliation, because the symptoms are consistent. There is no single combined license position, only fragments held in different functions. Renewal decisions are made one publisher at a time with no view of the whole. Nobody can say what the combined exposure is to within an order of magnitude. The first detailed measurement of a publisher happens only when that publisher sends an audit notice. And the question of who is accountable produces a list of functions rather than a name. Any one of these is a sign that the accountability gap has opened and that inherited exposure is sitting unmeasured.
The remedy is the same in every case: name the owner, give the mandate, and set the review cadence. Ownership is not a document, it is a person with the authority and the time to hold the position and keep it current as the estate changes.
Why an independent advisor holds the position
In many deals the cleanest answer to who owns reconciliation during the integration is an independent, buyer side advisor who holds the combined position, drives the measurement and resolution, and hands a maintained position to a named internal owner at the end. Acting only for the acquirer, with no affiliation to any publisher or reseller, the advisor has no incentive to sell more licenses and every incentive to close the exposure on the buyer terms. That independence is what keeps the ownership question from collapsing back into the accountability gap it was meant to fill.
Operating models and the handover to business as usual
There are three common operating models for who owns license reconciliation after close, and the right choice depends on the buyer structure. A central software asset management function works well for an acquirer that already runs mature SAM, since reconciliation becomes an extension of an existing capability with the tools and skills in place. An integration management office owns it well when the deal is large and reconciliation has to be sequenced tightly with infrastructure consolidation, because the office already holds the authority to direct both. A procurement led model fits when the main exposure is commercial and the priority is renewal leverage rather than technical deployment counting. Whichever model is chosen, the owner needs a mandate that spans both estates and the standing to act, not just to report.
The handover from the deal team to the business as usual owner is the moment most exposure is lost. The deal team holds the knowledge of what was discovered in diligence, which inherited terms carry the most risk, and where the change of control clauses bite. If that knowledge is not transferred deliberately to the owner who will run the estate, the buyer relearns it the hard way during the first audit. A clean handover documents the open exposures, the resolution decisions still pending, and the publishers most likely to act, so the standing reconciliation owner starts from the deal team position rather than from zero. This sits inside the wider sequencing of the post close reconciliation project plan.
The cost of leaving ownership unassigned
When no one owns license reconciliation after close, the estate does not stay still, it drifts toward exposure. Users are added without checking entitlement, infrastructure moves without counting the licensing consequence, and inherited terms sit unexamined until a publisher acts on them. The buyer that leaves ownership unassigned is not holding the position steady, it is letting it deteriorate, and the deterioration is invisible until an audit notice makes it visible at the worst time and on the publisher terms.
Assigning the owner early is cheap insurance against that outcome. The owner does not need to resolve everything immediately, but the standing responsibility means someone is watching the position, sequencing the resolutions, and keeping the deal team knowledge alive in the organisation. The cost of the role is a fraction of a single inherited audit settlement, which is why the ownership question belongs in the first weeks after close rather than being deferred until a problem forces it.