Contractual Differences Between RISE with SAP and BYOL Models

Section 1: The Two Models Defined

RISE with SAP is SAP's subscription offering where SAP owns, operates, and manages the entire technology stack—infrastructure, database, operating system, and application layer. The customer pays a single bundled monthly or annual fee that includes software licensing, cloud infrastructure, standard support, and routine maintenance. You are subscribing to a service, not purchasing ownership. When the contract ends, your rights end.

BYOL (Bring Your Own Licence) means you retain existing perpetual SAP S/4HANA or ECC licenses and deploy them on cloud infrastructure (AWS, Azure, GCP, or on-premise) that you or your cloud provider manages. You own the software rights indefinitely; SAP provides application-layer support only via a separate support contract priced at approximately 22 percent of net license value annually. You contract separately with your infrastructure provider for compute, storage, and backup services.

This is more than a technical distinction. The contractual consequences cascade: ownership rights, liability allocation, termination rights, pricing trajectories, and lock-in risk all flow from this fundamental model choice.

Why S/4HANA Migration Changes the Licence Baseline

This is a critical contractual risk in both models. When you migrate from ECC to S/4HANA, the licensing baseline may change. If you were running ECC with a named-user model, S/4HANA's newer licensing metrics (such as full user equivalents and indirect access measurement via DDLC) may impose higher licence counts. In a BYOL contract, you buy new S/4HANA perpetual licenses and pay for the upgrade. In a RISE renewal, SAP can reset your pricing based on your new S/4HANA usage footprint. Both models expose you to a ratcheting effect at migration—a critical clause to scrutinize during contract negotiation.

Section 2: Ownership and Liability

The ownership model determines who bears risk when systems fail, data is lost, or performance degrades.

RISE: SAP Owns Infrastructure and Assumes Liability

Under RISE, SAP owns and operates the infrastructure. The contract specifies SAP's service level agreement (SLA): typically 99.7% uptime for production environments, defined maintenance windows (usually monthly, scheduled in advance), backup and disaster recovery protocols, and incident response times (e.g., P1 critical incidents acknowledged within 15 minutes).

SAP is contractually responsible for provisioning servers, patching the operating system and database, managing encryption, handling failover, and performing backups. When the database crashes, SAP's team responds. If a patch causes an outage, SAP is liable. If data is lost due to inadequate backup procedures, SAP bears the remediation cost. The SLA contract specifies service credits (typically 5-10% of monthly fees) if these commitments are missed for extended periods. However, SAP's liability is capped—usually at 12 months of fees, sometimes lower for indirect or consequential damages.

The trade-off: you outsource operational complexity but lose direct control over infrastructure decisions. SAP decides which hyperscaler region to use, when patches are applied, when upgrades happen, and how to configure the network. Customization options are restricted.

BYOL: Customer or Cloud Provider Owns Infrastructure; SAP Supports Application Only

In a BYOL model, you (or your chosen cloud provider or systems integrator) own the infrastructure responsibility. SAP's support contract explicitly covers application-layer issues only: transaction processing, business logic, data integrity within the ERP modules. SAP will not support infrastructure, OS, database administration, or network issues—these fall to your cloud provider or internal team.

This creates a contractual split: your infrastructure SLA comes from your cloud provider's standard terms (typically 99.9% or 99.99% uptime for compute, with additional costs for premium availability). Your SAP application support SLA is separate: P1 incidents typically acknowledged within 1 hour, with resolution targets of 4-8 hours. But if the problem is "database is slow because of network misconfiguration," SAP won't engage—you resolve it with your cloud provider.

You own and control infrastructure decisions: which region, which availability zones, how many replicas for disaster recovery, when to scale, whether to use managed databases or self-managed. This flexibility is valuable if you have strong cloud operations capability. It becomes a liability if you lack that expertise.

What SAP will and will not support in BYOL environments is defined in the support contract's scope section. Common exclusions: OS patching, database backups (unless integrated through supported APIs), network configuration, firewall rules, cloud provider outages, and third-party middleware (unless certified by SAP). If your problem involves any excluded component, you're on your own.

Data Sovereignty and Residency

RISE contracts specify the hyperscaler and region where your data resides. You choose from SAP's list of available regions at contract start (e.g., "us-east-1 on AWS" or "Europe-west-1 on Azure"). If you later need to move to a different region for data sovereignty reasons (e.g., German data must stay in Germany due to regulatory changes), this typically requires renegotiation and potential redeployment costs.

