2 1 Revenue Recognition Explained
Key Concepts
- Revenue Recognition Principle
- Performance Obligations
- Transaction Price
- Allocation of Transaction Price
- Timing of Revenue Recognition
Revenue Recognition Principle
The revenue recognition principle states that revenue should be recognized when it is earned and realizable. This means that the company has completed the performance obligations and the payment is reasonably assured.
Performance Obligations
Performance obligations are the promises in a contract to transfer goods or services to the customer. These obligations must be distinct and capable of being separately identified to recognize revenue.
Example: A software company sells a one-year subscription to its software. The performance obligation is to provide access to the software for the entire year.
Transaction Price
The transaction price is the amount of consideration to which a company expects to be entitled in exchange for transferring goods or services to a customer. This price may include variable amounts, discounts, or other adjustments.
Example: A company sells a product for $100 but offers a 10% discount if the customer pays within 30 days. The transaction price is $90 if the customer pays on time.
Allocation of Transaction Price
The allocation of transaction price involves assigning the total transaction price to each distinct performance obligation in the contract. This ensures that revenue is recognized in proportion to the value of each obligation.
Example: A company sells a product and a one-year warranty. The total transaction price is $120, with the product valued at $100 and the warranty at $20. The transaction price is allocated accordingly.
Timing of Revenue Recognition
The timing of revenue recognition depends on when the performance obligations are satisfied. Revenue is recognized when control of the goods or services is transferred to the customer.
Example: A construction company recognizes revenue over time as it completes various stages of a building project, reflecting the transfer of control to the customer at each stage.
Examples and Analogies
Consider revenue recognition as "counting your chickens" when they hatch, not when you sell them. Performance obligations are like "milestones" in a project that must be completed before revenue can be recognized.
The transaction price is like the "final bill" after all discounts and adjustments are applied. Allocation of transaction price is like "dividing the bill" among different services or products.
Timing of revenue recognition is like "unlocking a door" to the customer's control, with revenue recognized as each door is unlocked.