Beta

Reports Allocation and chargeback

Cost allocation

What each team, cost centre or project cost in a month, by your own tags, with its share of the costs your teams share. The showback statement, one line per team.

What it shows

One month at a time, for one of your tag keys, such as Team, CostCenter or Project: a line for each of its values with the value's own cost, a column for each shared cost with the value's share of it, the total, and the total's share of the month. The cost no tag carries is a line of its own, (untagged), never hidden inside a team. A headline gives the month's total, how much of it is tagged, how much is shared, and how much of the tagging came from the bill and how much from your resources' current tags. The current month is projected to its end; any of the twelve before it can be opened. The statement downloads as CSV for finance.

A shared cost is cost several teams use and no single tag can carry fairly, such as a shared VPC's NAT gateways, a support plan, a shared cluster or the untagged cost itself. Your admins name it, pick its cost by accounts, services or tag values, and choose how it is split: in proportion to each team's own cost, evenly, or by fixed percentages finance agreed on. Each piece of cost goes to the first shared cost that picks it, so nothing is counted twice, and the shares always add up to the shared cost exactly.

Questions it answers

  • What did each team cost us last month, including its part of what the teams share?
  • How much of our AWS bill carries a team tag at all, and what is left untagged?
  • What is each team's share of the NAT gateways, the support plan and the shared cluster?
  • What do we send finance for showback this month?

What it reads

The same daily cost as budgets and unit costs: the amortized bill from your Cost and Usage Report for every day it holds, and the hourly run rate after that, so a team's figure, a budget and a cost per unit on the same accounts agree to the cent. Each cost line takes its tag from the bill when you activated the key as a cost allocation tag in AWS Billing, which keeps the tag each month had; otherwise from the resource's current tags in the daily inventory, which moves a resource's history with it when it is re-tagged. Cost without a resource, such as support, tax and credits, is untagged. Nothing it reads adds to your AWS bill.

What to do with it

Name your tag keys on your company's page, and activate each as a cost allocation tag in AWS Billing so a closed month's figures stay as they were. Start with the untagged line: the AWS resources report shows which resources lack the tag, and the infrastructure findings check a required-tags rule. Then name the shared costs the teams agree on, and send each team its line each month. A member whose groups see only some teams sees only those teams' lines.

Related reports

  • AWS cost per day, bill and analysis: What AWS cost per day, from the bill for each day it holds whole and the run rate after that, by account and service.
  • AWS resources: Every resource the daily inventory found, with its cost, by type and by its Environment and Team tags.
  • AWS infrastructure findings: Every resource checked against rules once a day, required tags among them.

The hosted plan has every report, and is free during early access: see pricing. The statement opens on this month or any of the twelve before it, and downloads as CSV. All reports.