SaaS Spend Management: How Finance Gets Control of Software Subscriptions

SaaS spend management is the finance practice of finding every software subscription a company pays for, paying each one from a controlled instrument, and cutting what isn't used before it renews. It covers the money side of software, while license management covers the seats.

Most controllers meet a new subscription the same way. It's a line on a card statement, coded to "software" or sometimes "office supplies," for a tool nobody in finance approved, and it has already renewed for another year. The employee who signed up may have left the company. The price may have gone up at renewal, and nobody noticed because the charge landed on a corporate card that reconciles itself every month without anyone reading the line.

Discovery tools help with that problem, and plenty of companies buy one. The faster lever usually sits with finance, though, in a question most software guides skip entirely, which is what instrument pays each subscription and who can change it.

Key Takeaways

• SaaS spend management is finance's view of software (what's paid, by which instrument, and when), and it complements IT's license view rather than replacing it.

• Software spending is growing faster than total IT budgets, and price increases at renewal compound the growth on any subscription nobody reviews.

• Hidden subscriptions surface in four payment records, namely card feeds, expense reports, the AP vendor master, and bank debits.

• Giving each recurring software vendor its own virtual card turns every renewal into a checkpoint that finance controls.

• Renewal reviews work best when they start 90 days out, with usage data in hand before the vendor's notice window closes.

What is SaaS spend management?

SaaS spend management is the process of tracking, paying for, and rightsizing the cloud software a company subscribes to, from the first sign-up through every renewal. It sits inside the broader discipline of spend management, with rules shaped by the way software is bought.

In practice the work breaks into four jobs:

• Finding every subscription, along with its owner and its current cost.

• Deciding which instrument pays each vendor and who's allowed to change it.

• Catching contract end dates and cancellation notice windows before they lapse.

• Matching seat counts and pricing tiers to what people actually use.

The scale explains why finance teams are paying closer attention. Worldwide software spending is forecast at $1,468 billion in 2026, up 15.5%, according to Gartner's July 2026 IT spending forecast. Three months earlier, Gartner's April 2026 forecast had put 2026 software spending at about $1.44 trillion, up 15.1%. When the forecaster revises its number upward inside a single quarter, a software budget built on last year's run rate is probably already short.

How is it different from SaaS license management?

SaaS license management is IT's view of software, tracking who holds a seat, at which tier, and whether they log in. SaaS spend management is finance's view of the same tools, tracking what's being paid, by which card or account, on what schedule, and against which budget line.

You need both. License data can tell you a design tool has dozens of inactive seats. Only payment data tells you those seats renew on the 14th, on a card held by someone in marketing, at a price higher than last year's. Most SaaS management platforms grew up on the license side. Their dashboards are strong on usage and much thinner on how the money moves, from card to vendor to ledger.

Why does software spend get away from finance?

Software spend escapes finance because buying it takes a card number and a few minutes, and nothing in that purchase path routes through procurement. The average organization runs 831 applications, according to Torii's 2026 SaaS Benchmark Annual Report, which is vendor research from a SaaS management company. Torii found that over 61% of those apps are shadow IT, discovered through usage, browser activity, or direct sign-up rather than through a purchase request.

Price is the second leak, stacked on top of volume. SaaS inflation reached 16.4% in June 2026, a new high above the 14.7% recorded in November 2025, according to the Vertice SaaS Inflation Index, also vendor research. An unreviewed subscription renews at whatever the vendor's new list price happens to be. On a card with no limit, the higher charge clears.

Both problems trace back to the purchase path rather than to anyone's discipline, and the purchase path is what maverick spend controls were built to address. Corpay pays software vendors by virtual card, ACH, or check from one approval flow, which puts that path back under finance.

Where do the leaks show up?

Each leak surfaces in a different record, which is why a single control never catches all of them. Unused seats are the biggest single category. Organizations leave an average of 36% of SaaS licenses unused, according to Zylo's 2026 SaaS Management Index, a vendor dataset covering more than 40 million licenses and $75 billion in spend.

Leak-to-control mapping reflects common card-program practice, not a single source.

How do you find every subscription you're paying for?

You find subscriptions by pulling four payment records into one list and sorting it by vendor, because every subscription has to be paid by something. Discovery tools read logins and browser activity. Finance can read the money, and no subscription avoids being paid.

The same logic applies to every small, scattered purchase category, and tail spend management runs on the identical principle of starting from payments rather than contracts. If your card program has no merchant restrictions yet, setting them up is the quickest first move, and locking down spend before it slips covers how to do that without slowing employees down.

