Who owns SaaS spend: FinOps, software asset management or procurement?
In brief
SaaS is moving into FinOps, but ITAM and procurement already hold contracts and entitlements. Who should own what, where FOCUS stands, and a working split.
Steve Elliott · · 7 min read
On this page
No single team should own SaaS spend end to end. In our view the split should follow the object: procurement owns the contract, software asset management owns entitlements and compliance, FinOps owns cost and usage data, allocation and forecasting, and a named business owner decides whether to keep paying.
In our reading, that is close to the FinOps Foundation's own guidance, with one departure on who keeps the inventory, even as its State of FinOps 2026 survey shows SaaS moving into FinOps teams' remit. We think the risk is not that FinOps takes SaaS on. It is that three teams build three SaaS inventories and arrive at a renewal with three different seat counts.
What does State of FinOps 2026 show about SaaS?
The FinOps Foundation's sixth annual survey, released on February 19, 2026, drew 1,192 respondents whose companies represent more than $83 billion in annual cloud spend. Two findings matter here:
- SaaS. 90% of respondents to the technology-areas question (n=632) now cover SaaS or plan to in the coming year, up from 65% in 2025.
- Licensing. 64% cover software licensing, up from 49%.
The SaaS figure combines teams that cover it today with teams that plan to, so it shows direction more than a finished handover. The report also captures the mood. One practitioner it quotes describes the shift as: "Now it's fix the contract and license mess."
The same report says FinOps teams collaborate most often with ITFM, followed by ITAM/SAM, which it ties to asset compliance and governance. It adds that larger companies tend to run separate FinOps and ITAM teams that collaborate, while smaller companies tend to combine them in one team.
Does the FinOps Foundation say FinOps should take over SaaS?
No. Its guidance is explicit that FinOps joins the work rather than absorbing it. Presenting the FinOps Framework 2026 in March, the Foundation wrote: "This is not about FinOps absorbing or redefining other disciplines." Its Intersecting Disciplines capability says the point is to prepare FinOps teams to work with disciplines already in place, not to encourage organizations to adopt them. It does allow that in some organizations the FinOps team may perform software asset management functions.
The detailed pages hand out roles:
- The SaaS FinOps technology category page has the FinOps practitioner build a central SaaS inventory together with ITAM, procurement, product and security. Procurement negotiates terms and runs renewal timelines. Finance defines chargeback models and validates invoices. Leadership establishes ownership and accountability for SaaS costs.
- The Licensing & SaaS capability gives the ITAM allied persona the license position of cloud resources, summaries of unallocated entitlements and renewals.
- The Introduction to FinOps for SaaS paper, last updated March 16, 2026, recommends "close collaboration with Procurement, ITAM/SAM and Finance teams" so a FinOps inventory matches existing systems of record rather than duplicating them.
Read together, the pages leave one seam open. Renewals sit with procurement on one page and with ITAM on another. We don't read that as a mistake: the Foundation is describing collaboration, not writing a RACI. But it means each organization has to decide who holds the renewal pen.
What does software asset management already own?
ITAM has its own international standard. ISO/IEC 19770-1:2017, the third edition, amended in 2024, sets requirements for an IT asset management system and was last reviewed and confirmed in 2024. Its annex lists 15 ITAM process areas, and it is built to integrate with standards such as ISO/IEC 27001 and ISO/IEC 20000-1. The Foundation's Intersecting Disciplines capability describes ITAM and SAM teams as handling contractual value and risk over the lifecycle of software and hardware assets.
That risk is the reason SAM cannot be reduced to a cost function. The Licensing & SaaS capability notes that license and SaaS contracts often run multi-year or perpetual, allow true-ups but not true-downs, and carry audit and penalty exposure. It frames the goal as avoiding both over-deployment, a compliance risk, and under-deployment, which is shelfware. A FinOps team that cuts seats without knowing the license position can create the first problem while solving the second. In our view, compliance and the effective license position (what you own against what you have deployed) should stay with SAM wherever a SAM team exists.
Who should hold contracts, entitlements, usage and renewals?
This table is our view of a working split, built from the roles the FinOps Foundation describes. One row, discovery, departs from the Foundation's SaaS page; we explain why below. It assumes separate teams. Where one team does both FinOps and SAM, the columns merge but the decisions don't.
| Object | Owns it | Contributes | Typical record |
|---|---|---|---|
| Contract and commercial terms | Procurement | Legal, SAM | Contract repository |
| Entitlements, license position, compliance | SAM | Procurement, engineering | SAM repository |
| Discovery of unapproved SaaS | SAM | FinOps (spend data), security (access logs) | SAM repository or SaaS management software |
| Usage and consumption data | FinOps | SAM, identity team | Vendor usage reports, identity logs |
| Cost data, allocation, forecast | FinOps | Finance | FinOps cost data, FOCUS where available |
| Invoice validation | Finance | FinOps | Accounts payable |
| Renewal decision (keep, cut, exit) | Business or product owner | Procurement (terms), SAM (position), FinOps (cost and usage) | Decision log |
Two rows carry the argument. First, discovery. The Foundation's SaaS page has FinOps build the inventory with ITAM. Where a SAM team already keeps a license repository, we would keep the record there: FinOps finds unapproved SaaS in card and expense spend, but one record beats two. Second, in our view the renewal decision belongs to the person whose budget pays for it, and the three specialist teams prepare the facts. That is consistent with the Intersecting Disciplines capability, which at Walk maturity expects "renewal, exit, and consumption accountability" to be assigned at signature, alongside procurement and finance. Giving the decision to the budget owner is our addition.
Where does FOCUS stand for SaaS?
The FOCUS specification now covers SaaS in its schema, but not every SaaS fact a renewal needs.
- FOCUS 1.2, ratified May 29, 2025, put SaaS and PaaS billing in the same schema as cloud. It added pricing-currency columns for credits, tokens and other virtual currencies, and an InvoiceId column linking each charge to its invoice.
- FOCUS 1.3, released December 11, 2025, added a Contract Commitment dataset that separates contract terms, such as dates and remaining units, from cost rows.
- FOCUS 1.4, ratified June 4, 2026, added Invoice Detail and Billing Period datasets and grew the Contract Commitment dataset from 13 to 30 columns. The Foundation's announcement asks practitioners to request FOCUS adoption from SaaS, PaaS and on-premises vendors that have not yet shipped FOCUS exports.
In our reading, adoption among SaaS vendors is still early. As of November 2026, the FOCUS adoption page lists SaaS and PaaS vendors as a category of data generator but names none, and the 1.4 announcement's request above points the same way. The providers the Linux Foundation named as supporting FOCUS in December 2025 are mostly clouds, plus Databricks and Grafana. The State of FinOps 2026 report says requests to expand FOCUS center on AI, data center and broader PaaS and SaaS support.
The scope matters for ownership. The 1.4 Contract Commitment dataset describes the terms of contracts between a provider and a customer: commitment quantity, unit, cost, payment model and period dates. It has no columns for assigned seats, notice periods, auto-renewal or use rights. So as of November 2026, FOCUS can bring SaaS cost and commitment burn into FinOps data, while the entitlement and contract terms SAM and procurement work from still live in their own systems. We think that is the right boundary for a billing standard, and a reason the split above will hold even as FOCUS coverage grows.
How does the split play out at renewal?
Take an illustrative example; the numbers are made up. A collaboration product costs $1.2 million a year: 5,000 seats at $240 each on a three-year contract, with renewal in 150 days and a 60-day notice period.
- SAM reports the position. 4,600 seats are assigned, a license utilization rate of 92%. No compliance gap.
- FinOps reports use and cost. 3,800 of the 4,600 assigned seats were active in the last 90 days, about 83%. Cost is allocated to four business units.
- Procurement reports the terms. The contract allows no reduction mid-term. Seat count can change only at renewal, and notice must go in 60 days before it.
- The product owner decides. Renew at 4,000 seats, leaving headroom above the 3,800 active. If the vendor accepts it, that saves 1,000 seats at $240, or $240,000 a year.
- SAM reclaims the inactive seats before the renewal date so the position stays compliant at the lower count.
License utilization rate is one of the KPIs the Foundation lists on its SaaS technology category page, and the Licensing & SaaS capability lists ITAM/SAM systems among its data sources. Each team brings one fact, and nobody re-counts seats in a spreadsheet the week before notice is due. For when to bill allocated costs back to business units, see showback to chargeback.
In our view, the place to start is a shared renewal calendar, with an owner named for every contract above a threshold. Contract renewals are where SaaS money is committed for years at a time, so they are where the division of labor earns its keep. An operating model that ties each contract to its owner, its funding line and the value it is meant to deliver is what makes that calendar more than a list.
Sources
- FinOps Foundation, State of FinOps 2026, February 2026
- Linux Foundation, State of FinOps survey: AI, value and skills top priorities as FinOps matures across technology value, February 19, 2026
- FinOps Foundation, FinOps Framework 2026: Executive Strategy, Technology Categories, and Converging Disciplines, March 19, 2026
- FinOps Foundation, FinOps for SaaS technology category
- FinOps Foundation, Licensing & SaaS capability
- FinOps Foundation, Intersecting Disciplines capability
- FinOps Foundation, Introduction to FinOps for SaaS, last updated March 16, 2026
- FinOps Foundation, FOCUS 1.2 is available, June 3, 2025
- Linux Foundation, FinOps Foundation launches FOCUS 1.3, December 11, 2025
- FinOps Foundation, Introducing FOCUS 1.4, June 10, 2026
- FOCUS, Specification v1.4: Contract Commitment dataset
- FOCUS, FOCUS adoption: who uses FOCUS?, accessed November 2026
- ISO, ISO/IEC 19770-1:2017 IT asset management systems: requirements
- ISO/IEC JTC 1/SC 7, ISO/IEC 19770-1:2017 flagship standard page
Frequently asked questions
Should FinOps own SaaS spend?
In our view, FinOps should own SaaS cost and usage data, allocation and forecasting, not the contract or the license position. The FinOps Foundation says its framework is not about absorbing other disciplines, and its guidance pairs FinOps with ITAM, procurement and finance. The decision to renew or cut a subscription should sit with the business owner who pays for it.
What is the difference between FinOps and software asset management for SaaS?
Software asset management tracks entitlements, license position and compliance across the life of software assets, under standards such as ISO/IEC 19770-1. FinOps brings cost and usage data, allocation, forecasting and accountability for spend. For SaaS, SAM answers whether you are entitled and compliant. FinOps answers what it costs, who uses it and who should pay.
Does FOCUS support SaaS billing data?
Yes, in the schema. FOCUS 1.2 added SaaS and PaaS billing, virtual currencies such as credits, and invoice IDs, and FOCUS 1.3 and 1.4 added contract commitment and invoice datasets. As of November 2026 vendor adoption is still early, and the FinOps Foundation asks practitioners to request FOCUS adoption from SaaS vendors. Seat assignments and notice periods sit outside the specification.
Should FinOps and ITAM be one team?
It depends on size. State of FinOps 2026 found larger companies tend to keep separate FinOps and ITAM teams that collaborate, while smaller companies tend to combine them. Either works if the decisions are split clearly. We think the test is whether both teams report the same seat count and the same SaaS cost at every renewal.
Steve Elliott
Published November 22, 2026
More on FinOps & Cloud
FOCUS, commitments, shared cost.
Keep reading
Forecasting cloud spend when usage won't sit still
Split committed, usage-driven and AI cloud spend, tie usage to business drivers, forecast in ranges and measure variance by line, with a worked example.
What the FinOps Framework 2026 changes for practitioners
A close reading of the FinOps Framework 2026: the new Executive Strategy Alignment capability, rewritten Scopes guidance, technology categories and renames.
The IT finance org chart: who owns what in a TBM model
A role-by-role map of IT finance and TBM: TBM office, IT finance, FP&A, FinOps, procurement and service owners, their reporting lines and model layers.
Should FinOps report to the CTO, CIO or CFO?
Most FinOps teams report to the CTO or CIO; 8% report to the CFO. When each line fits, what it costs, and how to make a dotted line to finance work.