SaaS spend management: How finance teams get subscription costs under control

Your SaaS costs are rising even when you haven't bought anything new. Between vendor price increases, auto-renewals nobody approved, and subscriptions that outlast the employees who signed up for them, software has quietly become one of the least controllable line items on your P&L.

71% of companies have at least one SaaS subscription with no billing owner. That lack of control usually starts quietly. A tool gets purchased on a company card, a renewal date sits in someone's calendar, and finance only sees the full picture once costs are embedded in the budget. Spend management for SaaS helps you find every subscription you pay for, control how new tools get purchased, and decide what you keep.

This guide runs from first audit to ongoing controls, with the UK-specific compliance context most guides miss. It's general guidance for finance teams, not tax or legal advice. Consult a qualified adviser for decisions specific to your organisation.

Why your SaaS portfolio is harder to control than any other cost category

UK CFOs are increasing their technology investment. Deloitte's CFO Survey for Q4 2025 found 59% of UK CFOs optimistic about AI's impact on their organisation, up from 39% a year earlier, with 77% expecting productivity growth over the medium term. Gartner forecasts European software spending to grow from around $290 billion in 2025 to over $335 billion in 2026 (roughly £230 billion to £266 billion at end-2025 rates).

Rising software spend is exactly where SaaS sprawl builds. Nobody sets out to create it. It happens because the buying process shifted: SaaS now sits with business units and individual employees signing up for tools on company cards, expense accounts, or free trials that quietly convert to paid plans.

If you've ever discovered a £200/month charge six months after someone left, you know how this plays out at month-end. Most finance teams discover one of these on their first audit. Some find a dozen.

Shadow IT creates costs you can't see and compliance risks you can't ignore

Every untracked subscription is both a financial leak and, where it involves personal data, a potential UK GDPR exposure. A marketing manager signs up for a data analytics tool using their work email. That tool may then process personal data without a data processing agreement, sit outside your data processing records, and stay unknown to finance entirely. In many organisations, technology spending now extends well beyond the IT department.

Duplicate subscriptions across departments mean you're funding the same capability multiple times and weakening your position on volume discounts. Building spend visibility at the subscription level is the first step toward fixing both.

Auto-renewals commit your budget by default

You rarely lose control of SaaS costs in one big decision. Auto-renewal clauses lock in spend quietly when nobody tracks notice windows. Miss the notice window, often 30 to 60 days before the contract end date, and you're locked in for another year at whatever price the vendor sets. The risk often stays invisible until the charge hits.

Teams that prepare for renewals earlier usually have more options to negotiate or cancel. If renewal dates are sitting in someone's personal calendar, or worse, in no calendar at all, the audit section below is where to start.

How to audit your SaaS estate and build a central inventory

If you've inherited a SaaS portfolio you didn't build, the first audit can feel overwhelming. You don't know what you don't know, and the data is scattered across card statements, expense claims, and departmental budgets nobody has consolidated. You already control the strongest discovery channel available: your financial data.

This part isn't elegant. Card statements, expense claims, and single sign-on logs are three different exports, and reconciling them takes a morning you didn't plan for. Start with the data sources you can access most easily.

Corporate card and expense claims analysis

If you need a baseline inventory quickly, this is usually the fastest place to start. Pull 12 months of card statements and flag every recurring charge. Look specifically for SaaS vendor names, free trial conversions, and charges appearing across multiple departments for similar amounts. This is also where SaaS subscription management typically begins for finance teams without a dedicated tool.

Email domain analysis

Card data won't catch everything. Every SaaS sign-up generates a welcome or confirmation email. Scan your corporate email provider (Google Workspace or Microsoft 365) for those sign-up messages, and you'll quickly see which tools employees are actually using.

Single sign-on and identity provider logs

Paid licences and real usage often drift apart. These logs show which tools people actually access, versus which licences your company pays for. Tools that sit outside your single sign-on (SSO) environment are likely shadow IT. The gap between what's paid for and what's authenticated through SSO shows where your controls have the widest holes.

Build the inventory with these minimum fields

