SAP RISE, decoded. One contract, four meters, every renewal.

RISE with SAP packages S/4HANA Cloud, infrastructure, services, and BTP credits under one annual fee. The single fee is the marketing. The renewal mechanics are not single line at all.

RISE with SAP, announced by SAP in 2021, has become the publisher's default commercial path for S/4HANA Cloud. The promise is operational simplicity. The reality is a contract that bundles four moving cost lines under one signature.

Customers that read RISE as a simplification project run into the same renewal trap: the four lines move independently, and the publisher walks each one upward at the anniversary if the customer cannot frame the conversation differently.

This hub pulls together the buyer side view of RISE. Read the related SAP knowledge hub, the SAP advisory practice, the SAP BTP knowledge hub, and the wider SAP pillar hub for the full renewal context.

What RISE actually is

The bundle in plain language

RISE with SAP packages four components into one annual contract.

• S/4HANA Cloud, Private Edition. The ERP application, run as a managed service.
• Hyperscaler infrastructure. AWS, Azure, or Google Cloud, provisioned by SAP, billed under the RISE line.
• SAP managed services. Basis, lifecycle, and the application management layer.
• BTP credit allocation. A small, bounded credit pool for integration and extension workloads.

Two contract variants

RISE comes in two operational shapes.

• RISE Premium Plus. The fuller package including additional managed services and the higher BTP allocation.
• Standard RISE. The base bundle. Most customers start here.
• Add ons. Sustainability, Signavio, Concur, and SuccessFactors sit alongside but are not in the RISE bundle.

What RISE is not

RISE is not S/4HANA Public Cloud. It is the Private Edition, sold under a managed service operating model.

RISE is not a license retirement program. Existing on premise licenses are converted into the RISE pool. Sometimes credited. Sometimes not.

Read the related SAP RISE ERP cloud advisory for the migration framework, and the hidden costs guide for the costs that sit outside the bundle.

The commercial anatomy

Full User Equivalent metric

RISE uses Full User Equivalent, abbreviated as FUE. FUE is a normalized unit that maps the various S/4 user types onto a single counter.

The conversion ratios published by SAP convert a basket of professional, functional, productivity, and developer users into FUEs. The ratios are not symmetric. Each user type carries a different weight.

Pricing structure

• Annual subscription fee. Anchored to the contracted FUE pool.
• Multi year term. Typically three or five years.
• Stepped uplift. Year on year price escalation, often four to seven percent.
• Overage rate. The unit price for FUEs consumed above the contracted pool.
• True forward clause. The contractual mechanism for catching up overrun at the anniversary.

Conversion from on premise

Existing S/4HANA on premise licenses do not transfer automatically. SAP offers a conversion credit, applied against the RISE fee.

The credit value is negotiable. The publisher's opening position is rarely the floor.

Read the related SAP RISE negotiation guide for the conversion math and the buyer side counter moves.

The four cost lines

Line 1: FUE subscription

The headline line. Driven by the contracted pool and the stepped uplift.

Buyer side moves include band negotiation, downward true up at midterm, and the FUE conversion ratios where they are unfavorable.

Line 2: Hyperscaler infrastructure

The infrastructure line sits inside the RISE contract but is provisioned by SAP on AWS, Azure, or Google Cloud.

The buyer cannot directly negotiate the hyperscaler. The buyer can negotiate region, environment count, and the right to bring own discount from an existing hyperscaler agreement.

Line 3: BTP credit overage

The RISE bundle includes a small BTP allocation. The allocation is rarely sufficient for an enterprise estate. The overage is billed under the BTP rate card.

Read the related SAP BTP knowledge hub for the credit governance framework and the renewal lever.

Line 4: Indirect access on S/4

Digital access licensing on S/4HANA falls outside the RISE bundle in most contract variants. Integration Suite flows, third party application access, and direct API calls all generate counted documents.

The cost lands on the S/4 renewal as a separate digital access line. It is the single biggest in term surprise on most RISE estates.

Indirect access overlap

How the documents are counted

Digital access counts documents created or modified inside S/4 by external systems. The framework includes sales orders, invoices, purchase orders, and several other document types.

