SAP S/4HANA Licensing: Strategy, Pricing, Audit Risk and Optimisation

The S/4HANA Licensing Landscape in 2026

SAP S/4HANA is not a single product with a single licensing model. It is a family of related products — on-premise, cloud private, cloud public — each with its own licensing mechanism, commercial structure, and negotiation dynamics. Understanding which model applies to your deployment, and how the applicable model's commercial terms work in practice, is the first and most important step in managing your SAP cost position effectively.

The three primary deployment and licensing models are: on-premise S/4HANA (perpetual named user licences with annual support at approximately 22% of net licence value), RISE with SAP S/4HANA Cloud Private Edition (FUE-based subscription delivered as a bundled managed cloud service), and S/4HANA Cloud Public Edition (FUE-based subscription on a multi-tenant, SAP-managed infrastructure with quarterly updates and clean core requirements). Each of these intersects with Digital Access licensing — the DDLC-based model for indirect access by third-party systems — which is a distinct charging layer applicable across all deployment models.

On-Premise S/4HANA Licensing

On-premise S/4HANA uses a perpetual named user licence model. You purchase a licence for each user category required in your deployment, and that licence is permanent — it does not expire when you stop paying SAP annual support. However, without active annual support you lose access to software updates, patches, legal change packages (critical for regulatory compliance), and SAP's support infrastructure. Annual support is contractually set at approximately 22% of your net licence value — the price after contractual discounts, not SAP's list pricing.

User categories for on-premise S/4HANA are: Professional Use (full access to all S/4HANA modules and functionality, highest price), Limited Use (single-module or single-domain access, middle tier), Self-Service Use (structured, limited transactions such as expense entry, timesheet submission, and leave requests, lowest price), and Developer Use (for technical users building or modifying system functionality). The consolidation from ECC's 100-plus user types to these three principal categories is genuine — but the boundaries between them are more precisely enforced in S/4HANA than in ECC, and misclassification creates audit risk.

The S/4HANA migration process changes your licence baseline. Migrating from ECC to S/4HANA requires a licence conversion exercise that reclassifies your users against the S/4HANA taxonomy. This exercise almost always identifies additional licence requirements compared to your ECC position, and it triggers a Digital Access assessment. Conducting both of these analyses independently — before engaging SAP in migration pricing discussions — consistently delivers better outcomes than allowing SAP's account team to conduct the assessment on your behalf.

RISE with SAP: Subscription Licensing and What the Bundle Really Contains

RISE with SAP is SAP's flagship cloud migration offer, packaging S/4HANA Cloud Private Edition with infrastructure hosting, managed application services, and SAP BTP access in a single annual subscription. The pricing metric is the Full User Equivalent (FUE): you purchase a total FUE pool and allocate users across the three S/4HANA user type tiers based on their access requirements. One Advanced (Professional) user equals 1.0 FUE; one Core (Limited) user equals 0.2 FUE; one Self-Service user equals approximately 0.033 FUE.

RISE list pricing runs approximately $170 to $185 per FUE per month, but contracted enterprise pricing after proper negotiation typically lands 25% to 45% below list for engagements above 100 FUEs. SAP's fiscal year ends December 31, which creates predictable commercial pressure patterns: SAP's account teams have maximum deal flexibility in Q4 and in the final weeks of each quarter. Buyers who structure their negotiation timeline to align with these windows, rather than SAP's preferred "close as soon as possible" timeline, achieve consistently better outcomes.

What RISE Includes — and the Critical Exclusions

RISE with SAP includes: S/4HANA Cloud Private Edition software, hyperscaler infrastructure hosting (on AWS, Azure, or Google Cloud, per customer choice), SAP Enterprise Support, a defined BTP CPEA credit allocation for platform consumption, migration tooling access, and basic application lifecycle management. What RISE genuinely does not include — regardless of how SAP's account teams describe the offer — are the SAP line-of-business cloud applications: SuccessFactors, Ariba, Concur, Fieldglass, and SAP Analytics Cloud beyond minimal embedded access. Each of these is a separate subscription that must be separately negotiated.

The BTP credit allocation included in RISE is frequently insufficient to support organisations that plan to use BTP intensively for integrations, extensions, and analytics. If your roadmap includes significant BTP usage, negotiate a specific credit volume in the RISE contract and build in mechanisms to acquire additional credits at the contracted rate rather than at SAP's standard BTP credit pricing.

Digital Access and the DDLC Metric

Digital Access is SAP's licensing model for indirect access to S/4HANA by third-party applications, automated processes, and system integrations. It replaces the legacy "indirect access" framework with a document-based charging model governed by the Digital Documents Licence Compliance (DDLC) metric. Under DDLC, SAP counts specific document types created in S/4HANA by external systems — not human users — and charges for these on a per-document basis.

The nine primary document types currently subject to Digital Access charging are: Purchase Orders, Sales Orders, Goods Movements, Material Documents, Production Orders, Quality Notifications, Maintenance Orders, Time Confirmations, and Project System Confirmations. A document is counted once when first created by an external process; subsequent reads, updates, and deletions do not generate additional charges. Read-only access by external systems does not create DDLC liability at all.

