FinOps 1013 min read
ByJubril Oyetunji
FinOps 101: Chargebacks vs showbacks
Understand what each team spends, divide shared infrastructure costs, and decide whether those costs belong in team budgets.
A recurring challenge when explaining why FinOps matters is that some of the terminology isn't intuitive. Chargebacks and showbacks are a good example. Both start by working out which teams use your infrastructure and what that usage costs.
Chargebacks assign those costs to a team's budget through an internal accounting process. Showbacks report the costs to teams without charging their budgets. Either approach can include a team's own resources and its share of common infrastructure.
In this post, you'll learn how to divide shared costs, use showbacks to help teams plan their spending, and decide when to introduce chargebacks.
Why is this important for teams?
Your cloud provider's invoice shows the total amount billed. It doesn't necessarily tell the product team what its new feature costs, or the data team how much it spends on training jobs.
Imagine an organization spending $10,000 a month. Product uses $5,000 directly, data uses $2,000, and a shared platform costs $3,000. That platform might include a Kubernetes cluster, monitoring, or networking.
The teams agree to split the platform cost 60/40. Product receives $1,800, bringing its total to $6,800. Data receives $1,200, bringing its total to $3,200.
The animation shows how those team totals add up to the same $10,000 bill.
Showbacks help teams understand their costs while finance pays from a central budget. Chargebacks, on the other hand, enable finance to charge those amounts to each team's budget.
How showbacks improve cost visibility
The primary goal of showback is cost awareness. When teams can see what they consume and what it costs, they can plan around it.
Give teams ownership of their costs
Teams can investigate their own costs without treating every increase as a mistake. Higher spend might reflect more customers or capacity reserved for reliability. Showback gives the team a starting point to explain the change.
Make planning more concrete
Engineers and finance can budget for both direct and shared costs. Reviewing them regularly helps teams plan for growth and check whether changes, such as reducing idle capacity, lower spend.
Make shared costs easier to discuss
Documenting the allocation helps teams understand and question their share. The 60/40 split in this example is an agreed rule. You can also allocate by measured usage or fund some costs centrally. The FinOps Foundation's allocation guidance describes these options.
Choosing between showbacks and chargebacks
Start with showback when teams need visibility or finance pays from a central budget. It gives teams time to check the allocation and resolve unclear costs.
Use chargeback when costs need to be recorded against departmental budgets. Agree on the reporting period, how shared costs and credits are handled, and how teams can challenge an allocation.
You can use both. Finance might charge a business unit while its engineers use showbacks for individual services. The FinOps Foundation's chargeback guidance makes the choice about accounting needs, rather than maturity.
Start with your team's spend
In CostGraph, use virtual tags to group spend by team, split shared costs, and review each team's total. The showback guide walks you through it.
Sign up for CostGraph to see how each team's spend contributes to your bill.