Volume forecasting is critical. A document pool sized too tight triggers a true forward. A pool sized too loose ties up budget that could fund FUE.

Buyer side counter moves

• Run a document type inventory across the connected systems.
• Establish a baseline measurement period before the renewal.
• Negotiate the digital access pool floor and the overage rate.
• Document which Integration Suite flows generate counted documents.
• Pull in the SAP advisory practice for the joint conversation across RISE and indirect access.

RISE is one contract with four meters. Treat each meter separately, run the year on the operating gates, and the renewal stops being a surprise.

Renewal traps to avoid

Top six traps

• FUE pool overrun. Letting the FUE consumption drift over the contracted pool without a midterm true up.
• Conversion ratio drift. User types reclassified into heavier FUE bands at renewal.
• Hyperscaler lock in. Region or hyperscaler choice that prevents future portability.
• BTP credit cliff. A bundled credit allocation that ramps up gradually then jumps at renewal.
• Indirect access surprise. Digital access true forward driven by uncounted document flows.
• Stepped uplift compounding. Year on year uplifts that compound through the multi year term.

Renewal cadence

The RISE renewal conversation should open twelve months before the anniversary. The contract complexity does not collapse into a three month cycle.

Earlier is better. Twelve months gives the buyer time to negotiate the FUE conversion ratios, the rate card, and the digital access pool floor in parallel.

Buyer side moves at renewal

Headline moves

• FUE band negotiation. Push the contracted pool to the operating reality, not the publisher's growth projection.
• Conversion ratio audit. Confirm the user type to FUE conversion is documented and locked.
• BTP credit conversion rights. Convert unused RISE BTP credits into other service families.
• Hyperscaler region lock. Lock the region to the contract effective date.
• Digital access pool floor. Negotiate the pool against a documented baseline.
• Stepped uplift cap. Cap the year on year escalator to a defensible CPI proxy.

Operational gates

The buyer side renewal posture is grounded in operational gates that run across the year, not just at anniversary.

Quarterly FUE consumption review, monthly BTP credit draw review, and a half yearly digital access reconciliation are the three gates that keep the renewal conversation honest.

What to do next

1. Inventory the full RISE contract across FUE, infrastructure, BTP credits, and digital access.
2. Run the FUE conversion ratio audit against the current user base.
3. Pull the BTP cockpit export and reconcile against the bundled allocation.
4. Establish a digital access baseline measurement across the connected systems.
5. Open the renewal conversation no later than twelve months before the anniversary.
6. Negotiate the FUE band, the BTP carry forward, and the digital access pool floor in parallel.
7. Cap the stepped uplift at a defensible escalator.
8. Brief the SAP advisory practice on the renewal posture you want to take.

Frequently asked questions

What does RISE with SAP include?

S/4HANA Cloud Private Edition, the hyperscaler infrastructure, SAP managed services, and a bounded BTP credit allocation. Add ons such as Signavio, Concur, and SuccessFactors sit alongside, not inside, the bundle.

What is a Full User Equivalent?

FUE is the normalized user metric SAP uses for RISE. The various S/4 user types convert to FUE at published ratios. The ratios are asymmetric, so user mix changes the FUE total.

How is RISE different from S/4HANA Public Cloud?

RISE is the Private Edition, sold as a managed service on hyperscaler infrastructure. Public Cloud is a different product with different commercial mechanics and a different upgrade cadence.

Are BTP credits included in RISE?

Yes, a small allocation. The allocation is rarely sufficient for an enterprise estate, and most RISE customers carry a separate BTP commit on top.

Does RISE cover digital access licensing?

Not in most variants. Digital access on S/4HANA is billed separately under the indirect framework. The cost lands on the S/4 renewal as its own line.

When should we open the RISE renewal conversation?

No later than twelve months before the anniversary. The contract has four interacting cost lines, and the negotiation needs time to land each one.

Can we change hyperscalers mid term?

Not easily. The region and hyperscaler are anchored at signing. The buyer side play is to negotiate a portability clause and to bring own discount from an existing hyperscaler agreement.