Understanding the BTP Licensing Landscape

SAP offers three primary commercial models for BTP consumption: Pay-As-You-Go (PayG), the Cloud Platform Enterprise Agreement (CPEA), and the newer BTP Enterprise Agreement (BTPEA, launched in 2023). Each has different economics, flexibility profiles, and risk characteristics. The right choice depends on your consumption patterns, project roadmap, and organisational readiness for cost governance.

Pay-As-You-Go: Exploration and Low-Volume Workloads

Pay-As-You-Go is SAP's entry-level BTP model. No upfront commitment. You provision BTP services and are billed monthly based on actual consumption at published list price. This model is ideal for proof-of-concept, experimental workloads, and teams early in their BTP adoption journey.

The strength of PayG is flexibility: you can try services, scale up or down, and exit with minimal commitment. The weakness is cost. PayG list pricing is typically 30–50% higher per unit than committed CPEA rates. At scale, this premium becomes significant.

For example, if you run HANA Cloud instances on PayG at list price and later commit to a CPEA, your effective per-instance cost can drop by 30–40%. This means a 6-month PayG exploration phase for a new HANA use case can cost more than three years of committed CPEA for the same workload.

When to use PayG: Proof-of-concepts, test projects, temporary data migration services, or any workload with uncertain duration. Set a time boundary (e.g., "PayG for 6 months, then evaluate for CPEA") to avoid drifting into expensive indefinite PayG consumption.

CPEA: The Industry Standard for Committed Consumption

The Cloud Platform Enterprise Agreement is SAP's standard commercial model for enterprise BTP consumption. You commit to a minimum annual credit volume (e.g., 100,000 credits per month for 12 months). In exchange, SAP offers a discounted per-credit rate. Unused credits at year end are typically forfeited unless you negotiate rollover provisions.

CPEA credits pool across all BTP services — HANA Cloud, Integration Suite, analytics services, security, and emerging services. This pooling is a major strength: your teams have flexibility to shift consumption between services without renegotiating the contract. If one project consumes fewer analytics credits than expected and another consumes more for integration, the pooling absorbs the variance.

CPEA is the right model for enterprises with predictable BTP usage above approximately EUR 200K per year. Below that threshold, the administrative overhead of chargeback and monthly governance often outweighs the pricing benefit. Above that threshold, CPEA delivers 30–50% cost savings compared to PayG.

Key CPEA negotiation points:

  • Credit rate (per unit price): The discount percentage below list price. Industry standard is 20–40% below list. Your leverage increases with committed volume and multi-year contract length.
  • Rollover provision: What happens to unused credits at year end. Default is forfeiture; best practice is to negotiate carry-forward of 15–25% unused credits to the next year. This prevents waste and reduces end-of-year rush spending.
  • Overage rate: If you exceed your committed volume during the year, what price do you pay? Lock a fixed overage rate (e.g., 1.5x the committed rate) rather than paying list price.
  • Minimum commitment ramp: For new BTP adoption, negotiate a lower minimum in year 1 and ramp to full commitment in years 2–3. This provides budget predictability while you build consumption.
  • Service coverage: Ensure the CPEA explicitly covers all services you plan to use, including newer services launched during the contract term. SAP occasionally launches new services that consume credits — you want these covered by your existing CPEA, not billed separately.

BTPEA: Subscription Entitlements Plus Credits

The BTP Enterprise Agreement, launched in 2023, is SAP's attempt to modernise BTP commercial models. Rather than a pure credits model, BTPEA includes a base platform fee (like an SaaS subscription) that covers defined services, plus a variable credit allocation for additional and experimental services.

Under BTPEA, certain core services — such as Platform Provisioning, Cloud Connector, and specified security services — are included as subscription entitlements in the platform fee. You pay a flat annual fee per subaccount (or per global account, depending on contract structure). Any consumption beyond the included services draws from a credit pool at a negotiated per-credit rate.

BTPEA is designed to suit organisations running a stable set of core BTP services continuously and then extending with experimental or temporary services. The fixed subscription fee creates cost predictability for the core platform, while credits handle variable workloads.

When to switch from CPEA to BTPEA: If your CPEA consumption is heavily weighted to a few core services that never scale down (e.g., Integration Suite, HANA Cloud for production systems), BTPEA's fixed subscription component can deliver savings. If your BTP usage is highly variable or experimental, CPEA remains superior — you avoid paying a subscription fee for unused capacity.

Switching to BTPEA at renewal requires careful modelling. Build a consumption profile for your current CPEA: which services are consumed, how consistently, and at what volume. Map each service to BTPEA's subscription entitlements. Calculate the effective cost under both models. The crossover depends on your specific consumption pattern.

RISE with SAP and BTP Bundling

RISE with SAP includes a BTP entitlement package as part of the overall contract. The entitlement covers certain subscription services (provisioning, connectivity, core platform features). This is separate from a standalone CPEA or BTPEA agreement.

A critical risk: overlap between RISE BTP entitlements and a standalone CPEA. Some enterprises inadvertently negotiate both RISE BTP entitlements and a separate CPEA credit commitment, paying for the same services twice. Before committing to additional BTP spend, review your RISE contract letter to understand exactly which BTP services and subscription tiers are included.

Best practice: if you have RISE, treat RISE BTP entitlements as your base platform commitment. Negotiate a standalone CPEA credit allocation only for services or consumption volumes beyond what RISE covers. Ensure the RISE contract and the CPEA are explicitly linked and co-terming (same start and end dates).

S/4HANA Migration and BTP Planning

