Skip to content
Finitizer

Cost Allocation Score

Upload a billing export and get a score out of 100 for how much spend you can assign to teams.

Multi-cloudReads your own dataBring a file
New here? See what this tool does, how to use it and how to get your data.

Learn more

Cost Allocation Score

What this free tool does for you

Cloud spend that no team owns cannot be charged back, budgeted or cut. Score how much of your bill you can assign to a team, out of 100, and get the fixes ranked by dollars.

How to use it

  1. Click Choose a billing export and pick a full month, or click Try a worked example.
  2. In Required tags, list the tag keys your policy says every resource must carry, separated by commas.
  3. Read your score and grade, then How the score breaks down to see where you lost points.
  4. Work down Fix these first: spend missing a required tag, with the biggest dollars at the top.
  5. Use Download the fix list as CSV, under the score, to send the list to the teams that own the spend.

Good to know

  • Tagged, but scored as untagged? On AWS, cost allocation tags must be activated in the billing console before they appear in the export.
  • A fair score. Tax, support and other charges that cannot carry a tag are left out, so they do not count against you.
  • Private. Your file is read in this browser tab and never uploaded.

Not sure where to get the data? .

Before you start: what to have readyShow
  • One billing export with tag or label columns included. Tags are opt-in on AWS cost allocation and have to be activated in the billing console before they appear in the export at all.
  • A full month. Allocation coverage is a share of spend, and a partial export skews it towards whatever ran early in the period.
  • Your list of tag keys that are supposed to be mandatory. The score is far more useful measured against the policy you have than against every key that happens to exist.
or drop an AWS CUR, GCP billing export, or FOCUS file (Azure: the FOCUS export) here

Your file is read in this browser tab and never transmitted. Tag values can contain customer names, so resource IDs are hashed by default and tag values are shown only in aggregate.

Want this done on your real bill?

FinOps-as-a-Service: A FinOps practitioner works with your team every month, so cost reviews happen without you hiring one. From $1,500 a month. Nothing paid upfront.

See the service

Untaggable charges are excluded, not counted against you

Tax, support, marketplace purchases, commitment charges and data transfer that names no resource cannot carry an allocation tag on any cloud. Counting them as “untagged” produces a score that is both wrong and demoralizing, 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.

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, marketplace items, data transfer that names no resource, cannot carry a tag at all. This tool measures the share missing a tag your policy requires.

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, the share of taggable spend carrying every required tag, or any tag of yours when none are entered (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. The file is read and analyzed in your browser tab and is never transmitted. Tag values can contain customer names, so resource IDs are hashed by default and values are only ever shown in aggregate.

Related tools

More tools for: Billing data, allocation and governance

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.

See how Finitizer works

Rate this tool

How would you rate the Cost Allocation Score?