What is the prerequisite for cause-based BTP cost allocation?

A subaccount structure that reflects organizational units, projects, or cost centers. SAP provides monthly balance statements at subaccount level.

Internal Cost Allocation for BTP: Chargeback Models for Hybrid Portfolios

Q: What is the difference between showback and chargeback?

Showback shows cost centers their BTP costs without creating an internal booking. Chargeback actually allocates costs to cost centers and creates genuine cost accountability.

Allocating BTP costs to business units and cost centers in a causally accurate way is an unsolved problem in most organizations. Without the right subaccount structure, there is no technical foundation for any reliable allocation. This article describes the organizational and technical prerequisites, how showback and chargeback differ in practice, and where SAP's native tools reach their limits.

Why Internal Cost Allocation Is a Controlling Requirement, Not an Option

BTP costs do not arise evenly across an organization. An integration initiative in logistics, a HANA Cloud database instance for financial planning, and an AI pilot in HR each generate different credit consumption, all drawing from a single annual budget commitment.

As long as that consumption is not broken down and traced back to the units that caused it, a classic governance problem emerges: the central IT budget absorbs costs whose drivers sit in the business lines. Business lines plan without knowing their actual BTP spend. And when renewal preparation starts, the data needed to anchor the next commitment to a credible consumption history simply is not there.

For SAP Platform Directors, this is a governance moment in the cost dimension, not internal cost accounting in a narrow sense. It is a governance prerequisite: if you do not allocate internally, you cannot demonstrate to the CFO and management which business unit is consuming which share of the SAP budget and why.

Subaccount Structure as the Unit of Attribution: The Design Decision with Cost Implications

The technical foundation for any internal BTP cost allocation is the subaccount structure of the Global Account. SAP delivers monthly balance statements at the subaccount level. What is not separated at the subaccount level cannot be separated at the reporting level.

This is not a purely technical architecture decision. It is a governance moment with direct cost consequences: how the Global Account and its subaccounts are organized determines the granularity at which causally accurate allocation is even possible.

Four organizational principles have proven themselves in practice:

By business unit: One subaccount per business unit. Simple to administer, but too coarse when multiple projects within a single BU have different credit profiles.

By project: One subaccount per BTP project or initiative. Precise attribution, but higher administrative overhead when projects change frequently. Well suited for organizations with clearly scoped, multi-year BTP projects.

By environment with project separation: One subaccount each for production, test, and development per project. This also enables a distinction between productive consumption and dev/test costs, which matters for non-production shutdown strategies and internal allocation.

By cost center: The subaccount structure mirrors the internal cost center hierarchy. A direct connection to accounting-level governance, but it requires a stable cost center structure that does not change frequently.

The challenge with granular structures: many subaccounts increase the administrative burden for entitlement assignment and monitoring. The right balance depends on organizational size, depth of BTP usage, and controlling requirements. What matters most is that this decision is made deliberately and documented before BTP workloads go live, not after.

Credit Rate as the Basis for Allocation: What the Cost Center Owner Needs to Know

BTP costs are incurred in Capacity Units (CUs), not directly in euros or dollars. The credit rate, meaning the contractually fixed price per Capacity Unit from the Order Form, is the conversion factor for internal allocation.

This difference from the list price is material to the internal allocation process. An Enterprise Agreement with a 25 to 35 percent discount off list price means the internal allocation should reflect the negotiated contract credit price, not the list price. Cost center owners who use the list price as their reference will systematically overstate the cost of their BTP consumption.

The practical process for a monthly cost center allocation follows three steps:

Read the balance statement: Pull the credit consumption for the month from the monthly balance statement for each relevant subaccount.
Convert to currency: Multiply the credit consumption by the contractually fixed credit price (from the Order Form) to get the monetary amount per subaccount.
Post to cost centers: Transfer the monetary amount to the cost center or internal budget owner mapped to that subaccount.

This process requires that the mapping between subaccounts and internal cost centers is maintained and current. Any change to the organizational structure requires a corresponding update to the subaccount assignment so that the allocation continues to work correctly.

Showback versus Chargeback: Two Levels of Internal Transparency

Two models for internal BTP cost distribution have established themselves in practice. They differ in how binding they are and how much implementation effort they require.

Showback makes BTP costs visible to cost centers and projects on a monthly basis, without triggering any actual internal booking. The controlling system stays unchanged. The effect comes from visibility: a person who regularly sees their BTP consumption as a concrete number develops a different cost awareness than someone receiving an opaque pooled invoice.

Showback is the simpler starting point. It requires no changes to internal booking processes and is achievable even when the subaccount structure is not yet fully separated by allocation unit. It creates the first governance moment in the cost dimension at the business line level.

Chargeback actually allocates BTP costs to cost centers or projects through internal bookings or corresponding budget assignments. Chargeback creates real cost ownership: if you consume more BTP resources, you feel it in your own budget. This direct governance impulse is more durable than visibility alone, because it shapes behavior.

Chargeback requires more mature infrastructure: a functioning subaccount architecture as the data foundation, a defined allocation model that is valid from an accounting standpoint, and the willingness of business lines to pay internally for their BTP usage. The FinOps Foundation describes showback as a typical maturity step on the path to chargeback: many organizations spend six to twelve months on showback to build internal acceptance and understanding of the cost structure before the chargeback process is introduced (Source: FinOps Foundation, FinOps Framework 2025).

