An SAP renewal is not a routine invoice. Between RISE with SAP, the Full-Use Equivalent (FUE) metric, indirect access, and a maintenance percentage that rides through every migration, the number on your order form is shaped by pricing mechanics most buyers never see until quote day.
This guide is written from the buyer's side by a strategic sourcing executive with Fortune 50 experience who has run thousands of renewals. It walks through how SAP pricing actually drives your cost, where the money quietly hides, the levers that genuinely move the price, and when to start. No hype, no referral fees, no vendor loyalty.
Every figure below is directional and estimated — drawn from public pricing and aggregated practitioner experience, not anyone's confidential contract and not a promise of savings. Use it to understand the shape of the problem, then pressure-test your own quote against it.
Directional and estimated ranges from public SAP pricing and aggregated renewal experience — not any organization's confidential terms, and not a guarantee of savings. Normalize your own order form to the same basis before comparing.
| Cost line | Typical unit | Directional range | Where you want to land |
|---|---|---|---|
| RISE with SAP | Per FUE / year | Quote-based, wide directional | Right FUE mix; convert users at 1 / 5 / 30 ratios accurately |
| Named user (on-prem legacy) | Per named user (perpetual) | Quote-based by user type | Retire unused named users before converting to RISE |
| Enterprise Support / maintenance | % of net license / year | ~22% of license value (directional) | Watch the effective % once folded into RISE |
| Digital / indirect access | Per document (order, invoice) | Quote-based, document-tiered | Measure indirect access now; negotiate the tiers |
| S/4HANA migration / conversion | FUE conversion credits | Quote-based | Negotiate conversion credits for existing ECC spend |
| Multi-year uplift | % increase / year | Commonly ~3–7% | Cap at CPI |
How to read this: SAP publishes no list price, and RISE bundles license, support, and infrastructure into one FUE-priced subscription. Discount depth tends to scale with FUE volume and multi-year commit, and the biggest exposure usually hides in the FUE conversion math and in indirect access you haven't measured — plus a maintenance percentage that survives the migration. Treat these as leverage on mix, tiers, and effective rate, not as a precise target.
How SAP pricing drives your renewal cost
SAP publishes no list price, which is the first thing working against you. With RISE with SAP, license, Enterprise Support, and cloud infrastructure are re-wrapped into a single subscription priced through the FUE metric. One FUE is generally equated to one Advanced Use user, five Core Use users, or thirty Self-Service users — so how your people are classified changes the bill dramatically.
A few mechanics matter more than the rest:
- FUE mix is the price. Misclassifying Core or Self-Service users as Advanced inflates your FUE count and your cost. Get the ratios right before you agree to a number.
- Discount depth scales with volume and commit. Larger FUE volumes and multi-year commitments tend to unlock deeper discounts — which cuts both ways if your usage is soft.
- Maintenance survives the move. Enterprise Support has historically run in the region of 22% of net license value. Once it is folded into a RISE subscription, watch the effective percentage — it does not disappear, it just gets harder to see.
Where the money hides
The biggest SAP overpayments rarely come from the headline user count. They come from lines buyers haven't measured:
- FUE conversion math. Moving from on-prem named users or ECC to S/4HANA and RISE runs through a conversion that can quietly re-price your whole estate. This is usually where the largest exposure sits.
- Indirect / digital access. Under SAP's digital access model, this is priced per document (orders, invoices, and similar) on a tiered basis. If a third-party system touches SAP data, you may owe for access you never counted. Measure it now, before SAP does.
- Dormant named users. Legacy perpetual named users you no longer use can get carried into the conversion. Retire them before you convert, not after.
- Engine and package metrics. Revenue-based, record-based, and other engine metrics drift from real usage over time. Each one should map to current consumption, not a number set years ago.
None of these show up as a problem on the quote. They show up as a bigger FUE total or an extra line you didn't budget.
The levers that actually work in an SAP renewal
A few moves consistently tend to move an SAP renewal number in the buyer's favor:
- Fix the FUE mix first. Reclassify users to the correct Advanced / Core / Self-Service tiers before you negotiate volume. Right-sizing the mix often beats chasing a bigger discount percentage.
- Negotiate conversion credits. Existing ECC and license spend is leverage. Push for conversion credits that carry that value into the RISE/S/4HANA subscription rather than resetting to zero.
- Cap the uplift. Multi-year uplifts commonly land in the mid-single digits — often around 3–7% per year. Aim to cap increases at CPI, and get the cap in writing for every renewal year.
- Tier indirect access deliberately. Once you've measured document volumes, negotiate the digital-access tiers instead of accepting a default that assumes worst-case usage.
- Watch the effective maintenance rate. Ask how the support component (historically around 22% of net license) is reflected inside the RISE price, and hold it accountable as a real line, not a rounding error.
Timing and leverage: when to start an SAP renewal
Leverage in an SAP renewal is mostly a function of time and optionality. The buyers who do well start early enough to have real choices and real data.
- Start 9–12 months out for a RISE or S/4HANA-linked renewal. Conversion analysis, user reclassification, and indirect-access measurement take months, not weeks.
- Measure before you meet. Walk into the conversation already knowing your true FUE mix and your document volumes. Data you can defend is your strongest lever.
- Keep alternatives credible. Even where a full platform switch is impractical, scope, timing, and commitment length are all negotiable — and SAP knows the difference between a buyer who has done the homework and one who hasn't.
- Don't negotiate against the clock. A quote that lands a few weeks before expiry hands the timeline to the vendor. Set your own.
Get the full SAP Renewal Playbook
This guide is the shape of the problem. The $59 playbook gives you the fillable worksheets, the six-point negotiation plan, two copy-paste emails, and the full pre-renewal checklist — everything to walk into the SAP conversation with a number and a plan.
Get the SAP playbook — $59 → Get the free 15-point renewal checklist →Frequently asked questions
How do you negotiate an SAP renewal?
Start 9–12 months early, correct your FUE user mix before discussing volume, measure your indirect/digital access, and negotiate conversion credits for existing ECC or license spend. Aim to cap multi-year uplifts at CPI and get the effective maintenance rate spelled out inside any RISE price. The core principle: walk in with defensible usage data so the vendor is negotiating against facts, not assumptions.
What is the FUE metric in SAP RISE pricing?
FUE stands for Full-Use Equivalent, the metric SAP uses to price RISE with SAP. One FUE is generally equated to one Advanced Use user, five Core Use users, or thirty Self-Service users. Because user classification drives the FUE count directly, misclassifying lighter users as Advanced can inflate your subscription cost significantly — which is why fixing the mix is often the highest-leverage move in the negotiation.
How much does SAP maintenance cost?
SAP Enterprise Support has historically run in the region of 22% of net license value per year (directional, not a quote). In a RISE with SAP subscription that maintenance is folded into the single price, so the important thing is to identify the effective percentage inside the bundle rather than assume it disappeared.
What is SAP indirect (digital) access and why does it matter?
Indirect or digital access is usage of SAP data by third-party or non-SAP systems. Under SAP's digital access model it is generally priced per document (such as orders and invoices) on a tiered basis. It matters because it is easy to incur without realizing it, and it can surface as an unexpected charge during a renewal or audit. Measure your document volumes before the negotiation so you can push for the right tiers instead of a worst-case default.
When should I start preparing for an SAP renewal?
For a RISE or S/4HANA-linked renewal, begin 9–12 months before expiry. Conversion analysis, user reclassification, and indirect-access measurement take months, and starting late hands the timeline — and the leverage — to the vendor.
Key takeaways
- SAP prices RISE through the FUE metric — your user classification mix, not just headcount, drives the cost.
- The biggest exposure usually hides in the FUE conversion math and in indirect/digital access you haven't measured.
- Enterprise Support has historically run around 22% of net license value; watch the effective rate once it's folded into RISE.
- Retire dormant named users and negotiate conversion credits before converting existing ECC spend.
- Start 9–12 months out with defensible usage data, and aim to cap multi-year uplifts at CPI.