Revenue Recognition: Five-Step Model – Detailed Notes
Revenue Recognition: Five-Step Model (Detailed Notes)
General framing
Two primary issues in revenue recognition:
Timing: when to recognize revenue (based on when control of the asset transfers to the customer).
Measurement: how much revenue to recognize (amount seller expects to be entitled to receive in exchange).
Core principle summary:
Recognize revenue when control of the asset passes to the customer (or over time if the criteria for recognizing over time are met).
Determine the transaction price (the expected consideration the seller will be entitled to).
This material is framed around the five-step model used to recognize revenue from contracts with customers.
Five Steps to Revenue Recognition
Step 1: Identify the contract(s) with the customer
Step 2: Identify the performance obligation(s) in the contract
Step 3: Determine the transaction price
Step 4: Allocate the transaction price to the performance obligation(s)
Step 5: Recognize revenue when, or as, each performance obligation is satisfied
Step 1: Identify the Contract(s) with the Customer
Contract definition
An agreement between two or more parties that creates enforceable rights and obligations.
Five criteria to be considered a contract
1) All parties have agreed to the contract and are committed to performing under the contract.
2) Each party's rights with respect to the goods or services being transferred are identifiable.
3) The payment terms for the goods or services being transferred are identifiable.
4) The contract has commercial substance (risk, timing, or amount of the entity's future cash flows is expected to change as a result of the contract).
5) It is probable that the seller will collect the consideration to which it is entitled in exchange for the goods or services.Collectability considerations
Collectability is assessed on expected consideration, not the contract price (e.g., a discount amount would not be part of collectability).
US GAAP: probable (likely to occur); IFRS: more likely than not (i.e., probability > 50%).
The assessment uses expected consideration, not necessarily the stated contract price.
Practical implications and illustrations
Example: On March 14, a salesman and a buyer agree to sell 1,000 boxes for $3,000 with delivery in 5 days and payment due within 15 days of delivery; a 5% discount is available if additional brands are purchased before payment. The collectability assessment might conclude that $2,850 is probable rather than the full $3,000.
If multiple contracts are negotiated as a package with a single objective, or if one contract's consideration depends on another, or if goods/services are part of one broader performance obligation, contracts may be combined.
Failure to identify a contract
If a contract is not identifiable, revenue recognition may be delayed or uncertain until the contract is identified and enforceable; revenue recognition typically occurs when consideration is received and there are no remaining obligations, or the contract is terminated with nonrefundable consideration, or control of transferred goods/services has shifted.
Example notes and journal implications
If cash is received but revenue cannot yet be recognized, recognize a liability (unearned revenue) and do not reduce inventory until performance occurs.
Contract identification examples (highlights)
Example 1: A simple identified contract with delivery and payment terms and a potential discount; probabilistic collectability discussion.
Example 2: Credo, Inc. contract for legal services with four quarterly installments ($60,000 total). If collectability is not probable, the contract may be considered not identifiable; journal entries may reflect partial recognition or deferral depending on collectability and performance.
Important takeaway
The contract must satisfy all five criteria to proceed to Steps 2–5.
Some contracts may be combined when appropriate.
Step 2: Identify the Performance Obligation(s) in the Contract
Performance obligation (PO) definition
A promise to transfer a distinct good/service (or a bundle of goods/services) to the customer, or a promise to transfer a series of distinct goods/services that are substantially the same and have the same pattern of transfer to the customer.
How to identify PO
First, identify the goods or services promised.
Then determine if they are distinct.
Distinctness criteria (two conditions)
1) The customer can benefit from the good or service on its own or with other readily available resources.Readily available resources include goods/services sold separately by the seller or another entity, or resources the customer already possesses.
2) The promise to deliver that good or service is separately identifiable from other promises in the contract.If a promise to deliver is separable from another promise, the two promises are not highly dependent or interrelated.
Example A: Coffee + mug in a campus welcome-back special
Standalone selling prices (SSP): coffee = $5, mug = $3.
Both items can be enjoyed separately, and the promises to transfer coffee and to transfer the mug are separately identifiable.
Conclusion: There are two PO (coffee and mug).
Example B: Coupon for two croissants with a coffee purchase
Coffee price = $5; croissant price = $2; coupon entitles two croissants; the coupon is for two croissants delivered at the same time.
The coffee is one PO (distinct and separable). The two croissants delivered upon coupon redemption are a single PO (not two distinct croissants because the promise is for two croissants delivered together).
Conclusion: There are two PO (cup of coffee and the two croissants under the coupon).
Practical notes
Some contracts include implicit or complementary promises; these may or may not be considered PO depending on whether they are separately identifiable and provide distinct benefits.
If some goods/services are not distinct, they may be bundled as a single PO.
PO identification examples (highlights)
Example 3: Coffee and mug -> two PO.
Example 3 (alternative): Coffee and coupon for croissants -> two PO, with croissants treated as a single PO when delivered together.
Step 3: Determine the Transaction Price
Transaction price definition
The amount of consideration the entity expects to be entitled to in exchange for transferring goods or services to the customer.
Not necessarily the stated contract price; it is the amount the seller expects to receive and ultimately recognizes as revenue.
Simple vs. complex cases
Simple: A fixed, non-contingent price.
Complex: Variable consideration, significant financing components, noncash consideration, consideration payable to the customer.
Variable consideration (VC)
What counts as VC
Price concessions, performance bonuses/penalties, discounts, refunds, rebates, incentives, etc.
The transaction price must include VC; thus the TP may be different from the contract price.
Approaches to estimate VC
Most-likely-amount approach: Use the single most likely amount in the range of possibilities as the estimate of TP.
Expected-value approach: Sum probability-weighted amounts in the range of possible consideration values.
ext{TP}{EV} = igl( ext{prob}1 imes ext{amount}1igr) + igl( ext{prob}2 imes ext{amount}_2igr) +
ext{…}Constraint on VC (to avoid revenue reversal)
There is a requirement to constrain VC when there is a significant risk that revenue may reverse in the future.
Guideline approximate: if the probability of reversal is around 25–30% or higher, reduce the recognized revenue.
IFRS vs US GAAP terminology: IFRS uses “highly probable” (around 70–75% likelihood is cited as a ballpark), US GAAP uses “probable”.
Examples illustrating VC (highlights)
Example 4 (Lled vs Elppa): A discount program dependent on annual purchases with multiple probability-weighted outcomes. Using EV vs MLA yields different TP; constrained vs unconstrained will affect final TP.
Example 4 computations show a probability-weighted unit price and transaction price around $974,000 vs $980,000 depending on method.
Example 5 (Bathrooms Are Us): Remodeling contract with an incentive bonus for water savings. Probabilities for different bonus amounts lead to a constrained transaction price; decisions depend on the assessed probability of achieving the bonus.
Significant financing component
When payment occurs significantly before or after delivery, a financing component may exist.
If the financing component is significant, separate revenue from financing income/expense using time value of money (TVM).
How to assess significance
Difference between contract price and cash selling price, the time between delivery and payment, and market interest rate.
TVM treatment
If delivery before payment (seller finances customer): recognize sales revenue (PV of the consideration) plus interest revenue on the financing portion.
If payment before delivery (customer finances seller): recognize revenue for the cash received, and the difference to delivery date is interest expense.
Simple formulas (for educational purposes in these materials)
PV of future cash:
FV from present value:
Noncash consideration
Seller may receive payment in noncash assets (e.g., stock).
Record transaction price at fair value at contract inception of the noncash consideration; if fair value cannot be reasonably estimated, use the standalone selling price of the good/service.
Example: If merchandise is exchanged for stock with a known fair value, use that fair value as the TP for revenue.
Consideration payable to a customer
Seller may pay the buyer to incentivize purchase; unless the payment is in exchange for a distinct good/service, the consideration should be deducted from the transaction price.
Example: Hulk Products contract includes a display payment to the customer; transaction price should deduct the incentive unless it is for a distinct good/service.
Standalone selling price (SSP) and allocation implications
SSP: the price the seller would charge for the same goods/services if sold separately to similar customers under similar circumstances.
If the sum of SSPs exceeds the TP, allocate the discount on a relative SSP basis:
Complexity in estimating SSP when not sold separately
Methods to estimate SSP (as per FASB/IASB): Adjusted market, expected-cost-plus-margin, residual approach.
SSP estimation methods (brief):
Adjusted market assessment: use the market price for the good/service and adjust as needed.
Expected-cost-plus-margin: forecast cost to provide the good/service and add a markup.
Residual approach: estimate SSP for everything possible; allocate the remainder to the item with no observable SSP.
SSP allocation example (illustrative): BartMan contract for four products at total TP = $1,000,000; SSPs for products 1–4 are given with market prices, costs, etc. Allocate TP to the four PO using SSP or alternative methods to illustrate how to allocate a discount or price differences.
Step 4: Allocate the Transaction Price to the Performance Obligation(s)
Core idea
Determine SSP for each PO; allocate TP proportionally to SSPs.
Allocation process
If the SSPs for all POs are known, allocate based on relative SSPs:
When SSPs are not observable
Use estimation methods (Adjusted market, Expected-cost-plus-margin, Residual).
Complexity considerations
Variable consideration and discounts may require adjustments to allocated TP across POs (e.g., if discounts apply to all goods/services, allocations should reflect relative SSPs).
Step 5: Recognize Revenue When, or as, Each Performance Obligation is Satisfied
The fundamental principle
Revenue is recognized when control over the transferred goods or services has passed to the customer.
Control means the entity has the ability to direct the use of the asset and obtain substantially all the benefits from owning the asset.
Revenue recognition can occur over time or at a point in time.
General rule: recognize when control transfers
Transfer over time (ROTO: revenue recognized over time as progress toward completion can be measured)
One of the following criteria must be met to recognize over time
The customer simultaneously receives and consumes the benefits as the seller performs (e.g., services that are provided continuously).
The customer controls the asset as it is being created or enhanced (e.g., construction projects).
The asset being created does not have an alternative use to the seller, and the seller has an enforceable right to payment for performance completed to date.
If progress toward completion cannot be reliably measured, recognize revenue only when the transfer is complete.
Progress measurement approaches: output methods (e.g., milestones, units delivered) or input methods (e.g., costs incurred, labor hours).
Transfer at a point in time (TAPT)
Revenue recognized when control transfers to the customer.
Five indicators (not criteria):
The seller has a present right to payment for the asset.
The customer has legal title to the asset.
The seller has transferred physical possession of the asset.
The customer has the significant risks and rewards of ownership.
The customer has accepted the asset.
Examples illustrating transfer timing
Example 10 (Memberships):
Annual memberships sold for $2,400 each; 50 memberships sold for $120,000 cash received on Jan 1.
Recognize revenue over time as benefits are delivered; typical journal pattern involves recording Unearned Service Revenue when cash is received and recognizing revenue quarterly as services are performed.
Quarterly recognition example (for a calendar year): recognize $30,000 per quarter, totaling $120,000 by year end.
Example 11 (Progress over time with enforceable right to payment):
A technology service contract for $10 million over three years; progress measured by labor hours; cash receipts occur at inception, during Year 2, and at completion.
Revenue recognized progressively based on percentage completion or hours incurred; maintain revenue and contract asset/liability accounts accordingly.
Example 12 (Point in time):
February 1: 100 jackets sold for $350 each on credit; jackets shipped; customer obtains title on shipment.
Journal: A/R 35,000; Sales Revenue 35,000; Inventory cost $20,000; COGS 20,000.
Practical guidance on recognizing over time vs point in time
If an entity can measure progress toward completion and has an enforceable right to payment for performance completed to date, recognize over time.
If not, recognize at a point in time when control transfers (e.g., shipping, delivery, or possession transfer events).
Step 6 (Supplemental): Summary of the Revenue Recognition Process
Recap of steps (in order)
Step 1: Identify the contract(s) with customers.
Step 2: Identify the performance obligation(s) in the contract.
Step 3: Determine the transaction price (including variable consideration, financing components, noncash consideration, consideration payable to customers).
Step 4: Allocate the transaction price to the performance obligation(s) using SSP and allocation methods.
Step 5: Recognize revenue when, or as, each performance obligation is satisfied (over time or at a point in time).
Important considerations while applying the steps
Contracts may be combined when criteria are met (single commercial objective, dependence of consideration on another contract, or goods/services part of one performance obligation).
Collectability assessments influence Step 1 (contract existence) and may impact whether revenue is recognized in Step 5.
The transaction price may require adjustments for variable consideration, financing components, noncash consideration, and consideration payable to customers.
The method used to estimate SSP can affect how TP is allocated across POs.
When recognizing revenue over time, adequate measures of progress must be available; otherwise, recognize at a point in time upon satisfaction of control transfer.
Quick reference of formulas used in the notes
Most-likely-amount approach:
Expected-value approach:
ext{TP}{EV} = igl(p1 imes a1igr) + igl(p2 imes a_2igr) +
ext{…}Allocation of TP to PO based on SSP:
Present value and future value in financing components:
Key takeaways for exam readiness
Always verify contract criteria before moving to PO identification.
Distinguish between distinct and non-distinct promises to determine the number of POs.
Be prepared to estimate and constrain VC; know when to apply the EV vs MLA approach.
Understand how to allocate price across POs using SSP and the three SSP estimation methods.
Decide whether revenue is recognized over time or at a point in time based on control transfer and progress measurement capabilities.