ASC 606 recognizes revenue in five steps, and FAR can test any of them. This lesson works through each step, then applies all five to one contract.
Step 1, the contract
The model applies only once a contract with a customer meets five criteria:
- Both sides have approved it (in any customary form) and intend to perform.
- Each party's rights can be identified.
- The payment terms can be identified.
- It has commercial substance: the entity's future cash flows are expected to change because of it.
- Collection is probable for substantially all of the consideration the entity will be entitled to for the goods or services it will actually transfer, judged on the customer's ability and intention to pay.
If a contract fails, cash received is a liability until the criteria are met, or until the cash is nonrefundable and one of three events occurs: nothing remains to deliver and substantially all the promised payment is in; the contract is terminated; or the entity has transferred what the cash relates to, has stopped, and owes nothing more.
Contributions to a not-for-profit are not customer contracts; they follow ASC 958-605 (ASU 2018-08).
Step 2, the performance obligations
A performance obligation is a promise to transfer a distinct good or service, or a series of distinct goods or services that are substantially the same and transfer to the customer in the same pattern. Distinct requires both:
- Capable of being distinct: the customer can benefit from it alone or with readily available resources (things sold separately by anyone, or already obtained).
- Distinct in the context of the contract: is the entity promising separate items, or one combined item they feed into? Signs of a combined item: the entity integrates the items into one output, one item significantly modifies or customizes another (or is modified by it), or the items are highly interdependent.
Items that fail are combined until the bundle is distinct. A warranty sold separately is a performance obligation. One included with the product is accrued as a warranty cost under ASC 460, except any part that provides a service beyond assuring the specifications.
Step 3, the transaction price
The transaction price is the consideration the entity expects to be entitled to, excluding amounts collected for others, like sales tax. It is also adjusted for a significant financing component, noncash consideration and consideration payable to the customer. Variable consideration (bonuses, penalties, rebates) is estimated by whichever method better predicts the amount, applied consistently: the expected value, probability-weighted and often suited to many similar contracts, or the most likely amount, often better when there are two possible outcomes.
Then the constraint: variable consideration enters the price only to the extent the entity judges that a significant reversal of cumulative revenue probably won't follow once the uncertainty clears. The risk is higher when the outcome hinges on factors the entity can't influence or will take long to resolve, or experience is thin. Update the estimate at each reporting date.
Noncash consideration is measured at fair value at contract inception. ASU 2025-07 (annual periods beginning after December 15, 2026) clarifies that shares or options a customer gives as payment are accounted for under ASC 606, not as derivatives or equity investments, until the right to them is unconditional.
Steps 4 and 5, allocation and timing
The price is allocated in proportion to each obligation's standalone selling price (SSP): what the entity would charge for that item alone. Observed separate prices are the best evidence; a list price isn't automatically the SSP. Otherwise it is estimated: adjusted market assessment, expected cost plus a margin, or, only for a highly variable or unset price, the residual approach. A bundle discount is spread across all obligations unless evidence ties it to specific ones.
Revenue is recognized when (or as) the customer obtains control. An obligation is satisfied over time if any one of these is true: the customer receives and consumes the benefit as the entity performs; the work creates or enhances an asset the customer controls as it is built; or the asset has no alternative use to the entity and the entity has an enforceable right to payment for work done to date. Otherwise it is satisfied at a point in time, shown by indicators such as possession, title and acceptance.
A worked example
On January 1, an equipment maker contracts to deliver a packaging robot, install it and service it for 24 months for a fixed 144,000. Installation is routine: other contractors offer it and it doesn't modify the robot, so there are three performance obligations. The customer will also pay a 12,000 bonus if the robot achieves 98% uptime over the 24 months. The model is unproven and uptime depends on the customer's plant, so the bonus is constrained to zero, to be reassessed each period.
| Obligation | SSP | Share | Allocated |
|---|---|---|---|
| Robot | 100,000 | 62.5% | 90,000 |
| Installation | 20,000 | 12.5% | 18,000 |
| Service (24 months) | 40,000 | 25% | 36,000 |
| Total | 160,000 | 100% | 144,000 |
The robot is delivered, with title, on February 1: 90,000. Installation is finished in February: 18,000. Service runs evenly from March 1 at 36,000 / 24 = 1,500 a month, so Year 1 gets 10 months, or 15,000. Year 1 revenue is 123,000; the other 21,000 follows over 14 months.
On the exam
Traps: a list price used as the SSP, a bundle discount put on one item without evidence, a two-outcome bonus estimated by expected value, and an assurance warranty treated as an obligation.