What are the 5 steps of ASC 606 revenue recognition?

ASC 606's five-step model: (1) Identify the contract with a customer — the contract must have commercial substance, both parties must have approved it, payment terms must be identifiable, and collection must be probable. (2) Identify the performance obligations in the contract — each distinct good or service (or bundle) is a separate performance obligation. (3) Determine the transaction price — the amount expected to be received, including estimates of variable consideration (constrained to the extent it is probable that a significant reversal will not occur), non-cash consideration, and significant financing components. (4) Allocate the transaction price to the performance obligations — based on relative standalone selling prices (SSP). (5) Recognize revenue when (or as) each performance obligation is satisfied — either at a point in time or over time.

When is revenue recognized over time vs at a point in time under ASC 606?

Revenue is recognized over time if any of three criteria are met: (1) the customer simultaneously receives and consumes the benefits as the entity performs (e.g., routine recurring services); (2) the entity's performance creates or enhances an asset that the customer controls as the entity creates it (e.g., building on the customer's land); (3) the entity's performance creates an asset with no alternative use, AND the entity has an enforceable right to payment for performance completed to date. If none of these criteria are met, revenue is recognized at a point in time — typically when control of the good or service transfers to the customer.

What is a performance obligation under ASC 606?

A performance obligation is a promise to transfer a distinct good or service to a customer. A good or service is distinct if: (1) the customer can benefit from it on its own or with other readily available resources (capable of being distinct), AND (2) it is separately identifiable from other promises in the contract (distinct within the context of the contract). The second criterion requires judgment: a license to use software that can only function with installation services the entity provides may not be separately identifiable if the installation significantly modifies the software. SaaS subscriptions are typically distinct from implementation services if customers can use the software without the implementation (i.e., via a self-service path).

How does ASC 606 apply to SaaS companies?

For a SaaS company, revenue recognition under ASC 606 involves: (1) Subscription revenue — typically recognized ratably over the subscription term as the customer simultaneously receives and consumes the software access benefit; (2) Implementation/onboarding services — if not distinct from the subscription, bundled with the subscription and recognized over the subscription term; if distinct, recognized as performed; (3) Professional services — if distinct (e.g., custom consulting), recognized as work is performed (input method); (4) Usage-based fees — variable consideration, recognized as usage occurs; (5) Multi-year prepaid contracts — if there's a significant financing component (>1 year prepaid), impute interest; adjust transaction price accordingly. Free trials do not typically start the performance period.

What is the difference between ASC 606 and IFRS 15?

ASC 606 (US GAAP) and IFRS 15 are largely converged — they use the identical five-step model. Key differences: (1) Licenses of IP: ASC 606 distinguishes between right-to-use (recognize at point in time) and right-to-access (recognize over time) based on whether the licensor's activities significantly affect the IP. IFRS 15 has the same framework but different interpretive guidance. (2) Sales with a right of return: both recognize revenue for the portion not expected to be returned, but there are minor differences in how the refund liability and asset for recovery are recognized. (3) Practical expedients: both standards offer similar expedients (right-to-invoice, completed contracts on transition), but the specific scope and availability differ. For multinational companies reporting under both US GAAP and IFRS, the accounting treatment is typically the same.

ASC 606 Revenue Recognition: 10 Worked Examples with AI

Ten worked ASC 606 revenue recognition examples: SaaS subscriptions, multi-element arrangements, construction contracts, variable consideration, contract modifications, principal vs agent, bill-and-hold, significant financing component, license of IP, and IFRS 15 comparison. Step-by-step five-step model application with Claude AI prompts.

Educational content, not professional advice — AI output and figures here can be wrong. Verify before you rely on it. Full disclaimer →

ASC 606 in Practice: Where the Complexity Lives

ASC 606 (Revenue from Contracts with Customers) replaced decades of industry-specific revenue recognition guidance with a single, principles-based five-step model. In theory, this simplification was welcome. In practice, applying those five steps to real-world contracts — with variable consideration, bundled deliverables, multi-year terms, and complex modification rights — requires judgment that often leads to significantly different accounting outcomes depending on how you apply the standard.

