RISE with SAP private cloud licensing. The FUE count and the year four cliff.

RISE private cloud is priced per FUE, and your bill is set by two numbers agreed at signature: the FUE count and the price once the conversion credit ends in year four. You can negotiate both.

RISE with SAP is the commercial wrapper SAP uses to sell S/4HANA Cloud, and the private cloud edition is its premium tier. You get a dedicated tenant, support for custom code and country extensions, and a higher price per FUE.

Two numbers set at signature decide what you pay over the contract: the FUE count and the price from year four. Most buyers work hard on the first and never negotiate the second.

How does SAP price RISE private cloud per FUE?

RISE private cloud is licensed per Full Use Equivalent, or FUE. The order form states a total FUE count and a price per FUE, and each named user draws on that total according to a weight set by the type of use.

How much of a FUE does each type of user consume?

SAP's service use description sets the ratios. One FUE covers one Advanced Use user, five Core Use users, 30 Self Service Use users or half a Developer Access user. A FUE cannot be split across use types, but you may change the allocation between types during the term.

A person placed in Advanced Use costs five times a Core Use user and 30 times a Self Service Use user. Our FUE calculation guide covers the classification rules in detail.

What does a FUE cost at list and after discount?

List pricing on the private cloud proposals we review runs 220 to 280 euros per FUE per month. Discounts reach 25 to 50 percent for mid market buyers and 50 to 70 percent for global enterprises. They are deepest in SAP's fourth quarter, October to December, since SAP's fiscal year follows the calendar.

That is a range of 66 to 210 euros for the same software. Our FUE price benchmark bands show where comparable buyers settle.

What sits inside the all in price?

Why does the RISE FUE count come in too high?

The count comes in high because most buyers start from their ECC named user inventory. That list carries a decade of role drift, template defaults and people who have left, and converting it at face value prices all of it into the subscription for the full term.

In the conversions we advised, rebuilding the count from 90 days of actual transaction logs removed 15 to 30 percent of FUE before signing. The rebuild shifts borderline users down a weight, professional to functional and functional to self service.

How do you check what your users actually do?

• Workload by user. Transaction ST03N shows which transactions each person ran, which tells you whether the work is heavy, operational or self service.
• Last logon. The user master records each last logon date, so dormant and departed accounts can be locked and excluded first.
• Roles. SUIM shows what each user is authorized to do. Broad roles are what push light users into Advanced Use.
• The license view. A USMM measurement consolidated in SLAW gives the picture SAP will see. Our guide to USMM, LAW and SLAW explains the output.

After go live, SAP meters FUE consumption monthly through SAP Private Cloud Metering, and the private cloud consumption card in SAP for Me shows the result by use type. Review it every quarter and compare it with your contracted count.

What is the rebuild worth in a worked example?

Say SAP proposes 1,200 FUE and you negotiate 150 euros per FUE per month, a 250 euro list price less 40 percent. That is 1,800 euros per FUE per year, or 2,160,000 euros a year as proposed.

Each person moved from Advanced Use to Core Use frees 0.8 FUE. Moving 100 people that way frees 80 FUE, worth 144,000 euros a year at the example price.

What is the RISE year four cliff?

The year four cliff is the price jump when the conversion credit ends. The credit, typically 50 to 70 percent of the perpetual residual value of your ECC licenses, applies to years one to three and then drops to zero. In the contracts we review it is usually the largest hidden cost.

In the illustrative seven year model below, about $0.9 million a year saved in years one to three turns into $0.7 to $1.0 million of annual overspend from year four.

What does the cumulative picture show?

Using the midpoints for years one to three, $3.3M on RISE against $4.2M for staying, RISE is $2.7M ahead after year three. The lead shrinks to $2.0M after year four, $1.2M after year five and $0.3M after year six. By the end of year seven RISE is $0.7M behind, at $31.5M against $30.8M.

Why can you not reverse the conversion later?

Your ECC perpetual licenses terminate on the signature date. You trade a perpetual entitlement for a subscription one, with no route back if the year four price disappoints, so the seven year model is the document the decision should rest on.

The EU commitments on SAP maintenance strengthen the on premises alternative. Put them in the decision file before the conversion is signed.

Why we do not judge RISE on the first year saving

The usual advice is to compare the RISE quote with today's spend and sign if it is lower. We disagree, because the credit is what makes years one to three look cheap. In the model, RISE is cheaper in each of the first three years and still costs more over the full term.

Negotiate the year four price as hard as the year one price instead. Write the post credit rate into the order form and cap increases after it. A 2 percent annual cap from year four would hold years 5 to 7 at about $5.20M, $5.31M and $5.41M, saving $0.58M against the uncapped curve.

