Editorial photograph of an SAP S/4HANA enterprise architecture review
Pillar · SAP · Licensing

SAP licensing.

SAP licensing in 2026 spans ECC, S/4HANA, RISE with SAP, BTP, and SuccessFactors. The Full Use Equivalent metric, the indirect access exposure, and the RISE versus on prem renewal trade off drive the bill. This is the buyer side pillar reference.

Read the PillarSAP Hub
20 to 35%Typical SAP saving
a leading industry analyst firmRecognized
Industry Recognized
500+ Enterprise Clients
$2B+ Under Advisory
11 Vendor Practices
100% Buyer Side Independent

SAP licensing in 2026 spans five major product families. Each family carries its own contracts, metrics, and renewal mechanics.

  • ECC. Legacy ERP. Mainstream support cliff in 2027. Extended support runs to 2030.
  • S/4HANA. On premise and private cloud ERP. The landing point for ECC migrations.
  • RISE with SAP. Bundled cloud subscription with S/4HANA Cloud Private Edition and SAP managed infrastructure.
  • BTP. Business Technology Platform for extensions and integrations.
  • SuccessFactors and Concur. Adjacent SaaS modules sold under their own metrics.

The licensing metrics span named users on the legacy ECC contracts, Full Use Equivalents under S/4HANA and RISE, engine specific metrics for HANA, BW, and PI, and the Digital Access per document metric for indirect access exposure.

The buyer side discipline is to right size each metric, model the RISE versus on prem scenario, cap the maintenance lift, and negotiate the indirect access exposure before the audit lands.

Pair this guide with the SAP knowledge hub, the SAP advisory practice, the RISE negotiation playbook, the HANA database licensing reference, the FUE calculation reference, and the RISE TCO calculator.

Key takeaways

What a CFO needs to know in 90 seconds

  • Five product families. ECC, S/4HANA on prem, RISE, BTP, SuccessFactors / Concur.
  • FUE is the new metric. Full Use Equivalent aggregates user types into one unit. RISE and S/4HANA Cloud Private Edition both use it.
  • Named user metrics live on. ECC and S/4HANA on prem still use Professional, Limited Professional, Employee, Developer.
  • Indirect access is real. Digital Access per document type. Exposure on Salesforce, ServiceNow, custom portals.
  • Maintenance lifts compound. 4 to 6 percent annual on on prem. Cap negotiation matters.
  • RISE is irreversible. The exit math at end of subscription is the buyer side concern.
  • ECC support cliff. Mainstream support ends 2027. Extended support to 2030. Plan the migration.

SAP documents the metrics this guide unpacks. Review the S/4HANA editions, the RISE with SAP bundle, the Business Technology Platform model, and the maintenance and support timeline on SAP’s own pages before you accept a renewal quote.

What products does SAP licensing cover in 2026?

ECC and the support timeline

SAP Business Suite 7, branded SAP ECC, is the legacy on premise ERP that thousands of enterprises still run in 2026. SAP set the mainstream support cliff at December 2027.

Extended support runs to December 2030, at an additional maintenance premium of 2 percent of annual maintenance for the first two years and 4 percent for the third. Beyond 2030, customers face either the migration to S/4HANA or the move to a third party support provider.

S/4HANA

S/4HANA is the on premise and private cloud version of the next generation ERP, running on the SAP HANA database. S/4HANA ships in three deployment models.

  • On premise S/4HANA. Perpetual license model with named user metrics and 22 percent annual maintenance.
  • S/4HANA Cloud Private Edition. Subscription model with FUE metrics. Often consumed through RISE.
  • S/4HANA Cloud Public Edition. Multi tenant public cloud. Subscription with FUE metrics and tighter customization scope.

RISE with SAP

RISE with SAP, launched in 2021 and refined through 2026, is the bundled cloud subscription that combines S/4HANA Cloud Private Edition with SAP managed infrastructure (typically Microsoft Azure, AWS, or Google Cloud), the SAP Business Network, and selected BTP services. The customer pays a single subscription fee that covers software, infrastructure, and managed services. The metric is FUE.

SAP BTP

The Business Technology Platform is the SAP platform for extensions, integrations, and analytics. BTP includes SAP Build (low code), SAP Integration Suite, SAP Analytics Cloud, SAP Datasphere, and the various BTP services. BTP is sold under the Cloud Platform Enterprise Agreement or as pay per use credits.

