Uncategorized

ASC 606 Revenue Recognition: The 5-Step Model, Performance Obligations, Worked Example

By chrisomo

ASC 606 revenue recognition replaces the old industry-specific revenue rulebook with a single five-step model that asks the same question for every contract: what did the company promise, and when did it satisfy each promise? Issued by FASB as ASU 2014-09 (and largely converged with IFRS 15), the standard has been in effect for public companies since fiscal years beginning after December 15, 2017, and for private companies since fiscal years beginning after December 15, 2018. Every contract with a customer, in every industry, runs through the same five gates.

What is ASC 606 revenue recognition?

ASC 606 is the FASB codification of Topic 606, Revenue from Contracts with Customers, the joint standard FASB and IASB published in May 2014 to replace the patchwork of industry-specific revenue guidance that came before. In US GAAP it superseded most of ASC 605 (general revenue), all of the software revenue guidance in ASC 985-605, the multiple-element arrangement rules in ASC 605-25, and pieces of more than 100 other Topics and Subtopics. The core principle is in ASC 606-10-10-2: an entity recognizes revenue to depict the transfer of promised goods or services to customers in an amount that reflects the consideration the entity expects to be entitled to in exchange for those goods or services.

The five-step model is the engine. ASC 606-10-25-1 says the entity applies the model to each contract with a customer. The mechanics of identification, measurement, and pattern of recognition all hang off that opening identification of a contract and the obligations inside it.

Why ASC 606 matters

Before ASC 606, revenue accounting was the largest area of US GAAP-IFRS divergence and the largest source of restatements. Industry-specific guidance let software vendors apply vendor-specific objective evidence of fair value to multiple-element arrangements, let real estate developers apply percentage-of-completion narrowly, and let media companies recognize advertising revenue under rules nobody else used. The result was that the same underlying economic transaction produced different revenue numbers depending on which industry guidance the seller chose.

The standard also changed the conversation about contract review. ASC 606 forces finance teams to read every contract for the unit-of-account question, the variable consideration question, the financing component question, and the principal-versus-agent question. That work used to live in pricing memos and sales operations spreadsheets. It now lives in revenue accounting workpapers and is tested by external auditors at every audit. For SaaS, subscription media, and any business with usage-based or tiered pricing, the standard is the single biggest disclosure obligation on the income statement.

For deal diligence, ASC 606 changed the quality of earnings analysis too. Buyers now examine whether the target has correctly identified performance obligations, whether implementation services are distinct from subscription, and whether revenue recognized over time properly reflects progress. Misclassification is one of the most common EBITDA adjustments a QoE provider books.

How ASC 606 works (mechanics)

Five steps, in order, every contract.

Step 1: Identify the contract with a customer

ASC 606-10-25-1 lists five criteria a contract must meet: the parties have approved the contract and are committed to perform, the entity can identify each party’s rights and the payment terms, the contract has commercial substance, and collection of substantially all of the consideration is probable. A contract can be written, oral, or implied by customary business practice. If the criteria are not met, the entity does not have a contract under Topic 606 and any consideration received is recognized as a liability until either the contract is created or the consideration is non-refundable and the entity has no remaining obligations.

Step 2: Identify the performance obligations in the contract

A performance obligation is a promise to transfer a distinct good or service (ASC 606-10-25-14). The distinct test is in ASC 606-10-25-19: the customer must be able to benefit from the good or service on its own or with other resources readily available, and the promise must be separately identifiable from other promises in the contract. ASC 606-10-25-21 gives factors that indicate the promise is not separately identifiable: a significant integration service, modification or customization of one good by another, or high interdependence.

The single most contested judgment under ASC 606 is whether implementation services bundled with a SaaS subscription are distinct. If the implementation is highly customer-specific, cannot be performed by a third party, and is required for the customer to access the SaaS, it is generally not distinct and is combined with the subscription into a single performance obligation recognized over the SaaS term.

Step 3: Determine the transaction price

Transaction price is the amount of consideration the entity expects to be entitled to in exchange for transferring the promised goods or services (ASC 606-10-32-2). It includes variable consideration, the effects of a significant financing component, non-cash consideration, and consideration payable to a customer. It excludes amounts collected on behalf of third parties such as sales tax.

Variable consideration (bonuses, penalties, discounts, rebates, refunds, performance bonuses, contingent fees) is estimated under one of two methods (ASC 606-10-32-8): expected value (probability-weighted across a range of outcomes) or most-likely-amount. The estimate is constrained under ASC 606-10-32-11 to the amount for which it is probable that a significant reversal will not occur when the uncertainty is resolved. Significant financing components apply when the timing of payment provides the customer or the entity with a significant benefit of financing; the practical expedient in ASC 606-10-32-18 lets entities ignore the financing component if the period between transfer and payment is one year or less.

Step 4: Allocate the transaction price to the performance obligations

