The savings are in arguments, not reports
SAP license optimization is seven specific levers, and most estates can move 15 to 30 percent of the bill without touching the landscape. The recoverable money sits in positions you can defend with usage evidence: whether a user's activity profile justifies Professional, how an engine metric is counted, what a billable document actually is. Tools surface candidates. Contract arguments produce the saving.
Prepared by Redress Compliance · August 10, 2026 · SAP advisory. Based on 25 to 35 SAP estates optimized, 2024 to 2025.
Executive summary
Named user reclassification moved 20 to 40 percent of Professional users to cheaper types after activity analysis. Named user spend optimises through matching each user's licence type to what they actually do in the system, and the activity record rather than the job title is the evidence.
SAP's contractual user definitions are broad, which cuts both ways: the same breadth that lets SAP argue users upward in an audit lets you argue them downward with twelve months of transaction history per user, which is evidence most estates hold and never assemble.
Inactive and duplicate accounts held 10 to 20 percent of named user licences before the first cleanup. Leavers and duplicated identities across systems keep consuming named user licences until they are measured out, and nothing surfaces them automatically.
Alongside reclassification this is the least contested part of the exercise, because no argument about entitlement is required: an account with no logon in ninety days or the same person counted across two systems is a data problem rather than a licensing dispute.
Engines meter on business metrics, so they drift past entitlement without any procurement event to flag it. Package and engine licences count orders, contracts, revenue, cores, and documents, and each of those moves with the business.
Order and document metered engines drift most in growing businesses, and core metered engines drift after an infrastructure refresh.
Measure engine metrics in the same quarterly self check as user counts, challenge the metric mapping where the contract wording leaves room, and retire dead engines the business abandoned but support still renews.
The measurement is the moment, so never submit a USMM or LAW result SAP will read before you have. Estates that reviewed their measurement results before submission avoided compliance findings that averaged six figures in the unreviewed group.
Digital access sits alongside this: it prices indirect use per document created, the estimation tools overstate billable documents where integrations retry or duplicate, and the conversion incentives are a recurring pattern rather than a one off gift.
Position digital access inside a RISE or renewal negotiation rather than as a standalone purchase.
The named user reclassification ladder
| From | To | Typical trigger | Observed share moved |
|---|---|---|---|
| Professional | Limited Professional | Display heavy profiles, single module use | 15 to 25 percent |
| Professional | Employee Self Service | HR and time entry only activity | 5 to 10 percent |
| Any active type | Retired or test | No logon in 90 plus days | 10 to 20 percent |
| Duplicated users | Single identity | Same person across systems | 3 to 8 percent |
Reclassification is decided by twelve months of transaction history per user, which converts a negotiation opinion into a measurement fact.
The evidence needed is specific: which transactions each user runs, in which modules, and how often, across the whole landscape rather than in the system where the licence happens to sit.
SAP's user definitions are deliberately broad, so both sides are arguing from the same text and the side with the activity data wins.
Most estates already hold this evidence in their own systems and have simply never assembled it into a licensing view, which is why the first pass of a reclassification exercise routinely produces a larger movement than anyone expected. The user type mechanics sit in the FUE and user counting guide.
Engines, documents, and the measurement itself
- Measure engines before SAP does. Engine metrics belong in the quarterly self check next to user counts, because orders, contracts, revenue, and core counts all move without a procurement event to flag them.
- Challenge the metric mapping. How a metric is counted is frequently arguable and the contract wording decides it, which makes engine drift a contract question rather than a compliance fact.
- Retire dead engines. Modules the business abandoned still renew in support unless somebody surfaces them, and nothing in the renewal process does that for you.
- Count your documents before discussing digital access, since the estimation tools overstate billable documents where integrations retry or duplicate, and the count is the whole basis of the price.
- Never submit a measurement SAP will read before you have. Estates that reviewed USMM and LAW results before submission avoided findings that averaged six figures in the unreviewed group.
The SAP digital access brief
Document based licensing for indirect use: what counts as billable, where the estimation tools overstate, and how the conversion discount actually behaves.
Get the white paper →Turning optimization into renewal leverage
Optimization findings are renewal currency, and a documented surplus changes the conversation from how much more to how much less, but only if the work lands before the negotiation opens.
Run the full measurement privately first, covering users, engines, and document counts, and treat it as a rehearsal for the measurement SAP will eventually run rather than as an internal reporting exercise.
Reclassify and clean before any number reaches SAP, because a position corrected after submission is a concession rather than a finding and the correction is much harder to argue once it sits in a system of record on the vendor side.
Quantify the shelfware and map it against both the roadmap and the RISE pitch, since unused entitlement is worth most when it can be traded against something SAP wants to sell rather than simply surrendered.
Then open the renewal with the measured position as the baseline and trade the surplus for things SAP can actually give: conversion credits, capped uplifts, and term protections. Timing decides whether any of this works.
The measurement belongs six to nine months before the renewal, because reclassification and cleanup take a quarter to execute and leverage needs the work finished rather than promised.
Digital access positions best inside the same event, since it prices indirect use per document and the conversion incentives recur, which makes them negotiable rather than exceptional.
The audit posture that runs alongside sits in the SAP audit survival guide and the indirect use mechanics in the digital access guide.
- Percentile standing for your exact deal size and industry, from real closed transactions
- Scenario simulation before the call: test alternative terms and see the financial impact of each
- A negotiation playbook, talking points, and a two page executive brief on day one
What we saw across SAP optimization engagements, 2024 to 2025
The standard advice is to buy a SAM tool, run the measurement, and trust the dashboard's savings number.
We disagree, because the recoverable money was in arguments rather than reports: whether a user's activity profile justifies Professional, how an engine metric is counted, what a billable document is:
Share reclassified to cheaper licence types once twelve months of activity data was analysed rather than job titles assumed.
Typical reduction achieved without touching the landscape, from reclassification, cleanup, engine measurement, and document audit.
Three patterns recurred: named user reclassification moving 20 to 40 percent of Professional users to lower types after activity analysis, inactive and duplicate accounts holding 10 to 20 percent of named user licences before the first cleanup.
And estates that reviewed measurement results before submission avoiding compliance findings that averaged six figures in the unreviewed group.
The buyer side move is to treat optimization as a negotiation discipline with a measurement attached rather than as a tooling exercise.
Tools surface candidates; the savings come from contract positions argued with usage evidence, and the evidence has to exist before the conversation rather than after it. The wider library sits in the SAP practice.
Your first five moves
- Pull twelve months of user activity data across the landscape, which transactions, which modules, how often, because that is the evidence a reclassification argument stands on.
- Reclassify users against activity profiles and clean inactive and duplicate accounts, which together moved 20 to 40 percent of Professional users and freed 10 to 20 percent of named user licences.
- Measure every engine metric against entitlement quarterly, since order, document, and core metered engines drift past entitlement with no procurement event to flag it.
- Audit billable document counts before discussing digital access, because estimation tools overstate where integrations retry or duplicate, and the count is the entire basis of the price.
- Land the measured position six to nine months before renewal, and never submit a USMM or LAW result you have not reviewed first. The SAP practice runs the measurement and the renewal with you.
Frequently asked questions
How do you optimize SAP named user licensing?
Through reclassification: matching each user's licence type to what they actually do in the system, with the activity record rather than the job title as the evidence.
Twelve months of transaction history per user, covering which transactions, which modules, and how often, converts a negotiation opinion into a measurement fact that SAP's own broad definitions have to answer.
How much can reclassification move?
In our file it moved 20 to 40 percent of Professional users to cheaper types after activity analysis, with display heavy and single module profiles going to Limited Professional and HR or time entry only activity going to Employee Self Service.
Alongside that, inactive and duplicate accounts held 10 to 20 percent of named user licences before the first cleanup.
Why do engine licences drift past entitlement?
Because they meter on business metrics that move on their own: orders, contracts, revenue, cores, and documents. An engine bought at one volume quietly runs past entitlement years later with no procurement event to flag it.
Order and document metered engines drift most in growing businesses, and core metered engines drift after an infrastructure refresh.
Is digital access cheaper than named users for indirect use?
For order heavy integrations, often not at list, which is why the document count audit and the conversion discount both matter before any signature.
The estimation tools overstate billable documents where integrations retry or duplicate, and SAP has run conversion incentives repeatedly, so the discount is a pattern rather than a one off gift.
Should we submit USMM and LAW results as they come out?
No. Never submit a measurement SAP will read before you have reviewed it. Estates that reviewed results before submission avoided compliance findings that averaged six figures in the unreviewed group.
The measurement is the moment the position becomes visible, and a correction made afterwards is a concession rather than a finding.
When should optimization run relative to the renewal?
Six to nine months out. Reclassification and cleanup take a quarter to execute, and leverage needs the work finished rather than promised.
Findings that land after the negotiation opens are arguments; findings that land before it are a baseline, and only the baseline changes the conversation from how much more to how much less.
Do SAM tools deliver the savings?
They surface candidates. The savings come from contract positions argued with usage evidence: whether an activity profile justifies Professional, how an engine metric is counted under your specific wording, what qualifies as a billable document.
Treat optimization as a negotiation discipline with a measurement attached rather than as a dashboard exercise.
Optimize the Estate First: The SAP Work That Pays for the Negotiation
SAP prices your future from your present, so a bloated estate converts into a bloated subscription. The user cleanup, engine and shelfware rationalization, resolving indirect access on your terms, and converting clean with the credits you earned.
