How to Apply FinOps to SaaS and PaaS With FOCUS 1.2

You apply FinOps to SaaS and PaaS by normalizing every vendor's billing data into the FOCUS 1.2 schema and then running the same FinOps loop you already run for cloud: inform, optimize, operate and govern. FOCUS, the FinOps Open Cost and Usage Specification, is the open standard that gives cloud billing data a common format; version 1.2, released in mid-2025, extended it to SaaS and PaaS so subscriptions and usage-based platforms can sit in the same table as your EC2 and BigQuery lines. That single change is what makes SaaS and PaaS spend governable rather than scattered.

This guide is part of our complete guide to SaaS and data platform cost optimization, the cluster pillar it links up to. It pairs with how to build a SaaS spend management process, which covers the operational side of owning and reviewing the spend this data feeds. For the authoritative spec, see the FOCUS specification and the FinOps Foundation's FOCUS 1.2 announcement.

What is FOCUS 1.2 and what did it add for SaaS and PaaS?

FOCUS 1.2 is the version of the FinOps Open Cost and Usage Specification that extends the standard to SaaS and PaaS billing data. Ratified by the FOCUS Steering Committee in May 2025 and announced at the FinOps X conference, it folds "Cloud Plus" reporting into the same schema as core cloud spend. The headline additions are columns for SaaS and PaaS vendor billing, an invoice ID column that links each cost row to a provider invoice, and four columns for reporting credits and tokens so you can track the burndown of virtual currencies that some SaaS vendors bill in. It also sharpens allocation with finer billing-account and sub-account granularity.

How do you apply FinOps to SaaS and PaaS, step by step?

Apply FinOps to SaaS and PaaS by normalizing billing data into FOCUS 1.2 and then running the standard FinOps loop on it. The sequence below is the one we use when extending a client's practice from cloud-only to the full stack.

1. Inventory every SaaS and PaaS vendorPull every vendor from accounts payable, the corporate card feed and SSO logs, and record for each whether it offers a billing or usage export. Expect the list to be longer than anyone predicted. The result is a complete vendor register.
2. Collect each vendor's billing exportGather the billing or usage data from each vendor, and flag which already publish FOCUS-conformed exports versus which need manual mapping. Major clouds and a growing set of platforms, including Databricks, Alibaba Cloud and Grafana, now publish FOCUS data. The result is raw data for every line of spend.
3. Map each vendor's fields to the FOCUS 1.2 schemaTranslate each vendor's columns into the FOCUS 1.2 fields, using the new SaaS and PaaS, invoice ID and virtual-currency columns where they apply. For non-conformed vendors, build a mapping once and reuse it each month. The result is one normalized table across all vendors.
4. Reconcile each row to its invoiceUse the FOCUS 1.2 invoice ID column to tie every normalized cost row back to the provider invoice, so finance can close the month against a source they trust. The result is billing data finance and engineering both believe.
5. Allocate and report on one dashboardLoad the normalized data into a single dashboard, allocate each cost to a team or product, and report SaaS, PaaS and cloud spend together. The result is one view of total technology spend, covered further in how to track and allocate SaaS costs by team.
6. Govern with budgets and anomaly alertsPut budgets and anomaly alerts on the normalized data so SaaS and PaaS get the same guardrails as cloud, catching a runaway usage-based platform the same week it spikes. The result is spend that holds instead of drifting back up.

Why normalize SaaS and PaaS onto FOCUS at all?

You normalize onto FOCUS because you cannot allocate, benchmark or govern spend that lives in a dozen incompatible formats. Before FOCUS, each vendor portal had its own columns, its own definitions of cost and usage, and its own export quirks, so building a single picture of technology spend meant a brittle pile of spreadsheets. A common schema turns that into one queryable table, which is the precondition for everything else: showback to teams, anomaly detection across vendors, and a defensible total-cost number for the CFO. This is the same visibility-first principle that underpins the entire SaaS and data platform cost pillar.

What does this not solve on its own?

FOCUS 1.2 gives you clean, unified data; it does not cut the bill by itself. Normalization is the See step, and the savings come from what you do next: rightsizing usage-based platforms, consolidating duplicate tools, and renegotiating renewals on the clean baseline the data reveals. The data also depends on vendor adoption, so for tools that do not yet publish FOCUS exports you carry a mapping burden until they do. Treat FOCUS as the foundation that makes the optimization work possible and trustworthy, not as the optimization itself.

The short version

Apply FinOps to SaaS and PaaS by treating them like cloud: normalize every vendor's billing into the FOCUS 1.2 schema, reconcile it to invoices, allocate it to owners, and govern it with budgets. FOCUS 1.2 is what makes this practical, because it extended the open billing standard to SaaS and PaaS, added invoice reconciliation, and added credit and token tracking. Get the data unified first, then run the cuts. For the operating system around it, read how to build a SaaS spend management process and return to the SaaS and data platform cost pillar.