Are ASC 606 and IFRS 15 the same? Where the two revenue standards still differ

ASC 606 and IFRS 15 are not the same, but they are close. The FASB and the IASB issued them together in May 2014 with the same core principle and the same five-step model, so most contracts produce the same revenue under both. The differences sit at the edges: the collectibility threshold, licenses of intellectual property, a handful of US-only policy elections, contract-cost impairment reversals, onerous contracts, and disclosures.

For a single-GAAP company, those edges rarely matter. For a dual-reporting team (a US subsidiary of a European parent, or an IFRS group with a US GAAP lender package), they decide whether one revenue schedule can serve both books. This comparison maps every difference that matters, cites the standards, and shows how to run both without a spreadsheet war.

Key takeaways

• ASC 606 and IFRS 15 share the same five-step model and core principle, so most contracts produce the same revenue under both.

• Collectibility is the most consequential day-one difference: "probable" means likely to occur under US GAAP, but more likely than not under IFRS, so a contract can exist under IFRS 15 and fail step one under ASC 606.

• US GAAP offers policy elections IFRS 15 does not: shipping and handling as a fulfillment cost, and excluding sales taxes from the transaction price.

• IFRS 15 requires reversing contract-cost impairments when conditions improve; ASC 340-40 prohibits it. IFRS also carries onerous-contract provisions under IAS 37.

• Licensing guidance differs in structure: ASC 606 classifies IP as functional or symbolic, while IFRS 15 asks whether the entity's activities significantly affect the IP.

• Loopfour, the deterministic finance workflow automation platform, runs one contract-data workflow that feeds both books, with each GAAP difference encoded as an approved rule, not a manual adjustment.

Are ASC 606 and IFRS 15 the same?

No. ASC 606 and IFRS 15 are substantially converged but not identical. Both require you to identify the contract, identify performance obligations, determine the transaction price, allocate it, and recognize revenue as obligations are satisfied. The wording of most requirements is the same, word for word.

The divergence came in two waves. The original 2014 standards differed in a few places, such as the definition of "probable." Then, when the boards amended their standards in 2016 after the Transition Resource Group discussions, they did not always make the same amendments. The FASB added more implementation guidance and more practical expedients; the IASB made fewer changes. The FASB's own comparison document catalogs the resulting differences. If you need the model itself first, start with what ASC 606 is and how its five steps work.

ASC 606 vs IFRS 15: the comparison table

The table below lists the differences a finance team is most likely to meet in practice. Items marked as US-only elections are optional under ASC 606 and unavailable under IFRS 15.

Where do ASC 606 and IFRS 15 differ most in practice?

For most SaaS and services companies, four differences do the real damage: collectibility, licenses, contract-cost impairment, and disclosures. The rest are elections you set once or edge cases you rarely meet. Here is each of the four in more detail.

Collectibility: the same word with two meanings

Both standards require that it be "probable" you will collect the consideration before a contract exists, but "probable" is defined differently. Under US GAAP, probable means "the future event or events are likely to occur," a threshold practitioners generally read as well above 50%. Under IFRS, probable means more likely than not.

The practical effect is a timing gap. A new customer with a thin credit file can have a valid contract under IFRS 15 while failing step one under ASC 606. Under ASC 606, cash received from that customer sits as a liability until one of three events in ASC 606-10-25-7 occurs. The third event, added by ASU 2016-12, lets you recognize the cash as revenue once you have transferred control of the goods or services to which it relates, stopped transferring further goods or services, and have no obligation to transfer more, provided the cash received is nonrefundable. IFRS 15 has no equivalent third event.

Licenses of intellectual property

ASC 606 sorts licenses into functional IP (such as software) and symbolic IP (such as a brand), while IFRS 15 asks whether your ongoing activities significantly affect the IP the customer has rights to. Functional IP licenses are usually recognized at a point in time under ASC 606. Symbolic IP licenses are always recognized over time.

The two tests usually agree. They diverge on edge cases, such as a brand license where the licensor no longer carries out any activities that support the brand: ASC 606 still recognizes it over time, while IFRS 15 can treat it as a right to use recognized at a point in time. ASC 606 also says revenue from a license renewal cannot be recognized before the renewal period begins, which IFRS 15 does not state explicitly. For a SaaS company that sells hosted access, this rarely bites, because hosted access is usually a service, not a license.

Contract costs: impairment and reversal

Both standards capitalize incremental costs of obtaining a contract, such as sales commissions, and both test those assets for impairment. The difference is what happens after an impairment. ASC 340-40 prohibits reversing an impairment loss. IFRS 15 requires a reversal when the impairment conditions no longer exist, capped at the carrying amount the asset would have had.

Over a few years, that single rule produces different contract-cost asset balances in the two books for any company that impaired capitalized commissions during a downturn.

Disclosures, including interim