Every S/4HANA cloud migration consumes substantial BTP resources. The Integration Suite (for Fiori, API management, process integration), data migration services, test data provisioning, and extension development all drive BTP credit consumption during the project window (typically 18–24 months).

S/4HANA migration also changes your SAP licensing baseline. The migration triggers a review of SAP Digital Access adoption levels and can create new obligations around document-driven licence consumption (DDLC). Your BTP strategy must account for these licensing implications.

Best practice: integrate BTP strategy into S/4HANA project planning from the start. Don't assume your existing CPEA will be sufficient for project consumption. Build a separate BTP budget for the project window, with an expected credit consumption profile. Once the project concludes and systems go live, transition the now-operational services (persistent integration, extension apps) into your operational BAU BTP budget and decommission the project subaccounts.

Negotiation Timing and Leverage

SAP's fiscal year ends December 31. All enterprise agreements, including BTP, renew against this calendar. This creates predictable urgency dynamics:

  • Q1–Q2 renewal conversations: Relaxed SAP sales behaviour. You have time to conduct RFP, vendor evaluations, and multi-vendor negotiations. SAP is willing to invest in longer sales cycles.
  • Q3 renewal conversations: Moderate urgency. SAP wants to close before year-end but isn't under extreme pressure yet. Still good negotiating environment.
  • Q4 (October–December) renewal conversations: Maximum SAP time pressure. If you're renewing in Q4 for a December 31 renewal, SAP needs to close quickly. Use this as leverage, but be prepared for harder pushback on pricing.

Start BTP renewal conversations 9–12 months in advance (e.g., January for a December 31 renewal). This gives you time for thorough negotiation without end-of-year urgency. Q4 negotiations are only advantageous if you have viable alternatives or are willing to walk away from renewal.

Co-Terming S/4HANA and BTP

A high-leverage negotiation strategy is to co-term your BTP agreement with your S/4HANA agreement — same start and end dates. This allows you to negotiate BTP and S/4HANA as a single commercial package.

SAP strongly prefers bundled negotiations: it creates a single touchpoint, reduces deal friction, and allows account leaders to cross-subsidise (offering concessions on one product to meet targets on another). You benefit through 10–20% better pricing on both products compared to standalone negotiations.

To execute co-terming, ensure your S/4HANA and BTP renewals align on the same end date. If they're currently staggered, negotiate an early renewal of the non-aligned contract to bring both to the same end date. The short-term cost of early renewal is usually offset by the pricing benefits of bundled negotiation.

Model CPEA vs BTPEA economics aligned to your consumption baseline and roadmap.

Our advisors conduct detailed cost-benefit analyses and lead BTP renewal negotiations.
Start a Review →

The Phased Adoption Strategy

For organisations new to committed BTP spend, a phased approach de-risks the decision:

  1. Months 1–6: Pay-As-You-Go exploration. Provision BTP services in a PayG model. Run uncontrolled workloads, experiment with different services, establish usage patterns. Don't over-optimise for cost yet.
  2. Months 6–9: Establish a consumption baseline. Analyse actual PayG consumption. Identify which services are consumed consistently vs. experimentally. Build cost projections for a 12-month period.
  3. Months 9–12: Transition to CPEA. Based on the consumption baseline, commit to a CPEA at a volume targeting 85–90% utilisation (allowing 10–15% variance). This balances cost savings against waste from under-utilisation.

This phased approach typically costs 10–15% more than a direct CPEA commitment because months 1–6 are billed at PayG premium rates. But it de-risks over-commitment and ensures your CPEA volume is validated against real consumption.

Governance as a Prerequisite

A critical principle: never commit to a CPEA without having a credit governance framework in place. Committing first and building governance later is a known failure mode. Teams lack cost visibility, consume heavily, and exceed the committed volume at renewal, requiring overage billing or a hasty renegotiation under SAP pressure.

Before committing to CPEA, establish the governance elements described in the credit management guide: subaccount structure aligned to cost centres, monthly consumption reporting, budget alerts, quota management, and chargeback. Once governance is in place and you've demonstrated 3–6 months of controlled consumption, commit to CPEA.

Seven Recommendations

  1. Start with PayG if you're new to BTP. Commit to CPEA once you have a consumption baseline. The 6–12 month PayG exploration phase costs more per unit but de-risks over-commitment. Once consumption patterns are clear, transition to CPEA to achieve 30–50% cost savings.
  2. Negotiate rollover of 15–25% unused credits into the following year. This is one of the highest-leverage CPEA clauses. Rollover prevents end-of-year waste and gives you budget flexibility across contract years.
  3. Lock overage pricing at a fixed rate (e.g., 1.5x committed rate) rather than accepting list price for overages. This protects against surprise overage bills if consumption exceeds your commitment.
  4. Co-term BTP and S/4HANA renewals to unlock bundled pricing discounts of 10–20%. If they're currently on different renewal dates, negotiate early renewal to align them.
  5. Review RISE BTP entitlements before committing to a standalone CPEA. Verify which BTP services are included in your RISE package to avoid duplicate commitments and cost duplication.
  6. Start BTP renewal negotiations 9–12 months in advance, targeting Q1–Q2 conversations.. Avoid Q4 urgency when SAP has negotiating leverage. In Q4, SAP will push harder on pricing and resist concessions.
  7. Model BTPEA economics carefully before switching from CPEA. BTPEA's fixed subscription component is advantageous only if your core service consumption is predictable and stable. For variable or experimental BTP usage, CPEA remains superior.