Home / Wiki / A / ASC 606

ASC 606

Accounting and Financial ManagementUpdated 16 Nov 2026

ASC 606 is the United States accounting standard for revenue from contracts with customers, codified as Topic 606 in the Accounting Standards Codification of the Financial Accounting Standards Board (FASB). It sets out when a company recognizes revenue and how much, using a single principles-based model for almost every industry. It applies to all entities reporting under US generally accepted accounting principles (GAAP), public and private.

The FASB issued the standard in May 2014 in a joint project with the International Accounting Standards Board (IASB), which published the closely matching IFRS 15 at the same time. The aim was to replace a patchwork of industry rules with one framework, so that revenue recognition would be comparable across companies and countries. Topic 606 took effect for public companies for annual periods beginning after 15 December 2017, which for most meant the 2018 calendar year.

01

Background and adoption

Before Topic 606, US GAAP contained many separate revenue rules for software, real estate, construction and other sectors, which could give different answers for economically similar transactions. Software companies, for example, needed vendor-specific objective evidence of fair value before they could recognize revenue separately for each element of a bundle, which often delayed revenue. The new standard replaced most of this guidance and added extensive disclosure requirements.

Companies could adopt it with a full retrospective method, restating prior years as if the standard had always applied, or a modified retrospective method, recording the cumulative effect in opening retained earnings at the adoption date. Private companies adopted later than public ones, after the FASB granted deferrals.

02

The five-step model

The core principle is that a company recognizes revenue to depict the transfer of promised goods or services to customers, in an amount that reflects the consideration it expects to be entitled to in exchange. The standard applies this through five steps:

  1. Identify the contract with a customer. A contract exists when the parties have approved it, each party's rights and the payment terms can be identified, it has commercial substance and collection of the consideration is probable.
  2. Identify the performance obligations. Each promise to transfer a distinct good or service, or a series of substantially identical services, is a performance obligation accounted for separately.
  3. Determine the transaction price. The transaction price is the consideration expected, including estimates of variable amounts such as discounts, rebates and usage fees, limited to amounts that are unlikely to reverse.
  4. Allocate the transaction price. The price is spread across the performance obligations in proportion to their standalone selling prices.
  5. Recognize revenue when or as each obligation is satisfied. An obligation is satisfied at a point in time, when control of the good passes, or over time, as the customer receives the benefit of the service.
03

Allocation formula and example

Step four normally uses a relative standalone selling price allocation:

Allocated pricei=Transaction price×SSPi∑SSP\text{Allocated price}_i = \text{Transaction price} \times \frac{\text{SSP}_i}{\sum \text{SSP}}
  • SSPi\text{SSP}_i is the standalone selling price of performance obligation ii, the price at which the company would sell it on its own.
  • ∑SSP\sum \text{SSP} is the total of the standalone selling prices of all obligations in the contract.
  • The transaction price is the total consideration for the whole contract.

Suppose a software company sells a one-year subscription and an onboarding training package together for $10,000. Sold separately, the subscription would cost $9,000 and the training $3,000, a total of $12,000. The subscription is allocated 10,000×9,000÷12,000=7,50010{,}000 \times 9{,}000 \div 12{,}000 = 7{,}500, or $7,500, and the training 10,000×3,000÷12,000=2,50010{,}000 \times 3{,}000 \div 12{,}000 = 2{,}500, or $2,500. The training revenue is recognized when the sessions are delivered, while the subscription revenue is recognized evenly at $625 a month over the year.

04

Application to subscription businesses

For software as a service (SaaS) and other subscription businesses, access to a hosted service is usually a stand-ready obligation satisfied over time, so revenue is recognized evenly across the service period. When a customer pays a year in advance, the cash received ahead of performance is a contract liability, commonly called deferred revenue, which is released month by month. Where a company has performed but its right to payment depends on something other than the passage of time, it records a contract asset rather than a receivable.

Several issues come up often in subscription billing:

  • Setup fees. An up-front setup fee is frequently not a distinct service, so it is recognized over the contract term, or longer if it gives the customer a material right to renew.
  • Usage-based fees. Variable charges tied to consumption are generally recognized in the period the usage occurs.
  • Contract modifications. Upgrades, downgrades and extra seats added mid-term are treated either as separate contracts or as changes to the existing one, depending on whether they add distinct services at their standalone prices.
  • Contract costs. Related guidance in ASC 340-40 requires incremental costs of obtaining a contract, such as sales commissions, to be capitalized and amortized, with a practical expedient for amortization periods of one year or less.
05

Relationship with IFRS 15

ASC 606 and IFRS 15 share the same core principle and five-step model, and most transactions produce the same result under both. Differences remain in areas such as the collectibility threshold, where "probable" carries a higher bar in US GAAP, the treatment of shipping and handling and of sales taxes, licenses of intellectual property and interim disclosures. Operating metrics such as billings and annual recurring revenue (ARR) are not defined by either standard; companies that publish them present them separately from reported revenue.

Last updated 16 Nov 2026