The FOCUS billing standard explained.

What problem does FOCUS actually solve?

Every cloud bills in its own dialect. AWS describes a charge one way in the Cost and Usage Report, Azure another way in its cost exports, GCP another in its billing export, and OCI another in its usage reports. The fields have different names, the cost concepts differ, and the same idea, what you were charged after discounts, lands in a different column with a different meaning on each platform. For a single cloud estate this is an annoyance. For a multicloud estate it is a tax on every cross provider question.

Before FOCUS, answering a question like which service costs us most across all four clouds meant building and maintaining a custom mapping, one that broke every time a provider changed its export. FOCUS replaces that bespoke work with a published standard. The providers map their native data to the common schema, and you consume one shape.

The core columns, and why they matter

FOCUS defines a set of common columns that carry the cost concepts buyers actually reason about. A few matter more than the rest.

• BilledCost is what appears on the invoice for the period, the amount you are billed before amortizing commitments.
• EffectiveCost spreads the cost of commitments and upfront payments across the period they cover, so a workload covered by a Savings Plan or Reservation shows its true amortized cost rather than a spiky purchase.
• ChargeCategory separates usage, purchases, taxes, and credits, so you can tell consumption apart from a commitment purchase or a refund.
• ServiceName and ServiceCategory describe what was bought in consistent terms, so compute in one cloud lines up with compute in another.

The split between BilledCost and EffectiveCost is the one that changes decisions. A team reading raw billed cost sees a commitment purchase as a one time spike and an idle covered instance as nearly free. EffectiveCost shows the real ongoing cost of running that workload, which is what rightsizing and allocation should be based on.

How do the four clouds map to FOCUS?

Each provider offers its billing data in or alongside the FOCUS format, mapped from its native export. The native sources remain the system of record; FOCUS is the normalized layer you build reporting on.

The practical point is consistency. Once each cloud's data lands in the common schema, a commitment in AWS Savings Plans, an Azure Reservation, a GCP CUD, and an OCI Universal Credit all show their amortized effect in the same EffectiveCost column, so you can compare coverage across providers without reconciling four definitions by hand.

Why normalized data is the FinOps foundation

Almost every FinOps activity depends on trustworthy, comparable data. Allocation and chargeback need a consistent cost figure to divide. Commitment coverage decisions need amortized cost across providers to judge where coverage is thin. Board reporting needs one number that means the same thing everywhere. When the data is in four dialects, each of these becomes a reconciliation argument before it becomes a decision.

This is why the State of FinOps 2026 treats data standardization as foundational rather than optional. With FOCUS, the conversation in a cost review shifts from whose extract is correct to which workload to act on. That shift is the entire value: less time defending numbers, more time changing them.

What FOCUS does not do

FOCUS is a data standard, not a savings engine. It will not rightsize an instance, buy a commitment, or eliminate waste. It also does not replace the native exports as the system of record; those remain the immutable source you retain for audit. And adopting it does not automatically make your reporting correct, because allocation logic, tagging discipline, and forecasting still have to be built on top.

Treat FOCUS as the clean foundation that makes everything above it easier and more defensible. The cost reductions still come from the operating model, the commitment strategy, and the architecture decisions, the same levers as always, now working off data you do not have to argue about.

How a buyer should adopt FOCUS

Start by normalizing every provider's billing data into FOCUS at the point of ingestion, keeping the native exports as the retained source of truth underneath. Rebuild reporting, allocation, and commitment coverage analysis on the normalized layer so they are provider neutral. Then document the mapping from each native format to the FOCUS columns, so the normalization stays auditable and a surprising number can be traced back to either the source or the translation.

Done in that order, FOCUS becomes the layer that every other FinOps capability sits on, and the one that lets a multicloud estate be reasoned about as a single thing rather than four.

Build on data you can trust

We normalize your AWS, Azure, GCP, and OCI billing into FOCUS and rebuild allocation, commitment, and reporting on top, so your cost reviews start at the decision instead of the reconciliation. Independent, buyer side, zero provider commissions. Our guarantee: we reduce your cloud spend or we reimburse our service fee. Pricing is either a Fixed Fee scoped up front or Gainshare, a share of verified savings with no retainer and no risk.