Revenue Recognition Examples: ASC 606 Allocation and Journal Entries

Revenue recognition is the accounting rule that decides when, and how much, revenue a company records. Under ASC 606 (US GAAP) and IFRS 15, a company recognizes revenue when it transfers control of promised goods or services to a customer, in the amount it expects to be entitled to, using a five-step model.

This application guide focuses on allocating a bundled contract price, choosing over-time or point-in-time recognition, and recording revenue, contract assets, and contract liabilities. It applies ASC 606 under U.S. GAAP; IFRS 15 comparisons are identified separately. For an introduction, begin with our five-step revenue recognition overview and contract criteria.

What Are The 5 Steps Of Revenue Recognition Under ASC 606?

The rules come from two converged standards. ASC 606, Revenue from Contracts with Customers, is issued by the Financial Accounting Standards Board (FASB) for US GAAP. IFRS 15 is issued by the International Accounting Standards Board (IASB) for companies that report under IFRS. Both use the same five-step model.

Here’s the five-step model at a glance, followed by a closer look at each step.

Step	What you do	Key question
1. Identify the contract	Confirm an enforceable agreement exists and meets the ASC 606 contract criteria	Is there a valid contract?
2. Identify the performance obligations	List each distinct good or service promised	What exactly did we promise?
3. Determine the transaction price	Measure the consideration you expect to be entitled to, including variable amounts	How much do we expect to get?
4. Allocate the transaction price	Split the price across obligations using relative stand-alone selling prices	How much belongs to each promise?
5. Recognize revenue	Record revenue when (or as) control transfers to the customer	When is each promise satisfied?

Step 1: Identify The Contract(s) With A Customer

Objective: Establish the legal agreement that creates enforceable rights and obligations.

Key Actions:

• Legal Enforceability: Contracts must be enforceable by law. This involves assessing the legal framework in the relevant jurisdictions and ensuring that the contract has clear terms regarding goods or services to be provided and payment terms.
• Commercial Substance: The contract must have commercial substance, meaning that the risk, timing, or amount of the company’s future cash flows is expected to change as a result of the contract.
• Approval and Commitment: Both parties to the contract must approve the contract (in writing, orally, or by other business practices) and are committed to fulfilling their respective obligations.
• Rights Identification: Identify the rights regarding goods or services to be provided.
• Payment Terms: The terms for payment for those goods or services must be identified and agreed upon.
• Collectability is Probable: It must be probable that the entity will collect substantially all of the consideration it will be entitled to for the goods or services that will be transferred. Only the customer’s ability and intention to pay count here. Watch the wording: under US GAAP, ‘probable’ means likely to occur, while IFRS 15 uses ‘more likely than not,’ which is a lower bar.

Step 2: Identify the Performance Obligations in the Contract

Objective: Determine the distinct goods or services promised to the customer.

Key Actions:

• Distinct Goods or Services: A good or service is distinct if the customer can benefit from the good or service on its own or together with other readily available resources, and if the entity’s promise to transfer the good or service is separately identifiable from other promises in the contract.
• Bundling and Unbundling: Businesses need to carefully evaluate their offerings to determine whether they consist of multiple performance obligations. This may involve unbundling bundled goods and services or combining multiple goods and services into a single performance obligation if they are not distinct.

Step 3: Determine the Transaction Price

Objective: Calculate the amount of consideration to which the entity expects to be entitled.

Key Actions:

• Variable Consideration and Constraints: Estimate the amount of consideration, which may include discounts, rebates, refunds, credits, incentives, and penalties. When estimating variable consideration, entities must consider the constraint on variable consideration to prevent overestimation of the transaction price.
• Financing Component: Adjust the transaction price for the time value of money when payment terms provide a significant financing benefit. A timing difference alone does not establish financing: some terms protect a party against nonperformance or serve another purpose. A practical expedient permits no financing adjustment when the expected period between transfer and payment is one year or less.
• Non-cash Consideration: Under ASC 606, measure noncash consideration at fair value at contract inception. If fair value cannot be reasonably estimated, measure it indirectly using the stand-alone selling price of the goods or services promised. This contract-inception measurement date is U.S. GAAP guidance; IFRS 15 does not prescribe the same measurement date.
• Consideration Payable to a Customer: Amounts you pay or owe to the customer (such as coupons, credits, or slotting fees) reduce the transaction price, unless the payment is for a distinct good or service the customer provides to you.

