Chargeback
Chargeback is the practice of allocating cloud costs to the departments, products or customers that caused them and then billing those costs to their budgets, usually as an internal recharge or intercompany invoice. It is showback with consequences: the same allocation, but the consumer’s budget changes when the statement is posted.
Because money moves, chargeback needs more than a report. It needs a written policy that says what is charged and how, allocation rules agreed in advance, a treatment for shared costs and commitment discounts that recipients accept as fair, a statement layout finance can post, and a process for disputes and corrections. The chargeback model template on this site is that document.
Chargeback is the strongest lever on cloud spend, because it gives the people who make provisioning decisions a budget line they own. It is also the easiest to get wrong. Charged back before the allocation is trusted, it turns data problems into political ones; with shared costs spread by guesswork, it teaches teams to avoid shared services; with rules changed mid-period, it destroys the trust it depends on.
The usual path is showback for a few cycles, then chargeback for directly attributable costs, then chargeback for each shared category as its allocation driver proves out, with the remainder kept on showback and reviewed as a budget of its own. Commitment discounts go to the consumers whose usage was covered, and unused commitment stays central as the cost of the decision to commit.
A well-run chargeback program reconciles to the invoice every period, reports its unallocated remainder honestly, and settles disputes by drilling into the data rather than by negotiation.
Go deeper
Related terms