That cap narrows the seven year gap from $0.7M to about $0.1M. Closing it takes a lower FUE count as well, so the rebuild and the year four terms belong in the same negotiation.

The credit expires on a date written into your own contract, so the price that follows it belongs in the same contract.

Does the hyperscaler choice change RISE pricing?

The hyperscaler changes less than the sales process implies. SAP holds the FUE rate constant across AWS, Azure and Google Cloud, with SAP managed infrastructure a fourth option few buyers choose. Only the bundled infrastructure line changes.

What changes the infrastructure line?

• Region coverage. Which regions each provider offers for your tenant.
• Data residency. Where the data must stay, which can narrow the choice.
• Disaster recovery. A warm or a hot standby shifts the line by 30 to 60 percent on its own, so price both.

Can RISE spend count toward an AWS or Azure commitment?

Where you hold an AWS EDP or an Azure MACC, RISE infrastructure spend can count toward it if SAP marketplace billing is enabled. Confirm that in writing before you choose the hyperscaler. Our guides to marketplace spend under an EDP and MACC negotiation cover the commitment side.

You can run the numbers in minutes on the RISE TCO calculator, and compare RISE, on premises S/4HANA and staying on ECC in our S/4HANA or RISE migration report 2026.

What does RISE private cloud include, and what does it leave out?

RISE includes less than many buyers assume. The bundle carries the S/4HANA subscription, managed infrastructure and service, BTP starter credits, and starter packages for Signavio and SAP Business Network. These license separately:

• SuccessFactors (see our SuccessFactors pricing guide)
• Concur
• Ariba beyond the basic Business Network starter
• Commerce Cloud and Customer Data Cloud
• Country payroll modules

The starter packages run out quickly when S/4HANA is heavily integrated with other systems. Size expected use before signing, so overage is priced while you still have a choice.

Do SAP audits continue on RISE?

Yes. Audit rights survive the conversion, and digital access remains the largest exposure. SAP licenses it separately, by document, and the starter pack depletes fast when third party systems create orders and invoices in S/4HANA.

Findings on RISE show up as FUE overage against the contracted count and as documents above your entitlement. Benchmark document volume in year one, then pre audit every quarter. The same report gives you evidence at renewal.

What have we seen in recent RISE conversions and renewals?

Two failures repeat across the RISE conversions and renewals we have advised on. Both come from accepting the first numbers on the table without testing them.

• The count. Buyers converted the FUE count from the old inventory without testing it. That was the largest overspend we found, and it carried into every year of the term.
• The credit. Buyers left the year four terms open while the credit in years one to three made the deal look cheap, then met the cliff unprotected.

What will the SAP account team say, and how should you answer?

Expect the account team to defend its sizing, the first year saving and the single price. These are the lines we hear most often, with the replies we give.

• "The FUE sizing comes straight from your current licenses." Reply that licenses bought years ago do not show current use. Offer your usage based count and ask SAP to reconcile its figure to yours, group by group.
• "RISE saves you money from day one." Ask for the year four price without the credit and a seven year comparison with staying on ECC.
• "The price is one bundled figure." Ask for the four lines priced separately before discussing the total.
• "Digital access can wait until after go live." Say no to that. Put a document allowance or a price per block of documents in the order form now, while you can still compare it with the rest of the deal.

Our note on SAP fiscal quarter timing explains when a quarter end deadline helps you.

Which contract terms should you ask for before signing RISE?

Ask for terms that fix the price after the credit ends and keep each cost line visible, and put them in the order form, where they bind.

1. Year four price. The post credit rate written into the contract, so the cliff is a known number.
2. Uplift cap. A ceiling on increases from year four. Our uplift cap benchmark shows what buyers obtain.
3. Allocation flexibility. Written confirmation that you can move FUE between use types during the term.
4. Use type ratios. The service use description version named in the order form, so the users each FUE covers are fixed for the term.
5. Disaster recovery tier. The standby option named and priced, instead of a default.
6. Digital access allowance. A document entitlement fixed at signature from your own volume estimate.

What to do next

1. Rebuild the count. Use 90 days of transaction logs, never the ECC inventory, and place each user in the lowest use type the work supports.
2. Settle year four at signing. Write the post credit price and the uplift cap into the order form.
3. Get the four lines. Price subscription, infrastructure, managed service and BTP separately and negotiate each.
4. Check your cloud commitments. Confirm marketplace billing against your EDP or MACC in writing before choosing the hyperscaler.
5. Watch digital access. Benchmark document volume in year one and pre audit every quarter.
6. Bring in help. Our SAP practice runs RISE conversions alongside your team.

Frequently asked questions