FOCUS, the FinOps Open Cost and Usage Specification, is an open standard that defines a common schema for cloud cost and usage data, so that a bill from AWS, Azure, Google Cloud, or OCI can be read with the same column names and the same meanings. Before FOCUS, every provider exported billing data differently: the field that means effective cost is named one thing in one cloud and something else in another, accounts and projects and subscriptions all model hierarchy differently, and discounts appear in incompatible ways. Anyone managing multicloud spend had to build and maintain fragile translation layers. FOCUS replaces that with a single agreed format, and it is governed by the FinOps Foundation as a vendor neutral standard.
This explainer is part of our FinOps cluster and links up to the pillar, what is FinOps, a practical introduction for 2026. FOCUS support is now a core buying criterion; see the sibling guide on how to choose a FinOps tool, where data portability is one of the decisive factors.
What problem FOCUS solves
The core problem is that cloud billing data is not comparable across providers without heavy normalization. A finance team trying to answer a simple question, what did we spend per team across all our clouds last month, faced a different data shape from each provider and had to reconcile them by hand or with custom code. Tooling vendors each built their own normalization, so switching tools meant relearning the data. FOCUS attacks this at the root by standardizing the schema itself: the same fields, the same definitions, the same units, regardless of which cloud produced the data.
FOCUS is to cloud billing data what a common file format is to documents: it lets the same tools read everyone's data without a custom importer for each source.
What FOCUS actually standardizes
The specification defines a set of columns with precise meanings that every conformant export must use. The most important cover cost, usage, and the dimensions you slice by:
| FOCUS concept | What it normalizes |
|---|---|
| Billed and effective cost | List price versus the cost after discounts and commitments |
| Account and sub account | The provider hierarchy: account, subscription, project |
| Service and resource | What was consumed, named consistently |
| Commitment discount | How reservations and savings plans apply |
| Tags | Allocation metadata in a consistent place |
The distinction between billed cost and effective cost is one of the quiet wins. Different clouds historically reported commitment savings in confusing ways; FOCUS defines effective cost so that the number you compare across providers actually means the same thing. For anyone doing multicloud reporting, that single definition removes a recurring source of error.
Why FOCUS matters for FinOps
FOCUS lowers the cost of three things FinOps depends on. Multicloud reporting becomes a matter of reading one schema rather than reconciling several, which is why it pairs naturally with our guide on FinOps for multicloud environments. Tool portability improves, because data in a standard format moves between tools without re engineering, reducing lock in. And the talent pool widens: a practitioner who learns the FOCUS schema can work across providers and tools, rather than learning each one's idiosyncratic billing export from scratch.
Standardizing your cost data on FOCUS?
We help teams adopt FOCUS as their normalized cost layer and pick tools that support it natively, so reporting stays portable. Fixed fee, performance fee, or ongoing Managed FinOps. On the performance model, you pay only from realized savings.
Talk about FinOps implementation →How adoption is unfolding
The major providers have moved to offer FOCUS conformant exports, and a growing share of FinOps tooling can ingest and emit the format. Because the standard is still maturing, the practical advice is to treat FOCUS support as a forward looking requirement when selecting tools and to begin standardizing internal reporting on its definitions, rather than waiting for universal coverage. Verify the current conformance status of each provider's export against their documentation before you depend on it, since support is expanding release by release.
FOCUS and the See step of our method
In our See, Cut, Lock, Run method, the See step is about getting tagging plus normalized data so every dollar has an owner. FOCUS is the normalization layer that makes See work across clouds: it gives you one consistent dataset to attribute, budget, and report against, rather than four incompatible ones. Adopting it is one of the highest leverage moves a multicloud organization can make on the data side, because every downstream activity, allocation, forecasting, anomaly detection, gets easier when the underlying data is standard.
The FinOps Operating Model Blueprint covers how to build your reporting layer on FOCUS, what to require from tools, and how the standard fits the See step of the method.
The short version
FOCUS, the FinOps Open Cost and Usage Specification, is the open standard that normalizes cloud billing data into one schema across providers, defining cost, usage, hierarchy, commitments, and tags consistently. It cuts the cost of multicloud reporting, improves tool portability, and is becoming a baseline requirement for serious FinOps tooling. Standardize your cost layer on it. When you want help adopting FOCUS and building reporting on top of it, that is part of what our FinOps implementation service delivers.