This guide works through 10 real-world ASC 606 scenarios with step-by-step analysis and Claude AI prompts that automate the five-step application and the supporting disclosures. The scenarios cover SaaS, construction, manufacturing, professional services, and licensing — the areas where auditors and SEC staff most frequently challenge revenue recognition. For the accounting MCP tools that automate ASC 606 calculations, see the ClaudeFinanceLab Accounting MCP which includes the revenue_recognition_asc606 tool.

Case 1: SaaS Subscription with Implementation Services

A software company signs a 3-year SaaS contract for $360,000 ($10,000/month). The contract includes 3 months of implementation services (setup, data migration, user training) valued at $45,000. The customer cannot use the software without the implementation.

"Apply ASC 606 five-step model to this SaaS contract: Total contract value $360,000 over 36 months. Implementation services $45,000 (months 1-3). Question: are the implementation services a distinct performance obligation? Key facts: (1) the customer cannot independently deploy this software without the implementation services — it requires the vendor's proprietary migration tools; (2) no other vendor provides compatible implementation services; (3) the implementation outputs are inputs to the SaaS service. Apply ASC 606-10-25-19 (capable of being distinct) and 25-21 (distinct within the context of the contract). Conclusion: the implementation is NOT distinct — it is combined with the SaaS subscription as a single performance obligation. Compute: (1) standalone selling price of the combined performance obligation; (2) revenue recognition start date — does the performance obligation begin at contract signing, at go-live, or at contract start?; (3) monthly revenue recognized over the 36-month term; (4) deferred revenue balance at month 6 (when implementation is complete but 30 months remain); (5) prepare the required ASC 606-10-50 contract liability disclosure."
"Modified version: same SaaS contract, but this vendor also sells implementation services to customers who use a competitor's platform. The implementation service is separately identifiable and sold at $45,000 standalone. Now the implementation IS a distinct performance obligation. Apply the five-step model: (1) Step 2: identify 2 performance obligations — SaaS subscription ($315,000 standalone value over 36 months) and implementation services ($45,000 standalone); (2) Step 3: transaction price = $360,000; (3) Step 4: allocate using relative SSP ratio (SaaS $315K / $360K = 87.5%, implementation $45K / $360K = 12.5%); allocated prices: SaaS $315,000, implementation $45,000; (4) Step 5: recognize implementation revenue as services are delivered (month 1-3, pattern = input method based on hours worked — assume equal over 3 months: $15,000/month); SaaS revenue recognized ratably from go-live: $315,000 / 33 months remaining = $9,545/month; (5) prepare journal entries for months 1-6; (6) compare total revenue recognized in year 1 under bundled vs. unbundled treatment."

Case 2: Variable Consideration and the Constraint

A pharmaceutical company licenses a drug compound to a distributor for a $2M upfront payment plus a 12% royalty on net sales. The distributor's first-year sales are estimated at $8-18M. The constraint on variable consideration requires the company to estimate the royalties it is "probable" of receiving without significant reversal risk.

"Variable consideration under ASC 606-10-32-11 (the constraint): License fee $2M upfront (recognized at point in time when license transfers). Royalties estimated at 12% of distributor net sales. Year 1 sales forecast: probability-weighted expected value = (30% × $8M) + (45% × $13M) + (25% × $18M) = $12.75M expected sales → $1.53M expected royalty. Apply the royalty exception: ASC 606-10-55-65 states that royalties on licenses of IP are NOT subject to the variable consideration constraint — instead, they are recognized when the subsequent sales or usage occurs. Compute: (1) revenue recognized at contract inception (year 0): $2M upfront only, NO royalty revenue yet; (2) revenue recognized in Year 1 as sales occur: $12.75M actual net sales × 12% = actual quarterly royalties as reported by distributor; (3) contrast with a non-IP arrangement (e.g., a manufacturing contract with volume rebates) where the constraint DOES apply — show how the recognized revenue would differ if the royalty exception did not apply; (4) disclosure requirement: quantify the transaction price allocated to remaining performance obligations if the $2M is recognized upfront and royalties are the residual."

Case 3: Construction Contract — Over-Time Revenue Recognition

A construction firm signs a $15M fixed-price contract to build a specialized manufacturing facility on the customer's land. Estimated total cost: $12M. At the end of year 1, costs incurred are $5.4M (45% of total). The project is 40 months total.

