Cloud billing data is fragmented by design. AWS, Azure and Google Cloud each describe the same charge in a different schema, with different column names and different definitions of what cost even means. Anyone who has tried to compare spend across three providers in one dashboard knows the tax that follows: custom ETL pipelines, hand-built mapping tables and arguments over numbers that should match but never do.

FOCUS removes that tax. It gives every provider one shared format for cost and usage data, so a single query works everywhere. For FinOps teams, that turns weeks of normalization into a column lookup. This guide explains what FOCUS is, how the specification is built, which providers support it today and where it still falls short.

What is FOCUS (the FinOps Open Cost and Usage Specification)?

FOCUS, the FinOps Open Cost and Usage Specification, is an open standard that defines a single vendor-neutral schema for cloud cost and usage data. It specifies a common set of columns, with fixed names and meanings, so billing data from any provider can be read, combined and analyzed the same way.

The specification is a community project maintained by the FinOps Foundation, which operates under the Linux Foundation. Hundreds of practitioners from cloud providers, software vendors and enterprises contribute to it. FOCUS began with cloud billing and now reaches across SaaS, PaaS, data center and AI spend, which makes it the closest thing the industry has to a universal language for technology cost.

If you are new to the standard, our FOCUS primer for beginners covers the fundamentals. This guide goes deeper into the schema, the versions and real provider support.

Where FOCUS stands in 2026: the version story

FOCUS has shipped four major versions in three years. The current release is FOCUS 1.3, ratified by the FOCUS Steering Committee on December 4, 2025.

Versions matter in practice because providers implement them on their own timelines. The format your provider exports today may trail the latest specification, and that gap decides which analyses you can run. Most teams roll out FOCUS in stages rather than all at once, starting with the datasets their providers already support.

What FOCUS actually looks like: inside the schema

A FOCUS dataset is a table of charges. Each row represents one charge, and every column has a defined name, data type and meaning set by the specification. That is the whole point: the column means the same thing no matter which provider produced the row.

The columns fall into a handful of families.

The specification is strict about internal consistency. The effective cost of usage has to reconcile against the billed cost of the purchases that funded it, so the numbers tie out across a dataset instead of drifting. Providers can add their own fields, but only behind an x_ prefix that marks them as extensions outside the standard. 

That single rule keeps a FOCUS file portable while still letting providers ship extra detail. Consistent service categories also make accurate cost allocation far easier, because a virtual machine is grouped the same way on every cloud.

BilledCost vs EffectiveCost: the column everyone asks about

BilledCost is the amount that lands on your invoice. EffectiveCost is what the charge actually costs after negotiated and commitment discounts, with prepaid commitments amortized over their term instead of hitting as a lump sum. For most cost analysis and trend reporting, EffectiveCost is the number you want, because it reflects the real economics of a resource rather than the accounting of when money moved.

Which cloud providers support FOCUS in 2026?

Every major cloud provider now publishes FOCUS data, though native support and version coverage differ.

AWS was the first major provider to ship native FOCUS exports and has since moved its FOCUS 1.0 Data Exports to general availability. Microsoft followed with a FOCUS dataset in Cost Management, and Google Cloud currently offers a BigQuery view rather than a one-click export. Beyond the hyperscalers, SaaS vendors including Datadog, Cloudflare, Snowflake and Fastly now publish FOCUS-aligned data, which extends the standard past raw infrastructure into the rest of the multi-cloud bill.

FOCUS vs AWS CUR: which one do you use?

FOCUS and the AWS Cost and Usage Report are not rivals. FOCUS standardizes cost data so it is comparable across providers. The CUR carries the deepest AWS-specific detail.

Split Cost Allocation Data for containers sits in CUR 2.0 and is not yet part of FOCUS 1.0, so many AWS teams export both and feed each into their cost reporting stack. FOCUS becomes the cross-provider layer, and the CUR stays the source for the deepest AWS questions.

Why FOCUS matters for your FinOps practice

FOCUS matters because it removes the translation layer between you and your cloud bill.

• One schema, one query: Write a cost query once and run it against every provider. The mapping tables and per-provider ETL jobs that used to break on every billing change disappear.

• 
  

• Portable skills: FOCUS is the shared vocabulary of FinOps, and the FinOps Framework guidance now uses FOCUS terms directly. A practitioner who learns the schema on one cloud is immediately productive on the next, which shortens onboarding and reduces key-person risk.

• Real efficiency: Because FOCUS carries a billed and effective cost on a single row instead of maintaining separate actual and amortized datasets, it produces roughly half the rows and a dataset about 30% smaller. That is a direct saving on storage and on the compute that scans it.

