FOCUS needs procurement: bringing all technology spend into FinOps

Abstract

Key findings

• 90%

  of FinOps teams manage SaaS spend or plan to in the next 12 months, up from 65% a year earlier.^[1]

• 98%

  manage AI spend or plan to, up from 63% in 2025. AI is now the most common area beyond the public cloud.^[1]

• 64%

  cover software licensing, and 48% the data center: spend that arrives as supplier invoices, not as a cloud export.^[1]

• 1.4

  The FOCUS version ratified on June 4, 2026. It adds an Invoice Detail dataset that carries payment terms, due date and the purchase order number.^[2]

1. Introduction

For most of its short history, FinOps has been a discipline of the cloud console. Engineers, finance and product teams learned to read the hourly line items of AWS, Azure, Google Cloud and OCI, to put them on the teams that spent them, and to buy commitments where usage was steady. The data was abundant, machine-readable and arrived every day.

That scope has widened quickly. The State of FinOps 2026, a survey of 1,192 practitioners representing more than $83 billion in annual cloud spend, finds FinOps teams taking on SaaS, licensing, private cloud, the data center and, above all, AI^[1]. Its authors also find FinOps leaders increasingly taking part in provider negotiations and multi-year investment decisions.

The new scope comes with a different kind of data. A SaaS vendor, a consultancy or an AI provider billed through a reseller rarely sends a daily cost and usage file. It sends an invoice, against a contract someone negotiated and, in a well-run company, a purchase order someone approved. Those records live in procurement and accounts payable. This paper looks at what that means for FOCUS, and for how companies should think about procurement.

2. FOCUS in brief

The FinOps Open Cost and Usage Specification, FOCUS, defines one set of columns and rules for cost and usage data, so that a bill from any provider can be read the same way^[4]. A row says who issued the charge (InvoiceIssuerName), what it cost (BilledCost, EffectiveCost), for which period (ChargePeriodStart, ChargePeriodEnd), at what price (ListUnitPrice, ContractedUnitPrice), and how it is allocated (Tags).

The specification has moved quickly toward the problems procurement deals with every day:

• FOCUS 1.2 is the version with the widest support today, among both providers and FinOps tools^[3].
• FOCUS 1.3, released in December 2025, added a Contract Commitment dataset that keeps the terms of a commitment apart from the cost rows it applies to^[3].
• FOCUS 1.4, ratified on June 4, 2026, grew that dataset from 13 to 30 columns and added two more: Billing Period, and Invoice Detail, which carries "payment currency, payment terms, due date, and purchase order number" so that FinOps and Accounts Payable can tie usage to the bill^[2].

In other words, the specification now has a place for the contract, the invoice and the purchase order. What it still needs is someone to fill those places for the vendors that are not clouds.

3. The spend outside the cloud bill

The large clouds publish FOCUS files today. Most of the vendors behind the new scope do not. The FinOps Foundation is direct about it: among its recommendations for 1.4, it asks practitioners to "request FOCUS adoption from SaaS, PaaS, and on-premises vendors that have not yet shipped FOCUS exports"^[2]. Practitioners agree on where the gaps are: their top requests for FOCUS to expand into are AI, the data center, and broader PaaS and SaaS support^[1].

Asking vendors is worth doing, and we come back to it below. But a company with hundreds of suppliers cannot wait for each of them to build an export. In the meantime, every one of those suppliers already sends something structured: an invoice. And before the invoice, most of them were bought through a contract and a purchase order.

That is the gap this paper is about. The cloud bill reaches the FinOps tool on its own. The rest of the spend reaches it only if someone turns invoices, purchase orders and contracts into the same columns. The team that already holds those records, checked and approved, is procurement.

4. Procurement as a source of FOCUS data

When we map the FOCUS columns that matter for non-cloud spend against what a procurement system holds, the overlap is close to complete. Table 1 shows the main ones.

Table 1. FOCUS columns for non-cloud spend, and the procurement record that holds each value.

Three properties make procurement data especially good FOCUS data:

• It is allocated before it is spent. A purchase order names its cost center and GL code when it is raised. Cloud FinOps spends much of its effort tagging after the fact; procurement data arrives tagged.
• It is checked. An invoice that has been matched to its purchase order and contract, and approved, is the amount the company actually owes. A FinOps report built on it agrees with what finance pays.
• It carries the contract. Commitments, rates and renewal dates are negotiated by procurement. FOCUS 1.3 and 1.4 finally give them a standard home, and procurement is the natural author. The FinOps Foundation itself lists procurement first among the teams that benefit from the Contract Commitment dataset^[2].