"ASC 606 construction contract — percentage-of-completion analysis: Contract value $15M, estimated total cost $12M, estimated gross profit $3M (20% margin). Year 1: costs incurred $5.4M. Apply ASC 606 over-time criteria: (1) Criterion 2 met — the contractor is building on the customer's land, so the asset is controlled by the customer as it is created. Revenue recognized over time. (2) Measure progress using the cost-to-cost input method (ASC 606-10-55-20): percentage complete = $5.4M / $12M = 45%. (3) Revenue to recognize in Year 1: 45% × $15M = $6.75M. (4) Cost recognized: $5.4M. (5) Gross profit Year 1: $6.75M − $5.4M = $1.35M (45% of total $3M). Now: cost overrun scenario — at end of Year 2, total estimated cost revised to $14M (up from $12M) — contract becomes a loss contract. Apply ASC 605-35 (which still applies for contract losses): recognize the full expected loss immediately. (6) Compute the expected loss and loss provision required; (7) prepare the journal entries for years 1 and 2 including the loss provision."

Case 4: Principal vs. Agent Determination

An online marketplace collects $1,000 from a customer for a hotel booking. The marketplace remits $850 to the hotel and keeps $150 as a commission. Is the marketplace the principal (recognizing $1,000 gross revenue) or agent (recognizing $150 net)?

"Principal vs. agent analysis under ASC 606-10-55-36: The question is whether the marketplace controls the hotel room before it is provided to the customer. Apply the three indicators: (1) Primary obligor — is the marketplace primarily responsible for fulfilling the promise to provide the hotel room? (If the hotel fails to provide a room, does the customer come back to the marketplace for a full refund?) Key fact: if yes, primary obligor indicator points to principal. (2) Inventory risk — does the marketplace have inventory risk (i.e., has it agreed to pay the hotel regardless of whether a customer purchases)? If marketplace only remits to the hotel after the customer pays, there is no inventory risk — agent indicator. (3) Pricing discretion — can the marketplace set the price charged to the customer? If yes, points to principal. Apply these three indicators to two scenarios: (A) Expedia-model — the customer sees the price, pays the marketplace, marketplace has pricing discretion, primary obligation to provide the room; (B) Trivago-model — the marketplace redirects customers to the hotel's own website for booking, marketplace charges the hotel an advertising fee. Determine: principal (gross $1,000 revenue) or agent (net $150 commission) for each scenario, with full ASC 606 analysis. Show the income statement impact of each determination."

Case 5: Contract Modifications

A three-year software license ($300,000/year) is modified at the end of Year 1 to add a new product module at $60,000/year for the remaining 2 years, and the original license price is renegotiated down to $280,000/year for the remaining 2 years.

"Contract modification analysis under ASC 606-10-25-12: Original contract: 3-year software license, $300,000/year, SSP = $300,000/year. At end of Year 1: (A) new module added at $60,000/year — is this SSP? Assume SSP for the new module is $65,000/year (5% discount from SSP). (B) Original license repriced to $280,000/year (was $300,000/year). Modification has two components: (1) The new module: is it a distinct performance obligation? Yes — the module functions independently. Price for remaining 2 years: $60,000/year × 2 = $120,000. SSP: $65,000 × 2 = $130,000. Discount: $10,000 — NOT priced at SSP. Because the new module is distinct BUT not at SSP, apply the modification rule: treat as a separate new contract ONLY if at SSP. Since not at SSP, it is a modification of the existing contract. (2) The repricing: this is a modification of the existing performance obligation. Combined modification treatment: (A) Is the combined modification a termination of the original contract + creation of a new contract? Only if the modification adds distinct goods at SSP — it doesn't (discount exists). Therefore: treat as a modification of the existing contract (ASC 606-10-25-13(b)). (3) Remaining transaction price = $280,000 × 2 + $60,000 × 2 = $680,000. (4) Remaining performance obligation (24 months of original license + 24 months of new module — treated as a single combined remaining obligation). (5) Catch-up revenue adjustment in month 13: compute the cumulative-catch-up."

Case 6: Licenses of Intellectual Property — Right to Use vs. Right to Access

A media company licenses its character IP (think Disney characters) to a toy manufacturer for 3 years at $5M upfront plus $0.50 per unit sold. The media company has ongoing plans to actively promote these characters through new movies and marketing campaigns.

