This site uses cookies to provide you with a more responsive and personalised service. By using this site you agree to our use of cookies. Please read our cookie notice for more information on the cookies we use and how to delete or block them.
The full functionality of our site is not supported on your browser version, or you may have 'compatibility mode' selected. Please turn off compatibility mode, upgrade your browser to at least Internet Explorer 9, or try using another browser such as Google Chrome or Mozilla Firefox.

ASC 606 — Revenue From Contracts With Customers

ASC 606, Revenue From Contracts With Customers, was issued jointly by the FASB and IASB on May 28, 2014. It was originally effective for annual reporting periods (including interim reporting periods within those periods) beginning after December 15, 2016, for public entities. Early application was not permitted (however, early adoption was optional for entities reporting under IFRSs). On August 12, 2015, the FASB issued an ASU, Revenue From Contracts With Customers (Topic 606): Deferral of the Effective Date, which deferred for one year the effective date of the new revenue standard for public and nonpublic entities reporting under U.S. GAAP. Therefore, for public business entities, certain not-for-profit entities, and certain employee benefit plans, the effective date for ASC 606 is annual reporting periods (including interim reporting periods within those periods) beginning after December 15, 2017. Early application is permitted only as of annual reporting periods (including interim reporting periods within those periods) beginning after December 15, 2016.

The effective date for all other entities is annual reporting periods beginning after December 15, 2018, and interim reporting periods within annual reporting periods beginning after December 15, 2019. All other entities may apply the ASU early as of an annual reporting period beginning after December 15, 2016, including interim reporting periods within that reporting period. All other entities also may apply ASC 606 early as of an annual reporting period beginning after December 15, 2016, and interim reporting periods within annual reporting periods beginning one year after the annual reporting period in which the entity first applies ASC 606.

Related resources

See our comprehensive collection of news and publications related to revenue as well as our project page detailing the progress of the FASB/IASB joint revenue project.


International guidance

For the IASB's guidance on revenue recognition, see IFRS 15, Revenue From Contracts With Customers.



