SAP licensing, four models running at the same time
SAP licensing is not one contract: it is five product families and four pricing models, named users for people, engine metrics for products, digital access for documents other systems create, and FUE subscription under RISE, and most estates run at least three simultaneously. The models interact, and the interaction is where budgets go wrong.
Prepared by Redress Compliance · August 7, 2026 · SAP advisory. Based on 35 to 45 SAP licensing reviews run 2024 to 2025.
Executive summary
Classification, not headcount, drives the user bill.
Every person touching SAP needs a named user license matched to a tier, and the spread is brutal: a Professional user lists at $4,500 to $6,500 against $180 to $300 for Employee Self Service, more than twenty times apart, with 19 to 22 percent annual support riding on whatever was paid, forever.
Across our reviews, unused and misclassified entitlement ran 20 to 30 percent of the named user base, accumulated through template defaults, role drift, and duplicate identities.
Engines meter beside the users. Products like Payroll and BW bill on their own metrics, orders, employees, revenue, memory, measured against baselines that in our estates no longer matched the deployment.
And service accounts are a contractual trap: many SAP agreements license each integration account as a Professional user, so every middleware connection and RFC user can carry a full fee. Read your definition before assuming a technical user is free, and count them before SAP does.
Digital access is the API question. Non SAP systems creating SAP documents trigger their own licensing across nine document types, two weighted at 0.2, independent of user counts, and the exposure stayed undocumented in most estates until an audit surfaced it.
The model applies to ECC and S/4HANA alike, in every deployment.
Cloud changes the metric, not the discipline.
Under RISE the estate prices as Full Use Equivalents, but classification still rules: the FUE conversion is built from the named user mapping, so a user cleanup changes the FUE math of a future RISE deal, an engine baseline feeds the audit.
And a digital access position priced on its own is a position priced badly.
The four models negotiate as one estate or they negotiate against you.
The named user tiers, and the observed price bands
| User type | Access rights | Observed list band |
|---|---|---|
| Professional | Full functional access across modules: configure, customize, transact | $4,500 to $6,500 |
| Limited Professional | Operational access on defined modules | $1,900 to $2,400 |
| Employee User | Self service: view own data, submit requests | $350 to $550 |
| Employee Self Service | Specific ESS scenarios only | $180 to $300 |
| Developer | ABAP development and configuration | $8,000 to $12,000 |
SAP stopped publishing a price list years ago. These bands are what we have seen on order forms and quotes across 2024 to 2026 engagements, before discount: the shape of the price list rather than the price list.
The arithmetic they carry is durable, one Professional user costs the same as 25 ESS users at the bottom of both bands, and a Professional bought at $6,500 carries $1,430 of Enterprise Support every year at 22 percent for as long as it stays on the contract.
How misclassification creeps, and where it corrects
Misclassification is rarely one bad decision; it accumulates. New accounts inherit the license type of a template user built on a Professional profile years ago. A user set up for full transactional work now only approves invoices, and the tier never moves down.
The same person holds accounts in ECC, BW, and a sandbox and counts three times unless LAW consolidation matches them.
The correction points are contractual: match each user to the lowest tier their real activity needs, remove inactive and duplicate accounts before any measurement, and reclassify at the annual system measurement, which is your right.
The tier definitions and the reclassification mechanics are worked in the named user types guide, and the measurement tooling SAP will run on you, USMM, LAW, and their successors, in the compliance tools guide.
The SAP negotiation fundamentals brief
The negotiation the licensing map feeds: the timing calendar, the discount ranges by deal type, and the clause set that survives the first term.
Get the white paper →The four models, and how they interact
| Model | What it licenses | Metric | Where it applies |
|---|---|---|---|
| Named users | People who log in | Classification tiers | ECC and S/4HANA on premise |
| Engine metrics | Products and modules | Orders, employees, revenue, memory | Perpetual estates and some cloud add ons |
| Digital access | Documents created by external systems | Nine document types, two weighted at 0.2 | ECC and S/4HANA, both deployments |
| FUE subscription | The whole estate as one number | Full Use Equivalents | RISE with SAP and S/4HANA Cloud |
Each model has its own deep treatment on the cluster: the Digital Access complete guide for the document meter, the FUE optimization guide for the conversion math, one FUE covering one advanced user, five core users, or thirty self service users.
And the HANA licensing analysis for the runtime versus full use decision underneath the database.
The interaction is the point: the named user cleanup runs before the FUE conversion, the engine baselines re-measure before the audit, and the digital access position prices inside the larger deal, never alone.
- 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 reviews, 2024 to 2025
Across 35 to 45 SAP licensing reviews run between 2024 and 2025, the money was in the same place almost every time:
Of the named user base: inactive accounts, duplicates, and tiers that never moved down after role changes.
The document exposure undocumented in most estates until SAP's measurement quantified it first.
The engine finding was quieter but persistent: metrics measured against baselines that no longer matched the deployment, in both directions, and nobody reconciling until a renewal or an audit forced it.
The audit posture that results, and the response sequence when the letter arrives, is worked in the audit survival guide; the support line the fees compound into, and how to negotiate it, in the support negotiation guide.
And the negotiation all of it feeds, timing, ranges, and the clauses that outlast the price, in the contract negotiation playbook.
Your first five moves
- Reconcile the named user base first: inactive accounts out, duplicates matched, tiers moved to real activity, the 20 to 30 percent that funds everything else.
- Count the service accounts against your contract's definition, because each middleware connection may carry a Professional fee.
- Re-baseline the engine metrics against the current deployment, before the annual measurement does it on SAP's numbers.
- Document the digital access position yourself: nine document types counted from your integrations, before an audit counts them for you.
- Run the cleanup before any RISE conversation, because the FUE conversion inherits whatever the user base says. The SAP practice runs the sequence with you.
Frequently asked questions
How does SAP licensing work in 2026?
Through four models running simultaneously: named user licenses classified by usage tier, engine metrics billing products on their own measures, digital access charging for documents created by non SAP systems, and FUE subscription under RISE for the cloud.
Most estates run at least three at once, and the models interact at every renewal, audit, and conversion.
What do SAP named user licenses cost?
Observed list bands before discount: Professional $4,500 to $6,500, Limited Professional $1,900 to $2,400, Employee $350 to $550, Employee Self Service $180 to $300, and Developer $8,000 to $12,000, with 19 to 22 percent annual support riding on each fee.
SAP no longer publishes a price list, so these are the shape from real order forms, not a tariff.
What is the most common SAP licensing waste?
Misclassified and unused named users: 20 to 30 percent of the base across our reviews, from template defaults inheriting Professional profiles, role drift that never re-tiers, and duplicate identities across systems.
The correction is contractual, reclassification at the annual measurement is your right, and it reprices both the support line and any future FUE conversion.
Are SAP service accounts licensed?
Often yes, and expensively: many SAP agreements license each integration service account as a Professional user, so middleware connections, RFC users, and batch accounts can each carry a full fee.
Read the definition in your own contract before assuming a technical user is free, and inventory them before SAP's measurement does.
What is SAP digital access?
The model charging for documents created in SAP by external systems, across nine document types with two weighted at 0.2, independent of named user counts.
It applies to ECC and S/4HANA in every deployment, and in most estates we reviewed the exposure stayed undocumented until an audit surfaced it, which is the expensive way to learn the count.
How does RISE change SAP licensing?
It replaces the perpetual metrics with a Full Use Equivalent subscription covering the estate as one number, but the discipline carries over: the FUE conversion is built from the named user mapping, so classification still rules.
And a user cleanup run before the conversion permanently lowers the subscription base it produces.
S/4HANA Negotiations: The Discount Is Dead. The Tier Is the Deal.
SAP moved from ad-hoc discounting to tier-based pricing: the FUE band sets the rate. Negotiating the band edges, the user-type mapping as the hidden discount, what remains genuinely negotiable, and protecting the tier at renewal.
