SAP BTP, decoded. The credit model, the cockpit, the renewal.

SAP Business Technology Platform consolidates integration, data, and extensibility services on a single consumption model. Treat the credit balance like a budget. Govern it like a balance sheet.

SAP Business Technology Platform, branded as SAP BTP, is the publisher's umbrella for integration, data, application development, and the analytics services that sit alongside S/4HANA. It is sold on a Cloud Credit model, governed by the cockpit, and billed against an annual commit.

BTP is also the fastest growing cost line on most SAP estates. The integration mandate around RISE has pushed connector volumes higher. The Build family has expanded the application development footprint. The AI services have introduced a new variable cost line that did not exist three years ago.

This hub pulls together the buyer side view of BTP. Read the related SAP knowledge hub, the SAP advisory practice, the SAP RISE knowledge hub, and the wider SAP pillar hub for the renewal and audit context.

What SAP BTP actually is

SAP positions BTP as the strategic platform underneath S/4HANA. The technical reality is a managed service estate billed on credits.

The service families

BTP is not a single product. It is a portfolio of more than fifty services grouped into a small number of families.

• Integration Suite. Cloud Integration, API Management, Open Connectors, Integration Advisor, Trading Partner Management.
• Build. SAP Build Apps, SAP Build Process Automation, SAP Build Code, SAP Build Work Zone.
• Data and Analytics. SAP Datasphere, SAP HANA Cloud, SAP Analytics Cloud, Data Intelligence.
• AI services. Joule, Document Information Extraction, Translation Hub, the AI Foundation services.
• Foundation services. Identity, Authorization, Connectivity, Job Scheduling, Application Logging.

How BTP relates to S/4HANA

BTP is technically separate from S/4HANA. Commercially the two are tightly linked.

RISE bundles include a small allocation of BTP credits. The allocation is rarely enough for an enterprise estate. Most customers carry a separate BTP commit on top of the RISE contract.

Read the related SAP RISE knowledge hub for how the bundled allocation works and where the gap usually opens.

The BTP credit model

Cloud Credits versus Pay As You Go

BTP is sold on one of two commercial models. The choice shapes every other lever in the contract.

• Cloud Credits. Annual commit. Credits draw down against published service rates. Unused credits expire at the end of the contract year.
• Pay As You Go. Retail rate, billed monthly. No commit, no discount.
• Enterprise Agreement variant. Multi year commit with stepped credit increases. The headline discount sits here.

Service rates and the rate card

Every BTP service has a published rate card. Rates are quoted in credits per unit of consumption.

The unit varies by service. Integration Suite is priced per message. API Management is priced per million calls. HANA Cloud is priced per gigabyte memory hour.

The rate card moves. SAP publishes the current version on the BTP discovery centre. Buyer side practice is to lock the rate card to the contract effective date.

Subaccount and directory model

Credits sit at the global account level. Consumption is tracked through directories and subaccounts.

• Global account. The contract entity. One per Enterprise Agreement.
• Directories. Optional grouping. Used to map business units or environments.
• Subaccounts. Where workloads live. Each subaccount carries its own consumption metering.

Service map and how each line gets billed

Integration Suite billing mechanics

Integration Suite is metered on messages. A message is one inbound or outbound exchange across an iflow.

Volume is volatile. A single batch job can move millions of messages overnight. Right sizing requires a baseline period of at least three months.

Read the related SAP BTP integration mandate costs guide for the volume sizing framework.

Build billing mechanics

Build is metered differently across its three sub products.

• Build Apps. Per active user per month. Active is defined narrowly.
• Build Process Automation. Per automated process unit. The unit definition is dense.
• Build Code. Per developer seat with a credit overlay for runtime.

Data and AI service billing

Datasphere, HANA Cloud, and the AI services run on capacity units. Capacity units are an abstraction over memory, storage, and compute.

Datasphere starts at the Standard tier and scales by Capacity Units. HANA Cloud is metered per gigabyte memory hour with a separate storage line.

The AI services include Joule and the document services. Most are credit consuming. Volume forecasting on AI services has been the largest source of overrun in the past twelve months.

Governance framework

First ninety days

The first ninety days set the governance tone for the whole term.