For each subscription, record:

1. Vendor name

2. Contract start and end dates

3. Annual cost

4. Named business owner

5. Licence count

6. Auto-renewal clause details (including notice window)

7. Whether the tool processes personal data

A spreadsheet works fine until you're managing around 50 applications. Beyond that point, manual upkeep starts to undermine accuracy.

This audit shouldn't be a single exercise. Schedule quarterly refreshes against card statements and SSO logs. The SaaS estate shifts faster than an annual review can track, especially with new AI tools joining the portfolio.

Approval workflows and policies that prevent new sprawl

Finding today's subscriptions won't solve much if tomorrow's purchases follow the same path. Without controls in place, the same sprawl will rebuild itself within months. Many companies still operate without a documented SaaS procurement policy, and that's where spend control starts to break down.

Set approval thresholds that account for recurring costs

Monthly pricing makes subscriptions look smaller than they really are. A common mistake is evaluating SaaS at its monthly cost rather than its annualised commitment. A £200/month subscription is a £2,400 annual commitment with auto-renewal provisions.

Would a £200/month subscription clear your current approval process, or does it slip through because nobody evaluates it at its £2,400 annual value? Your approval matrix should apply annualised values to every recurring subscription.

Consider a tiered structure based on contract value and data sensitivity. Low-value tools that don't process personal data might need only a department manager's sign-off. Anything above £5,000 annually, or any tool processing company or customer data, should route through both IT security review and finance budget confirmation.

Subscriptions are generally treated as an operating expense on the P&L (ICAEW guidance). Where a cloud arrangement gives the customer control of the underlying software, the cost may be capitalised under IAS 38. Approval workflows matter more for SaaS than for one-off purchases because they give finance earlier visibility, before spend becomes embedded.

Embed a "consolidate before you add" check

Duplicate tools are easier to prevent than unwind. Before any new tool is approved, the requesting team should confirm that no existing tool in your inventory already covers the use case.

Build this as a required field in the intake form. It catches duplicates at the point of purchase, which works far better than auditing for them after the fact every quarter. This way, finance keeps oversight without becoming the bottleneck for every £50 tool request.

Contract renewals and licence rightsizing: Where the savings are

Renewal season catches most finance teams off guard. The contract dates exist somewhere; nobody has consolidated them into a single view. Unused licences are common, so renewal decisions should start with actual usage, not the licence counts on paper.

Build a three-stage renewal calendar

Renewal dates matter less than the actions tied to them. Set automated alerts at three points before each contract end date:

• 90 days out: Trigger a usage review to confirm whether the tool is being used at the current licence count.

• 60 days out: Make the renewal or cancellation decision. Begin vendor negotiation if renewing.

• 30 days out: Escalate if no decision has been recorded.

When you do negotiate, lead with actual usage data. That gives you a stronger basis for discussing reduced licence counts or tier downgrades.

Use virtual cards to enforce subscription controls

The easiest subscription to track is the one tied to its own payment method. Assigning a unique virtual card to each subscription means the inventory updates itself. If you need to cancel a tool, you freeze the card. If a vendor increases pricing, the charge won't process at the higher amount without explicit finance approval.

Spendesk is an all-in-one spend management platform consolidating company cards, expense management, accounts payable, procurement, and budgeting. According to Spendesk, customers can save up to 7% on subscription costs.

For example, Niji scaled to 12x their original transaction volume, and their 104 subscriptions, including 80+ AI licences, needed centralised control. After implementation, they manage all of these through a single dashboard. For finance teams, that kind of central view makes it easier to spot ownerless subscriptions, track renewals, and keep recurring spend from slipping outside policy.

UK compliance requirements most SaaS guides ignore

Savings at renewal matter, but they're only part of the picture. UK finance teams also face regulatory obligations that most SaaS guides ignore, and the cost of missing them isn't small.

VAT reverse charge on overseas SaaS purchases

Overseas SaaS invoices can create problems long before an audit if the VAT treatment is wrong. When you buy SaaS from an overseas supplier in a B2B context, the VAT reverse charge applies.

