Key Takeaways
- Deferred revenue appears as a contract liability on the balance sheet until the entity delivers the promised goods or services.
- SaaS and subscription businesses routinely carry deferred revenue balances equal to 30% to 60% of annual revenue at any reporting date.
- Releasing deferred revenue too early overstates revenue and can trigger an audit qualification if the overstatement exceeds materiality.
- The balance must reconcile to underlying contracts, not just to cash received.
What is Deferred Revenue / Unearned Revenue?
IFRS 15.106 defines a contract liability as an entity's obligation to transfer goods or services to a customer for which it has already received consideration (or for which the amount is due). "Deferred revenue" and "unearned revenue" are presentation labels; the standard itself uses "contract liability." The substance is identical.
The mechanics are straightforward. When cash arrives before the performance obligation is satisfied, the entity credits a liability. As the entity delivers, it debits the liability and credits revenue. The auditor's job is to verify that the release pattern matches the actual transfer of control. ISA 315.25 requires the auditor to understand the entity's revenue recognition policies, including how management determines when a performance obligation is satisfied over time versus at a point in time. For deferred revenue, the risk of material misstatement sits primarily in the occurrence and cut-off assertions: did the entity release revenue only for obligations genuinely fulfilled before the reporting date?
The transaction price allocated to remaining performance obligations also triggers the IFRS 15.120 disclosure requirement, which means the auditor needs to reconcile the deferred revenue balance to the underlying contract population.
Worked example: O'Sullivan Tech Ltd
Client: Irish SaaS company, FY2025, revenue €8M, IFRS reporter. O'Sullivan sells a cloud-based compliance platform to mid-market audit firms across Europe. Annual subscription contracts run €24,000 per firm. Most subscriptions renew on 1 July. At 31 December 2025, O'Sullivan has 180 active annual contracts billed on 1 July 2025.
Step 1 — Calculate the deferred revenue balance at year-end
Each €24,000 annual subscription covers 1 July 2025 to 30 June 2026. At 31 December 2025, six months remain undelivered. Deferred revenue per contract: €12,000. Total deferred revenue from July-billed contracts: 180 × €12,000 = €2,160,000.
Documentation note: record the contract population (180 active subscriptions), billing date, subscription period, the straight-line basis for revenue release, and the resulting deferred revenue per contract.
Step 2 — Verify the release pattern
O'Sullivan recognises revenue on a straight-line basis over the subscription period (IFRS 15.B36 applies because the customer simultaneously receives and consumes the benefit of the platform access). The auditor selects a sample of 25 contracts and recalculates the monthly release for July through December 2025. All 25 match the general ledger postings within a rounding tolerance of €3 per contract.
Documentation note: record the sample size, selection method (random from the full contract population), the recalculation for each sampled contract, and the immaterial variance identified.
Step 3 — Test completeness of the liability
The auditor reconciles cash receipts for subscription invoices issued in June and July 2025 to the initial recognition of contract liabilities. Two contracts totalling €48,000 were invoiced on 28 June 2025 with service start dates of 1 July 2025. O'Sullivan recorded these as June revenue rather than deferred revenue. The auditor proposes a reclassification.
Documentation note: record the two misclassified contracts, the invoice dates, service start dates, and the proposed adjustment (debit revenue €48,000, credit contract liability €48,000). Add to the summary of uncorrected misstatements per ISA 450.A5 if management declines to adjust.
Step 4 — Evaluate disclosure
IFRS 15.120 requires disclosure of the transaction price allocated to remaining performance obligations. O'Sullivan's remaining obligation at 31 December 2025 is €2,208,000 (the corrected deferred revenue balance). The auditor confirms this figure appears in the revenue note with the expected recognition period (January to June 2026 for current contracts).
Documentation note: record the IFRS 15.120 disclosure check, the reconciliation of the deferred revenue balance to the remaining performance obligation disclosure, and confirmation of the expected recognition timeline.
Conclusion: the corrected deferred revenue balance of €2,208,000 is defensible because it reconciles to the underlying contract population, the straight-line release pattern reflects continuous service delivery, and the two misclassified contracts have been identified for adjustment.
Why it matters in practice
- The FRC's 2021/22 Annual Review of Corporate Reporting highlighted that entities frequently fail to reconcile their contract liability (deferred revenue) balances to the underlying contract population. IFRS 15.116(a) requires opening-to-closing reconciliation of contract liabilities, yet auditors on smaller engagements often test the balance by agreeing it to cash receipts alone without tracing through to the performance obligations.
- Teams sometimes apply a single release pattern to all deferred revenue without distinguishing between performance obligations satisfied over time and those satisfied at a point in time. A SaaS subscription (over time, per IFRS 15.35(a)) and a one-off software licence (point in time, per IFRS 15.38) sitting in the same deferred revenue account require different release triggers. ISA 540.13(a) requires the auditor to evaluate whether the entity's method for the accounting estimate is appropriate for the nature of the item.
Deferred revenue vs. accrued revenue
| Dimension | Deferred revenue (contract liability) | Accrued revenue (contract asset) |
|---|---|---|
| Cash timing | Cash received before performance | Performance completed before cash received |
| Balance sheet classification | Liability (obligation to deliver) | Asset (right to consideration for performance completed) |
| Revenue recognition trigger | When the entity satisfies the performance obligation | Already recognised; the asset awaits invoicing or payment |
| Audit risk focus | Premature release overstates revenue (occurrence, cut-off) | Failure to accrue understates revenue (completeness, cut-off) |
| Common industries | SaaS, media subscriptions, insurance premiums, construction advances | Construction (percentage-of-completion), consulting, long-term service contracts |
The two are mirror images. Deferred revenue asks whether the entity has earned what it already collected. Accrued revenue asks whether the entity has collected (or billed) what it already earned. On the same engagement, both balances can coexist when some contracts are prepaid and others are billed in arrears.
Related terms
Frequently asked questions
How do I audit deferred revenue on a SaaS engagement?
Reconcile the deferred revenue balance to the contract database. For each sampled contract, verify the billing date, the service start and end dates, and the monthly release calculation. IFRS 15.35(a) governs recognition over time when the customer simultaneously receives and consumes the benefit. Test both directions: confirm that revenue recognised in the period relates to obligations satisfied, and confirm that the remaining balance relates to obligations not yet fulfilled.
What is the difference between deferred revenue and a refund liability?
Deferred revenue represents an obligation to deliver goods or services. A refund liability under IFRS 15.55 represents an obligation to return cash to the customer (for example, under a right-of-return policy). Deferred revenue settles through performance. A refund liability settles through a cash payment or credit. Both appear as liabilities, but the underlying obligation differs.