ASC 606 Revenue Recognition: What It Is and How It Works

ASC 606, Revenue from Contracts with Customers, is the authoritative US GAAP standard governing when and how entities recognize revenue. If your company earns revenue from contracts, this standard applies to you. It replaced more than 200 pieces of legacy US GAAP revenue guidance with a single, principles-based framework built around one core question: has control of a promised good or service transferred to the customer?

The standard is fully effective and embedded in practice. But "fully effective" does not mean "settled." Revenue recognition remains one of the top five topics in SEC comment letters, and the SEC's Office of the Chief Accountant has noted in multiple speeches that it is consistently one of the top areas of financial statement restatement. Understanding the standard is not a one-time exercise.

Key takeaway: ASC 606 is not new, but it is still generating restatements, SEC comments, and audit findings. The standard is principles-based, which means the hard cases are genuinely hard and require documented judgment.

What Is ASC 606 Revenue Recognition?

ASC 606 is the FASB's codified standard for recognizing revenue from contracts with customers. It sits at Topic 606 of the FASB Accounting Standards Codification and was issued jointly by FASB and the IASB on May 28, 2014. The IASB counterpart is IFRS 15, making ASC 606 and IFRS 15 the most significant convergence achievement between the two boards.

As FASB explains: "Revenue is one of the most important measures used by investors in assessing a company's performance and prospects. However, previous revenue recognition guidance differs in GAAP and IFRS, and many believe both standards were in need of improvement."

The new standard:

• Removes inconsistencies across industries (pre-606, software, real estate, and construction each had their own rules)
• Provides a single principles-based framework applicable across all sectors
• Improves comparability across entities, industries, and capital markets
• Significantly expands disclosure requirements

Is ASC 606 Part of GAAP?

Yes. ASC 606 is fully embedded in US GAAP as codified by FASB. Public companies were required to adopt it for annual periods beginning after December 15, 2017 (calendar year 2018 for most). Private companies and not-for-profits had until annual periods beginning after December 15, 2018. Both deadlines are long past, but private companies that adopted in 2019 and have never revisited their policies as their business models evolved carry meaningful accounting policy drift risk.

ASC 606 vs. IFRS 15

The two standards share the same five-step model and core principle. The differences are narrow but matter in practice:

For US registrants, ASC 606 governs. Foreign private issuers reporting under IFRS apply IFRS 15.

The Core Principle of ASC 606

The core principle is to recognize revenue in an amount that reflects the consideration to which an entity expects to be entitled in exchange for transferring promised goods or services to a customer. This single sentence, codified at ASC 606-10-05-3, drives every judgment in the standard.

The shift from legacy GAAP is fundamental. Pre-606 standards often focused on risks and rewards of ownership, or on specific industry rules. ASC 606 focuses on control: revenue is recognized when the customer obtains control of the asset, not merely when delivery occurs or an invoice is issued.

As stated at ASC 606-10-25-23: "An entity shall recognize revenue when (or as) the entity satisfies a performance obligation by transferring a promised good or service to a customer. An asset is transferred when (or as) the customer obtains control of that asset."

The Five Steps of ASC 606

The five-step model, codified at ASC 606-10-05-4, is the analytical framework every entity applies to every revenue contract. The steps are sequential, but the judgments within them are interdependent.

Step 1: Identify the Contract with a Customer

A contract exists under ASC 606 when all five criteria are met: the parties have approved it and are committed to perform; each party's rights are identifiable; payment terms are identifiable; the contract has commercial substance; and collection of the consideration is probable. Oral and implied contracts can qualify. The collectibility criterion is where many arrangements fail at the threshold, particularly in healthcare and certain licensing arrangements.

Step 2: Identify the Performance Obligations

This is where most of the judgment lives. A performance obligation is a promise to transfer a distinct good or service. Under ASC 606-10-25-19, a good or service is distinct only if both criteria are met:

1. The customer can benefit from it on its own or with other readily available resources (capable of being distinct)
2. The entity's promise to transfer it is separately identifiable from other promises in the contract (distinct within the context of the contract)

Both must be satisfied. If either fails, the goods or services are combined into a single performance obligation.

