For years, the hardest part of multicloud cost reporting was not the analysis, it was getting four providers to speak the same language. AWS called a column one thing, Azure another, Google a third, and every cross-cloud report started with a custom mapping job that broke whenever a provider changed their export. FOCUS, the FinOps Open Cost and Usage Specification, ends that by defining one common schema every cloud can publish to, so a cost dataset from any provider has the same columns and the same meanings.
FOCUS, the FinOps Open Cost and Usage Specification, is an open standard maintained by the FinOps Foundation under the Linux Foundation that defines a single common format for cloud and SaaS billing data: a fixed set of column names, definitions, and value formats that every provider can export to. The point is normalization at the source, when AWS, Azure, Google Cloud, and OCI all publish a FOCUS dataset, their billing exports share the same schema, so one query or dashboard works across all of them without custom per-provider mapping. FOCUS is the foundation that makes genuine multicloud cost visibility practical rather than a permanent data-engineering project.
This article is part of the complete guide to cloud cost visibility and tooling. We work with FOCUS-formatted data across the 500-plus environments we have optimized since 2019, and it has changed the economics of multicloud reporting: the normalization work that used to consume weeks now starts from a common schema, so the time goes to analysis instead of plumbing.
Before FOCUS, each cloud's billing export had its own column names, its own way of representing discounts and commitments, and its own quirks. Building a single view of spend across providers meant maintaining a fragile translation layer that mapped each provider's format into a common model, and re-fixing it every time a provider changed something. This is the normalization burden detailed in how to normalize cost data across clouds. FOCUS moves that normalization upstream to the provider, so the data arrives already in a shared shape.
FOCUS standardizes the billing dataset along a few axes: a consistent set of columns such as billed cost, effective cost, the service and resource identifiers, the charge category, and the commitment-discount fields, with precise definitions so the same column means the same thing everywhere. Crucially it standardizes how amortized and effective costs are represented, which is exactly where providers used to differ most and where cross-cloud commitment analysis used to break. The result is that a FOCUS row from one cloud is directly comparable to a FOCUS row from another.
One of FOCUS's most useful standardizations is the distinction between billed cost, what appears on the invoice for the period, and effective cost, the amortized cost that spreads commitment purchases across the term they cover. Having both, defined identically across clouds, is what lets you compare true consumption cost across providers rather than comparing invoices that account for commitments differently.
FOCUS has matured quickly. Version 1.0 established the core schema; version 1.2, ratified in 2025, extended coverage so SaaS and PaaS billing can sit in the same schema as cloud usage; and version 1.3, ratified by the FOCUS Steering Committee in December 2025, added support for tracking contract commitments, allocating shared costs, and verifying data freshness. Because the spec is evolving, confirm which version a given provider's export currently conforms to against the FinOps Foundation documentation and the provider's own docs before you build on it, since adoption and version support vary by cloud.
FOCUS is not an end in itself, it is the enabler for everything downstream. A common schema is what makes a single multicloud cost dashboard maintainable, what lets you compare cost per unit across providers honestly, and what reduces the build-versus-buy calculus for tooling because the hard part, normalization, is increasingly solved at the source. The more providers and tools speak FOCUS, the less of your FinOps budget goes to data engineering and the more goes to the decisions that actually lower the bill.
We build FOCUS-based cost data pipelines and multicloud reporting that give you one honest view of spend across AWS, Azure, GCP and OCI. It is the See step of our method, the data foundation every other saving depends on.
Get a FinOps implementation plan →FOCUS standardizes the shape of billing data, not the meaning of your business. It gives every provider's export the same columns, but it does not tag your resources, build your allocation rules, or decide what a unit of value is for your organization, that work still sits with you, and it still depends on disciplined tagging and good native exports, whose gaps are covered in the limits of native billing consoles. FOCUS removes the translation tax; it does not remove the need for a FinOps practice on top of clean data.
FOCUS is the data standard at the base of modern cost visibility, the reason multicloud reporting is finally tractable. Read the complete guide to cloud cost visibility and tooling for the full picture, see how to normalize cost data across clouds for the work FOCUS reduces, and download The Multicloud Visibility and FOCUS Guide for adoption guidance and a schema reference. When you want a FOCUS-based data foundation built 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.