RISE with SAP. Read the contract before you sign.

RISE with SAP is the consolidation play SAP has positioned as the default path to S/4HANA. The bundle collapses infrastructure, S/4HANA, BTP credits, and managed services into a single subscription.

The simplicity has a cost. The customer that signs without sizing the FUE conversion, the migration credit, and the exit clauses absorbs 3 to 7 years of price the workload did not need to carry.

1. What RISE actually bundles

RISE with SAP packages four distinct components into a single subscription. Understanding what each component is and what each component is not is the first step in any sizing exercise.

The four components

• S/4HANA Cloud Private Edition (or Public Edition). The S/4HANA application running on SAP managed infrastructure.
• Hyperscaler infrastructure. AWS, Azure, or Google Cloud underneath, abstracted from the customer.
• SAP Business Technology Platform credits. Developer extensions, integrations, AI services, analytics.
• Application managed services. SAP run technical operations and basis administration.

What RISE is not

• The implementation. The customer signs a separate implementation partner agreement.
• The functional configuration. The customer or the partner configures S/4HANA modules.
• The third party integrations. Salesforce, ServiceNow, Workday connections sit in BTP or in separate integration tooling.
• The data migration. The customer is responsible for data extraction, cleansing, and load.
• The change management. User training, organisational change, business process redesign.

2. The FUE metric

The Full User Equivalent (FUE) is the RISE pricing metric for application users. Every named user role on the on premises SAP system converts to a fractional FUE on RISE. The conversion table is part of the order form.

FUE conversion table

On premises role	RISE FUE conversion	Indicative use case
Professional User	1.00 FUE	Full S/4HANA functional access
Functional User	0.50 FUE	Wider functional access without development
Productivity User	0.20 FUE	Limited transactional access
Developer User	1.00 FUE	Custom development access
Test User	0.20 FUE	Test environment only
Employee User	0.10 FUE	Self service only

The FUE negotiation move

1. Audit the actual user activity on the on premises system. Last 90 days of active users by role.
2. Test the role mapping. Many users assigned a Professional role only need Productivity access.
3. Reclassify before conversion. Move users to the lowest role that covers their actual use.
4. Sign the FUE count at the actual usage. Not at the contracted on premises user count.
5. Negotiate the FUE true up cadence. Annual true up rather than monthly.

3. The sizing trap

The single largest cost trap in the RISE contract is the FUE sizing. SAP commercial templates default to converting the contracted on premises user count. The contracted on premises count typically runs 20 to 40 percent above the actual active user count.

The sizing pattern

A customer that signed an on premises agreement for 5000 Professional Users 7 years ago typically has 3500 to 4000 active users today. Some retired. Some replaced. Some never used. The RISE conversion at the contracted count produces an FUE total 25 to 40 percent above the actual need.

4. The migration credit

The RISE migration credit is the financial mechanism that smooths the transition from the on premises maintenance stream to the RISE subscription. The credit is one time and material in size.

How the credit is constructed

• Source. 12 to 36 months of the existing on premises annual maintenance fee.
• Application. Discount applied against the RISE subscription invoice across the early term.
• Timing. Typically credited across the first 12 to 24 months of the RISE term.
• Documentation. Recorded in the RISE order form as a one time credit line.

The credit negotiation

1. Pull the on premises annual maintenance fee. The total across all SAP products.
2. Propose the credit at 24 to 36 months. Larger estates carry stronger leverage.
3. Negotiate the credit application timing. Front loaded credit improves the early term cash flow.
4. Document the credit in the order form. Not in side letters or verbal agreements.
5. Cross reference the credit against the FUE total. The credit and the FUE pricing move together.

5. Indirect access and digital access

SAP introduced the document based digital access model in 2018 to address the indirect access concern that had created significant audit exposure under the named user model. RISE incorporates the digital access blocks as a separate pricing line.

The digital access document blocks

• The metric. Documents created in the S/4HANA system by third party integrations.
• The document types. Sales orders, purchase orders, invoices, service orders, manufacturing orders.
• The pricing. Per million documents per year at tiered rates.
• The audit position. SAP runs the digital access estimation tool against the system to measure consumption.

