What Is Revenue Recognition Under Asc 606

By Kevin Fernando · Oct 7, 2026 · 10 min read

ASC 606 is the accounting standard that tells companies when and how to recognize revenue from customer contracts. It replaced five separate older standards with one unified model based on a five-step process: identify the contract, identify performance obligations, determine the transaction price, allocate the price, and recognize revenue when obligations are satisfied.

ASC 606 is the accounting standard that defines when a company recognizes revenue from customer contracts. Adopted by public companies for fiscal years beginning after December 15, 2017, it replaced five separate older standards with a single unified approach. The standard matters because it determines not just the amount of revenue a company reports, but the timing: revenue can be recognized before cash arrives, after it arrives, or in pieces over time, depending on the structure of the contract and the nature of the performance obligation.

Understanding ASC 606 is essential for anyone reading financial statements. The standard's five-step model forces companies to decompose contracts into their economic components and recognize revenue for each one as it is earned. This transparency reveals how a business actually generates value for customers, but it also creates complexity: variable consideration, contract modifications, and the distinction between point-in-time and over-time recognition all affect when revenue appears on the income statement. The timing of revenue recognition does not change cash flow, but it does change the financial ratios and trends investors use to assess performance.

What ASC 606 revenue recognition actually is

ASC 606 is the accounting standard that defines when a company recognizes revenue from customer contracts. It replaced five separate older standards with one unified framework. The standard applies to all contracts with customers, whether the customer is a consumer, a business, or a government entity. Revenue recognition under ASC 606 is not about cash: a company can recognize revenue before it receives payment, after it receives payment, or in installments over time. The standard defines revenue as the amount of consideration the company expects to receive in exchange for transferring goods or services to the customer. That consideration is usually money, but it can also be other assets or the settlement of liabilities. The core principle is that revenue is recognized when the company satisfies a performance obligation, meaning when it has transferred control of a promised good or service to the customer.

The five-step ASC 606 model

ASC 606 requires companies to follow a five-step process to determine when and how much revenue to recognize. The steps are sequential: each one builds on the previous one, and a company must work through all five before recording revenue. The process is designed to be applied consistently across industries and contract types, from software licenses to construction projects to retail sales. Working through the steps forces a company to decompose each contract into its economic components and recognize revenue for each component as it is earned, rather than treating the entire contract as a single revenue event.

Step 1: Identify the contract with a customer

A contract exists when the parties have committed to perform their obligations, the payment terms are identified, and it is probable the company will collect the consideration. ASC 606 applies only to contracts that meet these criteria. A contract can be written, oral, or implied by business practice, but the company must have evidence that both parties are committed. If a company has not yet received a signed purchase order or if the customer is unlikely to pay, no contract exists yet under ASC 606, and revenue recognition does not begin. This step screens out hypothetical or uncertain arrangements and ensures that revenue is recognized only for transactions with a real economic substance.

Step 2: Identify the performance obligations

A performance obligation is a promise to transfer a good or service to the customer. A single contract can contain multiple performance obligations. The company must identify each distinct promise separately. A promise is distinct if the customer can benefit from the good or service on its own or with other resources readily available to the customer, and the company's promise to transfer it is separately identifiable from other promises in the contract. This step prevents bundling: if a contract includes both a product and installation, those are two separate performance obligations. If a contract includes a product and a three-year service agreement, those are also separate. The company must recognize revenue for each obligation as it is satisfied, not as a single lump sum when the contract is signed.

Step 3: Determine the transaction price

The transaction price is the total amount of consideration the company expects to receive in exchange for satisfying the performance obligations. In the simplest case, it is the price stated in the contract. But contracts often include variable consideration: discounts, rebates, volume bonuses, penalties, or refund rights. The company must estimate the variable consideration and include it in the transaction price, but only to the extent it is probable the estimate will not reverse later. This constraint is called the "constraint on variable consideration." If a company is uncertain whether a customer will exercise a refund right, it must estimate conservatively. If a contract offers a 20 percent volume discount if the customer purchases more than 100 units, the company must estimate whether the customer will reach that threshold and adjust the transaction price accordingly. The transaction price is not necessarily the cash price: it is the amount of consideration the company is entitled to receive under the terms of the contract.

Step 4: Allocate the price to performance obligations

When a contract contains multiple performance obligations, the company must allocate the transaction price to each one. The allocation is based on the standalone selling price of each good or service: the price at which the company would sell that item on its own, without the other items in the contract. If the standalone selling price is observable, the company uses it directly. If it is not observable, the company estimates it using methods like the expected cost plus margin approach or the adjusted market assessment approach. The allocation determines how much revenue is assigned to each obligation, which in turn determines when revenue is recognized: an obligation satisfied at a point in time generates revenue immediately, while an obligation satisfied over time generates revenue gradually.

Step 5: Recognize revenue when performance obligations are satisfied

Revenue is recognized when the company satisfies a performance obligation by transferring control of the promised good or service to the customer. The timing depends on the nature of the obligation. Some obligations are satisfied at a point in time: the company transfers control in a single moment, and revenue is recognized all at once. Other obligations are satisfied over time: the company transfers control gradually, and revenue is recognized as the transfer occurs. An obligation is satisfied over time if the customer simultaneously receives and consumes the benefit of the company's performance, or if the company's performance creates an asset that the customer controls, or if the company's performance does not create an alternative use asset and the company has an enforceable right to payment for performance completed to date. A retail sale is typically satisfied at a point in time: control transfers when the customer receives the goods. A construction contract is typically satisfied over time: the customer controls the asset as it is built, so revenue is recognized as the construction progresses. A software-as-a-service contract is satisfied over time: the customer receives and consumes the service continuously.

