BTP credits, optimized. Five levers, four quarters, one renewal.

BTP cost optimization is not a Q4 exercise. It is a quarterly cadence anchored on five operating levers that move the bill, the commit, and the renewal in the same direction.

BTP is sold on credits. Credits run on consumption. Consumption runs on workload patterns that the customer controls. So BTP optimization is fundamentally an operating question, not a procurement question.

The mistake most enterprises make is to treat BTP as a flat run rate and chase the bill at renewal. That hands SAP the framing. The buyer side framing is to pull on five operating levers across the year so the renewal numbers are already where they need to be.

Read the related SAP BTP knowledge hub for the platform context, the BTP licensing strategy guide, the SAP advisory practice, and the SAP pillar hub for the wider renewal framework.

The five operating levers

Every BTP optimization decision can be classified into one of five levers.

Lever map

• Workload right sizing. Memory, storage, message volume, capacity unit allocations.
• Rate card negotiation. The credit price per unit. The discount applied to overrun.
• Credit lifecycle. Expiry, carry forward, conversion across service families.
• Subaccount governance. Production, non production, and sandbox separation.
• Integration architecture. Batch versus event flows, throttling, and the connector inventory.

Which lever moves the most

The lever that moves the most depends on the estate shape. For HANA Cloud heavy customers, right sizing is biggest. For Integration heavy customers, architecture is biggest. For most enterprises, the combined effect of credit lifecycle and rate card is the single largest move.

Run a baseline assessment with the SAP RISE TCO calculator before deciding where to push first.

Right sizing workloads

HANA Cloud right sizing

HANA Cloud is metered per gigabyte memory hour plus a storage line. Most estates run with memory provisioned to peak and storage provisioned to forecast.

The buyer side move is to suspend non production at night, separate the storage tier from the memory tier, and tier the workload across HANA Cloud, Datasphere, and the data lake.

Integration Suite right sizing

Integration Suite is metered on messages. Volume is a function of how the flows are designed.

• Batch low value flows. Polling integrations that ask the same question every five minutes.
• Throttle high frequency webhooks. Defer if the consumer can wait.
• Consolidate redundant flows. The same source to two destinations is one flow with a split, not two flows.
• Retire dormant iflows. Anything that has not fired in ninety days.

Build right sizing

Build Apps is per active user. Active is defined narrowly. The license cost is recoverable for users who logged in once and stopped.

Build Process Automation is per process unit. The unit definition is dense. Map the unit to the operating volume before assuming the licensed pool is correct.

Negotiating the rate card

What is in the rate card

The rate card is the price list that converts each unit of consumption into credits. The rate card moves. Buyer side practice is to lock it to the contract effective date.

Read the related SAP RISE negotiation guide for the wider rate card framework across the SAP estate.

Discount posture and overrun terms

• Headline discount. Applies to the in commit credits only. Mid term.
• Overrun discount. Negotiable. Default is retail. Buyer side floor is the in commit discount.
• Multi year stepped discount. Year on year deepening as the commit grows.
• True forward exposure. Single biggest line on the renewal proposal if not managed.

Optimization without governance is a Q4 cleanup. Optimization with governance is a renewal lever you can pull twice a year, every year.

Solving credit expiry

Default expiry rules

Cloud Credits expire at the end of the contract year unless the contract carries explicit carry forward language.

Pay As You Go customers do not have expiry because there are no credits. The trade off is the rate.

Carry forward and conversion rights

• Carry forward. Right to roll unused credits into the next contract year.
• Service family conversion. Right to convert unused credits across families.
• True down right. Right to lower the annual commit at a midterm gate.
• Credit pool aggregation. Right to pool credits across multiple subsidiaries.

Indirect access exposure through BTP

How the overlap works

BTP Integration Suite flows that touch S/4HANA generate documents inside the S/4 system. Those documents fall under the indirect access framework, the same framework that drives digital access licensing on S/4.

The cost does not appear on the BTP bill. It appears on the S/4 renewal as a digital access uplift.

Buyer side counter moves

• Run an Integration Suite call volume reconciliation against the digital access metric.
• Document which flows generate counted documents.
• Negotiate the digital access pool floor on the S/4 renewal, not the BTP renewal.
• Pull in the SAP advisory practice for the joint conversation across BTP and S/4.

What to do next

1. Pull the BTP cockpit export and classify spend across the five lever categories.
2. Identify the top three services by overrun risk and apply a quota.
3. Inventory the sandbox and non production subaccounts and assign a shutdown owner.
4. Lock the contractual rate card to the contract effective date in writing.
5. Open the carry forward and conversion conversation no later than six months before the renewal.
6. Reconcile Integration Suite flows against the digital access framework on S/4HANA.
7. Schedule the quarterly review with finance, architecture, and the SAP advisory team.
8. Brief the SAP advisory practice on the optimization posture you want to carry into renewal.

Frequently asked questions

How much can BTP cost optimization save?

Mature estates typically recover fifteen to thirty percent of in term spend through right sizing alone, with another five to ten percent at renewal through rate card and credit lifecycle moves.

Should we switch BTP to Pay As You Go?

Pay As You Go removes the commit risk but doubles the rate. It works for low volume, exploratory workloads. It is rarely the right answer for an enterprise estate.

Can we negotiate carry forward on Cloud Credits?

Yes. Carry forward is not in the default contract. It is negotiable, especially during multi year renewal cycles.

How often should we run a BTP optimization review?

Quarterly is the operating cadence. Monthly is appropriate for the first six months after a renewal or a major architecture change.

What is the relationship between BTP cost and S/4HANA indirect access?

Integration Suite flows that touch S/4HANA generate digital documents that fall under the indirect access framework. The cost lands on the S/4 renewal, not the BTP bill, so the review needs to span both.

Do we need a dedicated BTP cost owner?

Yes. A single named owner with cockpit access, finance partnership, and architectural authority is the only governance model that holds across a multi year term.