Cloud cost
Showback vs. chargeback
Showback reports each team's cloud spend for visibility only; chargeback bills that spend back to the team's budget.
Last updated
Definition
Showback is the lighter-weight, more common practice: each team sees a report of what its tagged resources cost, with no accounting entry attached. The goal is awareness and behavior change, not a budget transfer. Chargeback goes further, moving the actual dollar amount into the consuming team's cost center, which creates real financial accountability but also real organizational friction if the underlying tagging and allocation isn't accurate.
Most teams that aren't already running a mature FinOps practice get most of the behavioral benefit from showback alone, and save chargeback for cost centers large enough that the accounting overhead is worth it.
Where it shows up
Showback and chargeback both draw on the same tagged cost data, but showback surfaces it as a report a team can view for awareness, while chargeback moves the dollar figure into the consuming team's own cost center inside the finance system, with a real accounting entry attached to it.
What makes it expensive
The trap here is adopting chargeback before tagging and allocation are accurate enough to support it, creating real organizational friction over a number nobody fully trusts. A team billed off a number it can dispute will dispute it, once, and the program rarely recovers from that. Coverage has to be high, and stay high, before the first internal invoice goes out.
Related
More in Cloud cost
- Committed use discount (CUD)
- Reserved instance (RI)
- Savings plan (SP)
- On-demand vs. spot instances
- Data egress
- Amortized, blended, and unblended cost
- Billed vs. effective vs. list vs. contracted cost
- Rightsizing
- Idle and orphaned resources
- Storage class
- Lifecycle policy
- Incremental snapshot
- Allocatable capacity
- Requests vs. limits
- Cluster idle
- Workload idle
- Bin packing
- Cost allocation tags
- Tag coverage
- Unallocated spend
- Unit economics
- RI/SP coverage and utilization
- Observability tax
- Metric cardinality
- High-water-mark billing
- Log ingest vs. index
- Snowflake credit
- Auto-suspend / resume minimum
- BigQuery slot
- Bytes scanned & partition pruning
- Time Travel & Fail-safe
A total nobody owns, nobody fixes.
An unattributed cost stays unowned. CostMon assigns spend to an owner, so someone can act on it.