SAP licensing spans named users, engine metrics, digital access, and cloud subscriptions. This reference pulls the moving parts into one view so a buyer can see where cost and risk actually concentrate.
SAP licensing is not one model but a stack of them, and the cost lives in how user types, engine metrics, and digital access interact rather than in any single price.
Every SAP estate prices through four models: named users for people, engine metrics for products, digital access for documents created by other systems, and FUE subscription under RISE for the cloud. Most estates run at least three of them at the same time.
The SAP licensing model taxonomy
| Model | What it licenses | Metric | Where it applies |
|---|---|---|---|
| Named users | People who log in | User classification tiers | ECC and S/4HANA on premise |
| Engine metrics | Products and modules | Orders, employees, revenue, memory, application value | 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 deployment models |
| FUE subscription | The whole estate as one number | Full Usage Equivalents | RISE with SAP and S/4HANA Cloud |
The models interact, and the interaction is where budgets go wrong. A named 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 sections below take each model in turn. Then the guide works the S/4HANA conversion paths, the measurement tooling SAP will use on you, and the optimization sequence that ties all of it together.
Every individual who uses an SAP system needs a named user license, classified by how they use it. The classification, not the headcount alone, drives the bill.
SAP defines user types in its software use rights and price list documents. Professional, functional, and self service tiers carry very different fees.
Common SAP named user tiers
| Tier | Typical use | Relative cost |
|---|---|---|
| Professional | Full transactional | Highest |
| Functional / limited | Defined tasks | Medium |
| Self service / employee | Occasional self service | Lowest |
Misclassification is rarely one bad decision. It accumulates through role changes, reorganizations, and user creation templates that default to Professional where a lower tier would cover the real activity.
The tier spread is why this matters. A Professional license has historically listed at several times the fee of a functional tier and at a large multiple of employee self service, and 19 to 22 percent annual support rides on each fee for the life of the contract.
SAP stopped publishing a public price list years ago, so the working anchors are ratios and contract mechanics rather than printed numbers. Three anchors hold in almost every estate we see.
Reclassification is contractually clean at the annual system measurement, and nothing obliges you to keep a user at a tier the activity no longer justifies. The full tier catalog is worked through in our named user license types guide.
Beyond users, many SAP products bill on engine metrics tied to volume or capacity. Payroll bills on employee records, some analytics on data volume, and so on.
Engine measurements drift. A metric set years ago may no longer reflect the live system, creating both overpayment and compliance gaps. Check scope against the SAP maintenance and release information for each product.
Engines fall into a handful of metric families, and the family tells you where the drift risk sits. The map below covers the ones that surface most often.
Common SAP engine metric families
| Metric family | Typical products | What drives the count | Where it drifts |
|---|---|---|---|
| Employee based | Payroll, HCM modules | Employee master records, often including inactive ones | Leavers and seasonal staff never archived |
| Document or order based | Order management and industry engines | Documents or orders created per year | Volume grows silently with the business |
| Revenue or spend based | Industry solutions, procurement engines | Contracted revenue or purchase spend bands | Band thresholds crossed without anyone checking |
| Capacity based | SAP HANA full use, database options | Memory in gigabytes or cores allocated | Hardware upgrades reprice the license |
| Percentage of application value | SAP HANA runtime edition | A fixed percentage of the value of the SAP applications it runs | Every new application purchase raises it |
Two of these deserve a closer look, because they carry the largest surprises in the reviews we run.
Payroll style engines count employee master records, not active payslips. Estates that never archive leavers measure well above the true active population, and the whole overage flows into the engine fee and its support.
The HANA runtime edition is priced as a percentage of the value of the SAP applications running on it, not on the database itself. Buy more application licenses and the database fee rises with them, even though nothing changed in the database.
Check which basis your contract uses before any new purchase. The runtime percentage quietly turns every application discount conversation into a database price conversation as well.
Digital access licenses the documents that non SAP systems create in SAP, rather than the humans behind them. It replaced the older indirect use disputes for many customers.
Digital access counts nine document types, seven at full value and two at a 0.2 multiplier, per SAP’s own digital access materials. The transactional types are counted at line item level, not per document header.
SAP digital access document types
| Document type | Counted at | Multiplier |
|---|---|---|
| Sales | Line item | 1.0 |
| Invoice | Line item | 1.0 |
| Purchase | Line item | 1.0 |
| Service and maintenance | Document | 1.0 |
| Manufacturing | Document | 1.0 |
| Quality management | Document | 1.0 |
| Time management | Document | 1.0 |
| Financial | Line item | 0.2 |
| Material | Line item | 0.2 |
Only initial creation is charged. Reads, updates, and deletes are free, and follow on documents generated automatically from an already counted document are not counted again, a rule that materially lowers real exposure against naive estimates.
The weights shape the bill. Estates dominated by financial postings and goods movements measure far lower than the raw document count suggests because of the 0.2 multiplier, while order to cash integrations concentrate cost in sales and invoice line items.
The Digital Access Adoption Program gave existing customers two ways in: license at least 115 percent of the current document volume and pay only for the growth, or license 100 percent of current volume with a 90 percent discount. Document counts were estimated with SAP’s Global License Audit and Compliance team or with the SAP Passport measurement tooling.
The buyer side lesson outlived the program itself. SAP still prices digital access aggressively when it unlocks an S/4HANA or RISE commitment, so treat document conversion as a chip in the larger deal and never as a standalone list price purchase. Our digital access guide works the scenarios document type by document type.
The common advice is to focus negotiation energy on the upfront license discount. We disagree. In roughly 8 of 10 SAP estates we reviewed, the larger lifetime cost sat in support compounding on shelfware and in user misclassification, not in the original discount. A strong discount on licenses you never deploy still funds 20 percent annual support forever. The buyer side move is to right size the base first, strip inactive users and unused engines, then negotiate, so the recurring support line is calculated on what you actually run.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
Discount is a one time event. Support is a tax on everything you bought but never used.
RISE with SAP replaces perpetual licenses and separate support with one subscription measured in Full Usage Equivalents, so the negotiation moves from discount and support percentage to FUE count, user mix, and renewal protection.
An FUE is the normalization unit. Each user type converts to FUE at a fixed ratio published in SAP’s RISE with SAP service use descriptions, and the order form states one FUE total rather than a list of user licenses.
FUE conversion ratios under RISE with SAP
| User type | Users per FUE | FUE per user | Maps roughly to |
|---|---|---|---|
| Advanced use | 1 | 1.00 | Professional users |
| Core use | 5 | 0.20 | Functional and limited users |
| Self service use | 30 | 0.03 | Employee and occasional users |
| Developer access | 0.5 | 2.00 | Full development authorizations |
The ratios make the mix, not the headcount, the price driver. Moving 100 users from advanced to core classification releases 80 FUE, while a single developer consumes as much subscription as two advanced users.
Engines and digital access do not disappear under RISE. Some are absorbed into the FUE metric and others are priced as separate cloud services, so reconcile every engine on the legacy contract against the RISE order form line by line. Our cloud licensing models guide maps the subscription catalog.
There are three realistic paths off ECC: a product conversion that swaps licenses into S/4HANA equivalents, a contract conversion that restructures the whole agreement, and a move to RISE subscription, and each reprices the estate differently.
A product conversion exchanges individual licenses for their S/4HANA counterparts and leaves the rest of the contract standing. It is the least disruptive path, but it carries existing shelfware forward and keeps the old support base largely intact.
A contract conversion terminates the existing agreement and credits a negotiated portion of its value into a new S/4HANA contract. It is the one moment SAP will let you strip shelfware wholesale, which makes it the stronger path for estates carrying years of accumulated unused licenses.
The three paths off ECC compared
| Path | What happens to licenses | What happens to support | Best fit |
|---|---|---|---|
| Product conversion | Swapped item by item into S/4HANA equivalents | Base carries over largely unchanged | Clean estates with little shelfware |
| Contract conversion | Old contract terminated, credit applied to a new one | Recalculated on the new, smaller base | Estates with heavy shelfware |
| RISE subscription | Perpetual rights traded for an FUE subscription | Disappears into the subscription fee | Buyers who want SAP to run the stack |
Mainstream maintenance for SAP Business Suite 7 ends on December 31, 2027, extended maintenance runs 2028 to 2030 at a premium of 2 percentage points on the maintenance basis, and customer specific maintenance follows, per SAP’s published maintenance strategy. S/4HANA itself carries an innovation commitment to the end of 2040.
The dates cut both ways. SAP account teams use 2027 to force timing, while informed buyers use the 2030 extended runway and the third party support alternative to refuse a rushed conversion, because a conversion negotiated under deadline pressure reprices the estate on SAP’s terms.
Deciding two full budget cycles ahead of your chosen cutoff keeps every path open. Inside the final year, product conversion is often the only executable option, and SAP knows it. The clause level negotiation sequence sits in our SAP contract negotiation playbook.
SAP measures named users and engines with the USMM transaction in each system, consolidates the results in LAW 2.0, and estimates digital access documents with SAP Passport tooling, so the buyer defense is running the same tools first.
USMM runs inside each SAP system and counts user classifications and the engine metrics configured for that installation. LAW 2.0, the License Administration Workbench, then consolidates the per system results and matches the same person across systems so one human is not counted three times.
The consolidation step is where estates win or lose. If user IDs, email addresses, and personnel numbers are inconsistent across systems, LAW cannot group them, and the measured count inflates silently.
Document counting uses the SAP Passport measurement tooling delivered through support packages, or an estimation exercise run with SAP’s audit and compliance organization. Run the estimation yourself before accepting any SAP produced figure, because assumptions about which documents originated from indirect scenarios are exactly that, assumptions.
Treat the annual measurement as a rehearsal for the audit you will eventually get. The estates that struggle in audits are the ones where the first clean measurement happens under audit conditions, with SAP watching the clock.
SAP support and maintenance is charged as an annual percentage of the license base, commonly above 20 percent. It compounds and rarely shrinks on its own.
For an outside read on the position, independent firms running SAP licensing compliance reviews work measurement and entitlement gaps exclusively.
SAP Standard Support lists at 19 percent of the maintenance base and Enterprise Support at 22 percent. Few estates consume the Enterprise extras, so the 3 point downgrade is one of the rare purely mechanical savings in an SAP estate, worth testing against real ticket history at every renewal.
Watch the indexation clause too. SAP has applied inflation linked increases to support fees in recent years where contracts allow, so a base that never shrinks on its own now also drifts upward, and a cap or fixed rate belongs in every new agreement.
Shelfware termination is the other structural lever, and it has a deadline of its own. Licenses must be terminated ahead of the annual renewal notice period or the fee runs another year, and the sequencing lives in our support and maintenance negotiation guide.
The plays that move real money are user reclassification, engine re measurement, shelfware termination, support tier and indexation control, and FUE mix work before any RISE signature, roughly in that order of effort to payoff.
The order matters more than any single play. Cleanup and re measurement shrink the base, termination takes the shrunken base out of support, and only then does a discount conversation land on numbers that stay down.
Run the sequence ahead of any audit, renewal, or conversion event, because every play is cheaper when SAP is not in the room yet. Where the estate is heading to S/4HANA, fold the plays into the conversion negotiation itself, since that is where SAP concedes the most.
White Paper · SAP
The SAP contract. The buyer side fundamentals
Nine buyer side fundamentals for an SAP contract: discount baselines, indirect access caps, price protection, audit clauses, and clean exit terms. Read it free.
An SAP named user license authorizes one individual to use SAP, classified by usage type. Professional, functional, and self service tiers carry different fees, so classification drives the cost.
Engine metrics license products by volume or capacity rather than by user. Payroll bills on employee records and some analytics on data volume, each measured on its own baseline.
Digital access licenses the documents that non SAP systems create in SAP, rather than the people behind them. Nine document types are counted, with sales and invoice documents weighing most.
SAP support is charged as an annual percentage of the license base, commonly above 20 percent. It compounds each year and rarely shrinks unless you remove shelfware from the base.
Yes. Removing inactive and duplicate accounts, reclassifying over licensed users, and retiring unused engines all reduce the count and the recurring support that sits on it.
Cloud changes the metric, not the discipline. FUE and subscription replace perpetual licenses, but user classification and accurate measurement still determine the cost.
SAP audits most often surface over assigned user classifications and undocumented indirect or digital access. Both are manageable with accurate records kept ahead of the audit.
Right size first. A discount on undeployed licenses still funds 20 percent annual support forever, so reducing the base before negotiating protects the lifetime cost.
A Full Usage Equivalent is the single subscription metric under RISE with SAP. One FUE covers 1 advanced user, 5 core users, or 30 self service users, while a developer consumes 2 FUE, so the user mix sets the price.
DAAP was the SAP program for converting indirect access exposure into document licensing. It offered licensing 115 percent of current document volume with fees only on the growth, or a 90 percent discount when licensing current volume.
SAP RISE pricing benchmarks, the CVR framework, indirect access posture, and the buyer side moves across the full SAP estate.
Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next SAP renewal cycle.
An SAP estate is priced once and paid for every year. The annual number is the one that deserves the attention.
