Editorial photograph of an SAP S/4HANA program leadership team reviewing FUE metrics and licensing model options
Article · SAP · S/4HANA

SAP S/4HANA licensing. The 2026 buyer view.

S/4HANA carries the most complex licensing model in the SAP catalog. FUE metrics, RISE versus on premise, indirect access, and the digital access document model all shape the renewal envelope. The buyer side framework for the next S/4HANA program decision.

Read the Framework SAP Hub
FUEFull user equivalent metric
a leading industry analyst firmRecognized
Industry Recognized
500+ Enterprise Clients
$2B+ Under Advisory
11 Vendor Practices
100% Buyer Side Independent

SAP S/4HANA carries the most complex licensing model in the SAP catalog. The FUE metric replaces named user. The RISE bundle replaces on premise licensing. The digital access document model replaces the legacy indirect access rule.

The model changes every two years. Each change rewrites the renewal math. The customer who tracks the model shifts and aligns the contract language stays ahead of the SAP commercial model.

This article reads the S/4HANA licensing model from the buyer side. Pair it with the RISE negotiation, the S/4HANA migration negotiation, the deployment models landing, and the SAP contract negotiation playbook.

Key Takeaways

What a CIO needs to know in 90 seconds

  • FUE replaces named user as the S/4HANA metric. Full user equivalents weight different user roles.
  • RISE is a subscription bundle. Infrastructure, application, support, and S/4HANA in one rate.
  • Indirect access is now the digital access document model. Each document type creates a licensable event.
  • The on premise S/4HANA license is still available. RISE is not mandatory.
  • Escalators on RISE run 3 to 7 percent. Lower than legacy ECC support uplift.
  • ECC support runs to 2030. The migration deadline is real.
  • S/4HANA Cloud Public Edition is the simplest model. Limited customization, fastest deployment.

FUE metric explained

FUE stands for Full User Equivalent. SAP introduced FUE as the primary S/4HANA metric to replace the legacy named user categories. The FUE model groups roles by intensity and weights each role into a single common unit.

FUE weighting in 2026

Role categoryFUE conversionDescription
Developer Access1 user equals 1 FUEFull development and administration rights
Advanced Use1 user equals 1 FUEPower users running complex transactions
Core Use5 users equal 1 FUEStandard transactional users
Self Service Use30 users equal 1 FUELight read and self service users

The FUE optimization opportunity

Most S/4HANA estates over license at the Advanced Use band. The role assignment defaults to power user even where the actual usage is core or self service. A FUE optimization sweep typically reduces the FUE count 12 to 25 percent without functional impact on the user community.

RISE vs on premise in 2026

SAP offers S/4HANA through two primary commercial models. RISE is the subscription bundle. On premise S/4HANA is the perpetual license with the legacy support model. The choice depends on infrastructure strategy, migration timing, and procurement preference.

RISE vs on premise comparison

DimensionRISEOn premise
Licensing modelSubscriptionPerpetual plus annual support
InfrastructureIncluded via hyperscaler partnerCustomer responsibility
SupportIncluded in subscription22 percent annual support fee
Escalator3 to 7 percent annuallySupport uplift 3 to 8 percent
CustomizationLimited in Cloud Public EditionFull customization rights
Best forCustomers exiting data centersCustomers with deep customization

Three RISE flavors

  1. S/4HANA Cloud Public Edition. Limited customization, fastest deployment, lowest list rate.
  2. S/4HANA Cloud Private Edition. Higher customization, dedicated tenancy, mid list rate.
  3. RISE on customer hyperscaler. Customer brings the hyperscaler contract, SAP provides the application stack.

Indirect access in 2026

SAP indirect access has been the most contentious topic in the SAP commercial model. The 2018 outcomes based licensing introduced a per document model that simplified the math. The current model in 2026 builds on that foundation.

Three indirect access scenarios

  • Static read access. A reporting tool pulling SAP data into a data warehouse.
  • Transactional integration. A non SAP application creating sales orders, purchase orders, or financial documents in SAP.
  • API mediated access. A third party application using SAP APIs to read or write data.

The static read exemption

Pure static read access for analytics typically falls outside the licensable scope. The line gets blurry when the read access drives transactional decisions back into SAP. The contract language should explicitly carve out the analytics read access from the digital access document count.

Digital access document model

The digital access document model bills indirect access per document type per year. Each new document created by a non SAP system is counted against a tiered pricing band.

Digital access document pricing

Document typeBilling unitList rate per document
Sales documentEach new sales order0.25 to 0.50
Invoice documentEach new invoice0.40 to 0.80
Purchase documentEach new purchase order0.25 to 0.50
Service documentEach new service entry sheet0.20 to 0.40
Manufacturing documentEach new production confirmation0.05 to 0.15
Material documentEach new goods movement0.05 to 0.10
Quality documentEach new inspection0.10 to 0.25
Time management documentEach new time entry0.05 to 0.15
Financial documentEach new accounting entry0.30 to 0.60

Escalator clauses

The RISE subscription carries an annual escalator. The escalator is typically 3 to 7 percent on the standard order form. Strategic accounts close at 0 percent in year one and 3 percent thereafter.

Three escalator leverage points

  • Multi year prepay. A three or five year prepay reduces the effective escalator.
  • Volume tiering. Higher FUE counts unlock a lower escalator band.
  • Strategic alignment. RISE migration commitments inside the SAP roadmap carry deeper concessions.

Common S/4HANA licensing traps

The S/4HANA program surfaces recurring traps. Each one is buyer fixable with structured contract review.

