Key Takeaways

What Every Enterprise Buyer Must Know About RISE with SAP Contracts

  • RISE with SAP bundles S/4HANA Private Cloud, Business Technology Platform (BTP), SAP Enterprise Support, and infrastructure into a single Order Form — but each component carries its own pricing logic and renewal risk.
  • The RISE contract structure is designed to make unbundling difficult; SAP's "clean core" requirements and mandatory BTP minimum commitments create exit barriers that compound over time.
  • Most enterprises overpay 20–40% on their initial RISE proposal because SAP prices RISE assuming you won't benchmark or negotiate.
  • Key negotiation levers include: BTP credit sizing, annual escalation caps, exit provisions, SLA penalties, and infrastructure substitution rights.
  • Independent review of the RISE contract structure before signature can save $5–25M over a 5-year term for a mid-to-large enterprise.

RISE with SAP is SAP's flagship subscription offering, launched in 2021. It packages S/4HANA Cloud Private Edition, SAP Business Technology Platform (BTP), SAP Enterprise Support, and cloud infrastructure into what SAP calls "Business Transformation as a Service." The proposition is compelling — and deliberately so. One contract, one invoice, one relationship. What SAP's sales presentation omits is the contractual architecture underneath that proposition, which is engineered to maximise SAP's revenue over the contract term.

Our RISE with SAP advisory team has reviewed over 80 RISE proposals and negotiated contracts for enterprises across manufacturing, financial services, healthcare, and energy. The pattern is consistent: SAP's initial proposals include pricing that assumes you won't push back, terms that assume you don't understand what you're signing, and commitments that assume you'll accept SAP's unilateral right to modify components.

This guide breaks down the RISE with SAP contract structure in full — the components, the commercial logic, the hidden risk clauses, and the negotiation leverage you have before the contract is executed. If you are evaluating, renewing, or renegotiating a RISE engagement, read this before you take SAP's next call.

RISE with SAP Contract Series

Complete Guide: RISE with SAP Contract Structure

Pillar RISE Contract Structure: Complete Guide ← You Are Here Part 1 Key Clauses to Negotiate in Your RISE Contract Part 2 RISE Add-On Agreements: Hidden Costs Exposed Part 3 RISE with SAP Pricing Model Breakdown Part 4 RISE vs Hyperscaler Direct: True Cost Comparison

The RISE with SAP Contract Architecture: What You Are Actually Signing

A RISE with SAP contract is not a single agreement. It is a layered structure comprising several interdependent documents that collectively define your commercial obligations. Understanding each layer is essential — because SAP's sales team presents it as one unified deal, but the T&Cs governing each component can be amended, repriced, and restructured independently.

The core components of the RISE with SAP contract structure typically include:

1. The Master Agreement

Your existing SAP Master Agreement (or a new Master Agreement if you are signing RISE as a new customer) governs the overall commercial relationship. For existing SAP customers, this is often the ELA (Enterprise License Agreement) or general SAP Customer Agreement. The Master Agreement defines dispute resolution, liability caps, intellectual property terms, and governing law. SAP's standard Master Agreement is heavily weighted toward SAP — and most customers accept it unchanged. This is the first major negotiating error.

⚠ Critical Negotiation Point

SAP's standard liability cap in the Master Agreement is typically limited to the fees paid in the 12 months prior to the claim. For a multi-million-pound RISE contract, this cap can be grossly inadequate. Negotiating a higher liability cap — particularly for data breaches, service availability failures, and migration delays — is non-negotiable for large enterprises.

2. The Order Form

The Order Form is where the commercial deal is captured: the specific RISE components you are purchasing, the subscription term, the annual fees, the growth rates, and the payment schedule. SAP's standard Order Form is engineered to maximise inflexibility. It will specify a commitment period (typically 5 years, sometimes 7 or 10), annual price escalators tied to indices you may not control, and minimum consumption commitments — particularly for BTP.

