Support fees, enterprise discounts, cross-account data transfer, the shared logging pipeline. Some of your cloud bill simply cannot be tagged to a team, and if you leave it in an unallocated bucket your showback never adds up and no one trusts the numbers. The fix is not to tag the untaggable. It is to choose a fair, transparent split and document the rule so the allocation holds up when someone challenges it.
Allocating untaggable costs is the practice of distributing the portion of your cloud bill that cannot be attributed to a single owner, such as support charges, negotiated discounts, tax, and shared platform services, across the teams that benefit from it using a defined and defensible rule. The goal is not perfect precision, which is impossible for genuinely shared costs, but a split that teams accept as fair so that 100 percent of the bill is allocated and the showback reconciles. An allocation that leaves a large unallocated remainder is one no one trusts, because the costs a team does not see are the costs it will never work to reduce.
This article is part of the complete guide to cloud cost governance. The methods below are how we allocate the unallocatable across the 500-plus environments we have optimized since 2019, where the disputes are almost never about the method itself and almost always about whether the rule was explained before the first invoice landed on someone's desk.
Before reaching for a split, separate the truly untaggable from the merely untagged. Much of what ends up in the unallocated bucket is just resources someone forgot to tag, which is a tagging-coverage problem you fix at the source, covered in how to audit tag coverage across clouds. The genuinely untaggable is a shorter list: support and premium-tier fees, enterprise discount and commitment adjustments, marketplace charges, tax, and shared platform services like central networking, logging, and security tooling that serve everyone. Only these need an allocation rule.
If half your unallocated bucket is just untagged resources, no split is fair, you would be distributing one team's costs across everyone. Drive tag coverage up first, then allocate only what is left, which is the genuinely shared spend. Splitting before you have fixed coverage spreads accountability gaps rather than closing them.
The most common and usually the fairest method is to distribute shared costs in proportion to each team's own tagged spend. A team that accounts for 30 percent of the attributable bill takes 30 percent of the support fee and the shared-services cost. This works because the things that scale with shared cost, support tier, networking, central tooling, tend to scale with how much a team uses the cloud overall. It is simple to compute, easy to explain, and hard to argue with.
For costs that genuinely do not scale with usage, a flat per-team fee like a fixed compliance tool, an even split across the consuming teams can be fairer than a proportional one. Use this sparingly and only where the benefit really is equal regardless of size, because applied to scaling costs it overcharges small teams and undercharges large ones. The test is whether a team twice the size genuinely gets twice the benefit; if yes, use proportional, if no, even may fit.
Where a shared service emits a usage signal, allocate by that signal rather than by overall spend. Split a shared logging platform by log volume ingested per team, a shared data pipeline by records processed, a shared cluster by namespace resource consumption. Usage-based keys are the most accurate method for shared services and the most defensible, because the split tracks actual consumption. The trade-off is the effort to capture the usage data, so reserve this for the shared costs large enough to justify it. The broader treatment is in cost allocation for shared and platform services.
Commitment and enterprise discounts are a special case worth getting right. If a team's spend benefits from a centrally purchased commitment, the discount should follow the spend, so teams see their net cost after the saving, not the on-demand rate. Burying discounts centrally hides the value of the commitment program and distorts every team's true cost. Distribute the discount proportionally to the spend that drew it down, so the allocation reflects what each team actually costs the company.
Whatever methods you choose, the single most important step is writing the allocation rule down and publishing it before the numbers go out. A team that sees an unexplained shared-cost line on its showback will dispute it; a team that was told in advance how shared costs are split and can see the calculation will accept it. Document which costs are allocated by which method, review the rule with finance and team leads, and surface the split transparently in your reporting. Fairness perceived is fairness that holds, and it is what makes showback and chargeback credible.
We design fair, documented allocation rules for the untaggable part of your bill, support, discounts, and shared services, so 100 percent reconciles and teams accept the numbers. It is part of the See step of our method that gives every dollar an owner.
Get a FinOps implementation plan →Allocating untaggable costs is what makes allocation complete. Read the complete guide to cloud cost governance for the full picture, see cost allocation for shared and platform services for the usage-key detail, and download The Cloud Cost Governance and Tagging Toolkit for allocation-rule templates. When you want allocation designed and reconciled for you, see our FinOps implementation service.
New commitment instruments, FOCUS changes, hyperscaler pricing shifts, and the plays that actually move a bill. No schedule, no filler.