"License of symbolic IP — ASC 606-10-55-58 to 55-65C: The key question is whether the license provides a 'right to use' (recognize at point in time) or 'right to access' (recognize over time). For symbolic IP (i.e., IP that has significant value because of the licensor's past or ongoing activities — characters, brands, logos): ASC 606 states that the entity's ongoing activities will affect the value of the IP to which the customer has rights. Therefore, character IP licenses are typically 'right to access' licenses recognized over time. Apply: (1) $5M upfront: is this truly upfront revenue or should it be recognized over the 3-year license period? Under 'right to access': recognize ratably over 36 months = $138,889/month. (2) $0.50/unit royalty: apply the royalty exception (ASC 606-10-55-65) — recognize as the subsequent sales occur. (3) Contrast with a 'right to use' license — if the media company were licensing a proprietary software algorithm (functional IP) and had no plans to further develop or promote it, the license fee would be recognized at the point the license transfers. (4) Prepare the ASC 606-10-50 disclosure of remaining performance obligations for the 3-year term."

Case 7: Significant Financing Component

A company sells heavy equipment for $1.2M. The customer pays in 3 equal installments of $400,000 over 3 years. The company's incremental borrowing rate is 6%. Is there a significant financing component?

"Significant financing component analysis under ASC 606-10-32-15: Contract: $1,200,000 equipment sale, paid as $400,000 at delivery (Year 0), $400,000 at Year 1, $400,000 at Year 2. Incremental borrowing rate: 6%. Step 1: compute the cash selling price (what would the customer pay today for a cash sale) — if the equipment sells for $1,200,000 cash, then the installment plan includes financing. Step 2: compute PV of installment payments: $400,000 × (1 / 1.06^0) + $400,000 × (1 / 1.06^1) + $400,000 × (1 / 1.06^2) = $400,000 + $377,358 + $355,998 = $1,133,356. Step 3: Transaction price under ASC 606 = PV of consideration = $1,133,356 (not $1,200,000). The $66,644 difference ($1,200,000 − $1,133,356) is interest income recognized over the payment period. Step 4: apply the practical expedient — if the financing period is 1 year or less, the significant financing component can be ignored. Since the longest payment is 2 years: the expedient does NOT apply (payments extend beyond 1 year). Step 5: prepare the journal entries — recognize revenue at $1,133,356 at delivery, then interest income of $67,801 (Year 1) and $36,358 (Year 2) as the receivable accretes; (6) compare to the treatment if the customer had paid $1,100,000 cash — how does that affect the standalone selling price analysis?"

Case 8: Bill-and-Hold Arrangements

A manufacturer produces specialized industrial equipment to a customer's specifications. The customer requests that the finished equipment be stored at the manufacturer's warehouse for 6 months before delivery. The customer has paid in full ($850,000).

"Bill-and-hold arrangement — ASC 606-10-55-83 to 55-84: For revenue to be recognized before physical delivery, all four criteria must be met: (1) The reason for the bill-and-hold is substantive (the customer requested storage — not just a financing arrangement to recognize revenue early); (2) The product is identified separately as belonging to the customer (tagged, segregated); (3) The product is currently ready for physical transfer (completed, meets specifications); (4) The seller cannot redirect the product to another customer (due to the custom specifications, there is no alternative use). Apply: (1) If all 4 criteria are met: revenue of $850,000 is recognized at the time the product is complete and identified, not at physical delivery. (2) What is the seller's obligation after revenue recognition? Any storage services are a separate performance obligation — allocate a portion of the $850,000 to the storage service (6 months × estimated fair value of storage per month). (3) If the customer cancels after revenue recognition (before delivery): what are the implications? Compute the expected returns adjustment required; (4) Is the 6-month storage fee embedded in the $850,000 or separately billed? How does this affect the allocation?"

Case 9: Multi-Element Arrangement — Hardware, Software, and Support

A technology company sells a bundled package: hardware ($4,000 SSP), perpetual software license ($8,000 SSP), and 3-year support ($6,000 SSP). Contract price: $16,000.

