📋 Table of Contents
S/4HANA licensing in 2026 demands strategic urgency. Gone are the days when SAP licensing meant simply counting named users. Today's landscape is a complex mix of perpetual licences, cloud subscriptions, and usage fees based on document volumes. CIOs and CFOs face a structurally different model than legacy ECC, with high financial stakes for missteps.
Every aspect of your SAP S/4HANA agreement, from user counts and Digital Access documents to contract terms, can become a cost trap or a cost advantage. SAP is aggressively pushing customers to S/4HANA (often via RISE with SAP subscriptions) ahead of ECC's 2027 support deadline. The right licensing strategy can save millions, prevent compliance crises, and give you a competitive edge in digital transformation.
1. The Big Shift from ECC — What Has Changed in Pricing and Risk
Transitioning from SAP ECC to S/4HANA is not merely a technical upgrade. It is a fundamental shift in pricing models and risk exposure. Under ECC, companies primarily managed perpetual licences and a stable of named user types (Professional, Limited, Self-Service) with annual maintenance fees. S/4HANA introduces entirely new variables.
| Dimension | SAP ECC (Legacy) | SAP S/4HANA (New) |
|---|---|---|
| Licence Model | Perpetual + annual maintenance (~22%) | Perpetual OR subscription (RISE with SAP) |
| Cost Structure | CapEx (one-time purchase) | CapEx or OpEx (recurring subscription) |
| User Metrics | Named users (Professional, Limited, Self-Service, Developer) | Named users (on-prem) or Full User Equivalents (FUE) (cloud) |
| Indirect Access | Ambiguous, led to lawsuits (Diageo 2017) | Formal Digital Access model (9 document types) |
| Database | Choice of Oracle, SQL Server, DB2, etc. | Mandates SAP HANA, requires separate licence |
| Audit Intensity | Standard periodic audits | More assertive, steeper true-up clauses, fewer loopholes |
ECC-Era Thinking Will Fail in the S/4HANA Era
An ECC licensing strategy applied to S/4HANA will result in surprise costs and weaker negotiation positions. It is critical to unlearn old assumptions (such as "we just buy more named users if needed") and reframe your approach around S/4HANA's new metrics: FUE, Digital Access, and subscription economics. Executives must treat this as a boardroom issue, not just an IT procurement exercise.
Read: CIO Playbook: SAP S/4HANA Deployment Models | 3 Major SAP Licensing Models
2. The Licensing Spectrum — Perpetual, Subscription, Hybrid
In 2026, enterprises have three primary S/4HANA licensing models. Understanding this spectrum is key to picking a cost-effective path and negotiating the right terms. For a deep-dive comparison, see our RISE vs. On-Premise licensing guide.
| Model | How It Works | Best For | Watch Out For |
|---|---|---|---|
| Perpetual On-Premise | One-time CapEx purchase + 22% annual support. You own the licence indefinitely and run S/4HANA in your data centre. | Long-term stability, strong IT teams, control-focused organisations | High upfront cost, shelfware risk, you manage infrastructure and upgrades |
| Subscription (RISE with SAP) | Annual/monthly OpEx fee per FUE. Bundles software, infrastructure, and support. SAP handles upgrades. | Speed, OpEx preference, organisations lacking infrastructure teams | Vendor lock-in, no reduction during term, higher 5-year TCO, loss of perpetual rights |
| Hybrid | Mixed model: on-prem for some systems, cloud for others. Common during migration transitions. | Phased migrations, organisations with diverse regional requirements | Dual-running costs, complex governance, risk of double-counting users |
📊 5-Year TCO Comparison: Perpetual vs. RISE
Scenario: 500-user S/4HANA deployment
Perpetual: $5M licence + $1.1M/year support = $10.5M over 5 years
RISE: ~$150/user/month × 500 × 60 months = $4.5M... but list price. Negotiated at 40% discount = $2.7M. Plus migration costs, BTP fees, and renewal increases.
At first glance RISE looks cheaper, but factor in renewal price escalation (5–7% per year), loss of perpetual asset value, and reduced flexibility. Always run a complete 5-year and 10-year TCO model before committing. Use our S/4HANA migration cost estimator to model your specific scenario.
Perpetual often wins at 7+ years. Subscription wins on cash flow and speed.
Read: SAP RISE Negotiations Guide | On-Premise vs Cloud TCO Compared | RISE vs. Traditional Licensing
Need help evaluating perpetual vs. RISE for your specific situation?
RISE with SAP Advisory →3. Digital Access Deep Dive — Document-Based Charging
One of the most significant licensing changes in the S/4HANA era is SAP Digital Access, SAP's formal response to the indirect access problem. Rather than requiring a named user licence for every external system or person that touches SAP, Digital Access charges by documents created in SAP via non-SAP systems. For a full explanation of the nine document types, see The 9 Document Types in SAP Digital Access Explained.
SAP has defined nine document categories: Sales Orders, Purchase Orders, Invoices, Deliveries, Material Documents, Service Confirmations, Manufacturing Orders, Quality Notifications, and Time Confirmations. Whenever a non-SAP system creates one of these in your S/4HANA environment, it counts as a digital document requiring a licence.
Digital Access Charge = Document Volume × Tiered Unit Price
SAP only charges for document creation events. Viewing, querying, or updating documents does not incur additional cost.
| Aspect | Detail |
|---|---|
| What counts | Documents created by non-SAP systems (e-commerce platforms, supplier portals, RPA bots, IoT devices) |
| What doesn't count | Documents created by licensed named users, data queries/reads, document updates after creation |
| Pricing model | Tiered: first million documents at base rate, subsequent millions at lower unit cost. See Digital Access pricing explained |
| Measurement tools | SAP Estimation Tool (can overcount), SAP Passport Tool (more precise but requires system updates) |
| DAAP incentives | 90% discount if you buy coverage for all current usage, or 15% growth headroom at full price. See DAAP guide |
Digital Access Is a Top Audit Focus in 2025–2026
SAP auditors now routinely run scripts to identify interfaces and count documents. High-risk scenarios include: Salesforce creating thousands of orders in SAP, RPA bots generating transactions, IoT devices producing material documents, and any scenario with thousands of external users indirectly accessing SAP. Without a Digital Access licence, SAP could claim each external user needs a named user licence, creating a potentially catastrophic compliance exposure. Assess your risk with our free Digital Access risk assessment.
Read: How Digital Access Impacts S/4HANA and RISE Contracts | How to Lower Document Counts | Digital Access Audit Defense
Get ahead of it before SAP audits you. Conduct an internal Digital Access assessment now.
Digital Access Advisory →4. FUE in Action — Calculations, Risks & Optimisation
SAP's Full User Equivalent (FUE) model is the primary metric for S/4HANA Cloud and RISE licensing. It normalises different user types into a single unified metric for pricing. Think of 1 FUE as one "full" user in terms of system usage. For a complete walkthrough, see our FUE licensing explained guide.
1 Advanced = 1 FUE | 5 Core = 1 FUE | 30 Self-Service = 1 FUE
You buy a pool of FUEs and allocate them to users as needed using these conversion ratios.
| User Type | FUE Weighting | Typical Role | ECC Equivalent |
|---|---|---|---|
| Advanced | 1.0 FUE | Power users, full access across all modules, create/modify/report | Professional User |
| Core | 0.2 FUE | Operational users, restricted to specific modules or transactions | Limited Professional |
| Self-Service | ~0.033 FUE | Light users, ESS, time entry, leave requests, basic approvals | Employee Self-Service |
📊 FUE Calculation Example
Organisation: 50 Advanced users + 200 Core users + 1,500 Self-Service users
50 × 1.0 = 50 FUE | 200 × 0.2 = 40 FUE | 1,500 × 0.033 = 50 FUE
Total: 140 FUE required. Use our FUE licensing calculator to model your own scenario.
FUE Risks and Traps
Mis-estimating your user mix is the biggest danger. If you assume mostly Core users but reality demands more Advanced users, you will be under-subscribed. Conversely, overestimating heavy users means you bought more FUE than necessary.
Minimum commitments apply: RISE private edition typically requires 40+ FUE minimum, public cloud 35+. These minimums can force over-licensing in smaller deployments. See RISE Private vs Public Cloud for deployment option details.
No reduction during term: Once committed to a FUE count, you generally cannot decrease until renewal. If your workforce shrinks, you pay for unused capacity. Read about SAP termination and downsize rights.
Read: FUE Licensing: User Classifications & Optimisation | S/4HANA Licensing Types Explained | Mapping Legacy Licences to S/4HANA Roles
Need help right-sizing your FUE pool? Our team models user populations and negotiation scenarios.
SAP License Optimisation →5. 2025 Price Dynamics — Tiers, Blocks & the True-Up Game
SAP's pricing is deliberately opaque, but patterns emerge. No large customer pays list price. Discounts of 30%, 50%, even 70% are common in enterprise deals. SAP has internal volume bands where larger purchases unlock steeper discounts. For benchmark data, see our SAP Discount and Pricing Benchmarks Guide.
| Pricing Dynamic | How It Works | Negotiation Strategy |
|---|---|---|
| Volume tiers | More users/FUEs = lower per-unit cost. SAP has internal bands for higher discounts. | Bundle purchases into one deal to hit higher tiers. Aggregate across business units. |
| Block pricing | Digital Access docs sold in blocks (e.g., 1M). Need 1.2M? Buy 2M block. | Negotiate pro-rated overages instead of full-block purchases. Smooth out price cliffs. |
| True-ups | Periodic adjustments for usage exceeding licences. Audit or renewal-driven. | Pre-negotiate price protections: additional FUEs at same discount during term. |
| Support inflation | 22% of net licence annually, but SAP has raised rates. Compounds over time. | Negotiate caps (e.g., max 3%/year increase). See support negotiation strategies. |
| Cloud renewal uplift | RISE contracts often allow 5–7% price increase on renewal. | Lock renewal pricing now: "capped at 3%" or "right to renew at same rate for X years." |
True-Up on Your Terms, Not SAP's
It is always better to proactively approach SAP and say "we've added 50 users, we want to purchase them under our existing deal conditions" than to let an audit discover them. If your growth triggers a significant licence increase, use that as leverage to renegotiate the entire deal. You deserve a better volume discount at the new, higher volume. Pre-negotiate a price schedule for growth in your original contract.
Read: S/4HANA: Models, Costs & Strategic Considerations | Negotiating with SAP: A CIO's Playbook | SAP Cost Drivers & Optimisation
6. Common Failure Points — Where Enterprises Overspend
| Failure Point | What Happens | Cost Impact | Solution |
|---|---|---|---|
| Shelfware | Buying more licences than needed: overestimation or SAP-bundled extras sit unused | Paying support on 300+ unused licences = $250K+/year wasted | Start small, add with price protections. Use our shelfware assessment. |
| User misclassification | Assigning Professional licences to users who only need Limited or Self-Service | Professional costs up to 20× Self-Service. 500 downgradeable users = massive savings | Profile users by transaction usage data (USMM/LAW). Assign minimum privilege licence per role. |
| Cloud creep | Uncontrolled addition of users, integrations, modules in cloud subscriptions | Unexpected overage bills, true-up costs at renewal | Treat FUE/user counts as hard quotas. No new user group goes live without licence check. |
| Wrong package | Buying top-tier S/4HANA edition with modules you will never deploy | Paying for fluff: 40% of bundle functionality unused | Match packages to realistic 1–2 year roadmap. See RISE tiers & packaging changes. |
| Dual-running costs | Running ECC maintenance + S/4HANA subscription simultaneously during migration | Double-paying for same capability for 12–24+ months | Negotiate contractual grace periods. See cutting ECC maintenance costs. |
Real-World Optimisation: User Reclassification Saves $2.1M
A global manufacturer migrating to S/4HANA identified that out of 500 total users, only 100 were true power users needing Professional licences. The other 400 were scoped to single departments and could use Limited licences. By negotiating the correct licence mix instead of defaulting all 500 to Professional, the organisation saved $2.1M over 5 years in licence and support costs. See more SAP case studies.
Read: S/4HANA License Optimisation Strategies | Named User License Optimisation | Top 10 SAP Licensing Pitfalls
7. Matching Licensing to Corporate Strategy — M&A, Cloud & Beyond
Your SAP licensing strategy must align with your broader corporate strategy. Two companies with identical SAP systems might make very different licensing choices if one is planning an acquisition and the other is divesting a business. For detailed M&A guidance, see our SAP Licensing for M&A and Divestitures guide.
Mergers & Acquisitions
Merging two SAP-using companies: SAP licences are typically non-transferable. Post-merger, you must consolidate contracts via SAP's approval. Use this as an opportunity to negotiate a new, combined contract with higher volume (better discounts) and eliminate duplicates. Watch out for compliance gaps during Transitional Service Agreements.
Acquiring a non-SAP company: Count new users and include in your licence growth plans. Pre-negotiate add-on pricing (e.g., 20% more users at same discount) for anticipated acquisitions.
Divestitures: Licences cannot be transferred to the spun-off entity without SAP's agreement. Negotiate carve-out clauses and TSA periods now, before the divestiture, or the buyer faces licensing SAP from scratch under duress.
Cloud Strategy Alignment
If your strategy is "cloud-first," ensure your licence contract supports the journey. Negotiate the ability to sunset on-prem maintenance without penalty or trade perpetual licences for cloud subscription credits. If staying on-prem for critical systems, resist SAP forcing a one-size cloud deal.
AI and RPA Create Hidden Licensing Obligations
RPA bots and AI agents interfacing with SAP are either indirect access scenarios (triggering Digital Access document charges) or may require named user licences. SAP does not sell cheaper licences for bots. If you plan to deploy dozens of bots, negotiate a licensing approach upfront. See our SAP AI & Data Licensing Strategies guide.
Read: Modelling Costs After ECC Migration | ECC to S/4HANA Conversion Strategies | Managing SAP Notifications for Company Changes
8. Red Flags and Deal Killers
These are the mistakes that cost enterprises millions, and are often invisible until it is too late:
9. Negotiating a Better S/4HANA Deal
Every SAP negotiation is a high-stakes commercial exercise. The difference between a well-negotiated deal and a poorly-negotiated one can be millions of dollars over the contract term. For comprehensive tactics, see our SAP Contract Negotiation Playbook.
| Tactic | How to Execute | Expected Impact |
|---|---|---|
| Aggregate demand | Bundle all SAP purchases into one deal: users, Digital Access, BTP, analytics, to hit higher discount tiers | 10–20% better discount vs. piecemeal buying |
| Create competitive pressure | Position alternatives: staying on ECC with third-party support, evaluating Workday/Oracle Cloud. SAP must believe you have options. | Unlocks SAP's best discounts |
| Lock renewal pricing | Negotiate caps on renewal increases (e.g., max 3%/year) and right to renew at same terms | Prevents 25–35% cost escalation over two contract terms |
| Pre-negotiate growth pricing | Establish that additional FUEs/users during term are at same discount as initial purchase | Prevents SAP from charging list price on mid-term growth |
| Negotiate dual-use rights | Request 12–18 month period where ECC and S/4HANA run concurrently without double licence fees | Eliminates $1M+ in dual-running costs during migration |
| Address Digital Access proactively | Conduct internal assessment and include document volumes in the deal at negotiated rates | Avoids audit exposure and gets best pricing (DAAP-style discounts) |
Timing Is Everything
SAP's fiscal year ends in December, and sales teams face intense pressure to close deals in Q4. Negotiating in October–December gives you maximum leverage. SAP will offer better discounts and more concessions to meet their targets. Conversely, negotiating in Q1 (January–March) gives SAP all the time in the world to hold firm. Plan your negotiation timeline strategically. See SAP Negotiation Tactics for more.
Read: Negotiating with SAP: CIO Playbook | Negotiating for Audit Protection | S/4HANA Conversion Discounts & Migration Credits
Preparing for an SAP negotiation? Get independent advisory to maximise your position.
SAP Contract Negotiation Service →10. Action Checklist — 5 Things to Do Now
Run a Complete Licence Baseline
Map every SAP user, their actual transaction usage, and their current licence type. Identify misclassified users, shelfware, and unlicensed usage. This is your negotiation foundation. Use USMM/LAW/SLAW tools for data extraction.
Assess Digital Access Exposure
Count documents created by non-SAP systems. Use SAP's Estimation Tool or engage independent advisory. Decide whether to adopt the document model or maintain named user coverage. Try our Digital Access cost calculator.
Model Your 5-Year TCO
Compare perpetual vs. RISE vs. hybrid scenarios with realistic assumptions about growth, support escalation, renewal pricing, and migration costs. Do not rely on SAP's TCO calculator. Use our S/4HANA migration cost estimator and RISE vs On-Premise assessment.
Review Contract Terms for Gaps
Check your current SAP agreements for missing protections: renewal caps, M&A clauses, dual-use rights, growth pricing, and Digital Access coverage. See our SAP Licence Agreement guide for key terms.
Engage Independent Advisory
SAP negotiations are complex and high-stakes. An independent licensing advisor who has seen hundreds of SAP deals can identify savings opportunities, benchmark your pricing, and strengthen your negotiation position.
🔎 Need Independent SAP S/4HANA Licensing Advisory?
Redress Compliance provides vendor-independent SAP licence assessments, RISE advisory, Digital Access evaluations, contract negotiation support, and audit defense. We help Fortune 500 organisations navigate the S/4HANA transition with clear-eyed cost analysis and proven negotiation strategies.
SAP License Optimisation | Contract Negotiation Service | Audit Defense | RISE Advisory
11. Frequently Asked Questions
Perpetual licensing is a one-time CapEx purchase. You own the licence indefinitely and pay ~22% annual support. RISE with SAP is a subscription (OpEx) that bundles S/4HANA software, HANA database, infrastructure hosting, and support into a recurring fee. RISE requires surrendering perpetual rights and typically has 3–5 year minimum terms. Perpetual is better for long-term stability; RISE for speed and simplicity, but always run a full TCO comparison.
FUE is SAP's unified licensing metric for S/4HANA Cloud and RISE. 1 Advanced user = 1 FUE, 5 Core users = 1 FUE, 30 Self-Service users = 1 FUE. You buy a pool of FUEs and allocate them across user types as needed. The flexibility is valuable but requires careful planning. Read more about FUE licensing.
Digital Access is SAP's formal approach to licensing indirect/external system usage. It charges based on 9 document types created in SAP by non-SAP systems. Without it, SAP could claim every external user touching your system needs a named user licence, creating massive compliance exposure. Read about the DAAP program.
Generally, no. SAP subscription contracts commit you to a minimum FUE count for the entire term. If your workforce shrinks, you pay for unused capacity until renewal. This is why right-sizing from the start is critical. See our termination and downsize rights guide.
SAP's fiscal year ends in December. Q4 (October–December) is the optimal window for negotiation, as sales teams face intense pressure to close deals. They will offer better discounts. Avoid Q1 if possible. Also time negotiations around your own contract renewals and the ECC 2027 support deadline.
Yes. S/4HANA runs exclusively on SAP HANA. For on-premises deployments, you need a separate HANA database licence (Runtime at ~15% of S/4HANA licence value, or Full-Use at higher cost). For RISE/cloud subscriptions, HANA is included. See our HANA licensing calculator.
For on-premises S/4HANA, SAP may offer a conversion path allowing you to apply existing ECC licence value toward S/4HANA licences. For RISE, SAP typically requires you to retire existing perpetual licences in exchange for subscription credits. In both cases, negotiate hard on the conversion ratio. Read: ECC to S/4HANA Conversion Strategies.
SAP audits by running scripts against your system to extract user transaction data, compare user classifications to actual usage, and identify interfaces creating documents. Common findings include user misclassification and undeclared Digital Access documents. SAP has become more assertive as the 2027 ECC deadline approaches. Prepare with our SAP Audit Preparation Toolkit.
Third-party ECC support (from Rimini Street or Spinnaker Support) can reduce annual maintenance by ~50% and extend the life of your ECC investment without forcing a migration. This is a legitimate strategy for stable ECC environments. Use it as a bridge while planning migration, and as negotiation leverage with SAP. See switching to third-party support.
No large enterprise pays list price. Typical discounts range from 30% for smaller deals to 50–70% for large enterprise agreements. Digital Access often carries even steeper discounts (DAAP offered up to 90% off). The exact discount depends on deal size, competitive pressure, timing, and negotiation skill. See our SAP pricing benchmarks.
📚 Related Reading
CIO Playbook: S/4HANA Deployment Models → RISE: Contract & Licensing Challenges → RISE vs. On-Premise Licensing → FUE Licensing: Classifications & Optimisation → S/4HANA Licensing Types Explained → HANA Database: Runtime vs. Full Use → S/4HANA: Models, Costs & Strategy → Modelling Costs After ECC Migration → ECC to S/4HANA Conversion Strategies → Negotiating with SAP: CIO Playbook → SAP Contract Negotiation Playbook → Digital Access Adoption Program (DAAP) → 3 Major SAP Licensing Models → S/4HANA & HANA Licensing Guide → S/4HANA Optimisation Strategies → New S/4HANA Embedded Features → RISE vs. Traditional Licensing → RISE Negotiations Guide → CIO Playbook for SAP License Types → SAP ECC & S/4HANA License Agreements →Our SAP Advisory Services
Vendor-independent. Fixed-fee. Proven results across hundreds of enterprise engagements.