Why does ARR not match revenue in the accounts?

Because they measure different things on purpose. ARR annualises committed recurring subscriptions at a point in time; statutory revenue recognises the service actually delivered during the period, deferring the rest. A company growing quickly will always show ARR ahead of recognised revenue, and a company shrinking will show the reverse. The gap is information, not an error.

What is deferred revenue and where does it appear?

Deferred revenue is cash received or invoiced for services not yet delivered, and it sits on the balance sheet as a liability until the service is performed. For a business selling annual plans up front it is often one of the largest balances on the balance sheet. Recognising it on receipt pulls profit forward and leaves nothing on the balance sheet to show what has been promised.

What should an ARR-to-revenue bridge contain?

Opening ARR, new business, expansion, contraction and churn to closing ARR; then the reconciliation from ARR to billings in the period; then from billings to recognised revenue via the movement in deferred revenue. Each step should tie to the ledger. If any step is a plug figure, the bridge is decorative.

Should the board pack use management or statutory numbers?

Both, from one ledger, with the difference explained. A board managing on metrics that cannot be traced to the accounts is managing on something nobody will be able to audit later. Using the same underlying data for both, and reporting the bridge alongside, gives the board its operating view without creating a second version of the truth.

Does implementation revenue count towards ARR?

No. Implementation, onboarding and one-off professional services are not recurring, so they do not belong in an annualised recurring revenue figure. They are real revenue and belong in the accounts; they simply are not ARR. Including them is one of the fastest ways to lose credibility in a diligence conversation.

SaaS · 🇬🇧 United KingdomScenario

Building a bridge from ARR to billings to recognised revenue

ARR and statutory revenue are supposed to differ, because ARR annualises committed subscriptions at a point in time while statutory revenue recognises what was delivered in the period, so the answer is a standing bridge between them rather than an attempt to make the two numbers agree. This is an illustrative example of how Salt approaches SaaS reporting, using a UK subscription business on annual and monthly plans as the profile.

Ask how we'd handle this

Scenario — an illustrative example of how Salt approaches this problem. Not a description of a specific client engagement.

The business shape it describes: UK SaaS, annual and monthly subscription plans.

Scenario covers: Bookkeeping, revenue recognition and monthly board reporting
Jurisdiction: United Kingdom
Sector: SaaS

The setup

Take a UK SaaS company selling both annual and monthly plans, where the board tracks ARR from the billing system and statutory accounts are prepared on an accruals basis.
Nobody can explain the gap between the two, which quietly undermines confidence in both sets of numbers.

What usually turns out to be wrong

Annual plans billed up front and recognised on receipt in management reporting, while the statutory accounts defer them, so the two diverge by construction and nobody has said so out loud.
A material portion of billings in each period relating to future service, sitting as deferred revenue on the balance sheet and as revenue in the board pack.
No bridge between ARR, billings and recognised revenue, so each explanation of the gap is improvised and slightly different from the last.
The board pack and the statutory accounts built from different sources, which means a discrepancy cannot be traced without redoing both.

How this would be worked

Implement deferred revenue properly and recognise subscription revenue across the term of the contract.
Build a standing bridge from ARR to billings to recognised revenue, reported every month in the same format so the movement is comparable period to period.
Align the board pack to the same ledger the statutory accounts are prepared from, so both are views of one dataset.
Document what each metric means, including whether ARR is measured at period end or as an average, since that choice alone moves the number.
Separate one-off implementation and services revenue from subscription revenue, because only the second belongs in ARR.

Why we'd be the right fit

The gap between a billing system's ARR and accruals-basis statutory accounts is not an error to be removed. It is a reconciliation to be built and then maintained every month.
That needs someone who holds both the subscription metrics the board manages against and the recognition treatment the accounts require, and can reconcile them in terms each side accepts.

What the business would be able to do

The board and the statutory accounts would reconcile through an explicit bridge rather than diverging silently between meetings.
The finance lead would be able to explain any movement in one slide, which is usually what the board actually wanted.
Deferred revenue would be visible as a balance that grows and unwinds, rather than being invisible until year end.

What we'd flag

The bridge only stays useful if it is rebuilt every month. A reconciliation produced once for a board meeting and then left alone is a snapshot, and it will be out of date by the next meeting.

Answers

Building a bridge from ARR to billings to recognised revenue

Where this applies

ControllerService BookkeepingService All services in United KingdomFRS 102 / UK GAAP More scenarios42 illustrative, labelled examples

Start with a number

Recognise this shape in your own books?

Tell us where you trade and what shape the books are in. You get scope, price and a start date in writing within one business day — no obligation.

Get a quote in 24 hoursBook a call instead