Who it's for: anyone posting or reviewing revenue journals for SaaS customers who pay a year in advance.
What you'll get: every journal for an annual upfront contract from invoice to renewal, a 12-month table you can tick through, worked examples for free months and early cancellation, and a one-slide summary for your boss.
Reading time: about 10 minutes. Have last month's deferred revenue balance to hand.
Why annual billing trips people up
Annual upfront billing is brilliant for cash and confusing for everyone else. A £24,000 invoice lands in one month, but only £2,000 of it is revenue that month. The rest sits on the balance sheet, slowly turning into revenue for the next eleven months. Get the first journal wrong and every month after it is wrong too.
Key terms
- Deferred revenue: money billed for service not yet delivered. A liability on the balance sheet.
- Release: the monthly journal moving one month's worth of deferred revenue into revenue.
- Service period: the 12 months the customer is paying for. This drives revenue, not the invoice date.
- Tax point: the date that decides which VAT return the VAT on a sale goes on.
- Billings: the total invoiced in a period. Not the same as revenue.
The journals at a glance
| Event | Dr | Cr | Revenue impact |
|---|---|---|---|
| Invoice raised | Trade debtors (gross) | Deferred revenue (net); VAT output tax | None |
| Cash received | Bank | Trade debtors | None |
| Each month of service | Deferred revenue | Subscription revenue | One month's share |
| Payment processor fee (if paid by card) | Payment processing fees (cost) | Bank or processor clearing account | None (it's a cost) |
| Renewal invoice | Trade debtors | Deferred revenue; VAT output tax | None until the new term starts |
The revenue journal never touches the bank, and the invoice journal never touches revenue. If either does, something has gone wrong.
Worked example 1: a standard annual contract, month by month
MonthEndClub Co Ltd (fictional) signs Alder Ltd to a 12-month subscription running 1 November 2026 to 31 October 2027.
- Price: £24,000 plus VAT at 20% (the UK standard rate as at October 2026), so £28,800 gross.
- Invoiced on 15 October 2026, two weeks before the service starts, on 30-day terms.
- Alder pays by bank transfer on 14 November 2026.
- MonthEndClub Co Ltd releases revenue monthly: £24,000 ÷ 12 = £2,000 a month.
15 October: raise the invoice
| Account | Dr | Cr |
|---|---|---|
| Trade debtors | £28,800 | |
| Deferred revenue | £24,000 | |
| VAT output tax | £4,800 |
No revenue in October: the service hasn't started. For VAT, an invoice issued before the service usually creates the tax point, so the £4,800 typically goes on the return covering 15 October, even though the customer hasn't paid. Check the timing rules on gov.uk (VAT Notice 700 and HMRC's time of supply guidance) for your own billing pattern.
14 November: cash received
| Account | Dr | Cr |
|---|---|---|
| Bank | £28,800 | |
| Trade debtors | £28,800 |
30 November, and every month-end to October 2027: release
| Account | Dr | Cr |
|---|---|---|
| Deferred revenue | £2,000 | |
| Subscription revenue | £2,000 |
The 13-month view
| Month | Billed (net, £) | Released (£) | Deferred revenue at month-end (£) | Debtor at month-end (£) | |
|---|---|---|---|---|---|
| ☐ | Oct 2026 | 24,000 | 0 | 24,000 | 28,800 |
| ☐ | Nov 2026 | 0 | 2,000 | 22,000 | 0 |
| ☐ | Dec 2026 | 0 | 2,000 | 20,000 | 0 |
| ☐ | Jan 2027 | 0 | 2,000 | 18,000 | 0 |
| ☐ | Feb 2027 | 0 | 2,000 | 16,000 | 0 |
| ☐ | Mar 2027 | 0 | 2,000 | 14,000 | 0 |
| ☐ | Apr 2027 | 0 | 2,000 | 12,000 | 0 |
| ☐ | May 2027 | 0 | 2,000 | 10,000 | 0 |
| ☐ | Jun 2027 | 0 | 2,000 | 8,000 | 0 |
| ☐ | Jul 2027 | 0 | 2,000 | 6,000 | 0 |
| ☐ | Aug 2027 | 0 | 2,000 | 4,000 | 0 |
| ☐ | Sep 2027 | 0 | 2,000 | 2,000 | 0 |
| ☐ | Oct 2027 | 0 | 2,000 | 0 | 0 |
| Total | 24,000 | 24,000 |
What "done" looks like each month: the release is posted, the customer's deferred revenue balance matches the table, and the total deferred revenue account agrees to the schedule for all customers.
If MonthEndClub Co Ltd's financial year ends on 31 December, the year-end balance sheet shows £20,000 of deferred revenue for Alder and the 2026 P&L shows only £4,000 of revenue from a contract that brought in £28,800 of cash. That's correct, and it's worth explaining to anyone who only looks at the bank.
AI shortcut: give an approved AI tool the contract value, service start and end dates and your release method, and ask it to produce the 13-month table above, including a running deferred revenue balance. Check that releases total the contract value and the balance ends at zero. For a batch of new contracts, give it the billing export and ask for one table per customer plus a total.
Worked example 2: three free months
MonthEndClub Co Ltd signs Birch Analytics to a 15-month contract from 1 November 2026 to 31 January 2028. Birch pays £36,000 (plus VAT) upfront on 1 November for "12 months plus 3 months free".
The customer is getting 15 months of service for £36,000, so revenue is spread over all 15 months: £36,000 ÷ 15 = £2,400 a month. Releasing £3,000 a month for 12 months and nothing for the free months would bring revenue forward.
| Account (each month, Nov 2026 to Jan 2028) | Dr | Cr |
|---|---|---|
| Deferred revenue | £2,400 | |
| Subscription revenue | £2,400 |
Check: 15 × £2,400 = £36,000. The same logic applies if the free months come at the end, or in the middle. The sales team may describe it as a discount on year one; the accounts treat it as one price for 15 months.
Worked example 3: the customer cancels early
Back to Alder. After the April 2027 release, Alder gives notice and stops using the service from 30 April 2027. The deferred revenue balance is £12,000. What happens next depends on the contract:
| Contract term | Typical treatment of the £12,000 |
|---|---|
| No refund, and MonthEndClub Co Ltd has no further obligations | Released to revenue when the obligation ends, because nothing is left to deliver |
| Pro rata refund for unused months | Moved to a refund liability and paid back; never released to revenue |
| No refund, but access continues to 31 October | Keep releasing £2,000 a month; the service is still being provided |
Journals for a pro rata refund. Alder is refunded the six unused months: £12,000 plus the VAT of £2,400 via a credit note, so £14,400 in total.
| Account | Dr | Cr |
|---|---|---|
| Deferred revenue | £12,000 | |
| VAT output tax | £2,400 | |
| Trade debtors (credit note) | £14,400 |
| Account | Dr | Cr |
|---|---|---|
| Trade debtors | £14,400 | |
| Bank | £14,400 |
Revenue for the contract ends at six months × £2,000 = £12,000, which matches the six months of service delivered.
The monthly checklist
| Task | What "done" looks like | |
|---|---|---|
| ☐ | Check every new annual invoice went to deferred revenue | Revenue account shows no direct postings from the billing sync |
| ☐ | Confirm service dates for each new contract | Start and end dates agree to the order form, not the invoice date |
| ☐ | Flag free months, discounts and non-standard terms | Release amount reflects the full service period |
| ☐ | Post the month's release | Release total equals the schedule's "released" column |
| ☐ | Process cancellations and credit notes | Balance for each cancelled customer cleared or moved to a refund liability |
| ☐ | Reconcile deferred revenue | Ledger equals schedule; schedule agrees to billing system |
| ☐ | Check upcoming renewals | Renewal invoices raised for next month's start dates |
If you report under US GAAP (ASC 606)
The journals are the same: bill to deferred revenue (a contract liability), then release over the service period. One presentation point comes up more often in US audits: when an invoice is raised before the service starts and the customer can still cancel before paying, some companies don't record the debtor and deferred revenue until payment is due or received. The aim is to avoid grossing up the balance sheet for amounts that aren't yet an unconditional right to payment. Many UK teams take a similar view under IFRS 15, so it's worth agreeing a policy with your auditor.
Common mistakes and audit watch-outs
- Posting the annual invoice straight to revenue. Usually caused by a billing integration mapped to the revenue account. Check the mapping once and the revenue account every month.
- Starting the release on the invoice date. An October invoice for a November start releases nothing in October.
- Ignoring free months. Revenue is spread over every month of service, paid or free.
- Releasing the balance when a customer cancels with a refund due. Refundable amounts aren't revenue.
- Forgetting VAT timing. VAT on an advance invoice typically falls due on the return covering the invoice date, before the cash arrives. Cash flow forecasts need to allow for that.
- Netting card fees off revenue. If the customer pays through a processor such as Stripe, the fee is a cost. Revenue stays at the full price.
- Trusting an AI-built schedule without checking it. AI can slip a month on start dates or round inconsistently. Check the first and last month, the total and the zero balance at the end.
Tools that can help
Billing tools such as Chargebee and Stripe Billing can create revenue schedules from subscription start and end dates. Xero and QuickBooks users often run a spreadsheet schedule in Excel or Google Sheets and post one release journal a month; NetSuite can automate the release. An approved AI assistant is handy for building schedules for batches of new deals. Tools speed up the posting; the review of dates, terms and the reconciliation is still a person's job.
Take it to your boss: one slide
Why cash is up but revenue isn't (and why that's fine)
The problem
- Annual upfront deals bring in a year's cash at once, but revenue arrives monthly.
- People outside finance compare bank balances with the P&L and get confused.
- Mistakes at the invoice stage flow through every month after.
Three changes
- Report billings, revenue and deferred revenue side by side each month.
- Check billing-to-ledger mapping so annual invoices always land in deferred revenue.
- Use AI to draft schedules for new deals, reviewed against contracts.
| Risk | Control |
|---|---|
| Invoice posted to revenue | Monthly review of direct postings to revenue |
| Wrong start date or free months missed | Order form check on all new contracts |
| Refunds released as revenue | Cancellation review against contract terms |
| AI schedule errors | Approved tool; totals and dates checked by reviewer |
How we'll measure it: deferred revenue reconciled with nil unexplained difference each month, and no post-close revenue adjustments.
Rates, thresholds and rules in this guide
Figures were checked against the pages below in October 2026. They change regularly (often each April or at Budget time), and we can't guarantee they're still current or right for your situation. Always check the official page before relying on them.
- VAT rates (GOV.UK): the UK standard VAT rate of 20%
- VAT guide (VAT Notice 700) (HMRC, GOV.UK): tax points for VAT invoices issued before the supply, and for continuous supplies of services
- VAT Time of Supply Manual (HMRC, GOV.UK): tax point rules for invoices issued before the service
Key takeaways
- Annual invoices go to deferred revenue; revenue follows the service period.
- Release monthly (or daily) from the service start date, not the invoice date.
- Free months stretch the release over the full service period.
- On cancellation, the contract terms decide whether the balance becomes revenue or a refund.
- VAT on an advance invoice is usually due before the cash arrives.
- AI can build the schedule; a person checks dates, totals and terms.
FAQs
Why isn't the full annual invoice revenue when the customer has paid?
Because revenue is earned as the service is delivered. Payment in advance creates an obligation to provide 12 months of service, which is why it sits as deferred revenue until each month is delivered.
Should we release by month or by day?
Both are common. Monthly is simpler when contracts start on the 1st. Daily is more accurate for mid-month starts. Many teams pick one as a policy and use it for every contract.
What happens to deferred revenue at year-end?
It stays on the balance sheet as a liability, split between current (released within 12 months) and non-current (later). For a standard annual contract it's all current.
Can AI post these journals for us?
AI can draft the schedule and the journal, and some accounting tools can post recurring journals automatically. A person still reviews new contracts, checks the release against the schedule and approves the journal. Use only AI tools your company has approved for customer data.
Related guides
- How to Build and Reconcile a Deferred Revenue Schedule
- SaaS Revenue Recognition in Plain English (IFRS 15 / ASC 606)
- Upgrades, Downgrades and Mid-Contract Changes
- Journal Entry Cheat Sheet: Debits and Credits for Common SaaS Transactions
More in Revenue guides.
From the Club
Paid for upfront, enjoyed monthly. The Washed Cap · The Team Mug
Join the Club. New guides, early access and members-only batches. Join here.
This guide is general information about common practice. It isn't tailored to any business, and standards, tax rules and figures change. Check your own circumstances, the latest rules and, where needed, a qualified professional before acting.
Last reviewed: October 2026.