Skip to content

Blog

Software license audit for small businesses

A software license audit in a day: match what you pay for against who has accounts and who works for you, then cancel, trim or downgrade the rest.

· 9 min read

A software license audit, for a small business, is checking three lists against each other: what you pay for (from your bills), who has an account in each tool (from each tool's member page), and who actually works for you (from your directory). Any paid seat or subscription that doesn't match a current person and a current need gets cancelled, downgraded or reassigned. For a company of 5 to 50 people it takes about a day.

This is your own internal audit, sometimes called a SaaS audit. It isn't the same as a vendor's license compliance audit, where a software company checks that you haven't used more licenses than you bought. The same worksheet helps with both, though: if you know exactly who has what, a vendor's audit letter is a short reply. This post is part of our guide to SaaS management for small businesses.

Why audit

Three reasons, in the order most small companies feel them.

Money. Seats for leavers, tools nobody opened since spring, upgrades bought for a feature nobody uses. SaaS spend breaks down where it goes.

Access. Former employees and contractors still in tools that hold customer data. An audit is the moment you find them, and often the first time anyone has looked.

Evidence. If a customer's security questionnaire or an auditor asks how you review access, a dated, completed worksheet is the answer. What counts as enough evidence is your auditor's call, not ours.

Planning the day

Pick a day when the person running it can concentrate, and split it in three. The morning goes on bills, because they give you the most complete list. Midday goes on member lists, which is the slow, mechanical part. The afternoon goes on decisions, which need the tool owners, so book thirty minutes with each of them in advance.

The person running it needs admin or billing access to each paid tool, or someone who has it on call. If nobody at the company can open a tool's billing page, write that down: it is a finding in its own right.

Collecting the bills

Start with money, because everything you pay for leaves a trace.

Go back twelve months in card and bank statements. Twelve, not three, so annual renewals appear. Every recurring charge is a row. Then read expense reports, because tools paid on personal cards and claimed back hide there. Then search your email for "invoice", "receipt", "renewal" and "your subscription". Finally, open each known tool's billing page, because invoices sent to someone who has left never reached your inbox.

For each row, record the tool, vendor, plan, monthly or annual billing, renewal date, cost per month, and seats paid. Get seats paid from the tool's billing page, not the invoice total; you need the count.

Then add the free tools. They don't show on statements, but they hold company data and accounts. The post on SaaS sprawl lists where to find them, and the one on shadow IT covers the Google Workspace connected-apps list in detail.

Matching seats to people

Now open each paid tool's members page and match it against your directory, one tool at a time. Your directory is the source of truth: if you're on Google Workspace, that's the active user list in the Admin console.

Every account gets one of four marks. Matched and active is a current person who uses the tool. Matched, inactive is a current person who hasn't used it in 60 to 90 days, where the tool shows last activity. Leaver is an email belonging to someone no longer in the directory, or suspended there. Unknown is an email that matches nobody, such as a personal address, an old alias or a contractor nobody remembers.

Your worksheet ends up looking something like this. The prices are list prices from the vendors' pages as we read them on 27 October 2026 (Google Workspace, Notion, JumpCloud); the counts are an illustration:

ToolBillingRenewsPer seat a monthSeats paidMatched, activeInactiveLeaversUnknownDecision
Google Workspace Business StandardAnnual2027-04-01$142219030Delete or archive
Notion PlusAnnual2027-02-15$102013421Remove 3, ask 4
JumpCloud SSOAnnual2027-06-30$112219030Remove leavers

In that illustration, the leavers alone hold eight seats across three tools: three Google seats at $14, two Notion seats at $10 and three JumpCloud seats at $11. That is $95 a month, or $1,140 a year, before anyone has decided about the unknown Notion account or the four inactive users. Archiving the Google accounts instead of deleting them keeps part of that cost, because archived users need their own license.

Two things to check while you're in each tool. First, who the admins are: an ex-employee with admin rights is a bigger problem than one with a seat. Second, whether removing someone actually stops the billing. In some tools a suspended or deactivated user is still a paid seat; SaaS license management lists the rules for Google Workspace, JumpCloud and Slack.

What to cancel or downgrade

With every row filled in, make a decision per tool. There are only five:

DecisionWhen
KeepSeats match people, the plan matches what you use
TrimLeavers, unknowns or inactive people hold paid seats
DowngradeYou're on a plan for a feature nobody uses; or seats could be viewers
ConsolidateAnother tool on the list does the same job
CancelNobody uses it, or nobody can say why you have it

A few rules save trouble. Settle unknown accounts first. Find out who they are before anything else; some are contractors who still need access, and some shouldn't be there at all. Ask before removing the inactive, because ninety days without a login might be someone who uses the tool once a quarter. Transfer before you remove: files, projects, integrations and API tokens owned by a leaver break when their account goes.

Mind the renewal date. Cancelling or reducing seats just before an annual renewal saves a year; just after, it may save nothing until the next one. And export data before cancelling a tool, then remove every account in it, so nobody keeps using a tool you think is gone.

Upgrades bought for single sign-on deserve a separate look. If the reason was offboarding, the audit you just did shows whether SSO solved it. The SSO tax explains what those upgrades cost.

When a vendor audits you

A vendor's license compliance audit runs the other way: the vendor asks you to prove you haven't used more than you bought. It matters most for software licensed by count and installed on your own machines, where the vendor can't see usage directly; with per-seat SaaS, the vendor already sees every account. Your contract with the vendor sets what they can ask for and when, so read it before you reply.

Your own audit is the best preparation. If the worksheet shows who has each license and when it was last reviewed, a vendor's request becomes a matter of sending the relevant rows. If you find you're over, the honest move is to true up or remove the extra users before the vendor finds them.

What tools help

At 5 to 50 people, a spreadsheet is enough for the bills and the decisions. The slow part is the middle: opening every tool's members page, copying the list, and matching emails by hand. That's where tooling earns its keep. SaaS management platforms automate discovery and spend tracking, and are mostly built and priced for larger companies. Access tools that read each tool's member list for you cut the matching from hours to minutes. Neither replaces the decisions, which still need the tool owners.

Common mistakes

Auditing only the tools on the card. Free tools hold data and accounts too, and tools on personal cards only appear in expense reports.

Trusting the directory for contractors. Many contractors were never in Google Workspace. Keep a separate list with end dates, or every contractor shows as "unknown" and nobody knows which ones to keep.

Stopping at the worksheet. The audit saves nothing until the seats are actually removed and the next bill shows the lower count.

Not recording what changed. If someone later asks what the review found, "we cleaned some things up" is not evidence.

Turning the audit into evidence

The same worksheet can double as a record that you review access, which is what customers' security questionnaires usually ask about. It needs three additions. Each tool's row should name the person who confirmed the list, usually the tool's owner. Each decision should have a date it was carried out, not just a date it was made. And the file should be kept, not overwritten next quarter, so you can show a history.

Formal sign-off on who should have access is called access certification, and it asks for more detail than a cost audit does: every person, every role, confirmed by someone accountable. If you're heading toward an audit, read that before your next quarter's run, so one pass produces both.

Doing it every quarter

The first audit takes a day. The second takes a couple of hours, because the worksheet exists and the mess is gone. Keep it short and regular. Each quarter, add new charges from the last three months' statements, re-run the member-list match for every paid tool, review renewals due in the next 90 days, and record the date, who ran it, and what changed.

Between audits, offboarding does most of the work: every leaver removed from every tool the week they go. The employee offboarding checklist covers that, and a user access review covers the "should they still have this?" questions for current staff.

Where SmashSSO fits

SmashSSO speeds up the middle of the audit, matching seats to people, and leaves the bills to you. It does no spend tracking and has no CSV export, so it won't collect invoices, total your spend or hand you a spreadsheet.

For each tool you've added, it shows who has an account and with what role, matched by email against your Google Workspace directory, with accounts that match nobody flagged. People suspended in Google Workspace show every tool they're still in. From there you remove or change people across tools, through a tool's API where you've added a token or an agent in your own Chrome otherwise, and every change is recorded in an audit log, which helps when someone asks what the review changed. It costs a flat fee from $199 a month billed annually (pricing).

FAQ

What is a software license audit?
For a small business, it is checking what you pay for against who has an account in each tool and who actually works for you. Seats and subscriptions that do not match a current person and need get cancelled, downgraded or reassigned. It is different from a vendor's compliance audit, though the same records help with both.
How do I audit SaaS subscriptions?
Collect twelve months of card statements, expense reports and invoices into one row per tool. Then match each paid tool's member list against your directory, marking active, inactive, leaver and unknown accounts, and decide per tool whether to keep, trim, downgrade, consolidate or cancel.
What tools help with a software license audit?
A spreadsheet is enough for the bills and decisions at 5 to 50 people. The slow part is reading every tool's member list; access tools that read member lists for you, or SaaS management platforms built for larger companies, can speed that up.
How often should I audit software licenses?
Do a full audit once, which takes about a day, then repeat a shorter version every quarter. Between audits, removing every leaver from every tool the week they go keeps the numbers right.

Keep reading

Stop paying for a login button.

Sign in with Google Workspace, connect your tools, and see who has access to what in minutes.

Sign up with Google