Definition of showback and chargeback
Showback and chargeback refer to two ways of presenting a team with the cost of the IT services it consumes, in the cloud in particular. Showback shows it to the team. Chargeback charges it to the team’s budget. The French version of this site translates them as restitution des coûts and refacturation interne.
The FinOps Foundation glossary (finops.org, consulted on 12 November 2026) classes both as allocation strategies and describes them as reports of actual consumption.
| Showback | Chargeback | |
|---|---|---|
| Recipient | An entity, or any subset of the organisation | The budgets and accounts held in the financial system |
| Accounting effect | Generally none: the report serves visibility | The cost is charged; the report may be called an “invoice” internally |
| Breakdown | Free, including cross-cutting: all of production, all of storage | Mirrors the budget and accounting structure |
The “Invoicing & Chargeback” capability of the same framework sums up the gap: it lies in the formality of sending spending to official accounting budgets.
What each of the two reports is for
Showback gives a group, whatever its size, the cost of the scope for which it is responsible. The framework says it is required in every FinOps practice.
Chargeback makes each entity directly accountable for its spending. The framework does not regard it as a more mature stage than showback. It makes it depend on the organisation’s accounting rules and notes that official recharging may not be justified when costs go to a single cost centre.
What chargeback requires, and its limitations
Both reports presuppose allocation: each cost is attached to an owner, through the account structure and tags. This step is described in our FinOps entry, and the account structure is set from the landing zone onwards.
Chargeback adds constraints that the framework details.
- Finance must be able to rely on the consistency, timeliness and accuracy of cost data.
- The closing calendar sometimes comes before the provider’s invoice: estimates are booked, then adjusted.
- How shared costs are treated is decided with finance. The “Allocation” capability cites among them support, the core network and shared environments, of which an internal platform is one case.
One limitation remains: an allocation key is a convention, which those it charges may dispute once it is written into a budget.
Worked example: one invoice, three teams, two keys
Consider a hotel chain whose cloud invoice for one month amounts, by assumption, to 90,000 euros. Tags attach 60,000 of it to three teams: 36,000 to online booking, 18,000 to property management, 6,000 to data analysis. The remaining 30,000 euros are shared costs.
- Key proportional to direct costs (60%, 30% and 10%): the teams receive 18,000, 9,000 and 3,000 euros of shared costs, giving totals of 54,000, 27,000 and 9,000 euros.
- Equal-shares key (10,000 euros each): the totals become 46,000, 28,000 and 16,000 euros.
The sum remains 90,000 euros. Under showback, the data analysis team reads 9,000 or 16,000 euros. Under chargeback, the gap between these two amounts weighs on its budget.
Showback, chargeback, allocation, provider invoice: not to be confused
- Allocation attaches costs to their owners. Showback and chargeback present the result.
- The provider’s invoice is the document to be paid. The internal “invoice” of a chargeback redistributes its amount. The framework deals with both in a single capability, which also covers reconciling the invoices received.
- A showback report is not a budget: it shows spending without setting a ceiling.
The choice between showback and internal recharging is made together with the tagging rules and the treatment of shared costs, presented on our FinOps page.