RISE with SAP pricing: what is in the contract

RISE with SAP pricing is a quoted subscription, not a list price. The number SAP gives you is driven mainly by how many Full Use Equivalents (FUEs) you buy. System size, modules in scope and the length of the term do the rest.

Short answer: you pay one recurring fee that bundles the ERP software, the cloud infrastructure and SAP's technical operations. You do not get implementation, data migration or your partner's work, and most of the money you will regret is fixed in the first order form.

This article is a spoke of my ECC to S/4HANA migration guide. It covers the commercial side only. It is practical guidance from programme work, not legal advice, so have your contract counsel read the order form before anyone signs.

First, the names, because they changed. SAP now positions RISE with SAP as its route to the cloud for existing SAP customers, not as a single product. The ERP at its core is usually SAP Cloud ERP Private, which most people still search for as S/4HANA Cloud Private Edition.

SAP does not publish a RISE price on sap.com. You get a quote, and the quote is built on four things:

1. Full Use Equivalents. The usage metric for the ERP subscription.
2. System size. SAP ties the size of your production, quality and development systems to FUE tiers.
3. Modules and add-ons. Industry add-ons, extra cloud products and optional services such as disaster recovery.
4. Term. The length of the subscription and what happens when it renews.

FUEs do most of the work. SAP's service description guide for SAP Cloud ERP Private (version 4-2026, updated 20 April 2026) sets the ratios. One FUE covers one advanced user, five core users or 30 self-service users, and a developer counts as two FUEs.

The same guide adds two rules that matter commercially. You can move FUEs between use types during the term, but one FUE cannot be split across use types. The FUE entitlement in your order form is retained for the whole subscription term, so plan as if you cannot shrink it once signed.

This is where most budgets go wrong. People assume "SAP runs it" means SAP does everything.

The table below separates what the subscription covers from what you still pay for. The "included" column comes from SAP's own pages and service description guide. The "not included" column is where I see costs land later.

Area	Included in the subscription	Not included, or extra
ERP software	SAP Cloud ERP Private for the FUEs you buy	Industry add-ons and other SAP cloud products unless listed in your order form
Infrastructure	Hosting on a hyperscaler or SAP's own data centres, with no separate hyperscaler contract	Extra database or file storage beyond the default allocation
Technical operations	Management of infrastructure, operating system, SAP HANA database and the application, with application-level SLAs	Functional support of your business processes, unless you buy it separately
Service levels	The standard availability SLA	The 99.9% SLA, disaster recovery and GxP, each a separate subscription
System size	The usage tier that matches your FUE count	A larger tier, if data volume outgrows the FUE-based sizing
AI	Base AI, including Joule, at no extra cost	Premium AI and Joule Agents, paid in AI Units
Transformation tools	The RISE toolchain SAP describes (SAP Signavio, SAP LeanIX, WalkMe), to the extent your order form entitles you	Anything beyond the entitled users, environments or data loads
Implementation	The RISE with SAP methodology and SAP onboarding support	Partner fees, data migration, custom code remediation, testing and training

A few of these need a sentence of explanation.

On SAP's operations page, the managed service goes beyond infrastructure to include the operating system, the SAP HANA database and the application. That is technical operations. Your posting logic, your master data and your month-end close are still yours.

The service description guide is explicit about the optional pieces. The 99.9% SLA "requires additional infrastructure and services", and disaster recovery and GxP apply only where you buy them. The smallest base option is limited to the first usage tier, up to 135 FUEs.

On transformation tools, be careful. SAP's 2026 description of RISE names SAP Signavio, SAP LeanIX and WalkMe as part of the toolchain. What you are actually entitled to, and in what quantity, depends on the package and the order form, so check each line.

SAP Business Technology Platform (SAP BTP) credits follow the same rule. In SAP's earlier packaging, credits came with the premium packages, not the base one. If BTP credits are in your deal, find the amount, what they can be spent on and when they expire.

The three traps I see most often are renewal terms, FUE sizing and AI credits. None of them is hidden. They are just easy to wave through when the programme is under pressure to sign.

1. Renewal terms. The first term is negotiated hard. The renewal often is not, and it is where the long-term cost sits. SAP's service description guide says that for renewing subscriptions the then-current guide applies, so the rules can change at renewal. Fix the renewal price cap, the notice period and the terms that carry forward before you sign the first term.
2. FUE sizing. FUEs are sized early, often before the design is done, and often on job titles. Every user classified as advanced who only approves or displays costs five times what a core user would. Because the FUE count holds for the term, an oversized first order form stays oversized.
3. AI credits. On SAP's AI pricing page, Base AI is included with every SAP cloud subscription. Premium AI and Joule Agents are paid in AI Units, bought annually, and unused AI Units expire after 12 months. Usage above what you bought is billed as excess use unless you switch features off in SAP for Me.