What SAP's Native Tools Deliver and Where Their Limits Are

The BTP Cockpit and the monthly balance statements provide the raw data for internal allocation. They show credit consumption by service and by subaccount in a structured format. For monitoring and baseline analysis at the contract level, these tools are sufficient.

The limits become visible as soon as the allocation needs to go beyond the subaccount level or consolidate multiple contract structures.

The BTP Cockpit does not offer direct integration with internal ERP or controlling systems. The connection between balance statement data and internal cost centers has to be built outside the Cockpit, typically through manual or semi-automated data transfers.

It provides no consolidated view across multiple contract structures. If you run a CPEA agreement alongside several subscription contracts in parallel, you see them in separate views, not as a unified budget picture.

It delivers no automated booking logic. Transferring subaccount consumption data into internal accounting is a manual step or one that requires a process solution. In practice, this frequently leads to Excel-based allocation models that need to be reworked with every contract change or organizational adjustment.

That last point is the most consistently underestimated aspect: Excel allocation models are not a sustainably viable solution for a growing SAP portfolio. They do not scale with portfolio complexity, their quality depends on specific individuals, and they require manual rework with every contract change.

Three Typical Allocation Patterns in Practice

Three allocation approaches appear repeatedly in practice. Each has different strengths and weaknesses depending on the organizational structure.

Consumption-based allocation (direct): BTP consumption is transferred directly to the mapped cost centers based on subaccount data. This is the most precise method and creates genuine cost ownership. It requires that the subaccount structure is consistently organized by attribution unit, and it is the target path for any mature BTP governance.

Usage-based proration: Where subaccounts are not separated by cost center, the total consumption of a subaccount is distributed using a proration key. That key can be based on the share of active users per business unit, transaction volume shares, or a pre-agreed weighting. This method is less precise, but easier to operate when a full subaccount separation is not yet in place.

Flat-rate chargeback: A fixed internal price per defined BTP usage unit is set in advance and updated periodically. The advantage is predictability for business lines, because the internal price is stable and does not fluctuate month to month. The disadvantage is that actual contract costs will diverge when real consumption deviates from the plan. Flat-rate models are best suited for stable, predictable workloads such as HANA Cloud production operations or Integration Suite baseline services. For variable workloads, especially AI usage, they are less appropriate.

Common to all three patterns: the more the internal allocation reflects the actual contract logic, the more credible the foundation for renewal negotiations, budget forecasting, and strategic prioritization of new BTP initiatives.

How the "Cost" Governance Moment Connects BTP Governance and Internal Allocation

The cost governance moment in the FinOptory governance model covers four dimensions: ACV tracking, derived charges, invoice reconciliation, and internal allocation. These four dimensions are not independent.

ACV tracking tells you whether annual consumption is on track. Tracking derived charges lets you spot overage risk before it materializes. Reconciling the SAP invoice against your own balance statement data confirms plausibility. And internal allocation closes the loop: the costs visible at the contract level land with the units that generate them.

Without internal allocation, the first three dimensions remain tasks for the central IT budget, with the drivers in the business lines invisible. With internal allocation, a complete governance moment emerges: from contract structure through monthly consumption to organizational accountability.

This connection is why the decision on subaccount structure and allocation model should not be treated as a technical afterthought. It belongs in the BTP governance design from the start.

Frequently Asked Questions

How do I distribute BTP costs to internal cost centers when I do not have a clean subaccount structure?

Without subaccount separation, a directly consumption-based allocation is not possible. As a transitional approach, usage-based proration based on transaction volumes or user shares per business unit is a practical option. In parallel, the subaccount structure for new projects should be built consistently by attribution unit from the outset. Retroactively restructuring existing subaccounts is technically feasible, but requires care with entitlement reassignment (Source: SAP Help Portal, Monitoring Usage and Consumption Costs).

What is the difference between showback and chargeback for BTP?

Showback makes BTP costs transparent to cost centers and projects without triggering internal bookings. Chargeback actually allocates those costs against the budgets of the business lines. Showback builds cost awareness; chargeback creates cost ownership. Many organizations start with showback and introduce chargeback once internal acceptance of the cost structure has developed (Source: FinOps Foundation, FinOps Framework 2025).

How often should the internal allocation be updated?

Monthly, because BTP balance statements are delivered monthly and the relevant consumption components are billed on a monthly basis. Quarterly aggregation is sufficient for budget reviews, but it misses intra-year shifts that matter for renewal preparation or overage management.

What data do I need to set up a first chargeback process?

Four components are required: first, the monthly balance statements per subaccount from the BTP Cockpit; second, the contractually fixed credit price from the Order Form; third, the mapping between subaccounts and internal cost centers or projects; and fourth, a defined approval and booking procedure for the monthly allocation. The most time-consuming part is typically the mapping, because it connects the internal organizational structure with the BTP architecture decision (Source: SAP Help Portal, Monitoring Usage and Consumption Costs).

Next Steps

BTP cost allocation as part of the contract review: If you want to build a foundation for causally accurate allocation of your BTP costs, the starting point is a complete analysis of your current subaccount structure, contract models, and consumption data. The FinOptory Contract Review delivers that foundation in four weeks, with a concrete set of recommendations as the output.

Further reading: FinOps Inform-Optimize-Operate for SAP BTP | Allocating SAP Costs Internally: Where SAP's Native Tools Reach Their Limits | BTP FinOps: Overview