Most enterprises focus their attention on the headline fee. The Order Form's real risks are in the escalation mechanics, the measurement periods for usage overage, and the change control provisions that govern what happens when you want to modify scope. Our guide to key RISE contract clauses to negotiate covers the Order Form in detail.

3. The Supplemental Terms: S/4HANA Cloud Private Edition

RISE includes S/4HANA Cloud Private Edition (S/4HANA CPE) — which is S/4HANA deployed on SAP-managed infrastructure, hosted on your hyperscaler of choice (AWS, Azure, or Google Cloud). The supplemental terms for S/4HANA CPE define the service scope, the SLA commitments, the managed services responsibilities, and — critically — what SAP's obligations are during the migration itself.

SAP's supplemental terms for managed services are carefully worded to limit SAP's liability for migration delays, data integrity issues, and scope creep. The language around "joint responsibility" in the migration workstream is a particular area where enterprises have been exposed. When a go-live is delayed by 6 months, the supplemental terms will typically determine who bears the cost.

4. The BTP (Business Technology Platform) Commitment

Every RISE contract includes a BTP credit bundle. SAP bundles BTP credits into RISE as both an incentive and a lock-in mechanism. The incentive is genuine — BTP enables integration, extension, and automation. The lock-in is the commercial structure: minimum BTP consumption commitments that escalate annually, regardless of whether you are actually using the credits.

In practice, 70% of enterprises do not fully consume their included BTP credits in the first two years of a RISE contract. Yet the credits carry cash value, and SAP's standard terms do not allow unused credits to roll over or be redeemed. This is pure SAP revenue — you pay for credits that expire unused. Our analysis of RISE add-on hidden costs breaks down how BTP credit waste compounds over a five-year term.

5. Enterprise Support Schedule

SAP Enterprise Support is mandatory in RISE and is calculated at 22% of the Net Licence Value (NLV) — the same pricing model as on-premise, applied to your cloud subscription. Many enterprises are shocked to discover that the "support" bundled into RISE is not a flat infrastructure management fee; it includes a support component priced on the licence value of the underlying software. As your RISE footprint grows, your support cost grows in lockstep.

This is by design. SAP's Enterprise Support pricing model ensures that every incremental user, module, or add-on you add to your RISE estate carries an automatic 22% support premium. Our team regularly achieves SAP support cost reductions through alternative support frameworks — though RISE contracts require careful structuring to preserve this right.

22% SAP Enterprise Support cost as % of net licence value in RISE
20–40% Typical enterprise overpayment on initial RISE proposals without independent review
70% Enterprises that don't fully consume their included BTP credits in years 1–2
5–10yr Typical RISE commitment term; exit clauses are limited and costly

How SAP Prices RISE: The Commercial Logic You Must Understand

The RISE with SAP pricing model is constructed to obscure the true per-unit cost of what you are buying. SAP bundles components at a "package" price, applies volume-based discounts to the headline number, and uses anchor pricing — the list price — to make the discount appear generous. In reality, the discount is from a price that no sophisticated buyer pays.

SAP's RISE pricing is structured around three primary elements:

Per-User Subscription Fees

S/4HANA Cloud Private Edition is priced on a Named User basis. User types mirror the on-premise model — Professional Users, Limited Professional Users, Employee Users, and so on. The critical difference is that cloud subscriptions create a "minimum user floor" — you cannot reduce your user count below the contracted minimum, regardless of actual usage. SAP's sales teams typically push for higher user commitments upfront, knowing that the minimum floor will sustain revenue through the term even if your headcount falls.

Infrastructure and Hosting Fees

RISE includes cloud infrastructure managed by SAP on one of the major hyperscalers (AWS, Azure, GCP). The infrastructure component is priced by SAP — you do not directly purchase cloud capacity from the hyperscaler. This means you cannot benchmark SAP's infrastructure pricing against public cloud rates, and you cannot benefit from your own hyperscaler agreements. Many enterprises that already have significant AWS or Azure committed spend lose the opportunity to apply that spend to their RISE workloads.