ASC 606-10-25-21 identifies three indicators that promises are NOT separately identifiable:

• The entity provides a significant integration service (e.g., constructing a building from component inputs)
• One good or service significantly modifies or customizes another (e.g., specialized equipment with bespoke configuration)
• The goods or services are highly interdependent or interrelated (e.g., software with critical updates that alter its functionality)

As Deloitte notes: "Entities often have difficulty determining the appropriate judgments to apply in the identification of performance obligations and the assessment of whether an entity is a principal or an agent. Not surprisingly, these are two topics of the revenue standard on which entities commonly seek the SEC staff's views in prefiling submissions."

For SaaS and subscription businesses, the contested questions are whether a software license is distinct from implementation or setup services, and whether customer success activities constitute a separate performance obligation. KPMG's Revenue Recognition Handbook identifies these as the most litigated ASC 606 issues in the software sector.

Step 3: Determine the Transaction Price

The transaction price is the amount of consideration the entity expects to be entitled to. It includes fixed amounts and estimates of variable consideration, but variable consideration is subject to a constraint.

Variable consideration (discounts, rebates, refunds, royalties, performance bonuses, penalties) must be estimated using either:

• The expected value method: probability-weighted sum of possible outcomes (best when many outcomes are possible)
• The most likely amount method: the single most likely outcome (best when there are only two possible outcomes)

The estimate is then constrained: included in the transaction price only to the extent it is highly probable that a significant revenue reversal will not occur when the uncertainty resolves. This constraint requires significant judgment and documentation, and it is a frequent source of SEC comment letters.

Step 4: Allocate the Transaction Price

The transaction price is allocated to each performance obligation based on relative stand-alone selling prices (SSPs). SSP is the price at which the entity would sell the good or service separately. When observable stand-alone prices exist (i.e., the entity actually sells the item separately), use them. When they don't, the entity must estimate SSP using approaches such as adjusted market assessment, expected cost plus margin, or residual approach (only when SSP is highly variable or uncertain).

For bundled SaaS plus professional services offerings, SSP determination is one of the most contested areas in practice. Companies that set SSPs without a documented methodology, or that fail to update SSPs as pricing evolves, face both audit risk and SEC comment risk.

Step 5: Recognize Revenue When (or As) Performance Obligations Are Satisfied

Revenue is recognized either over time or at a point in time, depending on when control transfers.

Revenue is recognized over time if any one of three criteria is met, per ASC 606-10-25-27:

1. The customer simultaneously receives and consumes the benefits as the entity performs (e.g., routine cleaning services)
2. The entity's performance creates or enhances an asset the customer controls as it is created (e.g., construction on customer-owned land)
3. The entity's performance does not create an asset with an alternative use, and the entity has an enforceable right to payment for performance completed to date (e.g., highly customized manufactured goods)

If none of these criteria are met, revenue is recognized at a point in time, typically when the customer obtains control, evidenced by transfer of title, physical possession, acceptance, or the entity's right to payment.

For over-time obligations, the entity must select a measure of progress (output methods such as units delivered or milestones reached, or input methods such as costs incurred) and apply it consistently to similar obligations.

The Principal vs. Agent Determination

Whether an entity is a principal or an agent determines whether revenue is recorded gross or net, which can dramatically change reported revenue figures. This is one of the most consequential and most contested judgments in ASC 606.

A principal controls the good or service before it is transferred to the customer and records gross revenue. An agent arranges for another party to provide the good or service and records only the net fee or commission.

ASU 2016-08 clarified that the assessment focuses on control, not legal form or title. Three indicators of control (and therefore principal status) are:

1. Primary responsibility for fulfilling the promise to the customer
2. Inventory risk before or after the good or service is transferred
3. Discretion in establishing the price for the good or service

No single indicator is determinative. The analysis is highly fact-specific, which is why principal vs. agent conclusions that appear inconsistent with an entity's business model are a top SEC comment theme.

What Disclosures Does ASC 606 Require?

ASC 606's disclosure requirements are more extensive than legacy GAAP and are a consistent source of SEC comment letters. The standard requires disclosure of four categories of information, per ASC 606-10-50:

