The hidden uplifts in year four of a RISE contract.

Year four is where most RISE with SAP contracts begin to bleed. The first three years are negotiated under bright light, with discount stacks, executive scrutiny, and a procurement team that knows what it is signing. Years four through seven attract far less attention. That is exactly where SAP places the mechanisms that quietly grow the total cost of ownership: the indexed uplifts, the consumption escalators, the FUE re measurement clauses, the support tier resets, and the unit price floors that activate after the initial commitment expires. A disciplined buyer reads year four with the same care as year one, because almost every avoidable cost overrun on a RISE contract traces back to a clause that was easy to find on signing day and impossible to renegotiate after it activated.

01.Why year four is the inflection point

SAP designs RISE with SAP commercial structures around a three year economic horizon. The discount stack is calibrated to that window. The promotional credits, the bundling concessions, and the migration incentives all live inside the first thirty six months. When the calendar turns into year four, the proposal that looked attractive at signing reverts to a different commercial profile. Unit prices reset to a higher floor. Promotional credits expire. The terms that were marked transitional become permanent. The shift is rarely announced in a single conversation; it is engineered into the order form schedules and the price lists referenced by those schedules.

Buyers underestimate the inflection because the procurement team that negotiated the deal is rarely involved in tracking it. The contract goes into a repository. The owner moves to another project. The renewal team that picks it up two or three years later inherits a structure they did not design. By that point the supplier has the leverage. Reopening year four terms after signing is functionally impossible unless a material change in scope creates the opening.

The right time to negotiate year four is during the initial deal. Every uplift mechanism that activates after year three should be examined, priced, and either capped, removed, or traded for a different concession. The work is unglamorous. It also produces the single largest source of seven year TCO improvement we see across engagements.

02.The indexed uplift clause

The most common hidden uplift is the indexed escalator. The clause appears in the pricing schedule, often as a single sentence, and ties annual price increases to an inflation index such as the US Consumer Price Index or a comparable national equivalent. The clause is presented as standard. It is not. Buyers who accept it without negotiation give SAP an open ended path to grow the annual fee at rates that have, in recent years, run between five and eight percent.

The first move is to cap the index. A cap of two percent annually, applied to the base RISE subscription and to any consumption commitment, removes the worst case exposure. The cap should be expressed in absolute terms, not as a percentage of the prior year, because compounding language has been used to convert a small annual percentage into a much larger seven year total.

The second move is to delay the activation. If the index applies from year one, the compounding starts immediately. If the index applies from year four or year five, the buyer protects the heavily negotiated early years. Activation timing is one of the most negotiable elements of the clause and is rarely defended hard by the SAP side.

The third move is to exclude specific components from the index. BTP consumption credits, hyperscaler infrastructure pass through, and any one off implementation fees should never be subject to indexation. Buyers who do not separate these components find that the entire bundle escalates together, which produces increases on items where no cost basis justifies them.

03.The consumption escalator

The consumption escalator is the second category of hidden uplift. It applies to BTP, to elastic services, and to any element of the RISE bundle priced on a usage basis. The escalator works by setting a unit price for consumption during years one through three, then resetting that unit price upward for years four through seven. The reset is typically presented in a separate price list, referenced by the order form, and not surfaced in the executive summary.

The mechanism produces sharp increases because consumption tends to grow over the contract term. A buyer who consumes one thousand units in year one and three thousand units in year five faces both a higher unit count and a higher unit price. The combination compounds into a four to six times spend increase on the consumption line, even before any indexation is applied.

The defence is a price lock. The unit price applied to consumption during years one through three should be the same unit price applied during years four through seven, with no reset built in. If SAP resists, the next position is to cap the reset at a specific dollar amount per unit, agreed in advance, and recorded in the order form rather than in a price list that SAP can later update.

