Chargeback
Chargeback is billing each team or business unit for its allocated cloud cost, so the cost lands in that team's budget in the company's accounts. It uses the same allocation as showback, but money actually moves, which is why the rules for shared and unallocated cost must be agreed first.
In plain English
Think of flatmates settling up at the end of the month. Showback is the shared spreadsheet; chargeback is everyone actually transferring their share. Once money moves, every rule on the spreadsheet gets questioned.
Worked example
| Charged to Platform | $55,000 |
|---|---|
| Charged to Data | $33,000 |
| Charged to Checkout | $22,000 |
| Kept centrally: untagged, unallocated cost | $5,000 |
| Total charged back to teams | $110,000 |
Finance moves $110,000 into the three teams' budgets. The $5,000 nobody owns stays with the central cloud budget until it is tagged: charging it out by guesswork is how chargeback loses trust.
Why chargeback matters
When a team's cloud cost hits its own budget, cost becomes a trade-off the team makes rather than a surprise someone else absorbs. Chargeback is how companies with cost-centre accounting, internal platforms or customer-billed workloads make cloud spend part of each unit's P&L.
The price is precision. Once money moves, every allocation rule, shared-cost split and late adjustment matters, and finance needs the numbers in the format and at the time its accounting cycle expects.
Common mistakes
- Charging back before showback works. Teams that have never seen their numbers will dispute the first bill. Run showback until the allocation is trusted, then switch.
- Charging out unallocated cost. Spreading untagged spend across teams makes them pay for costs they didn't cause. Keep it central and give someone the job of reducing it.
- Ignoring commitment savings. If one team's commitment discounts another team's usage, decide whether savings stay with the buyer, follow the usage or are pooled, and write it down.
- Missing finance's calendar. Chargeback runs on the accounting close. Lock the month on an agreed date and post later adjustments in the next period.
Where to find it in AWS, Azure and Google Cloud
| Cloud | What it is called | Where to find it |
|---|---|---|
 AWS | Cost Categories and Billing Conductor | Cost Categories and split charge rules decide who owns what. AWS Billing Conductor produces pro forma bills per billing group and is built for organizations with chargeback requirements. |
 Azure | Cost allocation rules and exports | Cost allocation rules split shared costs across subscriptions, resource groups or tags before you export the data to finance. They don't change the invoice and don't cover reservation or savings plan purchases. |
 Google Cloud | Billing export to BigQuery | Projects, labels and Resource Manager tags in the billing export give finance the breakdown; the chargeback itself happens in your finance system. |
How CloudYali helps
CloudYali breaks cloud cost down by account, tag, team and custom dimensions, with the same allocation every month and scheduled cost reports, giving finance a consistent basis for chargeback.
Related terms
Allocation & accountability
Showback
Showback is reporting each team's allocated cloud cost back to that team, for visibility and accountability, without moving money between budgets. It shows owners what their choices cost so they can act on it, and unlike chargeback it is not entered into the company's accounts.
Allocation & accountability
Cost allocation
Cost allocation is assigning every part of the cloud bill to the team, product or customer responsible for it, using accounts, tags and agreed rules for shared costs. It turns one invoice into numbers each owner can act on, and it is the basis for showback, chargeback and unit economics.
Allocation & accountability
Cost allocation tags
Cost allocation tags are key-value labels, such as team=checkout, attached to cloud resources so their cost can be grouped by owner, product or environment. On AWS a tag key only reaches billing data after it is activated for cost allocation, and tag keys and values are case-sensitive.
Billing & cost types
Amortized cost
Amortized cost spreads each commitment fee across the period it covers, so a one-year Reserved Instance or Savings Plan paid up front shows up as a share of the fee every day of the term instead of one large charge on the day you buy it.
Governance & planning
Budget
A budget is a planned spending limit for a period, such as a team's monthly cloud cost, with alerts when actual or forecasted spend crosses thresholds you set, such as 80% and 100%. On AWS, Azure and Google Cloud a budget warns rather than stops spending, unless you attach actions or automation to it.
FinOps foundations
Unit economics
Unit economics is measuring cloud cost per unit of business value, such as cost per order, per customer or per API call, by dividing what a product costs by how much it delivered. It shows whether spend is growing because the business is growing or because the product is becoming less efficient.
Frequently asked questions
What is the difference between chargeback and showback?
Chargeback moves the cost into the team's budget in the company's accounts; showback only reports it. The allocation behind them can be identical.
Which cost basis should chargeback use?
Usually amortized cost, so a team that bought a commitment isn't charged the whole upfront fee in one month. State the basis in the policy and keep it fixed.
What about costs nobody owns?
Keep them central, report them and work them down rather than charging them out by guesswork. Disputed charges cost more trust than the money is worth.
