é É « » à è ù ç ô é
Deferred revenue: definition, recognition and audit risks
‹ Go back | Glossary

Deferred revenue: definition, recognition and audit risks

What is Deferred Revenue?

Deferred revenue is cash received from a customer before the related goods or services have been delivered, recorded as a liability until the performance obligation is satisfied. Despite sitting in the bank account, the money is not yet income: it represents an obligation to deliver, and recognising it early is one of the most common forms of revenue misstatement.

How deferred revenue is recognised

Under IFRS 15 and ASC 606, revenue is recognised when control of a good or service transfers to the customer. Cash received ahead of that point is recorded as a contract liability and released to revenue as the obligation is satisfied, either over time or at a point in time depending on the arrangement.

Subscription businesses illustrate the mechanics. An annual contract paid upfront creates a liability released in twelve monthly instalments. Multi-element contracts complicate this considerably: a package combining software, implementation, and support requires the price to be allocated across distinct obligations, each with its own recognition pattern.

Audit risks around deferred revenue

The core risk is premature recognition, releasing the liability before delivery to improve a period's results. The pressure is highest at year end, which is why cut-off testing around the reporting date is a standard procedure.

Other recurring findings involve allocation judgement in bundled contracts, deferred revenue balances that never move because the underlying obligation was never tracked, and manual reclassification entries that shift amounts between deferred revenue and recognised revenue without a documented trigger.

Deferred Revenue and Supervizor

Deferred revenue balances tie accounting entries to contractual obligations, and the connection is rarely tested at scale. Supervizor's finance transformation solution examines the full population of entries. Teams use it to:

  • Test revenue cut-off around period end to detect early recognition against delivery dates
  • Identify stale deferred balances that have not moved in line with the underlying contract term
  • Flag manual reclassifications between deferred and recognised revenue that lack documented support

Related Supervizor pages