In a BYOL contract, you have greater flexibility: you choose the cloud provider and region. If regulatory requirements change, you can move to a different cloud provider or on-premise without SAP's consent—you just need to maintain your support contract with SAP. This is a significant contractual advantage for organisations with complex data sovereignty requirements or multi-cloud strategies.

Section 3: Licence Terms and Rights

RISE: Subscription Licence—No Perpetual Ownership

Under RISE, you are licensing software for a fixed term (typically 1 to 3 years, with automatic renewal unless either party gives 60-90 days notice). You have no perpetual licence rights. When the contract expires and you choose not to renew, your usage rights expire. You lose access to the software immediately. You cannot run S/4HANA perpetually on the subscription you paid for; once the subscription term ends, you must either renew, migrate to public cloud (if leaving SAP entirely), or extract your data and move to BYOL.

The subscription model is operationally simpler (you don't manage licensing complexity), but it creates dependency. SAP owns the relationship and sets renewal terms. SAP can increase pricing at renewal, tie access to new products (e.g., bundling in SAP Analytics Cloud as a mandatory add-on), or discontinue the service in your region.

BYOL: Perpetual Licence—Customer Owns Rights Indefinitely

Under BYOL, you own perpetual S/4HANA or ECC licenses. These rights do not expire. Even if you stop paying for support, you retain the legal right to run the software. You could theoretically run an ECC instance on perpetual licenses indefinitely without paying SAP a penny—though you would sacrifice support, patches, and updates.

Annual support costs approximately 22% of the net licence value (NLV) per year. This is a well-established market rate. If you own $1 million in perpetual S/4HANA licenses, annual support is approximately $220,000. Unlike RISE, there is no built-in price escalation in the support contract itself—it renews at the same 22% rate annually (though SAP will occasionally negotiate increases). The perpetual licence value does not depreciate for accounting purposes; it remains an asset on your balance sheet.

Annual Support is Essential, Not Optional (for most organisations)

While perpetual licenses grant usage rights without support, most organisations cannot run without patches and updates. SAP releases critical security patches monthly and major updates (S/4HANA roadmap releases) quarterly. Running unsupported SAP is a business continuity and security risk. Practically, annual support is mandatory. The 22% NLV cost is your annual non-negotiable floor in the BYOL model.

Third-Party Maintenance Option Available Only in BYOL

A significant contractual advantage of BYOL: you can replace SAP's standard support with certified third-party SAP maintenance providers (e.g., Rimini Street, Ubiquitous, All for One). These providers offer equivalent or better support at 40-60% of SAP's cost, with more flexible terms. If you negotiate a third-party maintenance contract, your annual support cost could drop to $90,000-$130,000 instead of $220,000. RISE does not offer this option—you must use SAP's support, at SAP's pricing, as part of the subscription.

DDLC—Digital Data License Consumption and Indirect Access Exposure

SAP measures indirect access—users accessing SAP through non-SAP intermediary systems—via DDLC (Digital Data License Consumption). DDLC counts documents created by external systems that trigger SAP business logic. A customer portal where customers submit orders that flow into SAP is indirect access; the document count becomes a licensing liability.

RISE Contract Language on DDLC: RISE contracts do include indirect access clauses, but the language is typically more restrictive on SAP's ability to unilaterally audit and claim DDLC increases. RISE is a fixed-scope subscription; if you exceed document thresholds, SAP may require you to upgrade to a higher tier, but the cost impact is defined upfront. You are not typically exposed to a surprise audit claiming millions in back-dated indirect access fees, as can happen in BYOL.

BYOL Contract Language on DDLC: Standard SAP licence agreements apply. SAP retains broad audit rights. If SAP discovers you're generating 10 million documents monthly through indirect access but licensed for 2 million, SAP can claim you owe retroactive DDLC licenses for the prior 3 or 4 years. This exposure is extensive and adversarial—the leading cause of SAP licensing disputes and audit litigation. In a BYOL contract, you must carefully scope indirect access upfront and monitor document creation. A single overlooked integration can trigger a seven-figure audit claim.

Section 4: Cost and Escalation Structures

RISE: Annual Subscription with Built-In Escalation

RISE contracts include annual price escalation clauses, typically 3-5% per year. If your first-year RISE fee is $1 million, you can budget for approximately $1.03-$1.05 million in year two, $1.06-$1.10 million in year three, and so on. After 5 years, your annual cost is $1.16-$1.28 million (cumulative 16-28% increase). After 10 years, it's $1.34-$1.63 million (cumulative 34-63% increase).

This escalation is contractually locked in at signature, so there are no surprises. However, SAP may also adjust pricing at renewal if your consumption metrics change. If you grow from 1,000 to 1,500 employees, your per-user cost may increase. If DDLC thresholds are exceeded, tier upgrades are required. At contract renewal (typically every 3 years), SAP may reset pricing based on your updated FUE consumption assessment. This reset can be dramatic—a renegotiation of your entire baseline, not just the escalation applied to the prior year.

BYOL: Perpetual Licence (One-Time) Plus 22% NLV Annual Support Plus Infrastructure

BYOL has three cost components:

• Perpetual Licence (one-time): You buy S/4HANA perpetual licenses once. If you buy $1 million in perpetual licenses, that's a one-time capital expenditure. You own these licenses indefinitely.
• Annual Support (~22% NLV): $220,000 per year, renewable annually. SAP may negotiate increases, but there is no contractual escalation clause (unlike RISE). Alternatively, you can switch to third-party maintenance at 40-60% of SAP's cost.
• Infrastructure (hyperscaler or on-premise): Your cloud provider charges monthly or annually for compute, storage, data transfer, and managed services. Costs vary widely but expect $300,000-$600,000 annually for a mid-sized SAP environment on AWS or Azure.

Total 5-year BYOL cost: approximately $1M (licenses) + $1.1M (support) + $2.5M (infrastructure) = $4.6M. Total 10-year BYOL cost: approximately $1M (licenses) + $2.2M (support) + $5M (infrastructure) = $8.2M. Note that licenses are purchased only once, then support and infrastructure scale linearly with time.

5-Year and 10-Year Modelling Matters Enormously

Let's model a hypothetical $1.2M annual RISE contract (first year) against BYOL:

RISE (5 years, 4% annual escalation): $1.2M + $1.25M + $1.30M + $1.35M + $1.40M = $6.5M total (average $1.3M/year).

BYOL (5 years, assuming $1.5M upfront license, 22% support, $450K infrastructure/year): $1.5M (licenses) + $330K + $330K + $330K + $330K + $330K (support) + $450K x 5 (infrastructure) = $1.5M + $1.65M + $2.25M = $5.4M total (average $1.08M/year). BYOL is approximately $1.1M cheaper over 5 years.

RISE (10 years, 4% annual escalation): $1.2M + $1.25M + $1.30M + $1.35M + $1.40M + $1.46M + $1.52M + $1.58M + $1.64M + $1.71M = $14.61M total.

BYOL (10 years): $1.5M (licenses, one-time) + $3.3M (support over 10 years) + $4.5M (infrastructure over 10 years) = $9.3M total. BYOL is approximately $5.3M cheaper over 10 years.

The longer the contract horizon, the more BYOL's perpetual license advantage compounds. The escalation clauses in RISE mean that by year 10, your annual cost is significantly higher than year 1. BYOL's support cost is essentially flat (though subject to negotiated increases, they are not contractually mandated escalations).

RISE Contract Renewal: SAP Resets Pricing Based on FUE Consumption Assessment

When your RISE contract renews (typically every 3 years), SAP doesn't simply apply the escalation rate to the prior year's fees. Instead, SAP conducts a "sizing assessment"—measuring your actual user base, transaction volumes, and system utilization. SAP then sets the renewal price based on current market rates and your updated footprint. This can result in material price increases above the escalation rate, especially if your business has grown. If you signed a 3-year deal at $1.2M/year and your user base doubled, your renewal could be $2M/year or higher, not the $1.35M that the 4% escalation would suggest.

SAP Fiscal Year Ends December 31—Negotiate RISE Deals in Q4

SAP's sales incentives are tied to calendar-year fiscal targets. Deals signed in Q4 (October-December) often carry more aggressive discounts and better terms than deals signed in Q1-Q3. If you are evaluating RISE, negotiate in November or December to leverage SAP's year-end closing pressure. Similarly, license migration incentives (e.g., credits on your perpetual ECC licenses if you convert to RISE) are more generous in Q4.

Section 5: Termination, Exit, and Portability

RISE Early Termination: Significant Financial Penalties

RISE contracts typically lock you in for 1-3 years. If you attempt to terminate early, SAP's contract will include substantial penalties—typically covering the remaining contract term (e.g., if you have 18 months left, you owe 18 months of fees to terminate). Some contracts include "wind-down" clauses (e.g., you pay 75% of remaining fees to exit), but the financial impact of early termination is material.

The penalty is justified by SAP's perspective: they have invested in infrastructure provisioning, implementation support, and ongoing operations. Early termination deprives them of anticipated revenue. For you, this creates lock-in risk: if you discover RISE is not meeting your needs, you cannot easily walk away. You are financially trapped for the contract term.

RISE at End of Term: Three Expensive Options

When your RISE contract term expires, you have three paths, all with material costs:

• Renew: SAP resets pricing based on current market rates and your updated footprint (as described above). Renewal terms are often worse than the original deal. Budget for 10-30% price increases at renewal.
• Migrate to Public Cloud (SAP C/4HANA or other SaaS): If you exit SAP ERP entirely, you must migrate data, retrain users, and absorb implementation costs. Migration costs typically equal 30-50% of your annual software spend.
• Extract and Move to BYOL: This is the "RISE exit strategy." You extract your S/4HANA database and move to BYOL (on a hyperscaler or on-premise). SAP will assist with data extraction for a brief wind-down period (typically 30-60 days), but any extended extraction, data transformation, or custom work beyond that incurs professional services fees. You must also purchase perpetual BYOL licenses for the environments you're moving to. This is expensive but possible and gives you optionality at renewal.

BYOL Termination: Maximum Operational Independence

In a BYOL model, you have complete termination flexibility. You can cancel your support contract with 30-60 days notice (depending on terms). You can cancel your infrastructure contract with your cloud provider (typically 30 days notice). Your perpetual licenses remain valid indefinitely. You can literally unplug from SAP and continue running your ERP system unsupported, though this is not advisable long-term.

Practically, BYOL termination is clean: stop paying for support and infrastructure, keep running (or archive) your perpetual licenses. No financial penalties, no lock-in risk. This is a massive contractual advantage over RISE and a primary reason many large enterprises prefer BYOL despite higher year-one costs.

Data Portability Clauses: RISE vs BYOL

RISE contracts specify SAP's obligations to extract your data if the contract ends. Typically, SAP will provide your data in standard formats (e.g., CSV, XML) for 30-60 days post-termination. After that window, data may be deleted. You must have an extraction plan in place before contract end or risk losing data.

BYOL gives you full control of data: it resides in databases you own (or your cloud provider manages under your terms). You can extract, backup, and replicate data at any time without SAP's cooperation. This is a significant operational and contractual advantage if your business strategy requires data portability.

Lock-In Risk: RISE Creates Dependency; BYOL Preserves Independence

RISE creates lock-in because you are dependent on SAP's managed environment, pricing power at renewal, and operational decisions (region, upgrade timing, etc.). You cannot easily exit, and SAP knows this. BYOL, despite higher infrastructure complexity, preserves your operational independence. You control your infrastructure, your support relationship with SAP is separate from your infrastructure contract, and you can terminate either without terminating the other. This independence is particularly valuable in multi-cloud strategies or if you anticipate organizational changes (M&A, divestiture, cloud migration) over the contract term.

Section 6: Support and SLA Comparison

RISE SLA: End-to-End Support by SAP

RISE SLAs cover the entire stack. SAP supports infrastructure (hyperscaler management, failover, scaling), operating system (OS patching, hardening), database (tuning, backup recovery, replication), and application layer (business logic, transaction processing, reporting). A single support team owns all components. When you call SAP support, they investigate the entire stack. This end-to-end responsibility is operationally simpler for you.

Typical RISE SLA commitments:

• P1 (Critical): 99.7% uptime for production; acknowledged within 15 minutes; resolution target 4 hours.
• P2 (High): Acknowledged within 1 hour; resolution target 8 hours.
• P3 (Medium): Acknowledged within 4 hours; resolution target 24 hours.
• P4 (Low): Best effort; resolution target 5 business days.

Service credits apply if SAP misses these targets for extended periods (e.g., if P1 uptime falls below 99.7% in a month, you receive 5-10% credit on monthly fees). However, credits are capped and often require formal escalation to collect.

BYOL SLA: SAP Supports Application Layer Only; Cloud Provider Supports Infrastructure

BYOL splits responsibility. SAP's support contract covers application-layer incidents only: business logic, transaction processing, data integrity, reporting, customizations, interfaces. Infrastructure incidents (compute down, network latency, storage performance, database admin) are handled by your cloud provider or internal team.

Typical BYOL SLA commitments (SAP portion):

• P1: Acknowledged within 1 hour; resolution target 4-8 hours (for application-layer issues).
• P2: Acknowledged within 2-4 hours; resolution target 8-24 hours.
• P3: Acknowledged within 8 hours; resolution target 2-3 business days.
• P4: Best effort; no time commitment.

Your cloud provider (e.g., AWS) provides separate infrastructure SLA: typically 99.9% uptime for compute, 99.99% for managed databases. These SLAs are separate from SAP's and require separate escalation.

The operational risk in BYOL: when something breaks, determining whether it's an application issue (SAP's responsibility) or infrastructure issue (cloud provider's responsibility) can be contentious. You may find yourself in the middle, with SAP blaming the cloud provider and the cloud provider blaming your configuration. Having strong cloud operations capability mitigates this risk.

Premium Support Options Differ

RISE includes standard support as part of the subscription. You can upgrade to premium support (e.g., "Enterprise Support," dedicated technical account manager, faster response times) at additional cost, typically 20-50% above the base subscription.

BYOL includes standard support in the 22% NLV annual fee. Premium support (e.g., SAP Enterprise Support, ProActive Support) is an additional cost, typically $200,000-$400,000 annually on top of the 22% base, depending on your environment size. Premium support provides dedicated resources, quarterly health checks, and pro-active optimization recommendations. Many large BYOL customers opt for premium support to mitigate risk; this additional cost should be factored into the BYOL TCO model.

Section 7: Which Model Fits Which Organisation

RISE Suits:

• Organisations wanting to outsource IT operations: If you prefer to focus on business processes rather than infrastructure management, RISE's managed service model is attractive. SAP handles servers, patches, backups, DR.
• Those with limited cloud operations capability: If your internal team lacks cloud architecture and database administration expertise, RISE eliminates the need to hire or upskill. SAP provides the expertise as part of the service.
• New SAP customers without perpetual licence investments: If you are implementing SAP for the first time and have no existing perpetual ECC or S/4HANA licenses, RISE avoids the large upfront license purchase. You spread costs over time via subscription.
• Organisations seeking predictable, bundled costs: If budget certainty is critical, RISE provides a single monthly/annual fee covering all technology costs. No surprise infrastructure bills, no separate negotiations with cloud providers.

BYOL Suits:

• Organisations with significant perpetual licence portfolios: If you have $2M+ in perpetual S/4HANA or ECC licenses, moving to BYOL leverages this sunk investment. RISE would require you to sunset these licenses and pay a new subscription—BYOL extends their value.
• Those with strong cloud operations teams: If you have experienced infrastructure architects, database admins, and DevOps engineers, BYOL's operational flexibility is advantageous. You can optimize infrastructure independently of SAP.
• Organisations needing maximum flexibility or negotiating third-party maintenance: If you want to switch cloud providers, move to on-premise, or use third-party SAP maintenance providers, BYOL provides these options. RISE locks you into SAP's managed environment.
• Multi-cloud or hybrid-cloud strategies: If your business operates across AWS, Azure, GCP, and on-premise, BYOL allows you to run SAP in multiple clouds with a single support contract. RISE requires separate subscriptions per hyperscaler/region.
• Organisations with unpredictable growth: If your user base or transaction volumes are uncertain, BYOL's perpetual license model and separate infrastructure payments decouple growth costs. In RISE, significant growth triggers upward pricing resets at renewal.

Hybrid Approach: Core ERP on RISE, Satellite Systems on BYOL

Some large enterprises adopt a hybrid strategy: RISE for core S/4HANA (benefiting from managed operations and implementation support), BYOL for satellite systems (SuccessFactors, Analytics Cloud, Ariba) where they have existing perpetual licenses or can negotiate better third-party maintenance terms.

Conclusion: The Contractual Decision Framework

The RISE vs BYOL choice is fundamentally a contractual decision about ownership, liability, and long-term cost trajectory. RISE offers operational simplicity, bundled costs, and end-to-end support but creates lock-in and exposes you to escalation clauses and renewal pricing resets. BYOL preserves perpetual ownership, operational independence, and long-term cost control but requires infrastructure expertise and exposes you to DDLC audit risk.

Neither model is universally "better." The right choice depends on your operational maturity, existing license investments, growth trajectory, and tolerance for lock-in risk. Model both scenarios across 5 and 10-year horizons, including infrastructure costs, support options, and exit scenarios. Negotiate RISE contracts in SAP's fiscal year Q4 (October-December) to maximize leverage. For BYOL, explicitly scope indirect access DDLC thresholds upfront and monitor compliance continuously. In both cases, engage SAP licensing expertise before signing—the contractual terms will govern your relationship for years.