US public entities disclose more in their interim reports. Under US GAAP, public entities provide disaggregated revenue, contract balances, and remaining performance obligation information in interim statements. IAS 34 requires disaggregated revenue in interim reports under IFRS.

Nonpublic US entities can elect to omit several annual disclosures, including the quantitative remaining performance obligation disclosure. IFRS 15 has no private-company relief. A privately held US subsidiary of an IFRS parent therefore often prepares IFRS disclosures for group reporting that it never needs for its own US GAAP statements.

What a dual-reporting finance team should do

A dual-reporting team should keep one set of contract data, one set of step-one-to-step-five judgments, and a short, documented list of GAAP-specific adjustments. The goal is that the only differences between the two ledgers are the ones in the table above, each traceable to a rule.

→ Map your elections once. Decide your US policy elections (shipping and handling, sales taxes, practical expedients) and document the IFRS treatment for each. Store both in your revenue policy memo.

→ Tag contracts that sit on a difference. Collectibility-constrained customers, IP licenses, noncash consideration, and acquired contracts should carry a flag at contract creation.

→ Run one schedule, then derive the adjustment. Build the revenue schedule once. Post the GAAP difference as a separate, labeled adjustment in the secondary book or ledger.

→ Reconcile the two books every close. The reconciliation between IFRS revenue and US GAAP revenue should equal the sum of flagged adjustments. Anything else is an error.

NetSuite Multi-Book Accounting and similar ERP features let you post to a secondary accounting book. The ERP stores the numbers, but it does not decide which contracts need an adjustment. That decision needs contract-level data flowing reliably from your CRM and e-signature tools, which is where most dual-GAAP breaks start. Our guide to integration approaches for multi-entity and multi-subsidiary finance covers the plumbing.

How to choose a way to run ASC 606 and IFRS 15 side by side

Choose based on how many contracts sit on a GAAP difference, and how much of the adjustment you currently calculate by hand. If only a handful of contracts are flagged each year, a documented manual adjustment with a review sign-off works. If flagged contracts arrive weekly, manual adjustments become the audit finding.

A generic script copies contract fields between systems. Loopfour applies your approved GAAP rules to them instead. The Contract Agent reads the signed contract under a confidence threshold, and anything below it goes to a named reviewer in Slack. Every step after that is deterministic: flag the contract, build the schedule, post both books, and record the run in an execution tree. Horizontal tools offer more connectors for general use. For revenue that two sets of auditors will read, governance matters more.

Book a workflow review to see where your dual-GAAP adjustments are still calculated by hand.

Frequently asked questions

Is IFRS 15 the same as ASC 606? IFRS 15 and ASC 606 share the same core principle and five-step model and were issued jointly in May 2014. They are not identical. The main differences are the collectibility threshold, licensing guidance, US-only policy elections, contract-cost impairment reversals, onerous contracts, and disclosures.

What is the difference between probable under ASC 606 and IFRS 15? Under US GAAP, probable means likely to occur, which is a higher threshold. Under IFRS, probable means more likely than not. The difference matters most in step one, where collectibility must be probable for a contract to exist.

Can a company use one revenue schedule for both ASC 606 and IFRS 15? Yes, for most contracts, because the five steps produce the same answer. Contracts that touch a difference (constrained collectibility, certain licenses, noncash consideration, acquired contracts, or impaired contract costs) need a documented adjustment in the second book.

Does IFRS 15 have private-company relief like ASC 606? No. IFRS 15 applies the same requirements to all entities that use full IFRS. Smaller entities can use the separate IFRS for SMEs standard instead, while ASC 606 offers nonpublic entities specific disclosure and other elections.

Do ASC 606 and IFRS 15 treat sales commissions differently? Both capitalize incremental costs of obtaining a contract and both offer a practical expedient to expense them when the amortization period is one year or less. The difference is impairment reversal: IFRS 15 requires it when conditions improve, and US GAAP prohibits it.

Conclusion

ASC 606 vs IFRS 15 is a question of edges, not foundations. The five-step model is shared, so one set of contract data and one set of judgments can serve both books. The work is making sure every contract that sits on a difference is flagged, adjusted by rule, and reconciled every close. That is a workflow problem, and it is the kind that survives an audit when it runs the same way every time.

Tell us the one workflow your team dreads. We will show it running: deterministic, permissioned, and auditable.

Book a demo.

Sources

• FASB, Comparison of Topic 606 and IFRS 15

• KPMG, Revenue accounting: IFRS Accounting Standards vs US GAAP

• IFRS Foundation, IFRS 15 Revenue from Contracts with Customers

Related reading

• What is ASC 606? The five-step model, explained with SaaS examples

• Does ASC 606 apply to private companies and nonprofits?

• How to automate ASC 606 revenue recognition without losing the audit trail

• How to audit revenue recognition: what auditors test

• Audit trails for automated finance