Complete Licensing Guide for SAP ERP Private Cloud and RISE with SAP

Introduction: What Changed When SAP Rebranded RISE

In early 2025, SAP made a deliberate, strategic rename. RISE with SAP—the cloud offering that had dominated enterprise infrastructure conversations since 2021—became SAP Cloud ERP, Private Edition. The nomenclature shift signals SAP's intent: Private Edition is not merely a repackaging of cloud services, but a direct competitor to on-premise solutions and a clear alternative to public cloud deployments.

This guide addresses what that rebranding means for your licensing exposure, commercial terms, and total cost of ownership. Whether you are evaluating RISE for the first time, mid-contract review, or preparing for renewal, the fundamentals of the offer have not changed—but the clarity with which you can evaluate those fundamentals must.

SAP's commercial advisory specialists continue to present RISE (now Private Edition) as a fixed, bundled subscription. That narrative obscures a critical reality: the bundled components are modular, pricing is consumption-based in multiple dimensions, and the largest cost drivers—BTP credits for extensions, AI premium features, and infrastructure overages—operate outside the core subscription scope. Understanding these mechanics is not optional. It is the precondition for cost control.

The Five Core Components of SAP Cloud ERP Private Edition

SAP Cloud ERP Private Edition is sold as a single subscription. In practice, it comprises five distinct components, each with separate cost drivers and negotiation leverage points:

1. S/4HANA Enterprise License

The core software licence is perpetual intellectual property; you pay annually for the right to use S/4HANA on a named-user or concurrent-user basis. Under RISE, this is typically priced on a Full User Equivalent (FUE) model, which we address in detail in the next section. The licence itself—unbundled—would cost approximately £1.2–£1.8 million annually for a mid-market deployment. Under RISE, that cost is absorbed into the broader subscription.

2. Private Cloud Infrastructure

SAP provisions dedicated, single-tenant infrastructure on one of three hyperscalers: Amazon Web Services (AWS), Microsoft Azure, or Google Cloud Platform (GCP). You do not own the infrastructure; you lease it monthly. SAP does not disclose the underlying hyperscaler rates, nor does it publish the margin it applies. Industry analysis suggests SAP's markup is between 25–60% above direct cloud rates—a material cost lever that SAP's own pricing tools obscure.

3. Managed Services (Operating System, Database, Middleware)

SAP manages the HANA database, the operating system, backup, disaster recovery, and OS/database patching. You do not staff these functions; SAP does. This is a genuine operational cost savings compared to on-premise, where database teams are typically permanent headcount. The SLA is 99.7% production availability; 95% for development; and 99.9% for disaster recovery.

4. Business Technology Platform (BTP) Starter Credits

RISE includes an allocation of BTP credits at contract inception: typically between 4,000–16,000 credits per deal, depending on negotiated bundle size. These credits are intended for starter or proof-of-concept scenarios, not operational production workloads. As we explore in detail later, this allocation is a critical source of post-signature cost surprise.

5. Migration Support Services

SAP includes migration support: typically 150–250 days of professional services to move your ECC instance to S/4HANA on Private Edition. The value is significant, but the allocation is fixed; overspends require separate statement of work (SOW) contracts. Migration support is also available as a credit: up to 50% cost reduction off the infrastructure and licence components if you consume credits instead of cash. This discount decreases approximately 10% per year, making early migration financially favorable.

Licence Metrics: FUE Model, User Types, and Minimum Commitments

The FUE (Full User Equivalent) model is SAP's attempt to simplify enterprise licensing. In practice, it is a compression algorithm that obscures actual user counts and makes year-on-year cost predictability difficult.

User Type Classifications

Each user in your S/4HANA instance is classified into one of three categories, each assigned a FUE coefficient:

If your organisation has 800 Professional Users, 120 Limited Professional Users (at 0.5 FUE), and 900 Employee users (at 0.25 FUE), your total FUE is 1,000. SAP will price the licence on a 1,000-FUE basis, not on a raw headcount basis. This is a cost compression mechanism—but only if your user taxonomy is well-documented and defensible during annual true-up reviews.

Minimum Commitment

RISE Private Edition requires a minimum of 25 FUE for any contract. This is a de facto £0.5–0.8 million annual floor, depending on the region and discount applied. Smaller implementations or proof-of-concept scenarios that do not meet the 25-FUE threshold require separate licensing terms or are simply not available under RISE.

