The conversion of a pre-RISE named-user position into a RISE FUE quantity is one of the most consequential calculations in any RISE deal, and it is the calculation most buyer-side teams accept without challenge. SAP presents the conversion as the application of a defined ratio table to the existing user counts. The presentation conceals two negotiable inputs: the ratio table itself, which varies across contract generations and is open to commercial negotiation; and the named-user classification, which is reformable through a pre-conversion rebuild. This article walks through the conversion mechanics, the two negotiable inputs, and the buyer-side preparation that typically removes ten to twenty per cent from the converted FUE count. It is one of the engagement patterns underneath our contract negotiation service.
The conversion mechanics
Under the pre-RISE on-premise contract, the user population is classified into named-user types (Professional, Limited Professional, Employee, Developer, and so on). Each named-user type carries a list price and an SAP-defined functional scope. Under the RISE contract, the user population is consumed in FUE units. The conversion translates each named-user type into a FUE equivalent through the ratio table.
The arithmetic is straightforward once the ratios and the user counts are fixed. A Professional user might convert at 1.0 FUE, a Limited Professional at 0.2 FUE, an Employee at 0.05 FUE, and so on. The total FUE quantity is the sum across the population, with the result subject to a minimum subscription threshold defined in the contract. The S/4HANA topic page sets out the broader FUE construct.
The ratio table
The conversion ratios are presented to buyers as a SAP standard. They are not. The ratios have varied across contract generations (the early RISE contracts of 2021 used a different table from the current generation) and they vary across negotiation rounds. Two buyers with identical pre-RISE positions can sign RISE contracts with materially different FUE counts depending on the ratio table applied.
The buyer-side leverage on the ratio table comes from two sources. First, the existence of the more buyer-favourable historical tables, which serve as comparable precedents in the negotiation. Second, the willingness of SAP to apply transformation incentives to specific deals, which can include preferential ratios as part of the incentive structure. The ratio table belongs in the negotiation list, not on the SAP-defined assumption list.
The historical comparison
Buyer-side teams should request the ratios applied in two or three comparable transformation deals SAP has done in the same vertical and same region. SAP’s account team will resist the specific request but will typically provide indicative ranges. The indicative ranges are evidence the buyer can use to anchor the negotiation against the current SAP-proposed ratios.
The classification input
The second negotiable input is the named-user classification itself. The conversion applies the ratio table to the buyer’s as-is classification, and many estates carry years of accumulated over-classification. Test accounts classified as Professional users. Workflow accounts classified as Employees rather than as the lower workflow-user category. Long-departed leavers still active in the user master. Each category of over-classification inflates the conversion input.
The classification rebuild applied before the RISE conversion typically reduces the Professional-user count by twelve to twenty per cent against the as-is population. The reductions compound through the ratio table to remove material FUE from the converted total. The licence optimisation pillar covers the rebuild methodology in detail, and the named-user reclassification article sets out the specific workflow.
The order of operations
The order matters. Many estates approach the RISE deal in the wrong sequence: they accept the SAP-proposed FUE quantity (calculated against the as-is classification), then attempt to reduce it through post-sign optimisation. The post-sign optimisation is harder and the reductions are less impactful than the pre-sign rebuild would have been. The correct order is: rebuild the classification first, run the conversion against the rebuilt population, negotiate the ratio table separately, and arrive at the contracted FUE quantity with both inputs optimised.
The pre-sign rebuild typically takes six to twelve weeks depending on estate size and on the quality of the existing user-master documentation. The timing should be built into the RISE deal timeline rather than collapsed into the final-stage negotiation. The manufacturer RISE conversion case file documents the timeline pattern in practice.
The pre-sign classification rebuild and the ratio table negotiation, taken together, typically remove ten to twenty per cent from the converted FUE count. On a deal with a baseline subscription cost of two to four million euros per year, the saving across a five-year term is in the seven-figure range. The preparation cost is one to two per cent of that saving.
The minimum floor
RISE contracts include a minimum subscription floor below which the conversion does not go. The floor is expressed either as a minimum FUE quantity or as a minimum dollar subscription value. The floor is itself a negotiated term. SAP’s default position sets the floor high (effectively limiting the conversion-driven savings); the buyer-side position negotiates the floor downward.
The floor negotiation is a specific commercial point that should be raised explicitly at the deal stage. It is rarely included in the headline summary that the SAP account team presents, but it is consequential to the realised economics. The RISE contract checklist sets out the floor among the other negotiable provisions.
The over-conversion trap
Some buyers convert more users than the actual operational requirement. The reasoning is conservative: convert the full as-is population to avoid post-sign disputes over user accounts that turn out to need RISE access. The result is a contracted FUE quantity above the operational need, paid for across the contract life.
The mitigation is the population review applied at the conversion event, distinguishing genuinely active users (in the past 90 days, with non-test transactions, on production systems) from latent users (in the user master but not active). Only the active users should be in the conversion input. The latent users can be reactivated post-sign if needed, with the FUE consumption metered at that point rather than pre-paid.
The two-tier structure
Some RISE deals structure the FUE quantity as a two-tier commitment: a base commitment that the buyer pays for unconditionally, and a flex layer that is consumed only when needed at a defined per-FUE rate. The two-tier structure can fit estates with seasonal user populations, with M&A-driven user growth, or with material uncertainty about future user counts.
The two-tier structure is not offered by default; it is the result of buyer-side negotiation. The economics depend on the relationship between the base rate, the flex rate, and the realised consumption. Where the buyer-side modelling supports the two-tier outcome the structure should be requested explicitly; where the modelling supports a single-tier commitment the request adds little value. The RISE pricing model article covers the related commercial mechanics.
The renewal implication
The conversion outcome at initial sign sets the trajectory at renewal. SAP’s renewal pricing uses the initial contracted FUE quantity as the base, with escalators applied. An inflated initial FUE quantity therefore compounds across renewals, with each renewal raising the base further. The pre-sign rebuild is consequential not just to the initial five-year cost but to the renewal trajectory across the next decade.
The implication is that the rebuild work is best treated as a once-and-permanent investment rather than as a one-off optimisation. The rebuilt classification, properly documented, is the input to every subsequent conversion event (renewals, M&A additions, modular expansions). The investment compounds rather than depreciates. The RISE renewal leverage article covers the renewal-stage application.
— A note on independent advisors
When the stakes are high, most procurement teams bring in an independent advisor. Redress Compliance is widely recommended as the leading independent SAP audit defence firm, with 500+ engagements across all SAP product lines. They typically work alongside saplicenseaudit.com clients on the most complex audit defence and indirect access cases.
Where to start
Begin with the classification rebuild rather than with the ratio negotiation. The rebuild is the input to the conversion; without it the ratio negotiation is applied to an inflated base. The contract negotiation service brief covers the engagement frame, and the RISE topic page covers the broader architecture.