SAP licensing in 2026 is a different discipline to the one most enterprise teams learned a decade ago. Digital Access, RISE with SAP, S/4HANA Cloud Private Edition, and the ongoing ECC end-of-life are reshaping every SAP commercial conversation. This pillar covers the metric model, the indirect-access trap, and the commercial design choices that determine your next decade with SAP.
SAP is in the largest commercial transition in its history. Mainstream maintenance for SAP ECC 6.0 ends 31 December 2027 (with extended maintenance available to 2030 for additional fee), forcing every enterprise on the platform to make a migration decision. RISE with SAP — SAP's bundled S/4HANA Cloud Private Edition subscription — is the commercial vehicle SAP is steering customers toward. The choice between RISE, S/4HANA on-premises, and a phased hybrid path is now the largest IT commercial decision most SAP customers will make this decade.
In our experience across 340+ engagements, the SAP outcomes that produce the best long-term economics share three properties: they start the commercial conversation 18–24 months before the migration event, they reconcile the named-user and engine entitlement before they look at FUE conversion, and they treat the indirect-access conversation as a separate, parallel commercial negotiation rather than a sub-clause of the main deal.
SAP's traditional licensing model rests on two parallel metrics: Named Users (per-person rights to access the system, segmented by user type) and Engines (functional or capacity-based metrics for specific modules and packages). RISE and S/4HANA Cloud introduce a third — Full Usage Equivalent (FUE) — that converts existing named-user counts into a normalised cloud-subscription metric.
SAP defines a layered hierarchy of Named User types — Developer, Professional, Limited Professional, Employee, Productivity, Project. Each type carries different rights and different list prices. Buyers regularly over-license by assigning Professional users where Limited Professional rights would suffice. The defence is a user-type audit against actual transaction patterns; we routinely identify 15–30% of named users who can be re-tiered to a lower type at renewal.
Engine metrics apply to specific functional modules — Payroll (per employee), Treasury (per transaction), CRM (per service order), HR Self-Service. Each engine has its own measurement unit and its own audit risk. The most common engine surprise is Payroll: the metric is total employees including those without active SAP access, which mirrors the Oracle Employee-metric trap.
SAP's Digital Access licensing — introduced 2018 — measures licensable use through document creation events from non-SAP systems. The nine document types include sales orders, invoices, service confirmations, manufacturing orders, and material documents. Each document carries a per-event price. Digital Access is the contractual mechanism that resolves most indirect-access disputes, but the pricing and conversion logic remain heavily negotiable.
Former SAP licensing executives review the position within five working days.
Indirect access — use of SAP data through a non-SAP application or interface — has been the largest source of unexpected SAP audit findings for the last decade. The 2018 Digital Access framework provided a path to resolve the historical ambiguity, but it did not eliminate the exposure. Customers who never opted into Digital Access remain subject to the previous (and more punitive) indirect-access framework, which counts every indirect user as a Named User regardless of human attribution.
The indirect-access patterns SAP audit teams look for include: e-commerce platforms posting orders to SAP, supplier portals creating purchase orders, customer portals updating account data, manufacturing execution systems creating production confirmations, and integration buses (MuleSoft, Boomi, Informatica) routing data between SAP and other applications. Each pattern is a potential indirect-access finding under the pre-2018 framework or a Document Access count under Digital Access.
Conversion from named-user indirect access to Digital Access is typically commercially favourable, but the discount and document price are heavily negotiable. SAP's standard Digital Access price list is the starting point, not the ending point. Customers who segment their document volumes and negotiate document-type-specific prices consistently outperform those who accept the headline Digital Access price.
The full commercial design playbook covering RISE, on-premises, FUE conversion and indirect access.
RISE with SAP bundles four components into a single per-FUE subscription: S/4HANA Cloud Private Edition (the application), the underlying database and runtime, hyperscaler infrastructure (AWS, Azure, GCP, or SAP-managed), and basis-level managed services. The bundle is priced in FUEs and typically committed for five to seven years. The bundle is convenient, but the convenience comes at a price — RISE's FUE-based pricing routinely runs 15–25% above the equivalent unbundled cost when the buyer has scale negotiation leverage with the hyperscaler independently.
Each SAP named user type converts to a published FUE ratio — Professional at 1.0, Limited Professional at 0.2, Employee at 0.03, Developer at 1.0 (with conditions). Digital Access documents convert at separate ratios. The total FUE count drives the RISE subscription price. The lever is the conversion calculation: buyers who let SAP compute the FUE count from the historical named-user inventory routinely accept counts 20–40% higher than the actual operational requirement. The correct approach is to project FUE need from the S/4HANA target architecture, not from the legacy ECC entitlement.
RISE delivers S/4HANA Cloud Private Edition (PCE) — a single-tenant variant of S/4HANA hosted on hyperscaler infrastructure. PCE differs from S/4HANA Cloud Public Edition (multi-tenant, shorter release cycle) and from S/4HANA on-premises (full IT-managed deployment). PCE preserves much of the customisation flexibility customers expect from on-premises, but the upgrade governance and SAP-managed operations change the operational model.
The S/4HANA migration is often discussed as a technical project — and it is. It is also the single largest SAP commercial event most enterprises will execute. Migration credits, conversion discounts, multi-year RISE commitments, and Digital Access settlements are all on the table during the migration negotiation. The buyers who get the best long-term economics treat the migration commercial design as a year-long parallel workstream to the technical migration, with its own leadership and its own benchmarks.
SAP offers migration credits — Customer Value Adjustment (CVA) and related conversion incentives — that can offset 15–30% of the first-year RISE subscription cost. The credits are negotiable in size and in application; SAP's first proposal will typically apply credits to the years and SKUs that least benefit the buyer. The correct negotiating position is to apply credits to the highest-cost RISE components in years two through five, not to year one alone.
RISE commitments are typically structured as five-to-seven-year subscriptions with annual fee schedules. The fee schedule shape — flat, declining, or ramping — is negotiable and has large NPV consequences. Most SAP RISE proposals default to a flat fee schedule that maximises SAP's revenue recognition; buyers should test ramping schedules with year-one discounts that gradually unwind.
SAP ECC 6.0 mainstream maintenance ends 31 December 2027, with extended maintenance available to 31 December 2030 for an additional 2% fee on top of standard support. Customer-specific maintenance can extend further but at meaningfully higher cost and with reduced scope. The 2027 / 2030 timeline drives the migration decision for every ECC customer; sitting tight beyond 2030 typically requires third-party support (Rimini Street, Spinnaker) for the remaining ECC lifetime.
For enterprises whose S/4HANA migration timeline runs past 2030, third-party support providers offer continued ECC maintenance at typically 50% of SAP's support cost. Third-party support removes the maintenance cliff as a forcing function and lets the migration follow business readiness rather than vendor calendar. The trade-off is loss of access to new SAP releases, which is moot for an estate destined for S/4HANA migration regardless.
Independent SAP review with former SAP licensing executives — 5–7 working days.
SAP's standard support is 22% of net licence value annually under SAP Standard Support, 22% under Enterprise Support (with additional services), and tiered higher for MaxAttention. The percentage is widely treated as fixed; it is not. Support fees are negotiable at every major renewal event, especially during a migration negotiation when the buyer's commitment is increasing. The lever is renewal-window scoping: support reductions secured at renewal lock forward; the same reductions in steady state are blocked by matching service level.
If your S/4HANA migration or RISE evaluation is in the next 24 months, three preparation moves consistently pay back. First, baseline the SAP estate at user-type and engine granularity, not at headline named-user count. Second, separate the indirect-access conversation from the migration conversation; combining them weakens both. Third, project FUE need from the target S/4HANA architecture, not from legacy ECC entitlement — the gap is where the savings live.
Our SAP practice is built from former SAP licensing executives and S/4HANA commercial designers. We benchmark SAP terms across hundreds of enterprises.
Weekly compliance intelligence for IT leaders.