Revenue Recognition: IFRS 15 vs ASC 606 Deep Dive

Are They Really Converged?

Short answer: Yes and no. IFRS 15 and ASC 606 were jointly developed by the IASB and FASB and use the same core five-step revenue recognition model. For most revenue contracts, the accounting is identical.

But. They differ on:

• How to account for contract modifications (the biggest source of difference)
• Licensing of intellectual property (software, royalties)
• Some transition guidance (mostly historical now)
• Application guidance in edge cases

These differences mean two companies with identical contracts — one reporting under IFRS, one under US GAAP — could recognise revenue at different times, or in different amounts. Auditors routinely challenge revenue on these points.

Reference: IFRS 15 paragraphs 1— 40; ASC 606-10-1 onwards.

The Five-Step Model (Identical)

Both standards use the same model:

1. Identify the contract with a customer (or group of customers)
2. Identify performance obligations (goods or services promised)
3. Determine the transaction price (contract consideration)
4. Allocate the transaction price to each obligation
5. Recognise revenue when (or as) each obligation is satisfied

The definitions and requirements are word-for-word identical. Performance obligations, control of goods/services, transaction price — all the same. The divergence comes in applying these principles to complex contracts.

Contract Modifications: The Biggest Difference

This is where IFRS 15 and ASC 606 diverge most. A contract modification is a change to the scope, price, or terms that was not in the original contract.

IFRS 15 Approach (Stricter)

IFRS 15 requires you to account for a modification as either:

• A separate contract (if the promised goods/services are distinct and the price reflects the entity's standalone selling price)
• A contract change (if goods/services are distinct but not at standalone selling price; adjusts the existing obligation)
• A modification of existing obligation (if goods/services are not distinct; adjusts the original obligation retroactively — can even require reversal of prior revenue)

The key: if the modification adds distinct goods/services at standalone selling price, it is a new contract. Otherwise, it changes the original contract.

ASC 606 Approach (More Liberal)

ASC 606 has similar rules but applies the "distinct goods/services" and "standalone selling price" tests with different application guidance. In practice, ASC 606 is more likely to treat a modification as a contract change (adjusting the existing contract) rather than a separate contract.

Audit implication: IFRS auditors will ask: Is this really a separate contract? Prove it has distinct goods and standalone price. US GAAP auditors are slightly more flexible — a contract change is acceptable even if the conditions are not quite met.

Worked Example: Contract Modification

Reference: IFRS 15 paragraphs 18— 0; ASC 606-10-25-12 onwards.

Licensing and Right-to-Use vs Right-to-Access

Both standards require you to distinguish:

Both IFRS 15 and ASC 606 use this distinction, but the language differs slightly. IFRS emphasises "control" (entity controls the IP and restricts customer use); ASC 606 emphasises "benefit" (customer accesses the IP over time).

In practice: Most SaaS contracts are right-to-access (revenue over time). Most perpetual licences are right-to-use (revenue at a point in time). Where they diverge: hybrid contracts (e.g., a licence with mandatory updates and support) — IFRS may call it right-to-access; ASC 606 might call it right-to-use.

Worked Example: Software Licence Classification

Reference: IFRS 15 paragraphs 31— 1; ASC 606-10-25-49 onwards.

Variable Consideration: Expected Value vs Most Likely

Both standards allow variable revenue (e.g., sales bonuses, discounts, rebates). You estimate variable consideration using either:

• Expected value: Probability-weighted average of all outcomes (IFRS or ASC)
• Most likely amount: Single most-likely scenario (IFRS or ASC)

Both standards say to use whichever is more predictive given the facts. In practice, both IFRS and ASC 606 reach the same estimates — there is no divergence here.

Constraint: Both standards require you to only include variable amounts that are not probable to reverse (IFRS) or are resolved within 12 months (ASC 606, with a 5% margin-of-safety test). This is where auditors challenge: if you are unsure about a bonus, don't include it.

Reference: IFRS 15 paragraphs 56— 8; ASC 606-10-32-5 onwards.

Transaction Price Allocation

Once you have the total transaction price (including variable amounts), you allocate it to each performance obligation based on their relative standalone selling prices.

IFRS 15 method: Allocate based on observable standalone selling price. If not observable, estimate using expected cost plus margin, or adjust market approach.

ASC 606 method: Identical. Use observable prices if available; estimate if not.

Difference: Both are the same. Auditors challenge on what qualifies as "standalone selling price" — does the volume discount that Customer A gets apply, or should you use list price? Both standards have similar answers: use what a customer would pay for that item separately.

Contract Costs and Asset Capitalization

Both standards allow you to capitalise costs to obtain a contract (e.g., sales commissions) or fulfil a contract (e.g., setup, installation, training).

IFRS 15: Capitalise if the cost is incremental and the entity expects to recover it. Amortise over the contract period.

ASC 606: Capitalize if the cost is incremental. Amortise over the contract period or expected customer life (if longer).

Practical difference: ASC 606 may allow longer amortisation periods (contract life vs expected customer life), which could defer costs. IFRS is stricter: amortise only over the contract you have.

Principal vs Agent Assessment

When you are an intermediary (e.g., marketplace, distributor), you must assess whether you are the principal (revenue = gross amount) or agent (revenue = commission only).

Both IFRS 15 and ASC 606 use the same test: Do you control the goods/services before they transfer to the customer?

Control indicators:

• You are responsible for fulfilling the obligation
• You have discretion over pricing
• You bear credit risk
• You can select the supplier

No divergence here — both standards reach the same conclusion in most cases.

Audit Implications and Red Flags

For auditors:

• Contract modifications: Challenge whether a modification is truly separate or a contract change. Request analysis of whether distinct goods/services are at standalone selling price. IFRS is stricter.
• Licensing: Verify right-to-use vs right-to-access classification. This drives timing — point-in-time vs over-time revenue. Software companies frequently misclassify.
• Variable consideration: Push back on aggressive estimates. If a bonus is uncertain, exclude it — both standards are clear.
• Standalone selling prices: Request evidence. Don't accept management estimates without benchmarking. This is a high-risk area.
• Contract costs: Verify capitalization is justified and amortization is over the correct period. Watch for over-amortization (IFRS stricter).

For controllers and CFOs:

• Document contract modifications carefully. Define whether the added items are distinct and at standalone price.
• Maintain pricing lists for standalone selling prices. Auditors will ask to see them.
• If you are IFRS, contract modifications are stricter — expect longer periods before revenue recognition.
• For SaaS and subscriptions, make sure you are not capitalizing things that should be expensed under both standards.

Frequently Asked Questions

This guide is simplified for educational purposes and does not constitute professional accounting advice. Actual IFRS 15 vs ASC 606 assessments depend on specific contract facts, facts patterns, and judgments. Auditors and preparers should consult the full text of IFRS 15 and ASC 606, and their own professional advisors, before finalising revenue accounting treatment. The article reflects IFRS Accounting Standards and US GAAP effective as of July 2026.

Real-Life Case Study: The Same Contract Under IFRS 15 and ASC 606