The Five-Step Revenue Recognition Model Under ASC 606
ASC 606 established a comprehensive revenue recognition standard applicable across all industries. The five-step model is your foundation for exam success.
Step 1: Identify the Contract with a Customer
A valid contract requires that both parties approve it, each party's rights are identified, payment terms are specified, and the entity will likely collect payment.
Step 2: Identify Separate Performance Obligations
Performance obligations are promises to transfer distinct goods or services. A good or service is distinct if the customer can benefit from it independently and the entity's promise is separately identifiable from other promises.
Example: A software company selling a license with implementation services. If the customer can use the software alone, these are two separate performance obligations.
Step 3: Determine the Transaction Price
Transaction price includes fixed consideration and variable consideration. Estimate variable consideration using either:
- Expected value method (probability-weighted average of outcomes)
- Most likely amount method (single most likely outcome)
Adjust for time value of money if payment occurs significantly later.
Step 4: Allocate Price to Performance Obligations
Allocate the transaction price to separate obligations using standalone selling prices. When prices aren't observable, estimate them using:
- Adjusted market assessment approach
- Expected cost plus margin approach
- Residual approach
Step 5: Recognize Revenue When Control Transfers
Control transfers when the customer can direct use of the asset and obtain remaining benefits. Revenue is recognized either at a point in time or over time depending on when the customer obtains control.
Identifying Performance Obligations and Control Transfer
Performance obligations are promises to transfer distinct goods or services. Correctly identifying them directly affects timing and amount of revenue recognition.
When Is a Good or Service Distinct?
Two criteria must be met. First, the customer can benefit from the good or service on its own or with readily available resources. Second, the entity's promise is separately identifiable from other promises in the contract.
Example: A software company sells a license with implementation services. These are two separate performance obligations if the customer can benefit from the software license alone.
However, if implementation services significantly integrate with the software to create a combined asset, they may form a single performance obligation.
Point in Time Versus Over Time Recognition
Control transfers at a point in time when the customer obtains the ability to direct use and obtain substantially all remaining benefits at a single moment. This typically occurs at shipment or delivery of goods.
Control transfers over time when the entity:
- Creates an asset without alternative use and has an enforceable right to payment for completed work
- Provides services the customer simultaneously receives and consumes
- Creates or enhances an asset controlled by the customer
Common Exam Scenarios
Retail sales recognize revenue at point in time when goods transfer. Subscription services recognize revenue over time as services are delivered monthly. Construction contracts recognize revenue over time as progress is made. Licensing arrangements vary based on whether the license provides right of access or right of use.
Understanding these distinctions allows you to correctly apply the revenue recognition model to exam scenarios.
Variable Consideration and Constrained Revenue
Variable consideration includes amounts depending on future events beyond the entity's control. Common examples are discounts, rebates, refunds, credits, penalties, performance bonuses, and contingent consideration.
Estimating Variable Consideration
Estimate variable consideration at contract inception using either the expected value method or most likely amount method. Choose the method that better predicts the actual amount based on the nature of the variable consideration and specific facts and circumstances.
The Constraint Rule
Variable consideration is constrained, meaning it can only be included in transaction price to the extent it is highly probable that a significant reversal of cumulative revenue will not occur in the future. This constraint is critical for exam questions and requires judgment.
Example: A retailer offers a 30-day return period. Historical data shows 8% of units are returned. The entity can constrain variable consideration for these likely returns.
Updating Estimates
As additional information becomes available, entities update estimates of variable consideration and adjust cumulative revenue in the current period. This ongoing assessment distinguishes revenue recognition from earlier approaches.
Applying the Constraint
The constraint doesn't prevent including variable consideration but requires assessing whether recognition is highly probable given available information. When estimating variable consideration, consider contract terms, historical experience, market conditions, and entity policies.
This topic frequently appears on FAR exams as scenario questions requiring you to calculate revenue amounts including or excluding variable consideration.
Contract Modifications, Practical Expedients, and Exemptions
Contract modifications occur when parties approve changes to scope, price, or both. Determining how to account for modifications requires analyzing whether the modification creates a separate performance obligation or modifies an existing one.
Accounting for Modifications
If the customer gains rights to distinct goods or services not already provided and the selling price is observable, treat the modification as a separate contract. Otherwise, modifications either terminate the original contract and create a new one, or change the original contract's transaction price and performance obligations.
Example: A consulting firm has a contract for six months of advisory services. The client requests two additional months at an observable price reflecting standalone selling price. This is a separate contract.
If the client requests modifications without clearly stated additional consideration, the modification likely adjusts the existing contract's transaction price.
Key Practical Expedients
Contract term expedient: Do not adjust transaction prices for time value of money if payment occurs within one year or less.
Shipping and handling expedient: Account for shipping and handling costs as fulfillment costs rather than separate performance obligations if incurred after customer obtains control.
Scope Exemptions
ASC 606 exempts lease contracts (covered by ASC 842), insurance contracts (covered by ASC 944), and certain financial instruments. Small contract portfolios with similar characteristics can be combined for practical efficiency.
These provisions significantly impact how revenue is recognized across different industries and frequently appear on CPA exams.
Industry-Specific Applications and Common Exam Scenarios
Revenue recognition principles apply consistently across industries but manifest differently based on business models and contract types.
Technology and Software
SaaS contracts are recognized over time as services are delivered. Perpetual licenses with implementation require judgment about identifying separate performance obligations. Cloud services typically recognize revenue over time.
E-Commerce and Retail
Revenue is recognized at point in time when goods transfer to customers, typically at shipment or delivery. Businesses must account for returns, warranties, and refund obligations as variable consideration.
Real Estate and Construction
Real estate development contracts recognize revenue over time as the entity's performance creates or enhances an asset controlled by the customer. Construction contracts similarly recognize revenue over time using output methods when available.
Healthcare and Telecommunications
Healthcare entities recognize revenue over time as patients receive services, with considerations for insurance coverage and contractual adjustments. Telecommunications companies recognize revenue over multiple components including service access fees (over time) and equipment sales (point in time).
Typical Exam Scenarios
Exam questions frequently present multi-step scenarios requiring you to:
- Identify whether distinct performance obligations exist in bundled contracts
- Determine whether control transfers over time or at a point in time
- Calculate transaction prices with variable consideration
- Analyze effects of contract modifications
- Explain your conclusions using ASC 606 framework
Understanding both the theoretical framework and practical application across industries is essential for maximizing your FAR exam performance.