Before the Renewal Email Lands: A SaaS Licence Audit for UK SMEs

Software as a service has a convenient billing model and an inconvenient habit: it renews quietly. For many UK SMEs, the stack of tools used across finance, sales, operations and HR has grown one card payment at a time. By mid-November 2026, finance teams should be looking at the renewal calendar, not waiting for the vendor email. In many contracts, the notice window closes 30 or 60 days before the anniversary, and January price uplifts are often baked into the terms.

Start with the payment trail, not the contract folder

The contract folder is usually incomplete. Bank statements, card exports and direct debit mandates are more honest. Pull the last 12 months of software payments and build a simple subscription register. For each vendor, record the product, the internal owner, monthly or annual cost, billing frequency, renewal date, notice period, seat count, payment method and a link to the contract or order form. Note whether the figure is net or gross of VAT so the cash view is not distorted.

Assign a named owner to every line. A tool without an owner is a tool without a business case. This is also the moment to spot duplicate categories: two project management platforms, three video conferencing accounts, several analytics tools bought by different teams. The register should be dull, shared and current. A spreadsheet is sufficient if it is protected and reviewed.

Count seats against active use

Seat counts drift. Leavers keep licences, project teams keep access after the project closes, and shared logins hide the true number of users. Export the user list from each vendor admin console and compare it with HR records or the active directory. Flag accounts that have not logged in for 60 or 90 days. Do not cancel automatically where data retention, audit or client access obligations apply, but make a deliberate decision rather than paying by default.

Check minimum seat commitments too. Some contracts allow downgrades only at renewal, and some annual plans lock in the seat count for 12 months. If usage is seasonal, an annual upfront purchase may look cheaper per seat but cost more in practice. Right-sizing before renewal is easier than renegotiating after the invoice has been raised.

Read the renewal clause, not just the price

The renewal clause matters more than the headline subscription cost. Look for the notice period and the method required to cancel. Some suppliers accept an email; others require a portal submission or recorded delivery. Find any price escalation language: CPI or RPI-linked uplifts, list price adjustments, prevailing rate clauses or a stated percentage increase. A modest monthly fee can become a material annual cost after two or three automatic uplifts.

Diarise every notice deadline now. If a notice date has already passed for a contract that is not needed, ask the supplier whether a mid-term exit or downgrade is possible. If not, record the date for the next cycle and set an alert 90, 60 and 30 days before it. Do not rely on the renewal email as the first warning; by then the decision may already have been made for you.

Sort the estate into four boxes

A useful audit separates software into four groups: core, contested, duplicate and dormant. Core tools are business-critical and should be negotiated properly. Contested tools have low usage, poor adoption or a cost that no longer matches value. Duplicates perform the same job and should be consolidated. Dormant tools are paid for but unused and should be exported and cancelled.

For core tools, negotiate before renewal using evidence: active user numbers, growth forecasts, budget constraints and competitor quotes where available. Ask for seat right-sizing, a price hold, improved payment terms or a shorter notice period. Be cautious with multi-year discounts unless the contract includes a clear exit route. For contested tools, ask the owner to justify the renewal in one page. For duplicates, choose one platform and set a migration date. For dormant tools, confirm the data export and cancellation steps before the next billing date.

Put renewal dates where finance can see them

A subscription register is only useful if it feeds a calendar. Create a shared renewal calendar with owners and deadlines. Add a simple approval rule for new software: no card payment without a register entry and an owner. This does not need to be heavy bureaucracy. It stops the small, recurring purchases that never reach procurement and never appear in the budget.

Review the register quarterly and before each major renewal month. Finance should challenge any line that has no owner, no usage data or no renewal date. Department heads should confirm whether the tool is still needed. The aim is not to ban software; it is to make the buying decision visible before the money leaves the account.

Close the loop after cancellation

Cancellation is not complete when the email is sent. Get written confirmation, note the effective date, remove or freeze the payment method where appropriate, export the data and check the next statement for unexpected charges. Watch for true-up invoices, auto-renewals that were not properly processed and minimum-term charges. Update the register so the same subscription does not reappear in the next audit.

For UK SMEs, the festive period is a practical deadline. A two-hour review in November 2026 can prevent a year of silent spend and give owners room to negotiate before January 2027 invoices land. The renewal email is not the starting gun. The payment trail, the user list and the notice clause are.