How ASC 606 changes what revenue looks like

ASC 606 changed revenue recognition timing for many companies, particularly those with long-term contracts or bundled offerings. Under older standards, companies had more discretion about when to recognize revenue, and different industries followed different rules. ASC 606 unified the approach and forced companies to recognize revenue based on when they satisfied performance obligations, not when they received cash or when the contract was signed. Consider a software company that sells a perpetual license plus three years of support. Under older standards, the company might recognize the entire revenue when the customer signed the contract. Under ASC 606, the company must split the contract into two performance obligations: the license and the support service. The license is satisfied at a point in time when the customer gains access to the software, so revenue for the license is recognized immediately. The support service is satisfied over time as the company provides support throughout the three-year period, so revenue for the support is recognized ratably over three years. The total revenue from the contract is the same, but it is spread across time rather than recognized upfront. This change affects not just the income statement but also the balance sheet: the company records deferred revenue (a liability) for the support obligation and recognizes it gradually as the obligation is satisfied. The timing of revenue recognition also affects operating cash flow: revenue is recognized when the obligation is satisfied, but cash may have been received earlier, creating a difference between net income and operating cash flow.

Why revenue recognition timing matters to investors

Revenue recognition timing affects the financial ratios and trends that investors use to assess a company's performance. If a company recognizes revenue early, its revenue and net income appear higher in the near term, but future periods show slower growth. If a company recognizes revenue late, the opposite occurs. Investors need to understand a company's revenue recognition policy to compare it fairly to competitors and to assess whether reported growth is sustainable. Revenue recognition also reveals the company's business model. A company that recognizes revenue over time typically has long-term customer relationships and recurring revenue. A company that recognizes revenue at a point in time typically has transactional relationships. The timing of revenue recognition also affects operating cash flow. If a company receives cash upfront but recognizes revenue over time, its operating cash flow is higher than its net income in the near term. If a company recognizes revenue upfront but receives cash over time, its operating cash flow is lower than its net income. Understanding these differences helps investors assess the quality of a company's earnings and its ability to fund operations and growth.

Common edge cases and misreadings

The most frequent misreading of ASC 606 is treating revenue recognition and cash receipt as identical. They are not. A company can recognize revenue before it receives cash, after it receives cash, or in pieces over time. If a company sells goods on credit, it recognizes revenue when the customer receives the goods, not when the customer pays the invoice. If a company receives a deposit upfront but does not deliver the goods until later, it recognizes revenue when it delivers the goods, not when it receives the deposit. Another common confusion is between revenue recognition and the satisfaction of performance obligations. A performance obligation is satisfied when the company transfers control of the promised good or service to the customer. Revenue is recognized at that moment. But "control" is an accounting concept, not a legal one. Control transfers when the customer has the ability to direct the use of the asset and obtain substantially all of the remaining benefits. This can happen before or after the customer takes physical possession. A third edge case is contract modifications. If a customer requests a change to a contract after it has been signed, the company must determine whether the modification is a separate contract or a modification of the existing contract. If it is a separate contract, the company applies the five-step model to the modification. If it is a modification of the existing contract, the company may need to recalculate the transaction price and re-allocate it to the performance obligations, which can change when revenue is recognized. Variable consideration is also frequently misunderstood. The company must estimate variable consideration and include it in the transaction price, but only to the extent it is probable the estimate will not reverse later. If a company is uncertain, it must estimate conservatively. This constraint prevents companies from inflating revenue based on optimistic assumptions about discounts or rebates.

How ASC 606 connects to other financial statement items

Revenue recognition decisions flow directly into other financial statement items and ratios. When a company recognizes revenue, it typically records an increase in accounts receivable or a decrease in deferred revenue. Accounts receivable represents amounts owed by customers for goods or services already delivered. Deferred revenue represents amounts received from customers for goods or services not yet delivered. If a company receives cash upfront but recognizes revenue over time, deferred revenue decreases as revenue is recognized. If a company recognizes revenue before receiving cash, accounts receivable increases. These balance sheet changes affect operating cash flow. Operating cash flow is calculated by starting with net income and adjusting for non-cash items and changes in working capital. An increase in accounts receivable reduces operating cash flow because the company has recognized revenue but not yet received cash. A decrease in deferred revenue increases operating cash flow because the company received cash in a prior period and is now recognizing revenue. Understanding these connections helps investors trace the impact of revenue recognition choices through the entire financial statement. A company with growing deferred revenue may have strong future revenue visibility. A company with growing accounts receivable may have collection risk or may be extending credit terms to customers. A company whose operating cash flow is significantly lower than its net income may be recognizing revenue before receiving cash, which could signal aggressive revenue recognition or a shift in customer payment terms.

Do this automatically

A finance team manually applying the five-step ASC 606 model across multiple customer contracts must allocate hours to identifying each performance obligation, determining transaction prices, and allocating those prices to separate obligations, work that multiplies in complexity with contract volume and frequency. Software platforms can automate these sequential steps across all contracts simultaneously, reducing the manual effort required to ensure consistent revenue recognition. Financial research runs this kind of analysis end to end and cites every figure back to its original source, across as many subjects as you need, with Mimir attaching a citation to every figure. It will not tell you whether to buy the stock. That judgment stays yours, and deliberately so. Every plan includes it, including the free one.

Start your first report and run it on something you already know well.

This article is general research and information about financial concepts. It is not investment advice, and it does not account for your circumstances or objectives. Nothing here is a recommendation to buy, sell, or hold any security.