FAR coverage for the ASC 606 five-step model, principal-agent analysis, variable consideration, contract costs, licenses, and disclosure.
Revenue recognition under ASC 606 is tested in FAR because small fact changes can move revenue between periods, change the transaction price, or change whether revenue is reported gross or net. The model is contract-based, but the exam answer usually turns on control, distinct performance obligations, variable consideration, and presentation.
The safest approach is to work the five steps in order. Do not jump directly to revenue timing until the contract, performance obligations, transaction price, allocation, and transfer of control have been analyzed.
| Lesson | Main question | What to master |
|---|---|---|
| The ASC 606 Five-Step Revenue Recognition Model | What is the overall revenue recognition sequence? | Contract criteria, distinct performance obligations, transaction price, allocation, and transfer of control |
| Principal-Agent Analysis and Variable Consideration | Should revenue be gross or net, and how much variable consideration is included? | Principal-agent indicators, constraint on variable consideration, expected value, most likely amount, refunds, rebates, and bonuses |
| Contract Costs, Licenses, and Nonrefundable Fees | Which revenue-related costs or fees are deferred, capitalized, or recognized over time? | Incremental acquisition costs, fulfillment costs, right-to-use licenses, right-to-access licenses, and upfront fees |
| Revenue Presentation and Disclosure Requirements | How should revenue and contract balances be presented and explained? | Contract assets, contract liabilities, disaggregation, remaining performance obligations, and significant judgments |
flowchart LR
A["1. Identify the contract"] --> B["2. Identify performance obligations"]
B --> C["3. Determine transaction price"]
C --> D["4. Allocate price to obligations"]
D --> E["5. Recognize revenue when control transfers"]
The steps are sequential. A contract with unclear collection or enforceable rights may fail Step 1. A bundle of promises may need to be separated or combined in Step 2. Variable consideration and financing issues affect Step 3. Standalone selling prices drive Step 4. Over-time versus point-in-time transfer is decided in Step 5.
| Checkpoint | What to decide | Common FAR trap |
|---|---|---|
| Contract enforceability | Whether approved rights, payment terms, commercial substance, and probable collection exist. | Recognizing revenue before Step 1 has been satisfied. |
| Distinct promises | Whether goods or services are separately identifiable and provide benefit on their own or with readily available resources. | Treating a bundled arrangement as one obligation without testing distinctness. |
| Transaction price | Whether variable consideration, refunds, rebates, bonuses, financing, noncash consideration, or consideration payable to a customer affects measurement. | Including variable consideration that should be constrained. |
| Allocation | Whether standalone selling prices are observable, estimated, or subject to a discount or variable amount allocation. | Allocating cash received rather than the transaction price. |
| Control transfer | Whether the customer receives control over time or at a point in time. | Equating billing, cash collection, or legal title with revenue when control has not transferred. |