What are the five steps of the ASC 606 revenue recognition model?

The ASC 606 five-step revenue recognition model is, in order: (1) identify the contract with the 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. The five steps run in sequence, and each one feeds the next. Lightbridge ERP configures ERP systems so the five-step revenue recognition flow runs inside the platform rather than in spreadsheets.

Did ASC 606 replace ASC 605?

ASC 606 superseded most of legacy ASC 605 and most industry-specific revenue guidance under U.S. GAAP, though not literally every prior rule. It was issued jointly with the IASB and converged with IFRS 15, so the revenue recognition principle is now broadly aligned across U.S. GAAP and international standards. Public entities adopted ASC 606 for annual periods beginning after December 15, 2017, with private entities following one year later. The codified standard is maintained by the FASB at asc.fasb.org.

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

Under ASC 606, revenue is recognized over time when one of three criteria is met: the customer receives and consumes the benefit as the entity performs, the entity creates or enhances an asset the customer controls, or the asset has no alternative use and the entity has an enforceable right to payment for performance completed to date. If none of those apply, revenue is recognized at the single point in time when control transfers. Subscription and service contracts often recognize over time; product sales often recognize at a point in time.

How does ASC 606 treat deferred revenue?

When a customer pays before the entity satisfies its performance obligation, ASC 606 records the amount as a contract liability, commonly called deferred revenue or unearned revenue. The standard does not mandate that exact label on the face of the financial statements. The balance stays a liability until the obligation is satisfied, at which point it is recognized as revenue under step five. Our deferred revenue guide covers the contract-liability mechanics in detail.

What is the revenue recognition principle behind ASC 606?

The revenue recognition principle behind ASC 606 is that an entity recognizes revenue to depict the transfer of promised goods or services to a customer in an amount that reflects the consideration the entity expects to receive in exchange. Control, not cash, is the trigger: revenue is earned when control transfers, regardless of when payment arrives. This is why a prepaid annual contract recognizes revenue across the service period rather than all at once. The five-step model is the mechanism that applies this principle in practice.

How does ASC 606 apply to SaaS and subscription revenue?

For software-as-a-service and subscription businesses, ASC 606 usually identifies access to the hosted service as a single performance obligation satisfied over time, so revenue is recognized ratably across the subscription term. Usage-based fees, setup charges, and bundled professional services each require their own step-two and step-four analysis. Our SaaS revenue recognition guide works through these subscription-specific patterns under ASC 606.

Why do ASC 606 implementations fail?

ASC 606 implementations usually fail for design reasons, not accounting-standard reasons. The most common cause is configuring the system before the accounting policy is settled, so the performance obligations, standalone selling prices, and recognition triggers in the system do not match how the business actually contracts. Undocumented or inconsistent standalone selling prices, ad hoc handling of variable consideration and contract modifications, and revenue objects misaligned with policy all produce inconsistent revenue even when the arithmetic is correct. The fix is sequence: settle accounting policy first, then translate it into the system. Lightbridge ERP grounds every revenue configuration in policy before a single rule is built.

How does ASC 606 connect to sales commission accounting?

ASC 606 travels with ASC 340-40, which governs the incremental costs of obtaining a contract, such as sales commissions. Those costs are capitalized as a contract asset and amortized over the period of benefit (often the expected customer life, including anticipated renewals, frequently longer than the initial contract term) when recovery is expected. A practical expedient allows expensing as incurred only if the amortization period would be one year or less. Our sales commission accounting guide details the ASC 340-40 treatment.

JH Written by Jully Hayasaka with Robert LabardeeNetSuite Advanced Accounting Lead and Founder and CEO

Published June 2026. Last updated July 2026.

ASC 606 Revenue Recognition: The Five-Step Model

Lightbridge ERP defines ASC 606 as the U.S. GAAP standard for revenue recognition from contracts with customers, built on a five-step model. It directs an entity to recognize revenue when control of a promised good or service transfers, in the amount expected in exchange. ASC 606 superseded most legacy guidance and converged with IFRS 15.

Talk to an ERP advisor SaaS revenue recognition

This guide is general information, not accounting, tax, or legal advice. The authoritative text is the FASB Accounting Standards Codification at asc.fasb.org.

ASC 606 is the U.S. GAAP standard for revenue from contracts with customers.

ASC 606, titled Revenue from Contracts with Customers, sets a single principle for recognizing revenue across industries. It directs an entity to recognize revenue to depict the transfer of promised goods or services in the amount the entity expects to receive in exchange. The Financial Accounting Standards Board issued it as Accounting Standards Update 2014-09 and codified it at asc.fasb.org.

ASC 606 superseded most of legacy ASC 605 and most industry-specific revenue rules under U.S. GAAP. It did not replace every prior rule, but it consolidated a fragmented set of standards into one model. The FASB developed it jointly with the IASB, so ASC 606 converged with IFRS 15, the parallel international standard. Public entities adopted ASC 606 for annual periods beginning after December 15, 2017, and most private entities one year later.

