SAP BTP Licensing Models: BTPEA, CPEA, PayG, and Subscriptions Explained

JinJin48

SAP Consultant | BTP · S/4HANA · US Global Rollout

May 6, 2026 · 12 min read

1) Target Readers#

2) The Four Licensing Models#

SAP BTP organizes commercial access into two broad categories: consumption-based models and subscription-based models. Within consumption-based, there are three distinct flavors. Understanding the difference between them is the foundation of any BTP cost planning exercise.

2-1) SAP BTP Enterprise Agreement (BTPEA) — The Current Standard#

BTPEA is the current consumption-based model for SAP BTP, introduced in April 2024 as the successor to CPEA. Under BTPEA, an organization purchases a pool of cloud credits upfront — typically on an annual basis — and draws from that pool as BTP services are activated and used ( SAP BTP Pricing).

The core mechanics:

• Prepaid credits are committed at the start of the contract term. The larger the commitment, the greater the volume discount relative to Pay-As-You-Go list prices ( SAP Licensing Experts).
• Any current and future BTP service in the BTPEA catalog can be activated or deactivated at any time. There is no need to pre-select services at contract signing.
• Overages — usage beyond the credit balance — are invoiced monthly at list price ( SAP BTP Pricing).
• Unused credits expire at the end of the contract period. There is no automatic rollover; negotiating a partial rollover is possible but not guaranteed ( SAP Licensing Experts).
• Monthly balance statements are sent to the commercial contact and are accessible via the SAP for Me mobile app, providing transparency on per-service consumption ( SAP BTP Pricing).

A key advantage of BTPEA is access to the latest SAP innovations. Services such as SAP Analytics Cloud (public system option, BI and Planning) and certain AI capabilities are available exclusively under BTPEA and are not part of the CPEA catalog ( ASUG).

BTPEA also introduces a minimum price guarantee: if the price of any BTP service decreases after a contract is signed, SAP will bill at the new lower price for the remainder of the term ( ASUG).

One technical constraint: BTPEA does not support the SAP BTP NEO environment or deprecated services ( SAP Developers).

2-2) Cloud Platform Enterprise Agreement (CPEA) — Legacy, Frozen#

CPEA was SAP’s first consumption-based model for BTP and operated on the same credit-pool mechanics as BTPEA. However, as of April 15, 2024, CPEA is no longer available to new customers, and its service catalog is frozen — no new BTP services will be added to CPEA going forward ( SAP Developers).

Existing CPEA customers can remain on CPEA and continue to purchase additional credits at renewal. SAP has confirmed there is no forced migration to BTPEA, and the transition can happen at a standard renewal without any technical changes to the existing landscape ( ASUG).

The practical implication for CPEA customers: if an organization needs access to newer BTP services or AI capabilities that SAP has introduced after April 2024, those services will not be available under CPEA. Moving to BTPEA at the next renewal is the path to accessing them.

BTPEA and CPEA cannot coexist within a single Global Account. An organization requiring both models simultaneously would need two separate Global Accounts ( SAP Developers).

2-3) Pay-As-You-Go (PayG) — Zero Commitment#

Pay-As-You-Go for SAP BTP requires no upfront commitment and no minimum spend. Usage is billed monthly based on actual consumption at standard list prices — which are higher than the discounted rates available under BTPEA or CPEA ( SAP Licensing Experts).

PayG accounts also support Free Tier service plans, allowing teams to test specific services at no cost within defined limits ( SAP Developers).

PayG is the natural entry point for organizations that are:

• Running a proof-of-concept or pilot
• Uncertain about which BTP services they will ultimately need
• Not yet ready to commit to an annual spend

Transitioning from PayG to BTPEA is operationally straightforward: existing services and subaccounts are preserved, and billing simply shifts from per-use to credit-based ( Redress Compliance).

2-4) Subscription-Based Licensing — Predictable Costs for Known Needs#

The subscription model is the traditional approach: a fixed fee for a specific BTP service or bundle, covering a defined capacity over a fixed term (typically one to three years). Unlike consumption models, subscriptions do not use cloud credits; they are separate line items covering only the services named in the contract.

Subscriptions suit scenarios where:

• Usage of a specific service is stable and well-understood
• Budget certainty is a higher priority than flexibility
• The organization runs one high-use service (e.g., SAP Integration Suite) continuously at or near full capacity