The supplier doesn't charge UK VAT. You account for output VAT yourself and simultaneously reclaim input VAT, subject to normal recovery rules. It's worth checking that every overseas SaaS invoice is correctly issued as a B2B supply.

GDPR and your SaaS vendor register

A missing vendor record is a compliance risk in its own right. Under UK GDPR Article 28, you need a written Data Processing Agreement with each vendor that processes personal data on your behalf, including most SaaS vendors. The ICO sets out what these contracts must contain.

Under Article 30, you also need to list your vendors in your Records of Processing Activities and document any international data transfers. GDPR penalties can reach up to 4% of global annual turnover or £17.5 million, whichever is higher, for the most serious violations under UK GDPR Article 83.

Your SaaS inventory doubles as a compliance asset. The fields you already need for cost control (vendor name, owner, personal data flag) are the same fields you need for Articles 28 and 30. Accounting automation can help keep that record current as the estate changes.

Companies Act 2006 record keeping

Poor subscription records create accounting problems even when the spend itself is legitimate. Your accounting records must accurately reflect your company's financial position, per Companies House guidance. For SaaS portfolios, that means tracking contracts and committed future expenditure, and spreading upfront annual payments across the months of the contract as prepayments. HMRC tax rules require keeping accounting records for at least six years.

If your current systems can't produce that documentation on demand, the inventory work above is where to start.

SaaS contracts under FRS 102 and IFRS 16

Most SaaS contracts stay off the balance sheet, but not all of them. As service contracts, they're generally expensed in the P&L over the contract term, with any prepaid amounts recognised as assets. IFRS 16 lease accounting generally doesn't apply, and FRS 102 treatment depends on the applicable UK GAAP guidance.

The exception is dedicated infrastructure. If a SaaS contract gives you control over specific, identified IT infrastructure, it may count as a lease and need balance sheet recognition. The question is whether you control the underlying asset or simply consume a service. For long-term, dedicated infrastructure SaaS contracts, it's worth confirming the treatment with your auditor.

Getting SaaS costs under control without slowing your teams down

The companies with ownerless subscriptions aren't usually careless. More often, software buying moved faster than the controls around it. None of this is hard. It just hasn't been anyone's job to do all of it.

The finance teams that close that gap do the design work upfront. They build the inventory, set the approval thresholds, automate the renewal alerts, and assign a virtual card to every subscription. The alternative is funding tools nobody uses and explaining budget variances you didn't see coming.

Hidden subscriptions stop growing once each tool has an owner, a payment trail, and a renewal decision point. That closes the 71% gap from the opening of this guide, and stops the £200/month departed-employee charge from ever reaching your P&L.

See how Spendesk handles subscription management and virtual cards for finance teams looking to bring spend control software to their SaaS estate.

Frequently asked questions about SaaS spend management

What should finance prioritise first in an initial SaaS audit?

Start with the data you can access most easily. In practice, that usually means corporate card statements and expense claims first, because they show recurring charges, free trial conversions, and duplicate tools across departments. Once you have that baseline, deepen it with email domain analysis and single sign-on logs.

What evidence should finance bring into a SaaS renewal negotiation?

Actual usage data. If you can show how many licences are paid for, how many are actively used, and whether usage supports the current tier, you have a stronger basis for asking for reduced counts or a downgrade. Renewals work better when you lead with current usage rather than last year's contract.

How should finance handle subscriptions that sit outside single sign-on?

Treat them as a control gap worth reviewing closely. Tools outside your single sign-on environment are more likely to be shadow IT. That means finance may be paying for software that hasn't gone through the same visibility, ownership, or compliance checks as the rest of the stack. Compare what you pay for with what employees actually authenticate through single sign-on, and you'll see where those gaps sit.

How can finance keep control without becoming the bottleneck for every software request?

Set the rules before the purchase happens. Clear approval thresholds, a check for existing tools, and routing that sends requests to the right reviewers let finance keep oversight without manual involvement in every low-value request. That gives teams room to move while keeping software spend visible and accountable.