Contents
Key takeawaysCPEA, BTPEA or subscriptionCalculating capacity unitsConversion ratios by serviceOver commit versus under commitExpiry, rollover and overageChecking your consumptionWhat we have seenAnswering the account teamOrder form clausesPreparing for renewalWhat to do nextFAQEvery BTP service converts its own usage into capacity units at its own rate, and unused credits expire by default. Forecast service by service, commit at demonstrated consumption, and fix rollover and overage terms in the order form.
- Two credit models, one fixed model. CPEA and its successor BTPEA are prepaid credit pools; the subscription model buys named services at a fixed fee.
- Rates differ by service. Integration Suite converts by messages, HANA Cloud by memory and compute, Build and Joule services by users or runtime hours.
- Credits expire annually. Unused credits are written off at the end of each contract year unless the order form includes a rollover clause.
- Overage costs list price. Consumption above the commit is billed at list, so every unit over the line loses your full discount.
- The free tier is separate. Free service plans do not draw down credits, so count them out of the forecast.
- The catalog keeps changing. SAP revises services and conversion rates quarterly, so recalculate with current rates at every renewal.
- Over commit is the usual error. In the BTP reviews we ran, the median customer had committed 21 percent more than it went on to consume.
SAP Business Technology Platform charges most services through cloud credits, and each service converts its own usage (messages, memory, users, runtime hours) into a charge against them. That conversion is where BTP budgets go wrong. Map it service by service before you sign, and you avoid both expired credits and list price overage.
I spent years on the SAP side of these contracts. The model is flexible, but the default terms favor SAP wherever the forecast is off, so the forecast deserves more attention than the discount.
This guide covers the BTP commercial models, capacity units, cloud credits, conversion rates, expiry, overage and renewal terms. If BTP is sold to you inside a larger deal, read it alongside our RISE negotiation guide and the S/4HANA advisory page.
Which SAP BTP commercial model should you sign: CPEA, BTPEA or subscription?
Sign a credit agreement (CPEA or its successor BTPEA) for workloads you cannot yet size, and a subscription for services whose volume is stable. Picking the wrong model at signature means overpaying for the whole term.
Cloud Platform Enterprise Agreement (CPEA)
CPEA is a prepaid credit pool. You commit a dollar amount per year, the pool refills each contract year, and any eligible BTP service draws from it. SAP deducts the previous month's consumption from your balance every month.
BTP Enterprise Agreement (BTPEA)
BTPEA is also a prepaid credit model, and SAP now positions it as the standard for new credit contracts. You pay upfront, volume sets the discount tier, and consumption draws the balance down, exactly as under CPEA. The differences are these:
- Catalog. BTPEA adds services CPEA never covered, such as SAP Analytics Cloud, and drops older services with low adoption.
- Deprecation. Group 1 services are supported to the end of your contract. Group 2 innovation services can be withdrawn or moved to Group 1 with six months' notice.
Subscription, Pay-As-You-Go and the hybrid path
The subscription model is the fixed option: named services at fixed capacities for a fixed fee, renewed on a set cycle. Pay-As-You-Go has no commitment and bills every unit at list price.
A hybrid customer holds credits for variable workloads and subscriptions for stable production, which lowers over commit risk on the pool while keeping fixed prices where volume is known.
| Model | Pricing | Service mix | Exit or reset |
|---|---|---|---|
| CPEA | Prepaid credit pool | Any service in the CPEA catalog | Annual reset |
| BTPEA | Prepaid credit pool | Current catalog, including SAP Analytics Cloud | Annual reset |
| Subscription | Fixed fee per named service | Named services only | Subscription term |
| Pay-As-You-Go | List price in arrears | Any eligible service | No commitment |
| Hybrid | Credit pool plus subscriptions | Mixed | Per leg |
The Meters: BTP Credits and AI Units
How do you calculate SAP BTP capacity units?
You calculate capacity units service by service: take expected usage in each service's own metric, apply SAP's published rate, and add up the results. Capacity units measure consumption, and the credit balance is the money side of the same count.
What a capacity unit measures
A capacity unit is an abstract unit of service consumption. SAP Integration Suite messages, SAP HANA Cloud memory and SAP Build Apps users all convert to capacity units, each at a different rate.
Where SAP publishes the conversion rates
SAP publishes the rates by service in the BTP service catalog, and the SAP Discovery Center estimator applies them to a sizing you enter. The table updates quarterly, so read the current rates at every renewal.
How the free tier changes the count
Some BTP services offer a free plan in enterprise accounts, and that consumption does not draw down credits. Free plans are capped, carry no SLA, and a paid plan cannot switch back to free. Counting free plan usage against the pool inflates the forecast.
- Read the conversion table. Pull the current capacity unit rate for every active service.
- Map each service to consumption. Project annual consumption in capacity units first, and convert to credits last.
- Apply the free tier. Take the free plan allotment out of the projection.
- Validate against the prior year. Compare the projection with the trailing 12 months of actual consumption and explain every large gap.
Why do conversion ratios differ so much between BTP services?
Each service is metered on what drives its cost, so one credit buys very different amounts of work from service to service. Comparing services against one pool without normalizing the ratio compares unequal things.
Integration and event services
SAP Integration Suite and Event Mesh convert by message volume, and the rate is steep above the published tier. One chatty new interface can push a tenant past its tier within weeks.
Database and analytics services
SAP HANA Cloud and SAP Datasphere convert by memory size and compute hours, and the conversion compounds when both grow together. SAP's HANA Cloud Capacity Unit Estimator shows how each sizing choice changes the count. For Datasphere, see our Datasphere licensing guide.
Application and AI services
SAP Build Apps, SAP Build Process Automation and the SAP Joule AI services convert by named user or runtime hours. Runtime based consumption tracks adoption, so it climbs month by month after go live.
SAP now sells Joule and much of its Business AI in AI units, so check which meter your order form actually uses before you forecast it against the credit pool. Our Joule and AI units guide covers that meter.
What does over commit or under commit cost in practice?
Over commit usually costs more. Every unused credit is lost at the full price you paid for it, while overage only costs the discount you miss on the excess.
Say your trailing 12 months point to 850,000 in list value of consumption next year, your order form prices credits at a 30 percent discount, and overage is billed at list.
| Commit (list value) | Paid for credits | Unused or overage | Total paid | Cost per $1 consumed |
|---|---|---|---|---|
| 1,000,000 | $700,000 | 150,000 unused | $700,000 | $0.82 |
| 850,000 | $595,000 | None | $595,000 | $0.70 |
| 750,000 | $525,000 | $100,000 overage | $625,000 | $0.74 |
| 750,000 at a 25 percent tier | $562,500 | $100,000 overage | $662,500 | $0.78 |
The oversized commit wastes $105,000 (150,000 unused credits at 70 cents). Even the worst under commit case, with a lower discount tier, costs $37,500 less. A 50 percent rollover clause would carry 75,000 credits forward and cut the loss to $52,500.
Why a bigger commit for a better discount tier rarely pays
The usual advice is to commit high enough to reach the next discount tier, because adoption will fill the headroom. We disagree, because the median customer in our reviews was already over committed and unused credits are lost by default. Commit at demonstrated consumption, add a ramp tied to go live dates, and negotiate the top up rate instead.
What happens to unused BTP credits and to overage?
By default, unused credits expire at the end of each contract year, and consumption above the commit is billed at list price. Both defaults can be changed, but only in the order form before signature.
The default expiry
The standard CPEA term carries no rollover. Credits left at the end of the annual term are written off, and you start the next year with a fresh pool.
The negotiated rollover
A rollover clause carries unused credits into the next contract year. In negotiated deals, the achieved rollover ratio ranges from 20 to 100 percent, with the higher end usually tied to renewing at the same commitment or higher.
The true up when you cross the commit
Crossing the annual commit triggers a true up. It applies the list rate to the excess unless the order document names a different overage rate, so you lose your discount on every unit above the line.
How do you check your own BTP consumption?
Use the BTP cockpit for technical consumption by service and SAP for Me for the commercial balance. Read both monthly, because a spike in March is already on your balance in April.
The BTP cockpit
At global account level, the cost and usage view shows consumption by service and subaccount, with billing and usage tabs covering the past 12 months. It reports free tier usage separately from billable usage, and each subaccount's Entitlements area shows which plan every service runs on.
The SAP for Me portal
SAP for Me shows committed credits, consumed credits and the remaining balance by month. This is the view to put in front of finance and the renewal team.
- Trend by service. Chart each service separately, since one noisy service hides inside a flat total.
- Burn rate. Divide the remaining balance by the average of the last three months to see when the pool runs out.
- Plan check. Look for paid instances that could run on a free plan, and free plans close to their cap.
The over commit and under commit trap
Over commit leaves a write off at year end. Under commit pushes consumption to the list rate. The right size sits within one step of the trend line, which only works if someone reads the trend monthly.
What have we seen in recent BTP commitment reviews?
Across 37 BTP reviews, the median over commit was 21 percent, meaning the customer had committed about a fifth more than it went on to consume. That pattern is why we estimate that skipping the conversion work leaves about 20 percent of BTP spend on the table.
The most common cause was a misread integration service ratio. The fix that worked best was a monthly consumption review by service, which reduced both the over commit and the year end write off at the next renewal.
The discount on BTP credits only pays if the credits are consumed. Size the commitment to the trend you can show, then negotiate what happens when you are wrong.
What will the SAP account team say, and how should you answer?
Expect pressure toward a larger commitment and default terms. These are the lines we hear most, with a reply for each.
- "Commit a little more and you reach the next tier." Show the cost per consumed credit at your trailing consumption, and ask for the better tier with a ramp.
- "Headroom is never wasted, credits work for any service." It expires at year end under standard terms. If SAP expects it to be used, ask for rollover.
- "BTPEA is the standard now, we just flip the switch." Ask for your services listed by group. Any production service in Group 2 needs longer notice or a fallback.
- "Take the BTP credits inside the RISE bundle." Ask for the BTP line priced separately. Our guide to negotiating BTP inside an S/4HANA deal covers bundled credits.
Which clauses belong in the BTP order form?
The clauses that matter sit in the order document, not the global agreement, so they are negotiated deal by deal. Ask for these in writing:
- Rollover. The share of unused credits carried into the next year, and any condition on it.
- Overage rate. Overage billed at the contracted discount rather than list.
- Top up right. Extra credits purchasable during the term without losing your discount.
- Ramp. A commitment that steps up by year in line with go live dates.
- Conversion. The right to move spend between subscriptions and the credit pool when a workload stabilizes.
- Price protection. Confirmation that SAP's minimum price guarantee applies, so a list price cut during the term lowers your rate.
How should you prepare for a BTP renewal?
Start at least six months out and document lower consumption before the renewal letter lands. The letter assumes your prior commitment, and it is far easier to reset that figure early than to argue it down later.
The consumption review
Run a 12 month review by service. Identify over commit and under commit by service, and separate one off spikes such as migrations from lasting growth.
The conversion table refresh
Rebuild the forecast with the conversion rates in force at renewal, since the table changes quarterly. Check at the same time whether any of your production services moved between BTPEA groups or left the catalog.
The exit clauses
The renewal is the moment to negotiate rollover, conversion and overage clauses. Anything left out now stays out for the next contract period.
| When | What to do |
|---|---|
| 12 months before | Map subaccounts to owners and start the monthly consumption review |
| 6 months before | Refresh conversion rates, apply the free tier, build the forecast |
| 3 months before | Choose the model mix and table your clause requests |
| 1 month before | Compare the quote with the forecast and close open clauses |
We run this work within the Vendor Shield subscription, the Renewal Program, our SAP service line and the Software Spend Assessment. For price comparisons, see our benchmarking service and the Benchmark Program. More guides sit in the SAP Knowledge Hub.
What to do next
- Pull the BTP service inventory. List every BTP service in use across all global accounts and subaccounts.
- Read the conversion table. Capture the current capacity unit rate for each active service.
- Pull the consumption telemetry. Export the trailing 12 months of consumption from the BTP cockpit.
- Apply the free tier. Subtract the free plan allotment from the forecast.
- Pick the model. CPEA, BTPEA, subscription or a hybrid, depending on workload stability.
- Size the commitment. Set year one at demonstrated consumption, not the forecast.
- Negotiate the clauses. Rollover, conversion, ramp and overage terms go in the order document. Our SAP BTP licensing strategy guide covers consumption metrics and CPEA economics in more detail.
- Get an independent review. Have someone outside SAP's sales team check the forecast and the order form at each stage.
Frequently asked questions
What is a capacity unit in SAP BTP?
It is SAP's abstract measure of BTP consumption. Each service maps its own metric, such as Integration Suite messages, HANA Cloud memory or Build Apps users, to capacity units at its own published rate. The Discovery Center estimator applies those rates to a sizing you enter, which is the fastest way to test a forecast.
What is the difference between CPEA and BTPEA?
Both are prepaid cloud credit agreements with volume discount tiers. BTPEA covers a newer catalog that includes SAP Analytics Cloud and allows SAP to withdraw Group 2 innovation services on six months' notice. CPEA customers can move to BTPEA within their normal renewal, with no technical migration.
Do BTP credits roll over annually?
Not by default. Unused credits are written off at the end of each contract year. A rollover clause agreed at signature can carry part or all of the balance forward, and negotiated deals have achieved between 20 and 100 percent, often on condition that you renew at the same commitment or higher.
How do I forecast BTP consumption?
Export 12 months of consumption by service from the BTP cockpit, apply current conversion rates to next year's usage, and remove free plan consumption. Reconcile the result with the balance history in SAP for Me, and build it per subaccount so each owner confirms growth before you commit.
What happens when I exceed the BTP commit?
The excess is trued up at list price unless the order document names a different overage rate. The protections are an overage rate at the contracted discount and a right to add credits during the term at that discount, and both must be agreed before signature.
Which BTP services carry a free tier?
SAP lists the services with free plans in the BTP service catalog, and the list changes over time. You enable a free plan through subaccount entitlements. Check the cap before a pilot grows into production use, because a paid plan cannot be switched back to free.
Can I convert BTP service mix during the term?
Under a credit agreement, yes: consumption can shift between any eligible services without changing the contract. Subscriptions name specific services, so their mix is fixed until renewal unless the order form grants a conversion right. A hybrid gives flexibility on the credit side and fixed pricing on stable services.
How does Redress engage on SAP BTP?
We review consumption before you commit, benchmark conversion rates and pricing against other SAP customers, check the order document and run the renewal with you, including rollover, overage and conversion terms. The work runs through Vendor Shield, the Renewal Program or a fixed fee review, and we take no money from SAP.