FAQ Consumption-based commercial model CPEA & Cloud Credits
PUBLIC
Frequently Asked Questions | PUBLIC
Business Technology Platform | Cloud Platform Enterprise Agreement
Consumption-based commercial model CPEA & Cloud Credits
Date: March 2026
Frequently Asked Questions | PUBLIC
Business Technology Platform | Cloud Platform Enterprise Agreement
Consumption-based commercial model CPEA & Cloud Credits
Date: March 2026
© 2026 SAP SE or an SAP affiliate company. All rights reserved. See Legal Notice on www.sap.com/legal-notice for use terms, disclaimers, disclosures, or restrictions related to this material. 2 / 7
PUBLIC
GENERAL COMMERCIAL MODEL
What is the new
consumption-based
model in a nutshell?
The objective of the model is to create one rich and simple customer
experience for finding, trying, buying, and consuming cloud services
from SAP and partners for net-new and installed base customers. It
allows customers to integrate, extend and innovate own applications
with business and technical functionality, offered as cloud services in a
flexible way.
There is no need to license a SAP BTP service individually anymore.
Cloud services can be used when demand arises and be retired if not
needed anymore. Charges incur on actual usage and will be charged
monthly against the prior purchased cloud credit.
What are the benefits for
customers?
The SAP Business Technology Platform is the ultimate foundation to
intelligently connect people, things and businesses during all phases
of Build – Extend – Integrate.
This new consumption-based model offers customers:
• Simplified cloud engagement experience with to explore, procure
and provision SAP BTP.
• Flexibility in using eligible services for any SAP BTP use case.
Customers can pick and choose the services they need knowing
they have investment security in the cloud credits for SAP BTP.
Agility – direct and rapid access to newly released business- and
technical services for rapid application development and
innovation.
• Innovation – focus on innovation and not administrative overhead.
How does the cloud credit
model work?
A customer who meets the minimal commitment threshold (10.000
EUR annual spend or local currency equivalent. For details reach out
to your account executive) is eligible to sign the CPEA. This agreement
entitles to an annual amount of consumption of eligible cloud services.
The contract is renewable (typically a one- to three-year contract,
divided in annual credit periods).
Services consumed under this contract use a dedicated global
account on SAP BTP cockpit. The prepaid amount of service
consumption in each credit period is the “initial cloud credits balance”.
Flexibility and choice:
• Customers are entitled to consume any of the eligible cloud
services, in any of the countries and technical regions in which the
program has been released.
• Services are available per data center. Customers will have a
choice on the underlying infrastructure providers (Multi-Cloud:
SAP data centers, AWS, Azure and/or Google Cloud), according to
the availability.
• The service detail page on Discovery Center depicts per service in
which location the service is available. The charges for the
PUBLIC
GENERAL COMMERCIAL MODEL
What is the new
consumption-based
model in a nutshell?
The objective of the model is to create one rich and simple customer
experience for finding, trying, buying, and consuming cloud services
from SAP and partners for net-new and installed base customers. It
allows customers to integrate, extend and innovate own applications
with business and technical functionality, offered as cloud services in a
flexible way.
There is no need to license a SAP BTP service individually anymore.
Cloud services can be used when demand arises and be retired if not
needed anymore. Charges incur on actual usage and will be charged
monthly against the prior purchased cloud credit.
What are the benefits for
customers?
The SAP Business Technology Platform is the ultimate foundation to
intelligently connect people, things and businesses during all phases
of Build – Extend – Integrate.
This new consumption-based model offers customers:
• Simplified cloud engagement experience with to explore, procure
and provision SAP BTP.
• Flexibility in using eligible services for any SAP BTP use case.
Customers can pick and choose the services they need knowing
they have investment security in the cloud credits for SAP BTP.
Agility – direct and rapid access to newly released business- and
technical services for rapid application development and
innovation.
• Innovation – focus on innovation and not administrative overhead.
How does the cloud credit
model work?
A customer who meets the minimal commitment threshold (10.000
EUR annual spend or local currency equivalent. For details reach out
to your account executive) is eligible to sign the CPEA. This agreement
entitles to an annual amount of consumption of eligible cloud services.
The contract is renewable (typically a one- to three-year contract,
divided in annual credit periods).
Services consumed under this contract use a dedicated global
account on SAP BTP cockpit. The prepaid amount of service
consumption in each credit period is the “initial cloud credits balance”.
Flexibility and choice:
• Customers are entitled to consume any of the eligible cloud
services, in any of the countries and technical regions in which the
program has been released.
• Services are available per data center. Customers will have a
choice on the underlying infrastructure providers (Multi-Cloud:
SAP data centers, AWS, Azure and/or Google Cloud), according to
the availability.
• The service detail page on Discovery Center depicts per service in
which location the service is available. The charges for the
© 2026 SAP SE or an SAP affiliate company. All rights reserved. See Legal Notice on www.sap.com/legal-notice for use terms, disclaimers, disclosures, or restrictions related to this material. 3 / 7
PUBLIC
consumed services are subtracted monthly from the cloud credits
balance.
Cloud credits balance:
• Customers receive a monthly balance statement, that shows them
the consumption, and the balance of credits for the current credit
period.
• Unused cloud credits expire at the end of each credit period.
• Overage (usage beyond available cloud credits) is invoiced
according to the list price, subject to the price guarantee.
• A detailed break-down of service consumption and subaccounts is
further provided in the SAP BTP cockpit.
Entitlement management:
• Administrators can use the SAP BTP cockpit to set up SAP BTP
sub-accounts for different teams and projects to assign specific
service entitlements and to regulate and monitor how the eligible
cloud services are used throughout their organization.
SERVICES SCOPE AND HANDLING
Which services are
applicable under the
Cloud Platform Enterprise
Agreement (CPEA)?
The list of services is always available in the SAP Discovery Center -
Service Catalog. A summary of all services with their respective metric
and prices is available in the SAP Business Technology Platform - Price
List.
The Services Catalog provide a detailed description of its functional
scope for each cloud service, but also the available service plans in
the respective data centers. For each service it is clearly marked
whether the service is available only through subscription or also as
through the consumption-based model.
How is service
consumption managed?
Once the Cloud Platform Enterprise Agreement (CPEA) is signed,
customer administrators get access to the SAP BTP cockpit to view all
currently available services in a global account.
Here they can manage their service consumption across subaccounts
and see the actual consumption. Furthermore, monthly balance
statements are sent to the commercial contact mentioned in the CPEA
to provide transparency on the charges incurred. Additionally, the
balance statements are available via SAP for Me.
What happens with my
existing subscription
contracts?
There is no change. Existing contracts remain unchanged for the time
of their duration. SAP ensures business continuity for the contracts.
The subscription model and CPEA will co-exist for the time being to
give customers a broader choice.
PUBLIC
consumed services are subtracted monthly from the cloud credits
balance.
Cloud credits balance:
• Customers receive a monthly balance statement, that shows them
the consumption, and the balance of credits for the current credit
period.
• Unused cloud credits expire at the end of each credit period.
• Overage (usage beyond available cloud credits) is invoiced
according to the list price, subject to the price guarantee.
• A detailed break-down of service consumption and subaccounts is
further provided in the SAP BTP cockpit.
Entitlement management:
• Administrators can use the SAP BTP cockpit to set up SAP BTP
sub-accounts for different teams and projects to assign specific
service entitlements and to regulate and monitor how the eligible
cloud services are used throughout their organization.
SERVICES SCOPE AND HANDLING
Which services are
applicable under the
Cloud Platform Enterprise
Agreement (CPEA)?
The list of services is always available in the SAP Discovery Center -
Service Catalog. A summary of all services with their respective metric
and prices is available in the SAP Business Technology Platform - Price
List.
The Services Catalog provide a detailed description of its functional
scope for each cloud service, but also the available service plans in
the respective data centers. For each service it is clearly marked
whether the service is available only through subscription or also as
through the consumption-based model.
How is service
consumption managed?
Once the Cloud Platform Enterprise Agreement (CPEA) is signed,
customer administrators get access to the SAP BTP cockpit to view all
currently available services in a global account.
Here they can manage their service consumption across subaccounts
and see the actual consumption. Furthermore, monthly balance
statements are sent to the commercial contact mentioned in the CPEA
to provide transparency on the charges incurred. Additionally, the
balance statements are available via SAP for Me.
What happens with my
existing subscription
contracts?
There is no change. Existing contracts remain unchanged for the time
of their duration. SAP ensures business continuity for the contracts.
The subscription model and CPEA will co-exist for the time being to
give customers a broader choice.
© 2026 SAP SE or an SAP affiliate company. All rights reserved. See Legal Notice on www.sap.com/legal-notice for use terms, disclaimers, disclosures, or restrictions related to this material. 4 / 7
PUBLIC
How can I consume
services under the new
Cloud Platform Enterprise
Agreement (CPEA)?
New CPEA contracts will trigger the creation of a new global account
that provides access to all eligible services in the respective data
centers. Subsequently customers need to structure this global
account into sub-accounts and other related artifacts (e.g. directories
and/or spaces). Customers are free to choose the services they
require for their implementation, scale them up or even retire them, if
there is no need anymore. The CPEA provides the full flexibility for
adopting SAP BTP.
Can I combine our existing
subscription contracts
with a Cloud Platform
Enterprise Agreement
(CPEA)?
The CPEA, Pure-Pay-as-you-Go and the subscription model represent
three commercial models. Each of the models require a specific
contract and therefore it is not possible to combine these models
under one agreement. Also, from a technical perspective it is required
to separate the subscription and the consumption-based services in
segregated global accounts. Technically integration is possible, but
subject to technical restrictions and limitations.
Can I transform my
existing subscription
contract into CPEA?
Yes, a subscription trade-in program is available. This program is the
path to CPEA for existing SAP BTP customers to gain flexibility for
adopting additional services.
What if the services I
need are not on the list of
eligible cloud services
yet?
The list of eligible services is extended continuously. Available
services for the consumption-based license model are explicitly
marked in the SAP Discovery Center - Services Catalog.
If a service is not marked, it is either in development to become ready
for the consumption-based model or it does not qualify to be metered
and therefore will not get transformed.
What happens if
consumption exceeds my
prepaid cloud credits?
Any usage beyond the available cloud credits for the respective
period results in overages and will be invoiced according to the list
price. SAP will send these invoices monthly.
To avoid this, customers have the option to purchase at any point of
time top-up cloud credits at the same conditions as for the initial
purchase of the cloud credit. SAP BTP cockpit provides insights on the
consumption to detect overage early enough. For customers using the
new SAP BTP Cloud Management Tools (aka Feature Set B) there are
APIs available to detect overage programmatically (see blog).
PUBLIC
How can I consume
services under the new
Cloud Platform Enterprise
Agreement (CPEA)?
New CPEA contracts will trigger the creation of a new global account
that provides access to all eligible services in the respective data
centers. Subsequently customers need to structure this global
account into sub-accounts and other related artifacts (e.g. directories
and/or spaces). Customers are free to choose the services they
require for their implementation, scale them up or even retire them, if
there is no need anymore. The CPEA provides the full flexibility for
adopting SAP BTP.
Can I combine our existing
subscription contracts
with a Cloud Platform
Enterprise Agreement
(CPEA)?
The CPEA, Pure-Pay-as-you-Go and the subscription model represent
three commercial models. Each of the models require a specific
contract and therefore it is not possible to combine these models
under one agreement. Also, from a technical perspective it is required
to separate the subscription and the consumption-based services in
segregated global accounts. Technically integration is possible, but
subject to technical restrictions and limitations.
Can I transform my
existing subscription
contract into CPEA?
Yes, a subscription trade-in program is available. This program is the
path to CPEA for existing SAP BTP customers to gain flexibility for
adopting additional services.
What if the services I
need are not on the list of
eligible cloud services
yet?
The list of eligible services is extended continuously. Available
services for the consumption-based license model are explicitly
marked in the SAP Discovery Center - Services Catalog.
If a service is not marked, it is either in development to become ready
for the consumption-based model or it does not qualify to be metered
and therefore will not get transformed.
What happens if
consumption exceeds my
prepaid cloud credits?
Any usage beyond the available cloud credits for the respective
period results in overages and will be invoiced according to the list
price. SAP will send these invoices monthly.
To avoid this, customers have the option to purchase at any point of
time top-up cloud credits at the same conditions as for the initial
purchase of the cloud credit. SAP BTP cockpit provides insights on the
consumption to detect overage early enough. For customers using the
new SAP BTP Cloud Management Tools (aka Feature Set B) there are
APIs available to detect overage programmatically (see blog).
© 2026 SAP SE or an SAP affiliate company. All rights reserved. See Legal Notice on www.sap.com/legal-notice for use terms, disclaimers, disclosures, or restrictions related to this material. 5 / 7
PUBLIC
Can customers freely
choose and translocate
services between data
centers (DCs) with CPEA?
Yes, this is one of the major advantages of this model. Customers can
freely choose and switch between DCs through self-service activation
and deactivation.
Certain conditions apply though, for cloud services in the Neo domain.
For Cloud Foundry-based services, the activation and deactivations
are available and can be done in a flexible manner at customer’s
choice.
How do customers
integrate between
subscription-based and
CPEA based
environments?
If customers sign a CPEA contract they will receive a new global
account in which the activation, metering and billing of service usage
happens. This new global account can be integrated with existing
global accounts.
How fast and how often
can a customer switch
from one service to
another?
Following consumption logic is utilized when a calendar month /
billing cycle overlaps two contract phases:
• Usage is assigned to the first contract phase.
• Customer could pay for overage.
Example: 3-year contract starting October 15, 2019 until October 14,
2022. In this example the whole consumption of October will be
assigned to the first contract phase (month: October 1, 2020 –
October 14, 2020). November 2020 consumption will then be again
assigned to the calendar month / billing cycle (November 1, 2020 –
November 30, 2020).
Calendar month (=billing cycle): October 2020
Contract phase 1 Contract phase 2
Consumption
until October 14, 2020 from October 15, 2020
PUBLIC
Can customers freely
choose and translocate
services between data
centers (DCs) with CPEA?
Yes, this is one of the major advantages of this model. Customers can
freely choose and switch between DCs through self-service activation
and deactivation.
Certain conditions apply though, for cloud services in the Neo domain.
For Cloud Foundry-based services, the activation and deactivations
are available and can be done in a flexible manner at customer’s
choice.
How do customers
integrate between
subscription-based and
CPEA based
environments?
If customers sign a CPEA contract they will receive a new global
account in which the activation, metering and billing of service usage
happens. This new global account can be integrated with existing
global accounts.
How fast and how often
can a customer switch
from one service to
another?
Following consumption logic is utilized when a calendar month /
billing cycle overlaps two contract phases:
• Usage is assigned to the first contract phase.
• Customer could pay for overage.
Example: 3-year contract starting October 15, 2019 until October 14,
2022. In this example the whole consumption of October will be
assigned to the first contract phase (month: October 1, 2020 –
October 14, 2020). November 2020 consumption will then be again
assigned to the calendar month / billing cycle (November 1, 2020 –
November 30, 2020).
Calendar month (=billing cycle): October 2020
Contract phase 1 Contract phase 2
Consumption
until October 14, 2020 from October 15, 2020