- A SaaS spend audit is a structured review of every software subscription you pay for: what it costs, who owns it, and whether anyone actually uses it.
- Start by pulling spend from every source (card, AP, and ERP), then match each charge to a contract and to real usage.
- The waste is usually bigger than teams expect. A typical 250-person company loses about $180K a year to unused and forgotten software.
- A one-time audit finds the waste once. Continuous visibility is what keeps it from coming back.
A SaaS spend audit is a structured review of every software subscription your company pays for: what each tool costs, who owns it, and whether anyone still uses it. Done well, it turns a pile of decentralized contracts and card charges into one clear list of what to keep, cut, or renegotiate.
Most teams are surprised by what the first audit surfaces. Duplicate tools, licenses nobody logs into, and renewals that quietly auto-charged last quarter. This guide walks the exact checklist, step by step, so you can find the waste and stop it from creeping back.
What is a SaaS spend audit?
A SaaS spend audit is the process of finding every piece of software your company buys, confirming what each one costs, and checking whether it is actually used. The goal is a single, current view of your software spend that you can act on.
It is more than a finance categorization exercise. A spreadsheet of expenses tells you what you spent. An audit ties each dollar to a contract and to real usage, so you can see not just the cost but whether the cost is justified. That link between spend, contract, and usage is where the savings hide.
Why run a SaaS spend audit?
You run a SaaS spend audit because software is the easiest budget line to overspend and the hardest to see. Tools get bought on personal cards, renewals auto-charge, and licenses sit unused long after the person who needed them has left.
Source: License Logic’s interviews with 80 mid-market executives.
When spend is that decentralized, shadow IT and shelfware grow quietly, and the first time anyone notices a renewal is when it has already charged.
The SaaS spend audit checklist
Work through these seven steps in order. Each one builds on the last, so by the end you have a ranked list of exactly what to cut, renegotiate, or keep.
Pull spend from every source
Start by gathering every place software gets paid for. That means corporate cards, AP and invoices, and your ERP or accounting system. Software rarely lives in one budget line, so if you audit only one source you will miss the tools bought on someone else’s card.
Match each charge to a contract
Next, tie every recurring charge back to the contract behind it. Pull the agreements out of inboxes and shared drives and line them up against the spend. Any charge with no contract is a flag, and any contract with no matching charge is worth a second look too.
Measure real usage against licenses
For each tool, compare what you pay for against what people actually use. Sign-in data from your identity provider shows who logs in, and how often. This is where shelfware shows up: seats you bought, still pay for, and nobody touches.
Flag every renewal in the next 90 days
List every contract that renews in the next quarter, with its owner and its notice deadline. This is the window where you have leverage. Manual tracking catches only about 60% of renewals, so the ones you miss renew on the vendor’s terms instead of yours.
Hunt down shadow IT and duplicates
Look for tools that were never approved and for overlapping tools that do the same job. Two teams paying for two different project trackers is common, and so is a free trial that quietly converted to a paid plan. These are usually the fastest cuts.
Quantify the waste and rank it
Add up the unused seats, the duplicates, and the tools no longer in use, and put a dollar figure on each. Then rank them. A short list ordered by annual savings turns a messy audit into a clear action plan your finance and IT leads can agree on.
Assign an owner to every tool
Finally, give every remaining tool a named owner responsible for its renewal and its usage. Most waste comes back because no single person is accountable for a subscription. An owner on every line is what keeps the next audit small.
How often should you run a SaaS spend audit?
Run a full SaaS spend audit at least once a year, and a lighter review each quarter. Software changes faster than an annual budget cycle, so a yearly-only audit is often out of date by the time you finish it. Quarterly check-ins catch new shadow IT and upcoming renewals while you can still act on them.
Signs your SaaS spend audit is overdue
A few signals mean you are already flying blind and should audit now:
- You cannot name every software tool the company pays for.
- You have been blindsided by an auto-renewal in the last year.
- Contracts live in inboxes and personal drives, not one place.
- No single person owns software spend across the company.
- You suspect you are paying for seats nobody uses, but cannot prove it.
An audit is a snapshot, and the waste creeps back the moment it is done: a new tool gets bought, a renewal slips, someone leaves with an active license. License Logic keeps your contracts, spend, and usage side by side in one place, so the audit is always up to date instead of a once-a-year scramble. Track real license usage against what you pay, keep every agreement in one contract repository, and get a renewal alert before the notice deadline instead of after the charge.
If you want the background first, our guides on reducing SaaS costs and SaaS spend optimization are a good next read.
Frequently asked questions
What is included in a SaaS spend audit?
A SaaS spend audit includes every software subscription the company pays for, the contract behind each one, its real usage, and its upcoming renewal date. It pulls spend from cards, AP, and your ERP, then ties each charge to a contract and to who actually uses the tool.
How do I find SaaS spend that is not on a contract?
Compare your card and AP charges against your list of known contracts. Any recurring charge with no matching agreement is likely shadow IT: a tool bought outside procurement. Sign-in data from your identity provider helps confirm it by showing who is actually using the app.
How much does the average company waste on SaaS?
A typical 250-person company loses about $180K a year to unused and forgotten software. In License Logic’s interviews with 80 mid-market executives, half reported wasting 20% or more on licenses nobody uses. The exact figure varies, but almost every audit finds more waste than expected.
How long does a SaaS spend audit take?
A first manual audit often takes a few weeks, because the data is scattered across cards, invoices, and inboxes. Most of that time is gathering and matching, not analysis. When contracts, spend, and usage are already in one place, the same audit becomes a review that takes hours instead of weeks.
What is the difference between a SaaS spend audit and SaaS spend management?
A SaaS spend audit is a point-in-time review that finds waste once. SaaS spend management is the ongoing practice of keeping that waste from returning. The audit is the snapshot, and spend management is the habit that keeps the picture current between audits.
Can I automate a SaaS spend audit?
Much of it, yes. Connecting your spend sources, contracts, and identity provider lets a platform match charges to contracts and to usage automatically, so you are reviewing a current list instead of building one by hand. The judgment calls, like whether to cut or renegotiate a tool, still belong to your team.