Revenue Recognition: IFRS 15 vs ASC 606 Deep Dive

Are They Really Converged?

Short answer: more converged than almost anything else in the two frameworks. IFRS 15 and ASC 606 were drafted jointly and issued as a single agreed model. The five steps, the definition of control, the constraint on variable consideration and the contract modification guidance are the same requirements, and in several places the same words.

It is worth being explicit about that, because two claimed differences circulate widely and neither is real. Contract modification guidance is identical in IFRS 15.18 to .21 and ASC 606-10-25-10 to 25-13. And the variable consideration constraint is the same test; there is no ASC 606 twelve-month resolution rule and no percentage safe harbour.

The differences that do exist are narrower and mostly sit outside the recognition model:

• Collectibility in Step 1. Both require collection to be probable, but probable means more likely than not under IFRS and likely to occur under US GAAP. A marginal-credit customer can pass Step 1 under IFRS and fail it under ASC 606, which changes when a contract exists at all.
• Licensing. ASC 606 uses a functional and symbolic intellectual property taxonomy, plus a specific rule on the timing of licence renewals. IFRS 15 reaches broadly the same answers through the right to use and right to access analysis, but the renewal timing can differ.
• Shipping and handling. ASC 606-10-25-18B gives a policy election to treat activities after control passes as a fulfilment cost. IFRS 15 has no equivalent.
• Sales taxes. ASC 606-10-32-2A allows presentation net of all taxes collected from customers. Under IFRS the entity assesses each tax on principal versus agent principles.
• Non-cash consideration. US GAAP fixes the measurement date at contract inception. IFRS 15 does not specify one.
• Contract cost impairment. IFRS 15.104 requires reversal when the conditions causing the impairment no longer exist. ASC 340-40-35-6 prohibits reversal outright.
• Disclosure and reliefs. ASC 606 carries interim disclosure requirements and a set of reliefs for non-public entities that have no IFRS counterpart.

So two companies with identical contracts can still land in different places, but usually because of Step 1 collectibility, a licence renewal, or a contract cost reversal, not because of the core model.

Reference: IFRS 15.9(e), .18 to .21, .56 to .58, .104, B52 to B63; ASC 606-10-25-1(e), 25-10 to 25-13, 25-18B, 32-2A, 32-11, 55-58C, 55-60 and 55-62; ASC 340-40-35-6.

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: Identical Rules, Three Outcomes

A contract modification is an approved change to the scope or price of a contract. This is often written up as the main IFRS versus US GAAP difference. It is not one. IFRS 15.18 to .21 and ASC 606-10-25-10 to 25-13 impose the same requirements, so the analysis below applies unchanged under both.

What makes modifications hard is not a framework difference, it is that one set of rules produces three quite different answers depending on two questions: are the additional goods or services distinct, and is the additional price at standalone selling price.

The three outcomes

• Separate contract (IFRS 15.20). Both conditions met: the additional goods or services are distinct, and the price increase reflects their standalone selling price. Account for the modification entirely separately and leave the original contract alone. No adjustment to revenue already recognised.
• Termination and new contract, accounted for prospectively (IFRS 15.21(a)). The remaining goods or services are distinct from those already transferred, but the pricing condition fails. Treat the existing contract as terminated. The consideration still to be recognised, plus the modification consideration, is allocated across the remaining performance obligations. No catch-up.
• Continuation of the existing contract, with a cumulative catch-up (IFRS 15.21(b)). The remaining goods or services are not distinct and form part of a single performance obligation that is only partially satisfied. Update the measure of progress and take the adjustment to revenue immediately, which can increase or decrease revenue already recognised.

Where auditors actually push

Since the rules are the same, the challenge under both frameworks is the same: is the additional price genuinely at standalone selling price, and are the remaining goods or services genuinely distinct in the context of the contract. Neither standard permits separate-contract treatment where the conditions are not met, and no auditor under either framework should accept it.

Worked Example: Contract Modification

Reference: IFRS 15.18 to .21; ASC 606-10-25-10 to 25-13.

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.B52 to B63, particularly B58, B59A and B61; ASC 606-10-55-54 onwards, 55-60 (symbolic IP), 55-62 (functional IP), 55-58C (renewals).

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.

The constraint is the same test in both standards. Variable consideration is included in the transaction price only to the extent that it is highly probable (IFRS 15.56) or probable (ASC 606-10-32-11) that a significant reversal of cumulative revenue recognised will not occur when the uncertainty is subsequently resolved. The two words differ because each framework uses its own existing vocabulary, and the boards recorded in the Basis for Conclusions that the intended threshold is the same.

What the standards do give you is a list of factors that increase the likelihood of a significant reversal, at IFRS 15.57 and ASC 606-10-32-12: susceptibility to factors outside the entity's influence, a long period before the uncertainty resolves, limited experience with similar contracts, a practice of offering concessions, and a broad range of possible outcomes. That list, not a percentage, is what a challenge should be argued against.

One genuine exception sits alongside the constraint and is the same in both: sales-based and usage-based royalties on licences of intellectual property are recognised as the sales or usage occur, regardless of the constraint analysis.

Reference: IFRS 15.53 to .58, .B63; ASC 606-10-32-5 to 32-14, 55-65; IFRS 15 Basis for Conclusions BC203 to BC213.

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).

Recognition and amortisation are the same under both. Incremental costs of obtaining a contract are capitalised if the entity expects to recover them, with a practical expedient in both standards to expense them as incurred where the amortisation period would be one year or less. Both amortise on a systematic basis consistent with the transfer of the goods or services to which the asset relates, and both expressly contemplate that this period can extend beyond the current contract to anticipated renewals where the asset relates to them. IFRS is not stricter on this point, and the commission on a SaaS contract with expected renewals is amortised over the expected customer relationship under IFRS 15.99 just as it is under ASC 340-40.

The real difference is impairment reversal, and it is absolute. Where the conditions that caused an impairment of a contract cost asset no longer exist or have improved, IFRS 15.104 requires the impairment to be reversed, capped at the carrying amount that would have applied had no impairment been recognised. ASC 340-40-35-6 prohibits reversal entirely. So a contract that deteriorates and then recovers leaves a permanently lower asset under US GAAP and a restored one under IFRS.

Reference: IFRS 15.91 to .104; ASC 340-40-25-1 to 25-4, 340-40-35-1, 340-40-35-6.

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?

There are three indicators, and only three. They are the same in both standards:

• Primary responsibility for fulfilling the promise. Who is on the hook to the customer if the goods or services are not acceptable?
• Inventory risk. Does the entity hold the inventory before transfer, or take it back on return?
• Discretion in establishing the price. Can the entity set what the customer pays?

The indicators support the control assessment, they do not replace it and they are not a checklist to be scored. The question remains whether the entity obtains control of the specified good or service before it transfers to the customer. On this, IFRS 15 and ASC 606 genuinely do not diverge.

Reference: IFRS 15.B34A to B37A; ASC 606-10-55-36A to 55-39A; ASU 2016-08; Clarifications to IFRS 15 (April 2016).

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

About the author — Usman Qureshi (ACCA)

Usman Qureshi is a Chartered Certified Accountant (ACCA) working in audit and advisory. He writes on IFRS 15 and ASC 606 revenue recognition.

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