FOCUS billing data implementation: an acceptance checklist
Updated: 2 November 2026
Get a quote for my projectFOCUS gives cloud, SaaS and AI bills a common column set, but an implementation still has to choose a release, map provider differences and prove that the totals match the invoice. This page covers those three decisions.

On this page
Which FOCUS release you are actually asking for
The FOCUS site lists version 1.4 as current, ratified on 4 June 2026, after 1.3 on 5 December 2025, 1.2 on 29 May 2025 and 1.1 on 7 November 2024. The specification now defines more than the original cost table: a Contract Commitment dataset arrived in 1.3, and 1.4 added Invoice Detail and Billing Period datasets next to Cost and Usage.
Provider exports lag the specification. As of October 2026, focus.finops.org lists AWS, Microsoft Azure and Google Cloud at version 1.2 and Oracle at 1.0, with several SaaS and data platform vendors at 1.3. In AWS Data Exports the tables are named «FOCUS 1.2 with AWS columns» and «FOCUS 1.0 with AWS columns», with three additional AWS columns: x_Discounts, x_Operation and x_ServiceCode, and a choice of hourly, daily or monthly granularity. Microsoft's schema page for the FOCUS cost and usage details file lists version 1.0, a 1.0r2 date-format update and a 1.2-preview column set. Write the target release and the provider release into your requirements, separately.
Columns that decide whether the data reconciles
- BilledCost: the charge serving as the basis for invoicing, after reduced rates and discounts and excluding amortization of upfront charges.
- EffectiveCost: the amortized cost after discounts and the applicable portion of prepaid purchases. This is the column for allocating commitment spend to teams.
- ListCost and ContractedCost: list unit price times quantity, and contracted unit price times quantity. The gap between them is what your negotiated terms are worth on a given charge.
- ChargeCategory: Usage, Purchase, Tax, Credit or Adjustment. Keep Purchase and Tax rows out of consumption dashboards unless you mean to include them.
- ChargeClass: marks a row that corrects a charge invoiced in an earlier billing period.
- Tags: the key and value pairs you applied, as one JSON object. FOCUS does not fix missing tags.
- Columns starting with x_: provider-specific extensions. Decide how each will be used, because dashboards that depend on them are no longer provider-neutral.
Acceptance tests to run before calling it done
- For each billing account and billing period, sum BilledCost and compare it with the invoice total. Explain every difference.
- Sum EffectiveCost and compare it with the provider's own amortized view for the same scope.
- List row counts and totals by ChargeCategory and check that purchases, credits and taxes land where finance expects.
- Find rows with ChargeClass set to a correction, and confirm that late adjustments reach the month they belong to in your reports.
- Measure the share of cost rows with empty Tags, by account, and compare it with your tagging target.
- Check BillingCurrency against PricingCurrency and verify the conversion on a sample.
- Confirm that commitment-related columns, such as CommitmentDiscountId, identify the purchases you hold.
Keep the queries. They become the regression test the day a provider moves to a new release. Tag coverage, which the fifth test measures, is covered in the guide on cost allocation and tagging.

Want your FOCUS data checked against your invoices? Request my quote.
Decisions the project forces
- Version policy: who approves a move from one release to the next, and how old dashboards are migrated or frozen.
- History: ask each provider whether data from before the export was created can be produced in FOCUS form. Do not assume it.
- Mapping: a written table from each legacy report field to its FOCUS column, reviewed by finance.
- Ownership: who runs the ingestion job, who is paged when a file is late, and where the data lives.
FinOps Foundation also runs a FOCUS analyst certification, which is one way to check a provider's staff know the specification.
Official sources used
Documents behind the statements above, as read in October 2026.
- focus.finops.org/what-is-focus/: FOCUS releases, dates and datasets
- focus.finops.org/: provider support by FOCUS version
- focus.finops.org/focus-specification/v1-4/: FOCUS 1.4 specification
- focus.finops.org/docs/specification/v1-3/columns/cost-and-usage/charge-category: ChargeCategory allowed values
- docs.aws.amazon.com/cur/latest/userguide/table-dictionary-focus-1-2-aws.html: AWS FOCUS 1.2 table with AWS columns
- docs.aws.amazon.com/cur/latest/userguide/what-is-data-exports.html: AWS Data Exports table types
- learn.microsoft.com/en-us/azure/cost-management-billing/dataset-schema/cost-usage-details-focus: Azure FOCUS cost and usage details schema
Frequently asked questions
Does FOCUS replace invoice reconciliation?
No. FOCUS standardizes the columns, but you still compare totals with the invoice for each billing account and period. The Invoice Detail dataset introduced in 1.4 adds invoice-level detail to the specification, and provider support for it should be confirmed.
Can we assume every cloud supports the latest release?
No. Provider exports trail the specification, and each provider may add its own x_ columns. State the release you need and the release each provider delivers, and plan a mapping for the difference.
Turn the tests into procurement requirements with the cloud RFP billing-export checklist (French). Separate the export version actually delivered from the transformations needed for the target reporting model.
Continue your review
- FinOps consulting: cloud cost review and implementation scope
- Request a scoped FinOps quote
- How your request is handled: from enquiry to proposal
- Cloud cost allocation: tagging and ownership controls
- FinOps showback vs chargeback: choose a financial model
- FinOps KPIs: prove realized savings and business value
Request a quote for my project
Describe your project in a few lines and receive a quote from a specialist.
Request my quote