A post close reconciliation project plan is the difference between reconciliation that lands savings and a publisher audit that lands first. After a deal closes, the combined organisation has two software estates, two sets of agreements, and a window in which to measure, deduplicate, and consolidate before the first true up or audit notice arrives. A post close reconciliation project plan sequences that work into phases with owners, milestones, and a clear measured position at the end, so the buyer controls the timetable rather than the publishers. Inherited licensing exposure is usually latent and unquantified in standard due diligence, and without a plan it surfaces as an audit after close on the publisher schedule instead of being resolved on the buyer schedule.
This guide sets out a post close reconciliation project plan a buyer can run from day one. It is the operating backbone of post close license reconciliation and connects every other workstream in the cluster.
Post close reconciliation project plan: the phases that matter
A reconciliation plan moves through five phases. Inventory comes first, because nothing can be reconciled that has not been found, and the combined estate is never fully visible on day one. Entitlement reconstruction follows, gathering every agreement, amendment, and proof of purchase across both organisations. Measurement counts the combined deployment to each publisher exact logic and compares it to entitlement. Resolution closes the gaps, strips the overlaps, and sequences consolidation to the right renewals. Governance hands the maintained position to a named owner so it does not drift back into exposure. Each phase has a deliverable, and the plan does not advance until the deliverable exists.
The first phase depends on a disciplined inventory, which is the work of post close software inventory, and the measured output is the combined entity license position. The plan is the thread that connects them.
Owners, milestones, and the first 90 days
A plan without named owners is a wish list. Each phase needs a single accountable owner, a deadline tied to the integration calendar, and a deliverable that can be reviewed. The first 90 days carry the most leverage, because the combined estate is still fresh, the people who understand each system are still present, and no true up has yet locked the spend in. A plan that front loads inventory and entitlement reconstruction in those first weeks puts the buyer in measurement before the first publisher milestone arrives. The detail of that early window is set out in the first 90 days reconciling software after close.
Key takeaways
- A post close reconciliation project plan sequences inventory, entitlement, measurement, resolution, and governance.
- Each phase has a single accountable owner, a deadline, and a reviewable deliverable.
- The first 90 days carry the most leverage, before any true up locks the spend in.
- The plan does not advance until each phase deliverable exists, which keeps measurement honest.
- Without a plan, inherited exposure surfaces as an audit on the publisher schedule, not the buyer schedule.
Sequencing publisher work by risk
Not every publisher deserves equal urgency. The major audit risks after a deal come from Oracle, SAP, Microsoft, IBM, and increasingly Broadcom for VMware, Salesforce, and ServiceNow, as observed across recent audit activity as of 2026. A good plan sequences the measurement work by exposure, taking the publishers most likely to audit and most expensive to get wrong first. Oracle and SAP usually lead because their metrics are complex and their audit practice is aggressive, followed by Microsoft where the true up captures growth automatically. The plan allocates the scarce early weeks to the publishers where a measured position is worth the most, rather than spreading effort evenly across an estate where most of the risk sits with a few names.
Resolution and governance
Resolution is where the plan pays out. With the combined position measured, the buyer closes any shortfall on its own terms, strips the overlapping spend, and sequences consolidation to the renewals that capture the best pricing. Governance keeps the result. A reconciled estate drifts back into exposure within a year if no one owns it, so the plan ends by assigning a named owner, a review cadence, and the tooling to keep the position current. Without governance the buyer pays for the same reconciliation again at the next deal. The ownership question is treated in full in who owns license reconciliation after close.
Recommendations for buyers
- Front load inventory and entitlement reconstruction into the first weeks, while the people and records are fresh.
- Assign a single accountable owner and a reviewable deliverable to each phase of the plan.
- Sequence the measurement work by exposure, taking Oracle, SAP, and Microsoft first.
- Hold the plan at each phase until its deliverable exists, so measurement is never skipped.
- Resolve shortfalls and strip overlaps before the first true up or audit notice arrives.
- End the plan with named governance, a review cadence, and tooling so the position does not drift back.
How the plan handles surprises
No reconciliation plan survives contact with a real estate unchanged, so a good plan is built to absorb surprises rather than be derailed by them. The common surprises are an inventory that turns up software no one knew was deployed, entitlement records that cannot be located for a material agreement, and a true up or audit notice that arrives mid plan. The plan handles each by sequencing the highest exposure publishers first, so the most dangerous unknowns are measured early, and by keeping a documented position at every phase, so a notice that arrives mid plan is met with a partial measured position rather than nothing. A plan that front loads risk is far more resilient than one that works through the estate alphabetically.
The discipline that makes this work is the deliverable gate. Because each phase produces a reviewable artefact before the next begins, a surprise in any phase is contained to that phase rather than propagating through the whole programme. The plan bends, it does not break.
Why an independent advisor runs the plan
A post close reconciliation plan succeeds when it is driven to a measured position before the publishers move. An independent, buyer side advisor brings the sequence, the publisher counting logic, and the discipline to hold each phase to its deliverable, with no affiliation to any software publisher or reseller. That independence is what keeps the plan focused on the buyer outcome, a controlled and lower cost combined estate, rather than on selling more licenses.
A phased timeline and how to resource it
A workable post close reconciliation project plan runs across the first two quarters after close in clear phases. The first weeks are inventory and access, where the team secures both estates contract sets, entitlement records, and deployment data, and resolves the access rights that let it see across two organisations. The following weeks are measurement, where the combined position is built publisher by publisher against each agreement counting logic. The middle of the timeline is resolution, where shortfalls are closed and overlaps removed on the buyer terms. The final phase is governance, where a named owner, a review cadence, and the tooling to keep the position current are put in place so the estate does not drift back into exposure.
Resourcing decides whether the plan holds. Reconciliation needs a lead with the authority to direct procurement and IT, analysts who can reproduce publisher counting models, and access to both estates data without waiting on system integrations that may take months. Many buyers underestimate the contract gathering effort, which is often the slowest part because agreements sit in different repositories, languages, and formats across the two companies. The plan budgets for that effort explicitly and assigns the ownership question early, which is treated in full in who owns license reconciliation after close.
Milestones that show the plan is working
A post close reconciliation project plan needs visible milestones, because an integration with many moving parts will deprioritise reconciliation unless its progress is tracked. The first milestone is a complete contract and entitlement inventory across both estates, which proves the team can see what it has bought. The second is a measured combined position for each major publisher, which converts the inventory into a quantified exposure. The third is a resolution plan with owners and dates for each shortfall and overlap. The fourth is a governance model in place, with a named owner and a review cadence, so the position stays current after the project team disbands.
Tracking against these milestones keeps reconciliation visible to the integration leadership and protects the budget for it. A plan that reports only activity, rather than these outcomes, tends to lose priority to more visible integration tasks, and the exposure it was meant to resolve surfaces later as an audit. Tying each milestone to a quantified figure, the exposure found and the spend removed, is what keeps reconciliation funded to completion.