SAP BTP Licensing:
The Complete Enterprise Guide for 2026

SAP Business Technology Platform is SAP's unified cloud platform for integration, data management, analytics, application development, and artificial intelligence. It sits at the centre of SAP's cloud strategy: every major SAP product — S/4HANA Cloud, RISE with SAP, SuccessFactors, Ariba, Concur — depends on BTP capabilities for integration and extension.

Before BTP, enterprises could choose not to engage deeply with SAP's cloud platform. With RISE with SAP and S/4HANA Cloud Private Edition, that choice is largely removed. RISE contracts bundle BTP credits as part of the commercial package — which sounds generous until you examine what those credits actually cover and what happens when you need capabilities beyond the bundle.

The critical shift is this: BTP is no longer optional for enterprise SAP customers. It is the integration bus, the extensibility layer, and increasingly the analytics platform. Understanding how SAP BTP licensing works is therefore not a technical question — it is a commercial imperative. Our RISE with SAP advisory service routinely identifies BTP over-commitment as the single largest source of avoidable spend in RISE contracts.

SAP sells BTP through three primary commercial structures, each with very different cost implications:

1. Pay-As-You-Go (Free Tier + Consumption)

SAP's entry-level BTP model allows limited service usage for free, with charges triggered above defined thresholds. While attractive in principle, the pay-as-you-go model lacks cost predictability and is inappropriate for enterprise production workloads. Cost overruns are common as teams develop applications without visibility into underlying consumption rates.

2. CPEA — Cloud Platform Enterprise Agreement

CPEA is the standard enterprise BTP contract. Under CPEA, the customer pre-purchases a block of cloud credits — typically expressed in euros or dollars — which can be allocated across any BTP service. Credits are consumed at service-specific rates published in SAP's Supplement for SAP BTP. Unused credits at the end of the subscription period are forfeited. SAP typically quotes three- or five-year CPEA commitments with discounts for volume and term length.

The CPEA model appears flexible but hides a fundamental trap: SAP prices services in credits, not in meaningful unit costs, making it extremely difficult to forecast actual consumption against committed credit pools. Most enterprises over-commit at the start and face significant unused credit write-offs at the end of each contract year.

3. Subscription-Based Licensing

Specific BTP services — notably SAP Integration Suite, SAP Build Work Zone, SAP Data Intelligence, and SAP Analytics Cloud — are available as standalone subscriptions with fixed monthly or annual fees. These are priced by capacity tier (messages per month, users, data volumes) rather than flexible credits. Subscription licences are more predictable but less flexible than CPEA.

Understanding SAP BTP licensing requires mastering the distinction between three things SAP often conflates in sales conversations: entitlements, services, and consumption units.

Entitlements

An entitlement is the right to use a specific BTP service. Entitlements are granted either as part of a CPEA subscription (which grants access to all services, with consumption billed against the credit pool) or as specific service licences. An enterprise with a CPEA contract is entitled to use any BTP service listed in the Supplement — but must allocate credits in advance through the BTP Cockpit.

Services

BTP contains over 150 individual services spanning integration, analytics, data management, development tools, AI capabilities, and security. The most commercially significant include:

• SAP Integration Suite — message-based integration with SAP and third-party systems. Priced per integration flow executions per month.
• SAP Build Work Zone — the unified business site and Fiori Launchpad replacement. Priced per active user per month.
• SAP HANA Cloud — cloud-native in-memory database. Priced by compute capacity unit (vCPU-equivalent) per hour.
• SAP Analytics Cloud (SAC) — business intelligence and planning. Priced by named user type (Planning Professional, Business Intelligence Professional, Business Intelligence Standard).
• SAP Datasphere — data fabric and warehousing. Priced by capacity units (compute + storage).
• SAP AI Core / AI Launchpad — AI model training and serving. Priced by resource plan (compute hours).

Consumption Units and Credits

Under CPEA, all services are priced in credits. One credit does not equal one euro or dollar — it equals a service-specific quantity. SAP publishes a Credit Calculation Guide in the BTP Supplement, but the conversion rates are complex and change with each contract renewal. For example, 1,000 Integration Suite message executions might consume 0.2 credits, while 1 HANA Cloud compute unit consumes 12 credits per hour. These rates are not publicly advertised, and SAP's pre-sales teams rarely provide them proactively during contract negotiations.

Most enterprises understand the headline BTP price they agreed. Few understand where costs escalate beyond the original commitment. These are the most common sources of unplanned BTP spend we encounter.

1. RISE BTP Bundle Under-Sizing

RISE with SAP contracts include a BTP entitlement — but the included credits are sized around SAP's standard assumptions, not around the customer's actual integration and extensibility requirements. SAP deliberately sizes RISE BTP bundles conservatively, expecting customers to purchase additional credits. We have reviewed RISE contracts where the included BTP allocation lasted less than six months before the customer needed to purchase top-ups at unfavourable list prices.

2. Integration Suite Message Overruns

SAP Integration Suite is the most commonly under-estimated BTP cost driver. As enterprises migrate their middleware layer to BTP, message volumes grow faster than projected. A manufacturer moving 50 integrations from an on-premise middleware platform to Integration Suite may contract for 10 million messages per month based on current volumes — but after go-live, third-party integrations, new API consumers, and monitoring messages push actual volumes to 40 million within 12 months. The overage charges are significant.

3. HANA Cloud Compute Escalation

SAP HANA Cloud charges by the hour for active compute capacity. Enterprises frequently provision more capacity than needed in development and quality assurance environments — and fail to deprovision it when not in use. HANA Cloud compute charges running 24/7 in non-production environments can consume 30–40% of a CPEA credit pool within the first year.

4. SAP Analytics Cloud User Creep

