Unallocated Spend and Resource Mapping
Make missing ownership visible rather than distributing it arbitrarily.
Unallocated spend is a control, not an error to be concealed. It represents cost facts for which CoreFinOps cannot establish an authorized, reproducible business assignment under the current rules.
Why spend remains unallocated
Common causes include missing application IDs, incomplete resource tags, shared resources without a split rule, unknown workload owners, adjustment line items and incomplete discovery coverage. A CloudFormation role may validate while certain resource types remain out of collection scope.
Investigation workflow
- 1
Confirm the billing period and currency
Check Overview or Explorer before investigating individual resources.
- 2
Open Architecture → Unmapped Resources
Review resources lacking business context.
- 3
Inspect tag-based suggestions
A suggestion conveys evidence and confidence; it is not a confirmed assignment.
- 4
Approve or create a scoped financial rule
Approve a direct assignment or create a scoped financial rule with an owner and rationale.
- 5
Run allocation and compare
Compare the new result without discarding the prior as-calculated version.
Shared infrastructure
A shared NAT gateway, load balancer or other shared resource may support multiple workloads. A documented percentage split may be appropriate; an automatic equal split is not the default and requires an explicit policy.
Success criteria
Better coverage means more spend is defensibly mapped, not that the dashboard always reaches 100%. If an unexplained balance remains, keep it visible along with its period, value and source context.
Concept