5. Why procurement matters to the business

Procurement is often seen as the step between wanting something and getting it. The shift described above suggests a larger role. FinOps sees spend after it happens. Procurement shapes it before: it chooses the supplier, sets the rate, sizes the commitment and approves the order. When the two work from the same data, a company can close the loop.

• Commitments get used. A commitment that procurement negotiated and FinOps can see in FOCUS can be tracked against usage. A commitment that lives in a PDF is discovered at renewal.
• Budgets count everything. When SaaS, AI and services sit beside cloud in the same columns, a cost center's budget reflects all its spend, not only the part with an API.
• Negotiations start from evidence. FinOps leaders increasingly join provider negotiations^[1]. They bring usage; procurement brings the contract history. Together they know what to commit to.
• Overbilling is caught before it is paid. An invoice checked against its contract rate at approval never needs a credit later. Reporting it in FOCUS shows the saving where FinOps already looks.

6. Recommendations

For companies extending FinOps beyond the cloud, we recommend six steps:

1. Put every recurring supplier on a contract and a purchase order. The PO is where allocation, rate and approval are recorded once, before the first invoice.
2. Record contract terms as data. Rates, commitments, seats and renewal dates in fields, not only in the signed PDF, so they can be checked and exported.
3. Agree one cost center model. FinOps tags and procurement cost centers should name the same things, so the two sources join.
4. Export procurement data in FOCUS, and avoid counting it twice. If your FinOps tool already reads your cloud providers' own FOCUS files, leave the cloud invoices out of the procurement export.
5. Ask for FOCUS at renewal. Renewal is when procurement has the most leverage. Make a FOCUS export part of the request, as the FinOps Foundation recommends^[2].
6. Review together, every month. One meeting, one dataset: FinOps, procurement and finance looking at the same rows.

7. How Pleaxy fits

Pleaxy is procurement and accounts payable software, so we have an interest here, and we want to say plainly what we do. Pleaxy checks every supplier invoice against its contract rates, its purchase order and, for cloud and AI providers, its usage, before it is approved. Those checked invoices, debit notes and credit notes are what we write to FOCUS:

• FOCUS 1.2 or 1.4 Cost and Usage rows, in CSV or Parquet, delivered to your own storage bucket for your FinOps tool to read.
• One row per line, tax entry and adjustment, so each document's rows add up to its total, tagged with the purchase order, cost center, GL code and contract.
• With 1.4, your contracts' commitments as the Contract Commitment dataset.
• An option to leave out cloud and AI providers, for FinOps tools that already read those providers' own FOCUS files.

FOCUS export is switched on for each workspace on request. If you would like it for yours, talk to us.

8. Method and limitations

This paper is a synthesis of public sources, not a new survey. The figures come from the State of FinOps 2026 and from the FinOps Foundation's announcements of FOCUS 1.3 and 1.4. Two limits are worth stating:

• The State of FinOps figures in Figure 1 combine teams that manage an area today with those that plan to in the next 12 months. The survey had 1,192 respondents; each question was answered by fewer (N=632 for this one).
• The survey does not report what share of non-cloud spend reaches FinOps tools today, so the size of the gap described in Section 3 is not measured here.

The author works for Pleaxy, which sells the procurement software described in Section 7.

References

1. [1]FinOps Foundation. State of FinOps 2026. 2026. data.finops.org/
2. [2]FinOps Foundation. Introducing FOCUS 1.4: Invoice Reconciliation, Commitment Details, and Specification Maturity. 2026-06-10. www.finops.org/insights/introducing-focus-1-4/
3. [3]The Linux Foundation. FinOps Foundation Launches FOCUS 1.3 to Deepen Cloud and SaaS Billing Transparency. 2025-12-11. www.linuxfoundation.org/press/finops-foundation-launches-focus-1.3-to-deepen-cloud-and-saas-billing-transparency-announces-expanded-vendor-support-for-focus-1-2
4. [4]FinOps Open Cost and Usage Specification. FOCUS specification and changelog. 2026. github.com/FinOps-Open-Cost-and-Usage-Spec/FOCUS_Spec
5. All sources accessed November 2, 2026.