The consumption and subscription models are not mutually exclusive. An organization can maintain a BTPEA global account for flexible services while holding specific subscriptions for services with predictable, high utilization ( SAP Licensing Experts).

3) Trial and Free Tier — Getting Started Without Commitment#

Two no-cost options exist for teams that want to evaluate BTP before making any commercial commitment.

3-1) Trial Account#

The Trial account is a non-commercial, time-limited offering giving 90 days to explore a subset of BTP services in a test environment. At the end of the 90-day period — or after 30 consecutive days of inactivity — the account, all deployed applications, and all data are permanently deleted ( SAP BTP Trial).

Trial is intended for individual learning and sandbox exploration. It is not suitable for proof-of-concept work that needs to persist or be shared across a team.

3-2) Free Tier Service Plans#

Free Tier is not an account type — it is a set of service plans available within a commercial enterprise account (BTPEA or PayG). Free Tier plans have no time limit and give access to more than 90 BTP services up to defined usage thresholds, at no cost ( SAP BTP Trial).

The distinction matters in practice: a developer who needs persistent access to SAP AI Core for a real project needs a BTPEA or PayG account with the Free Tier plan for that service — not a trial account, which does not include AI Core ( SAP Community).

Free Tier plans can be upgraded to paid plans at any time without losing existing work, providing a smooth path from exploration to production.

4) BTP Licensing Within RISE with SAP and GROW with SAP#

Many SAP customers first encounter BTP licensing not through a standalone BTP contract, but through a RISE with SAP or GROW with SAP bundle.

4-1) What Is Included#

RISE with SAP includes BTP credits in the form of CPEA as standard. For S/4HANA public cloud customers under GROW, the included annual CPEA credit value typically falls between 2,000 and 16,000 credits, depending on the contract ( ITAA). GROW with SAP editions also include access to SAP Build tools for low-code application development ( LeverX).

These bundled credits are intended as a foundation — sufficient for basic extensions, integrations, and process automation at moderate scale.

4-2) The Limits of Bundled Credits#

An important constraint: the included BTP credits in RISE/GROW are a fixed allocation tied to the ERP contract. For organizations planning substantial BTP usage — custom extensions, advanced integrations, data analytics workloads, or AI services — the bundled credits will not be sufficient, and a separate BTPEA agreement is required.

SAP’s Clean Core strategy reinforces this dynamic. As customizations that previously lived inside S/4HANA are moved to BTP (the expected pattern for cloud-ready implementations), each extension, integration, and automation becomes a BTP cost that scales independently of the ERP subscription. Organizations with significant customization portfolios should model BTP costs separately and not assume the bundled credits cover them ( Redress Compliance — 2026).

4-3) 2025/2026 Bundle Changes#

SAP restructured RISE and GROW packaging in 2025. Several capabilities previously bundled in the standard RISE package — including SAP Datasphere, certain AI Unit capabilities, advanced Joule features, and sustainability tools — were moved to separate licensed add-ons, many of which consume BTP credits or require additional BTP agreements ( Redress Compliance — 2026). Organizations reviewing or renewing RISE contracts should verify which BTP-adjacent capabilities remain in their bundle versus what now requires separate procurement.

5) Choosing the Right Model#

The table below summarizes the primary trade-offs:

A common adoption path: start with PayG for pilots and proof-of-concept work, transition to BTPEA as usage stabilizes and the service mix becomes clear, and layer in individual subscriptions for any high-use services where fixed pricing provides meaningful budget certainty.

6) Monitoring and Cost Governance#

Under BTPEA or CPEA, cost governance is the customer’s responsibility. SAP provides tooling in the BTP Cockpit (Costs & Usage dashboard) to track credit consumption by service and set alerts. Recommended practices include:

• Review the monthly balance statement to verify per-service consumption matches expectations
• Set internal alert thresholds (e.g., at 75% credit consumption) to avoid surprise overages
• Use the SAP Discovery Center Pricing Estimator to model expected usage before committing to a credit level (note: this tool supports CPEA estimation; BTPEA pricing requires direct engagement with an SAP account executive)
• Assign ownership of BTP cost monitoring to a named role — ungoverned consumption accounts is a common source of unexpected overages ( SAP Licensing Experts)

