Skip to content
Cost allocation

Unallocated cloud costs: resolve ownership without hiding exceptions

Turn unallocated cloud and AI spend into a manageable exception queue. Distinguish missing metadata, shared services and overlapping rules.

1. Classify the reason, not just the amount

A missing owner can mean a new account, an absent project identifier, an outdated rule, a shared service or a source that never supplies the needed dimension. Those situations require different fixes. Start with the largest amounts and record the reason and available evidence.

Keep the provider, stable source identifier, period and currency with each exception. Do not label every unmatched item “untagged”: a project can have tags that are unavailable in the current reporting data.

2. Inspect rule order and matching

Review the active rules against the actual dimensions returned by each source. Check exact values, renamed projects and overlapping patterns. A broad rule can capture a specific account before its intended rule is evaluated.

Choose one deterministic winner for a cost item and explain that choice. Before changing a rule, inspect which other items would move. Keep the old and new policy versions so a historical statement remains understandable.

3. Keep shared cost a deliberate choice

A shared platform service is not necessarily missing metadata. Decide whether to retain its cost centrally or allocate it with an agreed driver. A usage measure, seat count and fixed proportion produce different statements.

If the driver is unavailable, mark the limitation and keep the shared bucket explicit. Do not fabricate usage or infer ownership from a similar project name. A disputed attribution should have a review owner and due date.

4. Preserve the total

After a mapping change, compare the sum of assigned, centrally retained and unallocated amounts with the same source total. Categories must be exclusive. Investigate duplicates or omissions before distributing the statement.

For a coverage measure, document which charges are eligible and how credits are treated. A ratio based on a small net total can be misleading. If the denominator is zero or invalid, show the measure as unavailable.

Source total = assigned cost + centrally retained shared cost + unallocated cost

5. Prevent the next exception

Make ownership part of the process for opening a source account or project. Record a stable owner mapping and review it when teams change. The goal is not to force every provider into an identical metadata model.

The guide below explains allocation with a worked example: assigned costs, shared services and amounts still to clarify. Review new cases at the monthly meeting and keep their amounts visible.

Sources & further reading