RISE private cloud licensing, the FUE count and the year four cliff
RISE with SAP is the commercial wrapper for S/4HANA Cloud, and the private cloud edition is its premium tier: a dedicated tenant, custom code and country extensions supported, at a higher price per FUE. The bill is decided by two numbers set at signing, the FUE count and the year four renewal cap, and most buyers optimize the first while never negotiating the second.
Prepared by Redress Compliance · August 7, 2026 · SAP advisory. Based on the RISE conversion and renewal engagement record.
Executive summary
The FUE count is the largest overspend, and it is set before signing. Every named user maps to a FUE weight, professional at 1.0 down to productivity users at 0.1, and most buyers walk in with the count from their old ECC named user inventory, which is almost always wrong: rebuilding it from 90 days of actual transaction logs removed 15 to 30 percent of FUE before signing. List runs 220 to 280 euros per FUE per month on private cloud, with discounts of 25 to 50 percent for mid market and 50 to 70 percent for global enterprise, strongest in SAP's Q4.
The conversion credit dies in year four, and the cliff is the contract's largest hidden cost. The credit covers years one to three at typically 50 to 70 percent of the perpetual residual value, then drops to zero: on the illustrative seven year model, the $0.9 million annual savings of years one to three flip to $0.7 to $1.0 million of annual overspend from year four onward. The ECC perpetual entitlement terminates at signature with no way back, so the year four renewal uplift cap anchors at signing or the cliff arrives unprotected.
The all in price hides four cost lines, and the leverage is in the lines. Subscription, bundled infrastructure, managed service, and BTP credits arrive as one number, and the breakdown is the negotiation: the FUE rate holds constant across AWS, Azure, and Google Cloud, while the infrastructure line changes, DR posture alone moving it 30 to 60 percent, and RISE infrastructure spend can count toward an existing EDP or MACC where marketplace billing is enabled. Demand the four line breakdown before comparing anything.
The audit machinery survives the move. SAP's audit rights continue on RISE, indirect access remains the largest exposure with the digital access starter pack running out fast on integrated landscapes, and the bundle excludes more than buyers assume: SuccessFactors, Concur, advanced Ariba, Commerce Cloud, and country payroll all license separately. Benchmark document volume in year one, and pre audit quarterly with the report doubling as a renewal lever.
The FUE math, weights and where the count inflates
| User type | FUE weight | Typical share of the population |
|---|---|---|
| Professional user | 1.0 | 10 to 20 percent |
| Functional user | 0.5 | 30 to 40 percent |
| Developer user | 0.5 | 2 to 5 percent |
| Self service user | 0.2 | 40 to 60 percent |
| Productivity user | 0.1 | 5 to 10 percent |
The seven year curve, and the cliff it hides
| Year | RISE all in | The ECC stay path | Variance |
|---|---|---|---|
| Years 1 to 3 | $3.2M to $3.4M with the conversion credit | $4.1M to $4.3M maintenance plus infrastructure | About $0.9M saved per year |
| Year 4 | $5.1M, no credit | $4.4M | +$0.7M overspend |
| Year 5 | $5.3M | $4.5M | +$0.8M |
| Years 6 to 7 | $5.5M to $5.7M | $4.6M to $4.7M | +$0.9M to $1.0M |
The SAP RISE negotiation guide
The proposal stack layer by layer: the FUE conversion, the year four cap, the four line breakdown, and the clauses that survive the credit's expiry.
Get the white paper →The hyperscaler decision, and what it actually changes
AWS, Azure, and Google Cloud are all supported, with SAP managed infrastructure the rarely chosen fourth, and the decision changes less than the sales process implies: the FUE rate holds constant across all three, and what moves is the bundled infrastructure line, region coverage, data residency options, and the DR posture that swings the line 30 to 60 percent between warm and hot. The commercial overlay is the real differentiator: where the buyer holds an AWS EDP or Azure MACC, RISE infrastructure spend can retire the cloud commitment if SAP marketplace billing is enabled, a term worth confirming in writing before the hyperscaler is chosen. The model runs in minutes on the RISE TCO calculator, and the full path comparison, RISE against on premise against staying on ECC, in the S/4HANA or RISE migration report.
- Percentile standing for your exact deal size and industry, from real closed transactions
- Scenario simulation before the call: test alternative terms and see the financial impact of each
- A negotiation playbook, talking points, and a two page executive brief on day one
What the engagement record shows
Across the RISE conversions and renewals in the engagement file, the same two failures repeated: the FUE count converted from the old inventory unexamined, and the year four terms left unnegotiated while the years one to three credit made everything look cheap:
Removed before signing by the transaction log rebuild, compounding at the per FUE rate all term.
Of perpetual residual value, applied to years one to three only, and gone at year four.
The permanence deserves its own line: the ECC perpetual license terminates at the signature date, trading perpetual entitlement for subscription entitlement with no way back, which is why the seven year model, not the year one price, is the decision document, and why the EU commitments that strengthen the on premises alternative belong in the file before the conversion signs. The bundle boundary completes the review: BTP starter credits, Signavio and Business Network starters included, while SuccessFactors, Concur, advanced Ariba, and country payroll all license separately, and the digital access exposure carries over intact, starter pack notwithstanding.
Your first five moves
- Rebuild the FUE count from 90 days of transaction logs, never the ECC inventory, and reclassify borderline users down the weight ladder.
- Anchor the year four renewal uplift cap at signing, because the credit expires, the cliff is the contract's largest hidden cost, and there is no way back to ECC.
- Demand the four line breakdown, subscription, infrastructure, managed service, and BTP, because the leverage is in the lines, not the total.
- Confirm marketplace billing against your EDP or MACC in writing before choosing the hyperscaler, and price the DR posture explicitly.
- Benchmark digital access document volume in year one and pre audit quarterly. The SAP practice runs the conversion with you.
Frequently asked questions
How is RISE with SAP private cloud licensed?
Per Full Use Equivalent: every named user maps to a weight, professional 1.0, functional and developer 0.5, self service 0.2, productivity 0.1, and the contract states the total FUE count and price per FUE. List runs 220 to 280 euros per FUE per month, discounted 25 to 50 percent for mid market and 50 to 70 percent for global enterprise, with Q4 the strongest window.
What is the RISE year four cliff?
The conversion credit, typically 50 to 70 percent of the perpetual residual value, applies to years one to three and then drops to zero: on the illustrative model, roughly $0.9 million of annual savings flip to $0.7 to $1.0 million of annual overspend from year four. The renewal uplift cap anchors at signing or the cliff arrives unprotected, with no path back to the terminated ECC licenses.
How much FUE can be removed before signing RISE?
15 to 30 percent, by rebuilding the count from 90 days of actual transaction logs instead of converting the old ECC named user inventory at face value. The old inventory carries a decade of role drift and leavers, and every FUE it inflates compounds at the per FUE rate across the whole term, which makes the rebuild the highest value pre signature exercise.
Does the hyperscaler choice change RISE pricing?
Not the FUE rate, which SAP holds constant across AWS, Azure, and Google Cloud: what changes is the bundled infrastructure line, moved by region coverage, data residency, and a DR posture worth 30 to 60 percent of the line. Where marketplace billing is enabled, RISE infrastructure spend can also count toward an existing AWS EDP or Azure MACC, confirmed in writing.
What is not included in RISE?
More than buyers assume: SuccessFactors, Concur, Ariba beyond the basic Business Network starter, Commerce Cloud, Customer Data Cloud, and country payroll modules all license separately. The bundle carries the S/4HANA subscription, managed infrastructure and service, BTP starter credits, and Signavio and Business Network starters, and the starter pools run out fast on integrated landscapes.
Do SAP audits continue on RISE?
Yes: audit rights survive the conversion, indirect access remains the largest exposure with the metric shifting to contractual FUE overage and digital access documents, and the starter pack depletes quickly on integrated landscapes. The discipline is benchmarking document volume in year one and pre auditing quarterly, with the report doubling as a renewal lever.
