RISE with SAP vs Traditional On-Premise Licensing

The Two Cost Models: Structure and Logic

Traditional on-premise SAP licensing is built on a capital expenditure model. The enterprise purchases perpetual software licences — an upfront payment that grants the right to use the software indefinitely — and then pays annual maintenance (typically 22 percent of the net licence value) for support, security patches, and legal updates. The perpetual licence itself is an asset on the balance sheet. The 22 percent maintenance fee is an operating expense that scales with the contracted licence value, not with actual usage.

RISE with SAP converts this model to a subscription basis. There is no upfront licence purchase. Instead, the organisation pays an annual subscription fee denominated in FUEs (Full Use Equivalents) that encompasses the S/4HANA software licence, infrastructure hosting, and SAP Enterprise Support. The subscription is a pure operating expense — no balance sheet asset, no depreciation — which is a structural advantage for organisations managing capital allocation constraints or seeking to optimise operating cost ratios.

The S/4HANA Baseline Reset

A comparison that ignores the baseline reset understates the complexity of the transition. On-premise SAP ECC licences are priced on Named User and engine metrics that differ significantly from S/4HANA's FUE metric. The migration to RISE is not simply a conversion of existing licences to a subscription price — it is a renegotiation of the entire licensing baseline under a new metric framework. SAP constructs the initial FUE baseline through a mapping exercise that is, in almost every case, weighted in SAP's commercial favour. Independent analysis of the FUE baseline is not optional — it is the single most important step in any RISE commercial evaluation.

Short-Term vs. Long-Term: Where Each Model Wins

The TCO comparison between RISE and on-premise is not a single calculation — it is a time-horizon-dependent analysis where the outcome reverses between Year 3 and Year 7 depending on several variables.

Years 1 to 3: RISE Typically Wins

In the first three years after a decision is made, RISE with SAP typically delivers lower total cost than a new on-premise investment. The absence of upfront licence capital expenditure, combined with the inclusion of infrastructure costs within the subscription, means the Year 1 cash outflow is substantially lower under RISE. An enterprise facing a €15 million to €25 million on-premise S/4HANA licence investment avoids that capital requirement under RISE, which is a material advantage for the CFO and for any organisation with constrained capital budgets. SAP's advertised 20 percent TCO reduction primarily applies to this short-term window.

The migration credit structure reinforces the short-term advantage. Enterprises migrating from ECC can receive credits of 45 to 60 percent of their first-year RISE subscription fees (at 2025 to 2026 rates), applied against the initial subscription cost. This reduces the Year 1 RISE outlay significantly and distorts the short-term comparison in RISE's favour.

Years 4 to 7: The Crossover Zone

As the cumulative RISE subscription cost accumulates over years four to seven, the comparison shifts. An on-premise organisation that completed its S/4HANA implementation and is running at steady state — depreciated licence assets, known maintenance at 22 percent — begins to show lower annual total cost than an equivalent RISE subscription. This is the TCO crossover point: the moment at which the cumulative RISE cost exceeds the cumulative on-premise cost for an equivalent capability footprint.

Industry analysis places the crossover typically between Year 4 and Year 7, depending on the negotiated RISE subscription rate, the organisation's infrastructure costs, and the degree to which on-premise hardware assets have been fully depreciated. Organisations that already own and operate SAP on mature, depreciated infrastructure are most likely to find that RISE is more expensive over this horizon.

What SAP's TCO Comparisons Routinely Omit

SAP's sales teams present TCO comparisons that systematically favour RISE by controlling which costs are included in each model. An independent buyer must understand and challenge these omissions.

Implementation Costs

Neither RISE nor on-premise S/4HANA eliminates the implementation programme. Both require technical migration, data cleansing, process redesign, testing, and change management. For a 2,000-FUE enterprise, implementation costs typically range from €3 million to €12 million depending on complexity. SAP's TCO models for RISE often reference the SAP-provided transformation services included in the RISE bundle — but these services cover programme governance and methodology support, not the systems integration and custom development work that accounts for the majority of implementation spend. Counting only the included RISE transformation services while applying the full implementation cost to the on-premise scenario is a material distortion.

