Cost Allocation Score
Upload a billing export and get a score out of 100 for how much of your spend can actually be attributed to a team — with untaggable charges excluded rather than counted against you, and a fix list ranked by unallocated dollars, not resource count.
Your file is read in this browser tab and never uploaded — there is no backend here to upload it to. Tag values can contain customer names, so resource IDs are hashed by default and tag values are shown only in aggregate.
Untaggable charges are excluded, not counted against you
Tax, support, data transfer, marketplace purchases, and commitment charges cannot carry an allocation tag on any cloud. Counting them as “untagged” produces a score that is both wrong and demoralising, and it is the main reason homegrown tag reports get ignored after the second circulation.
This tool classifies each charge as taggable, untaggable, or unknown, and scores only the taggable portion — the variant the FinOps Foundation documents. Anything it cannot classify is reported separately rather than quietly bucketed, because pretending to certainty we do not have is the same error in different clothing. Full methodology, weights, and bands.
Frequently asked questions
What percentage of cloud spend should be tagged?
The FinOps Foundation puts the initial goal at under 10% untagged, measured against taggable spend rather than all spend. Zero is unattainable because some charges — tax, support, data transfer, marketplace items — cannot carry a tag at all.
Why is my score higher than my raw tag coverage?
Because untaggable charges are excluded from the denominator rather than counted against you. Most tag reports do not do this, which is why they produce numbers that feel unfairly bad and get ignored. Support and tax cannot be tagged, so scoring you on them measures nothing you can change.
My AWS resources are tagged but the tool says they are not.
On AWS, cost allocation tags must be ACTIVATED in the billing console before they appear in the Cost and Usage Report at all. Until then, a fully tagged resource looks identical to an untagged one in the export. That is the first thing to check.
How is the score calculated?
Five weighted components: coverage of taggable spend (40), completeness against your required tag set (25), key hygiene such as case and spelling variants (15), value hygiene such as placeholder values (10), and concentration — whether unallocated spend is a few fixable groups or a long tail (10). Every weight and band is published on the methodology page.
Is my billing data uploaded?
No. This page has no backend, so there is nowhere for it to go. The file is read and analysed in your browser tab. Tag values can contain customer names, so resource IDs are hashed by default and values are only ever shown in aggregate.
A score is a starting line.
Finitizer tracks allocation continuously, tells you whether new spend is arriving tagged (the number that says whether the policy is actually working), and opens the tickets to fix what is not — across AWS and Google Cloud.