Ask most engineering orgs "what did the payments team spend on AWS last month" and the honest answer is a shrug and a spreadsheet. The bill is organized by service and account, not by the teams that incur it. Chargeback and showback — handing each team its share of the bill — only works when every dollar has an owner. Getting there is a data problem before it is a finance problem.
Tag coverage is the gate metric
Allocation runs on tags: team, environment, cost-center, whatever your taxonomy is. The first question is not "how do I allocate" but "how much of my spend is even taggable right now." CloudQuell computes tag coverage — the share of cost carrying the tags you allocate on — as a first-class number, broken down so you can see which accounts and services drag it down. If coverage is 60%, no allocation report built on those tags is trustworthy, and the number tells you so before you present it to finance.
The 20% that will never be tagged
Some cost is structurally untaggable or shared: a NAT gateway three teams route through, data transfer, support charges, a shared observability stack. Waiting for perfect tags means never allocating these at all. Allocation rules handle them — split a shared cost across cost centers by a fixed ratio or proportionally to their other spend, and route untagged cost to the owning team by account or by pattern. The goal is not perfect tags; it is 100% of the bill allocated, with the assumptions written down.
Cost centers that roll up
Teams ladder into groups, groups into departments, departments into the whole bill. CloudQuell models cost centers as a hierarchy, so a VP sees their org's total and drills to the team that moved it off the same allocation rules — one model, not a separate dashboard per level of the org chart.
Why "adds up to the whole bill" is the bar
A chargeback report that covers 80% of spend invites the same argument every month: teams dispute the number because the missing 20% is clearly someone else's. The moment every dollar is allocated — tagged directly or assigned by an explicit, visible rule — the argument moves from "this is wrong" to "let's change the rule," which is the conversation you actually want. Reconciliation to the total is the difference between a report finance trusts and one they redo by hand.
Connect a read-only IAM role and CloudQuell scores your tag coverage and lets you allocate the rest — every dollar owned, reconciled to the whole bill.
Try CloudQuell →