• It powers the core FinOps workflows: One clean schema is the foundation for chargeback and showback, commitment optimization, invoice reconciliation and unit economics. It also reduces vendor lock-in at the data layer, because your cost history stays portable even if your tooling changes.

The limits of FOCUS: what it does not solve yet

FOCUS is a standard, not a finished product. A few hard problems remain open, and an honest adoption plan accounts for them.

• No provider is fully conformant: Coverage is uneven. AWS's general-availability release closed 11 specification gaps but left 8 open, and Google Cloud still lacks a one-click export. The version and completeness you get depend on the provider, so validating each export matters more than assuming parity.

• Shared and split costs are still maturing: Allocating shared infrastructure across teams was largely provider-determined, with little visibility into the method. FOCUS 1.3 only just added columns that expose how those splits are made, so this is early.

• Commitment visibility was hard: Answering a question as simple as which commitments you hold and when they expire used to mean reconstructing terms from thousands of billing rows. The new 1.3 Contract Commitment dataset starts to fix that, but provider support will take time.

• FOCUS standardizes data, it does not optimize it: The specification gives you clean, comparable cost data. It does not find waste, rightsize resources or forecast spend. For that you still need a cost intelligence platform on top, and the cleaner your FOCUS data, the better that layer performs.

• Adoption takes real work: Practitioners consistently cite time, internal skills and waiting on vendors as the main barriers. The format is free, but the rollout is a project.

How to get started with FOCUS

Getting value from FOCUS takes four practical steps:

1. Turn on native FOCUS exports in each provider: Data Exports in AWS, the FOCUS dataset in Azure Cost Management, the BigQuery view in Google Cloud and the export in OCI. Choose the highest version each provider supports.

2. Land everything in one place: Send the exports to a single warehouse, an S3 and Athena setup or BigQuery. Because the schema is shared, you need one ingestion path instead of one per provider.

3. Standardize on EffectiveCost for analysis and trend reporting, and keep BilledCost for invoice reconciliation. Agreeing on this once prevents most reporting disputes later.

4. Query, then layer a platform: Start with the FinOps Foundation's FOCUS query library, then connect a tool that reads FOCUS natively. 

Amnic ingests FOCUS-aligned multi-cloud data and adds allocation, anomaly detection and forecasting on top, which is where cloud FinOps turns clean data into actual savings. You can book a demo to see it against your own bill.

The bottom line

FOCUS is the de facto standard for cloud cost data and the foundation that modern FinOps workflows now assume. The specification is not perfect and provider support is still catching up, but the direction is settled. Teams that adopt the format now spend less time wrangling billing data and more time acting on it, which is the entire reason FinOps exists.

FAQs

What is FOCUS in FinOps?

FOCUS, the FinOps Open Cost and Usage Specification, is an open standard that defines one common schema for cloud cost and usage data. It lets billing data from AWS, Azure, Google Cloud and other vendors be read and compared using the same column names and meanings.

Who created and maintains FOCUS?

FOCUS is a community project maintained by the FinOps Foundation, which operates under the Linux Foundation. Practitioners from major cloud providers, software vendors and enterprises contribute, and a Steering Committee ratifies each version of the specification.

What is the latest FOCUS version?

FOCUS 1.3 is the current release, ratified on December 4, 2025. It adds a dedicated Contract Commitment dataset, columns for splitting shared costs and flags that report data recency and completeness.

What is the difference between BilledCost and EffectiveCost?

BilledCost is the amount on your invoice. EffectiveCost is the real cost after negotiated and commitment discounts, with prepaid commitments amortized over time. For most cost analysis and trend reporting, EffectiveCost is the figure to use.

Do I still need the AWS CUR if I use FOCUS?

Often yes. FOCUS standardizes cost data across providers, while AWS CUR 2.0 carries deeper AWS-only detail such as Split Cost Allocation Data for ECS and EKS that FOCUS 1.0 does not yet include. Many teams export both.

Which cloud providers support FOCUS?

AWS, Microsoft Azure, Google Cloud and Oracle Cloud all provide FOCUS exports, though native support and version coverage differ. AWS and Azure offer production-ready exports, while Google Cloud uses a BigQuery view and Looker template.

Is FOCUS only useful for multi-cloud enterprises?

No. FOCUS helps any team, including those on a single provider or a single account. It standardizes cost data, simplifies onboarding and makes skills portable, so even one-cloud teams gain cleaner, analysis-ready billing data.