The AI point is moving fast. SAP says it is changing its AI commercial model later in 2026, moving most generative AI features into Base AI and refocusing Premium AI on agents priced per action. Do not prepay a large AI Unit pool for a pilot that has no owner and no use case.

Two things go into every RISE negotiation I am involved in: the modules that are included, and phase-wise pricing.

The modules that are included

Write down which modules, add-ons and cloud services are in the subscription, by name. "S/4HANA" is not a scope.

Check finance, logistics, any industry solution, analytics and the transformation tools line by line against your design. A module you need but did not list becomes a separate order later, without the bargaining power you had at the start.

Phase-wise pricing

Phase-wise pricing means you pay as phases go live, not for the full scope from day one. If your programme rolls out by entity, region or wave, the subscription should follow the same shape.

Without it, you pay full FUEs for users who will not touch the system for a year or more. On a RISE programme that runs 9 to 18 months before the first go-live, that is real money.

My view is that these two terms matter more than the headline discount. A good discount on the wrong scope, paid too early, is still overspend.

The other terms I would check

Beyond those two, this is the list I would work through with procurement:

1. Renewal cap. A ceiling on the uplift at renewal, written into the first contract.
2. FUE reallocation. Confirm in writing how users move between use types as roles change.
3. Credit expiry. Every BTP credit, AI Unit and included service, with its expiry date and owner.
4. Storage and tier growth. What a larger system tier or extra storage costs before you need it.
5. Exit and data. Export format, timing and charges if you leave or do not renew.

In January 2024 SAP offered migration credits for RISE and GROW moves, available through the end of 2024. I have not found a current SAP-published equivalent. Ask your account team whether any incentive applies to your deal, and get it in writing.

My SAP licence negotiation guide covers user classification, digital access and renewal clauses in more depth.

Take these into the commercial meeting. The answers should come back in writing, not in a slide.

1. Which modules, add-ons and cloud services are in this subscription, listed by name?
2. How did you size our FUEs, and on what user data?
3. Which system tier does that FUE count give us, and what happens if our data outgrows it?
4. Can the subscription ramp by phase, so we pay as each phase goes live?
5. What is the renewal price cap, and which terms carry into the renewal?
6. Which BTP credits, AI Units and transformation tool entitlements are included, how much, and when do they expire?
7. Where is the line between SAP's technical operations and our responsibilities?
8. What does exit look like: data format, timing and cost?

The partner matters here too. If your systems integrator is helping to size FUEs, ask whose interest that sizing serves. My guide on how to choose an S/4HANA migration partner covers what to ask them.

Before the next commercial meeting, build your own FUE count. Pull a list of users by what they actually do in the system, classify them as advanced, core or self-service, and map them to your rollout phases.

That one exercise tells you whether SAP's sizing is right and gives you the basis for phase-wise pricing. Then put the full programme cost next to the subscription, using my guide to S/4HANA migration cost, because the subscription is only part of it.

If you are still deciding between editions, read RISE with SAP public vs private cloud first, and my RISE with SAP page for the offering itself. I help organisations review RISE deals before they sign, so get in touch if an independent view would help.

How much does RISE with SAP cost?

SAP does not publish a RISE with SAP price list. The price is quoted and depends mainly on the number of Full Use Equivalents, the system size, the modules in scope and the term. The subscription is only part of the cost: implementation, data migration and partner fees sit on top.

What is an FUE in RISE with SAP?

A Full Use Equivalent is the usage metric for SAP Cloud ERP Private. One FUE covers one advanced user, five core users or 30 self-service users, and a developer counts as two FUEs. You can move FUEs between use types during the term, but the FUE count in your order form holds for the whole term.

What is included in RISE with SAP?

The subscription includes the SAP Cloud ERP Private software for your FUEs and hosting on a hyperscaler or in SAP's data centres. SAP also manages the infrastructure, operating system, database and application. Base AI, including Joule, is included.

Tool entitlements such as SAP Signavio, SAP LeanIX and BTP credits depend on your package and order form.

What is not included in RISE with SAP?

Implementation, data migration, custom code remediation, testing, training and partner fees are not included. Neither are the 99.9% SLA, disaster recovery, GxP, extra storage, Premium AI and add-ons not listed in your order form. Functional support of your business processes is also yours unless you buy it separately.

Are SAP AI Units included in RISE with SAP?

Base AI is included in every SAP cloud subscription and does not use AI Units. Premium AI, such as Joule Agents and advanced AI services, is paid in AI Units, bought annually. Unused AI Units expire after 12 months, and usage above what you bought is billed as excess use.

What should I negotiate in a RISE with SAP contract?

I always negotiate the modules that are included, by name, and phase-wise pricing so you pay as phases go live. Then fix the renewal price cap and notice period, the expiry of every credit and the exit terms. Size your own FUEs before you accept SAP's number.