Foundations of Revenue Recognition

1. Why Revenue Recognition Matters

Revenue recognition is the single most audited, most restated, and most scrutinized area of financial reporting. Getting it wrong doesn't just cause accounting headaches — it drives board investigations, SEC enforcement actions, acquisition valuation disputes, and in extreme cases, fraud charges.

Why finance teams care

For SaaS and AI companies, revenue recognition isn't just a compliance checkbox. It has direct business consequences:

• Audit credibility: Auditors focus more time on revenue than almost any other line item. Strong documentation speeds audits and reduces costly adjustments.
• Board and investor confidence: Institutional investors and board members read your revenue recognition notes carefully. Unclear policies signal risk.
• M&A valuations: Buyers model future revenue based on your recognition policies. Companies with conservative, well-documented policies command higher multiples.
• Regulatory scrutiny: The SEC regularly issues comment letters on revenue recognition. For public or pre-IPO companies, the stakes are existential.
• Salesforce compensation: Sales commissions and quotas are often tied to recognized revenue — not bookings. Getting the timing wrong creates compensation disputes.

2. Evolution from Legacy Standards

To understand why IFRS 15 and ASC 606 were introduced, you need to understand what they replaced — and why the old standards were failing technology companies.

The old regime: IAS 18 and ASC 605

Before 2014, revenue recognition was governed by:

• IAS 18 (IFRS, international) — a principles-based standard with broad guidance but limited specificity
• ASC 605 (GAAP, US) — a rules-based patchwork of over 200 industry-specific pronouncements, SAB 104, and EITF consensus positions

The problem? Neither standard was designed for the subscription economy. By 2010, SaaS companies were signing multi-element contracts with software licenses, implementation services, training, and ongoing support — all bundled into a single deal. The old standards had no coherent framework for this.

The 2014 convergence

IASB (IFRS) and FASB (US GAAP) jointly published the new standards in May 2014. Both became effective for most public companies in 2018. The effort took nearly a decade and produced a single coherent model — the 5-step framework — applicable to virtually every revenue transaction across all industries.

3. The 5-Step Model Overview

The core of both IFRS 15 and ASC 606 is a five-step framework that applies to every revenue transaction. Each step must be addressed — in order — before revenue can be recognized.

4. Key Terminology

These eight terms form the core vocabulary of IFRS 15 and ASC 606. Understanding them precisely is essential for applying the 5-step model correctly.

Contract

An agreement between two or more parties that creates enforceable rights and obligations. Under ASC 606, not every signed document qualifies — 5 specific criteria must be met.

Performance Obligation

A promise to transfer a distinct good or service (or a series of distinct goods/services that are substantially the same) to a customer.

Transaction Price

The amount of consideration an entity expects to receive in exchange for transferring promised goods or services. Excludes amounts collected on behalf of third parties (e.g., sales tax).

Standalone Selling Price (SSP)

The price at which an entity would sell a promised good or service separately. Used as the basis for allocating the transaction price across multiple performance obligations.

Principal vs. Agent

A principal controls the good/service before transfer and recognizes gross revenue. An agent arranges for the transfer and recognizes only the net fee or commission.

Contract Modification

A change in the scope or price (or both) of a contract that is approved by both parties. Must be evaluated to determine whether it creates a new contract or modifies the existing one.

Deferred Revenue

A contract liability representing consideration received (or receivable) before performance obligations are satisfied. Common in SaaS for annual prepayments.

Over Time vs. Point in Time

Revenue from performance obligations satisfied progressively over a period (e.g., subscriptions, SLAs) is recognized over time. Obligations satisfied at a specific moment (e.g., delivering a license) are recognized at a point in time.

5. IFRS 15 vs. ASC 606: What's Actually Different

The two standards were designed to be identical. For SaaS and AI companies, the differences are almost never material to the revenue number itself. Here's a complete comparison:

6. SaaS & AI Scenarios: The 5-Step Model in Practice

Abstract principles become clear with concrete examples. Here are three common SaaS and AI contract structures and how the 5-step model applies to each.