SuccessFactors, Concur, Ariba

The SAP SaaS modules cover HR (SuccessFactors), travel and expense (Concur), procurement (Ariba), and customer experience (CX). Each module is sold separately with its own metric (per employee per month for SuccessFactors, per transaction for Concur, per spend volume for Ariba).

How do SAP named user metrics work?

The legacy ECC and on premise S/4HANA licensing model uses named user metrics. Each user logging into the system is licensed under a specific named user type. The named user types carry different price points and different access rights.

The five named user types in 2026

TypeAccess rightsList price per user (approximate)
Professional UserFull functional access across modules. Configure, customize, transact.$4,500 to $6,500
Limited ProfessionalOperational access on defined modules. Limited config.$1,900 to $2,400
Employee UserSelf service. View own data. Submit requests.$350 to $550
Employee Self Service (ESS)Specific ESS scenarios only.$180 to $300
Developer UserABAP development and configuration.$8,000 to $12,000

Named user rules to know

  1. One named user per human. Pool accounts are not allowed. Each human with login rights is licensed.
  2. Tier matches usage. Audit the user tier against the actual transaction profile. Down classify where appropriate.
  3. Service accounts. Each integration service account is a Professional User in many contracts.
  4. Auto provisioning. Active Directory linked provisioning often creates users at the default Professional tier. The down classification work runs periodically.

How does SAP FUE math work?

The Full Use Equivalent metric, introduced with S/4HANA Cloud Private Edition and rolled into RISE, aggregates different user types into a single counting unit. The FUE conversion ratio simplifies the contract math by collapsing the named user complexity into one number.

FUE conversion ratios

User typeConversion to FUEInterpretation
Advanced User1 user = 1 FUEFull S/4HANA functional user
Core User5 users = 1 FUEOperational user, limited scope
Self Service User30 users = 1 FUESelf service access only
Developer1 user = 2 FUEPremium developer access

The FUE classification opportunity

Most RISE contracts are signed with a heavy Advanced User assumption. The buyer side audit consistently finds 25 to 40 percent of the Advanced User population running Core or Self Service usage patterns. The reclassification at renewal converts the contract math to a lower FUE total without changing the user experience.

How does SAP engine licensing work?

Beyond the named user tier or the FUE total, SAP also licenses engines and add ons separately. The engine licenses cover specific functional scopes that fall outside the named user metric.

Common SAP engines and their metrics

  • SAP Payroll. Per employee paid through the system.
  • SAP Treasury. Per managed bank account or per treasury professional.
  • SAP Sales and Distribution. Engine fee plus per order document in selected contracts.
  • SAP Manufacturing Execution. Per work center or per production order.
  • SAP CRM (legacy). Per CRM user or per sales transaction.
  • SAP Solution Manager. Bundled with the customer support contract.
  • SAP Process Integration (PI/PO). Engine fee plus per message volume.

How does SAP indirect access licensing work?

Indirect access, formally Digital Access in 2026 SAP contracts, is the licensing exposure when a third party system or a non SAP user invokes SAP functionality through APIs, RFCs, IDocs, or middleware. The exposure typically lands on enterprise architectures where SAP ERP integrates with Salesforce, ServiceNow, custom portals, e commerce platforms, and shop floor systems.

Digital Access pricing per document

Document TypeList price per document
Sales document$0.40
Purchase document$0.40
Invoice document$0.40
Financial document$0.40
Manufacturing document$0.40
Service document$0.40
Material movement document$0.40
Quality document$0.40
Time document$0.40

Indirect access rules to know

  1. The Digital Access model replaced indirect named user. SAP shifted from per indirect user to per document type starting 2018.
  2. Document Type counting. Each unique document created through indirect access counts. Read only access does not consume the metric.
  3. The Digital Access Adoption Program (DAAP). SAP runs discount programs for customers moving from named indirect to Digital Access.
  4. Audit risk. SAP can request middleware logs and integration data at audit. The buyer side defense pack documents the document flow.
  5. The contract clauses matter. The Digital Access scope clauses in the contract drive the exposure. Read every API and integration clause.

Is RISE or on prem S/4HANA the better licensing model?

The choice between RISE with SAP and continued on premise S/4HANA is the largest single decision in any 2026 SAP renewal. The decision turns on five inputs.