The full text of ASC 606 can be found in the FASB Accounting Standards Codification (link to the FASB's Web site; registration required). Also, the full text of the Codification and Deloitte-authored Q&As related to the Codification are available in the Deloitte Accounting Research Tool (DART) Web site (subscription required).

ASC 606 provides accounting guidance related to revenue from contracts with customers. The guidance applies to all entities and to all contracts with customers, with the exception of the following transactions noted in ASC 606-10:


  1. Lease contracts within the scope of Topic 840, Leases.
  2. Insurance contracts within the scope of Topic 944, Financial Services—Insurance.
  3. Financial instruments and other contractual rights or obligations within the scope of the following Topics:
    1. Topic 310, Receivables
    2. Topic 320, Investments—Debt and Equity Securities
    3. Topic 323, Investments—Equity Method and Joint Ventures
    4. Topic 325, Investments—Other
    5. Topic 405, Liabilities
    6. Topic 470, Debt
    7. Topic 815, Derivatives and Hedging
    8. Topic 825, Financial Instruments
    9. Topic 860, Transfers and Servicing.
  4. Guarantees (other than product or service warranties) within the scope of Topic 460, Guarantees.
  5. Nonmonetary exchanges between entities in the same line of business to facilitate sales to customers or potential customers. For example, this Topic would not apply to a contract between two oil companies that agree to an exchange of oil to fulfill demand from their customers in different specified locations on a timely basis. Topic 845 on nonmonetary transactions may apply to nonmonetary exchanges that are not within the scope of this Topic.

ASC 606-10 provides the following overview of how revenue is recognized from an entity's contracts with customers:


The core principle of this Topic is that an entity recognizes revenue to depict the transfer of promised goods or services to customers in an amount that reflects the consideration to which the entity expects to be entitled in exchange for those goods or services.

An entity recognizes revenue in accordance with that core principle by applying the following steps:

  1. Step 1: Identify the contract(s) with a customer—A contract is an agreement between two or more parties that creates enforceable rights and obligations. The guidance in this Topic applies to each contract that has been agreed upon with a customer and meets specified criteria. In some cases, this Topic requires an entity to combine contracts and account for them as one contract. This Topic also provides requirements for the accounting for contract modifications. (See paragraphs 606-10-25-1 through 25-13.)
  2. Step 2: Identify the performance obligations in the contract—A contract includes promises to transfer goods or services to a customer. If those goods or services are distinct, the promises are performance obligations and are accounted for separately. A good or service is distinct if the customer can benefit from the good or service on its own or together with other resources that are readily available to the customer and the entity’s promise to transfer the good or service to the customer is separately identifiable from other promises in the contract. (See paragraphs 606-10-25-14 through 25-22.)
  3. Step 3: Determine the transaction price—The transaction price is the amount of consideration in a contract to which an entity expects to be entitled in exchange for transferring promised goods or services to a customer. The transaction price can be a fixed amount of customer consideration, but it may sometimes include variable consideration or consideration in a form other than cash. The transaction price also is adjusted for the effects of the time value of money if the contract includes a significant financing component and for any consideration payable to the customer. If the consideration is variable, an entity estimates the amount of consideration to which it will be entitled in exchange for the promised goods or services. The estimated amount of variable consideration will be included in the transaction price only to the extent that it is probable that a significant reversal in the amount of cumulative revenue recognized will not occur when the uncertainty associated with the variable consideration is subsequently resolved. (See paragraphs 606-10-32-2 through 32-27.)
  4. Step 4: Allocate the transaction price to the performance obligations in the contract—An entity typically allocates the transaction price to each performance obligation on the basis of the relative standalone selling prices of each distinct good or service promised in the contract. If a standalone selling price is not observable, an entity estimates it. Sometimes, the transaction price includes a discount or a variable amount of consideration that relates entirely to a part of the contract. The requirements specify when an entity allocates the discount or variable consideration to one or more, but not all, performance obligations (or distinct goods or services) in the contract. (See paragraphs 606-10-32-28 through 32-41.)
  5. Step 5: Recognize revenue when (or as) the entity satisfies a performance obligation—An entity recognizes revenue when (or as) it satisfies a performance obligation by transferring a promised good or service to a customer (which is when the customer obtains control of that good or service). The amount of revenue recognized is the amount allocated to the satisfied performance obligation. A performance obligation may be satisfied at a point in time (typically for promises to transfer goods to a customer) or over time (typically for promises to transfer services to a customer). For performance obligations satisfied over time, an entity recognizes revenue over time by selecting an appropriate method for measuring the entity’s progress toward complete satisfaction of that performance obligation. (See paragraphs 606-10-25-23 through 25-30.)

In addition, ASC 606-10 contains guidance on the disclosures related to revenue, and notes the following:


This Topic also includes a cohesive set of disclosure requirements that would result in an entity providing users of financial statements with comprehensive information about the nature, amount, timing, and uncertainty of revenue and cash flows arising from the entity’s contracts with customers. Specifically, Section 606-10-50 requires an entity to provide information about:

  1. Revenue recognized from contracts with customers, including the disaggregation of revenue into appropriate categories
  2. Contract balances, including the opening and closing balances of receivables, contract assets, and contract liabilities
  3. Performance obligations, including when the entity typically satisfies its performance obligations and the transaction price that is allocated to the remaining performance obligations in a contract
  4. Significant judgments, and changes in judgments, made in applying the requirements to those contracts.

Additionally, Section 340-40-50 requires an entity to provide quantitative and/or qualitative information about assets recognized from the costs to obtain or fulfill a contract with a customer.

Content from the FASB Accounting Standards Codification® included at is copyrighted by the Financial Accounting Foundation, 401 Merritt 7, PO Box 5116, Norwalk, CT 06856-5116, and is reproduced with permission.


FASB Accounting Standards Updates

The following ASUs amended the guidance in this Topic:


Proposed FASB Accounting Standards Updates

No current proposed ASUs on Topic 606.

Correction list for hyphenation

These words serve as exceptions. Once entered, they are only hyphenated at the specified hyphenation points. Each word should be on a separate line.