Allocation is at relative standalone selling price (ASC 606-10-32-31). Standalone selling price is the price at which an entity would sell the good or service separately to a customer. If observable standalone prices are not available, the entity estimates using one of three methods (ASC 606-10-32-34): adjusted market assessment, expected cost plus a margin, or residual approach (only when the selling price is highly variable or uncertain).

Step 5: Recognize revenue when (or as) the entity satisfies a performance obligation

ASC 606-10-25-27 lists three criteria for over-time recognition: the customer simultaneously receives and consumes the benefits as the entity performs, the entity’s performance creates or enhances an asset the customer controls, or the entity’s performance does not create an asset with alternative use and the entity has an enforceable right to payment for performance completed to date. Meeting any one criterion is enough.

For over-time recognition, the entity selects a method that depicts performance: output methods (units delivered, milestones, time elapsed) or input methods (costs incurred, labor hours, machine hours). For point-in-time obligations, revenue is recognized when control transfers (ASC 606-10-25-30), with indicators including transfer of title, physical possession, customer acceptance, and the customer obtaining significant risks and rewards.

Scope of ASC 606 vs prior US GAAP

Worked example: SaaS plus implementation, $120K subscription and $20K services

Company A signs a contract with Customer B on January 1, 2026. The contract grants Customer B access to the SaaS platform for 12 months at $120,000 (billed and collected upfront) and provides implementation services for $20,000 (also billed and collected upfront). The implementation runs from January 1 to February 28, 2026. Customer B can choose to perform the implementation itself or use a third party, and the SaaS platform is functional without the implementation services. Standalone selling prices: SaaS $120,000/year, implementation $20,000.

Step 1: Contract. Signed agreement, defined payment, commercial substance, probable collection. Contract exists.

Step 2: Performance obligations. Two: (a) SaaS access over 12 months, (b) implementation services. Because the customer can benefit from the SaaS without the implementation and the implementation is not customer-specific, the implementation is distinct under ASC 606-10-25-19. Two performance obligations.

Step 3: Transaction price. $140,000 fixed. No variable consideration, no financing component (payment is upfront), no consideration payable to the customer.

Step 4: Allocation. At standalone selling prices: SaaS $120,000, implementation $20,000. No discount allocation needed because the total equals the sum of standalone selling prices.

Step 5: Recognition. The SaaS performance obligation is satisfied over time (customer simultaneously receives and consumes the benefit; ASC 606-10-25-27(a)). Recognize $120,000 ratably over 12 months, $10,000 per month. The implementation services are satisfied over time as the work is performed (ASC 606-10-25-27(a)). Recognize $20,000 over the two-month implementation period, $10,000 per month.

Journal entries:

January 1, 2026 (contract inception and billing):

• Dr. Cash 140,000
• Cr. Contract liability (deferred revenue) 140,000

January 31, 2026 (first month of SaaS plus implementation):

• Dr. Contract liability 20,000
• Cr. Revenue, subscription ($120,000 / 12) 10,000
• Cr. Revenue, professional services ($20,000 / 2) 10,000

February 28, 2026 (second month, implementation completes):

• Dr. Contract liability 20,000
• Cr. Revenue, subscription 10,000
• Cr. Revenue, professional services 10,000

March 31, 2026 through December 31, 2026 (months three through twelve, SaaS only):

• Dr. Contract liability 10,000
• Cr. Revenue, subscription 10,000

Total recognized over twelve months: $120,000 subscription plus $20,000 services equals $140,000. The contract liability runs from $140,000 at inception to zero at December 31, 2026.

Variant: implementation is not distinct. Assume the implementation is highly customer-specific, the SaaS does not function without it, and a third party cannot perform it. Under ASC 606-10-25-19 the implementation is not separately identifiable; the two are combined into a single performance obligation. Recognize the full $140,000 ratably over the 12-month SaaS term beginning when the implementation finishes (March 1, 2026): $140,000 / 10 months = $14,000 per month, March through December. Implementation revenue moves from $20,000 in months one and two to a deferral until month three. The pattern of recognition is materially different. This is why the distinct judgment is the most-contested step in SaaS revenue accounting.

Sales commissions under ASC 340-40. Assume Company A pays its sales rep a $7,000 commission on signing the contract. Because the contract term is 12 months and the commission is incremental to obtaining the contract, ASC 340-40-25-1 requires capitalization. Amortize over the period of benefit (assume 12 months matches the customer life). $7,000 / 12 = $583 per month sales commission expense.

Recent changes (ASU updates affecting ASC 606)

ASU 2014-09 created Topic 606. Since then FASB has issued targeted amendments to clarify or simplify pieces of the standard.