Our analysis shows that in a straight cost comparison, SAP's RISE infrastructure pricing typically runs 15–35% above what enterprises could achieve by running S/4HANA workloads directly on a hyperscaler. The RISE vs hyperscaler direct cost comparison walks through a detailed example.

BTP and Add-On Consumption Fees

Beyond the base RISE bundle, SAP structures additional revenue through BTP overage charges (when you exceed your included credits), add-on modules (SAP Ariba, Concur, SuccessFactors, Fieldglass), and integration services. These add-on agreements are covered by separate Order Forms but are commercially linked to the RISE Master Agreement — and SAP uses the interdependency to limit your negotiating leverage on each component individually.

🔴 High Risk: SAP's Unilateral Modification Rights

SAP's standard RISE terms include provisions allowing SAP to modify the service scope, component definitions, and technology stack with notice periods as short as 90 days. This means that services you contracted for — including specific BTP services, integration tools, or managed service tiers — can be modified or discontinued without your consent. Negotiating explicit protection clauses against unilateral scope changes is essential.

The Lock-In Mechanisms SAP Builds Into Every RISE Contract

RISE with SAP is a strategically designed lock-in. This is not a criticism — it is an accurate description of the commercial architecture. Understanding the lock-in mechanisms allows you to negotiate protections and, where possible, preserve optionality. Ignoring them results in contracts where exit is effectively impossible without significant financial penalty.

Clean Core Requirements

SAP promotes "clean core" as a best-practice methodology for S/4HANA migrations — minimising custom code and building extensions on BTP rather than in-system. The clean core approach has genuine technical merit. The commercial implication is that it drives dependency on BTP for customisations that would otherwise live in your on-premise estate. Every BTP-based extension you build deepens your dependence on SAP's platform — and makes switching to a competitor, or moving to a hyperscaler-hosted S/4HANA, progressively more difficult.

Data Portability and Exit Provisions

SAP's standard RISE terms give you the right to export your data at contract end. What they do not typically provide is: a guaranteed format for data export that is compatible with non-SAP systems, SAP-assisted migration support to a competitor platform, or meaningful notice periods that allow you to plan an exit before renewal dates. Negotiating explicit data portability provisions — including format specifications, export timelines, and assisted migration clauses — is critical for any enterprise that values commercial flexibility.

Renewal Mechanics and Evergreen Traps

Many RISE contracts include auto-renewal provisions with minimum notice periods (often 12 months) to prevent renewal. Missing the notice window locks you into another full subscription term. SAP's commercial teams are structured to maximise the probability that you miss the window — and the contract terms support this by making the notice period difficult to identify without careful legal review. We recommend building a formal SAP contract renewal programme with independent review at least 18 months before each renewal date. Our SAP contract negotiation service includes proactive renewal management for exactly this reason.

Is Your RISE Contract Structured to Protect You?

Our independent advisors have reviewed 80+ RISE proposals. We identify overpriced components, unfair terms, and missing protections before you sign.

Book a Free RISE Review

Negotiation Leverage in a RISE Contract: What Actually Works

The common belief is that RISE is a take-it-or-leave-it offer. It is not. SAP has significant commercial pressure to close RISE deals — it is the primary vehicle for driving on-premise customers to the cloud and for generating recurring subscription revenue. This pressure creates real negotiating leverage if you know where to apply it.

Competitive Tension

SAP's largest source of concern is a genuine evaluation of the alternative: running S/4HANA on hyperscaler-managed infrastructure directly, or evaluating Oracle, Microsoft, or another ERP vendor. Even if you have no real intention of switching, a credible competitive evaluation extends your negotiating window and drives meaningful discount. SAP's commercial teams are instructed to win RISE deals, not to lose to hyperscaler-direct alternatives. This creates leverage — but only if you demonstrate you've done the work. Our RISE vs hyperscaler cost analysis gives you the data to make this case credibly.

BTP Credit Rightsizing