7) Negotiation Considerations#

When entering a BTPEA or CPEA agreement, several contractual terms are worth raising with the SAP account team:

• Credit rollover: SAP’s default is no rollover of unused credits. Even a 10% carryover negotiated into the contract reduces the risk of losing value at year-end.
• Rate protection: Lock the per-service credit rate so that SAP cannot increase how many credits a service costs mid-contract.
• Overage pricing: Request that overages be billed at the contracted discounted rate rather than list price, or at minimum negotiate a cap on overage list-price increases.
• True-up rights: Secure the right to purchase additional credits mid-year at the same discounted rate if consumption exceeds projections.

( SAP Licensing Experts — CPEA Tips, Redress Compliance)

Note: Exact BTPEA credit pricing and discount tier details are not publicly disclosed. Contact your SAP account executive for a formal quote.

Summary#

SAP BTP licensing is not a single decision — it is a layered set of choices that should reflect an organization’s current usage certainty, service breadth, and growth trajectory. BTPEA is the current standard for consumption-based access and the only path to SAP’s latest innovations. CPEA remains valid for existing customers but no longer receives new services. PayG offers the lowest barrier to entry with no commitment. Subscriptions serve specific, stable workloads. And for RISE/GROW customers, bundled BTP credits are a starting point — not a ceiling.

Understanding the mechanics of each model before signing a contract, and establishing governance practices for credit consumption, are the two most practical steps any organization can take to control BTP costs as adoption grows.

FAQ#

Q: Can I use BTPEA and CPEA in the same Global Account? A: No. BTPEA and CPEA cannot coexist within a single Global Account. Two separate Global Accounts are required if both models are needed simultaneously.

Q: What happens if I run out of credits before my contract ends? A: Usage beyond your available credit balance results in overages, which are invoiced monthly at SAP list prices. To avoid this, set BTP Cockpit alerts and consider negotiating overage pricing protections at contract signing.

Q: If I stay on CPEA, what am I missing? A: CPEA’s service catalog was frozen as of April 2024. Any new SAP BTP service introduced after that date — including certain AI capabilities and SAP Analytics Cloud (public system option) — will only be available under BTPEA.

Q: Does RISE with SAP cover all my BTP needs? A: For basic extensions and integrations, the bundled CPEA credits in RISE are often sufficient. For substantial BTP usage — advanced integrations, data analytics, AI services, or large-scale custom development — a separate BTPEA agreement is typically required.

Q: Is switching from Pay-As-You-Go to BTPEA technically disruptive? A: No. Existing services and subaccounts are preserved during the transition. The switch is a commercial change; no technical migration or reconfiguration is needed.

Q: What is the difference between Trial and Free Tier? A: Trial is an account type — non-commercial, 90-day, deleted at expiry. Free Tier is a set of service plans within a commercial enterprise account (BTPEA or PayG) with no time limit, supporting genuine development and testing work.

References#

1. SAP BTP Pricing — accessed 2026-05-06
2. Get Started with SAP BTP Enterprise Accounts — SAP Developers — accessed 2026-05-06
3. SAP Experts Detail New SAP BTPEA — ASUG — accessed 2026-05-06
4. SAP BTP Licensing – How Does It Work? — SAP Licensing Experts — accessed 2026-05-06
5. SAP BTP Licensing Models: PayG, Subscription, and CPEA — Redress Compliance — accessed 2026-05-06
6. SAP BTP Licensing Explained: Custom Development and Integration Costs — Redress Compliance — accessed 2026-05-06
7. RISE with SAP — A Contractual and Commercial Perspective — ITAA — accessed 2026-05-06
8. RISE with SAP in 2026: What Changed — Redress Compliance — accessed 2026-05-06
9. SAP BTP Trial and Free Tier — SAP — accessed 2026-05-06
10. SAP BTP License Types for IT Leaders — SAP Licensing Experts — accessed 2026-05-06
11. CPEA Consumption Tips — SAP Licensing Experts — accessed 2026-05-06
12. Difference Between GROW and RISE — LeverX — accessed 2026-05-06
13. Free Tier Account — SAP Community — accessed 2026-05-06

What to Read Next#

This site organizes BTP knowledge into the following structure: