The Second Budget

Yesterday I wrote about the price history nobody keeps for you (Old Chips Are Supposed to Get Cheaper). This post is about the other end of the transaction: the budget. A budget sounds like the most straightforward number in the entire cost conversation. It is a number. Somebody approved it. Spending is supposed to live inside it. In the cloud, at any real scale, that is not how it works.

The layer everyone sees

The official layer is real. Cost centers exist. Each one has a budget. Finance expects the cloud bill to split along those lines, so the platform team stands up chargeback: tags, accounts, allocation rules, a monthly file that posts into the accounting system. The FinOps Foundation draws the line cleanly: the difference between showback and chargeback is the formality of “sending expenses to official accounting budgets,” and “chargeback is dependent on organizational accounting policies.”¹ On paper, the machinery is complete.

Where it breaks

Then the cloud bill arrives. A $12,000 enterprise support charge “isn’t being distributed to any of the teams and would need to be determined how to be paid.”² Shared services (observability, the data platform, the shared clusters) generate charges that no single cost center owns. A savings plan purchased centrally lands on the team that bought it, not the team that consumed the discount. The Foundation’s own worked example shows teams held “accountable for more or less than their actual usage.”³

So even when there are officially allocated budgets with cost centers, you end up needing another layer of budget. I have had to build one at every scale I have worked at.

The pretend budget

Here is what actually happens, from my own experience. You take finance’s budget and apply corrections to it. You reallocate the shared costs the way the teams actually experience them. You fold the discounts in where they really land. You keep some margin for the month’s surprises. That number is the one you manage cloud against. It is not in the accounting system. Nobody announces it in a policy email.

And it takes a couple of years for people to stop calling it the pretend budget. It is not one. But the name sticks until finance is in on it.

The conversations are the funny part, if you can laugh at them. You end up in meeting after meeting where somebody asks: “OK, which budget is it? Is it the real budget or is it your fake budget?” This happens at every large company, because every large company has to do this. That question is the thing you want to avoid, and the only way to avoid it is to get finance to build it with you.

The actual budget

Because here is the thing. When you sign a purchase order, when you hire somebody, that money comes out of the actual budget, finance’s budget, the one in the accounting system. Microsoft’s FinOps guidance puts the split plainly: “Chargeback is represented in the accounting system. Budgets are managed through the budget system.”⁴ Two systems, two calendars, two owners, and nothing keeps them synchronized.

So you will be in those conversations, and finance will look at the second budget and say: wait, what did you do? And the explanation is the whole job in one sentence.

To manage cloud and account for shared services, we took your budget and applied some corrections to it so it makes more sense for how we manage cloud.

Say that to the wrong finance partner and they laugh and keep calling your budget the fake budget. Then you have no way to influence your customers, because nobody believes your numbers. The relationship with finance is not a soft skill next to the real work. It is the mechanism that makes the second budget credible. You have to partner with finance to get this right.

Not purely engineering

This is why FinOps is never really a purely engineering function. The book makes the same point from the other direction: a budget states how much the organization intends to spend, and enforcing it takes separate mechanisms (chapter 7). At scale there are at least two budgets. The one on the books feeds accounting. The one you actually steer by is the one you built. The second one only stops being “fake” when finance is in the room where it is made.

Sources

---

1. FinOps Foundation, “Invoicing & Chargeback,” FinOps Framework capability, accessed October 21, 2026: Invoicing & Chargeback — “The primary difference between showback and chargeback is the formality described in this capability of sending expenses to official accounting budgets”; “Showback is always required in any FinOps practice, but chargeback is dependent on organizational accounting policies.”↩︎

2. FinOps Foundation, “Managing Shared Cloud Costs,” working-group report, last updated January 9, 2026: Managing Shared Cloud Costs — the $12,000 enterprise support example: “The $12,000 enterprise support charge isn’t being distributed to any of the teams and would need to be determined how to be paid”; “certain teams or business units may be held accountable for more or less than their actual usage.”↩︎↩︎

3. Microsoft Learn, “Invoicing and chargeback,” FinOps on Microsoft Cloud, updated April 1, 2026: Invoicing and chargeback — “Chargeback is represented in the accounting system. Budgets are managed through the budget system.”↩︎