SAP's standard RISE proposals include BTP credits that are sized to maximise SAP's revenue from overage charges and future upsells, not to reflect your actual consumption. Challenging the BTP credit bundle — with a bottoms-up consumption model based on your actual integration and extension requirements — is one of the highest-value negotiation moves available. Reductions of 20–40% on BTP commitments are achievable with evidence-based counterproposals. Our dedicated series covers this in depth: see the RISE with SAP BTP credits complete guide, BTP credit negotiation strategies, and cost optimisation tactics for a full framework.

Escalation Cap Negotiation

SAP's standard RISE contracts include annual price escalators tied to indices like CPI or a fixed percentage (typically 3–5%). Over a 7-year contract, a 5% annual escalator compounds to a 41% increase on the base subscription fee. Negotiating a hard cap on annual escalation — tied to a specific index with a maximum floor — is a commercially significant protection. Many enterprises accept SAP's standard escalator without challenge.

Infrastructure Substitution Rights

Negotiating the right to migrate RISE workloads to your own hyperscaler footprint — without penalty, given sufficient notice — is a powerful exit provision that SAP will resist but can be achieved. This provision does not mean you intend to exercise it; it means you preserve the commercial option. Its existence alone disciplines SAP's behaviour on future pricing and scope modifications.

Due Diligence Checklist Before Signing a RISE Contract

Based on our review of over 80 RISE contracts, these are the areas where enterprises consistently fail to conduct adequate due diligence before signature. Each represents a category of avoidable commercial exposure.

Pre-Signature Due Diligence

1. Component mapping: Have you mapped every component in the Order Form to a specific business requirement? Can you justify every BTP credit, every user licence, every module? SAP proposals routinely include components you don't need yet that create future minimum commitments.

2. SLA verification: Have you stress-tested SAP's SLA commitments against your actual business continuity requirements? Standard RISE SLAs offer 99.5% availability — but the credits for downtime are capped at percentages of monthly fees that are immaterial for genuine business disruption.

3. Migration obligations: Does the contract clearly assign responsibility for migration phases, including data migration, custom code remediation, testing, training, and go-live support? Is there a liquidated damages provision if SAP fails to meet migration milestones?

4. Exit mechanics: Can you leave at the end of the contract term without penalty? Is there a data portability commitment in a usable format? Is the notice period for non-renewal clearly documented?

5. Unilateral modification protection: Are there explicit limitations on SAP's right to modify service scope, pricing, or component definitions without your consent?

The Case Study: €18M Saved on a 7-Year RISE Contract

