On this page · 9 sections
Every cloud invoice describes the same thing, what you used and what it cost, in a different vocabulary. AWS has line items and usage types, Azure has meters and charge types, Google Cloud has SKUs and services, and each SaaS vendor has its own export. Anyone running a multi-cloud estate has spent hours building a mapping layer to compare them. FOCUS exists to replace that layer.
FOCUS, the FinOps Open Cost and Usage Specification, is an open standard from the FinOps Foundation that defines common columns and semantics for billing data. You can read the current version at focus.finops.org.
A Short History
According to the published release history, the specification has moved quickly:
- 1.0 (November 2023): the first production-ready schema.
- 1.1 (November 2024): deeper provider billing detail and metadata about the data itself.
- 1.2 (May 2025): combined SaaS, PaaS and cloud billing, with handling for virtual currencies such as credits and tokens.
- 1.3 (December 2025): a Contract Commitment dataset and columns for splitting shared costs.
New revisions continue to ship, so check the specification site for the latest version, and expect your providers to export different versions at any one time.
The Four Cost Columns Every FinOps Team Should Know
FOCUS defines several cost measures. The four below do most of the work, and mixing them up is the most common source of reports that do not reconcile.
| Column | What it represents | Use it for |
|---|---|---|
ListCost | Cost at public list price | Measuring discount depth |
ContractedCost | Cost at your negotiated rates | Comparing contract terms |
BilledCost | The amount invoiced for the charge | Reconciling to the invoice |
EffectiveCost | Billed cost with commitment fees amortized across usage | Allocation and unit economics |
A simple rule: reconcile with BilledCost, analyze with EffectiveCost. Commitments make the difference. An upfront Reserved Instance payment shows as a large billed charge in one month, while the effective cost spreads it across the workloads that benefit, which is what you want when charging teams back. Our commitment guide explains why that distinction matters.
A worked example (illustrative numbers)
Suppose you pay $12,000 upfront for a one-year reservation in January. Your January invoice shows a $12,000 charge, so BilledCost for that line is $12,000 in January and zero for the other eleven months. EffectiveCost spreads it as $1,000 a month across the resources that consumed the reservation. A report built on billed cost shows January as a spike and a team that benefited all year looks cheap for eleven months. A report built on effective cost shows steady, fair numbers. This is the single most common reason finance and engineering totals disagree.
Other Column Families Worth Learning
- Service and resource:
ServiceName,ServiceCategory,ResourceId,RegionId. A sharedServiceCategorylets you compare compute, storage and AI spend across providers without a custom taxonomy. - Charges:
ChargeCategoryandChargeClassseparate usage, purchases, taxes and credits, and flag corrections. - Commitments:
CommitmentDiscountId,CommitmentDiscountTypeand status columns make commitment utilization reporting consistent across clouds. - Billing:
BillingAccountId,BillingPeriodStart,ProviderNameandBillingCurrency.
Who Publishes FOCUS Data
AWS, Microsoft Azure, Google Cloud and Oracle Cloud publish FOCUS-format billing data, as do a growing number of SaaS and data vendors. Coverage and versions differ by provider, and they change, so verify the current state in each provider's documentation before you design around it.
Why It Matters More Now: AI and SaaS Spend
The case for FOCUS got stronger once AI arrived. Tokens, API calls and credits do not fit a traditional compute-and-storage bill, and the State of FinOps 2026 report shows 98% of teams now manage AI spend. A common schema that treats these as billing data, with the same cost columns and allocation fields as a virtual machine, is what lets you ask for total cost per feature instead of three separate reports. Our guide to FinOps for AI goes deeper on the AI side.
A Practical Adoption Checklist
- Pick one provider first. Enable its native FOCUS export and run it in parallel with your current report for a full billing period.
- Reconcile before you migrate. Compare
BilledCosttotals to invoices, andEffectiveCostto your current amortized numbers, and document every difference. - Plan for mixed versions. Normalize on a single internal version and handle columns that exist in one provider's export but not another's.
- Move allocation rules onto FOCUS columns. Tag-based allocation, shared-cost splits and chargeback logic should read the standard fields.
- Add the rest gradually. Bring in the second cloud, then SaaS and AI vendors, one at a time.
Where FOCUS Does Not Help
A standard schema makes data comparable, not good. FOCUS will not fix missing tags, wrong allocations or an absent ownership model, and it does not tell you what to optimize. Treat it as plumbing for the practices in our FinOps guide and the allocation playbook, not a replacement for them.
How Varcio Uses FOCUS
Varcio normalizes multi-cloud cost data into one model and its AI cost tracking uses FOCUS-compatible fields so token and model spend can sit beside the rest of your bill. See how it works on the platform overview, or talk to our FinOps team about a FOCUS adoption plan.
Frequently asked questions
What is FOCUS in FinOps?
FOCUS, the FinOps Open Cost and Usage Specification, is an open standard from the FinOps Foundation that defines a common set of columns, definitions and formats for billing data, so cost data from different cloud and SaaS providers can be analyzed together without custom mapping for each vendor.
What is the difference between BilledCost and EffectiveCost?
BilledCost is what appears on the invoice for the charge. EffectiveCost spreads upfront and recurring commitment fees (such as Savings Plans or Reserved Instances) across the resources that used them, so it reflects the true cost of usage. Use BilledCost to reconcile to invoices and EffectiveCost to analyze and allocate.
Which cloud providers support FOCUS?
AWS, Microsoft Azure, Google Cloud and Oracle Cloud all publish FOCUS-format billing data, and a growing list of SaaS and data vendors do too. The version supported differs by provider and changes over time, so check each provider's documentation for the version it currently exports.
Do I need to rebuild my cost reporting to adopt FOCUS?
No. Most teams adopt it incrementally: enable the native FOCUS export from one provider, validate it against the existing report and invoice, then move dashboards and allocation rules onto the common columns one provider at a time.
