Why SAP's Cloud Licensing Is Complicated
SAP built its commercial model over four decades. The on-premise perpetual licence framework, with its named user categories and package-based engine licences, was designed in an era when software ran on hardware you owned. Cloud changed the economics — recurring subscription revenue, consumption-based billing, and bundled services — but SAP did not replace its legacy model. It added cloud models on top of it. The result is a licensing landscape where the same customer can simultaneously hold perpetual on-premise licences, cloud subscriptions, BTP credit agreements, and standalone SaaS contracts, all governed by different commercial terms and measured by different metrics.
This complexity serves SAP commercially. It is very difficult to compare the total cost of your current position against alternatives when the metrics are incommensurable. A buyer who does not understand the model cannot negotiate it effectively. The purpose of this article is to give procurement and IT leaders a clear map of the principal cloud licensing models, what each includes and excludes, and where the commercial risk sits in each.
RISE with SAP: The Enterprise Cloud ERP Bundle
RISE with SAP is SAP's primary commercial vehicle for large enterprises moving from on-premise ECC to cloud-based S/4HANA. It is a subscription bundle — not a licence type — that packages together S/4HANA Cloud (either public or private edition), a defined allocation of BTP credits, SAP Business Network access, and infrastructure services from SAP or a hyperscaler partner.
The pricing metric for RISE is Full User Equivalents (FUE) — a simplified metric that aggregates different named user types into a single number. A full Professional user counts as 1.0 FUE; a limited-function user might count as 0.2 FUE. FUE simplifies the user count negotiation compared to the legacy model's multiple named user categories, but it also allows SAP to claim a higher total user count by including light-touch access patterns that would not have triggered licence fees under the old model.
RISE includes two tiers: Base and Premium. Base covers core S/4HANA Cloud public or private edition, a starter BTP credit allocation, and SAP Business Network Starter Pack. Premium adds SAP Signavio (process analysis), more BTP credits, and additional transformation tools. In July 2025, SAP retired the Premium Plus tier and unbundled the capabilities that had sat within it — most significantly, advanced Joule AI features and certain sustainability and analytics tools. These now require separate add-on purchases that consume BTP credits or carry standalone subscription fees.
The fact SAP's sales team rarely volunteers: the BTP credits included in a standard RISE Base subscription are typically insufficient for any meaningful custom extension programme. The starter allocation covers infrastructure baseline consumption and perhaps a small number of integration flows — it is not sized for a real Clean Core migration programme where customisations move from the ERP core onto BTP. Customers routinely discover in year one or two that they need a separate BTPEA at additional cost, over and above their RISE subscription.
GROW with SAP: Cloud ERP for Mid-Market and Greenfield
GROW with SAP targets smaller organisations and greenfield deployments — organisations that do not have a legacy on-premise estate to migrate and want a standardised, best-practice S/4HANA Cloud public edition implementation. GROW is always public cloud only; private cloud is not an option, and significant customisation is explicitly outside scope.
GROW is priced more transparently than RISE, offered in predefined Base and Premium editions with clearer feature differentiation. The implementation model is "fit-to-standard" — you configure SAP's best-practice processes rather than implementing custom workflows. This reduces implementation cost and timeline significantly compared to RISE, but it also means organisations that require industry-specific functionality or complex integrations may outgrow GROW quickly.
Commercially, GROW deals are less negotiable than RISE deals. The reduced complexity and standardised scope mean SAP has less discretionary margin to offer. However, for organisations genuinely suited to the model — mid-market businesses without extensive legacy integration requirements — GROW provides a competitive total cost of ownership that is materially lower than a full RISE implementation.
Standalone Cloud Subscriptions: SuccessFactors, Ariba, Concur
SAP's cloud portfolio extends well beyond ERP. SuccessFactors (HR), Ariba (procurement), and Concur (travel and expense) are each governed by their own subscription models with distinct pricing metrics.
SuccessFactors is priced on a per-employee-per-month (PEPM) basis, applied across your total employee headcount for modules licensed. PEPM rates vary significantly by module, tier, and contract volume — full HCM suites for a 10,000-employee enterprise carry different effective rates than point solutions for a 500-employee organisation. The total SuccessFactors cost for a large enterprise running Core HR, Talent, and Workforce Analytics can exceed the cost of the core S/4HANA ERP subscription.
Ariba uses a transaction-based model for its Network (Ariba Network fees apply per invoice or purchase order processed through the platform) alongside subscription fees for procurement applications. The combination of application fees and network transaction fees means the total Ariba cost is often 30–50% higher than what was modelled during initial procurement.
Concur charges per expense report submitted and per travel booking transaction rather than purely per seat. For organisations with high per-employee submission rates, converting to a flat-rate enterprise model at renewal typically reduces cost — but only if the negotiation is anchored to 12 months of actual transaction data rather than SAP's per-report rate card.
BTP Credit Models: BTPEA and PAYG
SAP Business Technology Platform sits beneath all of SAP's cloud products as the integration, extension, and data layer. BTP is licensed separately from both RISE and standalone cloud modules, through one of two commercial models: BTPEA (BTP Enterprise Agreement, successor to CPEA) or Pay-As-You-Go (PAYG).
BTPEA involves an annual prepaid credit commitment, converted into a pool of cloud credits that can be consumed across 90+ BTP services. Discounts of 25–40% versus PAYG list price are achievable at meaningful commitment volumes. The critical risk — as covered in detail in our BTP credit management guide — is that unused credits expire at year-end with no automatic rollover. Approximately 25% of all BTP credits purchased in 2025 went unconsumed.
PAYG offers maximum flexibility at maximum cost — list price, billed monthly, with no commitment. For most production SAP workloads, PAYG is the wrong model. The per-unit economics only make sense for experimental workloads or very low, unpredictable consumption patterns.
The 2025 Packaging Changes and Their Commercial Impact
SAP's mid-2025 packaging changes affected every enterprise running RISE. The retirement of Premium Plus and the unbundling of AI and advanced analytics capabilities from the base tiers created a direct cost increase for any customer who had been relying on those capabilities under their existing subscription. The new pricing model requires separate add-on purchases for Joule's advanced AI skills, SAP Datasphere, and certain sustainability reporting tools.
For customers renewing RISE agreements after July 2025, the commercial conversation has shifted. Previously, Premium Plus provided an all-in subscription that absorbed most AI and analytics costs. Now, the equivalent capability requires a Premium subscription plus multiple add-ons. The effective all-in cost for customers seeking the same functionality is typically 15–25% higher under the new model than under the retired Premium Plus tier.
The migration credit dynamic compounds this. SAP's migration credits — applied against new RISE or S/4HANA subscriptions for customers converting from on-premise perpetual licences — decline at approximately 10% per year. A customer who converts in 2025 receives meaningfully more credit offset against their first-year subscription cost than the same customer who waits until 2027. SAP's Q4 (July–September) remains the best window for both negotiating this credit and securing the largest discretionary discounts on the new subscription.
Not sure which SAP cloud model fits your estate?
We model total cost of ownership across RISE, GROW, and hybrid approaches and identify the commercial position that minimises long-term SAP spend.How to Compare Models Objectively
SAP's sales team will present a commercial comparison using SAP's preferred metrics and SAP's assumptions about your growth trajectory. That comparison will almost always favour the model SAP is currently selling. The independent comparison requires different inputs: your actual current licence entitlements and their maintenance cost, your realistic five-year user growth by access type, your integration landscape and the Digital Access exposure it creates, and your implementation readiness and timeline.
The total cost of a cloud transition is almost always higher in years one and three than SAP's initial modelling suggests. The drivers are predictable: BTP credits beyond the RISE allocation, add-ons to replace unbundled capabilities, higher-than-modelled user counts as access patterns broaden in cloud, and implementation partner costs that exceed the original project scope estimate. Organisations that build their own financial model — rather than relying on SAP's — consistently negotiate better commercial terms and experience fewer surprises in year two.
Our SAP commercial advisory team has advised on more than 80 SAP cloud transitions. The pattern is consistent: buyers who invest in independent modelling before the commercial conversation starts save between 15% and 35% on the total contract value compared to those who do not. The complexity of SAP's cloud licensing is not accidental — it is commercial strategy. The mitigation is information.