Executive Summary
Step 5 of the Five-Step Revenue Recognition Model under ASC 606 and IFRS 15—Recognize revenue when (or as) performance obligations are satisfied—is where contractual economics are ultimately translated into reported financial performance. While the standard’s definition appears concise, practical application is highly nuanced and judgment-intensive. This whitepaper provides a structured, narrative-driven explanation of Step 5, expanding well beyond the core definition to address control transfer, timing patterns, progress measurement, balance sheet impacts, and common misconceptions. Through a broad set of distinct scenarios, it establishes a durable mental model that connects accounting guidance, operational execution, and audit expectations.
The objective is not merely to restate the standard, but to help practitioners internalize why revenue is recognized when it is, how different recognition patterns coexist within a single contract, and where judgment materially affects financial outcomes.
Introduction: What Step 5 Is Really About
At its core, Step 5 answers a single foundational question:
When does control of a promised good or service transfer to the customer—and therefore when should revenue move from the balance sheet to the income statement?
By the time an entity reaches Step 5, pricing and allocation decisions have already been completed in Steps 3 and 4. Step 5 is not about how much revenue to recognize—that amount is already determined. Instead, it is exclusively about timing and pattern of recognition.
Key principles that define Step 5 include:
- Revenue is recognized only when a performance obligation is satisfied
- Satisfaction can occur at a point in time or over time
- The amount recognized equals the transaction price allocated to that performance obligation
- Recognition typically results in a reduction of a contract liability or an increase (or reduction) of a contract asset
This step is grounded in the concept of control, not billing, invoicing, or cash receipt.
Control as the Central Concept
Control refers to the customer’s ability to direct the use of, and obtain substantially all of the remaining benefits from, an asset, while preventing others from doing so. Control does not require all indicators to be present simultaneously, but common indicators include:
- Legal title
- Physical possession
- Significant risks and rewards of ownership
- Customer acceptance
- A present right to payment
The assessment of control transfer underpins every revenue recognition decision in Step 5.
Two Revenue Recognition Patterns
Every performance obligation must be evaluated to determine whether it is satisfied:
- At a point in time, or
- Over time
This classification is mandatory and directly drives the revenue recognition pattern.
Performance Obligations Satisfied at a Point in Time
Characteristics
Point-in-time recognition applies when control transfers discretely. Revenue is recognized in full at a specific moment rather than progressively.
Typical triggers include shipment, delivery, customer acceptance, legal title transfer, or system go-live.
Illustrative Scenarios
Hardware Sale with FOB Shipping Point
Control transfers upon shipment. Revenue is recognized on the shipment date, regardless of billing or cash timing.
Perpetual Software License (Right to Use)
When a license key is made available and no ongoing obligations exist, control transfers immediately and revenue is recognized at that point.
Customer Acceptance Clauses
When delivery occurs before formal acceptance, control does not transfer until acceptance criteria are met. Revenue is deferred until that event.
Binary Milestone Contracts
If payment and enforceable rights arise only upon achievement of a specific milestone, revenue is recognized only when that milestone is achieved.
These scenarios illustrate that point-in-time recognition hinges on control, not physical delivery alone.
Performance Obligations Satisfied Over Time
A performance obligation is satisfied over time if any one of the following criteria is met:
- The customer simultaneously receives and consumes the benefits of performance
- The entity’s performance creates or enhances an asset the customer controls
- The entity’s performance does not create an asset with alternative use, and the entity has an enforceable right to payment for performance completed to date
Over-time recognition is one of the most judgment-intensive areas in the standard.
Illustrative Scenarios
SaaS Subscriptions
Customers consume the service as it is provided. Revenue is recognized over time, often on a straight-line basis.
Payroll or Transaction Processing Services
Benefits are consumed continuously. Revenue is recognized as services are performed.
Construction on Customer-Owned Land
Work-in-progress is controlled by the customer. Revenue is recognized over time based on progress.
Highly Customized Software with No Alternative Use
When the asset cannot be repurposed and payment for work to date is enforceable, revenue is recognized over time—even prior to delivery.
Measuring Progress for Over-Time Performance Obligations
When revenue is recognized over time, entities must select a method that faithfully depicts performance.
Output Methods
These measure results directly transferred to the customer, such as milestones achieved or units delivered. While intuitive, they may fail to capture work in progress.
Input Methods
These measure effort expended relative to total expected effort, such as cost-to-cost or labor hours. They require careful exclusion of inefficiencies and wasted costs.
Cost-to-Cost Illustration
If total expected cost is $1,000,000 and costs incurred to date are $400,000, progress is 40%, and 40% of the allocated revenue is recognized.
Progress measurement choices significantly affect revenue timing and are a frequent audit focus.
Interaction with Contract Assets and Contract Liabilities
Step 5 is where balance sheet accounts reverse into revenue:
- When revenue is recognized before billing, a contract asset arises
- When billing occurs before performance, a contract liability is recorded and released as revenue is recognized
Prepaid Subscription Example
Cash is received upfront, creating a contract liability that is reduced over time as revenue is recognized.
Unbilled Services Example
Revenue is recognized as work is performed, creating a contract asset until billing occurs.
Partial Satisfaction and Mixed Recognition Patterns
Most real-world contracts contain multiple performance obligations with different recognition patterns.
For example:
- A software license recognized at a point in time
- Implementation services recognized over time
- Support services recognized over time, often straight-line
Each performance obligation follows its own recognition logic, even within a single contract.
Common Misconceptions
Several misconceptions are frequently challenged in audits:
- Revenue follows invoicing
- Cash receipt triggers revenue
- Milestones automatically justify point-in-time recognition
- Equal billing implies equal revenue recognition
- Over-time recognition always means straight-line
Each of these contradicts the control-based framework of Step 5.
Mental Model to Retain
Step 5 can be viewed as:
A systematic release of previously allocated transaction price from the balance sheet to the income statement, driven solely by the transfer of control of each performance obligation.
This framing reinforces that revenue recognition is detached from billing mechanics and cash flows.
Conclusion
Step 5 of ASC 606 and IFRS 15 is where contractual promises become reported revenue. It is the point at which accounting theory, operational execution, and legal enforceability converge. Mastery of this step requires:
- Clear identification of performance obligations
- Sound judgment in determining point-in-time versus over-time satisfaction
- Defensible progress measurement methodologies
- Strong alignment between contracts, operations, and accounting systems
Ultimately, Step 5 is not about accelerating or deferring revenue—it is about faithfully representing the transfer of control to the customer. Organizations that internalize this principle achieve more consistent financial reporting, stronger audit outcomes, and a clearer connection between commercial strategy and financial results.
Enterprise Resource Planning and Integrations BlogSpot 