ASC 606 and IFRS 15: The Complete Guide
Before 2018, U.S. companies followed more than 100 industry-specific rules for recognizing revenue, one set of guidance for software, another for construction, another for real estate. Comparing two companies' revenue meant first understanding which rulebook each one used. ASC 606 and its international counterpart, IFRS 15, replaced that patchwork with a single, principles-based framework that applies the same way regardless of industry.
This guide covers what the standard actually requires, walks through the five-step model in practical terms, and covers where modern billing models, subscription, usage-based, and hybrid arrangements in particular, most commonly create compliance problems.
ASC 606, formally "Revenue from Contracts with Customers," is the U.S. GAAP standard, developed jointly by the Financial Accounting Standards Board (FASB) and the International Accounting Standards Board (IASB), that governs when and how much revenue a company recognizes from contracts with customers. IFRS 15 is the IASB's version of the same standard, used internationally. The two share the same five-step model and reach the same conclusions in nearly all cases; the specific places they diverge, covered in detail below, are narrow but worth knowing precisely.
Key takeaways
- The core principle: recognize revenue to reflect the transfer of promised goods or services to a customer, in an amount reflecting what the company expects to be entitled to in exchange, not simply when cash is received.
- The standard applies in five steps: identify the contract, identify the performance obligations, determine the transaction price, allocate that price across obligations, and recognize revenue as each obligation is satisfied.
- Revenue recognition and cash collection are different events. A company can recognize revenue before, after, or at the same time it actually receives payment, which is precisely why subscription and multi-element contracts require careful handling.
- Most real-world compliance problems happen at steps 3 and 4 for modern billing models: determining transaction price when consideration is variable (usage-based billing), and allocating price across obligations when a deal bundles multiple products or services.
- ASC 606 and IFRS 15 are not fully identical, but the differences are narrow enough that a well-designed process typically satisfies both.
The five-step model
Step 1: Identify the contract
A contract is an agreement, written, oral, or implied, that creates enforceable rights and obligations between two parties. It must meet specific criteria to qualify: both parties have approved it, each party's rights regarding goods or services are identifiable, payment terms are identifiable, and it's probable the company will collect the consideration it's entitled to. Multiple contracts with the same customer, signed close together, sometimes need to be combined for accounting purposes even if they're legally separate.
Step 2: Identify the performance obligations
A performance obligation is a distinct promise to transfer a good or service. A single contract can contain several: a SaaS subscription might bundle the core software license, implementation services, and ongoing support as three separate obligations, each potentially recognized on a different schedule.
Step 3: Determine the transaction price
This is the amount of consideration a company expects to be entitled to in exchange for the goods or services. For fixed-fee contracts this is straightforward. For usage-based or variable consideration, discounts, rebates, refunds, performance bonuses, it requires estimating an amount and constraining that estimate so revenue isn't recognized before it's reasonably certain to be realized.
Step 4: Allocate the transaction price to performance obligations
When a contract bundles multiple performance obligations, the total transaction price has to be allocated across them, typically based on each obligation's standalone selling price, the price the company would charge for that obligation if sold separately. This is one of the more operationally difficult steps for companies with bundled pricing, tiered packages, or frequent upsells and downsells.
Step 5: Recognize revenue when or as each performance obligation is satisfied
Revenue is recognized either at a point in time (control of a good transfers at delivery) or over time (a service is delivered continuously, like a subscription). Most SaaS revenue is recognized over time, spread across the subscription period as the service is delivered.
Where ASC 606 and IFRS 15 actually differ
The FASB and IASB jointly developed the five-step model and describe the two standards as reaching the same conclusions on the core requirements for revenue from contracts with customers, with only minor differences remaining. Those differences are narrow, but for companies reporting under both frameworks, or evaluating a platform that needs to support both, they're worth knowing precisely rather than assuming full equivalence.
| Area | ASC 606 (U.S. GAAP) | IFRS 15 |
|---|---|---|
| Collectibility threshold | ASC 606 (U.S. GAAP)"Probable" is generally applied at a higher bar, commonly interpreted around 75 to 80 percent likelihood | IFRS 15"Probable" means more likely than not, around 50 percent likelihood |
| Collectibility guidance | ASC 606 (U.S. GAAP)Includes explicit additional guidance directing entities to assess the customer's ability and intent to pay | IFRS 15No equivalent additional guidance; collectibility is assessed more generally at contract inception |
| Impairment loss reversal on contract costs | ASC 606 (U.S. GAAP)Reversal of a previously recognized impairment on capitalized contract costs is prohibited | IFRS 15Reversal is required when the conditions that caused the impairment no longer exist |
| Onerous contracts | ASC 606 (U.S. GAAP)No general standard for loss-making contracts; relies on other, sometimes industry-specific guidance | IFRS 15Addressed separately under IAS 37, with a provision recognized when unavoidable costs exceed expected economic benefits |
| Interim disclosures | ASC 606 (U.S. GAAP)Interim disclosure requirements are closer to the annual requirements | IFRS 15Fewer interim disclosure requirements than ASC 606 |
| Practical expedients and transition relief | ASC 606 (U.S. GAAP)More extensive practical expedients and transition relief available | IFRS 15Fewer practical expedients; more case-by-case judgment required |
The collectibility threshold is the difference practitioners flag most often, since it can genuinely shift the timing of when a contract qualifies for revenue recognition at all, not just how much is recognized. For a single, creditworthy customer this rarely matters in practice. For a portfolio of customers with thinner credit histories, or for companies reporting under both standards for different jurisdictions, it's worth documenting the reconciliation explicitly rather than assuming one conclusion carries over to the other.
Where modern billing models create the most difficulty
Usage-based billing. Determining the transaction price (step 3) is inherently harder when consideration varies month to month based on actual usage. The standard requires estimating variable consideration and constraining that estimate, which means a usage-based business needs a defensible, consistent methodology, not an ad hoc monthly judgment call.
Contract modifications. When a customer upgrades, downgrades, or renegotiates mid-contract, the accounting treatment depends on whether the modification is treated as a separate contract or a modification of the existing one, which changes how remaining revenue is recognized going forward.
Multi-element arrangements. A deal that bundles a subscription, a professional services engagement, and a support tier requires standalone selling price allocation across all three (step 4), and getting this wrong is one of the more common sources of restatement risk for growing SaaS companies.
Tiered and milestone billing. Revenue recognition timing depends on how performance obligations are defined and when they're satisfied, which for milestone-based contracts means recognizing revenue as each milestone is completed rather than evenly over the contract term.
How Campfire automates ASC 606 and IFRS 15 compliance
Campfire's Revenue Automation product handles revenue recognition across subscription, usage-based, milestone, and transaction billing models, with contract modifications, upsells, downsells, and standalone selling price allocation handled automatically rather than through manual spreadsheet calculation. For usage-based arrangements, it connects to metering engines like Metronome and Harvest and applies pricing tiers to raw usage data automatically, tracking arrears, prepaid credits, expirations, rollovers, and tranches separately. Every change to contract terms, pricing, and dates is tracked with a timestamp and user attribution, giving a full audit trail for exactly the kind of judgment calls, step 3 and step 4 in particular, that auditors scrutinize most closely.
If you're evaluating any platform for ASC 606 or IFRS 15 compliance, ask specifically how it handles standalone selling price allocation across bundled obligations and how it treats contract modifications. Those two areas are where genuine automation differs most from a system that simply calculates straight-line amortization on simple subscriptions.
FAQ
What's the difference between ASC 606 and IFRS 15?
They're the U.S. GAAP and international versions of substantially the same standard, developed jointly by the FASB and IASB, and they reach the same conclusions in nearly all cases. The differences that remain are specific: a higher collectibility threshold under ASC 606, a prohibition on reversing contract cost impairments under ASC 606 where IFRS 15 requires reversal, and separate treatment of onerous contracts under IFRS (via IAS 37) versus no general U.S. GAAP equivalent.
Why does the collectibility threshold difference between ASC 606 and IFRS 15 matter?
ASC 606 generally applies "probable" at a higher bar, commonly around 75 to 80 percent likelihood, while IFRS 15 treats "probable" as more likely than not, around 50 percent. This can shift whether a contract qualifies for revenue recognition at all, not just the amount recognized, which matters most for portfolios of customers with weaker credit profiles or for companies reconciling reporting across both standards.
Does ASC 606 apply to private companies?
Yes. ASC 606 applies to both public and private companies, though public companies generally had earlier effective dates and face more extensive disclosure requirements.
How is usage-based revenue recognized under ASC 606?
Usage-based revenue is a form of variable consideration under step 3 of the model. Companies must estimate the expected transaction price and constrain that estimate so revenue isn't recognized before it's reasonably certain to be realized, then recognize revenue as the usage-based service is delivered.
What is standalone selling price, and why does it matter?
Standalone selling price is the price a company would charge for a specific good or service if it sold that item separately. It matters because step 4 of the model requires allocating a bundled contract's total price across performance obligations based on their relative standalone selling prices, which directly affects how much revenue is recognized against each part of a deal.
What does Campfire cost for revenue automation?
Campfire offers tailored pricing based on company size and complexity. Contact the team for a demo and custom quote.