The five RISE decision questions

  1. Is SAP managing infrastructure the strategic direction? Yes points to RISE.
  2. Is hyperscaler choice flexibility important? Yes points to on prem with customer managed cloud or a non RISE migration.
  3. Is the customization scope heavy? Heavy customization points to on prem or S/4HANA Cloud Private Edition outside RISE.
  4. Does the exit and data portability concern weigh heavily? Yes points to on prem.
  5. Does the TCO model favor the bundle? Run the math at three year and five year horizons.

Typical RISE versus on prem TCO at 1,000 user enterprise

ScenarioYear oneFive year total
On prem S/4HANA$2.5M to $4M (one time license + year one maintenance + infrastructure + managed services)$10M to $15M
RISE with SAP$2.8M to $4.5M annual subscription$14M to $22M

How is the SAP HANA database licensed?

The SAP HANA database carries its own licensing model separate from the application layer. The two HANA models are Runtime License and Full Use License.

HANA Runtime versus Full Use

  • HANA Runtime License. Bundled with the SAP application that runs on it. Cannot be used for non SAP data or for non SAP applications.
  • HANA Full Use License. Permits use as a general purpose database. Priced separately. Used when HANA is exposed to non SAP applications or non SAP data.

See the dedicated HANA database licensing reference for the detailed math.

What negotiation levers move the SAP licensing price?

The eight levers below recur across every SAP optimization engagement Redress runs.

  1. Right size named users. Active user audit. Tier down to Limited Professional, Employee, ESS where applicable.
  2. Audit FUE classification. Advanced versus Core versus Self Service. The reclassification carries the biggest single saving in RISE.
  3. Cap the maintenance lift. 0 to 3 percent annual against the standard 4 to 6 percent.
  4. Map indirect access exposure. Document the integrations. Negotiate the Digital Access scope.
  5. Run the RISE versus on prem TCO. Three year and five year horizons. Hidden cost lines.
  6. Model the ECC support cliff. Mainstream 2027, Extended 2030, third party support beyond.
  7. Lock the multi year subscription rate. Three year RISE caps the escalator.
  8. Time the renewal against SAP fiscal year. SAP fiscal Q4 December. Plan negotiation window.

The SAP renewal review found two hundred Professional Users with Limited Professional usage profiles, an Advanced User population in RISE running at thirty percent Core usage patterns, an indirect access exposure undocumented across four major integrations, and a maintenance lift offered at five percent. The combined moves saved eight figures across the five year horizon.

Where the common advice on SAP licensing is wrong

The common advice is to wait for the ECC 2027 maintenance cliff to force the move to S/4HANA and RISE, then negotiate. We disagree. In our reviews, the customers who waited negotiated from weakness, because the deadline had already removed their best alternative and SAP knew it. The buyer side move is to model the licensing position 24 to 36 months early, right size the named user and engine metrics first, and treat the migration date as a lever you control rather than a gun SAP holds. A clean baseline built early is worth more than any deadline driven discount.

A software asset manager comparing SAP named user categories and engine metrics on a spreadsheet during a licensing review
Named user reclassification is the quietest source of SAP savings. Most estates carry Professional licenses on users whose actual activity fits a far cheaper category.
52
SAP licensing reviews 2024 to 2025
24%
Median named user spend removed
22%
Median indirect access exposure cut

Source: Redress Compliance advisory engagement file, 2024 to 2025.

The recoverable money in a SAP estate is rarely in the headline ERP line. It is in stranded users, shelfware engines, and the Digital Access count nobody measured.

What to do next

  1. Pull the SAP contract library. Every product, every metric, every renewal date.
  2. Run the named user audit. USMM or LAW measurement. Compare to license counts.
  3. Inventory engines. Payroll, Treasury, PI/PO, Solution Manager, others.
  4. Map indirect access. Every integration into SAP. Document type by document type.
  5. Model the RISE versus on prem scenario. Three year and five year horizons.
  6. Score the ECC roadmap. Migration plan against the 2027 and 2030 support cliffs.
  7. Build the FUE classification evidence. Advanced versus Core versus Self Service usage data.

Frequently asked questions

What is a Full Use Equivalent (FUE) in SAP licensing?

FUE is the S/4HANA Cloud Private Edition and RISE licensing metric that aggregates different user types into one unit. One Advanced user counts as a full FUE, while Core and Self Service users count at lower fractions. The mix of user types drives the total commit.

What is the difference between RISE and on prem S/4HANA?