Step 4: Allocate the Transaction Price to the Performance Obligations in the Contract

Objective: Distribute the transaction price to each performance obligation based on their stand-alone selling prices.

Key Actions

• Stand-Alone Selling Price (SSP): The transaction price is allocated to each performance obligation based on its SSP, which is the price at which an entity sells a promised good or service separately to a customer.
• Estimating SSP: If a stand-alone selling price is not directly observable, it must be estimated. Methods for estimating SSP include the adjusted market assessment approach, the expected cost plus a margin approach, and the residual approach. The residual approach is allowed only when the selling price is highly variable or uncertain.
• Allocation Based on SSPs: Generally, divide the transaction price in proportion to each performance obligation’s SSP. Specific exceptions allow qualifying discounts or variable consideration to be allocated to particular obligations.

Step 5: Recognize Revenue When (or As) the Entity Satisfies a Performance Obligation

Objective: Recognize revenue when the promised good or service is transferred to the customer, and the customer gains control over it.

Key Actions

• Transfer of Control: Revenue is recognized when control of the promised goods or services is transferred to the customer, which can occur over time or at a point in time.
• Over Time Recognition: Revenue is recognized over time only if at least one of these three criteria is met: (1) the customer receives and uses the benefit as you perform, like a monthly cleaning service; (2) your work creates or improves an asset the customer already controls, like a renovation on the customer’s building; or (3) your work creates an asset with no alternative use to you, and you have an enforceable right to payment for work completed to date, like a custom machine built to one customer’s specs. When a criterion is met, measure progress with an output method (for example, units delivered or milestones reached) or an input method (for example, costs incurred or labor hours used).
• At a Point in Time Recognition: If none of the three over-time criteria is met, revenue is recognized at a point in time, the moment the customer obtains control. Control means the customer can direct the use of the asset and obtain substantially all of its remaining benefits. ASC 606 lists five indicators that control has passed: (1) you have a present right to payment, (2) the customer has legal title, (3) the customer has physical possession, (4) the customer has the significant risks and rewards of ownership, and (5) the customer has accepted the asset. No single indicator decides it on its own.

Watch: The Five-Step Revenue Recognition Model

Review the five steps with Professor Farhat, then follow an illustrative aircraft transaction from the customer contract through revenue recognition. This focused segment runs from 4:59 to 8:26. The aircraft example assumes that control transfers upon delivery.

How Revenue Is Recognized In Practice: Over Time Vs. At A Point In Time

Under ASC 606, every performance obligation is recognized in one of two ways: over time or at a point in time. Older US GAAP (ASC 605) had separate industry methods, such as the completed-contract method and the milestone method. ASC 606 replaced them with the single five-step model. Here’s how common business situations work today.

Point In Time: Retail And Product Sales

A bookstore sells a $30 book at the register. The customer walks out with the book, so control transfers immediately and the bookstore records the sale right away (ignoring sales tax and expected returns).

Account	Debit	Credit
Cash	$30
Revenue		$30

Over Time: Long-Term Construction Contracts

A construction company signs a $10,000,000 contract to build an office building on the customer’s land. Because the customer controls the building as it goes up, revenue is recognized over time. The company measures progress as costs incurred to date divided by total expected costs, which is called a cost-to-cost input method. Many textbooks and exam questions still call this the percentage-of-completion method.

• Total expected costs: $8,000,000
• Costs incurred in Year 1: $3,200,000
• Progress: $3,200,000 ÷ $8,000,000 = 40%
• Year 1 revenue: $10,000,000 × 40% = $4,000,000
• Year 1 gross profit: $4,000,000 minus $3,200,000 = $800,000

When Progress Can’t Be Measured Reasonably

If a company can’t reasonably measure its progress but expects to recover its costs, ASC 606 says to recognize revenue only up to the costs incurred (no profit) until progress can be measured. The obligation remains eligible for over-time recognition; this cost-recovery approach applies until progress can be measured reasonably. If a contract doesn’t meet any of the three over-time criteria, revenue is recognized at a point in time, often when the finished project is handed over.

Subscriptions And SaaS

