RISE pricing and the cloud-credit unit

The RISE with SAP bundle restructures every commercial element of an SAP relationship: the licensing model, the infrastructure, the support tier, the renewal cycle, the upgrade cadence, and the audit posture all move under a single subscription contract priced in cloud credits. The mechanics are unfamiliar to procurement teams whose history is in on-premise ECC, and the differences are easy to under-read at signing. This article walks through the cloud-credit unit, the tier structure, the price-protection mechanics, and the buyer-side positions that have closed in our negotiations.

What a cloud credit is

The RISE pricing model expresses consumption as a quantity of cloud credits applied against a monthly or annual entitlement. Each licensed component — users by category, S/4HANA tenant size, integration suite throughput, Digital Access document volume — carries a credit conversion factor in the order form. The conversion factor is the unit price the buyer pays. The negotiation is rarely about the credit count, which is determined by the actual consumption; it is almost always about the conversion factor, the duration over which it is fixed, and the rebate mechanic when consumption falls below the contracted entitlement.

The tier structure

RISE entitlements are tiered: the conversion factor decreases as the contracted volume increases. The tiers are defined by SAP and, in negotiated agreements, are sometimes layered with additional discount bands for committed-spend thresholds. The buyer-side discipline is to negotiate placement at the tier that includes a defined headroom above the current consumption, with the conversion factor fixed for the contract term. Without the fixed-factor clause, the volume-banded mechanic can ratchet the per-credit price up as the buyer’s consumption crosses into a higher band — an outcome that no buyer would accept if it were stated plainly. The RISE negotiation tactics white paper documents the tier benchmarks across our engagements.

The headroom calculation

Headroom for a RISE contract is sized on a different basis from a traditional licence contract. The relevant inputs are the integration roadmap, the projected S/4HANA tenant growth, the named-user growth, and any planned Digital Access expansion. For an estate with a stable footprint, twenty to thirty per cent headroom is usually sufficient. For an estate in an active migration, the figure rises to forty or fifty per cent. The cost of headroom is the unused entitlement; the cost of being short is the on-demand premium, which is typically two to three times the contracted rate. The arithmetic favours headroom in most cases.

The price-protection mechanics

The standard RISE order form prices the contract for the initial term and applies an annual escalation to the renewal price. The escalation is typically tied to an SAP-published index or a defined percentage. The buyer-side position is to negotiate the escalation down to a cap of two to four per cent per year, with a floor of zero, and to apply it to the renewal-term price rather than the in-term price. The cap protects the buyer from the indexation surprise that has hit some early RISE customers as the SAP-published index moved.

A second price-protection mechanic is the most-favoured-nation clause, which entitles the buyer to the lowest conversion factor offered to a peer customer of comparable size in the contract year. The clause is rarely conceded but is sometimes substituted with a more limited ‘market-rate review’ clause that triggers a renegotiation if SAP’s published list-price benchmark moves materially. Either form provides a defensive floor on price erosion. The price benchmarks article covers the broader pricing landscape.

The true-up and true-down mechanics

The standard RISE true-up clause is upward-only: if consumption exceeds the contracted entitlement, the buyer pays the on-demand premium on the overage. The buyer-side position is that the true-up should be bilateral — if consumption falls below the contracted entitlement, the contract steps down to the lower tier at the corresponding conversion factor. The bilateral clause is one of the most consequential single edits in the order form because the standard upward-only language imposes a one-way ratchet that locks the buyer into volumes that may never recur. The audit clauses article covers the broader floor-and-cap structure.

The rollover mechanic

Unused credits in a contract year are, under the standard RISE order form, forfeit at year-end. The buyer-side position is to negotiate a rollover clause that permits a defined proportion of unused credits — typically twenty to forty per cent — to roll into the following year. The clause is sometimes conceded outright and sometimes conceded with a defined cap on cumulative rollover across the term. Either form materially improves the buyer’s economic exposure to the headroom calculation, because under-consumption is no longer pure forfeit.

The service-level credits

The RISE service-level schedule defines availability targets for the hosted S/4HANA tenant and the connected services. Where the targets are missed, the standard remedy is a service credit applied against the next billing cycle. The buyer-side position is to ensure that the credit is meaningful in proportion to the impact, that the measurement window is short enough to capture incidents, and that the cap on cumulative credits is high enough that a chronic underperformance does not bottom out the remedy. The clauses are negotiable and are routinely under-attended at signing. The RISE topic page covers the broader operational profile.

The conversion-from-perpetual mechanic

For buyers converting from a perpetual ECC licence to a RISE subscription, the order form should carry a defined credit for the existing perpetual entitlement against the RISE conversion factor. The credit is sometimes structured as a one-time discount, sometimes as a reduction in the contracted credit count, and sometimes as a defined term-extension at the contracted price. The form matters less than the substance: the perpetual investment should be reflected in the RISE economics or the conversion is not commercially rational. The bank-renegotiates-RISE case file documents one such conversion in full.

What to negotiate alongside the credits

RISE is rarely a standalone negotiation. The negotiation should pull three additional levers alongside the credit pricing. The exit terms — the data-egress charges, the migration assistance, and the conversion-back-to-perpetual options — should be defined upfront, because the cost of negotiating them mid-term is materially higher than the cost of writing them in at signing. The Digital Access entitlement, which is often bundled inside the RISE order form, should be negotiated against the buyer-side baseline rather than the SAP-supplied estimate; the methodology is described in the baseline measurement article. And the audit-rights and data-residency clauses should be reviewed for jurisdictional compatibility with the buyer’s operating geography.

The contract negotiation service page describes how we run a full RISE engagement, and the RISE conversion tactics article covers the conversion-specific patterns. The work, end to end, takes six to twelve weeks per contract event. The recurring savings sit in the seven-figure range for any meaningful enterprise estate.

The renewal-cycle implications

A RISE contract restructures the renewal cycle of the SAP relationship. Where the legacy perpetual-and-maintenance model spread the negotiation across a recurring maintenance event and a periodic capital-investment event, the RISE subscription concentrates the leverage moment at a single annual renewal point. The procurement function should treat that concentration as a planning opportunity: the data room, the consumption measurement, the conversion-factor benchmark, and the leverage instruments should all be lined up for the renewal window with months of preparation rather than weeks. The cumulative effect, across a three-year horizon, is a renewal cycle that closes on the buyer’s preferred economics rather than SAP’s template defaults. The procurement function that does not run the preparation in advance is, in effect, signing the template default.

The RISE topic page covers the broader operational profile, and the bank-renegotiates case file documents one engagement where a mid-term renegotiation closed materially better economics than the original signing.