SAP Business Technology Platform is central to every S/4HANA and RISE deployment — yet its licensing model remains opaque to most buyers. Understanding BTP credits, entitlements, and the CPEA/BTPEA commercial framework is essential for controlling costs and negotiating effectively.
SAP Business Technology Platform (BTP) is SAP's unified cloud platform for integration, extension development, data management, analytics, and artificial intelligence. It serves as the technical foundation for connecting SAP applications with each other and with third-party systems, and for building custom extensions to SAP functionality without modifying core SAP code.
BTP consolidates several previously separate SAP platform products — SAP Cloud Platform, SAP Integration Suite (formerly SAP PI/PO cloud), SAP Analytics Cloud, SAP HANA Cloud, and others — under a single commercial and technical umbrella. For organisations on S/4HANA or RISE, BTP is not optional: it is the prescribed platform for integration development, cloud-to-cloud connectivity, and SAP's "clean core" extension philosophy.
This guide is part of our comprehensive SAP license negotiation guide. For BTP in the context of RISE, see our RISE with SAP review. For the integration aspects specifically, our S/4HANA migration negotiation guide covers BTP integration scope and cost modelling.
SAP BTP is licensed through a credit-based commercial model. Rather than purchasing individual BTP services separately, customers purchase a block of BTP credits — a flexible commercial currency that can be applied across the BTP service catalogue. This model is designed to provide flexibility, but in practice it creates complexity that makes cost control and forecasting difficult.
Want independent help negotiating better terms? We rank the top advisory firms across 14 vendor categories — free matching, no commitment.
Each BTP service consumes credits at a rate that varies by service and consumption metric. For example, the SAP Integration Suite consumes credits based on the number of API calls, message packages processed, or integration flows executed. SAP Analytics Cloud consumes credits per session or user. HANA Cloud consumes credits based on compute hours and storage volume. The credit consumption rates for each service are published in SAP's commercial price list and service catalogue documentation.
Credits are purchased upfront as part of the BTP enterprise agreement. The agreement specifies a total credit entitlement over the contract period (typically 1–3 years) and a credit consumption schedule. Unused credits at the end of the contract period are typically forfeited — they do not roll over. Credits consumed in excess of the contracted volume attract overage charges, priced at SAP's standard retail credit rate rather than the discounted contracted rate, which is typically 3–5 times higher.
The most common BTP commercial failure mode is underestimating credit consumption during scoping, exhausting contracted credits mid-year, and then paying overage rates for the remainder of the period. This can turn a well-negotiated BTP contract into a significant budget overrun. Rigorous consumption forecasting before signing is non-negotiable.
Two successive commercial frameworks govern BTP credit purchases. Understanding which you have — or which you are being offered — affects your commercial flexibility and risk profile.
CPEA is the predecessor framework, still in active use for many enterprise customers who adopted BTP before 2022. Under CPEA, credits are purchased at a fixed rate with annual credit pools. The key characteristic of CPEA is that it operates as a prepay model: customers commit to a credit volume upfront and consume from that pool. CPEA agreements typically include a catalogue of eligible services and service-specific consumption metrics.
BTPEA is SAP's current commercial framework for BTP, introduced to simplify and standardise the commercial model. BTPEA operates on a similar credit-pool basis but with updated service catalogue coverage, improved commercial flexibility in some respects, and better alignment with SAP's current BTP architecture. Key differences from CPEA include broader service catalogue coverage under a single credit pool, updated consumption metrics for newer BTP services (particularly AI and data management), and annual credit true-up provisions in some agreement structures.
| Dimension | CPEA | BTPEA |
|---|---|---|
| Commercial framework age | Legacy (pre-2022) | Current (2022+) |
| Credit pool flexibility | Annual pools, less flexible | Multi-year pooling options |
| Service catalogue coverage | Older services, gaps | Comprehensive, updated |
| AI/data services inclusion | Limited | Full catalogue |
| Migration path | Can migrate to BTPEA | N/A — current standard |
| Overage risk | Higher — annual expiry | Moderate — depends on terms |
The BTP service catalogue includes over 90 services organised into capability areas. The most commercially significant categories for typical enterprise deployments are integration, data and analytics, application development, and AI services.
Get the IT Negotiation Playbook — free
Used by 4,200+ IT directors and procurement leads. Oracle, Microsoft, SAP, Cloud — all covered.
The central integration platform for connecting SAP and non-SAP applications. Integration Suite is the cloud successor to SAP PI/PO and is mandatory for most RISE deployments where integrations with third-party systems are required. Credit consumption is based on integration flows (iFlows) deployed, API calls processed, and message packages executed. Integration Suite is frequently the highest single credit consumer in a BTP deployment.
SAP's cloud BI and planning platform. SAC is separately licensed either as a standalone subscription (per-user, per-year) or as a BTP service consumed through credits. The credit model applies to SAC used within BTP's commercial framework; standalone SAC purchases follow a different pricing structure. Credit consumption for SAC depends on the number of users, sessions, and the specific SAC editions (BI, planning, or predictive) in use.
A managed HANA database service on BTP, used for analytics, application data persistence, and as the foundation for SAP Data Warehouse Cloud (now SAP Datasphere). HANA Cloud credit consumption is based on compute capacity (HANA units) and storage volume. For organisations building embedded analytics on BTP outside of the core S/4HANA HANA database, HANA Cloud can become a significant credit consumer.
SAP Build Apps (formerly AppGyver), SAP Build Process Automation, and SAP Build Work Zone constitute SAP's low-code/no-code application development suite. Credit consumption for these services is based on active users, process executions, and in some cases the number of applications deployed. These services are increasingly strategic for organisations adopting SAP's clean core extension approach.
SAP AI Core provides the runtime for deploying and running AI models on BTP, while Joule is SAP's generative AI copilot integrated across SAP applications. Credit consumption for AI services is based on compute resources consumed by model execution and API calls. As organisations deploy more AI features within SAP applications, AI service credit consumption is growing rapidly and was not anticipated in most CPEA or early BTPEA agreements.
RISE with SAP includes a standard BTP credit entitlement as part of the subscription bundle. The size of this entitlement — and critically, what it actually covers — is one of the most commercially contentious aspects of RISE negotiation.
SAP's standard RISE BTP inclusion is structured as a block of BTP credits sized to cover the "foundation" integration and extension use cases for an S/4HANA deployment: the standard pre-built integrations between S/4HANA and other SAP cloud applications, basic process automation, and a limited set of Integration Suite iFlows. For organisations with complex integration landscapes — significant third-party system connectivity, custom extensions, advanced analytics workloads — the standard RISE BTP entitlement is almost always insufficient.
The standard BTP entitlement in RISE typically covers: access to SAP Integration Suite with a defined iFlow and API call allowance, SAP Business Network Starter Pack connectivity, basic SAP Build Work Zone access for the standard SAP Fiori launchpad, and a limited HANA Cloud allocation for non-production purposes. It does not cover custom Integration Suite iFlows developed for third-party connectivity at production volumes, SAP Analytics Cloud at meaningful user scales, SAP AI Core and Joule beyond basic entitlements, or substantial SAP Datasphere/Data Warehouse Cloud workloads.
In our experience reviewing RISE agreements, the standard BTP credit entitlement covers approximately 20–40% of the actual BTP consumption required for a typical enterprise S/4HANA deployment with a complex integration landscape. The remaining 60–80% must be purchased as additional BTP credits — an expense that is rarely fully modelled during the RISE business case.
The BTP credit entitlement within RISE is negotiable. Before signing a RISE agreement, conduct a thorough BTP consumption assessment covering all planned integration scenarios, custom extension workloads, analytics user volumes, and AI service usage. Then negotiate the RISE BTP entitlement against this forecast — ensuring sufficient credits are included in the base subscription rather than purchased at separate (and higher) overage rates post-signature.
BTP cost overruns are common and often significant. Understanding the typical overrun scenarios allows you to model and mitigate them before they occur.
The most frequent overrun driver is integration message volume. SAP Integration Suite credits are consumed per message package (typically 1,000 messages). Organisations that underestimate the volume of integration messages generated by their ERP/CRM/procurement/ecommerce landscape routinely exhaust Integration Suite credits within 6–9 months of a 12-month credit period.
As SAP embeds Joule and AI capabilities directly into S/4HANA and other cloud applications, AI service credit consumption is growing unexpectedly. Customers who signed RISE or BTP agreements before Joule's widespread rollout may find their credit entitlements do not account for this workload at all.
SAP Analytics Cloud adoption often expands faster than forecast as business users discover its capabilities. If SAC is licensed through BTP credits rather than as a standalone subscription, rapid user adoption can exhaust analytics credits well ahead of schedule.
Concerned about BTP credit adequacy in your RISE or BTP agreement?
BTP commercial terms are negotiable, and organisations that approach BTP as a standard "take it or leave it" SAP offering systematically overpay. Key negotiation points include credit volume and price, service catalogue scope, credit carry-forward provisions, and overage rates.
Like all SAP products, BTP credits are discounted from list price based on volume commitment and strategic account importance. Larger credit commitments attract larger discounts. The most effective approach is to model your BTP consumption conservatively, commit to a volume that covers your realistic minimum, and negotiate volume step-up provisions that allow you to add credits at the same or better discount rate if consumption exceeds forecast.
Unused credits that expire at year-end represent pure commercial waste. Negotiating a carry-forward provision — typically 10–25% of annual credits — provides buffer against consumption timing variability. This is a standard ask in BTP negotiations and is often granted for accounts above a certain credit volume threshold.
If you do exceed your contracted credit volume, the rate at which overage is priced can be capped in the agreement. Rather than defaulting to full list price (3–5x the contracted rate), negotiate a cap of 120–150% of your contracted per-credit rate for overages. This significantly reduces the financial consequence of consumption overruns.
Once deployed, BTP costs can be actively managed through consumption monitoring and architecture decisions.
Implement SAP BTP cockpit monitoring to track credit consumption by service and by BTP subaccount in near-real-time. Set consumption alerts at 70% and 90% of the credit period allocation. Review integration flow design for efficiency — badly designed iFlows that generate unnecessary messages are a common source of avoidable credit consumption. Consider whether certain analytics workloads could run on embedded S/4HANA analytics (which does not consume BTP credits) rather than SAP Analytics Cloud.
For RISE customers specifically, review the service catalogue inclusions in your RISE agreement against your actual BTP service usage. Some services that you are consuming from BTP credits may actually be included in your RISE base entitlement — billing configuration errors of this type are not uncommon and can result in unnecessary credit consumption for services you are already paying for.
Don't sign a RISE or BTP agreement without an independent credit assessment. The gap between included entitlement and actual need is often measured in millions.