ASC 606 vs IFRS 15: what's the difference?
ASC 606 and IFRS 15 share the same five-step revenue recognition model and were developed jointly by the FASB and IFRS Foundation. They differ in details: ASC 606 applies a stricter US GAAP collectibility threshold, includes explicit licensing implementation guidance, and requires more granular interim disclosures for public companies than IFRS 15 does.
Part of the revenue recognition guide.
| Standard setter | FASB (ASC 606) vs IFRS Foundation (IFRS 15) |
|---|---|
| Collectibility threshold | ASC 606 applies the US GAAP 'probable' definition; IFRS 15's threshold is comparatively lower |
| Licensing guidance | ASC 606 has explicit implementation guidance; IFRS 15 has less specificity |
| Interim disclosures | ASC 606 requires more granular interim disclosures for public companies |
Where do the two standards actually differ?
Not in the five-step model itself — in collectibility thresholds, licensing guidance, and disclosure requirements.
Does it matter which one my company uses?
Yes for disclosure and judgment calls; the underlying mechanics you build workflows around are the same.
Next step
Map the finance workflow with the most exposure and prove the automation path.
Bring the invoice, contract, payment reconciliation, or customer finance workflow you have to defend at audit. Loopfour can map the trigger, controls, integrations, and approval loop.
Worked example
Same contract, both standards
A $120,000 annual SaaS contract with a bundled onboarding service is split into two performance obligations under both standards using the same five-step model. The allocation math is identical; the two standards diverge only in disclosure granularity and the collectibility assessment made before recognition begins.
Frequently Asked Questions
Sources
Related
Definition
What is ASC 606 revenue recognition?
ASC 606 is the FASB standard for recognizing revenue when control of a good or service transfers to the customer, for the amount expected in exchange. It uses one five-step model: identify the contract, identify performance obligations, determine the transaction price, allocate that price, and recognize revenue as each obligation is satisfied.
Read moreHow-to
How do you calculate a contract's transaction price under ASC 606?
Transaction price is the consideration a company expects in exchange for goods or services. Start with the stated contract price, add variable consideration using the expected-value or most-likely-amount method, constrained to amounts unlikely to reverse, adjust for any significant financing component, then subtract noncash consideration and amounts payable to the customer.
Read moreIntegration
Which billing platforms support automated ASC 606 revenue recognition?
Stripe Billing, NetSuite, and Salesforce Revenue Cloud all offer native ASC 606 and IFRS 15 revenue recognition automation, generating deferred revenue schedules and recognition journal entries from contract and invoice data. Spreadsheet-based tracking has no native automation and carries meaningfully higher manual-error and audit risk as contract volume and complexity grow.
Read more