Five S/4HANA traps to watch in 2026

  • FUE over assignment. Roles defaulting to Advanced Use where Core Use fits.
  • Hidden indirect access scope. Third party integrations not declared at contract sign.
  • RISE hyperscaler lock in. Bundled hyperscaler contract limits customer flexibility.
  • Customization scope creep. Cloud Public Edition customizations exceeding allowable scope.
  • ECC sunset risk. Customer not aligned to the 2030 ECC support end date.

What to do next

The eight step checklist below runs the buyer side S/4HANA licensing process. Open it at the start of any S/4HANA program planning cycle.

  1. Inventory the current user base. Map every role to the FUE category that actually fits.
  2. Run the indirect access discovery. Identify every non SAP integration creating documents in SAP.
  3. Model the RISE vs on premise scenarios. Five year TCO across both paths.
  4. Open the digital access negotiation. Settle the document count and pricing band before contract sign.
  5. Negotiate the FUE pricing. Push for volume tiers and Multi year discount.
  6. Negotiate the escalator. Target 0 percent year one and 3 percent thereafter.
  7. Lock the customization carve outs. Confirm the allowable customization scope in Cloud Public Edition.
  8. Align the ECC sunset plan. Confirm the migration timeline and the bridge support window.

Frequently asked questions

What is the FUE metric in S/4HANA?

FUE stands for Full User Equivalent. SAP weights different user roles into a common unit. Developer Access and Advanced Use roles count as one user equals one FUE. Core Use counts as five users per FUE. Self Service Use counts as thirty users per FUE. The total FUE count drives the S/4HANA license bill.

Is RISE mandatory in 2026?

No. The on premise S/4HANA license is still available. SAP positions RISE as the recommended path for new customers and for ECC migrations. The on premise path remains available for customers with deep customization, regulatory data residency requirements, or strategic infrastructure preferences.

How does the digital access document model work?

SAP bills indirect access per document type per year. Each new document created in SAP by a non SAP system counts against a tiered pricing band. Sales orders, invoices, purchase orders, and financial documents carry different list rates. Pure static read access for analytics typically falls outside the licensable scope.

What is the RISE escalator in 2026?

RISE carries a standard escalator of 3 to 7 percent on the order form. The escalator is negotiable. Strategic accounts close at 0 percent in year one and 3 percent thereafter. Multi year prepay reduces the effective escalator. Volume tiers and strategic alignment with the SAP roadmap unlock additional concessions.

When does ECC support end?

SAP committed to maintenance for ECC 6.0 through 2027 with extended maintenance available through 2030 at a higher rate. The 2030 end date is the practical deadline for ECC to S/4HANA migration. Customers running ECC in 2026 should have a documented migration plan and a credible target date.

How do we negotiate S/4HANA licensing down?

Run the FUE optimization sweep, declare the indirect access scope upfront, model RISE vs on premise across five years, negotiate the digital access document count, push for volume tiers and multi year discount, target a zero escalator in year one, and lock the customization carve outs. The total addressable discount typically lands 25 to 40 percent below initial SAP quote.

How Redress engages on SAP S/4HANA

Redress runs the SAP S/4HANA licensing work on every program engagement. The work inventories the user base, runs the indirect access discovery, models the RISE vs on premise scenarios, negotiates the digital access count, and aligns the ECC sunset plan. The deliverable is a defended licensing model, a clean contract, and a multi year cost projection.

Read the related Vendor Shield, the Renewal Program, the Benchmark Program, the Software Spend Assessment, the Benchmarking framework, the about us page, the management team page, the locations page, and the contact page.

Model the RISE TCO against on premise S/4HANA in under five minutes.
Open the SAP RISE TCO Calculator →
White Paper · SAP

Download the SAP RISE Negotiation Guide.

A buyer side framework for the next SAP S/4HANA program, RISE migration, or ECC sunset. FUE optimization tables, indirect access discovery model, digital access document pricing, and the negotiation workbench used on every SAP engagement.

Used across five hundred plus enterprise software engagements. Independent. Buyer side. Built for enterprise customers running SAP at scale against the SAP commercial model.

SAP RISE Negotiation Guide

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

Open the Paper →
4 FUE
Role categories
3 to 7%
RISE escalator band
12 to 25%
FUE optimization range
500+
Enterprise clients
100%
Buyer side

We mapped every S/4HANA user to the right FUE category, identified 19 percent over assignment to Advanced Use, declared the indirect access scope upfront, modeled RISE Private Edition against on premise across five years, and landed the program 33 percent below the original SAP quote with the digital access document count fixed in writing.

Chief Information Officer
European industrial manufacturer
More Reading

More from this practice.

SAP Hub →
SAP RISE Negotiation
SAP · Guide
SAP RISE Negotiation
The RISE negotiation framework.
22 min read
S/4HANA Migration Negotiation
SAP · Guide
S/4HANA Migration Negotiation
ECC to S/4HANA program economics.
24 min read
S/4HANA Deployment Models
SAP · Landing
S/4HANA Deployment Models
Cloud Public, Private, on premise compared.
18 min read
SAP Indirect Access Changes
SAP · Article
SAP Indirect Access Changes
The digital access document model explained.
16 min read
SAP Contract Negotiation Playbook
SAP · Pillar
SAP Contract Negotiation Playbook
Master contract framework.
26 min read
Editorial photograph of enterprise contract negotiation strategy

Your SAP S/4HANA program is your envelope.

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

SAP licensing intelligence, monthly.

RISE pricing movements, FUE optimization signals, indirect access shifts, and SAP commercial behavior across every renewal cycle.