The practical shift was from rules tied to specific industries to a principle tied to control. Revenue is earned when control of a good or service transfers to the customer, not when an invoice is sent or cash arrives. This is general information and not accounting advice, but it is the foundation every revenue process in an ERP system has to encode.

ASC 606 applies a five-step revenue recognition model, in order.

The core of ASC 606 is a five-step model that runs in sequence. Each step narrows the question from "is there a contract" down to "how much revenue, and when." The five steps below are the structure every revenue recognition decision under ASC 606 follows.

Step 1

Identify the contract with the customer

A contract exists when parties have approved it, rights and payment terms are identifiable, the agreement has commercial substance, and collection of the consideration is probable. Under ASC 606, this gate determines whether revenue accounting begins at all.

Step 2

Identify the performance obligations

Within the contract, each distinct good or service (or distinct bundle) is a separate performance obligation. ASC 606 treats a distinct promise as one the customer can benefit from on its own and that is separable from other promises in the contract.

Step 3

Determine the transaction price

The transaction price is the consideration an entity expects to receive in exchange for the goods or services. Under ASC 606 this includes variable consideration (discounts, rebates, refunds), significant financing components, noncash consideration, and amounts payable to the customer.

Step 4

Allocate the transaction price

The transaction price is allocated to each performance obligation in proportion to its standalone selling price. ASC 606 requires this allocation so that revenue attaches to the specific promises a contract bundles, not to the contract as an undivided whole.

Step 5

Recognize revenue as obligations are satisfied

Revenue is recognized when (or as) the entity satisfies a performance obligation by transferring control to the customer. Under ASC 606 this happens either over time or at a single point in time, depending on how control passes.

The five-step revenue recognition model is the spine of ASC 606. NetSuite implements it through native revenue recognition tooling: see how NetSuite Advanced Revenue Management automates step four and step five, and how NetSuite SuiteBilling handles subscription billing that feeds the model.

ASC 606 recognizes revenue either over time or at a point in time.

Step five of ASC 606 splits into two timing patterns. The default question is whether control transfers continuously or in a single moment. The three cards below set out the over-time criteria, the point-in-time indicators, and how an entity measures progress when recognition is spread over a period.

Recognized over time

ASC 606 requires over-time recognition when one of three criteria is met: the customer simultaneously receives and consumes the benefit as the entity performs, the entity creates or enhances an asset the customer controls, or the asset has no alternative use and the entity holds an enforceable right to payment for work completed. Subscriptions and many services fall here.

Recognized at a point in time

When none of the over-time criteria apply, ASC 606 recognizes revenue at the point control transfers. Indicators of that transfer include a present right to payment, legal title, physical possession, the risks and rewards of ownership, and customer acceptance. Most product sales and perpetual licenses fall here.

Measuring progress over time

For over-time obligations, ASC 606 calls for a single method that faithfully depicts progress: an output method (units delivered, milestones, time elapsed) or an input method (costs incurred, labor hours). The method should reflect the pattern in which control transfers, applied consistently across similar obligations.

ASC 606 creates contract liabilities and connects to contract cost rules.

When a customer pays before an obligation is satisfied, ASC 606 records a contract liability, commonly labeled deferred or unearned revenue, though the standard does not require that exact wording on the face of the statements. The balance remains a liability until the performance obligation is satisfied and step five recognizes it as revenue. Our deferred revenue guide walks through that mechanic in full.

ASC 606 also travels with ASC 340-40, which governs the incremental costs of obtaining a contract. Sales commissions are capitalized as a contract asset and amortized over the period of benefit, often the expected customer life including anticipated renewals, when recovery is expected. A practical expedient permits expensing as incurred only when the amortization period would be one year or less. Our sales commission accounting guide covers ASC 340-40 in depth.

Subscription businesses sit squarely inside these rules: recurring access is usually one over-time obligation, while setup fees, usage charges, and bundled services each get their own analysis. Our SaaS revenue recognition guide applies ASC 606 to the subscription model end to end.

Most ASC 606 problems come from policy gaps, not the standard.

Organizations that struggle with ASC 606 usually do not struggle with the standard itself. They struggle because the accounting system was configured before the accounting policy was settled, so the model does not reflect how the business actually contracts. The order matters: decide the policy first, then translate it into the system. Before any configuration, a finance team should settle how performance obligations are identified, how variable consideration and contract modifications are treated, and what triggers recognition, whether time-based, milestone, delivery, or usage. Once those decisions exist, the system build becomes a translation exercise rather than a guess.

The recurring failure modes are consistent across platforms: performance obligations that do not match the real contract, standalone selling prices that are undocumented or applied inconsistently, and revenue objects that are misaligned with policy, which produces inconsistent revenue even when the math is technically correct. These are design problems, not arithmetic problems. On NetSuite, the mechanics of that translation live in Advanced Revenue Management, and the broader reasons finance-system projects go wrong are covered in the guide on why ERP implementations fail.

Lightbridge ERP turns ASC 606 revenue recognition into a working ERP process.

