What is FOCUS? The open billing format, and any vendor in one place
The CostReveal team, , 4 minute read
Every vendor bills in its own shape. One names a project, another a workspace, a third an organization; one bills by request, another by token, another by seat. Putting them side by side has meant a spreadsheet and a person who knows each vendor's quirks. FOCUS is the industry's answer: one open format that any vendor's bill can be written in. This guide covers what FOCUS is, the columns that matter, and how to use it to bring a vendor CostReveal has no connector for into the same place as the rest of your spend.
What FOCUS is
FOCUS, the FinOps Open Cost and Usage Specification, is an open format for billing data, maintained by the FinOps Foundation. It names a common set of columns, such as what was billed, in which currency, for which period, to which account and for which service, and defines what each one means, so a row from any vendor reads the same way.
Cloud providers already export it. CostReveal reads Azure's cost exports and Oracle Cloud's cost reports in FOCUS. For a vendor with no export of its own, FOCUS is a format you can write yourself, from an invoice, an admin panel or a usage API.
The columns that matter
A FOCUS file has one row per charge. CostReveal needs six columns:
| Column | What it holds |
|---|---|
BilledCost | What the vendor billed for the row, as a plain decimal such as 12.40. |
BillingCurrency | The currency of BilledCost, such as USD or EUR. |
BillingPeriodStart | The first day of the billing period, such as 2026-10-01. |
ChargePeriodStart | The day the charge began. |
ChargeCategory | Usage, Purchase, Tax, Credit or Adjustment. |
BillingAccountId | The vendor's account, organization or workspace the row is billed to. |
Others make the spend easier to explain: ServiceName for what was bought, SkuMeter and ConsumedQuantity for what was measured and how much, InvoiceId for the invoice a row is on, and Tags, a JSON object such as {"team":"search"}, for who it belongs to. Dates are in UTC, and amounts carry no currency symbol and no thousands separator.
Bringing a vendor in
In CostReveal, a vendor with no connector is a custom source:
- Under Connections, open Custom source, choose Add a custom source, and name the vendor as its bill names it.
- Download the template, which has the columns already named, and fill it from the vendor's figures.
- Send the file, by choosing it under Send a FOCUS file, or from your own systems.
Each file is kept exactly as sent. Under Files sent, each one says which billing periods it stated, how many lines it added and restated, and which rows it left out and why.
To send files on a schedule, create a key with the scope Send data only, which can send data and read nothing, and post each file to the custom source's address:
curl -X POST "<the address shown in Connections>?name=2026-10.csv" \
-H "Authorization: Bearer <your key>" \
-H "Content-Type: text/csv" \
--data-binary @2026-10.csv
Corrections without surprises
Vendors restate. A credit arrives late, a usage figure is revised, a month is closed a week after it ends. FOCUS files make that safe, because each billing period a file has rows for becomes exactly what the file says:
- A row not recorded before is added.
- A row whose amount changed is restated, pointing at what it corrects.
- A row the file no longer has is restated to zero, once.
Periods the file has no rows for stay as they are. So send a billing period whole, and send it again in full to correct it. Sending the same file twice changes nothing, so a retried job is safe. Nothing is ever edited or deleted: every change is a new line, and what was sent before is kept.
Explained like any other spend
Once in, a custom source's spend is explained, budgeted, allocated and reported like any other:
- Service is the file's
ServiceName, with the DIRECT basis. - Team, feature and customer come from the
Tagscolumn, read with your project's tag keys, and from allocation rules that match the custom source, its services or its accounts. - Spend that nothing names is shown as unknown, never spread across teams.
A FOCUS file has no column for a model, so a custom source's spend is not shown by model. Every amount is recorded exactly as the file states it, and attribution must add up to it on every dimension.
Frequently asked questions
Do I need a vendor's cooperation to use FOCUS? No. You can write a FOCUS file yourself from the vendor's invoice, admin panel or usage figures.
Can I send Parquet as well as CSV? Yes, both are read.
How do I correct a month? Send its billing period again, in full. Rows that changed are restated and rows that are gone are restated to zero.
Is a retried upload counted twice? No. Sending the same file again changes nothing.
Can a custom source be split by team? Yes, by the Tags column, or by allocation rules that match it.
Keep reading
- Tracking Mistral costs in CostReveal: a custom source from Mistral's figures.
- Tracking Cohere costs in CostReveal: the same for Cohere.
- Allocation rules for shared costs: splitting what no tag names.