Accountants for SaaS startups

SaaS accountants who understand deferred revenue.

Subscription revenue does not arrive when the cash does, and getting that wrong makes your accounts, your runway and your investor reporting all disagree with each other.

Talk to us See pricing

The short answer

We act for UK SaaS and software startups: recognising subscription revenue over the period it is earned rather than when it is invoiced, keeping MRR and ARR consistent with the statutory accounts, claiming R&D relief on genuine engineering, and getting VAT right when customers are outside the UK.

The single most common thing we fix on a SaaS company's books is an annual contract booked as revenue on the day it was invoiced. It flatters the first month, empties the eleven after it, and produces a set of accounts that contradicts the MRR chart in the board pack. Investors notice, and they notice at exactly the wrong moment.

Deferred revenue is not difficult, but it has to be built into the bookkeeping rather than corrected at year end. Once it is, your accounts and your metrics finally say the same thing — and your runway calculation stops being optimistic by a quarter.

Where the money actually goes

The four numbers that decide a SaaS year

Deferred revenue

An annual plan paid up front is a liability until you have delivered the service. Recognised monthly, it makes the accounts match the MRR chart. Recognised on invoice, it makes year two look like a collapse.

Cloud and data costs

Hosting, data licences and compute are a real cost of sale, and a meaningful slice of them may sit inside an R&D claim. They have to be split deliberately rather than dumped in overheads.

Engineering payroll

Usually the largest line, and the one that decides the size of an R&D claim. Which engineers spent what proportion of their time on genuinely uncertain work is a question worth answering monthly, not in month thirteen.

VAT on overseas customers

Place of supply for digital services is not where you are, it is where your customer is, and it differs for businesses and consumers. Get it wrong across a few hundred subscriptions and unpicking it is genuinely expensive.

R&D relief in this sector

Where a software claim usually stands or falls

HMRC is asking a technical question, not a commercial one, and software claims are where that distinction bites hardest. Building a well-made product on mature frameworks is not an advance in the field, however hard it was and however novel the business idea.

What does usually qualify: algorithms with no published solution; making a system perform at a scale where the standard architecture demonstrably fails; integrations that genuinely required experiment, failure and redesign; machine learning work where it was unknown at the outset whether the approach would function at all.

What usually does not: standard web and mobile applications, interface design, configuring off-the-shelf software, API integrations that worked as documented, data migration, and testing that was hard rather than uncertain.

Two things then decide the number. Cloud computing and data licence costs qualify, which matters a great deal to a company whose infrastructure bill is its second-largest line. And the PAYE and NIC cap — £20,000 plus 300% of your PAYE and NIC bill — bites hard on teams whose engineers invoice through their own companies rather than sitting on payroll. That is a decision about how you hire, made long before the claim, and it is worth modelling first.

How we handle R&D claims SEIS and EIS

A worked example

The same spend, two routes

A loss-making UK SaaS company, year to 31 March. Total expenditure £600,000. Of that, £220,000 is qualifying R&D — engineering time on genuinely uncertain work, plus the cloud and data costs behind it. PAYE and National Insurance for the year: £45,000.

Intensity: £220,000 ÷ £600,000 = 36.7%, comfortably above the 30% threshold, so the intensive route is available.
Intensive route: £220,000 × 186% = £409,200 surrendered, at 14.5% = £59,334 in cash.
Merged scheme: £220,000 × 20% = £44,000, taxed at the small profits rate, leaving £35,640.
Cap check: £20,000 + (300% × £45,000) = £155,000. The claim sits well under it and pays in full.

The difference is £23,694 on identical work, decided entirely by an intensity calculation. And had the cloud costs been left out — as they routinely are, because the person preparing the claim is working from a pre-2023 list — the claim would have been smaller again.

Illustrative figures, chosen to show how the arithmetic behaves. Your numbers will differ, which is exactly why the calculation gets done before anything is filed.

What we do for you

The job, end to end

Revenue recognised over the subscription period, built into the bookkeeping rather than fixed at year end
MRR, ARR and churn that reconcile to the statutory accounts, so the board pack and the filing agree
R&D claims on genuine engineering, with the cloud and data costs included and the PAYE cap modelled first
VAT registration and place-of-supply treatment for customers outside the UK
EMI options for the engineers you cannot yet pay properly, valued with HMRC
Runway and burn that account for deferred revenue rather than flattering it

Questions

Straight answers

How should a SaaS startup recognise annual contracts?

Over the period the service is delivered, not on the date you invoice. An annual plan paid up front creates deferred revenue — a liability — that unwinds monthly into the profit and loss account. Doing it on invoice inflates the month of sale and empties the following eleven, which is why some SaaS accounts look like a business that grew brilliantly and then stopped.

Does our cloud bill qualify for R&D relief?

Cloud computing and data licence costs have qualified since April 2023, so the compute behind genuinely uncertain development work can go into a claim. Ordinary production hosting for a running product does not. The split has to be defensible, which is easier if it is tracked through the year rather than reconstructed afterwards.

We sell to customers in the EU and the US. Where is our VAT due?

Place of supply for digital services follows the customer, not you. Business customers outside the UK are generally outside the scope with the reverse charge applying; consumers are taxed where they are, which can create obligations in their country. It is one of the few areas where a few hundred small subscriptions create a genuinely awkward problem, so it is worth settling before you scale.

Do you work with pre-revenue software companies?

Yes, and it is the best time to start. Pre-revenue is when the share structure, the R&D position and the payroll decisions are still cheap to change, and all three are expensive to unwind once there is a valuation and an investor on the register.