A customer pays $1,200 upfront for a one-year SaaS subscription. SaaS (software as a service) means cloud software the customer accesses online instead of installing it. The company provides the service every day, so it recognizes $100 of revenue each month ($1,200 ÷ 12).

Entry	Account	Debit	Credit
Upon receipt of upfront payment	Cash	$1,200
Upon receipt of upfront payment	Contract liability (deferred revenue)		$1,200
Each month	Contract liability (deferred revenue)	$100
Each month	Revenue		$100

Exam trap: a software license is different. If the customer gets a one-year license to software it downloads and runs on its own computers, that’s a right to use functional intellectual property. The license revenue is generally recognized at the point in time the customer can start using the software, not spread over the year. Any separate support or updates are still recognized over time.

Milestone Payments

ASC 606 also retired the old milestone method. Today, a milestone can serve as an output measure of progress. A milestone payment that depends on an uncertain event, like a regulatory approval, is treated as variable consideration. The company includes it in the transaction price only when it’s probable that including it won’t cause a significant reversal of revenue later. For a biotech firm doing contract research, that often means an approval-based payment stays out of revenue until the approval is essentially assured.

Challenges In Applying ASC 606

• Estimation and Judgment: Measuring progress over time and estimating variable consideration both require significant estimates, and those estimates are updated every reporting period.
• Compliance and Consistency: Companies must apply ASC 606 or IFRS 15 consistently across similar contracts and over time.
• Complex Contracts: Multiple performance obligations, variable consideration, rights of return, and contract modifications all make the analysis harder.

Presentation

ASC 606 and IFRS 15 put a lot of weight on presentation and disclosure. The goal is to give financial statement users clear information about the nature, amount, timing, and uncertainty of revenue and cash flows from contracts with customers. Here’s how revenue shows up in each statement:

Balance Sheet (Statement of Financial Position) Presentation

• Assets and Liabilities Related to Contracts: Companies need to present any contract assets and contract liabilities on their balance sheet. A contract asset is recognized when a company has transferred goods or services but its right to payment is conditional on something other than the passage of time, such as finishing another part of the contract. If only time needs to pass, the right is unconditional and is recorded as a receivable instead. A contract liability (often called deferred revenue or unearned revenue) is recognized when a company receives payment, or has an unconditional right to payment, before it transfers the goods or services.
• Disclosure: Separate disclosure of contract assets and liabilities from other assets and liabilities provides clearer insights into the company’s contractual obligations and rights.

Income Statement (Statement of Comprehensive Income) Presentation

• Revenue Recognition: Revenue should be presented in the income statement as it is recognized from the transfer of promised goods or services to customers, reflecting the transaction price allocated to the satisfied performance obligation.
• Disaggregation of Revenue: Entities must disaggregate revenue recognized from contracts with customers into categories that depict how the nature, amount, timing, and uncertainty of revenue and cash flows are affected by economic factors.

Statement of Cash Flows

• ASC 606 doesn’t change how cash flows are classified. Cash collected from customers is still an operating inflow. What changes is the gap between revenue and cash, which shows up as changes in receivables, contract assets, and contract liabilities when operating cash flow is reconciled from net income (the indirect method).

Notes to Financial Statements

• Significant Judgments and Changes: Entities must disclose significant judgments and changes in judgments made in applying the revenue recognition standard to their contracts with customers.
• Performance Obligations: The notes should include information about the nature, timing, and uncertainty of revenue and cash flows from performance obligations, including when the entity typically satisfies its performance obligations (e.g., upon shipment, upon delivery, over time) and the significant payment terms (e.g., payment terms, financing components, incentives).
• Transaction Price Allocated to Remaining Performance Obligations: An explanation of when the entity expects to recognize as revenue the amount of the transaction price that is allocated to the remaining performance obligations.
• Contract Balances: The opening and closing balances of receivables, contract assets, and contract liabilities from contracts with customers, including the significant changes during the period.
• Costs to Obtain or Fulfill a Contract: If significant, the method used to determine the amortization for costs to obtain or fulfill a contract and the closing balances of any capitalized costs.

Private companies get some relief here. Nonpublic entities can elect to skip certain disclosures, such as the quantitative disaggregation of revenue and the detailed remaining performance obligation disclosures.