The DDLC risk for enterprises with complex integration landscapes — CRM systems posting sales orders, procurement platforms creating purchase orders, workforce management applications submitting time confirmations — can be substantial. Based on our advisory experience, DDLC claims in the range of $2 million to $15 million are common for large enterprises that have not proactively assessed and managed their Digital Access position. Conducting an independent DDLC assessment before any S/4HANA migration negotiation is not optional for organisations with non-trivial integration landscapes — it is essential to understanding the actual total cost of the migration.

Annual Support Costs: The Perpetual Overhead

For on-premise S/4HANA customers, annual support is approximately 22% of net licence value — paid annually to SAP indefinitely as long as the organisation remains on SAP's standard or enterprise support. For a $10 million licence investment (after negotiated discounts), this means $2.2 million annually in support costs. Over a ten-year period, this represents $22 million in cumulative support spend on top of the initial licence investment.

This support cost dynamic creates meaningful leverage for customers exploring alternatives. Third-party maintenance providers — Rimini Street and Spinnaker Support being the leading options — offer support services for on-premise SAP licences at approximately 50% of SAP's support rate. For a customer paying $2.2 million annually in SAP support, third-party maintenance represents an immediate $1.1 million annual saving. This optionality is a powerful negotiating tool in support renewal discussions with SAP, even for organisations that ultimately choose to remain on SAP support.

In RISE with SAP contracts, annual support is embedded in the subscription fee and is not separately itemised. Third-party maintenance is not available for RISE deployments, as SAP's infrastructure management services are contractually integrated with the subscription. This structural difference is one of the most commercially significant distinctions between on-premise and RISE — RISE customers cannot use third-party maintenance as a support negotiation lever, making renewal pricing protection clauses in the initial RISE contract particularly important.

User Licence Optimisation: Finding the 20% to 30% Saving

User licence optimisation is the most consistently high-value cost reduction activity available to SAP customers outside of a major renegotiation. The principle is straightforward: users who are classified at a higher licence tier than their actual access patterns require are costing more than necessary, and reclassifying them to the appropriate tier reduces either the annual support bill (on-premise) or the FUE count (cloud).

The optimisation process requires three steps. First, conduct an access analysis using SAP's USMM tool or a third-party licence management solution to determine actual transaction usage — not role assignments, but actual access events — for every user over the most recent twelve-month period. Second, compare actual usage against the S/4HANA user type definitions to identify users who qualify for a lower tier based on their actual access patterns. Third, implement role modifications that restrict access to match the lower tier, then validate the reclassification against the next USMM measurement.

In organisations that have not conducted this exercise since their S/4HANA go-live, user licence optimisation typically delivers 20% to 30% reduction in FUE requirements or equivalent savings on on-premise user licence count. For a large enterprise with a $500,000 annual S/4HANA support bill or a $3 million annual RISE subscription, this represents $100,000 to $900,000 in annual savings that persist for the life of the deployment.

SAP Audit Defence: Managing the Measurement Risk

SAP measures licence compliance using the USMM report (User and System Measurement), which captures the access patterns of all users in the production system over a defined period and maps them against contracted licence entitlements. The measurement is conducted at SAP's request (typically annually, though SAP reserves the right to request measurements more frequently under most enterprise licence agreements) or as part of a formal licence audit.

The highest-risk audit scenarios for S/4HANA customers are: user type misclassification (users classified as Limited who have accumulated Professional-level access through role additions or workflow approvals), Digital Access DDLC violations (third-party integrations creating chargeable documents without corresponding Digital Access entitlements), and engine or package licence non-compliance (specialised SAP components used without explicit licence entitlement). Each of these risk areas can be proactively managed through regular internal measurement, access governance processes, and independent licence health checks conducted before SAP's measurement dates.

If you receive a formal audit notification from SAP, the immediate priorities are to secure legal representation with SAP contract expertise, to conduct an independent measurement using your own USMM run (which provides a baseline for the negotiation), and to avoid making formal admissions of non-compliance before the scope and magnitude of any claim has been independently assessed. SAP's initial audit claims are routinely overstated — independent assessment consistently identifies 40% to 70% of the claimed liability as either disputed or non-applicable — and the negotiated settlement is almost always substantially lower than the initial claim.

Cost Optimisation Strategies: The Highest-Leverage Actions

Based on our experience across more than 500 SAP advisory engagements, the following strategies consistently deliver the highest return on investment for organisations managing their S/4HANA cost position. In order of typical impact: negotiate before committing (the most leverage exists before any commercial commitment is made — for on-premise migrations and for RISE deals, the pre-signature negotiation determines 80% of the outcome); conduct independent user classification (20% to 30% FUE reductions are achievable through rigorous access analysis); assess DDLC before migration (quantifying Digital Access liability before the migration negotiation prevents it from being treated as a cost to be managed post-signature at SAP's preferred pricing); engage independent advisors with current benchmarking data (the advisory fee is typically recovered 10 to 20 times in improved commercial terms); and negotiate renewal protections upfront (RISE contracts without escalation caps expose you to aggressive renewal pricing at year three).

SAP's account teams are sophisticated, well-resourced, and work to well-defined playbooks. The organisations that achieve the best commercial outcomes are those that match this sophistication with independent advice, current market data, and disciplined negotiation discipline. Those that do not are paying a significant premium above the market rate for identical capabilities.