FAR coverage of contract identification, performance obligations, transaction price, allocation, and revenue recognition timing.
ASC 606 recognizes revenue to depict the transfer of promised goods or services to customers in an amount that reflects the consideration the entity expects to receive. FAR questions usually test whether the candidate can apply the sequence, not merely recite it.
The five steps are sequential. If a valid contract does not exist, the remaining steps do not create revenue. If performance obligations are misidentified, transaction price allocation and revenue timing will also be wrong.
| Step | Question | Main FAR risk |
|---|---|---|
| 1. Identify the contract with a customer | Does an enforceable customer contract exist? | Recognizing revenue before enforceable rights, payment terms, or probable collection exist |
| 2. Identify performance obligations | What distinct goods or services were promised? | Separating promises that should be combined, or combining promises that are distinct |
| 3. Determine transaction price | How much consideration does the entity expect to receive? | Ignoring variable consideration, financing, noncash consideration, or consideration payable to the customer |
| 4. Allocate transaction price | How should the price be assigned to performance obligations? | Allocating based on cost or billing schedule instead of relative standalone selling price |
| 5. Recognize revenue | When does control transfer? | Recognizing revenue based on cash collection instead of satisfaction of the performance obligation |
flowchart LR
A["1. Identify contract"] --> B["2. Identify performance obligations"]
B --> C["3. Determine transaction price"]
C --> D["4. Allocate transaction price"]
D --> E["5. Recognize revenue when control transfers"]
A contract exists under ASC 606 only when enforceable rights and obligations are present. Contracts can be written, oral, or implied by customary business practice, but the arrangement must satisfy the contract criteria.
Key criteria include:
The customer must be obtaining goods or services that are outputs of the entity’s ordinary activities. A collaboration or cost-sharing arrangement may not be a customer contract if the counterparty is not purchasing goods or services as a customer.
Contract modifications are also tested in Step 1. A modification is treated as a separate contract when it adds distinct goods or services and the price increases by an amount that reflects standalone selling price. Otherwise, the entity evaluates whether the remaining goods or services are distinct and accounts for the modification prospectively or as part of the existing contract.
A performance obligation is a promise to transfer a distinct good or service to the customer. A promised good or service is distinct only if both criteria are met:
This step prevents mechanical separation of every contract line item. If goods or services are highly integrated, highly interdependent, or significantly modify each other, they may form one combined performance obligation.
| Fact pattern | Likely conclusion |
|---|---|
| Standard product plus optional support sold separately | Multiple performance obligations may exist |
| Customized system requiring design, integration, and installation | Promises may be combined into one performance obligation |
| Stand-ready service over a contract term | A performance obligation satisfied over time |
| Administrative setup activity that does not transfer a good or service | Not a separate performance obligation |
The transaction price is the amount of consideration the entity expects to be entitled to for transferring goods or services. This amount may differ from the stated contract price.
Common adjustments include:
Variable consideration is estimated using either the expected value method or the most likely amount method, depending on which better predicts the consideration. The estimate is constrained. Include variable consideration only to the extent it is probable that a significant reversal of cumulative revenue will not occur when the uncertainty is resolved.
The exam trap is recognizing the highest possible bonus or incentive merely because it is contractually available. ASC 606 requires both estimation and constraint.
When a contract has more than one performance obligation, the transaction price is allocated based on relative standalone selling prices.
[ \text{Allocated price to obligation} = \frac{\text{Standalone selling price of obligation}}{\text{Total standalone selling prices}} \times \text{Transaction price} ]
Standalone selling price is the price at which the entity would sell the good or service separately to a similar customer in similar circumstances. If directly observable prices are unavailable, the entity estimates them using methods such as adjusted market assessment, expected cost plus margin, or a residual approach when the selling price is highly variable or uncertain.
For example, assume a contract price of $1,600 includes a license with standalone selling price of $900, installation with standalone selling price of $300, and support with standalone selling price of $600. Total standalone selling prices are $1,800. The license allocation is $800, calculated as $900 divided by $1,800 multiplied by $1,600.
| Obligation | Standalone selling price | Allocation |
|---|---|---|
| License | $900 | $800 |
| Installation | $300 | $267 |
| Support | $600 | $533 |
| Total | $1,800 | $1,600 |
Revenue is recognized when, or as, the entity satisfies each performance obligation by transferring control to the customer. Control means the customer can direct the use of the asset and obtain substantially all remaining benefits.
Revenue is recognized over time if at least one over-time criterion is met:
If none of the over-time criteria are met, revenue is recognized at a point in time. Indicators of point-in-time transfer include present right to payment, transfer of legal title, physical possession, significant risks and rewards of ownership, and customer acceptance.
| Trap | Better FAR reasoning |
|---|---|
| Recognizing revenue when cash is received | Cash receipt creates revenue only when the performance obligation is satisfied |
| Treating every listed deliverable as distinct | Apply both distinct criteria and combine highly integrated promises |
| Ignoring collection probability | A contract may fail Step 1 if collection is not probable |
| Allocating based on invoice amounts | Use relative standalone selling prices unless a specific exception applies |
| Recognizing all variable consideration | Apply the constraint to avoid significant revenue reversal |
| Assuming long-term contracts are always over time | At least one ASC 606 over-time criterion must be met |