Growth and Overage Mechanics

Your initial contract locks FUE count for the first 12 months. After that, if you add users, SAP will true-up your licensing at anniversary. The true-up is typically at the original contract price, not the then-current market price. However, if you exceed the initial FUE by more than 10% at true-up, SAP may require a renegotiation or may apply the then-current rate. This mechanism creates a commercial incentive to either understate FUE at signature or to carefully manage user additions during the contract term.

Infrastructure: What Is Included and What SAP Does Not Disclose

SAP's marketing emphasises infrastructure simplicity: "Let us manage your cloud. Pay one price." The reality is more complex.

What Is Included

The RISE subscription covers the hyperscaler infrastructure (compute, storage, network), SAP's management layer, backup and disaster recovery, and regional redundancy. For most organisations, this is sufficient. You do not need dedicated database administrators; you do not need to negotiate cloud contracts directly; you do not bear the risk of capacity underprovisioning.

What SAP Does Not Disclose

SAP does not publish the underlying hourly rates it pays to AWS, Azure, or GCP. It does not disclose the margin it applies over those rates. It does not publish the infrastructure cost component separately, making it impossible to benchmark or to model cost escalation independently. This opacity is intentional: it preserves SAP's pricing power and prevents customers from using competitive cloud pricing as a negotiation anchor.

The practical implication: if AWS infrastructure costs increase (e.g., due to global energy prices or GCP competitive discounting), you have no visibility into whether SAP passes those increases to you directly or absorbs them. Your cost escalation is entirely within SAP's control.

Regional Pricing Variance

Infrastructure costs are region-dependent. EMEA (Europe, Middle East, Africa) is typically 15–25% more expensive than North America. APAC is regional: Australia and New Zealand are premium; India and Southeast Asia are discounted. SAP's pricing models often apply a single EMEA rate regardless of country, creating cross-subsidies. A German multinational may see higher-than-necessary costs if applications are consolidated in a single geographic region, while a US company may see artificially low regional costs if applications are distributed.

BTP Credits: The Starter Allocation vs. Operational Reality

This section is critical. It represents the largest post-signature cost surprise in RISE contracts.

The Marketing Narrative

SAP markets BTP credits as "included." The narrative: you get a allocation of credits; you can use them for extensions, integrations, or AI services; any overage is billed separately. Simple. Transparent.

The Operational Reality

The allocation—typically 4,000–16,000 credits per deal—is sized for demonstration, proof-of-concept, or intermittent usage. It is not sized for production operations. A Clean Core migration strategy (discussed in detail later) requires BTP extensions to replace customisations. A single extension that runs continuously will consume 500–2,000 credits per month. AI and analytics workloads consume 1,000–5,000 credits per month. Integration scenarios for multiple legacy systems will consume 2,000–4,000 credits per month.

Therefore: an organisation with a genuine digital transformation programme will exhaust the bundled allocation within 2–6 months of production cutover and will begin incurring consumption-based overage charges. Those overages are billed monthly, outside the subscription, and are not subject to the same discount structure as the core licence.

A Real Client Pattern

A UK financial services company signed a 5-year RISE contract with a total contract value of £3.2 million. The business case included cost-benefit analysis across multiple scenarios. The scenario models showed positive net present value (NPV), assuming modest utilisation of extensions and moderate AI adoption. The company's procurement team negotiated 30% discount off list price and believed they had secured excellent terms.

Eighteen months into the contract, after their Clean Core extension programme was live (consuming 2,400 credits per month) and their internal teams had adopted SAP Joule for financial forecasting (consuming 1,200 credits per month), annual BTP overage costs reached £180,000. This cost was not in any version of the business case presented during the sales cycle. Worse, the overage billing is outside the scope of the original discount and is now negotiated at full list rates.

This pattern is not unique. It is systemic.

The Pricing Model

BTP credits are not published with transparent unit economics. SAP's rate card shows bundles (e.g., "10,000 credits = £45,000"), but does not disclose the cost per credit or how consumption is calculated. This opacity is maintained deliberately: if customers could calculate backwards from their extension and integration requirements to the credit cost, they would model BTP as a separate consumption-based cost and would negotiate differently.

SAP Joule AI Under RISE: What Is Included and What Costs Extra