SAC is sold on named user licences. Planning Professional users — required for anyone interacting with budgeting and forecasting models — cost significantly more than Business Intelligence Standard users. SAP's pre-sales teams routinely propose more Planning Professional licences than needed; we routinely right-size these to reduce SAC spend by 20–35%.

5. Expired Credits With No Rollover

CPEA credits expire at the end of each subscription year with no rollover. SAP does not notify enterprises proactively when they are approaching year-end with significant unused credits. We have seen enterprises forfeit hundreds of thousands of euros in unused credits simply because no internal process existed to track consumption and accelerate usage before the expiry date.

SAP BTP contracts are negotiable — more so than SAP's sales process implies. The following negotiating positions are achievable for enterprise buyers who push back with evidence and expertise.

Request Transparent Credit Pricing

Demand that SAP provide the Credit Calculation Guide for every service you intend to consume. Convert SAP's credit prices into actual service unit costs (cost per 1,000 Integration Suite executions, cost per HANA Cloud compute hour) and compare against market rates. This analysis consistently reveals that SAP's BTP credit pricing is 25–50% above comparable hyperscaler costs for equivalent compute and integration capabilities.

Negotiate a Consumption Buffer

Build a minimum 20% buffer into your CPEA credit pool based on your modelled consumption. This is especially important in year one, when actual usage patterns are unknown. SAP will offer discounts for increased commitment — take them only when your consumption model justifies the volume.

Insist on Credit Rollover

Credit rollover — the ability to carry unused credits into the next subscription year — is negotiable. SAP's standard terms prohibit it. In competitive situations or large-volume renewals, SAP has agreed to partial rollover provisions. This single clause can save enterprises hundreds of thousands of euros in forfeited credits.

Challenge RISE BTP Bundle Size

If your BTP entitlement is included within a RISE with SAP contract, model your expected BTP usage before signing and push SAP to size the bundle accordingly. Do not accept SAP's standard sizing without independent validation — the standard RISE bundle is designed to be insufficient, creating a dependency on additional BTP purchases.

Benchmark SAC User Licences

SAP Analytics Cloud user pricing is often inflated in initial proposals. Push back on the ratio of Planning Professional to Business Intelligence licences; most organisations over-budget on the premium user type. We consistently achieve 20–35% reductions in SAC licensing by right-sizing user classifications before contract signature.

BTP is increasingly part of SAP's audit and compliance review process. Unlike traditional Named User audits conducted through USMM and LAW, BTP compliance is assessed through consumption data pulled directly from the BTP Cockpit and service-specific usage reports. SAP has full visibility into your BTP consumption through its cloud platform telemetry — there is no equivalent of the on-premise USMM measurement that you can control.

The most common BTP compliance findings relate to service usage outside the contracted entitlement scope — particularly when developers enable BTP services in sub-accounts without proper governance controls. An enterprise with a CPEA subscription may have contracted for specific services, while developers have enabled additional services in development subaccounts that were not included in the commercial agreement. SAP may characterise this as an unlicensed use of BTP services and raise a back-licence claim accordingly.

The defence against this is straightforward but requires discipline: implement BTP subaccount governance, enforce service entitlement approvals through a central Cloud Centre of Excellence or SAP Basis team, and conduct quarterly internal BTP consumption reviews. If you are approaching an SAP audit and concerned about your BTP position, our SAP audit defence service includes a BTP compliance assessment as part of the pre-audit preparation. Review our comprehensive SAP audit guide to understand the full audit process.

What is included in a RISE with SAP BTP entitlement?

RISE with SAP includes a BTP entitlement that covers core integration capabilities (SAP Integration Suite at a base tier), SAP Build Work Zone Standard Edition, and a pool of general cloud credits. The exact allocation varies by RISE contract size and is negotiated in the Order Form. Standard RISE BTP allocations are typically insufficient for enterprises with complex integration landscapes — always model your actual requirements before accepting the default bundle.

Can unused SAP BTP credits be rolled over to the next year?

Not by default. SAP's standard CPEA terms forfeit unused credits at the end of each subscription year. Credit rollover is negotiable in competitive contract situations or at renewal, but requires explicit contractual language. Without it, any unused credits simply expire. We recommend tracking BTP consumption monthly against your annual credit pool to avoid year-end forfeitures.

How is SAP HANA Cloud different from SAP HANA on-premise licensing?

On-premise SAP HANA is licensed on a capacity model — you purchase the right to a specific amount of memory (e.g., 128 GB, 512 GB). SAP HANA Cloud is consumption-based: you pay per compute capacity unit per hour of active use. This creates significant cost variability. Systems running 24/7 in non-production environments will accumulate costs rapidly. Disciplined scheduling of HANA Cloud instances — stopping them outside working hours — can reduce costs by 60–70% in development and QA environments.

What is the difference between SAP Integration Suite and SAP Cloud Integration?

SAP Cloud Integration (formerly HCI, or HANA Cloud Integration) is now a capability within SAP Integration Suite. SAP Integration Suite is the expanded umbrella service that includes Cloud Integration, API Management, Event Mesh, Integration Advisor, and Open Connectors. Enterprises with legacy Cloud Integration subscriptions may need to renegotiate their contracts to ensure they are mapped to the correct Integration Suite tier as SAP phases out standalone Cloud Integration sales.

How does SAP audit BTP usage?

SAP has direct telemetry visibility into BTP consumption through the platform's native monitoring infrastructure. During an audit, SAP will request consumption reports from the BTP Cockpit and service-specific usage data. Unlike on-premise audits where you run USMM, BTP audit data is generated by SAP's systems. This means the onus is on the customer to ensure that service usage aligns with contracted entitlements at all times — there is no opportunity to remediate after the fact as there is with Named User audits.