About This Template
Revenue recognition is one of the most consequential — and most frequently mishandled — accounting areas for SaaS and subscription businesses. The difference between cash received and revenue recognised can be significant: a customer who pays £24,000 for an annual subscription in January generates £24,000 of cash but only £2,000 of recognised revenue per month. If the company recognises the full £24,000 in January, both the revenue and the balance sheet are wrong — and auditors will find it.
IFRS 15 (Revenue from Contracts with Customers) provides the framework for recognition. Its five-step model requires companies to identify the contract, identify the performance obligations, determine the transaction price, allocate the price to performance obligations, and recognise revenue when (or as) performance obligations are satisfied. For most SaaS and subscription businesses, this means recognising monthly subscription revenue on a straight-line basis over the contract term, and recognising usage-based revenue as services are consumed.
This template provides four sheets: Instructions (covering IFRS 15 principles), a Contract Register for active contracts, a Monthly Recognition Schedule showing the recognition of each contract's revenue across 12 months, and a Deferred Revenue Bridge summarising the monthly movement in the deferred revenue liability with key metrics.
What's Included
Sheet 1: InstructionsAn overview of the IFRS 15 five-step model and how it applies to common revenue types at SaaS and fintech businesses. Includes guidance on how to classify contracts (subscription, usage, one-time, milestone) and how to choose the appropriate recognition method for each. Also covers how to tie the schedule to your accounting system's deferred revenue balance.
Sheet 2: Contract RegisterA register of all active contracts with the following columns: Contract ID, Customer Name, Contract Start, Contract End, Total Contract Value (£), Revenue Type (Subscription / Usage / One-time / Milestone), Recognition Method (Straight-line / Usage / Milestone), PO/SO Reference, VAT Rate, and Notes. Structured for 20 active contracts — add rows as needed. This is the source of truth for the Monthly Recognition Schedule.
Sheet 3: Monthly Recognition ScheduleFor each contract in the register, a row showing: Deferred Revenue b/fwd (opening balance), revenue recognised in each month (Jan–Dec), Deferred Revenue c/fwd (closing balance), and an annual total recognised. For straight-line contracts, the monthly recognition is Total Contract Value divided by contract months. Usage and milestone contracts require manual input. Totals row provides the aggregate revenue recognised by month and the total deferred revenue balance at each month-end.
Sheet 4: Deferred Revenue BridgeMonthly: Opening deferred revenue balance, new bookings (cash received for future periods), revenue recognised in the period, cancellations and refunds, and closing deferred revenue balance. A 12-month running view. Key metrics: Deferred Revenue as months of forward revenue, NRR (Net Revenue Retention) calculated from the schedule, and the ratio of deferred revenue to recognised revenue.
How to Use This Template
- Populate the Contract Register first: Enter every active contract at the start of the period. For existing contracts, calculate the opening deferred revenue balance (total cash received minus total revenue already recognised) and enter it in the Deferred Revenue b/fwd column.
- Choose the correct recognition method: Subscription contracts: straight-line over the contract period. Usage-based contracts: recognise as services are delivered (enter actual usage each month). Milestone contracts: recognise when the specific milestone is achieved (binary — 0 or full milestone amount). One-time setup fees: recognise when the distinct performance obligation (implementation) is complete, not when cash is received.
- Update monthly: At each month-end, (a) add new contracts signed in the month to the register, (b) update usage-based recognition for the actual usage delivered, (c) flag any cancellations or contract modifications, and (d) reconcile the closing deferred revenue balance to the accounting system.
- Reconcile to the balance sheet: The closing Deferred Revenue balance in the Bridge tab should equal the Deferred Revenue liability in your accounting system at each month-end. If they differ, the difference represents either a booking not yet recorded in the schedule or a journal entry that was posted directly to the balance sheet without going through the recognition schedule.
- Provide to auditors at year-end: This schedule, together with the signed contracts and invoices, forms the core of the revenue recognition audit file. Auditors will sample-test individual contracts, trace to invoices and bank receipts, and verify that the recognition method applied is consistent with the contract terms.
Frequently Asked Questions
What's the difference between MRR and recognised revenue?
MRR (Monthly Recurring Revenue) is a sales and operations metric: it represents the normalised monthly value of your contracted subscription base. It is not an accounting measure and does not follow GAAP or IFRS. Recognised revenue is an accounting measure: it represents the amount of revenue that has been earned in the period in accordance with IFRS 15. For a monthly subscription paid monthly, MRR and recognised revenue are the same. For an annual subscription paid upfront, MRR is one-twelfth of the annual contract value each month, and recognised revenue follows the same straight-line pattern — but the timing of cash collection is different. The gap between cash collected and recognised revenue is the deferred revenue balance.
How do I handle mid-contract upgrades?
Mid-contract upgrades (expansions) are one of the most common recognition complexities at growth-stage SaaS companies. Under IFRS 15, you need to determine whether the upgrade creates additional distinct performance obligations. In most cases, a seat upgrade or feature upgrade adds to the existing contract rather than creating a new one. The practical approach is to calculate the remaining value of the original contract plus the incremental value of the upgrade, and spread the combined amount over the remaining contract term. Update the Contract Register with the new total contract value and remaining term, and the Monthly Recognition Schedule will recalculate.
What about usage-based billing?
Usage-based revenue (variable consideration under IFRS 15) is recognised as services are delivered, not when invoiced. This means that if a customer uses £5,000 of API calls in July but you invoice monthly in arrears and the invoice goes out on 1 August, the £5,000 should be recognised in July as accrued income, and the invoice in August simply converts accrued income to a receivable. The key is to have reliable usage data from your platform systems that you can use to calculate the accrual at each month-end. For usage-billed contracts, enter the actual monthly usage amounts in the Monthly Recognition Schedule rather than a straight-line calculation.
