# FinOps and Cloud Bills

> Why cloud bills grow faster than anyone thinks, and how to get coders and finance to share them. Who sees the bill, who pays it, and one format for all.

**Course:** [Virtualization and Cloud Computing](https://learn.benibix.com/learn/infrastructure-virtualization)  
**Time:** 11 min

**After this lesson you can:**

- Say what FinOps is for
- Tell showback from chargeback
- Explain why a shared bill format helps

## Who spends the money, and who sees the bill

FinOps is a way to run cloud spending as a team sport. Coders, finance and managers look at the same bill, often each week. They share the job of keeping it in check. It exists because in the cloud, anyone who can start a server can spend money. The bill comes a month later.

In a data centre, buying a server took weeks and a signature. In the cloud it takes a click. So costs spread across dozens of teams, and nobody feels the total until it lands on one desk.

FinOps runs in a loop of three steps. Inform: show each team what it spends. Optimize: cut waste and buy smarter. Operate: make it a habit, with goals and owners. Then the loop starts again.

Showing each team its share starts with labels. Each server and disk is tagged with the team that owns it. Showback then sends each team a report of its share, while one central budget still pays the whole bill.

Chargeback goes a step further. Each team's share comes out of that team's own budget. People watch spending far more closely when it is their money, but it takes clean labels to be fair.

Firms that use several clouds get bills in several formats, with different names for the same thing. FOCUS is a shared format for cloud bills. Bills from different clouds then line up, column by column, in one sheet.

The mistake is to make FinOps one person's job. A single analyst can find waste, but only the engineers who started those servers can turn them off. The habit has to live in the teams that spend.

![One cloud bill of 50,000 euros is split by labels into three teams: web, data and sales. From there two paths run. In the top path, showback, each team gets a report and one central IT budget pays the whole bill. In the bottom path, chargeback, each team's share is taken out of that team's own budget.](https://learn.benibix.com/diagrams/inf-showback-chargeback.svg)

### Example: A test server nobody owned

A software firm's cloud bill rises 30% in three months. No team thinks it is theirs.

They tag every server by team. A weekly report then finds 14 large test servers left running since a project ended. Turning them off saves 9,000 euros a month.

**Words in this lesson:** [FinOps](https://learn.benibix.com/term/infrastructure/finops), [Showback](https://learn.benibix.com/term/infrastructure/showback), [IT Chargeback](https://learn.benibix.com/term/infrastructure/it-chargeback), [FinOps Open Cost and Usage Specification (FOCUS)](https://learn.benibix.com/term/infrastructure/focus-specification)

**Question:** How is showback different from chargeback, when you split a cloud bill by team?

**Answer:** Showback shows each team its share. Chargeback takes it from the team's budget. Both split the bill by team. With showback a central budget still pays. With chargeback each team pays its own share.

---

Source: https://learn.benibix.com/learn/infrastructure-virtualization/finops-and-cloud-bills
Author: Behnia Zarei (a developer in Vienna, Austria, who builds and teaches data, AI and business intelligence at BENIBIX)
Publisher: BENIBIX Learn (https://learn.benibix.com/)
Last updated: 2026-11-19
Licence: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Quote freely with attribution.
