FOCUS 1.2 Is What Finance Teams Have Been Waiting For

The FinOps Foundation’s release of the FOCUS 1.2 specification is a very promising and necessary evolution for the discipline. It is a known truth in FinOps, or any industry as a matter of fact, that technological innovation, and the spending that fuels it, can go wildly out of hand without the right controls. I believe this update represents a major step toward creating those controls, not through restriction, but through clarity. FOCUS 1.2 is architected to provide a common format to unify billing data from these differing scopes of technology spend. It is creating a common language for cost.

Practitioners have struggled to translate the unique billing reports of dozens of different vendors into a coherent financial narrative. This fragmentation creates data silos and immense friction, making a complete view of technology spend nearly impossible. FOCUS 1.2 directly confronts this chaos. By folding SaaS and PaaS billing data into the same structure as core cloud spend, it gives teams a single, unified vocabulary.

The FOCUS specification has evolved significantly since its inception, deliberately expanding its scope to match the growing responsibilities of FinOps practitioners. Initially developed with critical adoption from major cloud providers like AWS, Microsoft, and Google Cloud, the standard was architected to normalize cost and usage data from core cloud infrastructure. However, the industry has shifted into what the FinOps Foundation calls a "Cloud+" era, where practitioners are now applying FinOps principles to a wider range of technology costs, including SaaS tools, licenses, and AI spend. This created a pressing need for the FOCUS standard to evolve beyond its original boundaries to provide a common format for these diverse scopes of technology spend.

With version 1.2, FOCUS makes a pivotal leap to address this need by formally incorporating support for SaaS and PaaS billing data. This is not merely a minor addition but a fundamental expansion designed to unify these disparate billing models into a single, cohesive schema. The release introduces new columns specifically designed to handle the virtual currencies, such as credits or tokens, that many SaaS vendors use for billing. By enabling practitioners to track the consumption of Snowflake Credits or Databricks DBUs alongside their cloud spend, FOCUS 1.2 provides the unified view necessary for this expanded "Cloud+" world, paving the way for it to become the primary format for cost and usage data across the industry.

Another particularly impactful aspect of this new specification is its focus on unit economics and multi currency normalization. The ability to calculate cost per unit, whether that unit is a gigabyte stored, a user served, or a proprietary token consumed, provides essential context to raw usage reports. By introducing columns that capture both the original pricing currency (like SaaS credits) and the final billing currency (like USD or EUR), FOCUS 1.2 creates a direct translation mechanism. This translation is a tremendous benefit for the finance persona; it demystifies consumption, provides a clearer basis for preparing budgets and forecasts, and aligns technology spend with what the finance team actually pays.

This enhancement represents a positive and inclusive shift, deliberately extending the value of FinOps data beyond engineering teams and directly into the workflows of the finance department. When finance can clearly understand burn down rates on virtual currencies or see how a charge on a report ties directly to a specific invoice ID, the practice of FinOps becomes more deeply embedded across the organization. It fosters a shared understanding and a common language around value, ensuring teams can collaborate more effectively on spending and act accordingly.

In a significant step forward, this update builds a vital bridge between technology and finance departments. The new InvoiceId column directly links every charge in a usage report to the final paid invoice, solving a critical challenge during month-end close. This dramatically simplifies financial reconciliation and builds essential trust across teams.