SAP Joule is the company's co-pilot for enterprise software. Base Joule skills are included in S/4HANA and in the RISE subscription: summary generation, data retrieval, simple process automation. Premium skills—advanced forecasting, generative content creation, scenario modelling—consume BTP credits.

Base Skills (Included)

Summarisation of documents, data tables, and reports; data retrieval from S/4HANA tables; natural language query interface; process recommendations based on transaction history.

Premium Skills (BTP Consumption)

Financial and demand forecasting; generative document creation (contracts, RFQs); advanced scenario analysis; custom skill development; integration with third-party AI services.

The cost differential is material. A financial planning team that uses base Joule for summarisation bears no additional cost. A finance team that uses Joule for multiple monthly forecasting scenarios (demand, cash flow, headcount planning) will consume 500–1,500 credits per month—adding approximately £2,500–£7,500 monthly to the BTP bill.

Governance and Overages

Most organisations do not establish consumption budgets for BTP or SAP Joule. Users adopt the tool, consumption accelerates, and the bill surprises finance at invoice review. SAP provides consumption dashboards, but visibility is typically not integrated into procurement or IT governance. Best-practice organisations establish monthly BTP budgets, set alerts at 70% and 90% of allocation, and require approval for new premium Joule scenarios.

Clean Core and the Extension Cost Trap

Clean Core is SAP's strategy for simplified, future-proof S/4HANA deployments. The philosophy: minimise customisations in S/4HANA itself; move all customisations, extensions, and integrations to BTP side-by-side applications. The benefits are real—reduced upgrade risk, faster innovation, cleaner data models. The cost implication is straightforward but often not acknowledged in the business case: every customisation you move to BTP becomes a new recurring consumption cost.

The Commercial Mechanics

If your ECC instance had 80 ABAP customisations, your Clean Core migration will likely move 60–70 of those to BTP extensions. Each extension must run somewhere: on BTP compute, at BTP prices. Those costs are consumption-based, scale with usage, and are not subject to multi-year contract discounts. SAP's Clean Core tools and consulting services help you identify and migrate these customisations. The benefit—simpler S/4HANA—is genuine. The cost transfer—from perpetual licencing to subscription consumption—is the mechanism.

Migration Path Economics

An extension that would cost £80k–£150k to build and maintain in-house over five years as an ABAP customisation will cost £30k–£60k annually on BTP. The net cost is reasonable if you have genuine operational benefit (faster deployment, easier maintenance, access to pre-built components). But this calculation is not always transparent in the business case. Many organisations find themselves in Clean Core migrations where the original cost estimates did not account for post-go-live extension and maintenance costs.

Migration Credits: The Decreasing Incentive You Must Model Now

SAP offers migration credits as an incentive to move from ECC to S/4HANA. The offer is time-limited and declining.

Current Offer (2025–2026)

Up to 50% of the infrastructure and licence costs can be covered by migration credits if you consume them within the first 12–24 months post-signature. This is equivalent to a 25% discount on the core RISE subscription—a material incentive.

Declining Schedule

The migration credit offer decreases approximately 10% per calendar year. By 2027, the available credit will be 40–45% of current levels. By 2030, it will approach zero. This declining schedule is SAP's commercial lever to accelerate migration decisions. Organisations delaying migration into 2027 or 2028 will face meaningfully lower credits and, as a result, higher net ECC-to-S/4HANA transition costs.

Financial Modelling

If you are evaluating migration timing, the credit schedule is a material factor. A one-year delay in migration could cost an additional £200k–£400k in foregone credits for a mid-market deployment. Conversely, accelerating migration to capture maximum credits requires earlier organisational readiness (data cleansing, technical preparation, resource availability). The intersection of credit availability and migration readiness is where negotiation should focus.

The SAP ERP Private Edition Transition Option: Who Qualifies and What It Offers

In Q1 2025, SAP introduced the ERP Private Edition Transition Option for select large enterprise customers. This is a new contract instrument, not broadly marketed, and qualifies only for specific customer segments.

Eligibility

Large enterprises (typically £5 million+ annual ECC licence spend); existing 5-year S/4HANA commitments; or organisations with extended maintenance contracts on EHP 6–8. SAP's sales teams have explicit authority to offer this option, but it is not automatic and requires direct negotiation.

What It Offers

An extension of ECC licence support to December 31, 2033—seven years beyond the current mainstream maintenance end date of December 31, 2027. In exchange, customers commit to S/4HANA migration by 2030 and accept a 20% pricing uplift on any RISE or S/4HANA commitments made from 2026 onwards.

