What are the differences between IFRS 15 and ASC 606?

IFRS 15 vs ASC 606 — Core Rule

Both IFRS 15 and ASC 606 use the same five-step revenue recognition model (identify contract, performance obligations, transaction price, allocation, and recognition), but critical differences exist in performance obligation definition, contract modifications, collectability assessment, and presentation that can materially impact reported revenue and working capital.

How IFRS 15 vs ASC 606 Works

• Performance obligations and control transfer: IFRS 15.27 defines a performance obligation as a promise to transfer a "distinct" good or service. ASC 606-10-25-19 uses the same concept but ASC 606 applies a narrower definition of "distinct" in the context of goods and services. Under IFRS 15, a performance obligation must be separately identifiable in the contract and from the customer's perspective represent a separately deliverable item. Under ASC 606, the guidance focuses more heavily on whether the customer can benefit from the good or service either on its own or with readily available resources.

• Contract modifications: IFRS 15.20–21 treats contract modifications as part of the original contract if they do not create a separate performance obligation, versus ASC 606-10-25-12 which requires a more prescriptive assessment of whether a modification creates a separate contract or is a continuation. Under IFRS 15.21, modification proceeds are allocated to remaining performance obligations using the original standalone selling price unless the modification adds distinct goods/services at a different price (in which case the new price applies). ASC 606 permits an entity to account for the modification as a termination of the existing contract and creation of a new contract if the remaining goods/services are materially different from those in the original arrangement.

• Collectability and revenue recognition: IAS 15.38 states that revenue is recognized when (or as) a performance obligation is satisfied, contingent on the entity having a "contract" (IFRS 15.9 defines this as an agreement with commercial substance and probable consideration). ASC 606-10-25-1(a) also requires "probable" consideration but adds an explicit criterion that the customer must have the ability and intent to pay (ASC 606 effectively raises the bar on customer creditworthiness at the outset). IFRS 15 does not explicitly require an upfront collectability assessment; instead, collectability is tested at contract inception (IFRS 15.37), and subsequent impairment of receivables is handled under IFRS 9 (separate from revenue recognition).

• Presentation and timing: IFRS 15.B3–B4 permits presentation of revenue gross (principal) or net (agent) depending on whether the entity controls the good/service before transfer to the customer. ASC 606-10-25-45 uses similar language but interpretive guidance (ASC 606-10-55-36 to 55-40A) has developed a more prescriptive agent test. Both standards require similar disclosures, but IFRS 15 Appendix B provides more narrative guidance on contract modification, while ASC 606 separates this into codified paragraphs.

• Practical differences in contract estimates: IFRS 15.24 requires the transaction price to reflect the entity's best estimate of consideration expected to be entitled to, using either the expected value method or most likely amount method. ASC 606-10-32-3 uses identical wording, but U.S. practice often applies more conservative expected value calculations upfront. IFRS practice may defer adjustments to variable consideration until recognition is highly probable (IFRS 15.56).

IFRS 15 vs ASC 606 — Practical Example

A software company enters into a three-year license agreement with a customer for €3,000,000 (€1,000,000 per year) bundled with implementation services (€500,000). Under both IFRS 15 and ASC 606, the entity must identify two performance obligations: the license (transferred over time) and implementation (transferred at a point in time, Day 30).

IFRS 15 approach

The entity allocates price based on standalone selling prices: license €2,400,000 (80% of total), implementation €600,000 (20% of total).

ASC 606 approach

Under ASC 606, the same allocation typically applies, but the entity must satisfy an explicit collectability test at contract inception. If the customer has a weak credit profile, ASC 606 permits deferral of revenue recognition until the performance obligation is satisfied and collectability becomes probable (ASC 606-10-32-3). Under IFRS 15, this collectability question is resolved separately through IFRS 9 impairment.

IFRS 15 vs ASC 606 — Common Pitfalls

• Collectability timing: Many practitioners apply IFRS 15 without performing upfront collectability screening, leading to revenue recognition on contracts with doubtful debtors. ASC 606 explicitly requires this assessment at contract inception; IFRS 15 does not, creating a pitfall for cross-GAAP reporters. Audit firms often flag this in dual-reporting environments.

• Contract modification scope: IFRS 15 and ASC 606 diverge on scope changes. A customer requesting a 10% scope increase at the original unit price must be treated as a modification under IFRS 15 (allocated to remaining obligations), but under ASC 606 it may qualify as a separate contract if the goods/services are materially different. This creates different revenue timing and working capital effects.

• Principal vs. agent: The definitions are nearly identical, but ASC 606's interpretive guidance (particularly around customer options and return rights) is more prescriptive. Entities applying IFRS 15 may incorrectly claim principal status on distributor arrangements where ASC 606 would require agent accounting due to customer control of returns or pricing.

IFRS 15 vs ASC 606 — Key Paragraphs

• IFRS 15.27–28 (performance obligation definition and distinctness)
• IFRS 15.20–21 (contract modifications)
• IFRS 15.37–38 (contract and revenue recognition criteria)
• ASC 606-10-25-1 (contract requirements and collectability)
• ASC 606-10-25-12 (contract modification accounting)
• ASC 606-10-25-45 to 25-47 (principal vs. agent)