FOCUS 1.4 Made Token Spend Official. That's Not the Same as Making It Legible.

FOCUS 1.4 made token spend official. That's not the same as making it legible.

On June 4, the FinOps Foundation ratified FOCUS 1.4. Two new datasets, 47 new columns, and the first version of the spec to treat token-based spend as a first-class billing object. A week later at FinOps X in San Diego, the Linux Foundation announced the Tokenomics Foundation to govern this work going forward. JPMorganChase, IBM, Booking.com, Salesforce, and Oracle signed on as founding supporters.

The press covered the foundation launch. The spec itself is the part that changes how you buy software.

What FOCUS 1.4 actually added

FOCUS - the FinOps Open Cost and Usage Specification - is a schema that lets organizations normalize billing data across cloud providers. Before it, every provider sent cost data in a different format. Finance teams built custom pipelines to reconcile AWS, Azure, and GCP into something a CFO could sign off on.

FOCUS 1.4 extends this to tokens. The new columns cover token type (input, output, cached), model identifier and version, provider, unit price per token, and estimated cost per call.

This is the first time LLM spend has a defined place in the FinOps spec. Once something is in the spec, it becomes a procurement requirement. Organizations that have standardized on FOCUS for their cloud bills will expect the same from AI spend vendors. Vendors that can't produce compliant output will lose RFPs to vendors that can.

The gap the spec doesn't close

FOCUS 1.4 tells you which columns to populate. It doesn't tell you how to populate them in a way your CFO can work with.

A token event happens at the API layer. The model receives a prompt, returns a completion, and the provider logs the tokens consumed. What that log doesn't tell you is which customer triggered the call, which agent or workflow was responsible, or how the cost maps to a revenue line in your P&L.

FOCUS compliance means you can produce structured data with the right column names. FOCUS-useful output means that data is attributed at the business unit level and can be reconciled against your customer invoices at month close. Most of what's being sold as "AI cost visibility" today stops at the first one. You can see aggregate token spend broken down by model. You still can't answer the CFO's question: which customers are costing us money, and is gross margin per customer holding as we scale AI usage?

Why the founding supporters matter

JPMorganChase and IBM didn't sign on to the Tokenomics Foundation to normalize token usage for engineering dashboards. They want margin analytics, audit trails, and a clear view of what each product line is spending on AI per customer per billing period.

When organizations of that size drive a spec, they drive procurement requirements. Within 12 to 18 months, a FOCUS 1.4 gap in a vendor evaluation will be disqualifying, not a roadmap question. The enterprise buyers writing the checks are the same ones who just committed to the standard.

What a control plane does that a dashboard doesn't

Most tools in this space were built for engineers. They track tokens, report spend, and surface anomalies after the fact. That's useful, but it stops well short of what a finance team needs at close.

A control plane sits in the request path. It enforces budget rules before the API call is made, attributes cost to a customer or agent at call time rather than reconciliation time, and produces output a finance team can close the books with - not a CSV that someone has to clean up in a spreadsheet.

FOCUS 1.4 compliance is table stakes for any serious vendor in this space. The question worth asking is what happens above it: who handles the attribution hierarchy, the override approvals, the immutable audit log, and the month-close reconciliation a CFO can sign off on.

Three questions for your next vendor evaluation

1. Can you produce FOCUS 1.4 compliant output, column by column, for every LLM call?
2. Can you attribute that spend to a specific customer, agent, or cost center at call time, before the invoice arrives?
3. Can your output feed directly into our month-close process, or does finance need to reconcile it manually?

If the answer to any of those is "we're working on it," you have an observability tool. That distinction matters when your AI bill is a line item your CFO has to explain to the board.