Are IFRS 15 and ASC 606 the same standard?

They are substantially converged but not identical. Both were developed jointly by the IASB and FASB and share the same five-step model. However, differences exist in areas like licensing, interim disclosures, collectability thresholds, and impairment of contract costs. For most SaaS companies, the practical outcome is very similar.

Which standard should a SaaS company follow?

It depends on jurisdiction and reporting framework. US-listed companies follow ASC 606 (US GAAP). Companies reporting under International Financial Reporting Standards — common in the UK, EU, Australia, and most other countries — follow IFRS 15. Dual-listed companies may need to comply with both.

How do the standards differ on licensing revenue?

ASC 606 distinguishes between licences that grant a 'right to access' IP (recognised over time) and a 'right to use' IP (recognised at a point in time). IFRS 15 uses the same distinction but the application guidance is less prescriptive, which can lead to different conclusions in borderline cases.

Do both standards require the same disclosures?

Annual disclosure requirements are largely aligned. The key difference is interim reporting: ASC 606 requires disaggregated revenue disclosures in interim periods, while IFRS 15 defers to IAS 34, which has less specific requirements. This means US GAAP quarterly filings tend to include more revenue detail.

Can Revnary handle both IFRS 15 and ASC 606?

Yes. Revnary applies the shared five-step model and produces recognition schedules that work under both standards. The straight-line allocation methodology is identical across IFRS 15 and ASC 606 for the vast majority of SaaS contracts.

IFRS 15 vs ASC 606: Comparison Guide for SaaS

Background: Two Standards, One Framework

IFRS 15 (Revenue from Contracts with Customers) and ASC 606 were developed jointly by the International Accounting Standards Board (IASB) and the Financial Accounting Standards Board (FASB). The goal was to create a single, converged revenue recognition model that would replace the fragmented guidance that previously existed under both US GAAP and IFRS.

Both standards became effective in 2018 and apply to all contracts with customers, regardless of industry.

The core five-step model is identical:

Identify the contract
Identify performance obligations
Determine the transaction price
Allocate the price
Recognise revenue

Where the standards diverge is in the application guidance and specific edge cases.

In practice: If your SaaS company sells straightforward subscriptions in a single jurisdiction, the standard you follow is determined by your reporting framework — and the day-to-day accounting will look the same either way.

Key Differences at a Glance

Area	ASC 606 (US GAAP)	IFRS 15
Licensing IP	Explicit guidance: 'right to access' (over time) vs 'right to use' (point in time)	Same distinction but less prescriptive application guidance
Variable consideration constraint	Include to extent 'probable' a significant reversal won't occur	Include to extent 'highly probable' a significant reversal won't occur — a higher threshold
Collectability threshold	If not probable, defer revenue until criteria met or contract terminated	If not probable, do not recognise a contract; reassess when circumstances change
Interim disclosures	Disaggregated revenue required in quarterly filings (ASC 270)	Defers to IAS 34 — less specific interim requirements
Contract cost impairment	Impairment tested at the contract level	Impairment tested at the 'unit of account' level, which can be broader
Non-cash consideration	Measured at fair value at contract inception	Measured at fair value at contract inception (converged)
Principal vs agent	Control-based model; consider 'who controls the good before transfer'	Same control-based model but additional indicators in application guidance

Licensing: The Biggest Practical Difference

For SaaS companies, the licensing distinction is the most frequently encountered divergence.

ASC 606: Provides explicit criteria to determine whether a licence grants a “right to access” the entity's IP (recognised over time, typical for SaaS) or a “right to use” it (recognised at a point in time, typical for on-premise software).
IFRS 15: Uses the same conceptual framework but with less prescriptive guidance, which can lead to different conclusions in borderline cases.

Practical impact for SaaS: Most SaaS arrangements reach the same conclusion under both standards — the subscription is a right-to-access licence recognised over time. But for hybrid models that combine hosted services with downloadable components, the analysis can diverge.

Variable Consideration

Both standards require entities to estimate variable consideration (e.g., usage overages, volume discounts, SLA credits) and include it in the transaction price subject to a constraint. The difference is in the probability threshold:

ASC 606: Include variable consideration to the extent it is “probable” (commonly interpreted as roughly 75%+ likelihood) that a significant reversal will not occur
IFRS 15: Uses “highly probable” (commonly interpreted as roughly 85%+ likelihood), a stricter threshold

In practice, this means IFRS reporters may recognise slightly less variable consideration upfront than their US GAAP counterparts for the same contract, with the difference caught up in later periods.

Principal vs Agent: Who Controls the Good?

When a SaaS company involves third parties in delivering services (e.g., marketplace models, reseller arrangements), both standards require the entity to determine whether it acts as principal (recognise gross revenue) or agent (recognise net commission).

Both use a control-based approach. Key indicators include:

Which party is primarily responsible for fulfilment
Which party bears inventory or credit risk
Which party has discretion over pricing

IFRS 15 includes additional indicators in its application guidance that can influence the conclusion differently in edge cases.

In practice: SaaS companies operating app-store or marketplace models should analyse this carefully under each standard, as gross vs net treatment can materially change reported revenue.

SaaS-Specific Implications

For the vast majority of straightforward SaaS subscription contracts, IFRS 15 and ASC 606 produce identical outcomes: revenue is recognised ratably over the subscription period. The differences become material in these scenarios:

Hybrid on-premise/cloud licensing arrangements
Significant variable consideration (usage-based with large volume tiers)
Marketplace or reseller arrangements requiring principal/agent analysis
Multi-element arrangements with distinct professional services
Contracts with significant financing components (long payment terms)

In practice: If every contract in your book is a fixed-price annual SaaS subscription, the standard you follow is unlikely to change your numbers. Focus your analysis time on the edge cases above.

Practical Compliance Tips

Know your reporting framework. US GAAP means ASC 606. IFRS means IFRS 15. Dual-listed companies should document where the two diverge.
Document your judgements. Both standards are principles-based. Auditors expect written accounting memos for significant arrangements.
Automate recognition schedules. Manual spreadsheets introduce errors, especially on contract modifications. Use a tool like Revnary to generate compliant schedules automatically.
Align with your auditor early. Discuss non-standard arrangements before year-end to avoid surprises and potential restatements.

IFRS 15 vs ASC 606: A Comparison Guide for SaaS

Key takeaways

Related tools & resources