• ASU 2015-14 deferred the effective date one year for both public and nonpublic entities.
• ASU 2016-08 clarified principal versus agent considerations (gross versus net presentation) by focusing on control of the specified good or service before transfer to the customer.
• ASU 2016-10 simplified identifying performance obligations and licensing guidance (functional versus symbolic IP licenses).
• ASU 2016-12 provided practical expedients on transition, sales tax presentation (gross or net by election), and noncash consideration measurement date.
• ASU 2016-20 made technical corrections and improvements.
• ASU 2017-13 updated SEC paragraphs in the codification for SEC staff observations.
• ASU 2018-18 clarified the interaction between Topic 606 and the collaborative arrangements guidance in Topic 808.
• ASU 2020-05 deferred the effective date for nonpublic entities again because of the pandemic, pushing private-company application to fiscal years beginning after December 15, 2019.
• ASU 2021-08 changed how an acquirer measures contract assets and contract liabilities in a business combination, requiring the acquirer to apply ASC 606 to determine carrying amounts at the acquisition date rather than measuring at fair value under ASC 805. This is one of the most practitioner-relevant updates because it affects every EBITDA add-back related to acquired deferred revenue.

Common implementation pitfalls

• Treating implementation services as distinct without testing both prongs (ASC 606-10-25-19). Capable of being distinct alone is not enough. The promise must also be separately identifiable in the context of the contract.
• Failing to constrain variable consideration (ASC 606-10-32-11). Estimates booked in revenue without the constraint test produce reversals later. The constraint requires probable that no significant reversal will occur.
• Missing the principal-versus-agent question (ASC 606-10-55-37). Gross versus net presentation depends on which party controls the specified good or service before transfer. Reselling marketplaces and platforms get this wrong frequently.
• Recognizing setup fees upfront when they are not distinct. A non-refundable setup fee that grants no distinct good or service is part of the transaction price for the underlying ongoing performance obligation and recognized over the same period (ASC 606-10-55-51).
• Misapplying the sales- and usage-based royalty exception (ASC 606-10-55-65). The exception applies only to licenses of intellectual property; service contracts and goods sales remain under the general variable consideration rules.
• Failing to capitalize sales commissions under ASC 340-40-25-1. Incremental costs of obtaining a contract that the entity expects to recover are capitalized. The practical expedient for contracts of one year or less lets entities expense as incurred.
• Inadequate disaggregation under ASC 606-10-50-5. Single-line revenue presentation rarely meets the disclosure objective. Disaggregation by major product line, geography, customer type, contract duration, or timing of transfer is typically required.

Frequently asked questions

What is the difference between a contract asset and a receivable under ASC 606?

A contract asset arises when the entity has performed but the right to consideration is conditional on something other than the passage of time (ASC 606-10-45-3). A receivable arises when the right is unconditional. The distinction matters for credit risk presentation and disclosure.

How does ASC 606 treat a contract modification?

ASC 606-10-25-10 treats a modification as a separate contract if it adds distinct goods or services at a standalone price. Otherwise it is a termination of the existing contract and creation of a new contract (with prospective allocation) or a continuation of the existing contract (with cumulative catch-up). The fact pattern drives the answer.

What is the practical expedient for shipping and handling under ASC 606?

ASC 606-10-25-18B allows entities to elect to account for shipping and handling activities performed after control transfers as a fulfillment cost rather than a separate performance obligation. The election is a policy election applied consistently.

Does ASC 606 apply to nonpublic entities?

Yes. Nonpublic entities applied Topic 606 for fiscal years beginning after December 15, 2019 (deferred by ASU 2020-05 from the original 2018 effective date). Interim period guidance applies for fiscal years beginning after December 15, 2020.

How does ASC 606 affect deferred revenue acquired in a business combination?

ASU 2021-08 amended ASC 805 to require the acquirer to apply Topic 606 to recognize and measure contract assets and contract liabilities at the acquisition date. The acquirer treats the deferred revenue as if it had originated the contract, which generally avoids the historical fair-value haircut that compressed post-deal revenue. Effective for public business entities for fiscal years beginning after December 15, 2022.

What is a stand-ready obligation?

A stand-ready obligation is a promise to make a good or service available whenever the customer wants it (ASC 606-10-55-156). The classic example is unlimited cloud access. Revenue is generally recognized ratably over the stand-ready period because the customer benefits as time passes regardless of usage volume.

How do you handle a contract with a significant financing component?

ASC 606-10-32-15 requires the entity to adjust the transaction price for the time value of money. The entity uses the rate that would be reflected in a separate financing transaction between the parties. Interest income or interest expense is presented separately from revenue.

What disclosure does ASC 606 require for remaining performance obligations?

ASC 606-10-50-13 requires disclosure of the aggregate amount of transaction price allocated to performance obligations that are unsatisfied (or partially unsatisfied) at the reporting date, and when the entity expects to recognize that amount as revenue. There is a practical expedient for contracts with original expected duration of one year or less and for certain right-to-invoice arrangements.