The Trade-Off

For a large enterprise, this option provides runway: migrate to S/4HANA at a slower pace, avoid the 2027 cliff, and defer capital expenditure. The cost is a 20% premium on all RISE and S/4HANA new or renewed contracts through 2030. For some organisations—those with genuinely complex migrations, limited internal resources, or significant ECC customisation—this trade-off is rational. For others, it is a costly hedge against a problem that better project management could solve.

Window and Terms

The Transition Option is available for purchase through 2028. After 2028, the option expires and extended maintenance (2028–2030) becomes the only path forward, at a premium of +2% annually (approximately 24% over the three-year period). This is why the Transition Option window is material: it caps cost escalation at 20% through 2030, rather than allowing escalation through extended maintenance.

SLAs, Contract Terms, and Lock-In Mechanics

Service Level Agreements (SLAs)

RISE contracts include SLAs for uptime and performance. The structure is:

• Production environment: 99.7% availability. This translates to approximately 8 hours of planned or unplanned downtime per year.
• Development and quality assurance environments: 95% availability (36 hours per year).
• Disaster recovery: 99.9% target (9 hours per year).

These SLAs are industry-standard for enterprise cloud platforms. They are also business-critical: any production outage cascades through finance, procurement, and operations. SAP provides service credits (typically 10–25% of monthly fees) if availability falls below the SLA. However, credits are often capped (e.g., maximum 12 months of credits per incident) and are applied as subscription offsets, not cash refunds. Organisations relying on RISE for mission-critical processes should negotiate SLA penalties with cash refund provisions, not credit offsets.

Contract Terms and Escalation

RISE contracts are typically five years, with full-term lock-in. Year-on-year price escalation is typically 3–4%, compounded. Total contract value (TCV) over five years for a mid-market deployment (500 FUE, £1.2 million Year 1 licence cost) is approximately £6.5–£7.2 million, assuming standard escalation.

Renewal terms favour SAP. At the end of Year 5, you have three options: renew at then-current SAP rates (typically 10–15% above your Year 5 rate); request a transition to perpetual licensing (no longer available for new S/4HANA customers); or consider alternative platforms (a lengthy, costly process). This lock-in is structural and intentional. It reflects SAP's commercial strategy: maximise customer commitment at signature; manage renewal leverage at anniversary.

Termination and Exit Costs

Early termination of a RISE contract—before the five-year term expires—incurs penalties equal to 50–100% of remaining contract value, depending on the contract year. This is a significant exit barrier. Organisations that experience technology failures, regulatory changes, or organisational restructuring during the contract term often find exit costs prohibitive and are forced to continue the contract despite changed circumstances.

Benchmarking Discounts: What Good Looks Like

SAP's published list prices are approximately £2.2–£3.0 million annually for a mid-market RISE deployment (500 FUE, including licence, infrastructure, and managed services). However, virtually no organisation pays list price.

Discount Landscape

Median discounts from list price are approximately 45%. Well-negotiated deals (with competitive leverage, multi-year commitment, and skilled procurement) achieve 55% discounts. Top-quartile deals—negotiated by organisations with genuine alternatives or during SAP's fiscal Q4 (July–September)—achieve 60% discounts. Beyond 60%, SAP becomes reluctant; the deal economics become loss-leading and require director-level commercial approval.

Discount Mechanics

Discounts are applied as percentage reductions from list price. A 55% discount on a £2.5 million list price yields a Year 1 cost of £1.125 million. However, discounts are often applied to Year 1 only, with escalation clauses applying to Years 2–5 from the discounted baseline. A contract that states "55% discount + 4% annual escalation" costs less over five years than one with "40% discount + 4% annual escalation from list," even though the discount percentage is nominally lower.

Discount Levers

SAP's sales teams have discount authority in the following order:

1. Multi-year commitment: Five-year deals receive larger discounts than three-year deals.
2. Competitive pressure: Organisations evaluating alternative platforms (Oracle, Infor, Workday) receive higher discounts. This is SAP's "save deal" dynamic.
3. Fiscal timing: SAP's fiscal year ends September 30. Q4 (July–September) is the period of maximum discount authority, as sales teams pursue annual quota.
4. Customer size: Enterprise accounts (£500m+ revenue; global operations) receive larger discounts than mid-market.
5. Existing SAP footprint: Organisations with large existing SAP investments (multiple instances, SuccessFactors, Ariba, etc.) receive higher discounts than net-new customers.

