The ROI of Software Asset Management is the ratio between the cost of a SAM program and the savings it demonstrates in licensing, separating actual cost reduction, avoided costs, and avoided audit risks. Proof for leadership depends less on the formula and more on evidence: a baseline recorded before the first action, a record of savings per item, and validation of the number by the finance department.
Why is the ROI of Software Asset Management disputed by the finance department?
The ROI of Software Asset Management is often disputed because the IT and finance departments define savings in different ways. For IT, a recovered license is a saving. For finance, savings only exist when actual spending falls below an approved baseline. A number that mixes the two concepts loses credibility at the first budget meeting, even if each item is correct in isolation.
The pressure to prove results is real. Flexera's 2026 State of ITAM report indicates that 48% of organizations underwent manufacturer audits in the last year, and only 36% have complete visibility of their assets.Flexera, 2026With low visibility, IT has difficulty showing where each value came from, and leadership begins to treat SAM as a cost center, not as a margin driver.
The ROI formula is the simple part of the problem: (benefits minus investment) divided by the investment. The complete calculation, with the most commonly used sources of benefit, is in the article about... Differences, integration, and ROI of SAM and ITAM.. This article discusses the next step: how to transform that calculation into a number that leadership accepts, audits, and uses for decision-making.
The three types of economy that leadership separates
Licensing savings are divided into three categories with different accounting treatment: realized savings, avoided costs, and avoided risks. The U.S. agency CMS (Centers for Medicare & Medicaid Services) defines cost savings as "a reduction in actual expenditures below the current cost level to achieve an objective" and cost avoidance as "a reduction in probable future costs that would occur if the proposed solution were not implemented."CMS, IT Governance trainingThe risk avoided is a third class, typical of SAM, linked to exposure in audits.
| Type | What is in SAM? | Impact on the budget | Minimum evidence | Who validates |
|---|---|---|---|---|
| Economy achieved | License not renewed, contract reduced, SaaS subscription canceled, edition downgrade. | It reduces spending compared to the previous year or the current contract. | Contract or invoice before and after, with the same scope. | Finance and purchases |
| Cost avoided | Additional purchase waived due to license reallocation, negotiated adjustment lower than proposed, reduced true-up. | It does not reduce current spending; it prevents a planned increase. | Original proposal or quote and actual contracted amount. | Financial, with approval from the budget owner. |
| Risk avoided | Licensing deficit identified and corrected prior to a manufacturer audit. | No direct impact; reduces contingent liability. | Effective licensing status before and after correction. | Legal, compliance and finance |
The rule of thumb for reporting is to never sum the three categories into a single unlabeled total. Leadership accepts seeing the three numbers side-by-side, but rejects a total that presents avoided cost or avoided risk as if it were a reduction in spending. Separating the categories is what makes Software Asset Management ROI auditable.
The chain of evidence: from baseline to economic record.
The chain of evidence is the set of records that links each reported value to a verifiable document. It has three links: the baseline recorded before the first action, the savings record per item, and the validation of the number by the finance department. If any link is missing, the value may be true, but it is not verifiable.
Baseline before first action
The baseline is a snapshot of spending and licensing position at the moment the program begins. It should record, by manufacturer, the annual contracted value, the number of usage rights, the recorded consumption, and the renewal dates. A baseline created after the first optimizations underestimates the result and, worse, leaves the number open to questioning because there is no way to prove the starting point.
Savings record by item
The savings ledger, also called a savings account, is a list of each license optimization action with its corresponding value and evidence. It replaces the untraceable consolidated spreadsheet and allows finance to audit any line. The table shows the minimum fields of a defensible ledger.
| Field | Expected content |
|---|---|
| Manufacturer and product | Standardized product and edition, as they appear in the inventory. |
| Type of economy | Completed, cost avoided, or risk avoided. |
| Action performed | Removal, relocation, downgrade, cancellation, renegotiation |
| Value and basis of calculation | Price actually contracted, not list price, and reference period. |
| Effective date | Date on which the savings became effective in the contract or invoice. |
| Evidence | Contract, invoice, proposal, reconciliation report, or removal record. |
| Validation status | Pending, validated by finance, or rejected, with the reason. |
Validation by finance department
Validation by the finance department is the link that converts an IT number into a company number. In practice, the accounting department verifies the evidence for each line item, accepts or reclassifies the type of savings, and approves the value for the period. A Software Asset Management ROI validated in this way can be included in the following year's budget planning, which is the strongest proof that leadership recognizes the result.
Potential savings and realized savings in ServiceNow
In ServiceNow, the Software Asset Workspace natively separates potential savings from realized savings, which resolves one of the most common reporting errors. The Optimization and Savings dashboard calculates realized savings from removal candidates in the Closed Complete state and potential savings from candidates who are still open (ServiceNow DocsThe table summarizes the most useful indicators for executive reporting.
| Indicator | Where it is | What does it measure? | Use in reporting |
|---|---|---|---|
| Total actual savings YTD | Optimization and savings dashboard | Cost savings from completed removal candidates this year. | Economic results achieved during the period |
| Cumulative actual savings | Optimization and savings dashboard | Cumulative savings from all completed applications. | Cumulative results of the program |
| Potential savings | Optimization and savings dashboard | Economics for candidates whose applications are not yet finalized | Economic pipeline, never added to the actual amount. |
| Total spend vs. potential savings, top 10 publishers | Optimization and savings dashboard | Spending and potential savings of the ten largest manufacturers | Prioritization of future actions |
| Software true-up cost | Asset Management Executive dashboard | Cost of regularizing what is already in use. | Licensing exhibition |
| Software success savings | Asset Management Executive dashboard | Real savings from completed SAM targets. | Monitoring of goals agreed upon with leadership. |
The Asset Management Executive dashboard brings together SAM, HAM, and Cloud Cost Management indicators into a single view, making it easier to present the topic to an executive committee without creating separate reports.ServiceNow DocsHowever, the values depend on the quality of the cost registered in the usage rights and the inventory that feeds the reconciliation. If the cost of each entitlement is incorrect, the dashboard reports an accurate number for an incorrect piece of data.
The origin of this evidence lies in the SAM reconciliation and optimization processes. Reconciliation calculates the effective licensing position by comparing installations and consumption with acquired rights. Optimization creates removal candidates from reclamation rules and usage data, and each completed candidate generates a traceable savings record. Therefore, the inventory maintained in a CMDB Governed governance is a condition for the number to withstand an internal audit.
4MATT, a ServiceNow Elite Partner in Brazil with over 110 certified specialists, implements and operates SAM programs in ServiceNow; this practice was recognized by ServiceNow in... Validated Practice in SAM. More details about the scope are on the page. software asset management (SAM).
How to prepare an executive ROI report for Software Asset Management.
The executive ROI report for Software Asset Management works best in three cadences, each with a specific audience and question. The monthly cadence serves operations, the quarterly cadence serves IT leadership and finance, and the annual cadence tracks the renewal and budget cycle.
| Cadence | Public | Question answered | Content |
|---|---|---|---|
| Monthly | SAM team and ITAM manager | Is the economic pipeline moving? | Open and completed applications, potential savings, items pending validation. |
| Quarterly | CIO, controllership and purchasing | How much evidence did the program provide, and how much did it cost? | Validated savings, cost avoided, risk avoided, program cost, and ROI for the period. |
| Annual | Board of Directors and Budget Committee | What changes in next year's budget? | Cumulative results, renewals for the following year, savings targets, and audit risks. |
The quarterly report should show the program's investment with the same rigor as the economics. This includes the tool subscription, deployment and operation services, internal team hours, and the cost of content and integrations. An ROI that hides the program's cost is discarded as quickly as one that inflates the economics.
Renewals by major manufacturers are the moment when results are most visible. A price adjustment announced and negotiated downwards, for example, is a cost avoided, not a savings achieved, and should appear as such in the report. The article about... Microsoft 365 price adjustment in 2026 This shows how this type of event affects the software budget.
Mistakes that cause leadership to reject the number.
The reporting errors that most undermine the credibility of Software Asset Management ROI are predictable and avoidable. Almost all of them stem from the same cause: calculating savings using IT logic and presenting them using finance terminology.
- Calculate the savings based on the manufacturer's list price, not the price actually contracted.
- Add potential savings and realized savings together to form the same total.
- Present the avoided cost as a budget reduction.
- Counting the same license twice, once upon removal and once upon subsequent renewal.
- Reporting the full annual savings of a stock that only became valid midway through the period.
- Ignoring repurchase: a removed license that is then repurchased months later is not cost-effective.
- Omitting the cost of the program when calculating ROI.
Each of these errors is corrected by the chain of evidence described above. The item-by-item savings log prevents double counting, the type field separates realized from avoided, and financial validation acts as an independent review before the number reaches management. To broaden the cost perspective beyond the software, see the... IT asset optimization practices in 2026.
Frequently asked questions about ROI of Software Asset Management
How to calculate the ROI of Software Asset Management?
The ROI of Software Asset Management is calculated as (benefits minus investment) divided by the investment, based on a baseline recorded before the start of the program. Benefits should be separated into savings realized, costs avoided, and risks avoided, and the investment should include tools, services, internal hours, and integrations.
Does the avoided cost count towards licensing savings?
Cost avoidance is a legitimate benefit, but it is not a reduction in spending. It represents an increase that was planned but did not occur, such as an additional purchase that was avoided due to license reallocation. It should appear in the report on a separate line, distinct from the savings achieved.
Who should validate the savings generated by SAM?
The savings must be validated by the finance or accounting department, with support from purchasing for contracts and from legal and compliance for audit risk. Validation provides evidence for each line item in the savings record and is what allows the number to be included in the following year's budget.
What is the difference between potential savings and realized savings in ServiceNow?
In ServiceNow's Software Asset Workspace, realized savings come from completed removal candidates (Closed Complete), while potential savings come from candidates that are still open. Potential savings are part of the program's pipeline and should not be added to realized savings.
How often should SAM's ROI be reported to leadership?
The most common practice is to monitor the pipeline monthly with the SAM team, report the validated results quarterly to the CIO and finance, and consolidate the accumulated data annually, aligned with the contract renewal cycle and budget planning.
Does the risk of audit avoidance factor into ROI?
It falls under its own category, with no direct impact on the budget. A licensing deficit corrected before an audit reduces a contingent liability, but the amount depends on the actual licensing position determined and should not be added to the savings achieved. To understand the relationship between SAM and the rest of the asset lifecycle, see the page on ITAM.