Knowing the ASC 606 five-step model is one thing. Encoding it in an ERP so revenue posts correctly every period is another. Lightbridge ERP is an independent, vendor-neutral advisory firm whose senior finance professionals (CPAs, controllers, and former CFOs) design revenue recognition configurations that map performance obligations, standalone selling prices, and over-time schedules to the system that actually runs the books.

Because Lightbridge accepts no vendor kickbacks, no reseller quotas, and no partner-tier incentives, the platform recommendation follows fit, not commission. For organizations already on NetSuite, the practice delivers ASC 606 automation in-house through native revenue tooling. For other platforms, Lightbridge provides program governance and technical leadership while vetted partners execute. Either way, the goal is the same: an auditable revenue recognition process that satisfies ASC 606 without spreadsheets. This page is general information, not accounting, tax, or legal advice.

ASC 606 revenue recognition: frequently asked questions

What is ASC 606 revenue recognition?: ASC 606, Revenue from Contracts with Customers, is the U.S. GAAP standard that governs how and when an entity recognizes revenue. It replaced a patchwork of industry-specific rules with a single principle: recognize revenue to depict the transfer of promised goods or services in the amount the entity expects in exchange. The standard is applied through a five-step model. ASC 606 was issued as Accounting Standards Update 2014-09 and is codified by the FASB at asc.fasb.org. This guide is general information, not accounting, tax, or legal advice.
What are the five steps of the ASC 606 revenue recognition model?: The ASC 606 five-step revenue recognition model is, in order: (1) identify the contract with the 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. The five steps run in sequence, and each one feeds the next. Lightbridge ERP configures ERP systems so the five-step revenue recognition flow runs inside the platform rather than in spreadsheets.
Did ASC 606 replace ASC 605?: ASC 606 superseded most of legacy ASC 605 and most industry-specific revenue guidance under U.S. GAAP, though not literally every prior rule. It was issued jointly with the IASB and converged with IFRS 15, so the revenue recognition principle is now broadly aligned across U.S. GAAP and international standards. Public entities adopted ASC 606 for annual periods beginning after December 15, 2017, with private entities following one year later. The codified standard is maintained by the FASB at asc.fasb.org.
When is revenue recognized over time versus at a point in time under ASC 606?: Under ASC 606, revenue is recognized over time when one of three criteria is met: the customer receives and consumes the benefit as the entity performs, the entity creates or enhances an asset the customer controls, or the asset has no alternative use and the entity has an enforceable right to payment for performance completed to date. If none of those apply, revenue is recognized at the single point in time when control transfers. Subscription and service contracts often recognize over time; product sales often recognize at a point in time.
How does ASC 606 treat deferred revenue?: When a customer pays before the entity satisfies its performance obligation, ASC 606 records the amount as a contract liability, commonly called deferred revenue or unearned revenue. The standard does not mandate that exact label on the face of the financial statements. The balance stays a liability until the obligation is satisfied, at which point it is recognized as revenue under step five. Our deferred revenue guide covers the contract-liability mechanics in detail.
What is the revenue recognition principle behind ASC 606?: The revenue recognition principle behind ASC 606 is that an entity recognizes revenue to depict the transfer of promised goods or services to a customer in an amount that reflects the consideration the entity expects to receive in exchange. Control, not cash, is the trigger: revenue is earned when control transfers, regardless of when payment arrives. This is why a prepaid annual contract recognizes revenue across the service period rather than all at once. The five-step model is the mechanism that applies this principle in practice.
How does ASC 606 apply to SaaS and subscription revenue?: For software-as-a-service and subscription businesses, ASC 606 usually identifies access to the hosted service as a single performance obligation satisfied over time, so revenue is recognized ratably across the subscription term. Usage-based fees, setup charges, and bundled professional services each require their own step-two and step-four analysis. Our SaaS revenue recognition guide works through these subscription-specific patterns under ASC 606.
Why do ASC 606 implementations fail?: ASC 606 implementations usually fail for design reasons, not accounting-standard reasons. The most common cause is configuring the system before the accounting policy is settled, so the performance obligations, standalone selling prices, and recognition triggers in the system do not match how the business actually contracts. Undocumented or inconsistent standalone selling prices, ad hoc handling of variable consideration and contract modifications, and revenue objects misaligned with policy all produce inconsistent revenue even when the arithmetic is correct. The fix is sequence: settle accounting policy first, then translate it into the system. Lightbridge ERP grounds every revenue configuration in policy before a single rule is built.
How does ASC 606 connect to sales commission accounting?: ASC 606 travels with ASC 340-40, which governs the incremental costs of obtaining a contract, such as sales commissions. Those costs are capitalized as a contract asset and amortized over the period of benefit (often the expected customer life, including anticipated renewals, frequently longer than the initial contract term) when recovery is expected. A practical expedient allows expensing as incurred only if the amortization period would be one year or less. Our sales commission accounting guide details the ASC 340-40 treatment.

From the ASC 606 model to a revenue process that runs itself.

When revenue recognition has to be right every period, Lightbridge ERP configures the five-step model into your ERP and keeps it audit-ready. Vendor-neutral, no kickbacks, senior finance talent.

Talk to an ERP advisor Read the deferred revenue guide