"Multi-element arrangement — three performance obligations: Total SSP = $4,000 + $8,000 + $6,000 = $18,000. Contract price: $16,000 ($2,000 discount). Apply ASC 606 relative SSP allocation: Hardware allocation = ($4,000 / $18,000) × $16,000 = $3,556. Software license = ($8,000 / $18,000) × $16,000 = $7,111. Support contract = ($6,000 / $18,000) × $16,000 = $5,333. Step 5 — timing of recognition: (1) Hardware: recognized at a point in time when control transfers (delivery date). Journal entry: Dr. Accounts Receivable $3,556, Cr. Revenue $3,556. (2) Perpetual software license: does it meet the 'right to use' criteria? If the entity is not expected to undertake significant activities that would affect the software (it's a perpetual license for a standalone product), recognize at point in time when the license key is delivered. Revenue: $7,111 at delivery. (3) Support contract: recognized over 36 months ratably = $5,333 / 36 = $148/month. Deferred revenue at contract inception: $5,333. (4) Prepare the full journal entries for Month 1 (delivery), Month 6 (6 months of support recognized), and Year 1 annual disclosure."

Case 10: IFRS 15 vs. ASC 606 — Key Differences in Practice

"IFRS 15 vs. ASC 606 comparison for a SaaS company reporting under both (dual-filer): The company has a 2-year SaaS contract with a 60-day free trial. Contract value: $120,000. Implementation services are distinct at $15,000. Usage-based overage fees capped at $25,000 for the 2-year term. Analyze under both standards: (1) Free trial — ASC 606: trial period is not a contract until the customer accepts; IFRS 15: same treatment. (2) Implementation services (distinct) — both recognize as performed. No difference. (3) Usage-based fees — ASC 606 practical expedient allows recognition of usage fees in the period of usage if the allocation is consistent with the allocation objective; IFRS 15 has the same right-to-invoice practical expedient. (4) Significant financing component — both standards exempt contracts where the customer has the right to receive services over more than 12 months and the financing component was not the primary reason for the installment payment. (5) Transition — company adopted both ASC 606 and IFRS 15 in the same period using the modified retrospective method. Identify the two areas where a judgment call might lead to different revenue recognition under each standard in the context of this contract."

Using the ASC 606 MCP Tool

The ClaudeFinanceLab Accounting MCP includes the revenue_recognition_asc606 tool, which automates the five-step application for standard revenue patterns. Set it up once and call it from Claude Desktop:

{
  "mcpServers": {
    "claudefinlab-accounting": {
      "url": "https://claudefinancelab.com/accounting/sse",
      "headers": { "Authorization": "Bearer YOUR_API_KEY" }
    }
  }
}

Once configured, prompts like "Apply ASC 606 to this SaaS contract: [paste contract details]" will invoke the tool and return a step-by-step five-step analysis with journal entries and disclosure notes.

ASC 606 Revenue Recognition Examples: 10 Worked Cases with Claude AI (2026)

ASC 606 in Practice: Where the Complexity Lives

Case 1: SaaS Subscription with Implementation Services

Case 2: Variable Consideration and the Constraint

Case 3: Construction Contract — Over-Time Revenue Recognition

Case 4: Principal vs. Agent Determination

Case 5: Contract Modifications

Case 6: Licenses of Intellectual Property — Right to Use vs. Right to Access

Case 7: Significant Financing Component

Case 8: Bill-and-Hold Arrangements

Case 9: Multi-Element Arrangement — Hardware, Software, and Support

Case 10: IFRS 15 vs. ASC 606 — Key Differences in Practice

Using the ASC 606 MCP Tool

Related Articles

Get free access

ASC 606 Revenue Recognition Examples: 10 Worked Cases with Claude AI (2026)

ASC 606 in Practice: Where the Complexity Lives

Case 1: SaaS Subscription with Implementation Services

Case 2: Variable Consideration and the Constraint

Case 3: Construction Contract — Over-Time Revenue Recognition

Case 4: Principal vs. Agent Determination

Case 5: Contract Modifications

Case 6: Licenses of Intellectual Property — Right to Use vs. Right to Access

Case 7: Significant Financing Component

Case 8: Bill-and-Hold Arrangements

Case 9: Multi-Element Arrangement — Hardware, Software, and Support

Case 10: IFRS 15 vs. ASC 606 — Key Differences in Practice

Using the ASC 606 MCP Tool

Related Articles