SAP License Audits Contact Us
Home · Journal · RISE Contracts · Cloud credit roll-over

What the RISE contract says about credit roll-over

Cloud credits and BTP allowances sit in a category of the RISE contract that most buyers do not read carefully and most lawyers do not negotiate. The default position is forfeiture. The negotiated position is rarely better than partial roll-over. Both are knowable in advance.

Published 2026-05-26By The SAPLicenseAudits Editorial Desk9 min readRISE cluster
Cloudscape at sunrise with sun breaking through layered cumulus

RISE contracts present a composite economic offer: the S/4HANA Cloud subscription, the hyperscaler infrastructure, the technical managed-service component, and a quantum of cloud credits or Business Technology Platform allowances that sit alongside the subscription. The credits and allowances are typically presented as a benefit of the package, valued at list price, and intended to consume during the contract term. In practice the unused balance is forfeited at term end or at anniversary date unless the contract has been negotiated to provide otherwise. The economic significance of the forfeiture clause is, in our experience, frequently larger than the negotiated discount on the subscription itself. The full advisory frame is covered in our contract negotiation service.

The standard position

The standard RISE order form treats credits as use-or-lose. Unused balances expire at the end of each contract anniversary or, in some templates, at the end of the contract term as a whole. The forfeiture is contractual; there is no automatic refund, no automatic conversion to subscription, and no automatic carry forward. The clauses governing the forfeiture are typically in the order form schedule or in the supplementary terms attached to the RISE contract, and are rarely flagged during the commercial conversation.

The commercial dynamic

SAP’s commercial team is incentivised against subscription gross margin and against credit-package attach rate. The credit attach is positive for SAP because it sells additional product at near-zero marginal cost, increases the apparent total contract value, and removes residual elasticity from the renewal. The buyer’s economic interest is the opposite. A credit package that the buyer cannot consume is paid for at list and forfeited at term end. The dynamic produces a systematic over-allocation of credits at the contract signing.

Unused cloud credits and BTP allowances are, in aggregate, one of the largest categories of paid-for-but-unused SAP spend in our practice. The number is rarely tracked by the buyer because the consumption metric is not the same as the procurement metric.

The negotiation levers

Three negotiation levers can move the standard position. None is volunteered; each requires explicit negotiation and explicit drafting.

Lever one — right-sized allowance

The strongest lever is to size the credit allowance to documented consumption forecasts rather than to accept the proposal’s default. The forecast should be evidenced by the planned workload, the technical readiness, and the consumption rate of similar deployments. A right-sized allowance produces a lower contract value but a higher utilisation rate, which is the buyer’s economic interest.

Lever two — intra-term roll-over

Where the allowance must remain larger than the early-year consumption profile, an intra-term roll-over clause permits unused balances to carry forward to subsequent years within the same contract term. The clause does not extend the credit life beyond the contract end, but it absorbs the consumption ramp-up. The standard SAP position resists this clause; the negotiated position is achievable on a meaningful proportion of contracts.

Lever three — conversion to subscription

The third lever is the right to convert unused credit balances into permanent subscription entitlement at a pre-agreed conversion ratio. The clause requires careful drafting because the conversion ratio is the economic substance: an unfavourable ratio turns the clause into a notional benefit. The conversion right is generally available only on larger contracts and only when negotiated against the closing position of the commercial cycle.

The BTP distinction

Business Technology Platform allowances follow a parallel structure to cloud credits but have a separate consumption metric and a separate roll-over treatment. The BTP allowance is governed by the Cloud Platform Enterprise Agreement schedule rather than the RISE schedule, and the two schedules use different forfeiture defaults. Estates with both should ensure that the negotiation positions are aligned. See the RISE pricing model article for the surrounding pricing mechanics and the RISE topic page for the full schedule structure.

The operational implication

A right-sized and rolled-over credit allowance creates an operational obligation: the consumption rate must be monitored against the forecast, deviations must be addressed before the anniversary, and the negotiated roll-over clause must be actively invoked rather than passively relied on. Estates that secure the negotiated clause but fail to operate the monitoring find the clause never engaged and the benefit never realised. The RISE T-shirt sizing article covers the related capacity-monitoring discipline.

The renewal position

The credit consumption history is the principal evidence at the next renewal. Estates that have under-consumed the allowance will face a proposal to retain the original size with a roll-over offer that monetises the under-consumption to SAP’s account. Estates that have over-consumed will face uplift purchases at the unprotected rate. Both positions are weak relative to a documented consumption history with a right-sized allowance. The contract negotiation pillar covers the renewal mechanics and the manufacturing RISE renewal case file illustrates the consumption-history negotiation in practice.

— 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

Estates that have signed a RISE contract within the last twelve months should review the credit and BTP schedules against the consumption rate to date. Estates approaching a RISE signature should size the allowance against a documented forecast rather than accept the proposal’s default. The RISE negotiation playbook contains the clause drafts and forecast templates. Across our 500+ engagements, the credit and BTP allowance work has contributed materially to the $180M+ in aggregate savings the practice has delivered.

An audit notification is not an invoice.

It is the opening position of a negotiation. Speak with a specialist before responding. The first conversation is at no cost and under privilege.

Contact Us →
— Subscribe

SAP Audit Alerts · The weekly briefing

Every Wednesday. Field reports from active matters, decoded SAP communications, and what to look for in the next audit cycle. Work email only.