Most SaaS subscriptions renew automatically. The seat count and the plan are set when the tool is first bought, usually by the team that wanted it, and the vendor charges the same card for the same amount every cycle until someone stops it. Nobody checks whether the seats are still used, because nobody has to: the vendor has no reason to ask, and the card pays whatever is presented to it.
In a software company of fifty to three hundred people, with eighty or so paid tools, that means most renewals are decided by whoever set the number up first, often a year or more ago. No single renewal costs much. The problem is eighty of them a year, with no step in the process that would catch one at the wrong number.
This article covers how much of the seat count is typically wasted, why the new consumer rules on auto-renewal won't help a business, why the usual fixes miss most renewals, and how a card limit catches a renewal at the wrong amount before it is paid.
How many seats go unused
Zylo's 2026 SaaS Management Index finds that the average organisation uses 54% of the licences it pays for. The other 46% are unused or underused, which Zylo puts at about $19.8m of wasted spend a year per organisation. The data describes large enterprises, but there is no reason to think a smaller company behaves differently.
What the benchmark can't tell you is which of your own renewals went through at the wrong number last month.
The new consumer rules won't help you
UK consumers are about to get protection against exactly this. From 1 January 2027, the subscription rules in the Digital Markets, Competition and Consumers Act require traders to send a reminder before a contract auto-renews, give a cooling-off period after a trial ends or a contract renews for a year or more, and make cancelling as easy as signing up. The start date was brought forward to January 2027 in August after two earlier delays.
Unfortunately none of it applies to businesses. The rules cover contracts between a trader and a consumer, and a company buying software for its team is not a consumer. For your renewals, the vendor's "your plan has renewed" email, sent after the charge to whoever signed up, will probably remain the only notice you get.
Why the usual fixes miss most renewals
There are three common fixes that teams try, but each has the same weakness: It depends on someone having recorded the right thing at the right time.
1. A renewal calendar works if the contract date was entered when the tool was bought and someone acts before it. In a company adding tools team by team, the date often isn't entered, and acting on it is somebody's side task. The calendar holds the contracts someone remembered and misses the rest.
2. Asking vendors to switch off auto-renew has to be done tool by tool, and some vendors won't allow it.
3. A purchasing policy governs the first purchase. A renewal is a charge against a card that already exists, so there is nothing for the policy to attach to.
Put the check on the payment
The fix that doesn't depend on anyone remembering is to limit what each subscription can charge. Give every subscription its own card, with a limit set at the approved amount.
A renewal at the approved amount goes through and is attributed to the tool. A renewal at a higher plan, or with more seats, exceeds the limit and is declined. A renewal against a card that was closed when the tool was cancelled is declined too. In either case the vendor chases the failed payment or suspends the tool, so the renewal reaches a person before any money leaves.
How Moss does it
In Moss, each subscription gets a virtual card with a recurring limit set to the approved amount. For a tool you want to re-approve every time, a single purchase card closes after one charge, so nothing renews until someone issues a new card and gives the vendor new billing details.
A charge above the limit, or against a closed card, shows in Moss as a declined transaction with the reason. Attempted charges stay visible even on cards that are no longer active, so a vendor trying to renew against a card you closed shows up rather than disappearing. Declined charges sit in the card transactions list, filtered by status, with the vendor's name on each.
Moss also offers merchant cards, which link a card to a named vendor for accounting. They don't block other vendors, so it is the card limit, not the vendor link, that stops a renewal at the wrong amount.
What a caught renewal looks like
The result is a renewal that reaches a person instead of going through unnoticed. Say a design tool comes up for renewal at twelve seats, but finance only ever approved eight, so the card for that tool is limited to the value of eight seats. Without the limit, the charge would go through, the "your plan has renewed" email would go to whoever signed up, and the extra four seats would stay on the bill until someone happened to notice.
With the limit, the charge fails. The declined transaction appears in Moss with the vendor's name and the reason, and somebody has to decide: approve the extra seats and raise the limit, or cancel. Either way the renewal goes through on a number someone chose, rather than the number the vendor had on file.
Check out our help centre to see how to change card limits and the card types available in Moss.