• Appoint a BTP cockpit owner. One named person.
• Configure cost alerts at seventy, eighty five, and ninety five percent of the annual commit.
• Establish a monthly consumption review with finance and the SAP architecture lead.
• Document the production, non production, and sandbox subaccount split.
• Lock the rate card in writing to the contract effective date.

Quarterly review cadence

A quarterly business review with SAP is unavoidable. The buyer side version is non negotiable.

• Pull the consumption export from the cockpit at the start of every quarter.
• Reconcile actual credit draw against the contract.
• Walk forward the projected end of year position.
• Identify services trending toward overrun. Decide before SAP does.

BTP credits are the fastest moving cost line in the SAP estate. The governance you set in the first ninety days decides what the next three years cost.

BTP at the SAP renewal

What SAP sees

SAP renewal teams read the same cockpit data the customer reads. They see consumption growth, overrun trajectory, and service mix.

Their preferred move is to walk in with a renewal proposal pre framed off the current state. Growth justifies an uplift. Overrun justifies a true forward. Service mix justifies a bundled commit.

Buyer side moves at renewal

• Lock the rate card to the renewal effective date. The published rates drift upward.
• Negotiate credit conversion rights. Unused credits in one service family should be convertible into another.
• Push the commit floor. Avoid taking the full uplift SAP opens with.
• Stage the multi year commit. Year one anchors the rate. Year two and three buy time on capacity expansion.
• Lock the discount on overage. Overrun billed at retail is the single biggest leak.

Indirect access overlap

Integration Suite usage can touch the SAP indirect access framework. Connector volumes to S/4HANA generate the same documents that the indirect framework measures.

The risk is not the BTP bill. The risk is the indirect digital access line on the S/4 renewal.

Read the related SAP pillar hub for the wider indirect framework.

Cost traps to avoid

Top five traps

• Sandbox sprawl. Sandbox subaccounts that consume credits because nobody shut them down.
• API call leakage. Webhooks and polling integrations that hammer API Management at high volume.
• HANA Cloud over provisioning. Memory and storage sized to peak forever, not to baseline.
• AI service experimentation. Joule and Document services ramping without a quota.
• Credit expiry. Buying more credits than the estate can consume, with no carry forward right.

Service migration timing

SAP migrates services. Cloud Integration is the renamed Process Integration. Build Apps is the renamed AppGyver. Each migration carries a service consumption profile change.

Run a service inventory at every contract anniversary. Catch the migrations before the bill reflects them.

What to do next

1. Pull the current BTP cockpit export and confirm credit draw against the annual commit.
2. Identify the top three services by current consumption and the top three by growth rate.
3. Confirm the contractual rate card and check for retail uplift clauses on overage.
4. Set cost alerts at seventy, eighty five, and ninety five percent of commit.
5. Document the sandbox and non production subaccount footprint and the shutdown owner.
6. Run an Integration Suite call volume reconciliation against the indirect access framework.
7. Open the renewal conversation no later than nine months before contract anniversary.
8. Brief the SAP advisory practice on the renewal posture you want to take.

Frequently asked questions

What is SAP BTP in plain language?

SAP Business Technology Platform, or BTP, is the publisher's bundle of integration, data, build, and AI services sold on a Cloud Credit model. It sits alongside S/4HANA, not inside it.

Do RISE customers get free BTP credits?

RISE contracts include a small allocation of BTP credits. The allocation is rarely sufficient for an enterprise estate, and most customers carry a separate BTP commit on top of the RISE contract.

Do unused BTP credits roll over?

By default, unused credits expire at the end of the contract year. Carry forward rights and credit conversion across service families are negotiable but not automatic. Read the contract before the cockpit.

How are BTP services billed?

Each service is billed against a unit of metering. Integration Suite is per message. HANA Cloud is per memory hour. Build Apps is per active user. The rate card converts each unit into credit consumption.

Can BTP usage trigger SAP indirect access?

Integration Suite volumes that touch S/4HANA can generate the same digital documents that the indirect framework measures. The risk does not sit on the BTP bill. It sits on the S/4 renewal line.

What is the biggest BTP cost trap?

Credit expiry combined with a high overrun rate. Customers buy more credits than they can consume, then pay retail on the services that run over. Both ends of the leak should be closed before the renewal.

When should we open the BTP renewal conversation?

No later than nine months before the contract anniversary. Earlier is better. SAP renewal teams need time to negotiate the rate card, the commit floor, and the carry forward terms.