Implementing ASC 606 and IFRS 15 requires entities to carefully evaluate their contracts with customers and make significant judgments that affect how and when revenue is recognized and presented in the financial statements. The increased disclosure requirements under these standards aim to enhance transparency and provide financial statement users with a more detailed understanding of an entity’s revenue.

Worked Example: Solar Installation and Maintenance Revenue

Let’s consider a hypothetical company, GreenTech Innovations, which specializes in green technology solutions. GreenTech Innovations enters into a contract with Cityscape Constructions to install an advanced solar panel system on a new building. The contract also includes maintenance services for the solar panel system for one year after installation.

Contract Overview:

• Contract Value: $200,000
• Contract Terms:
  • Installation of the solar panel system: $150,000
  • One-year maintenance service post-installation: $50,000
• Payment Terms: The customer pays $100,000 upon signing, and the remaining $100,000 becomes unconditionally due upon completion of the installation. The maintenance service fee is included in the initial contract value.
• Installation Time: Estimated to take 6 months.
• Maintenance Period: 12 months following installation completion.

Detailed Example Analysis:

Step 1: Identify the Contract(s) with a Customer

GreenTech Innovations and Cityscape Constructions have a written agreement that is enforceable, with clear terms regarding the goods and services to be provided and the payment terms. Assume both parties have approved and committed to the agreement, the contract has commercial substance, their rights and payment terms are identifiable, and collection of substantially all consideration is probable. All ASC 606 contract criteria are therefore satisfied.

Step 2: Identify the Performance Obligations in the Contract

The contract has two distinct performance obligations:

1. Installation of the solar panel system: This constitutes a distinct service as Cityscape Constructions will benefit from the installed system independently.
2. One-year maintenance service: This is a distinct service that maintains the functionality of the solar panel system, separate from the installation.

Step 3: Determine the Transaction Price

The transaction price agreed upon in the contract is $200,000. This includes fixed consideration for both installation ($150,000) and maintenance services ($50,000). Assume there is no variable consideration and no significant financing component.

Step 4: Allocate the Transaction Price to the Performance Obligations in the Contract

The transaction price is allocated to the performance obligations based on their stand-alone selling prices (SSPs):

• Installation: GreenTech sells installations like this separately for $165,000, so that’s its stand-alone selling price.
• Maintenance Service: GreenTech sells one-year maintenance plans separately for $55,000.

The two SSPs add up to $220,000, but Cityscape is paying $200,000 for the bundle. That $20,000 discount is spread across both obligations in proportion to their SSPs:

• Installation: $200,000 × ($165,000 ÷ $220,000) = $150,000
• Maintenance: $200,000 × ($55,000 ÷ $220,000) = $50,000

Here the allocation lands on the same amounts listed in the contract, but that’s a coincidence. Relative stand-alone selling prices determine the allocation in this example. This is the general rule; qualifying discounts or variable consideration may instead be allocated to particular performance obligations when the standard’s specific criteria are met.

Step 5: Recognize Revenue When (or As) the Entity Satisfies a Performance Obligation

• Installation of the Solar Panel System: The panels are installed on Cityscape’s own building, so Cityscape controls the work as it happens (over-time criterion 2). GreenTech recognizes the $150,000 over the 6-month installation using an input method: costs incurred to date divided by total expected costs. For example, if 40% of the expected installation costs have been incurred at a reporting date, cumulative installation revenue is $60,000 ($150,000 × 40%).
• One-Year Maintenance Service: The $50,000 allocated to maintenance is recognized evenly over the 12-month service period, about $4,167 per month ($50,000 ÷ 12 = $4,166.67), because Cityscape receives the benefit of being covered as each month passes.

Journal Entries For The GreenTech Example

These are revenue-side entries only; installation costs and related expense entries are omitted. On the balance sheet, a single contract is shown as one net contract asset or net contract liability, but separate lines make the logic easier to follow.

Entry	Account	Debit	Credit
1. Upfront payment received	Cash	$100,000
1. Upfront payment received	Contract liability		$100,000
2. During installation (6-month total)	Contract liability	$100,000
2. During installation (6-month total)	Contract asset	$50,000
2. During installation (6-month total)	Revenue		$150,000
3. Installation complete, second payment billed	Accounts receivable	$100,000
3. Installation complete, second payment billed	Contract asset		$50,000
3. Installation complete, second payment billed	Contract liability		$50,000
4. Second payment collected	Cash	$100,000
4. Second payment collected	Accounts receivable		$100,000
5. Each month of maintenance (12 months)	Contract liability	$4,167
5. Each month of maintenance (12 months)	Revenue		$4,167

