The RISE renewal is not the on-prem renewal. The FUE measurement, the subscription term, the hyperscaler-pass-through line and the ramp-up versus run-rate disposition all read differently. The Admodum read on the architecture, the renewal-time levers and the disposition framework.
The RISE renewal is the subscription-renewal architecture. The buyer renews a subscription contract that includes the S/4HANA Cloud Private Edition (the SAP-managed cloud-native S/4HANA product), the BTP overlay (the Business Technology Platform services included in the RISE bundle), the embedded SAP Best Practices methodology, the embedded SAP support (typically Enterprise Support inclusive), and the embedded hyperscaler-pass-through infrastructure (AWS, Azure or Google Cloud). The renewal closes against the contracted FUE position, the contracted subscription term and the contracted price-per-FUE.
The RISE renewal differs structurally from the on-prem renewal: the on-prem renewal is a maintenance renewal against a perpetual licence position (twenty-two percent of the original licence value per annum); the RISE renewal is a subscription renewal against a subscription position (the price-per-FUE applied to the FUE inventory). The wider RISE bundle anatomy spoke reads the bundle structure.
The FUE measurement at renewal is the inflation-risk surface. The contracted FUE position at the original RISE adoption is the buyer's run-rate FUE: the buyer pays per FUE at the contracted price-per-FUE level. The actual end-user surface at renewal may have grown beyond the contracted FUE (organic user growth, new business unit migrations, acquired business unit migrations). The renewal-time FUE reconciliation runs the buyer-side rehearsal against the publisher-side measurement.
The reconciliation is structurally similar to the named-user recategorisation on the ECC track: the buyer reads each user against the FUE-category definitions, recategorises down where the activity evidence supports it, reconciles the duplicate accounts, and produces the renewal-time FUE position-of-record. The wider FUE conversion arithmetic spoke reads the FUE-category mechanics; the wider named-user recategorisation spoke reads the recategorisation discipline.
The subscription-term lever is the term length. The standard RISE term is five years; the buyer can elect a three-year term or, in some published cases, a seven-year term. The price-per-FUE differs across the term lengths: a five-year term typically prices at a four-to-eight-percent discount against the three-year term; a seven-year term typically prices at a further three-to-five-percent discount against the five-year term. The longer term carries the lower per-FUE price but the higher commitment risk: the buyer is committed to the SAP-hosted architecture for the term length and the exit cost is the contracted termination-for-convenience clause (often a substantial termination fee or no early termination right at all).
The buyer-side optionality is the term-length-versus-price-per-FUE trade-off and the early-termination right. The negotiating posture varies: a buyer with a strong BATNA (the third-party-support BATNA, the deferred-conversion BATNA or the lift-and-shift BATNA) may elect a three-year term to retain the renewal optionality; a buyer with no credible BATNA may elect the five-year term to capture the price discount.
The hyperscaler-pass-through line is the embedded infrastructure cost. The RISE contract includes the AWS, Azure or Google Cloud infrastructure that hosts the S/4HANA Cloud Private Edition: the infrastructure is procured by SAP from the hyperscaler under the SAP-side hyperscaler agreement, and passed through to the buyer inside the RISE contract. The hyperscaler price itself is not negotiable as a price (it is the hyperscaler's price; SAP procures at its negotiated rate; the buyer cannot directly access the hyperscaler-side procurement). The RISE-side margin on top of the hyperscaler price is negotiable: the typical RISE-side margin on the embedded infrastructure runs at fifteen to twenty-five percent above the published hyperscaler list price.
The renewal-time read of the line is the cost-stack reconciliation: the hyperscaler-side published list price, the SAP-side procurement discount (which the buyer cannot directly access but can read against published benchmarks), the RISE-side margin against the cost line. The wider SAP hyperscaler choice spoke reads the hyperscaler-selection question (AWS, Azure or Google Cloud) inside the RISE contract.
The ramp-up versus run-rate disposition is the structural pricing model. The original RISE contract typically carries a ramp-up curve: the price-per-FUE in year one is lower than the price-per-FUE in years three and four (the run-rate years). The ramp-up curve is designed to ease the initial spend (the buyer's first-year RISE bill is lower than the corresponding on-prem maintenance plus hyperscaler infrastructure cost would have been) and to set the renewal-time price floor at the run-rate level (the buyer renews against the higher run-rate price level, not against the lower ramp-up price level).
The buyer-side discipline reads the ramp-up-versus-run-rate curve at adoption against the renewal-time price level. The discipline runs three readings: the original ramp-up curve (the price-per-FUE in each year of the original term), the run-rate price level (the price-per-FUE in the final year of the original term), and the published renewal-price level (the price-per-FUE in the first year of the renewal term). The publisher-side default is the renewal-price-equals-the-run-rate position; the buyer-side counter is the renewal-price-equals-a-blended-position-of-record. The wider SAP BATNA spoke reads the BATNA leverage on the renewal-price negotiation.
At the close of the RISE renewal cycle, the buyer is in one of four published positions. The first is the renew-at-run-rate position: the buyer renews against the run-rate price level, with the contracted FUE inventory carried forward against the rehearsed renewal-time FUE reconciliation. The second is the renew-with-adjustment position: the buyer renews against an adjusted price level (a buyer-side concession achieved through the FUE reconciliation, the term-length lever or the hyperscaler-margin reading). The third is the partial-extension position: the buyer extends the existing RISE contract on a shorter bridge (typically twelve to twenty-four months) while running the broader renewal-or-exit work in parallel. The fourth is the RISE-to-on-prem reversion position: the buyer terminates the RISE contract at the end of the term and reverts to the on-prem licensing position.
The wider engagement sits in the SAP practice; the aggregated reading list sits in the SAP knowledge hub; active renewal moments route to the Renewal Programme; active audit moments route to Audit Defence.
A senior Admodum SAP advisor will read your FUE reconciliation, your subscription-term options, your hyperscaler-pass-through margin and your ramp-up-versus-run-rate disposition on a private call. Active renewal moments route to the Renewal Programme.