Chargeback Calculator
Allocate 100% of a cloud bill onto consuming teams, spreading shared platform and untagged cost by even, proportional or weighted keys.
Inputs
Team A Fully Loaded Charge
$90,769.23
Team B Fully Loaded Charge
$52,948.72
Team C Fully Loaded Charge
$33,282.05
Total Charged to Teams
$177,000.00
Shared Cost Landing on Team A
$30,769.23
Team A Uplift over Direct Cost
51.3%
Share of the Invoice Allocated
100.0%
Cost Left Unallocated
$0.00
Step by step
Values used
Team A direct cost = 60,000 USD/month; Team B direct cost = 35,000 USD/month; Team C direct cost = 22,000 USD/month; Shared platform cost = 48,000 USD/month; Untagged cost that must still be recovered = 12,000 USD/month; Shared-cost allocation key = Proportional to direct usage; Team A weight = 3 weight; Team B weight = 2 weight; Team C weight = 1 weight
Chargeback
team charge = direct cost + (shared pool + untagged cost) × allocation share, where the share is 1 ÷ teams, direct cost ÷ total direct cost, or the team weight ÷ total weight.
Team A Fully Loaded Charge
= 90,769.23
Team B Fully Loaded Charge
= 52,948.72
Team C Fully Loaded Charge
= 33,282.05
Total Charged to Teams
= 177,000.00
Shared Cost Landing on Team A
= 30,769.23
Team A Uplift over Direct Cost
= 51.3
How it works
Chargeback moves the whole invoice onto consuming teams, which means the shared platform layer and any untagged cost must be pushed somewhere rather than absorbed centrally. The allocation key decides who pays: an even split is simple but punishes small teams, proportional tracks usage and is the common default, and a weighted key lets you encode a business judgement such as revenue or headcount. The moment cloud cost lands in a team's own budget, behaviour changes — but so does the argument, because the shared-cost key is where every dispute happens. Publishing the key and driving the unallocated residual to zero is what makes chargeback defensible; this is a modelling aid, not accounting or tax advice.
Formula
Chargeback
team charge = direct cost + (shared pool + untagged cost) × allocation share, where the share is 1 ÷ teams, direct cost ÷ total direct cost, or the team weight ÷ total weight.
- shared pool
- Platform and untagged cost that no single team consumed directly
- allocation share
- Fraction of the shared pool a team absorbs under the chosen key
- residual
- Any part of the invoice left unallocated — chargeback must drive this to zero
Frequently Asked Questions
How is Chargeback calculated?
team charge = direct cost + (shared pool + untagged cost) × allocation share, where the share is 1 ÷ teams, direct cost ÷ total direct cost, or the team weight ÷ total weight. Chargeback moves the whole invoice onto consuming teams, which means the shared platform layer and any untagged cost must be pushed somewhere rather than absorbed centrally. The allocation key decides who pays: an even split is simple but punishes small teams, proportional tracks usage and is the common default, and a weighted key lets you encode a business judgement such as revenue or headcount.
Why does Chargeback matter?
The moment cloud cost lands in a team's own budget, behaviour changes — but so does the argument, because the shared-cost key is where every dispute happens. Publishing the key and driving the unallocated residual to zero is what makes chargeback defensible; this is a modelling aid, not accounting or tax advice.
What values do I need to enter?
This calculator takes 9 inputs: Team A direct cost, Team B direct cost, Team C direct cost, Shared platform cost, Untagged cost that must still be recovered, Shared-cost allocation key, Team A weight, Team B weight, Team C weight. The pre-filled defaults are a realistic starting point — replace them with figures from your own environment for a result you can act on.
How is chargeback different from showback?
Chargeback transfers real budget: 100% of the invoice lands in consuming teams' cost centres and they answer for it. Showback reports the same numbers without moving any money, so the central platform team still holds the invoice. Showback is the usual first step because it exposes the allocation disputes before money is at stake.
You might also need
- Resource Tagging Coverage CalculatorCommonly used together
- Showback CalculatorCommonly used together
- Cloud Budget Forecast CalculatorCommonly used together
- Cloud TCO CalculatorAlso in Multi-Cloud & FinOps
- Multi-Cloud Cost Comparison CalculatorAlso in Multi-Cloud & FinOps
- Cloud ROI CalculatorAlso in Multi-Cloud & FinOps