What is Revenue Recognition (ASC 606 / IFRS 15)?
The accounting rules that determine when and how much revenue a company can record from its contracts with customers.
Definition
Revenue recognition governs the timing of recording revenue so that it reflects when goods or services are actually delivered to the customer, not simply when cash is received or an invoice is raised. The converged standards ASC 606 (US GAAP) and IFRS 15 use a five-step model: identify the contract, identify the performance obligations, determine the transaction price, allocate the price to the obligations, and recognise revenue as each obligation is satisfied. This matters most for subscriptions, bundled deals, long-term projects, and multi-element arrangements where cash and delivery diverge. Misapplying these rules is a frequent source of restatements, so automation and auditability are critical.
How Revenue Recognition Works in ERP
An ERP with revenue management identifies performance obligations on each contract, allocates the transaction price across them, and builds revenue schedules that release revenue over time or at a point in time. It posts the recognised revenue to the general ledger and parks the rest in deferred revenue, keeping billing and recognition separate. The system handles contract modifications, variable consideration, and produces audit-ready waterfall and disclosure reports.
ERP Vendors with Strong Revenue Recognition
Frequently Asked Questions
What is the five-step model under ASC 606 and IFRS 15?
The five steps are: identify the contract with the customer, identify the distinct performance obligations in it, determine the transaction price, allocate that price to each obligation, and recognise revenue as each obligation is satisfied. The model focuses on transferring control of goods or services to the customer. It applies across industries and replaced a patchwork of older, industry-specific rules. ERPs build this logic into their revenue management modules so the steps are applied consistently.
Why can't a company just recognise revenue when it invoices the customer?
Invoicing and earning revenue are different events. If a customer pays a year of subscription up front, the cash and invoice arrive immediately but the service is delivered over twelve months, so revenue must be recognised monthly as the obligation is met. Recording it all at once would overstate current results and misrepresent performance. The ERP separates billing from recognition, holding unearned amounts in deferred revenue until they are earned.