What SAP Doesn't Explain About RISE Add-On Costs
- BTP credits included in the standard RISE bundle are consistently oversized relative to actual consumption — 70% of enterprises don't fully consume them in years 1–2, yet pay for unused credits that expire.
- Add-on cloud applications (Ariba, SuccessFactors, Concur, Fieldglass) carry their own subscription fees, support costs at 22% of licence value, and separate escalation mechanisms — compounding your total SAP spend independently of the core RISE fee.
- SAP Signavio for process mining is increasingly included in RISE proposals as a "complementary" bundle, but carries minimum commitment levels that create a new cost floor regardless of usage.
- Integration costs between RISE and add-on applications — often requiring BTP integration services — create a second layer of consumption that SAP's proposals typically underestimate.
- The total cost of a RISE deployment including all add-on agreements is typically 40–80% higher than the core RISE subscription fee presented in SAP's initial proposal.
This article is part of our complete guide to RISE with SAP contract structure. Read alongside our analysis of RISE with SAP pricing mechanics for a full picture of the cost model.
SAP has spent a decade building a suite of cloud applications that are commercially connected to the S/4HANA platform. RISE creates the S/4HANA anchor; the add-on applications extend the commercial relationship across procurement (Ariba), HR (SuccessFactors), expense management (Concur), contingent labour (Fieldglass), and process intelligence (Signavio). Each add-on is positioned as a productivity enhancement — and many deliver genuine value. The commercial problem is in how they are priced, bundled, and obligated within the broader RISE framework.
The BTP Credit Problem: What SAP Doesn't Tell You
Business Technology Platform (BTP) is SAP's integration and extension platform. In RISE, BTP credits are included in the base bundle — SAP positions this as one of the key advantages of the RISE offer versus managing S/4HANA on-premise or via a third-party. The problem is in the sizing, the consumption model, and the expiry mechanism.
How SAP Sizes BTP Credits in RISE Proposals
SAP's standard RISE proposals include a BTP credit bundle sized using a "standard consumption model" — an SAP-defined estimate of how much BTP your RISE deployment will consume, based on your user count, modules, and a set of assumed integration and extension use cases. This model is designed to generate overage revenue, not to reflect your actual likely consumption.
In practice, BTP consumption in the first two years of a RISE deployment is typically well below SAP's estimate. Implementation projects are delayed. Integration use cases that SAP's model assumes are live in year 1 may not be activated until year 2 or 3. The result: credits expire unused, and in year 3 or 4 when your BTP consumption actually ramps up, you are now buying additional BTP credits at an overage rate that SAP controls.
SAP's standard BTP credit terms: credits included in the annual RISE subscription. Credits expire at the end of each annual period. Unused credits are forfeited — they have no cash value, no rollover option, and cannot be applied to overage in the following year. For a €5M/year RISE contract with €800K of included BTP credits, consuming 60% of those credits means €320K of value forfeited every year. Over a 5-year term, this compounds to €1.6M in paid-for-but-never-used platform credits.
BTP Overage: The Revenue Mechanism SAP Relies On
When you exceed your included BTP credits, SAP charges overage at your contracted per-unit rate — which was set during the original RISE negotiation. If you didn't negotiate this rate independently, you are paying SAP's standard overage pricing, which is typically 2–3x what a dedicated BTP subscription would cost for the same consumption level.
The pattern is predictable: years 1–2, significant underconsumption and credit waste. Years 3–5, consumption ramps as integrations and extensions go live, triggering overages. SAP benefits at both ends — from forfeited unused credits in years 1–2, and from overage revenues in years 3–5. Our RISE advisory team consistently identifies this pattern and restructures BTP commitments to avoid it.
SAP Cloud Application Add-Ons: The Full Cost Picture
Beyond BTP, the major RISE add-on cost categories are SAP's cloud application suite. Each carries its own pricing model, support cost, and escalation mechanism.
SAP Ariba (Procurement)
Ariba is SAP's cloud procurement suite. It is priced on a transaction volume basis (for network transactions) and a user subscription basis (for sourcing, contracts, and spend analysis modules). Ariba's pricing model is opaque by design — the "transaction fees" for Ariba Network access are particularly difficult to benchmark, as they are tied to the value and volume of transactions processed through the Ariba Network.
Hidden cost to watch: Ariba subscription fees escalate independently of your RISE contract. Ariba implementations typically take 12–24 months, meaning you pay full subscription fees during a period of minimal usage. Ariba transaction fees for suppliers on the Ariba Network are often partially passed to suppliers — but the supplier onboarding costs (SAP's preferred "Ariba Network Enablement" programmes) can run into six figures.
SAP SuccessFactors (HR)
SuccessFactors is SAP's cloud HCM suite. It is priced per employee per month (PEPM) across modules including Core HR, Talent, Learning, and Workforce Analytics. The PEPM rate varies by module and by your negotiated discount from list price. SAP's standard RISE proposals include SuccessFactors at a "bundle rate" that appears attractive but is calculated from a list price that no sophisticated buyer should pay.
Hidden cost to watch: SuccessFactors pricing escalates annually independently of your RISE escalation. Employee count changes (up or down) are measured quarterly, creating a "true-up" mechanism that adds complexity. Integration between SuccessFactors and S/4HANA for HR-to-Finance processes requires BTP integration services — consuming your BTP credit allocation from a non-S/4HANA use case.
SAP Concur (Travel & Expense)
Concur is priced per active user per month. The pricing model rewards volume but the minimum commitment structures mean that enterprises with seasonal travel patterns often pay for inactive users during low-travel periods. Concur's implementation is typically faster than Ariba or SuccessFactors — but the data migration costs from legacy T&E systems are frequently underestimated.
Hidden cost to watch: Concur charges per expense report submitted, per travel booking, and per active user. For enterprises with high T&E volume, the transaction-based elements can significantly exceed the user subscription fee. SAP's RISE proposals often present only the per-user fee without modelling actual transaction volumes.
SAP Signavio (Process Intelligence)
Signavio has become SAP's primary process mining and transformation tool. SAP increasingly bundles Signavio credits into RISE proposals as a differentiator — but the bundle typically includes a minimum Signavio commitment that creates a new cost floor. Signavio is priced on a workspace and user basis, with separate modules for process discovery, process management, and the process insights/analytics layer.
Hidden cost to watch: Signavio licensing requires separate Professional Services engagement for setup, data source configuration, and the integration with your source systems (S/4HANA, legacy ERP, other applications). These Professional Services costs are separate from the Signavio licence fee and from the RISE managed services scope — creating an additional implementation budget that enterprises frequently fail to plan for.
The True Total Cost of RISE: A Model for Enterprise Buyers
SAP's RISE proposal presents the total contract value as the core subscription fee plus any explicitly listed add-on subscriptions. The true total cost of ownership includes categories that SAP's proposals systematically omit or understate.
| Cost Category | What SAP Shows | What You Actually Pay |
|---|---|---|
| Core RISE Subscription (S/4HANA + Infrastructure + Enterprise Support) | €5,000,000/yr | €5,000,000/yr |
| BTP Credits (included but unused, years 1–2) | Included | €300,000 forfeited annually |
| BTP Overages (years 3–5 as usage ramps) | Not modelled | €200,000–400,000/yr |
| Ariba / SuccessFactors / Concur add-ons | Quoted separately | €800,000–1,500,000/yr |
| Signavio (process intelligence) | Included as bundle | €120,000/yr minimum commitment |
| Professional Services (migration, integration, extensions) | Partially shown | €2,000,000–5,000,000 (one-time) |
| Annual escalation (5-year term, 4% compounding) | Footnoted | +22% by year 5 on all subscription components |
| 5-Year True TCO vs SAP's Quoted 5-Year Value | €25,000,000 | €38,000,000–48,000,000 |
The model above is indicative for a mid-market enterprise (1,500–3,000 users) with a standard RISE plus Ariba and SuccessFactors configuration. The variance between SAP's presented cost and the true TCO consistently falls in the range of 40–80%. This is not accidental — it reflects a pricing presentation strategy designed to get signature before the full cost picture is understood.
Get a True RISE TCO Analysis
Our RISE advisory team builds full TCO models for enterprise buyers — before you sign, not after.
Negotiation Strategies for RISE Add-On Costs
The add-on agreements in RISE are negotiable — but they require different strategies from the core RISE subscription negotiation. Add-on agreements are often managed by separate SAP product teams with different commercial structures, incentives, and concession authorities.
For BTP credits, the most effective strategy is a consumption-based justification model. Build a bottoms-up estimate of your actual BTP consumption for years 1–3 based on specific use cases (integrations, extensions, analytics). Use this model to challenge SAP's standard credit sizing. Request a right-sizing mechanism at the year 1 or year 2 anniversary. Negotiate rollover of up to 20% of unused credits between annual periods. For detailed guidance on the mechanics of RISE contract negotiation, our guide to key RISE contract clauses covers BTP commitment structuring in depth.
For cloud application add-ons (Ariba, SuccessFactors, Concur), negotiate pricing and escalation independently of the core RISE deal. Do not allow SAP to bundle these into the RISE negotiation in a way that forces you to close all components simultaneously — SAP uses this bundling to limit your leverage on each individual component. Our SAP licence optimisation service includes specific analysis of add-on pricing relative to market benchmarks.
For Signavio, evaluate whether the included bundle in your RISE proposal reflects a consumption level you will actually achieve. Signavio's value depends entirely on how deeply you integrate it with your source systems and how actively your process teams use it. An oversized Signavio commitment creates the same waste pattern as oversized BTP credits.
What to Ask SAP Before Signing Any Add-On Agreement
These are the questions every enterprise buyer should ask SAP before executing any RISE add-on agreement. SAP's answers — or non-answers — will tell you a great deal about where the commercial risk is concentrated.
- What is the specific consumption basis for the BTP credit bundle, and can you provide a usage model based on our specific integration and extension requirements?
- What is the rollover policy for unused BTP credits, and is this negotiable?
- What are the escalation mechanics for each add-on agreement, and are they aligned with or independent of the core RISE escalation?
- What minimum commitment applies to each add-on subscription, and can it be reduced at annual review?
- What are the integration costs (BTP services) required to connect each add-on to RISE, and are these included in the add-on subscription or billed separately?
- What are the exit provisions for each add-on, and are they aligned with the core RISE contract term?
SAP's ability to answer these questions clearly and specifically — with written documentation — is a proxy for the quality of the commercial relationship you are entering. Vague answers should be treated as red flags, not reassurances. For further context on how SAP constructs its overall RISE pricing architecture, see our RISE pricing model breakdown.
Frequently Asked Questions
SAP Licensing Experts is an independent advisory firm — not affiliated with, endorsed by, or partnered with SAP SE. SAP, RISE with SAP, BTP, Ariba, SuccessFactors, Concur, Signavio, Fieldglass are trademarks of SAP SE. Our advice is 100% buyer-side.