RISE is a cloud subscription bundle that includes S/4HANA Cloud Private Edition, SAP managed infrastructure, and a fixed service catalog. On premise S/4HANA is a perpetual license the customer hosts and manages. RISE trades capital cost and control for a managed operating model.

How does SAP indirect access work in 2026?

Indirect access, now branded Digital Access, applies when a non SAP system or user creates SAP documents through APIs, RFCs, or middleware. SAP licenses it per document across nine document types. Run the document count before SAP runs it for you.

What is the typical SAP renewal lift?

On premise maintenance carries an annual lift of 4 to 6 percent under standard SAP terms, while RISE subscriptions carry escalators of 3 to 7 percent. Negotiate a hard cap on both the annual and the cumulative increase across the term.

When should an enterprise move to RISE?

RISE fits when the organization is migrating from ECC to S/4HANA and wants SAP to manage the cloud infrastructure. It is the wrong move when the customer needs hyperscaler flexibility, runs a heavy custom estate, or has no committed transition timeline.

How are SAP engines and packages licensed?

Engines such as HANA, BW, and PI carry their own metrics that sit outside the named user and FUE counts, often measured by memory, throughput, or document volume. Map every active engine before renewal, because shelfware engines are a common and recoverable overspend.

How is the SAP HANA database licensed?

HANA is licensed either by memory under runtime and full use editions or bundled inside RISE and S/4HANA Cloud. The runtime edition restricts use to SAP applications, while full use allows non SAP workloads at a higher price. Match the edition to the actual workload.

How does Redress engage on SAP licensing?

Redress runs the SAP inventory across ECC, S/4HANA, RISE, BTP, and Concur. The work covers the named user audit, the FUE math, the indirect access exposure assessment, the RISE versus on prem scenario, and the renewal negotiation, all from the buyer side.

How Redress engages on SAP licensing

Redress runs SAP licensing programs as part of the SAP advisory practice. The work covers the named user audit, the FUE classification, the indirect access exposure map, the RISE versus on prem scenario, and the renewal benchmark. Programs run as a focused engagement or as part of the wider Vendor Shield subscription.

Read the related Renewal Program, Benchmark Program, RISE Negotiation playbook, HANA Licensing reference, RISE TCO Calculator, about us, management team, locations, and contact pages.

Score your SAP posture against the buyer side benchmark in under five minutes.
Open the RISE TCO Calculator →
White Paper · SAP

Download the SAP RISE Negotiation Guide.

A buyer side reference on the RISE with SAP negotiation. FUE classification math, indirect access exposure, the multi year subscription lock, the exit and data portability clauses, and the buyer side red lines that hold.

Independent. Buyer side. Built for CFOs, CIOs, and vendor management teams. No SAP influence. No sales kickback.

SAP RISE Negotiation Guide

Open the white paper in your browser. Corporate email only.

Open the Paper →
20 to 35%
SAP saving
1 = 5 = 30
FUE ratios
$0.40
Per Digital Access doc
500+
Enterprise clients
100%
Buyer side

The SAP renewal review found two hundred Professional Users with Limited Professional usage profiles, an Advanced User population in RISE running at thirty percent Core usage patterns, an indirect access exposure undocumented across four major integrations, and a maintenance lift offered at five percent. The combined moves saved eight figures across the five year horizon.

Group CFO
European industrial group
More Reading

More from this practice.

SAP Hub →
SAP RISE Negotiation
SAP · White Paper
SAP RISE Negotiation Guide
The RISE negotiation playbook.
22 min read
SAP HANA Licensing
SAP · Guide
SAP HANA Database Licensing
Runtime versus Full Use reference.
18 min read
SAP FUE Calculation
SAP · Reference
SAP FUE Calculation
The Full Use Equivalent math reference.
10 min read
SAP RISE TCO Calculator
SAP · Tool
SAP RISE TCO Calculator
The RISE versus on prem cost model.
5 min check
SAP Services
SAP · Services
SAP Advisory Practice
The SAP vendor management practice.
15 min read
Editorial photograph of enterprise contract negotiation strategy

SAP overspend is a fixable problem.

We have run 500+ engagements across 11 publishers. Every engagement starts with one conversation.

SAP intelligence, monthly.

FUE classification examples, RISE TCO benchmarks, indirect access negotiations, ECC migration patterns, and the wider SAP commercial leverage signals across every program we run.