Cost centre allocation gives every line of the cloud bill two owners: the team that can change the usage, and the cost centre that carries the cost in the books. Often they are the same unit, but not always, and a cost allocation that records only one of them fails at the other. Without a team, a recommendation reaches nobody who can act on it; without a cost centre, no budget can be run and no month-end close can be split. Two mechanisms rest on mapping both, showback and chargeback: reporting cost to its owner, and charging it to the owner's cost centre.
How it works
Team and cost centre
The team is the operational owner. It decides the size, running time and architecture of the resources, and recommendations, anomalies and budget alerts should reach it. The cost centre is the financial owner, a unit in the chart of cost centres that costs are booked to and budgets are planned against. In the FinOps Foundation's Allocation capability, choosing the units cost is allocated to falls to the Finance persona, while putting the metadata on resources falls to Engineering (see core and allied personas in the FinOps framework).
The two mappings drift apart when several teams book to one cost centre, when a platform team runs resources for several cost centres, or when a reorganisation renames, merges or splits cost centres while teams and resources stay unchanged. The mapping holds up when a table with an effective date leads from what the resource carries (the team, the product, or a cost-center value as tags and labels lists it) to the current cost centre. A reorganisation then changes rows in that table instead of hundreds of tags.
Showback and chargeback
The FinOps Foundation covers both mechanisms in its Invoicing & Chargeback capability, part of the Manage the FinOps Practice domain. It places the difference in formality, not maturity: chargeback is not a more advanced form of showback, and not every organisation needs it.
| Showback | Chargeback | |
|---|---|---|
| What happens | cost is reported to its owner | cost is charged to the cost centre in the accounting system |
| Granularity | anything: team, product, environment, feature | the cost centres in the chart |
| Completeness | a visible remainder without an owner is acceptable | the whole invoice is booked; whether shared and unallocated cost goes to consuming cost centres or stays in a central budget is for finance and the controller to decide |
| Data | continuous, provisional data included | at the close, where needed on estimates reconciled once the data is final or after a restatement |
| Agreed with | the team | finance and the controller, on keys, timing and cost basis |
Chargeback therefore needs what showback can do without: an agreed destination for every line, a consuming cost centre or a central budget, including shared cost and the unallocated remainder, and agreement with finance on which data state and which cost basis get booked. The FinOps Foundation's Allocation capability describes both destinations for shared cost as the organisation's choice.
Provider fields
Only Azure has a field of its own for the cost centre. Its cost details carry CostCenter for EA and MCA, described as the cost centre defined for the subscription; for MCA, Microsoft fills it only in open billing periods. Under an Enterprise Agreement, departments group enrollment accounts, and both carry a cost centre as a property maintained by department admins and account owners respectively. The cost details hold the department name in InvoiceSectionName. A department contains usage only, though, and no purchases such as reservations or Marketplace.
AWS and Google Cloud have no such field. On AWS the cost centre comes from a tag on the resource, from an account tag that covers the whole account, or as the value of a cost category, which maps accounts and tags to values by rules and appears in the CUR 2.0 column cost_category. For applications priced per user (Amazon Q Business, Amazon Q Developer and Amazon QuickSight), AWS can take up to four user attributes from IAM Identity Center as cost allocation tags: Cost center, Division, Organization and Department. On Google Cloud a label on the resource or the project carries the cost centre, in the export under labels or project.labels, or a folder in the resource hierarchy represents it. Tags and labels covers how such keys are applied.
What it means for your cost
The same invoice yields two views: one per team, for decisions about usage, and one per cost centre, for budgets and the close. Both add up to the invoice. Each line belongs to exactly one team and exactly one cost centre, or it sits visibly in the remainder; a line in two cost centres is counted twice, a line in none is missing. Segments and hierarchies covers how several such dimensions coexist over the same data.
The cost basis decides who carries commitments. On billed cost, a purchase of reservations or Savings Plans stays with the account or billing level that bought it; on amortized cost it spreads over the usage that consumes it. Which basis gets booked is for finance and the controller to settle. How an internal charge is treated in the accounts is a question for the company's controller and auditor; the billing data supplies the amounts and where they came from. The team view is also the numerator for unit costs, and who owns which view in which role is described in FinOps roles and responsibilities.
Where it goes wrong
- A cost centre tag with no dated mapping. Symptom: after a reorganisation, reports show old and new cost centres side by side, and some resources carry numbers that no longer exist. Cause: the cost centre exists only as a tag value on the resources, with no dated table translating old values into new ones; every change means retagging, and a tag only counts from the day it is set.
- Chargeback without complete allocation. Symptom: the charges add up to less than the invoice, and the difference lands, unexplained, with IT. Cause: no destination was agreed for shared and unallocated cost, so whatever no rule reaches stays with the unit that pays the invoice.
- An empty cost centre in closed Azure months. Symptom: cost details for closed months under a Microsoft Customer Agreement lack a value in
CostCenter, while the current month has one. Cause: Microsoft provides the field for MCA only in open billing periods; a separate mapping from subscription to cost centre bridges the gap. - Only one of the two mappings. Symptom: recommendations go to cost centre managers who do not know the resources, or teams see cost that reaches no cost centre. Cause: either the team or the cost centre was recorded, not both.
- Showback dropped as a first stage. Symptom: since chargeback started, teams see their cost only as a booking after the month-end close. Cause: showback was treated as a stage that chargeback replaces, although the teams' running view is exactly what showback provides; the FinOps Foundation separates the two by formality, not maturity.
Sources
Read on 2026-10-16. FinOps Foundation Invoicing & Chargeback capability and Allocation capability (CC BY 4.0); Microsoft cost details fields, EA billing administration on the Azure portal and understand and work with scopes; AWS organizing costs using AWS Cost Categories, CUR 2.0 cost category column, using account tags for cost allocation and using user attributes for cost allocation; Google Cloud Structure of Standard data export.