The negotiation moves

• Run the digital access estimation tool internally. Before SAP runs it externally.
• Forecast the 3 year document growth. The contract should not be sized at year 1 consumption.
• Negotiate the right tier. Larger document blocks carry larger discounts.
• Reserve the right to add document types. Without renegotiating the entire tier.
• Document the integrated third party systems. Sources that create documents must be named.

6. BTP credits and the application platform

SAP Business Technology Platform is the development, integration, and analytics layer of the RISE stack. BTP is priced in credits that the customer consumes against developer extensions, integration scenarios, and AI services.

The BTP credit units

BTP service	Credit consumption pattern	Sizing discipline
Cloud Foundry runtime	Per application instance per hour	Right size the application memory profile
Integration Suite	Per message processed	Filter low value messages at source
HANA Cloud	Per GB of memory per hour	Compress data, archive cold data
AI Foundation	Per inference per model	Cache inferences where possible
Data Sphere	Per data product capacity unit	Right size the capacity tier

The BTP sizing discipline

• Forecast the 3 year BTP usage by service. Cloud Foundry, Integration Suite, HANA Cloud, AI, Data Sphere.
• Right size the credit pool. Year 1 consumption plus modest buffer.
• Negotiate the credit rollover. Unused credits should carry forward.
• Negotiate the credit conversion. Credits should be fungible across BTP services.

7. The exit clauses

The RISE contract template assumes the customer stays on RISE for the full term and renews. The exit clauses that govern the alternative path are typically thin in the default contract. The customer must negotiate stronger exit language at signing.

Required exit clauses

• Data return obligation. SAP delivers all customer data in a defined format within a defined window.
• Source system handback. Right to receive the S/4HANA system image for self hosting.
• Transition assistance. SAP provides defined hours of transition support.
• Termination for material breach. Clear definition of what constitutes breach.
• Termination for convenience window. Some enterprise customers have secured a one time exit at mid term with defined penalty.
• Data residency continuity. Data stays in the customer's chosen region throughout the term and the exit.

The exit defense

The exit clauses are most often the lever that brings SAP back to the table on the broader commercial terms. The customer that negotiates stronger exit language signals that the RISE commitment is not unconditional. SAP commercial teams respond to conditional commitments with stronger pricing flexibility.

8. The renewal mechanics

The RISE renewal is the second largest commercial event in the RISE lifecycle after the initial signing. The renewal cap, the renewal pricing formula, and the renewal notice window all need to be negotiated at the original signing.

The renewal cap

• CPI plus 2 percent maximum. Some customers have secured a flat 3 percent cap.
• Cap applies to the full subscription. Not just the base, but base plus all add ons.
• Cap applies for the full renewal term. Year 4 plus pricing is bound.
• Renewal pricing formula referenced to the original FUE rate. Not to the SAP list at renewal.

The renewal notice window

1. 180 days minimum. Enough lead time to scope an alternative.
2. Renewal proposal delivery at 180 days. Not at 30 days.
3. The customer's notice right to non renew. 90 day notice without cause.
4. Right to extend at signing rates. The customer can extend 12 to 24 months at the original rate.

What to do next

The checklist takes the SAP buyer from where they are today to a sized, hardened, signed RISE agreement.

1. Pull the on premises user activity. Last 90 days, by role, by entity.
2. Run the FUE conversion modelling. At actual activity, not contracted count.
3. Pull the digital access estimation. Internally, before SAP runs it.
4. Construct the migration credit proposal. 24 to 36 months of on premises maintenance.
5. Size the BTP credit pool. 3 year forecast by service.
6. Draft the exit clauses. Data return, system handback, transition assistance.
7. Negotiate the renewal cap. CPI plus 2 percent maximum.
8. Run the deal through Vendor Shield. Independent buyer side review before signature.

Frequently asked questions

How Redress engages

Redress runs this practice inside the Vendor Shield subscription, the Renewal Program, the SAP Knowledge Hub, and the Software Spend Assessment.

Read the related SAP RISE Negotiation Guide, the SAP Hub, the case studies, the benchmarking service, the management team page, the about us page, and the contact page.