Revenue recognition (IFRS 15 / ASC 606): the CFO's practical guide

The 5-step model, in CFO language

Every revenue transaction now runs through the same five steps:

1. Identify the contract with the customer (it can be written, oral, or implied, and collectibility must be probable)

2. Identify the performance obligations, the distinct promises in that contract

3. Determine the transaction price, including variable consideration, financing components, and non-cash payments

4. Allocate the transaction price to each performance obligation based on standalone selling prices

5. Recognize revenue when (or as) each performance obligation is satisfied

The seductive simplicity of the framework hides where the real work lives: Steps 2 and 4. Most restatements and SEC comment letters since 2018, including the 2023 enforcement action against GTT Communications ($25 million SEC settlement for improperly bundled performance obligations), have hinged on whether obligations were truly "distinct" and how transaction price was allocated.

Case study one: boeing, the 737 MAX, and the long tail of "over time" revenue

In March 2019, the 737 MAX was grounded worldwide. Boeing had a backlog of over 4,400 aircraft. Under IFRS 15 / ASC 606, Boeing recognizes commercial aircraft revenue at a point in time, specifically, when control transfers to the airline at delivery. That single accounting choice meant the grounding didn't just hurt earnings; it created a cascade of revenue recognition problems that the company is still unwinding in 2026.

Here's what made Boeing's situation a masterclass in 606 complexity:

Customer concessions as variable consideration. Boeing offered airlines billions in concessions, credits, and penalty payments for delays. Under Step 3, variable consideration must be estimated and constrained, you can only include it in the transaction price to the extent it's "highly probable" (IFRS 15) or "probable" (ASC 606) that a significant reversal won't occur. CFO Brian West, who joined Boeing in 2021, had to constantly re-estimate these concessions as the situation evolved. Each estimate change flowed to the income statement.

Contract modifications. When the MAX grounding forced re-deliveries, delivery slot swaps, and order conversions (737 MAX 8 to MAX 10, for instance), each change had to be assessed: was this a modification of the existing contract, a new contract, or a termination? The accounting answer dictated the revenue timing. By Boeing's 2024 10-KKThe average number of new users each existing user generates through referrals. Above 1.0, growth compounds on itself and becomes exponential.View full definition →, the company disclosed over $5 billion in customer concession liabilities still working through the income statement.

The deferred revenue cliff. Boeing's contract liabilities (advance payments from airlines) ballooned to over $50 billion. Under 606, those balances only convert to revenue at delivery. When the second grounding event hit in January 2024 after the Alaska Airlines door plug incident, the deferred revenue runway extended yet again.

The CFO lesson: If you sell long-cycle products, your point-in-time vs. over-time judgment is the most consequential 606 decision you'll make. It determines whether a black swan event hits you instantly or grinds through your P&L for half a decade.

Case study two: Salesforce, multi-element SaaS, and the SSP problem

Now flip the industry. Salesforce sells a typical enterprise deal that might include: a three-year subscription to Sales Cloud, professional services for implementation, training credits, premium support, and a discounted add-on to Marketing Cloud activating in year two. That's potentially five performance obligations in a single contract worth, say, $4.8 million.

Under ASC 606, Salesforce has to:

1. Determine which obligations are "distinct." Is implementation distinct from the SaaS subscription, or so integrated that they're a single obligation? Salesforce, like most SaaS companies, generally concludes implementation is distinct (it can be, and often is, performed by third parties like Accenture or Deloitte).

2. Establish a Standalone Selling Price (SSP) for each. This is where the real work lives. Salesforce maintains a rigorous SSP analysis using observable prices when available, and an "expected cost plus margin" or "residual approach" when not. The SSP work isn't a one-time setup, it's a quarterly governance process, because pricing patterns shift.

3. Allocate the $4.8M based on relative SSP. If the SaaS subscription's SSP is $5M but the customer is paying $4M for it (a discount), the discount must be allocated proportionally, unless the company can demonstrate the discount relates to specific obligations.

4. Recognize each obligation appropriately. Subscription revenue: ratably over the service period. Implementation: as performed. Training credits: as used or when they expire (breakage). The premium support: ratably.

