SAP licensing splits across named user, package, engine, FUE, and consumption metrics. Read the buyer side 2026 reference on every metric, the conversion math, and the leverage points that move the price.
SAP licensing carries five metric families: named user, package, engine, FUE, and consumption. Each has its own math. Each carries its own audit risk. The 2026 reference is the buyer side map across the five families, the conversion logic between them, and the negotiation levers that bend the price.
Pair this guide with the RISE versus on premise article, the RISE negotiation framework, the audit defense framework, and the cloud licensing models article.
SAP grew by acquisition for thirty years. Each module brought its own metric. The five families now coexist in the same agreement. A typical large enterprise sees four of the five on the same order form. The complexity is structural, not accidental.
Most enterprises do not have a clean license position. User counts drift. Engine consumption drifts. Indirect access creeps in via integrations. The audit script lands on the gap. The defense lives in the evidence file.
Named user licenses are assigned to a person. The license type depends on the work the person does. Professional, limited professional, and employee are the three common tiers. Each carries a different price and a different scope.
| User type | Scope | List price band | Common allocation |
|---|---|---|---|
| Professional | Full transactional access | $3,000 to $4,500 | Power users, finance, procurement |
| Limited Professional | Defined transaction set | $1,200 to $2,000 | Approvers, line managers |
| Employee | Self service only | $200 to $400 | General workforce |
| Developer | Development environments | $5,000 to $7,000 | ABAP and development teams |
Package licenses cover named scope. Engine licenses cover consumption. The engine metric varies by module. Order volume, payroll headcount, revenue, and customer count are common engine measures. Each one needs an evidence file.
Engine measurement runs on SAP measurement scripts. The script reads system tables. Without a parallel evidence file the script is the audit position. Build the evidence file quarterly. Reconcile measurement to evidence before the audit lands.
Full User Equivalent is the cloud metric. Each named user type maps to a FUE ratio. The FUE total drives the RISE and GROW subscription price. The conversion math sits in the order form, not in the brochure.
| User type | FUE ratio | 100 users = FUE | Common buyer move |
|---|---|---|---|
| Advanced | 1.0 | 100 FUE | Defend headcount evidence |
| Core | 5 to 1 | 20 FUE | Right size limited tier |
| Self service | 30 to 1 | 3.3 FUE | Move workforce to self service |
| External | 50 to 1 | 2 FUE | Maximize external classification |
Indirect access is the use of SAP data and SAP function through a non SAP front end. The 2018 reform moved indirect access from user counts to document counts. The risk is still live. Integrations, bots, and external portals all read SAP data.
The evidence file is the artifact that lets the CFO walk into the SAP audit call and lead the conversation. Without the file, the script becomes the position. With the file, the audit becomes a reconciliation.
The seven step checklist below moves an SAP estate from drift to defended license position.
Annual measurement is the SAP standard. The buyer should run an internal measurement quarterly. The internal measurement uses the same scripts as the SAP audit. The gap between the two becomes the evidence file. Quarterly discipline beats annual surprise every time.
Yes. Most enterprises carry ten to twenty percent named user drift. The reclamation work pulls back inactive accounts, downgrades over licensed users, and rightsizes the tier mix. The savings appear at the next true up and at the next renewal anchor. The work pays back in one quarter.
No. The reform replaced user count licensing with document count licensing for indirect scenarios. The risk shifted. Document counts now drive the bill. Integrations, bots, and external portals all generate documents. The evidence file still matters.
SAP offers a conversion credit when an on premise estate moves to RISE. The credit applies a defined ratio against the FUE bill. The ratio is negotiable. The starting point is in the order form. The buyer position is to model the full five year picture before signing.
Engine licenses vary widely. A finance engine on revenue can cost millions for a large enterprise. A payroll engine on headcount runs into mid six figures. The list price is in the SAP price list. The discount band is in the negotiation. The evidence file is in the buyer position.
Redress runs the agreement review, the named user file, the engine measurement, the indirect access map, the FUE model, and the renewal negotiation. Engagements close inside twelve weeks. The work is buyer side. No vendor influence. No sales kickback.
Redress runs SAP licensing reviews as part of the buyer side advisory practice. The work covers the agreement review, the named user file, the engine measurement, the indirect access map, the FUE model, and the renewal negotiation. Engagements close in eight to twelve weeks.
Read the related Vendor Shield, Renewal Program, Benchmark Program, Software Spend Assessment, Benchmarking framework, about us, management team, locations, and contact pages.
A buyer side reference on SAP named user, engine, FUE, and indirect access licensing. Includes the engine measurement template, the FUE conversion model, the indirect access map, and the negotiation language used across hundreds of SAP renewals.
Independent. Buyer side. Built for CFOs, ERP leads, and procurement teams carrying SAP licensing decisions. No vendor influence. No sales kickback.
Open the white paper in your browser. Corporate email only.
Open the Paper →The evidence file is the artifact that lets the CFO walk into the SAP audit call and lead the conversation. Without the file, the script becomes the position. With the file, the audit becomes a reconciliation.
We have run 500+ engagements across 11 publishers. Every engagement starts with one conversation.
Named user benchmarks, engine measurement patterns, FUE conversion math, indirect access patterns, and the wider SAP commercial leverage signals across every engagement we run.
Once a month. Audit patterns, renewal benchmarks, vendor commercial signals across Oracle, Microsoft, SAP, Salesforce, IBM, Broadcom, AWS, Google Cloud, ServiceNow, Workday, Cisco, and the GenAI vendors. No follow up sales pressure.
Free providers (Gmail, Yahoo, Outlook) cannot subscribe. Work email only. Unsubscribe in one click.