The supporting defence is a consumption commitment that matches realistic usage. Buyers who over commit on consumption end up subsidising units they never use. Buyers who under commit face overage rates that are several multiples of the committed rate. The right answer is a commitment slightly below the central forecast, with a credit pool for overages priced at the same rate as the committed units.

04.The FUE re measurement clause

The Full Use Equivalent re measurement clause is the third category and the most technical. Under RISE with SAP, user counts and license metric values are translated into FUE units, and the FUE conversion factors can change over time. The order form typically commits to a specific FUE count for years one through three. For years four onward, the contract often includes a re measurement provision that re evaluates the actual usage against the original FUE assumption.

The re measurement provision sounds neutral. In practice it almost always increases the buyer's commitment because the conversion factors SAP applies for re measurement are not the same factors used for the original sizing. Higher value user types are weighted more heavily. New license types introduced after signing are folded into the count at their current pricing. The result is a year four true up that frequently runs ten to twenty percent above the original FUE count.

The buyer side response is to fix the FUE conversion factors at signing and to bind them for the full seven year term. If SAP introduces new license types during the term, those types should be priced separately under the existing discount stack rather than folded into the FUE count. The order form should specify that re measurement, if it happens at all, is done using the original conversion table.

05.The support tier reset and the unit price floor

The fourth and fifth categories often appear together. The support tier reset moves the buyer from a negotiated support tier in years one through three to the standard support tier in year four. The change is sometimes accompanied by a fee increase, sometimes by a service reduction, and sometimes by both. Buyers who do not read the support schedule line by line discover the change only when a service request is downgraded.

The unit price floor sets a minimum price per unit that applies regardless of any discount stack agreed for years one through three. The floor is presented as protection for SAP against unrealistic discounting. In practice it functions as a ratchet that prevents the buyer from negotiating further reductions at renewal. The floor needs to be either removed or set at a level that the buyer is confident can be improved at renewal.

The combined defence against both mechanisms is to negotiate the year four through year seven commercials as carefully as years one through three. The buyer should request a single pricing table that covers all seven years, with the same discount stack applied across the full term, and with any tier changes either prohibited or subject to bilateral agreement. The conversation is uncomfortable in the late stages of a negotiation because the seller will push back on giving up the year four flexibility. The pushback is itself evidence that the year four flexibility is valuable.

Almost every avoidable cost overrun on a RISE contract traces back to a clause that was easy to find on signing day and impossible to renegotiate after it activated.

06.How to find every hidden uplift before signing

The discipline is procedural. Before signing, the buyer team should produce a single document called the uplift map. The document lists every clause in the order form, in the pricing schedule, and in any referenced price lists, that has the potential to increase a fee or reduce a service after year three. The document is reviewed line by line with legal, with finance, and with the operational team that will actually own the contract after signing.

The map produces a list of remediation items. Some items will be capped. Some will be removed. Some will be traded for other concessions. The remediation list is run as a discrete workstream in the final stages of negotiation, separate from the headline pricing conversation. The separation is important because SAP will negotiate the headline price hard and the schedules lightly. The buyer who reverses that emphasis recovers value in the schedules that more than offsets a slightly weaker headline discount.

The output of the uplift map is also the foundation for the seven year TCO model. The TCO model needs to include both the base case, where every uplift activates as written, and the negotiated case, where the uplifts have been capped or removed. The delta between the two is the value the buyer team has created in the schedules. That delta typically runs between twelve and twenty two percent of the seven year contract value across engagements, which is large enough to justify the procedural overhead many times over.

07.Conclusion

Year four is not a problem of vigilance after signing. It is a problem of design at signing. The hidden uplifts are not actually hidden, they are documented in the order form and the schedules, but they are positioned where executive attention rarely lands. The buyer team that treats years four through seven with the same intensity as years one through three closes the gap between the headline economics and the realised economics of a RISE deal. The seven year TCO that matters is the one the contract produces, not the one the discount stack implied at signing. Reading year four early, and reading it slowly, is the simplest way to make those two numbers converge.