• Why a contract asset in entry 2? Once installation revenue passes the $100,000 already collected, GreenTech has earned more than it can bill. Its right to the extra $50,000 depends on finishing the installation, so it’s a contract asset, not a receivable.
• Why a contract liability in entry 3? After the second payment is billed, GreenTech is owed or has received $200,000 in total but has earned only $150,000. The $50,000 difference is maintenance it still owes Cityscape.
• The monthly maintenance entry is $50,000 ÷ 12 = $4,166.67, rounded to $4,167. Adjust the final month to $4,163 so the year totals exactly $50,000.

Common Revenue Recognition Exam Traps

These are spots where candidates commonly slip on exam questions:

1. Collectability wording: Under ASC 606, the test is whether it’s probable you’ll collect substantially all of the consideration. ‘Probable’ means likely to occur under US GAAP, but only ‘more likely than not’ under IFRS 15.
2. Contract asset vs. receivable: If your right to payment depends only on time passing, it’s a receivable. If it depends on doing more work, it’s a contract asset.
3. SaaS vs. software license: SaaS is a service recognized over time. A license to software the customer runs itself is usually recognized at a point in time.
4. Allocation: Split the transaction price using relative stand-alone selling prices, not the prices the contract happens to list.
5. Over time first: Before defaulting to point-in-time recognition, check the three over-time criteria.
6. Variable consideration constraint: Include variable amounts only to the extent it’s probable (US GAAP) or highly probable (IFRS 15) that a significant revenue reversal won’t occur.

Continue with the Intermediate Accounting course, practise with the FAR Test Bank, or explore the free sample course.

Key Takeaways

• Revenue is recognized when (or as) control of a good or service transfers to the customer, not when cash arrives.
• ASC 606 (US GAAP) and IFRS 15 use the same five-step model: contract, performance obligations, transaction price, allocation, and recognition.
• The transaction price is allocated using relative stand-alone selling prices.
• Revenue is recognized over time if at least one of three criteria is met; otherwise it’s recognized at a point in time.
• Cash received before you perform is a contract liability. Revenue earned before you have an unconditional right to bill is a contract asset.

Frequently Asked Questions

Does signing a contract create revenue?

Signing alone does not create revenue. If the customer pays before performance, the seller generally records a contract liability. Revenue follows satisfaction of the performance obligation.

Why does GreenTech allocate $50,000 to maintenance?

Maintenance represents $55,000 of the $220,000 total stand-alone selling prices. Its 25% share of the $200,000 transaction price is $50,000.

Why is GreenTech’s unbilled revenue a contract asset?

The remaining right to payment is conditional on completing installation. Once that condition is satisfied and only the passage of time remains before payment, the unconditional right is presented as a receivable.

Can the contract show a receivable and a contract liability together?

Yes. Receivables are presented separately from the net contract position. At completion of installation, GreenTech has an unconditional $100,000 receivable and a $50,000 contract liability for maintenance still to be provided.

Must every contract discount be allocated proportionately?

No. Relative stand-alone selling prices are the general rule. A discount may be allocated entirely to selected performance obligations when the specific evidence and criteria in ASC 606 are satisfied. GreenTech’s example assumes no such exception applies.

How is variable consideration estimated?

Use the expected value or most likely amount method, whichever better predicts the consideration. Under ASC 606, include the estimate only to the extent it is probable that a significant reversal of cumulative revenue will not occur when the uncertainty is resolved. Reassess estimates at each reporting date.

For authoritative guidance, consult FASB ASC 606, particularly the recognition, measurement, presentation, and disclosure sections. For international comparisons, consult the IFRS Foundation’s IFRS 15 overview.

About The Author

Mansour Farhat, CPA, CIA, DBA, is the instructor behind Farhat Lectures, where he teaches accounting courses and supplemental CPA exam review for students and exam candidates. His lessons, including the ASC 606 video on this page, are also available on the Farhat Lectures YouTube channel.