Which records reveal hidden subscriptions?

Four records reveal nearly all of them:

1. Corporate card feeds. Sort by merchant and flag charges that repeat monthly or annually at a similar amount. Software vendors often bill through a payment processor, so the merchant name can differ from the product name.

2. Expense reports. Software reimbursed on personal cards is the hardest category to see, since it's coded once, approved, and forgotten. Search descriptions for "subscription," "license," "pro," and "annual."

3. The AP vendor master. Larger SaaS contracts usually arrive by invoice, so they sit here with payment terms and a purchase order, if you're lucky.

4. Bank debits. A few vendors pull payment directly from the operating account, and those lines are easy to misread as bank fees or transfers.

Once the list exists, check it against a benchmark. The same Zylo index puts median SaaS spend at $9,455 per employee. If your total lands far below that, the list is more likely missing reimbursements or debits than proving the company is unusually lean.

Best practices for a virtual card program

Learn the internal strategies that make a virtual card program succeed — from program design to driving the vendor acceptance that determines how much of your AP spend earns rebates.

Download the guide

Who should own the inventory, IT or finance?

Both should own it, with a split that matters. IT should own the license record, meaning who has access and whether it's secure. Finance should own the payment instrument for every subscription, because whoever controls the card controls the renewal.

I'd resist handing the whole inventory to IT, even when IT already runs a SaaS management platform. IT can revoke a login, but it can't stop a renewal charge from clearing on a card it doesn't administer, and the vendor will keep billing a cancelled user's seat until someone changes the contract. The cleanest arrangement I've seen gives IT the access decisions and finance the card limits, with the renewal calendar shared between them.

Should every SaaS subscription get its own virtual card?

Most recurring subscriptions should, yes. The exceptions are annual contracts the vendor invoices for payment by ACH, and the handful of vendors whose billing portals make card updates painful enough to cost more time than the control saves.

A virtual card issued to a single vendor changes three things at once:

• Each vendor gets its own spend limit, so a price increase above that limit declines instead of clearing.

• Cancelling becomes a matter of closing the card, which stops the charge even when nobody can find the admin login.

• Coding gets simpler, because the card maps to one vendor, one GL account, and one cost center.

The limits are real, too. Replacing a card means someone has to log into the vendor's billing portal and update the card on file, and that login often belongs to the employee who signed up two years ago. Annual contracts billed by invoice usually belong on ACH, where the payment runs through AP approval. One-time annual payments suit single-use virtual cards, while monthly subscriptions need a multi-use card locked to the vendor. For employees who need a new tool this afternoon, instant virtual cards issued on request keep the purchase fast and still put it on a card finance can see.

When a company first moves subscriptions onto per-vendor cards, the first round of declines is the most useful report the program will produce. Every failed charge is either a tool nobody claims or a price nobody approved, and the owner has to come forward to get the charge reinstated. Corpay's single-use virtual cards cover one-off software purchases the same way, with each card number limited to one approved charge.

How do card controls stop auto-renewals and price increases?

Card controls stop them by making the renewal charge fail unless someone has decided to let it through. Three settings do most of the work:

• A spend limit set at the current contract price, plus a small buffer for taxes, so any increase above that buffer declines.

• An expiry date set a few weeks before the renewal date, so renewing requires a new card and therefore a decision.

• A merchant lock that restricts the card to one vendor, so it can't drift into other uses.

Given the inflation figures above, the spend limit does most of the protective work on its own. A declined charge forces the conversation that a cleared charge would have skipped. The broader rules behind these settings, including how limits differ by role and department, are covered in card controls and spend policies and in corporate card spend controls by department.

Tracking alone doesn't seem to be enough. In Flexera's 2025 State of ITAM Report, vendor research from a software asset management company, 35% of respondents said SaaS waste increased over the past year, even though 59% actively track usage and 56% rightsize contracts and subscriptions (n=506), according to Flexera's announcement of the survey. As far as I can tell, the gap is that tracking produces a report while a declined charge produces a decision.

How do finance teams cut unused software at renewal?

Finance teams cut unused software by starting the review early enough to act on usage data before the vendor's notice window closes, which usually means 90 days ahead of renewal. The payment owner belongs in that review, since they're the one who can change the card.

What does a renewal review look like 90 days out?

A renewal review is a short sequence with fixed dates, run from a shared renewal calendar:

1. At 90 days, pull usage for every seat, the current price, and the contract's notice terms. Most SaaS contracts require written notice well before renewal, so this is the last comfortable point to start.

2. At 60 days, the business owner decides whether to renew as is, reduce seats, move to a cheaper tier, consolidate with another tool, or cancel. Send cancellation or rightsizing notice in writing.

3. At 30 days, update the card limit and expiry date to match the new contract, or close the card if the tool is being cancelled.

4. On the renewal date, reconcile the charge against the approved amount, and investigate any difference the same week.

The step people skip is the fourth one. A renewal that clears at a higher amount than approved usually means the vendor applied a price increase the contract allowed, and catching it in week one is much easier than arguing about it in month eleven.

How do you measure whether the program is working?

Measure the program by how much software spend sits on controlled instruments and how many renewals get reviewed before the notice deadline. A short scorecard covers it:

• Total software spend per employee, tracked quarterly.

• The share of software spend paid by per-vendor cards or approved AP invoices, as opposed to reimbursements and general cards.

• The number of subscriptions with no named owner.

• Renewals reviewed before their notice date, as a percentage of all renewals in the quarter.

A cautionary number belongs here, even though it measures cloud infrastructure rather than SaaS. Wasted cloud spend rose to 29% in Flexera's 2026 State of the Cloud Report, the first increase in five years (n=750+). If waste can climb in a category that has had dedicated cost tooling for years, nobody should expect a SaaS scorecard to improve every quarter.

The open question I don't have a clean answer to is AI software. Subscriptions to AI models and AI-powered tools are being added faster than most quarterly review cycles can absorb, often by individual employees on personal cards, and the usage data that would justify a renewal decision is thin because the tools are so new. The per-vendor card approach still works for them. Deciding which ones deserve a renewal is harder, and I suspect most finance teams will be making that call on judgment for another year or two.

Pay every software vendor from one controlled program with Corpay

The hardest part of SaaS spend management is the moment a renewal clears on a card nobody is watching. Corpay closes that gap at the payment layer. Corpay virtual cards give each software vendor its own controlled card with limits and expiry dates you set per vendor. Single-use virtual cards handle one-time annual payments. Corpay commercial cards with card controls put employee software purchases into the same feed, so finance sees every subscription in one place.

Not every software vendor bills to a card. For invoice-billed contracts, Corpay's fully managed AP pays vendors by virtual card, ACH, or check. Each payment posts to the ledger with its coding through 100+ ERP integrations, including NetSuite, Sage Intacct, Business Central, and Acumatica. Corpay customers earn $800M+ in rebates per year on card spend, and most programs are live in weeks. Corpay expense management brings reimbursed software purchases into the same view.

Corpay works alongside a SaaS management platform rather than replacing one. The platform tells you which seats are idle, and Corpay controls the card that pays for them. If you're comparing options, the guide to the best spend management platforms covers the criteria, and our newsroom piece on IT expense management focused on SaaS and AI costs gives the CIO's side of the same problem.

Frequently Asked Questions

What does SaaS spend management include?

SaaS spend management includes finding every software subscription, deciding which payment instrument pays each vendor, tracking renewal dates and notice windows, and rightsizing seats and tiers to actual use. It's finance's view of software, built from card, expense, AP, and bank records.

What is the difference between SaaS management and SaaS spend management?

SaaS management usually means managing licenses, access, and security for cloud applications, which is typically IT's job. SaaS spend management focuses on the money, meaning what each subscription costs, which card or account pays it, and when it renews. Mature programs run both together.

How do you track software subscriptions paid on employee cards?

Pull every corporate card feed and expense report into one list, sort by merchant, and flag charges that repeat monthly or annually at similar amounts. Then move each recurring subscription onto its own vendor-locked virtual card so future charges appear in one feed.

Are virtual cards good for recurring subscriptions?

Yes, for most of them. A vendor-locked virtual card with a spend limit set at the contract price declines unapproved price increases, and closing the card stops a cancelled subscription from billing again. Annual contracts paid by invoice usually fit ACH better.

How much software spend is typically wasted?

A large share. Zylo's 2026 index found that more than a third of SaaS licenses go unused on average, and Flexera's research shows waste rising even at companies that track usage. Reviewing seats 90 days before each renewal is the most direct fix.

David Luther

Product Marketing Program Manager

David Luther, MBA is a product marketing program manager with years of experience in commercial banking, finance, and technology sectors, with research and writing appearing in financial publications.

Virtual Card

Expense management