Negotiation Framework and Timing Strategy

Pre-Negotiation Positioning

Begin negotiations with a clear understanding of your BATNA (best alternative to negotiated agreement). This is typically: continue with ECC and extended maintenance; migrate to an alternative platform; or delay migration. SAP's negotiators will attempt to collapse this optionality and present RISE as the inevitable path. Your leverage is directly proportional to how credible your alternatives are.

Document your data. Prepare a detailed user taxonomy (Professional, Limited Professional, Employee counts by department). This removes ambiguity and prevents SAP from later asserting higher FUE counts during true-up. Model infrastructure usage independently: database size, transaction volume, integration frequency. SAP's pre-configured infrastructure sizing tools will typically over-provision; independent modelling will identify right-sizing opportunities.

Commercial Negotiation Sequence

1. Year 1 Discount: Begin by establishing the Year 1 all-in price. Focus on total cost, not line-item discount percentages. A £1.2 million Year 1 cost (40% off list) is a clear negotiating anchor.
2. Year 2–5 Escalation: Establish escalation rates. Standard SAP escalation is 3–4% annually. Negotiate for 2–2.5% if your procurement leverage is strong, or for a fixed total cost with internal allocation across years. Fixed-price five-year contracts are rare but possible for highly competitive situations.
3. BTP Credit Allocation: Negotiate for the maximum credit allocation (16,000 credits) and, if possible, secure a commitment that overconsumption in Year 1–2 is covered by credits rather than cash. This funds early extension and integration work without immediate overages.
4. Migration Support and Credits: Confirm the migration support allocation (days) and secure maximum migration credits (50% of infrastructure and licence) for the first 24 months post-signature. Confirm the credit schedule decline and, if possible, negotiate for an extended availability window.
5. Infrastructure Overages: Establish the cost structure for infrastructure overages (e.g., cost per additional gigabyte of storage, per additional CPU, per additional network transfer). Get this in writing; rely on verbal assurances from SAP's sales teams at your own risk.
6. SLA Credits and Remedies: Ensure SLA credits are cash refunds, not subscription offsets. Negotiate for penalty escalation if SLA breaches occur consecutively (e.g., if two incidents occur within 12 months, the penalty increases).

Timing Strategy

If your fiscal calendar permits, initiate negotiations in June or early July. This places you in SAP's Q4 (their fiscal quarter running July–September), when discount authority is highest. Close the deal before September 30 if possible; SAP's financial reporting year cycles on October 1, and you will typically have more leverage before year-end close than after.

Avoid negotiating during January–March. This is SAP's fiscal Q2, when sales teams are rebuilding quota; discount authority is typically lower. May–June (Q3) is moderately advantageous; at that point, teams are ahead of or behind quota and are motivated to move deals.

Conclusion

RISE with SAP—now SAP Cloud ERP, Private Edition—can deliver genuine value: operational simplification, reduced infrastructure management burden, faster innovation cycles via BTP extensions and SAP Joule. But only when buyers understand exactly what is included, model total cost of ownership independently of SAP's pre-configured calculators, and negotiate from a position of understanding rather than accepting the packaged narrative.

The five core components have distinct cost drivers. FUE models compress user counts but require rigorous true-up governance. Infrastructure costs are opaque; that opacity is deliberate. BTP credits are not "free"; they are starter allocations that will exhaust under any genuine digital transformation programme. Clean Core strategies transfer customisation costs from perpetual to consumption-based models. Migration credits are declining and time-limited. Contract lock-in is structural.

Organisations that treat RISE as a simple "cloud ERP" subscription and that budget accordingly will face systematic cost surprises: BTP overages, infrastructure scaling costs, higher-than-modelled discount escalation at renewal. Organisations that deconstruct the offer into its five components, model each cost driver independently, and negotiate with full transparency of consumption patterns will establish sustainable, predictable cost positions and will retain optionality for future technology choices.

The rebranding from RISE to Private Edition does not change the fundamental mechanics. It clarifies SAP's positioning: Private Edition is a premium, fully-managed offering for large enterprises that value operational simplification and are willing to accept lock-in and consumption-based cost growth in exchange. That trade-off is defensible. But it must be a conscious choice, not a result of incomplete information or compressed negotiation cycles.