License reconciliation tooling and methods are often confused, and the confusion is expensive. Tooling discovers what is installed and running across the combined estate. Methods turn that raw deployment data into an effective license position by matching it against entitlement, applying each publisher's specific counting rules, and resolving the gaps with judgment. A buyer who buys a discovery tool and expects a compliance answer gets a data dump. A buyer who pairs the right tooling with disciplined method gets a position that holds up when a publisher tests it. This page explains where the tools end and the advisory work begins, as part of post close license reconciliation.
What license reconciliation tooling and methods each contribute
License reconciliation tooling and methods do different jobs that only add up when combined. Tooling answers the question of what is deployed: which products are installed, on which hardware, used by how many people, across both companies. Methods answer the harder questions: what the combined entity is actually entitled to under its agreements, how each publisher counts that entitlement, and where deployment exceeds it. Discovery is necessary and not sufficient. The reason is simple. Entitlement lives in contracts, not on servers, and the rules that convert a server count into a license requirement are publisher specific, frequently undocumented, and change with editions and metrics. No scanner knows your contract terms.
The tooling layer: what discovery does well
Good discovery tooling earns its place. It inventories installed software across servers, desktops, and cloud, normalises product names to a recognised catalogue, captures usage metrics like active users and processor cores, and reads cloud consumption from provider consoles. After a deal it is the fastest way to see across two estates that were never managed together. The categories of tool worth knowing are inventory and discovery platforms, software asset management suites that add entitlement tracking, and cloud cost tools that read consumption directly. None of them, on their own, tells you whether you are compliant, because none of them holds your contracts or knows how a given publisher counts.
| Tool category | What it captures | What it cannot do |
|---|---|---|
| Inventory and discovery | Installed software, hardware, usage metrics | Match deployment to contract entitlement |
| Software asset management suite | Discovery plus entitlement records | Resolve ambiguous or disputed metrics |
| Cloud cost and consumption | Subscription and usage spend | Identify indirect access exposure |
| Publisher verification scripts | Vendor view of deployment | Protect the buyer's interest |
Note the last row. Some publishers offer their own measurement scripts. These produce the vendor's view of your deployment, framed to support the vendor's position, and should never be the buyer's only source. Running a publisher's script and reporting its output as your position hands the publisher the negotiation.
Key takeaways
- Tooling discovers what is deployed; methods turn that into an effective license position by matching it to entitlement and publisher counting rules.
- No scanner knows your contracts, so discovery data alone is a data dump, not a compliance answer.
- Publisher provided measurement scripts give the vendor's view and must never be the buyer's only source.
- The hardest gaps, indirect access and ambiguous metrics, are resolved by method and judgment, not by a tool.
- A defensible position documents its data sources, assumptions, and counting decisions so it survives a publisher challenge.
The methods layer: where judgment is decisive
The method layer is where reconciliation becomes defensible. It starts by assembling entitlement from every agreement across both companies, including the buried terms and inherited settlements that tools cannot see. It then applies each publisher's counting rules to the deployment data, which is where expertise matters most. Oracle counts processors with core factors and has views on virtualization that can multiply a requirement. SAP distinguishes named users by type and has indirect access exposure that no installed software scan detects. Microsoft varies by metric across editions and agreement types. Getting these conversions right is the whole game, and it is covered product by product in pages like reconciling Oracle licensing after a merger and reconciling SAP licensing after a merger.
The gaps no tool closes
Two exposures defeat tooling entirely and have to be handled by method. The first is indirect access, where a third party system or a person reads data from a licensed platform without a direct login, which SAP and others treat as a licensable use. No installed software scan sees it, because nothing is installed. The second is ambiguous or disputed metrics, where the contract language and the publisher's interpretation diverge, and the right answer depends on negotiation history and case knowledge rather than a count. These are exactly the gaps that surface as eight figure claims, which is why they belong to the advisor and not the tool. The risk is set out in reconciling cloud entitlements across entities.
What a defensible position documents
The output of good method is not a number but a documented position. It records every data source and its date, every assumption made, every counting decision and the contract clause that supports it, and the residual uncertainty where interpretation is open. That documentation is what lets the buyer defend the position when a publisher challenges it, and what lets the deal team trust the exposure figure. A position presented as a single number with no working is a position that collapses under the first pointed question. The same evidential discipline underpins building the combined entity license position.
Recommendations for buyers
- Use tooling for discovery, not for compliance. Let it tell you what is deployed, then apply method to decide what it means.
- Never rely on a publisher's own script. It gives the vendor's view; keep an independent source the buyer controls.
- Assemble entitlement from every agreement. Include buried terms and inherited settlements no scanner can see.
- Handle indirect access and disputed metrics by judgment. These are the gaps that become large claims, and no tool resolves them.
- Document sources, assumptions, and counting decisions. A defensible position shows its working and survives a challenge.
License reconciliation tooling and methods together produce a defensible result
License reconciliation tooling and methods are partners, not substitutes. Tooling gives you speed and reach across two estates. Method gives you a position you can defend, by matching deployment to entitlement, applying publisher specific counting rules, resolving the gaps that scanners cannot see, and documenting every decision. Buy a tool and skip the method and you have a data dump. Combine them with discipline and you have an effective license position that protects the deal. We bring both, from the buyer's side only, paid solely by the acquirer, and we write the position so it holds when a publisher tests it.