In Salesforce's FY2025 10-KKThe average number of new users each existing user generates through referrals. Above 1.0, growth compounds on itself and becomes exponential.View full definition →, the company reported $37.9 billion in revenue with $30.5 billion in remaining performance obligations (RPO), the metric that 606 made famous. RPO is now the leading indicator analysts use for SaaS, because it captures contracted-but-unrecognized revenue.

The CFO lesson: In SaaS, your CRMCRMCustomer Relationship Management: software and strategy to manage and analyse customer interactions throughout their lifecycle.View full definition →/CPQ system, your billing system, and your revenue subledger must speak the same language as your contracts. The companies that struggled with 606 in 2018, and are still struggling in 2026, are those whose contract data lives in five systems with three definitions of "start date."

The principal vs. agent trap

One more 606 landmine that has bitten companies repeatedly: principal vs. agent (gross vs. net revenue). Groupon famously had to restate its IPO-era revenue from gross to net, cutting reported revenue by more than half. The 606 test is whether you "control" the good or service before transferring it to the customer. In 2024, the SEC opened inquiries into several embedded fintech and marketplace companies on this exact point. If you're a CFO at a platform, marketplace, or reseller, this is the question that determines whether you're a $1B revenue company or a $200M revenue company, same economics, very different valuation multiples.

What a CFO actually does on monday morning

The standard is the standard. The question is how you operationalize it. Here's what separates CFOs who sleep well from those who get the 3 AM call from the audit partner:

1. own the contract review process

In every well-run finance organization in 2026, no material new contract template, and no significant non-standard amendment, gets signed without revenue accounting review. At companies like Adobe and ServiceNow, deal desks are jointly staffed by sales operations and revenue accounting. A non-standard term like "termination for convenience with 30-day notice" can convert a three-year subscription into a series of one-month contracts for accounting purposes, destroying the revenue profile you promised investors.

2. build a defensible SSP methodology

Your SSP file should be a living document, refreshed at least annually, with clear documentation of:

• Observable price evidence
• Pricing tiers and discount patterns
• The methodology when no observable price exists
• The "corridor" of acceptable prices

When the SEC or your auditor challenges allocation, and in 2026, with AI-driven audit tools at firms like PwC and EY flagging anomalies faster than ever, your SSP file is your defense.

3. master your variable consideration

Rebates, volume discounts, performance bonuses, penalties, refund rights, all of these are variable consideration. The constraint principle requires you to estimate the amount you expect to keep, not the maximum possible. Companies that load the income statement with optimistic variable consideration estimates are the ones that restate. Use either the expected value method (probability-weighted) or most likely amount method consistently, and document why you chose each.

4. get your disclosures right

606 brought disaggregated revenue disclosures, RPO disclosures, contract balance roll-forwards, and significant judgment disclosures. In 2026, these disclosures interact with the new CSRD sustainability reporting in Europe and SEC climate disclosures in the US, companies are increasingly being asked to disaggregate revenue by sustainable activity, geography, and timing of transfer simultaneously. Your disclosure controls should be reviewed annually, not built once in 2018 and forgotten.

5. know where 606 meets pillar two

Here's a 2026-specific issue most CFOs underestimate: OECD Pillar Two (the 15% global minimum tax) uses financial accounting income as its starting point. That means your 606 judgments, when revenue is recognized, in which entity, allocated to which performance obligation, now directly affect your global tax bill. A revenue allocation that shifts $50M from Year 1 to Year 2 between a Singapore subsidiary and a US subsidiary could change your top-up tax materially. Tax and revenue accounting are no longer separate workstreams.

Key takeaways: the CFO's action checklist

1. Audit your performance obligation inventory this quarter. Pull your ten largest contract templates and walk through Steps 1-5 with your controller and revenue accounting lead. If you can't articulate the distinct obligations and SSPs in 90 seconds per contract type, your team can't either. This is the single highest-ROIROIReturn on Investment: the ratio of net profit to the cost of an investment. A 300% ROI means each dollar invested returns $3.View full definition → exercise in revenue ass