Software reconciliation for compliance compares the rights you own with the installs, subscriptions and users your environment actually consumes. It runs weekly by default, can be started on demand for one publisher or all publishers, and produces results that show compliance status, true-up cost and the remediation options open to you. The sections below explain how to read them.
What the reconciliation compares
Reconciliation works from two sides. The first is the entitlements, meaning the rights you have bought and recorded as active. The second is the consumption discovered in your environment: installed software, assigned users and subscriptions. For each software product, the process counts how many rights are in use and sets that figure against the number of active rights purchased. Compliance status is calculated by comparing the rights in use with the active rights purchased, and the over-licensed amount gives the estimated cost of rights that are not being used.
Groups and subgroups let you cut the same calculation by country, department, company, region or cost center. The defaults that apply to the weekly run are set in the software asset properties. Group and subgroup values (country, department, company, region or cost center) are recorded on each reconciliation run, so the results show which slice of the estate the run covered.
An installation with no matching entitlement is counted as an unlicensed install. Those counts feed the true-up figure, so a gap in entitlement records appears as a cost in the results. Vendor-specific rules are covered on the publisher license reconciliation page.
Running a reconciliation in the workspace or classic view
Two routes start a run, and they suit different environments. The table below sets out the differences.
| Route | Where to start | Role required | Notes |
|---|---|---|---|
| Software Asset Workspace | Software asset overview, or License usage, then Run Reconciliation | sam_user or sam_admin | A domain filter appears when domain separation is enabled. Results appear in the Reconciliation tab. |
| Software Asset Management classic | All > Software Asset > Reconciliation > Run Reconciliation | sam_admin | Requires the legacy SAM module. If the classic menu is not visible, use the reconciliation task in the workspace. |
In the workspace, choose one publisher or all publishers, optionally narrow by group or subgroup, and select Run Reconciliation. Once the run completes, the results are listed in the Reconciliation tab. In classic, choose publishers or all, set the group and subgroup if you want them, and select Continue.
A manual run takes time, and a classic run can take an extended amount of time to finish. Reconciliation covers products that have software entitlements or installs. Selecting specific publishers gives faster results, so narrow the scope first when you need an answer sooner.
Reading product, model and metric results
Reconciliation output has three tiers, and each tier answers a narrower question than the one above it.
Product results are generated for each licensable product after a run, even without a software model. They show compliance status, true-up cost, over-licensed amount, potential savings and install counts. For SAP products, the unlicensed list shows unlicensed users or engines instead.
Software model results exist where a software model or an entitlement exists for the product. Each record carries its own status, unlicensed installs, true-up cost, over-licensed amount and potential savings. Depending on the product, the related lists add remediation options, unlicensed consumptions for consumption-based models, unlicensed Oracle options and purchase orders. Purchase orders appear when the Procurement plugin is active.
License metric results sit beneath a model and show rights owned, rights used and the allocation breakdown. A model can have several metric results when several licenses are bought for the same software. The Rights Used By tab lists the users or devices consuming rights; it is hidden for the IBM Resource Value Unit metric, which is calculated at product level.
For licensable products, a software model is created automatically when an installation has no matching software model, once the automatic creation property is enabled. A separate property does the same for products that are not licensable.
The License Position report
The License Position report lists compliance for each software model in one place, and you can view and export it. Each row carries the publisher, product, edition, version, model status, license metric, total spend, rights owned, rights used, rights needed, rights available, unlicensed installs, true-up cost, potential savings, over-licensed amount and software model name. The group and subgroup used for the run appear on the form.
| Field | What it measures |
|---|---|
| Rights used | Allocated rights in use, plus rights not allocated but installed |
| Rights available | Rights owned, less rights used |
| Rights needed | Rights required to cover the unlicensed installs |
| True-up cost | Estimated cost of fixing non-compliance using the fewest rights needed |
| Potential savings | Estimated savings from reclaiming unused installs |
| Over-licensed amount | Total cost of rights that are not being used |
Two reports can appear for one model. If a model has a perpetual license with Software Assurance and a subscription entitlement, the run generates two metric results, one with active maintenance set to true and one set to false, and therefore two position reports. Unlicensed installs and unlicensed subscriptions in the same model produce a separate report each.
Choosing a remediation path
Model results list remediation options beyond buying new licenses, and the options follow what the numbers show. When rights are in use but not allocated, the run creates Create Allocations and Remove Unallocated Installs for each unique license metric. User CAL and Device CAL metrics are excluded from that pair. When allocated rights are not in use, because the user or device holding them does not have the software installed, a Remove Allocations option appears. The Allocations needed figure applies only to Per Named User and Per Named Device metrics.
Removal candidates handle the reclaim side. They are created from reclamation rules or added manually, and they carry a justification: Low Usage (the default), Unallocated, Unlicensed or Restricted Software. Each candidate moves through states that run from Attention Required and Ready, through Awaiting User, Awaiting Approval and Awaiting Revocation, and end at Closed Complete, Closed Skipped or Closed Canceled. The potential savings figure reflects what you recover once candidates are reclaimed.
With the Procurement plugin active, model results also offer purchase orders. Remediation options sit beside the model’s true-up cost and potential savings figures, so read those figures together before choosing an option.
How license types change the result
The license type on each entitlement changes what the reconciliation counts. The table below summarizes the main cases.
| License type | Effect on reconciliation |
|---|---|
| Perpetual | Grants indefinite use without maintenance rights. Maintenance or Software Assurance entitlements must be linked to it before they count. |
| Perpetual with Software Assurance (Microsoft) | Microsoft-specific Software Assurance treatment is covered on the publisher license reconciliation page. |
| Subscription | Unlicensed subscriptions appear in their own Unlicensed Subscriptions related list on the product results record. |
| Perpetual with maintenance (non-Microsoft publishers) | The cost of a maintenance entitlement linked to a perpetual entitlement is included in the total cost when reconciliation runs. |
| Upgrade and step-up | Related versions are linked on the Upgraded Entitlements tab of the software entitlement form, which is where a standard version is linked to its upgrade or step-up to an enterprise edition under active maintenance. |
| Software Assurance and maintenance entitlements | Not reconciled on their own. They must be linked to a base perpetual license. |
| Add-on and From SA (Microsoft 365) | Recorded as their own entitlements, which track the From SA and Add-on licensing terms of Microsoft 365 subscription products. |
Products installed on AWS or Azure add cloud fields, including the cloud provider, Azure concurrent rights, shared or dedicated host type and edition flexibility for Windows Server and SQL Server. This field appears only with dedicated hosts on AWS or Azure and marks licenses bought before 1 October 2019, since dedicated-host rules depend on purchase date. The Virtualization Adapter applies compliance rules to products running on virtualization technologies.
Keeping the position current
The License Workbench is a simplified view of the same reconciliation results, with color-coded publisher cards. Each card shows the compliance status, the percentage of compliance and the key financial figures, and selecting a card opens that publisher’s details page. Publishers can be pinned per user, and pinned publishers are displayed first. It also trends rights consumed against rights purchased, so you can buy before consumption exceeds ownership.
On upgrade to the Yokohama release or later, reconciliation script includes moved into the Software Asset Management store application, which activates automatically with the Software Asset Management Professional or Foundation plugin. Customized script includes must be moved to the new ones, because the old ones are deprecated. Related guides sit on the Software Asset Management Professional hub.
Frequently asked questions
How often does reconciliation run?
It runs weekly by default and can also be started on demand for one publisher, all publishers, or a group and subgroup. Microsoft, IBM and Oracle specifics are covered on the publisher license reconciliation page.
Who can read the reconciliation results?
Users with the sam_user role can view the results. Starting a run in the workspace needs sam_user or sam_admin, while a classic run needs sam_admin.
Why does a product appear with no software model?
Product results are generated for licensable products whether or not a model exists. A model results record is created only when a model or an entitlement exists for the product.
What is the difference between true-up cost and potential savings?
True-up cost estimates the cost of closing a non-compliance gap using the fewest rights needed. Potential savings estimates what you recover by reclaiming unused installs.