1. Disaggregated revenue: Revenue broken into categories that depict how the nature, amount, timing, and uncertainty of revenue and cash flows are affected by economic factors. The SEC expects this to be entity-specific, not boilerplate.
2. Contract balances: Opening and closing balances of contract assets and contract liabilities (deferred revenue), and how they changed.
3. Performance obligations: Description of when obligations are typically satisfied, significant payment terms, and the nature of goods or services promised.
4. Significant judgments: The judgments made in applying the standard, particularly around variable consideration, performance obligation identification, and the timing of satisfaction.

For entities with long-term or subscription contracts, ASC 606-10-50-13 also requires disclosure of the remaining performance obligations (the "backlog" disclosure): the aggregate transaction price allocated to obligations not yet satisfied, and when the entity expects to recognize that revenue. This is a key investor metric for SaaS, subscription, and long-term contract businesses, and a frequent source of SEC comments.

A practical expedient at ASC 606-10-50-14 allows entities to omit the backlog disclosure for contracts with an original expected duration of one year or less, or where revenue is recognized in the amount the entity has the right to invoice.

Contract Modifications: A Persistent Source of Error

Contract modifications are one of the most common sources of ASC 606 errors, particularly in long-term service, construction, and SaaS contracts. When a contract is modified, the entity must determine which of three accounting treatments applies, per ASC 606-10-25-12:

The three-way analysis requires fresh judgment each time a contract changes. In practice, companies with high contract modification volumes (construction, government contracting, enterprise SaaS) often apply the wrong treatment or fail to document the analysis at all.

ASC 340-40: The Companion Standard You Cannot Ignore

ASC 606 does not stand alone. ASC 340-40 governs the costs to obtain and fulfill a contract, and the two standards work together. Many companies under-implement ASC 340-40.

Under ASC 340-40-25-1, incremental costs of obtaining a contract (the clearest example: sales commissions paid only when a contract is signed) must be capitalized as an asset if the entity expects to recover them. The asset is amortized on a basis consistent with the transfer of the goods or services to which it relates.

A practical expedient allows expensing as incurred if the amortization period would be one year or less. Companies that blanket-expense all sales commissions without applying this analysis, or that apply the wrong amortization period, are under-implementing the standard. PwC's Revenue from Contracts with Customers guide is particularly strong on the ASC 606 and ASC 340-40 interaction.

Recent FASB Amendments That Practitioners Need to Know

FASB has issued at least six ASUs amending or clarifying ASC 606 since the original standard. Two are especially important for finance teams in 2026.

ASU 2021-08: Deferred Revenue in Business Combinations

ASU 2021-08 changed how contract assets and contract liabilities (deferred revenue) acquired in a business combination are measured. Previously, acquirers measured deferred revenue at fair value under ASC 805, which typically resulted in a significant write-down and suppressed post-acquisition revenue. ASU 2021-08 requires acquirers to measure contract liabilities in accordance with ASC 606, as if they had originated the acquiree's contracts themselves.

This is a significant change for M&A accounting. For public companies, it was effective for fiscal years beginning after December 15, 2022. For a practical walkthrough of the broader ASC 805 framework, see our ASC 805 Business Combination Accounting guide.

ASU 2024-03: Coordinating Revenue and Expense Disaggregation

ASU 2024-03 (Disaggregation of Income Statement Expenses) is effective for public business entities for fiscal years beginning after December 15, 2026. While it primarily addresses expense disaggregation, it intersects directly with ASC 606 revenue disclosures. Finance teams implementing ASU 2024-03 should design their revenue and expense disaggregation categories in coordination, not in silos. For a detailed breakdown of what ASU 2024-03 requires, see our DISE Disclosure Requirements guide.

The FASB's Post-Implementation Review: What It Means

FASB completed its post-implementation review of ASC 606 in 2024, concluding that the standard is functioning as intended and no fundamental changes are needed. Key themes from preparers and auditors: principal/agent and variable consideration remain the hardest areas; disclosure requirements are burdensome for smaller entities; and some industry-specific issues in software and construction still generate diversity in practice.

The practical implication: no relief is coming. Companies should treat their existing accounting policies as final and ensure they are still fit for purpose as business models evolve.

Common ASC 606 Mistakes and SEC Comment Triggers

