Revenue Recognition is the accounting principle and framework for recognising revenue when control of goods or services transfers to the customer. The current standards are ASC 606 (US GAAP) and IFRS 15 (international), both based on the same five-step model that aligns revenue timing with the substance of the transaction.
Revenue is the top line of every income statement and the most-watched metric in financial reporting. When revenue is recognised affects when profits appear, when AR balances change, and when bad debt reserves need to be established. Revenue Recognition rules ensure that recorded revenue matches the economic substance of the underlying transaction rather than the timing of cash receipt or contract signing. Done correctly, recognition produces financial statements that reflect business reality. Done incorrectly, it produces misleading reports that can trigger restatements, audit issues, and in severe cases regulatory enforcement.
ASC 606 and IFRS 15 both follow the same five-step revenue recognition framework.
The model replaced industry-specific revenue rules with a single principles-based framework applicable across industries.
ASC 606 is the US GAAP standard issued by FASB; IFRS 15 is the international standard issued by IASB. Both were issued jointly in May 2014 (ASU 2014-09 and IFRS 15) with the same five-step model and largely converged guidance. Practical differences are limited to a few areas:
For most companies, the practical accounting under either standard produces the same revenue recognition timing and amount.
Identifying performance obligations is the most judgement-intensive step in the model. A performance obligation is a promise to transfer a distinct good or service to the customer. Distinct means:
Multi-element arrangements (a hardware sale bundled with installation and software) require splitting the contract into separate performance obligations and allocating the transaction price across them. SaaS contracts bundling subscription, implementation, and training raise the same allocation question.
Mistake 1: Treating contract signing as the trigger. Revenue is recognised when performance obligations are satisfied, not when the contract is signed. SaaS subscriptions are recognised ratably over the service period, not upfront.
Mistake 2: Missing variable consideration. Rebates, refunds, performance bonuses, and volume discounts are part of the transaction price and reduce revenue. Failing to estimate them at recognition time leads to subsequent restatements.
Mistake 3: Inadequate documentation of judgement. The five-step model is principles-based and requires significant judgement. Audit and SOX controls require documented evidence of how each step was applied.
Mistake 4: Ignoring contract modifications. Contract amendments may create new performance obligations or change existing ones. The accounting treatment varies by whether the modification is a new contract, a separate modification, or a prospective change.
Revenue recognition affects AR in three important ways:
For finance teams, revenue recognition and AR management are tightly coupled, and policy changes in one often require corresponding changes in the other.
Revenue Recognition is the accounting principle and framework for determining when and how much revenue to record. Under ASC 606 (US GAAP) and IFRS 15 (international), revenue is recognised when control of goods or services transfers to the customer, following a five-step model that aligns revenue timing with the substance of the transaction.
The five steps: identify the contract with a customer, identify the performance obligations, determine the transaction price, allocate the transaction price to the performance obligations, and recognise revenue when each performance obligation is satisfied. The same model applies under IFRS 15.
ASC 606 is the US GAAP standard issued by FASB; IFRS 15 is the international standard issued by IASB. They were issued jointly in 2014 with the same five-step model and largely converged guidance. Practical differences are limited (slightly different collectibility threshold expression, more extensive ASC 606 disclosures, slightly different effective dates). For most companies, both standards produce the same revenue recognition timing and amount.
Revenue recognition timing creates AR. Revenue recognised before cash collection appears as AR until paid. Subscription businesses with annual prepayment have low AR; project-based businesses with milestone billing have higher AR. The allowance for doubtful accounts matches expected bad debt to the revenue recognition period.
A performance obligation is a promise in a contract to transfer a distinct good or service to the customer. Distinct means the customer can benefit from the good or service on its own and the promise is separately identifiable from other contract promises. Multi-element arrangements (e.g., hardware plus installation plus software) require splitting the contract into separate performance obligations and allocating the transaction price across them.
ASC 606 was issued in May 2014 (ASU 2014-09) and became effective for public companies for fiscal years beginning after December 15, 2017, and for private companies one year later. IFRS 15 became effective for periods beginning on or after January 1, 2018. Both standards replaced industry-specific revenue rules with a single principles-based framework.