BTP Consumption Costs

RISE with SAP includes a starter BTP credit allocation. Production integration environments routinely consume BTP credits beyond the included allocation within 12 to 18 months of go-live. BTP overage is billed at list prices that are 2 to 3 times the rate achievable through committed volume purchase. The incremental BTP cost is rarely included in SAP's RISE TCO model but represents a real annual cost that materialises post go-live.

DDLC Exposure

The Digital Documents Licence Charge (DDLC) is the metric through which SAP monetises indirect access in S/4HANA and RISE environments. Every business document — sales order, purchase order, invoice, delivery — processed via a non-named-user interface (a third-party system, a portal, an EDI gateway) counts towards DDLC. DDLC charges are not included in the headline RISE FUE subscription price; they are a separate licence dimension that requires a dedicated allocation. Organisations with high transaction volumes and complex integration landscapes face material DDLC exposure that does not appear in standard RISE TCO comparisons.

SuccessFactors and Other Cloud Modules

RISE with SAP covers S/4HANA Cloud Private Edition. It does not include SAP SuccessFactors (HR and HCM), SAP Ariba (procurement), SAP Concur (travel and expense), or SAP Analytics Cloud at production scale. These modules are sold under separate subscription models — SuccessFactors on PEPM (Per Employee Per Month) pricing, Ariba on transaction-volume pricing, Concur on per-user pricing. An enterprise running the full SAP suite will find that the RISE subscription covers only a portion of total SAP costs. The total SAP landscape cost — including cloud HCM, procurement, and analytics — is substantially higher than the RISE headline figure.

Where On-Premise Retains Advantages

The traditional on-premise model retains specific advantages that RISE does not replicate, particularly for organisations with distinctive characteristics.

Fully depreciated estate. Organisations that implemented SAP 10 to 15 years ago and have fully depreciated their licence assets are paying only the 22 percent annual maintenance fee — approximately €3 million to €5 million per year for a mid-sized enterprise. Their annual total cost of ownership is dramatically lower than the RISE subscription for equivalent scope. For these organisations, the financial case for RISE is difficult to make before the 2027 ECC maintenance deadline creates pressure.

Contractual ownership and exit rights. Perpetual licences are owned assets. An enterprise running on-premise S/4HANA retains its software even if its relationship with SAP deteriorates. Under RISE, the subscription can theoretically be terminated — with consequences for software access that do not exist under perpetual licensing.

Predictable cost trajectory. On-premise maintenance at 22 percent is a known, fixed cost that escalates predictably. RISE subscription costs include renewal escalation clauses that can compound over a five-year term. Organisations should model RISE renewal rates, not just initial year pricing, when comparing the models.

Making the Decision: A Framework

The right model depends on five factors that interact differently for every organisation. Assess each honestly before committing.

Capital constraint and balance sheet position. If the organisation faces capital constraints or preference for OpEx over CapEx, RISE wins structurally. The perpetual licence investment does not materialise, and the subscription cost is fully expensed in the year incurred.

Existing infrastructure depreciation status. If SAP runs on infrastructure that is substantially depreciated and well-managed, the TCO advantage of RISE is reduced and the crossover point extends. Model the on-premise TCO using actual, not theoretical, infrastructure costs.

Integration complexity and DDLC exposure. High transaction volumes and extensive third-party integrations increase DDLC exposure and BTP consumption costs under RISE. These costs require independent modelling before the comparison is valid.

Customisation requirements. Extensive ABAP custom code does not preclude RISE (private cloud allows it) but does increase implementation complexity and cost. Model the implementation premium for a custom-code-heavy estate before accepting RISE's time-to-value narrative.

The 2027 deadline context. For organisations on ECC EHP 6 to 8, mainstream maintenance ends in December 2027. The deadline creates real commercial pressure but should not override the financial analysis. Third-party maintenance options and SAP's extended maintenance programme provide alternatives that remove the urgency SAP applies to accelerate RISE adoption.