Derivative Pricing in SAP RISE Contracts: How Hidden Price Logic Eats Into Your Budget

You adjust the system sizing. More capacity after go-live, because load is higher than originally planned. A technical decision that looks manageable. Then comes the next invoice.

The amount grows not only for the adjusted component. Disaster Recovery, certain add-ons, capacity extensions: all derivatively priced. The price of one component is calculated as a percentage of another, the so-called base component. Contract analysis in practice shows that Disaster Recovery often sits at a fixed percentage of the monthly subscription. If the base goes up, every dependent line goes up proportionally. Automatically. For the rest of the contract term.

What looks like a simple price logic at first sight has substantial consequences in practice. Not because SAP hides this in your contract, but because the structure is complex and rarely calculated through in full at initial negotiation. The result: companies notice cost changes only when the invoice arrives.

A structural shift of control

Gartner described the pattern clearly back in 2023. A report covered by The Register in September 2023 put it this way: “Several cost components previously under the user’s control will move to SAP, reducing client influence on running costs.” That is not a value judgement but a structural description of the RISE model. Costs that used to be steerable through your own infrastructure decisions are moved into a subscription whose price trajectory is set by SAP.

In 2025 a further factor entered the picture: the introduction of the FUE metric, Full Use Equivalent. Functions that customers previously covered through lower-tier licence categories are pushed into more expensive Professional categories. Speaking to The Register in July 2025, Michael Bloch of the DSAG board put it plainly: "FUE metric costs more compared to the old RISE Premium." The base on which all derivative components sit is raised. Not through an explicit new contract line, but through a redefinition of the price metric.

Scott Bickley of Info-Tech Research describes this in CIO Magazine as a "stealth price increase": customers have to acquire higher-tier licences that are exponentially more expensive. Mike Tucciarone, VP Analyst at Gartner, adds that specific capabilities such as SAP Datasphere have dropped out of the standard scope. Together this creates an effect that is poorly addressed in existing contracts: the price base rises without an explicit price increase being negotiated, and every derivative position follows the base.

Timing sharpens the situation. Increases hit immediately as soon as sizing changes or a new metric applies. Reductions are typically only available at renewal. The asymmetry is contractually intended, not accidental.

What you can do: four concrete steps

1. Full mapping of derivative price components

Before approving or commissioning a sizing change, know which contract components are derivatively priced and which base component they reference. That sounds obvious but is often poorly documented in practice. Build a complete list of all components that depend on another as a percentage, including the formula and the current base values.

The mapping is not a one-off task. It belongs in the process of every material contract change. A sizing request that runs through without this preparation is a financial risk that materialises weeks later.

2. Negotiate clauses for mid-term reductions

The asymmetry between immediate increases and deferred reductions is negotiable, at least in a new negotiation or a renewal. Check whether your contract allows mid-term reductions and under what conditions. If not, make this an explicit negotiation point.

Even without full symmetry, buffers can be built in. For example defined points in the year at which sizing reductions can take effect, or a fixed percentage by which a reduction is possible outside of renewal. What is not regulated contractually sits at SAP’s discretion.

3. Assess the FUE impact on the current contract structure

The FUE conversion has not been fully evaluated in many existing contracts. Which of your current licence categories are affected? Which functions previously included in standard scope fall under the new metric? And how does that change the base on which your derivative components are calculated?

This analysis is time-critical. If your contract is up for renewal in the next twelve to eighteen months, the FUE impact should already be reflected in your planning baseline, not only when SAP presents the renewal offer.

4. Establish mid-cycle monitoring as a mandatory process

SAP RISE contracts are not static documents. Sizing changes, usage patterns develop, SAP adjusts metrics and scope. Anyone who only looks at the contract once a year, just before renewal, is reacting too late.

Mid-cycle monitoring concretely means: quarterly review of actual cost against contract expectation, systematic capture of sizing changes and their financial impact, and a clear owner on your side responsible for the task. This does not require heavy infrastructure. It requires a process and accountability.

Conclusion

Derivative pricing is not a flaw in the SAP RISE model but a structural feature that requires full transparency and active management. The combination of percentage-based dependencies, asymmetric adjustment rules and the FUE conversion creates an environment where cost changes do not always show up as explicit price increases.

Customers who know their contract, which positions are derivatively dependent, how the base metrics are defined and how the FUE conversion changes the price base, can steer. Those who do not, see the change first in the next invoice. SAP RISE contracts are complex enough to justify a structured approach: before signing, after go-live, across the full lifecycle.

Sources:
Gartner via The Register (1 September 2023): “Several cost components previously under the user’s control will move to SAP.”
Michael Bloch (DSAG) via The Register (11 July 2025): "FUE metric costs more compared to the old RISE Premium."
Scott Bickley (Info-Tech) via CIO Magazine (27 June 2025): "This is a stealth price increase."
Mike Tucciarone (Gartner) via CIO Magazine (27 June 2025): "Some capabilities, such as SAP Datasphere, are no longer included."