Showback and chargeback: choose shared-cost rules teams can act on
Distinguish showback from chargeback and compare shared-cost allocation rules. Work through a reconciled platform bill, incentive changes and a disputed cost correction.
TL;DR: Showback explains attributable cost; chargeback posts agreed costs into accountable budgets. Choose the financial process separately from the allocation formula, and make shared-cost rules understandable enough that teams can change a useful engineering decision.
Visibility and budget authority are separate choices
A team can receive an accurate monthly service-cost report without its budget being debited. That is showback. Chargeback adds a formal accounting consequence under the organization's approved process. The FinOps invoicing and chargeback capability explicitly distinguishes the two and does not treat chargeback as inherently more mature.
Start from a reconciled dataset. Cloud cost allocation explains owner mapping, unknown rows and cost-basis consistency. This page assumes those inputs exist and asks a different question: which shared charges should influence a team's decisions, and through what policy?
A report can show both controllable usage and an allocated corporate cost, provided they remain distinguishable. Asking a team to reduce a centrally negotiated fixed support fee that it cannot influence creates an accounting target without an engineering action.
Compare two rules on the same platform bill
Consider a hypothetical $18,000 monthly bill: Team A has $8,000 of direct cost, Team B has $4,000, and the shared platform costs $6,000. Ignore taxes and credits for this exercise, and use one consistent cost basis.
An equal split assigns $3,000 of platform cost to each team. A usage-based split, using an agreed 80/20 share of normalized platform consumption, assigns $4,800 to A and $1,200 to B.
| Rule | Team A total | Team B total | Combined total |
|---|---|---|---|
| Equal shared split | $11,000 | $7,000 | $18,000 |
| 80/20 usage split | $12,800 | $5,200 | $18,000 |
| Central shared budget | $8,000 | $4,000 | $12,000 teams + $6,000 central |
Every rule conserves the same bill. Changing the split is not a $1,800 saving for B; it transfers that amount to A. The FinOps shared-cost guidance describes several legitimate strategies, including central funding and allocation. The right rule depends on what behavior the organization wants and which usage measurements are defensible.
Match the denominator to the responsibility
CPU time can be reasonable for part of a shared compute service, but it ignores reserved headroom, memory-heavy tenants and persistent storage. Requested capacity may better express reservation responsibility, while actual consumption may better express metered service use. Either can create incentives: billing only usage may encourage teams to reserve excessive idle capacity; billing requests without reviewing safety margins may encourage dangerous under-requesting.
For this example, suppose platform cost consists of $4,000 fixed capacity and $2,000 variable processing. A proposed rule allocates fixed cost equally and variable cost at 80/20. A receives $2,000 + $1,600 = $3,600 shared cost, and B receives $2,000 + $400 = $2,400. Totals become $11,600 and $6,400. That may better express the service agreement, but the split remains an organizational policy, not a mathematical discovery.
The diagram separates formula acceptance from posting authority. A platform engineer should not turn an experimental dashboard into a financial transfer merely because the totals match.
Make corrections traceable
Record the usage period, allocation-rule version, cost basis and effective owner mapping with each report. Offer a way to challenge a row with evidence. If an idle capacity pool belongs to platform resiliency rather than one application, resolve that ownership explicitly instead of relabeling it to satisfy a coverage target.
Assume A's usage share was incorrectly reported as 80% and is corrected to 70%. Under the fully usage-based rule, A's shared charge falls from $4,800 to $4,200 and B's rises from $1,200 to $1,800. The total remains $6,000. For an already closed period, follow the agreed adjustment process and retain the original report; silently rewriting history makes earlier budget decisions impossible to explain.
Cloud discounts also need policy. A central commitment may reduce the provider bill while utilization risk remains with the central purchaser. Assign the benefit and unused commitment cost deliberately. Do not combine list-price service numerators with a discounted invoice denominator and label the unexplained difference waste.
Self-check: after chargeback, Team B moves a workload into an unmetered shared service and its report falls by $1,000 while the organization pays the same amount. Did the initiative save money? No. Investigate the allocation gap and assess whether the move changed useful output or operational cost. In an interview, report both the team-budget effect and the organization-wide result instead of treating them as equivalent.