The SEC's Division of Corporation Finance has identified consistent patterns in comment letters on ASC 606 filings:

• Insufficient disaggregation of revenue: Generic categories (e.g., "product" and "service") that don't reflect the entity's actual economic drivers
• Boilerplate accounting policy disclosures: Policies that recite the standard rather than describing the entity's specific judgments and contract types
• Inadequate disclosure of significant judgments: Particularly around variable consideration constraints and performance obligation identification
• Principal vs. agent conclusions inconsistent with the business model: Where the gross/net presentation doesn't align with how the entity actually operates
• Backlog disclosure gaps: Missing or incomplete remaining performance obligation disclosures for long-term contracts

For finance teams using AI tools to automate contract review and obligation mapping, there are additional risks to manage. Our article on AI revenue recognition risks for controllers covers the four most common failure modes in AI-assisted ASC 606 workflows.

Licenses of Intellectual Property: Right to Use vs. Right to Access

For software, media, pharmaceutical, and franchise businesses, the distinction between a license that is a "right to use" and one that is a "right to access" determines whether revenue is recognized at a point in time or over time. This is one of the most contested areas in practice.

Under ASC 606-10-55-58, a license is a right to access the entity's IP (recognized over time) if the entity's ongoing activities are expected to significantly affect the IP to which the customer has rights. If the entity's activities do not significantly affect the IP, the license is a right to use (recognized at the point in time the license is granted).

For SaaS businesses, this distinction often determines whether a software license bundled with ongoing updates is one performance obligation recognized over time, or two separate obligations with different recognition patterns.

FAQ

What is ASC 606 revenue recognition?

ASC 606 is the US GAAP standard, codified at FASB ASC Topic 606, that governs when and how entities recognize revenue from contracts with customers. It applies to all entities that enter into contracts to provide goods or services, with limited exceptions (leases, insurance, financial instruments). The core principle: recognize revenue when control of a promised good or service transfers to the customer, in an amount reflecting the consideration the entity expects to receive.

What are the five steps in the ASC 606 revenue framework?

The five steps are: (1) identify the contract with a customer; (2) identify the performance obligations in the contract; (3) determine the transaction price; (4) allocate the transaction price to the performance obligations; and (5) recognize revenue when or as each performance obligation is satisfied. Steps 2, 3, and 5 generate the most judgment and the most audit and SEC comment activity.

What are the five criteria for revenue recognition under ASC 606?

This question usually refers to the five criteria for a contract to exist under Step 1: (1) the parties have approved the contract and are committed to perform; (2) each party's rights regarding the goods or services are identifiable; (3) payment terms are identifiable; (4) the contract has commercial substance; and (5) collection of the consideration is probable. All five must be met before the five-step model applies.

Does ASC 606 apply to my industry?

ASC 606 applies to all entities that enter into contracts with customers to provide goods or services, with narrow exceptions for leases (ASC 842), insurance contracts (ASC 944), financial instruments (ASC 310, 320, 323, 815), guarantees (ASC 460), and nonmonetary exchanges between entities in the same line of business. It applies to SaaS, construction, healthcare, manufacturing, licensing, professional services, and most other industries.

What is the difference between a principal and an agent under ASC 606?

A principal controls the good or service before it is transferred to the customer and records gross revenue. An agent arranges for another party to provide the good or service and records only the net fee or commission. The distinction is determined by whether the entity controls the specified good or service before transfer, assessed using three indicators: primary responsibility for fulfillment, inventory risk, and pricing discretion.

How does ASC 606 interact with ASU 2021-08 in M&A transactions?

ASU 2021-08 requires that deferred revenue (contract liabilities) acquired in a business combination be measured under ASC 606, not at fair value. This means the acquirer must apply ASC 606 to the acquiree's contracts as if it had originated them. The result is that post-acquisition revenue is no longer suppressed by the fair-value write-down that applied under the prior rules.

Where can I find the primary source text for ASC 606?

The full standard is available at ASC Topic 606 on the FASB Codification. The leading practitioner references are the Deloitte Roadmap to Applying the New Revenue Recognition Standard, the PwC Revenue from Contracts with Customers guide, and the KPMG Revenue Recognition Handbook.