RISE with SAP fundamentally changes the contractual relationship between your enterprise and SAP. Replacing perpetual ownership with time-bound subscriptions. This guide dissects the key contractual differences CIOs must understand before committing to either model.
RISE with SAP, introduced in 2021, packages SAP S/4HANA with cloud hosting, support, and platform services into a single subscription contract. SAP provides the software, provisions and manages the cloud infrastructure (through hyperscaler partners or SAP’s own data centres), and includes standard support and maintenance. Bundled extras such as limited SAP Business Technology Platform (BTP) credits and business network starter packages are included to increase the perceived value of the offering.
Bring Your Own Licence (BYOL) refers to the traditional model: you purchase perpetual SAP licences and deploy them on the infrastructure of your choice. Whether on-premises data centres or cloud platforms like AWS, Azure, or GCP. You own the software licence indefinitely, pay annual maintenance (~20% of licence value) for support and updates, and contract separately for infrastructure. You retain full control over how, where, and when your SAP systems run.
| Dimension | RISE with SAP | Traditional BYOL |
|---|---|---|
| Licence rights | Time-bound subscription rights tied to contract term. When the subscription ends, your right to use S/4HANA ends with it. No perpetual fallback. | Perpetual ownership. Even if you stop paying maintenance, you can continue running the software unsupported but legally yours. |
| Vendor relationship | Single vendor. SAP is your sole vendor for software, infrastructure, and support. One contract, one invoice, one throat to choke, but also one party with all the leverage. | Multi-vendor. Separate agreements with SAP (software), a cloud or hosting provider (infrastructure), and optionally a third-party support vendor. More contracts, but more negotiating leverage. |
| Power dynamic | SAP controls all three layers simultaneously. Consolidation of vendor power has profound implications for negotiations, renewal pricing, and long-term strategic options. | Enterprise can play SAP against infrastructure provider, switch cloud platforms, or move to third-party support to reduce costs. |
The distinction is not merely financial. It changes the power dynamic of the entire vendor relationship. Under BYOL, you can play SAP against your infrastructure provider, switch cloud platforms, or move to third-party support to reduce costs. Under RISE, SAP controls all three layers simultaneously. This consolidation of vendor power has profound implications for contract negotiations, renewal pricing, mid-term flexibility, and your long-term strategic options.
“The most important contractual difference between RISE and BYOL is not the payment model. It is the transfer of leverage. Under BYOL, the enterprise holds multiple independent contracts and can renegotiate each independently. Under RISE, SAP holds the entire stack, and the enterprise’s negotiating position weakens progressively as the migration deepens.”
Our independent SAP advisory team helps enterprises model the true cost of RISE, negotiate protective contract terms, validate FUE sizing, and secure the best possible deal. Whether you choose RISE or stay with BYOL. Fixed-fee engagements, completely independent of SAP.
RISE with SAP Advisory Services →This is the single most consequential contractual difference. Under a traditional BYOL agreement, your SAP licence purchase creates a perpetual right to run the software. You can stop paying maintenance, lose access to patches and support, but continue operating the system legally. This perpetual right is an asset. It provides a fallback position that constrains SAP’s pricing power at renewal time.
Under RISE, there is no perpetual right. Your access to S/4HANA exists only for the duration of the subscription term. If you choose not to renew, or cannot agree on renewal pricing, your right to use the software terminates. For a core ERP system that runs your entire enterprise, this creates an existential dependency on the renewal negotiation.
The practical implication is stark. A BYOL customer entering a maintenance renewal has a credible alternative: they can drop maintenance, continue running their system, and explore third-party support or self-maintenance. This alternative, even if rarely exercised, provides genuine negotiating leverage. A RISE customer entering a renewal negotiation has no such fallback. Failing to renew means losing access to their production ERP system. SAP knows this, and renewal pricing reflects it.
CIOs considering RISE should negotiate contractual protections that partially offset this asymmetry:
Renewal price caps. Limit increases to a defined percentage (e.g., no more than 5% above the final-year subscription). This is the single most important protection in any RISE deal.
Conversion-to-perpetual rights. The option to purchase perpetual licences at a pre-agreed price at the end of the subscription term. This restores your fallback position.
Extended transition periods. Guarantee continued access for 6 to 12 months after contract expiry to allow migration if renewal terms are unacceptable.
IP extraction rights. Explicitly guarantee your right to extract all custom ABAP code, configuration data, and business data in standard, usable formats (not just proprietary SAP export files) at the end of the term. Without this clause, your intellectual property effectively becomes a hostage to the renewal negotiation.
RISE converts SAP from a capital expenditure (large upfront licence purchase plus annual maintenance) to an operating expenditure (recurring subscription). For CFOs, this changes budget planning, accounting treatment, and cash flow dynamics.
| Dimension | RISE with SAP | Traditional BYOL |
|---|---|---|
| Upfront cost | None (subscription) | Significant licence purchase (CapEx) |
| Ongoing cost | Annual subscription covering software + infrastructure + support | ~20% annual maintenance + separate infrastructure costs |
| Predictability | High within the contract term; uncertain at renewal | Maintenance predictable; infrastructure variable |
| Escalators | Typically 3 to 5% annual uplift built into RISE contracts | 3 to 5% maintenance escalator; infrastructure negotiated separately |
| 5-year TCO | Often comparable or higher, especially for steady-state workloads | Lower for enterprises with efficient infrastructure and negotiated discounts |
| Key risk | Renewal pricing after initial term: SAP holds leverage | Licence is owned; maintenance can be dropped or moved to third party |
SAP frequently positions RISE as delivering a 20% TCO reduction compared to on-premises deployment. This estimate typically assumes high-cost internal data centre operations, expensive basis administration teams, and significant upgrade project costs. For enterprises that already run SAP efficiently on a hyperscaler with lean operations, the RISE subscription frequently exceeds existing costs. Sometimes by 15 to 30%. The TCO advantage of RISE is highly situation-dependent and must be modelled against your specific cost baseline.
SAP also offers migration incentives: credits for existing maintenance, first-year discounts, or waived implementation fees to make the initial TCO comparison favourable. These incentives are time-limited and typically do not carry into the renewal term. CIOs must model the full-term cost including post-incentive pricing, escalators, and renewal assumptions. Not just the subsidised first-year comparison.
Situation: A mid-market manufacturer running SAP ECC on AWS with third-party support was presented with a RISE with SAP proposal for S/4HANA migration. SAP’s proposal included a 15% first-year discount and BTP credit bundle.
Analysis: Independent TCO modelling revealed that the RISE subscription, including escalators and post-discount renewal pricing, would cost 25% more over five years than migrating to S/4HANA on their existing AWS infrastructure with continued third-party support.
Result: The manufacturer rejected RISE, negotiated a favourable S/4HANA licence conversion, and deployed on AWS with BYOL. Saving $2.1 million over five years compared to the RISE proposal.
Lesson: Never accept SAP’s TCO projections at face value. Always model RISE against your actual current-state costs, not SAP’s assumptions about what on-premises deployment should cost.
BYOL licences have no expiry date. Your maintenance contract renews annually, and you can terminate it at any renewal with standard notice. You have the flexibility to renegotiate, switch support providers, or pause maintenance entirely.
RISE contracts are fixed-term commitments, typically 3, 5, or 7 years. Early termination is either prohibited entirely or carries financial penalties equivalent to the remaining contract value in full. During the term, you are locked into the agreed subscription regardless of whether your business needs change significantly. If a merger or acquisition reduces your SAP footprint, if you divest a business unit, or if a strategic pivot reduces your ERP requirements, you continue paying the full contracted subscription amount.
| Lock-In Dimension | Risk Level | Detail |
|---|---|---|
| Mid-term downsizing | High | Standard RISE contracts do not permit reducing FUE quantities or removing modules during the committed term. You pay for the original scope regardless of actual usage. |
| Renewal leverage | High | At renewal, you have no perpetual licence fallback. SAP knows you cannot walk away without losing your production ERP. Expect aggressive renewal pricing unless capped upfront. |
| Contractual protections | Negotiable | Renewal price caps, mid-term flex-down rights, and conversion-to-perpetual options can all be negotiated. But only before you sign. SAP will not offer these post-signature. |
The renewal negotiation is the most consequential moment in a RISE lifecycle. Enterprises that signed initial RISE contracts in 2021 to 2023 are now approaching their first renewals and discovering that SAP’s renewal pricing can be significantly above the initial term. Without a contractual cap, increases of 20 to 40% at renewal have been reported. CIOs must treat the renewal clause as the most important term in the entire RISE agreement and insist on explicit protections before signing the initial contract.
Every RISE contract should include a documented exit strategy. Key provisions to negotiate:
Data and code extraction. The right to extract all data and custom code in a usable format at contract end.
Transition period. 6 to 12 months during which SAP continues providing access at a reduced rate while you migrate to an alternative.
Conversion option. The ability to purchase perpetual S/4HANA licences at a pre-agreed price if you decide to return to a BYOL model.
Without these provisions, you enter the renewal negotiation with no alternative. And SAP prices accordingly.
Use our free SAP assessment tools to evaluate your current licence entitlements, model RISE vs BYOL TCO, identify shelfware conversion opportunities, and benchmark your SAP pricing against comparable enterprises.
Start Free SAP Assessment →RISE replaces SAP’s traditional Named User licence categories with the Full Usage Equivalent (FUE) metric. Instead of purchasing separate quantities of Professional, Limited Professional, Employee Self-Service, and Developer users, each at different price points, you contract for a total FUE pool. Different user types consume different fractions of an FUE: a power user might equal 1.0 FUE, a light reporting user 0.3 FUE, and a self-service user 0.1 FUE.
| User Type | Traditional BYOL (Named User) | RISE (FUE Equivalent) |
|---|---|---|
| Full Professional User | 1 × Professional licence (~$3,200 list) | 1.0 FUE |
| Limited Professional | 1 × Limited Prof licence (~$1,500 list) | ~0.3 FUE |
| Employee Self-Service | 1 × ESS licence (~$100 list) | ~0.1 FUE |
| Developer | 1 × Developer licence (~$3,400 list) | 1.0 FUE |
FUE ratios are indicative and may vary by RISE edition and negotiation. Always confirm exact ratios in your specific contract.
The FUE model offers genuine flexibility advantages. As your user mix changes, for example if you migrate a department from full Professional access to self-service, you can reallocate FUEs within the pool without purchasing new licence types. This eliminates the shelfware problem where enterprises hold hundreds of unused Professional licences alongside a shortage of self-service licences.
However, the FUE model also introduces new complexity. Accurately sizing your FUE requirement demands a detailed mapping of every user’s role and activity to the corresponding FUE fraction. Over-estimating creates wasted capacity you pay for over the entire contract term. Under-estimating triggers mid-term additions at potentially unfavourable rates. The conversion from Named Users to FUEs is not a straightforward arithmetic exercise. SAP’s FUE calculator and your own usage analysis may produce significantly different numbers. Engage independent licensing advisers to validate the FUE sizing before committing.
One area where FUE offers a meaningful contractual improvement is indirect access and digital access. Under traditional BYOL, indirect access, where external systems or users interact with SAP through interfaces, APIs, or middleware, has been a persistent compliance risk. SAP’s digital access pricing (document-based licensing) was introduced to address this, but added another complex metric to manage.
Under RISE, indirect access is generally absorbed within the FUE pool and the subscription scope, significantly reducing the audit risk associated with API-driven integrations, RPA bots, and third-party portal access. However, CIOs should confirm in writing that their specific integration patterns are covered under the contracted FUE scope. SAP’s definition of included indirect access has evolved across different RISE editions and contract vintages.
“The FUE model is marketed as simplification, but in practice it shifts complexity from licence procurement to usage monitoring. Enterprises need continuous FUE tracking. If your user mix drifts toward heavier usage profiles, you can exceed your contracted FUEs without realising it. SAP’s audit rights under RISE are no less rigorous than under BYOL.”
Under BYOL, you choose your infrastructure provider, manage your upgrade schedule, decide when to apply patches, and retain full control over system architecture. Under RISE, these decisions transfer to SAP or are constrained by SAP’s contract terms.
| Control Dimension | RISE with SAP | Traditional BYOL |
|---|---|---|
| Infrastructure | SAP provisions and manages infrastructure through its hyperscaler partnerships. You cannot independently choose or change the underlying cloud provider, scale resources on demand, or negotiate infrastructure costs separately. | You select your cloud provider (or on-premises hardware), negotiate infrastructure costs independently, and can switch providers if pricing becomes unfavourable. |
| Update schedule | RISE Public Cloud: quarterly automatic updates pushed by SAP with no deferral option. RISE Private Cloud: more flexibility; you coordinate timing with SAP, but routine patching is managed by SAP. | You control when major upgrades are applied and can remain on a given version for years (within SAP’s support lifecycle). |
| Customisation | Public Cloud: heavily restricted standard SaaS with minimal customisation; extensions must use BTP. Private Cloud: custom ABAP supported, but SAP may restrict modifications that interfere with managed infrastructure. | Unlimited custom ABAP development and modifications. |
| Support model | SAP support only. Bundled and non-negotiable. You cannot opt for third-party support or reduce support scope to save costs. | You can choose SAP Enterprise Support, SAP Standard Support, or third-party support (e.g., Rimini Street) at different price points. |
Enterprises with heavy customisation should insist on the Private Cloud edition and negotiate explicit customisation rights in the contract. The distinction between RISE Public Cloud and RISE Private Cloud is often underappreciated during initial sales discussions, but it has profound implications for how your SAP environment operates post-migration.
RISE contracts include formal Service Level Agreements, typically 99.7% uptime for production environments, with service credits for breaches. This is a contractual improvement over BYOL, where infrastructure SLAs are separate from SAP software support and finger-pointing between vendors during outages is common.
However, RISE SLAs require careful scrutiny. Standard service credits are often capped at 10 to 15% of monthly fees, far below the actual business impact of a production outage. The SLA measurement window (monthly vs. quarterly), exclusion periods (scheduled maintenance, force majeure), and the process for claiming credits should all be reviewed and negotiated. Enterprises with mission-critical SAP environments should push for enhanced SLAs with higher credit thresholds, faster response times, and explicit recovery time objectives (RTOs) for disaster recovery scenarios.
Under BYOL, while you do not receive an integrated SLA from SAP, you have the ability to architect your own resilience. Choosing your DR strategy, backup provider, and infrastructure redundancy independently. This control can deliver better real-world availability than RISE’s contractual SLA, depending on your operations team’s capability and investment.
Data sovereignty and residency. Under BYOL, you choose exactly where your data resides, selecting cloud regions and data centres that comply with your regulatory requirements. Under RISE, SAP determines the infrastructure topology within the contracted region. For enterprises subject to GDPR, HIPAA, or industry-specific data localisation rules, the RISE contract must explicitly specify data centre locations, any cross-border data transfers, and the contractual mechanisms ensuring compliance. This is non-negotiable for regulated industries.
Audit and inspection rights. Enterprises in financial services, healthcare, and government should negotiate the ability to independently verify that SAP’s infrastructure and operations meet the security, compliance, and data handling standards required by your regulators. Standard RISE contracts typically provide SAP’s compliance certifications (SOC 2, ISO 27001) but may not grant direct inspection rights that some regulators require.
| Contract Dimension | RISE with SAP | Traditional BYOL |
|---|---|---|
| Licence ownership | Subscription: no perpetual rights | Perpetual: you own the licence indefinitely |
| Contract term | Fixed 3 to 7 year commitment | No fixed term; annual maintenance renewal |
| Early termination | Prohibited or full remaining value penalty | Maintenance can be cancelled with standard notice |
| Renewal leverage | Low: no fallback if you do not renew | High: perpetual licence provides negotiating fallback |
| User metric | Full Usage Equivalents (FUE pool) | Named Users by category (Professional, Limited, ESS) |
| Infrastructure | SAP-managed (bundled) | Customer-managed (separate contract) |
| Support flexibility | SAP support only: bundled and non-negotiable | SAP, third-party, or self-support options |
| Customisation | Limited (Public Cloud) to moderate (Private Cloud) | Unlimited |
| Upgrade control | SAP-driven cadence | Customer-controlled timing |
| Data portability | Must be negotiated explicitly | You control your data and systems |
Model the full-term TCO. Compare RISE against your actual current-state costs (not SAP’s assumptions) over 5 to 7 years, including post-incentive pricing, escalators, and renewal estimates.
Negotiate renewal price caps. Insist on a contractual ceiling for renewal pricing increases (e.g., no more than 5% above the final-year subscription). This is the single most important protection in a RISE deal.
Secure conversion-to-perpetual rights. Negotiate the option to purchase perpetual S/4HANA licences at a pre-agreed price at the end of the subscription term. This restores your fallback position.
Include mid-term flex-down rights. Negotiate the ability to reduce FUE quantities by 10 to 15% annually if business needs change. Standard RISE contracts do not include this; it must be added.
Validate FUE sizing independently. Do not rely solely on SAP’s FUE calculator. Engage independent advisers to map your current users to FUE equivalents and identify potential over-subscription.
Negotiate data portability and exit rights. Ensure the contract grants you the right to extract all data and custom code in usable formats at contract end, with a 6 to 12 month transition period.
Scrutinise SLAs. Review uptime commitments, service credit caps, measurement windows, and exclusions. Push for enhanced SLAs with meaningful financial remedies.
Address M&A scenarios. Include provisions for licence adjustments in the event of divestitures, mergers, or significant workforce reductions.
Retain the BYOL option as leverage. Even if you are leaning toward RISE, maintain a credible BYOL alternative throughout negotiations. SAP’s pricing improves significantly when they believe you might not sign.
Engage independent advisers. RISE contracts are complex and heavily favour SAP’s standard terms. Specialist firms identify hidden costs, draft protective clauses, and benchmark pricing against market norms.
No. RISE grants time-bound subscription rights only. You have the right to use S/4HANA for the duration of the contract term. When the subscription ends, whether by expiry or non-renewal, your usage rights terminate. This is fundamentally different from BYOL, where your perpetual licence remains yours indefinitely regardless of whether you continue paying maintenance.
Standard RISE contracts do not permit early termination without paying the remaining contract value. You are committed for the full term (typically 3 to 7 years). To mitigate this, negotiate mid-term flex-down rights allowing partial quantity reductions, and include provisions for licence adjustments in the event of divestitures or significant workforce changes.
Traditional BYOL licensing requires purchasing specific quantities of each user type (Professional, Limited Professional, Employee Self-Service) at different prices. FUE pools all user types into a single metric. Each user type consumes a fraction of an FUE (e.g., Professional = 1.0, ESS = 0.1). This provides flexibility to reallocate as your user mix changes, but requires careful initial sizing to avoid over- or under-subscription.
Not always, but frequently for enterprises with efficient operations. SAP positions RISE as offering approximately 20% TCO savings, but this assumes high-cost data centre operations. Enterprises already running lean SAP environments on hyperscalers often find RISE 15 to 30% more expensive over five years. The only way to determine which model is cheaper for your organisation is a detailed TCO comparison against your actual current-state costs.
No. RISE bundles SAP support as a non-negotiable component of the subscription. You cannot opt for third-party support providers (such as Rimini Street) to reduce costs. Under BYOL, switching to third-party support is a legitimate cost-saving option and a powerful negotiating lever against SAP.
SAP’s Cloud Extension Policy allows you to convert existing on-premise licence maintenance value into RISE subscription credits. However, the conversion ratio is not always one-to-one, and the perpetual licence rights for the converted products are typically surrendered. Negotiate the conversion terms carefully. Once perpetual rights are surrendered, they cannot be recovered without repurchasing at current prices. For more detail, see our guide on RISE Impact on Existing Licences & Shelfware.
The most critical protections are: renewal price caps (limiting increases to a defined percentage), conversion-to-perpetual rights at contract end, mid-term flex-down provisions, data portability and exit transition periods, enhanced SLAs with meaningful credits, and explicit customisation rights if using Private Cloud edition. None of these protections appear in SAP’s standard RISE terms. They must all be negotiated before signing.
Redress Compliance helps enterprises model the true cost of RISE, negotiate protective contract terms, validate FUE sizing, and secure the best possible deal. Whether you choose RISE or stay with BYOL, we work completely independently of SAP. Fixed-fee engagements with guaranteed ROI.