A customer pays you £1,200 for an annual plan. Your bank balance jumps by £1,200 that day. But if your P&L shows £1,200 of revenue in that same month, it's wrong, even though the cash genuinely arrived.
This is the single most common source of confusion for founders looking at their own accounts for the first time. Here's what's actually going on, and why it matters more than it seems.
Cash isn't revenue
Getting paid and earning revenue are two different events. You've been paid the moment the card is charged. But you haven't earned the money yet, because you haven't delivered the service yet. You owe the customer 12 months of access.
Accounting recognises this by treating the unearned portion as a liability, not income. That liability is called deferred revenue (sometimes "unearned income").
Working through the example
Customer pays £1,200 upfront for a 12-month plan on 1 June.
- Cash: +£1,200 on 1 June, in full
- Revenue recognised: £100 in June, £100 in July, £100 in August, and so on through May of next year
- Deferred revenue (balance sheet liability): starts at £1,100 after June, and decreases by £100 each month as it's recognised as revenue
By the end of the contract, all £1,200 has moved from "deferred revenue" to "revenue". At any point in between, your balance sheet shows exactly how much you still owe the customer in service.
If you instead booked the full £1,200 as revenue in June, that month looks artificially strong, and every month after looks artificially weak, since none of the ongoing service shows up as income at all.
Why this matters beyond bookkeeping tidiness
Your monthly numbers become meaningless without it. If some customers pay monthly and others pay annually upfront, a P&L without deferred revenue swings wildly based on how many annual renewals happened to land that month, not on how the business is actually performing.
Investors and lenders check for it. Anyone doing diligence on a subscription business will ask how you handle deferred revenue. If the answer is "we don't", it signals the rest of the books probably aren't reliable either.
It reconciles against your MRR. Monthly recurring revenue and P&L revenue should tell a consistent story over time. If they diverge sharply and you can't explain why, deferred revenue is usually the reason.
You need it to know what you actually owe. If you shut down tomorrow, the deferred revenue balance is roughly what you'd owe customers for undelivered service. It's a real liability, not an accounting abstraction.
How to handle it practically
For monthly billing, you can mostly ignore this. Revenue is recognised in the same month it's collected, so cash and revenue line up closely enough not to matter.
For annual (or multi-month) upfront payments, you need a deferred revenue schedule:
- When the payment comes in, record the full amount as deferred revenue (a liability), not revenue
- Each month, release the appropriate portion (contract value ÷ contract length) from deferred revenue into recognised revenue
- Keep a simple schedule (a spreadsheet is fine) tracking each annual contract's start date, monthly release amount, and remaining balance
FreeAgent doesn't automate this for you. There's no native "spread this invoice over 12 months" feature, so you'll be doing the monthly release with manual journal entries unless you build your own tooling around it.
The common mistake
The most common mistake isn't getting the mechanics wrong, it's not doing it at all. Founders on annual-heavy plans often just book payments as revenue when they land, because that's what the bank feed shows and nobody's told them otherwise. The books balance, VAT returns file fine, and everything looks normal until someone asks "what's your revenue trend look like month over month?" and the answer doesn't hold together.
If you're taking any upfront annual payments, it's worth setting up the deferred revenue schedule now, even if it's just a spreadsheet, rather than trying to reconstruct 18 months of contracts later.
If you're using Stripe
Stripe Billing tracks subscription and invoice data accurately, but it reports what was billed and collected, not what should be recognised as revenue in a given period. If you're syncing Stripe invoices into FreeAgent with ClearingHouse, you'll get an accurate mirror of what Stripe billed and collected, which is the correct starting point for a deferred revenue schedule, but the recognition and release still needs to happen as a separate step on top.
Blog