A global manufacturing group approached us 6 weeks before planned RISE contract signature. They had been in negotiation with SAP for four months and believed they had received a competitive proposal. Our analysis of the contract structure identified the following issues: BTP credit bundle oversized by 35% versus actual consumption modelling; no cap on annual price escalation (SAP's standard 4% applied throughout); infrastructure pricing 28% above equivalent AWS direct cost; SLA credits capped at 10% of monthly fees with a 15-minute downtime measurement threshold; no data portability provision for contract exit.

Over the course of a six-week renegotiation, our RISE advisory team secured: a 35% reduction on BTP commitments; a 2% annual escalation cap; a contractual right to migrate to self-managed infrastructure at the end of year 3 with 12 months' notice; and a data portability schedule with SAP-assisted migration included. Total contractual value reduction over the 7-year term: €18M. This is not an exceptional result — it is representative of what structured negotiation achieves when you understand the contract architecture. You can read more in our case studies section.

RISE with SAP in 2026: What's Changed and What Matters Now

SAP's commercial strategy for RISE has evolved significantly since the product launched. In 2026, several developments have material impact on the contract structure enterprises should negotiate.

First, SAP has made RISE with SAP the primary path for ECC customers facing the 2027 end-of-mainstream maintenance deadline. This creates genuine urgency for customers — and SAP's commercial team exploits that urgency by compressing negotiation timelines. Do not allow the 2027 deadline to be used as a reason to skip independent contract review. The right RISE contract structure, negotiated properly, is worth far more than the few months SAP's timeline pressure is designed to cost you.

Second, SAP has expanded the RISE bundle to include additional components — most notably SAP Signavio for process intelligence and additional SAP Build low-code tools. These additions have real value but also reset commitment levels, create new consumption obligations, and provide SAP with another pricing lever at renewal. Each new component added to your RISE bundle requires the same scrutiny as the original contract. For detailed guidance on navigating the migration from ECC, see our S/4HANA migration licensing service.

Third, SAP has introduced GROW with SAP as the cloud ERP offering for smaller enterprises and greenfield deployments. GROW uses S/4HANA Cloud Public Edition and has a fundamentally different contract structure from RISE — less negotiable on infrastructure, but more modular on applications. If your organisation is evaluating both RISE and GROW, the contract structure comparison is essential. For a comprehensive breakdown of SAP's overall licensing framework, the RISE with SAP Guide is the starting point.

Frequently Asked Questions: RISE with SAP Contract Structure

How long is a typical RISE with SAP contract term?
SAP's preferred RISE contract term is 5–7 years, with 10-year terms offered in exchange for larger discounts. Shorter terms (3 years) are possible but typically come with less favourable pricing. Our recommendation is to negotiate for the term that matches your cloud roadmap — and to ensure that exit and renewal provisions are clearly defined regardless of the term length.
Can I negotiate the infrastructure component of RISE separately?
SAP's preference is to bundle infrastructure within the RISE price, obscuring the infrastructure cost. It is possible to negotiate visibility into infrastructure pricing — and in some cases, to negotiate the right to substitute your own hyperscaler footprint. This requires specific contractual language and is most achievable when negotiated at contract inception, not at renewal.
What happens to my existing on-premise SAP licences when I move to RISE?
SAP offers a licence conversion mechanism — your existing on-premise licence value can be credited toward the RISE subscription fee. The conversion rate SAP proposes is almost always unfavourable. Independent analysis of the conversion economics, including the residual value of your existing licences and the true cost of the RISE subscription, is essential before agreeing to SAP's conversion terms.
What is the SAP RISE contract exit mechanism?
Standard RISE contracts provide for exit at the end of the contract term with a minimum notice period (typically 12 months). Mid-term exit is generally only possible with significant financial penalty. The key protections to negotiate are: clear data portability provisions; SAP-assisted migration support for exit; and a defined process for returning your intellectual property. Without these provisions, the commercial cost of switching post-signature is very high.
How much can I actually save by negotiating a RISE contract independently?
Based on our engagements, independent review and negotiation of a RISE contract for a mid-to-large enterprise typically achieves 15–35% reduction in total contract value over the subscription term. This includes pricing improvements, BTP rightsizing, escalation cap negotiation, and exit provision improvements. For a 5-year RISE contract with a total value of €20M, this represents €3–7M in achievable savings.
Is RISE with SAP right for every SAP customer?
Not necessarily. RISE with SAP is the right path for many organisations — but it is not universally optimal. Enterprises with existing hyperscaler commitments, complex integration landscapes, or specific data residency requirements should evaluate RISE carefully against alternatives including hyperscaler-hosted S/4HANA, third-party managed S/4HANA services, and, for some use cases, non-SAP ERP alternatives. Independent evaluation of the commercial and technical case is the only way to make this decision with confidence.

Related Reading

RISE with SAP SLA & RACI Series

Contract structure is the foundation — but SLA commitments and RACI accountability are what make or break delivery. The following guides cover what to demand and how to negotiate it:

Our Services

RISE with SAP Advisory

Independent RISE contract review, pricing analysis, and negotiation support — buyer-side only.

Explore RISE Advisory → Case Studies

Real RISE Contract Savings

See how we've helped enterprises save €5–25M on RISE contracts through independent negotiation.

Read Case Studies →

SAP Licensing Experts is an independent advisory firm. We are not affiliated with, endorsed by, or partnered with SAP SE or any SAP subsidiary. SAP, RISE with SAP, S/4HANA, BTP, and all SAP product names are trademarks of SAP SE. Our advice is 100% buyer-side.