Executive Summary
How deployment choice shapes licensing, cost, and compliance
The choice between S/4HANA Public Cloud, Private Cloud (RISE with SAP), or On-Premise directly influences total cost of ownership, agility, and licence compliance risk. Each model has a distinct licensing approach, from subscription-based SaaS with FUE metrics to traditional perpetual licences with named users, affecting budgeting (OpEx vs CapEx), contract negotiations, and future flexibility. For the full S/4HANA licensing framework, see our SAP S/4HANA licensing complete guide.
Table of Contents
1. S/4HANA Deployment Options Overview
Three models, three licensing approaches
| Aspect | Public Cloud (SaaS) | Private Cloud (RISE/HEC) | On-Premise |
|---|---|---|---|
| Model | Multi-tenant SaaS | Single-tenant managed cloud | Self-managed (own DC or IaaS) |
| Customisation | Limited (config + BTP extensions) | Full (ABAP modifications, industry modules) | Maximum (full code access, custom add-ons) |
| Updates | Automatic quarterly (SAP-controlled) | Coordinated with customer schedule | Customer-controlled timing |
| Infrastructure | SAP-managed shared | SAP/partner-managed dedicated | Customer-managed |
| Licensing | Subscription per FUE (OpEx) | Subscription bundle: licence + infra + support (OpEx) | Perpetual licence + annual maintenance (CapEx + OpEx) |
| Best For | Standardised processes, mid-market | Large enterprises needing cloud + customisation | Regulated industries, maximum control |
Public Cloud (SaaS)
SAP hosts on shared infrastructure with automatic quarterly updates. Limited to configuration and BTP extensions. Subscription-based FUE model covering software, support, and infrastructure.
Private Cloud (RISE)
Single-tenant on dedicated resources. Full S/4HANA scope including industry modules and ABAP modifications. Single contract bundling licence, infrastructure, Basis operations, and BTP. See our RISE with SAP advisory.
On-Premise
Maximum control over every aspect. Traditional perpetual licence plus annual maintenance (20 to 22% of net licence value). Named-user categories. HANA licensed separately by memory capacity or CPU cores.
2. Licensing Model Implications by Deployment
FUE metrics, RISE bundles, and perpetual licence dynamics
Public Cloud Licensing: Subscription SaaS per FUE
Full User Equivalent (FUE) is an abstract unit representing one fully active user. Companies purchase a block of FUEs distributed among user categories: Advanced User = approximately 1.0 FUE (power user, broad access), Core User = approximately 0.2 FUE (limited, task-specific), Self-Service User = approximately 0.03 FUE (view reports, light tasks), Developer = approximately 2.0 FUEs. This tiered approach lets a larger number of light users be covered by a smaller FUE allocation.
Subscription covers software licence, support, and cloud infrastructure as a single OpEx cost. No traditional named-user licences to manage. Users can be swapped or re-categorised within FUE capacity. Minimum commitment typically around 15 FUEs, multi-year contracts. Caution: Unused FUE capacity (shelfware) still incurs costs. You generally cannot reduce FUE counts mid-contract, only at renewal.
Private Cloud Licensing: RISE Subscription Bundle
RISE with SAP provides a single contract covering S/4HANA licence, infrastructure/hosting, Basis operations, BTP runtime, and Business Network, also measured in FUEs. Enterprises with existing on-premises licences can sometimes bring them to a hosted private cloud (HEC or partner-managed), paying only a hosting fee. RISE shifts from CapEx to OpEx while preserving broad software scope. Simplifies vendor management (one contract) but makes cost breakdown less transparent. Once signed, you typically retire previous on-premises licences for migrated systems. For detailed RISE outcomes, see our RISE with SAP case studies.
On-Premise Licensing: Perpetual Plus Maintenance
Named users (Professional, Limited Professional, Employee Self-Service) each granting specific access rights. Certain modules licensed by revenue, employee count, or system size. HANA database licensed separately by memory capacity or CPU cores. Significant upfront purchase with annual maintenance at 20 to 22% of net licence value. Over long periods, annual fees accumulate but are generally lower per year than equivalent subscription. Any future cloud move requires contract conversion or new purchase; perpetual licences cannot be simply ported to SaaS. If SAP audit finds usage beyond licensed amounts, the company must purchase additional licences plus pay maintenance retroactively. See our SAP audit defence service.
3. Compliance Considerations by Model
Audit risk applies to all three deployment models
On-Premise Compliance
Customer tracks all usage. Each user or system accessing S/4HANA must have proper licence. Indirect access (third-party apps using SAP data) is a major audit risk. SAP Digital Access model charges per document. SAP retains right to audit with 30 days’ notice. Misclassifying users equals non-compliance.
Public Cloud Compliance
System enforces limits and you cannot add users beyond FUE subscription. Shifts compliance to contractual level. Indirect use still applies via API calls. SAP often includes a Digital Access allowance but excess usage may require upgrade. Focus: manage user roles and counts against FUE contract.
Private Cloud Compliance
Hybrid approach. SAP audit rights apply. More freedom to customise means more risk of exceeding scope (extra sandboxes, more HANA memory). Indirect access rules still apply. FUE user classification must match actual usage patterns. Negotiate coverage in RISE contract.
Facing an SAP Audit or Compliance Review?
Our defence specialists have helped enterprises avoid millions in unexpected costs across all three deployment models.
SAP Audit Defence Service →4. Cost Optimisation Strategies
Model-specific tactics for controlling SAP licensing spend
On-Premise Cost Optimisation
Periodically review user licences. Reclaim from departed employees or changed roles. Optimise the mix: ensure heavy users have Professional licences, casual users have limited or ESS types. If you have excess licences, negotiate licence swaps or shelfware retirement with SAP. Large customers can negotiate caps on yearly maintenance increases. Consider infrastructure optimisation: rightsize HANA database footprint, archive data to reduce memory requirements and lower HANA licence tier. For practical tactics, see our white paper on 10 proven strategies to cut SAP licensing costs.
Public Cloud Cost Optimisation
Right-size FUE allocation: not all users need Advanced (1.0 FUE). Many can be Core (0.2) or Self-Service (0.03). Correctly categorising each role maximises coverage of purchased FUEs. Negotiate to begin with a lower commitment and add users at agreed pricing as needed. You generally cannot reduce mid-contract, so it is financially safer to slightly underestimate and add later than overcommit. Maximise ROI by using everything included in your subscription (analytics, mobile apps) instead of buying third-party tools.
Private Cloud (RISE) Cost Optimisation
RISE deals can bundle more than you need (Business Network, BTP credits, add-ons). Scrutinise each component and remove or scale down items you will not use near-term. Work with SAP to size systems appropriately. Archive legacy data to reduce HANA memory footprint. Evaluate RISE vs on-premises over 5+ years. Sometimes existing licence owners pay a premium for RISE convenience. Ensure subscription cost is justified by benefits. Benchmark pricing against similar companies or engage independent experts. For RISE negotiation outcomes, see our RISE with SAP case studies.
Our SAP Licence Optimisation Service Has Saved Enterprises Millions
Let us analyse your SAP licensing landscape across any deployment model. See our SAP licence optimisation service.
SAP Licence Optimisation →5. Strategic Negotiation Tactics for CIOs
Conversion rights, exit clauses, flexibility, and leverage
Conversion and Hybrid Licensing Options
If running SAP ECC or S/4HANA on-premises, leverage SAP’s Contract Conversion or RISE conversion programmes that credit existing investment toward subscription. Negotiate explicit conversion rights: the ability to convert unused on-premises licences into cloud subscription credits at a later date. Consider a “cloud extension policy”: maintain some perpetual licences as a fallback while adding cloud subscriptions. For guidance on negotiating conversions, see our guide on negotiating S/4HANA licensing conversions and discounts.
Exit and Reversibility Options
Negotiate what happens at contract end or if you leave RISE. Key clauses: a buy-out clause giving you the option to purchase perpetual licences at a discounted rate if exiting subscription after a certain term, transition assistance providing a reasonable period for data migration or read-only access, and retaining a small number of on-premises licences active as insurance with reduced maintenance proportionally.
Future Flexibility Clauses
SAP typically locks customers into 3 to 5 year contracts. Negotiate: growth and shrinkage rights to adjust user quantities mid-term, reduction options if divesting a business unit, price protections capping renewal increases (for example max 3% per year), and model swap rights allowing transition between Public and Private without complete re-licensing.
Leverage SAP’s Strategic Goals
SAP is keen on moving customers to cloud. Ask SAP for comparative TCO analyses or trial periods, which can lead to improved financial terms. Be aware SAP may intentionally make on-premises deals less attractive to steer you to cloud. Demonstrate knowledge of this tactic to push for better on-premises terms as a credible alternative. If opting for cloud, negotiate value-added features: training credits, inclusion of SuccessFactors or Ariba at package rates, and BTP credits.
Indirect Access and Legal Protections
Address indirect use explicitly: get written confirmation of what is included. List all non-SAP front-ends and integrations and ensure coverage. Cloud contracts introduce new considerations (liability, data protection, SLA remedies). Have legal review. Ensure audit rights are reciprocal. Cap on indexation. Document everything. For detailed indirect access strategies, see our white paper on the top 10 pitfalls in SAP Digital Access.
Preparing for a Major SAP Negotiation?
Our team has negotiated hundreds of SAP contracts saving clients millions. See our SAP contract negotiation service.
SAP Contract Negotiation →6. CIO Recommendations & Next Steps
Seven-step action plan for S/4HANA deployment and licensing
Assess Business Requirements and IT Strategy
Map needs for flexibility, customisation, and control. Standardised processes point to Public Cloud. Industry-specific or regulatory requirements point to Private Cloud or On-Premise. Align with overall cloud strategy and digital transformation roadmap.
Build a Multi-Year TCO Comparison
5 to 10 year analysis for each model including software, infrastructure, internal support, implementation effort, and compliance/audit costs. Present to CFO and CEO with clear CapEx vs OpEx trade-offs. For TCO benchmarks, see our article on on-premise vs cloud TCO compared.
Engage Early with SAP and Independent Advisors
Discuss conversion programmes and incentives. Validate SAP’s claims with independent SAP licensing advisors or user groups (ASUG, DSAG). Informed perspective strengthens negotiations.
Strengthen Licence Management Governance
On-premises: maintain accurate user records, run SAP licence measurement tools regularly. Cloud: monitor FUE consumption, track Digital Access documents, watch contractual limits. Proactive management avoids compliance firefights.
Negotiate with the Future in Mind
Push for conversion rights, adjustment clauses, price locks, model swap options. Do not accept default contracts. Use the 2027 ECC deadline to negotiate from choice, not desperation. See our 10 SAP negotiation tactics white paper.
Plan for Organisational Change
S/4HANA (especially cloud) changes the operating model. Prepare IT teams and end-users for SaaS features, quarterly updates, and new UIs. Invest in change management to adopt standard practices and avoid expensive custom development.
Stay Informed on SAP’s Roadmap
RISE and GROW programmes continue evolving. Engage with user groups and analyst updates. Knowledge of new options or licensing models provides ongoing renegotiation leverage. See our SAP Knowledge Hub for the latest.
FUE Model = New Compliance Paradigm
Both Public and Private Cloud use Full User Equivalents. Right-size allocations by user category (Advanced 1.0, Core 0.2, Self-Service 0.03). Unused FUEs equal wasted spend. Cannot reduce mid-contract.
RISE Shifts CapEx to OpEx
RISE bundles licence, infrastructure, and support into a single subscription. Simplifies vendor management but makes cost breakdown less transparent. Once signed, you typically retire on-premises licences.
Audit Risk Does Not Disappear in Cloud
SAP retains audit rights across all models. Indirect access, user misclassification, and scope creep are risks everywhere. Negotiate clear metrics, Digital Access allowances, and audit procedures in every contract.
2027 Deadline = Negotiate Now
SAP ECC end-of-support creates urgency. The closer to 2027, the less leverage you have. Use time now to negotiate conversion rights, price protections, exit clauses, and model flexibility.
Frequently Asked Questions
Common questions about S/4HANA deployment models and licensing
FUE (Full User Equivalent) is SAP’s cloud licensing metric. One FUE represents one fully active user. Different user categories consume different fractions: Advanced Users = 1.0 FUE, Core Users = 0.2 FUE, Self-Service Users = 0.03 FUE, Developers = 2.0 FUEs. You purchase a block of FUEs and distribute them across user types. This tiered approach lets more light users be covered by fewer FUEs.
Yes. SAP offers Contract Conversion programmes that credit some existing investment toward RISE subscriptions. However, once you sign a RISE contract, you typically retire your previous on-premises licences for migrated systems. The conversion terms are negotiable: seek explicit credit amounts, ensure fair valuation of existing licences, and negotiate the right to convert additional licences at predetermined rates in the future.
No. While the SaaS model technically enforces some limits (you cannot add users beyond subscription), SAP retains full audit rights across all deployment models. Indirect access via third-party integrations, user misclassification, and scope creep remain risks. Cloud contracts should explicitly address Digital Access allowances, how metrics are measured, and audit procedures.
It depends entirely on your specific situation. On-premises can be most cost-effective over 10+ years if user counts are stable and you optimise licences well, but has high upfront costs. RISE and Private Cloud offer OpEx predictability and reduced IT overhead but may cost more over the same period. Public Cloud is simplest but least customisable. Build a 5 to 10 year TCO comparison including all components.
Start planning now. The closer to 2027, the less negotiating leverage you have. Assess which deployment model fits your needs. Engage SAP early for conversion programme details and incentives. Negotiate from a position of choice (multiple options evaluated) rather than last-minute desperation. Secure price protections, conversion rights, and flexibility clauses while SAP is motivated to accelerate cloud adoption.
Key negotiation points: conversion credit for existing licences, caps on annual price increases, exit and buy-out clauses, model swap rights (Public to Private), user quantity adjustment rights mid-term, clear Digital Access and indirect use coverage, SLA remedies and penalties, transition assistance at contract end, pricing locks for future user additions, and inclusion of value-added features (training credits, SuccessFactors/Ariba at package rates).