How the Shift from ECC to S/4HANA Changes Everything About SAP Licensing, Perpetual vs Subscription vs Hybrid Models Compared, Digital Access Document-Based Charging Explained, Full User Equivalent (FUE) Calculations and Optimisation, RISE with SAP Contract Dynamics, 2026 Price Trends and True-Up Mechanics, Common Overspend Traps and Audit Risks, and the Negotiation Framework for Reducing S/4HANA Costs
SAP S/4HANA licensing represents a structural break from the ECC licensing model that enterprises have managed for two decades. Instead of simply counting named users with annual maintenance, S/4HANA introduces subscription pricing (via RISE with SAP), Full User Equivalent (FUE) calculations that normalise different user types into a single metric, Digital Access document-based charging for indirect use, and higher-stakes audit mechanics with steeper true-up clauses.
The financial stakes are significant: the difference between an optimised and unoptimised S/4HANA deal can be $2M–$10M+ over a 5-year term for mid-to-large enterprises. Getting the licensing model right — perpetual vs subscription vs hybrid — is a board-level decision with multi-year cost implications. For the complete SAP licensing knowledge base, see the SAP Licensing Knowledge Hub.
| Licensing Dimension | SAP ECC (Legacy) | SAP S/4HANA (2026) | Cost/Risk Impact |
|---|---|---|---|
| Pricing model | Perpetual licence + ~22% annual maintenance | Perpetual, subscription (RISE), or hybrid — multiple models with different cost structures | Model selection alone can create $1M–$5M+ difference over 5 years |
| User metrics | Named users: Professional, Limited, Self-Service | FUE model: Advanced (1.0), Core (0.2), Self-Service (0.033) — plus legacy named user options | Mis-estimating user mix can cause 20–40% over or under-licensing |
| Indirect/Digital Access | Ambiguous — led to litigation (Diageo case) | Formalised Digital Access with 9 document types and tiered pricing | Unmanaged Digital Access creates $500K–$10M+ audit exposure |
| Contract structure | Perpetual with annual renewal of maintenance | 3–7 year subscription commitments with minimum FUE counts and limited reduction rights | Lock-in risk: cannot reduce mid-term; renewal price increases of 5–7% |
| Audit posture | Periodic SAP audits on named user counts | More aggressive audits targeting Digital Access, FUE over-allocation, and cloud compliance | SAP using audits to accelerate ECC-to-S/4HANA migration |
Enterprises face three primary S/4HANA licensing models, each with distinct financial profiles and risk characteristics. For the detailed TCO comparison, see On-Premise vs Cloud for S/4HANA: TCO Compared. For RISE-specific contract dynamics, see S/4HANA Cloud (RISE) vs On-Premise Licensing.
| Dimension | Perpetual On-Premise | Subscription (RISE with SAP) | Hybrid |
|---|---|---|---|
| Cost structure | One-time CapEx licence + ~22% annual support | Annual OpEx subscription — bundles software, infrastructure, and support | Mix of CapEx (on-prem) and OpEx (cloud) — requires careful management |
| 5-year TCO (1,000 users, illustrative) | $5M licence + $5.5M support = $10.5M | $3M/year × 5 = $15M (subscription never stops) | Varies: typically between perpetual and full subscription |
| Ownership | You own the licence indefinitely | You lose access if subscription ends | Own on-prem; subscription for cloud portions |
| Flexibility to reduce | Can reduce users (stop paying support on unused) | Cannot reduce FUE mid-term; locked into minimum commitment | Mixed — on-prem flexible; cloud locked |
| Infrastructure responsibility | Customer manages hardware, OS, patching | SAP/hyperscaler manages everything | Split responsibility |
| Upgrade path | Customer controls timing (can delay upgrades) | SAP manages upgrades (less control but always current) | On-prem can lag; cloud stays current |
| Best for | Long-term stability, strong IT team, cost control over 7+ years | Speed to deploy, OpEx preference, small-to-mid IT organisations | Phased migration, risk distribution, large enterprises with diverse requirements |
For migration credit negotiation tactics, see How to Negotiate S/4HANA Licensing Conversions and Migration Credits. For the CIO migration playbook, see CIO Playbook: Migrating from SAP ECC 6.0 to S/4HANA.
The FUE model is SAP's unified licensing metric for S/4HANA Cloud and RISE. Instead of buying specific named user types, organisations buy a pool of FUEs and allocate them across user categories. For the complete FUE calculation methodology, see FUE Licensing in S/4HANA: User Classifications and Optimization.
| User Category | FUE Weight | Users per 1 FUE | Typical Role | Annual Cost per User (illustrative, negotiated) |
|---|---|---|---|---|
| Advanced User | 1.0 FUE | 1 | Full SAP access: finance managers, supply chain leads, power users across modules | $1,200–$1,800 |
| Core User | 0.2 FUE | 5 | Operational roles: AP clerks, warehouse operators, sales coordinators — limited to specific transactions | $240–$360 |
| Self-Service User | 0.033 FUE | 30 | Employee self-service: leave requests, expense reports, time entry, basic approvals | $40–$60 |
FUE Calculation Example: An organisation with 50 Advanced users, 200 Core users, and 3,000 Self-Service users needs: (50 × 1.0) + (200 × 0.2) + (3,000 × 0.033) = 50 + 40 + 99 = 189 FUEs. With SAP's minimum purchase requirements, the actual contract might be 200 FUEs.
For guidance on mapping legacy ECC user types to S/4HANA categories, see Mapping Legacy SAP ERP Licences to S/4HANA User Roles. For licence type definitions, see S/4HANA Licensing Types: Professional, Limited, and Self-Service.
Digital Access licensing is SAP's formalised model for charging when non-SAP systems create transactional documents in S/4HANA. It replaces the ambiguous 'indirect access' rules that led to high-profile litigation. For Digital Access advisory services, see SAP Digital Access Advisory Service.
| Document Type | What Triggers It | Common Source Systems | Compliance Risk Level |
|---|---|---|---|
| Sales Orders | Order created in SAP by external e-commerce, CRM, or EDI system | Salesforce, Shopify, SAP Commerce Cloud, EDI | Very high — highest volume for customer-facing enterprises |
| Purchase Orders | PO created in SAP by procurement platform or supplier portal | Ariba, Coupa, supplier EDI | High — especially for organisations with automated procurement |
| Invoices (customer) | Invoice generated in SAP triggered by external billing system | Billing platforms, subscription management tools | High for high-transaction businesses |
| Invoices (supplier) | Supplier invoice posted to SAP via AP automation | Basware, Tungsten, OpenText | Medium-high |
| Deliveries / Goods Movements | Delivery or goods receipt created by WMS or logistics platform | Manhattan Associates, Blue Yonder, custom WMS | Medium |
| Manufacturing Orders | Production order created by MES or scheduling system | MES platforms, IoT systems | Medium for discrete manufacturing |
| Read-only / Query access | External system reads data from SAP (no document creation) | BI tools, reporting, dashboards | No Digital Access charge — only creation events are counted |
For the complete Digital Access adoption programme (DAAP) analysis, including the 90% discount option and 15% growth headroom option, contact our SAP Digital Access Advisory Service.
RISE with SAP is SAP's flagship subscription offering that bundles S/4HANA software, infrastructure (on SAP or hyperscaler), Business Technology Platform (BTP) credits, and support into a single annual fee. For complete RISE negotiation guidance, see RISE with SAP Negotiations Guide. For RISE advisory, see SAP RISE Advisory Services.
| RISE Contract Element | SAP's Standard Position | Risk to Customer | What to Negotiate |
|---|---|---|---|
| Term length | 3–7 years (SAP prefers longer) | Long lock-in with limited exit options | Shorter initial term (3 years) with renewal options; negotiate exit rights at year 3 |
| FUE minimums | 40 FUE minimum (private); 35 FUE (public cloud) | Over-licensing for smaller deployments | Negotiate lower minimum if deployment is below threshold; request credits for unused FUEs |
| Price increase at renewal | 5–7% uplift at renewal (standard clause) | Multi-million dollar cost creep over contract lifecycle | Cap renewal increases at 0–3%; lock in renewal pricing at contract signing |
| BTP credits | Included but often insufficient for real usage | BTP overage charges are expensive | Negotiate additional BTP credits; see Negotiating BTP in Your SAP Deal |
| ECC licence conversion credits | SAP offers credits for converting existing perpetual licences to RISE subscription | Credits may not cover full perpetual licence value; you surrender perpetual rights | Maximise conversion credit value; negotiate to retain perpetual fallback rights |
| Reduction rights | No mid-term reduction — locked into contracted FUE/spend | Cannot reduce if business shrinks or restructures | Negotiate 10–20% reduction right at each annual anniversary or at renewal |
For RISE contract challenges and trap avoidance, see S/4HANA RISE Contract and Licensing Challenges. For termination and downsize rights, see SAP Termination and Downsize Rights.
The headline S/4HANA licence cost represents only part of the total investment. Several 'hidden' costs consistently catch enterprises by surprise. For the complete hidden costs analysis, see S/4HANA Add-Ons and HANA Database Licensing Costs. For SAP AI licensing after the July 2025 changes, see SAP AI and Data Licensing Strategies.
| Hidden Cost | What It Is | Typical Impact | How to Manage |
|---|---|---|---|
| HANA database licensing | S/4HANA requires SAP HANA — licensed separately by memory (GB of RAM) | $500K–$3M+ for enterprise HANA instances (256GB–2TB+) | Negotiate HANA as part of the S/4HANA deal; right-size memory allocation |
| Support fee inflation | SAP charges ~22% annual support on net licence value; has imposed periodic increases | $100K–$1M+ annual increase without caps | Negotiate support fee caps (max 3% annual increase); consider third-party support for stable modules |
| BTP overage | Business Technology Platform usage exceeding included credits incurs additional charges | $50K–$500K+ depending on integration complexity | Negotiate additional BTP credits upfront; monitor consumption monthly |
| SAP AI features | New AI capabilities (Joule, embedded AI) may require additional licences or premium editions | $100K–$1M+ depending on AI scope and user count | Clarify AI licensing in contract; negotiate included AI features |
| Embedded analytics add-ons | Advanced analytics, planning, and reporting tools beyond standard S/4HANA may require additional licences | $50K–$500K+ | Evaluate which analytics are included in base vs add-on |
| Retired component replacement | Legacy SAP components retired in S/4HANA migration must be replaced with new solutions (often additional cost) | $100K–$2M+ per component | See Retiring Old SAP Components During S/4HANA Migration |
S/4HANA consolidates many previously separate SAP products into the core system. However, some embedded features require additional licensing or have usage restrictions that differ from the standalone versions. For the complete embedded features licensing guide, see Navigating Licensing for New S/4HANA Embedded Features.
| Embedded Feature | Previously Separate Product | S/4HANA Licensing Status | Cost Implication |
|---|---|---|---|
| Embedded Analytics | SAP BW (Business Warehouse) | Included in S/4HANA base licence for operational reporting | No additional cost for standard embedded analytics |
| Extended Warehouse Management (EWM) | SAP EWM (standalone) | Included in base but advanced features may require additional licence | Verify which EWM features are included vs additional |
| Transportation Management (TM) | SAP TM (standalone) | Embedded in S/4HANA but may require premium edition or add-on | $200K–$1M+ if advanced TM capabilities needed beyond basic |
| Asset Management | SAP PM / EAM | Included in S/4HANA base | No additional cost for standard capabilities |
| Advanced ATP (Available to Promise) | SAP APO | Embedded but advanced scenarios may require additional licensing | Depends on complexity of ATP requirements |
| Central Finance | New capability | Available as part of S/4HANA — requires appropriate user licences | User licences cover access; no separate module licence needed |
Understanding which features are included vs additional is critical during S/4HANA migration planning. For deployment model implications, see SAP S/4HANA Deployment Models and Licensing Implications.
SAP audit and compliance risks in S/4HANA differ from ECC. SAP has become more assertive in audits, particularly targeting organisations delaying migration. For SAP audit defence, see SAP License Audit Defense Service.
| Overspend Trap / Audit Risk | How It Happens | Financial Impact | Prevention |
|---|---|---|---|
| Over-allocating Advanced users | Defaulting all users to Advanced (1.0 FUE) instead of categorising by actual role | 2×–5× excess FUE purchase; $500K–$5M+ overspend | Detailed user role analysis; assign Core (0.2) or Self-Service (0.033) wherever appropriate |
| Unmanaged Digital Access | External systems creating SAP documents without Digital Access licences | $500K–$10M+ audit exposure for unlicensed document creation | Conduct Digital Access assessment; licence document types proactively |
| Shelfware from over-purchasing | Buying more FUEs or modules than needed — especially when bundled with RISE | $200K–$2M+ in unused licences that cannot be reduced mid-term | Right-size before signing; negotiate reduction rights at renewal |
| Support fee creep | SAP applies annual support increases above initial contracted rate | $100K–$1M+ cumulative over 5 years | Cap support increases contractually; review support invoices annually |
| Dual licensing during migration | Running ECC and S/4HANA simultaneously without dual-use rights | Double licensing cost during migration period (potentially $1M–$5M+) | Negotiate dual-use rights for migration period; document timeline |
| BTP overage surprise | Exceeding included BTP credits without monitoring consumption | $50K–$500K+ in unplanned BTP charges | Monitor BTP consumption monthly; negotiate additional credits |
Every S/4HANA contract is negotiable. SAP's list prices are starting positions, and enterprise customers routinely achieve 30–50% discounts. For the complete SAP negotiation playbook, see Negotiating with SAP: A CIO's Playbook. For professional negotiation support, see SAP Contract Negotiation Service.
| Negotiation Lever | How to Execute | Expected Impact | SAP's Counter |
|---|---|---|---|
| Competitive alternatives | Present Oracle Cloud ERP, Microsoft Dynamics 365, or Workday quotes before engaging SAP | 20–40% discount from SAP | SAP will emphasise integration, ecosystem, and switching costs |
| Fiscal quarter-end timing | SAP's fiscal year ends Dec 31; quarters end Mar 31, Jun 30, Sep 30, Dec 31 — negotiate close to these dates | 10–25% additional discount from SAP rep quota pressure | SAP may pressure for rushed signing; resist without full term review |
| ECC licence conversion credits | Demand maximum credit for existing perpetual ECC licences being converted to RISE | $1M–$10M+ in credits applied to RISE subscription | SAP may undervalue existing licences; insist on fair market value or historical purchase price |
| Bundle deal | Combine S/4HANA with BTP, SuccessFactors, Ariba, and other SAP products in a single negotiation | 15–30% volume discount across the bundle | SAP prefers large deals — use aggregation as leverage |
| Cap renewal price increases | Insert contractual cap on annual/renewal price increases at 0–3% | $500K–$3M+ saved over 5–7 year term vs uncapped 5–7% increases | SAP's standard is 5–7% — push back firmly |
| Negotiate dual-use rights | Secure contractual right to run ECC and S/4HANA concurrently during migration without double licensing | Avoids $1M–$5M+ in duplicate licence costs during transition | SAP usually agrees if time-limited (12–24 months) and part of a migration plan |
For S/4HANA cost modelling, see Modelling S/4HANA Licensing Costs After ECC Migration. For S/4HANA licence optimisation strategies, see S/4HANA License Optimization Strategies.
| # | Action | Owner | Timing | Key Outcome |
|---|---|---|---|---|
| 1 | Conduct user role analysis: map every user to Advanced, Core, or Self-Service; calculate total FUE requirement | SAM / IT / Business | Before any S/4HANA deal | Accurate FUE sizing — avoid 20–40% over/under-licensing |
| 2 | Run Digital Access assessment: count document volumes by type across all interfaces; determine if document-based licensing is more cost-effective than named users | SAM / Integration Team | Before contract signing | Digital Access compliance with no audit surprises |
| 3 | Model 5-year TCO for perpetual vs subscription vs hybrid: include licence, support, infrastructure, migration, and hidden costs | Finance / IT / Procurement | Before model selection | Data-driven licensing model decision |
| 4 | Obtain competitive quotes from Oracle Cloud ERP, Microsoft Dynamics 365, or Workday before engaging SAP | Procurement | 6–12 months before deal | Competitive leverage for 20–40% SAP discount |
| 5 | Maximise ECC licence conversion credits: document all existing perpetual licences and demand fair market value credit against RISE subscription | Procurement / SAM | During negotiation | $1M–$10M+ in credits applied to new contract |
| 6 | Negotiate critical contract terms: annual price cap (0–3%), reduction rights (10–20% at renewal), dual-use rights for migration, additional BTP credits | Procurement / Legal | During negotiation | Cost certainty and flexibility over contract term |
| 7 | Evaluate embedded features: determine which S/4HANA embedded capabilities replace standalone SAP products and whether additional licensing is required | Enterprise Architecture / SAM | During migration planning | No unexpected licence costs for embedded features |
| 8 | Plan for hidden costs: budget separately for HANA database licensing, BTP overage, AI capabilities, retired component replacement, and support fee increases | Finance / IT | Before deal signing | Complete cost picture — no budget surprises post-signing |
| 9 | Implement ongoing FUE governance: monitor user-to-FUE allocation quarterly; reassign FUEs from dormant users; maintain headroom for growth | SAM | Quarterly from go-live | Continuous compliance and cost optimisation |
| 10 | Begin renewal negotiation 12+ months before contract expiry: re-benchmark pricing, reassess FUE and Digital Access requirements, and present competitive alternatives | Procurement / SAM | 12 months pre-renewal | Avoid auto-renewal at inflated pricing; secure competitive renewal terms |
For expert assistance with S/4HANA licensing, RISE negotiations, Digital Access compliance, and SAP audit defence, Redress Compliance provides independent advisory through our SAP License Optimization Services, SAP Contract Negotiation Service, SAP Digital Access Advisory Service, and SAP RISE Advisory Services.
S/4HANA licensing covers the commercial terms for using SAP's next-generation ERP. It includes user-based licensing (via named users or Full User Equivalents), Digital Access document-based licensing for indirect use, and optional subscription models via RISE with SAP. The licensing model differs significantly from legacy ECC.
Perpetual licensing is a one-time purchase (CapEx) with ongoing ~22% annual support. Subscription (RISE with SAP) is an annual fee (OpEx) that bundles software, infrastructure, and support. Perpetual is typically cheaper over 7+ years; subscription is cheaper short-term with lower upfront cost but higher total cost over time.
FUE is SAP's normalised user metric for S/4HANA Cloud. Advanced users = 1.0 FUE, Core users = 0.2 FUE (5 per FUE), Self-Service users = 0.033 FUE (30 per FUE). Organisations purchase a pool of FUEs and allocate them across user categories based on role requirements.
Digital Access is SAP's licensing model for indirect use — when non-SAP systems create transactional documents (sales orders, POs, invoices, etc.) in S/4HANA. SAP charges by document volume across 9 defined document types with tiered pricing. Unmanaged Digital Access is a major audit risk.
RISE with SAP is SAP's flagship subscription offering that bundles S/4HANA software, infrastructure (SAP or hyperscaler), BTP credits, and support. It typically requires a 3–7 year commitment with minimum FUE purchases and limited mid-term reduction rights.
List prices vary significantly by deployment model and user count. Illustrative ranges: perpetual on-premise licences of $2,500–$4,000 per named user, RISE subscriptions of $100–$200 per user per month (depending on user type), plus HANA database licensing and support. Enterprise deals typically achieve 30–50% off list.
For perpetual licences, you can stop paying support on unused licences (subject to contract terms). For RISE subscriptions, SAP's standard terms do not allow mid-term reduction — you are locked into the contracted FUE count until renewal. Negotiate reduction rights (10–20%) during contract negotiation.
The top risks are: over-allocating Advanced users (2×–5× excess FUE spend), unmanaged Digital Access ($500K–$10M+ audit exposure), support fee creep, dual licensing during ECC-to-S/4HANA migration, shelfware from over-purchasing, and BTP overage charges.
SAP uses tiered pricing by document volume across 9 document types. The first tier has the highest per-document rate; rates decrease with volume. SAP offered a Digital Access Adoption Program (DAAP) with options including 90% discount on document licences. Contact SAP or an independent advisor to assess your document volumes and optimal approach.
SAP offers credits for converting existing perpetual ECC licences to RISE subscriptions. The credit value varies — SAP may offer 30–60% of original licence value applied over the RISE term. Negotiate to maximise credit value and clarify whether you retain any perpetual fallback rights.
SAP conducts licence audits (often annually via LAW measurement reports) checking user counts, FUE allocation, Digital Access document volumes, and module usage against contracted entitlements. Findings require true-up purchases. SAP has become more aggressive, using audits to accelerate ECC-to-S/4HANA migration.
Key hidden costs include HANA database licensing ($500K–$3M+ for enterprise instances), support fee inflation, BTP overage charges, SAP AI feature licensing, retired component replacement costs, and any embedded feature add-on licensing required beyond the S/4HANA base.
Begin at least 12 months before contract expiry. Reassess FUE requirements, benchmark pricing against competitive alternatives, evaluate whether perpetual or subscription model still fits, and negotiate renewal terms before SAP's auto-renewal clauses activate.
Key differences: FUE replaces simple named user counts, Digital Access formalises indirect use charging, subscription models (RISE) shift from CapEx to OpEx, minimum commitments and limited reduction rights increase lock-in, and support cost inflation mechanisms are more aggressive.
This article is part of our SAP S/4HANA Licensing pillar. Explore related guides:
Redress Compliance provides independent SAP licensing advisory services — fixed-fee, no vendor affiliations. Our specialists have helped enterprises save millions through strategic licence optimization, Digital Access negotiation, and contract restructuring.
Explore SAP Advisory Services →Redress Compliance has helped hundreds of Fortune 500 enterprises — typically saving 15–35% on Oracle renewals, ULA negotiations, and audit defense.
100% vendor-independent · No commercial relationships with any software vendor
Book a free consultation with our licensing specialists. No obligations, no vendor ties — just independent advice tailored to your situation.
Book Your Free Consultation →