32.1 Revenue Contract Modifications and Variable Consideration
Key Takeaways
- The 2026 FAR Blueprint keeps revenue recognition in Area III (Select Transactions, weighted roughly 25-35%), emphasizing application of the ASC 606 five-step model and revenue journal entries.
- A modification is a separate contract only when it adds distinct goods or services priced at standalone selling price (SSP) plus normal small adjustments.
- When remaining goods are distinct but the modification is not a separate contract, account for it prospectively as termination of the old contract and creation of a new one.
- Variable consideration is estimated using expected value (many outcomes) or most likely amount (binary), then constrained to the amount probable not to reverse significantly.
- Sales- or usage-based royalties on licenses are recognized at the later of the sale/usage or satisfaction of the related performance obligation.
Why Modifications And Estimates Matter
Revenue recognition under Accounting Standards Codification (ASC) 606 is easy to state and hard to execute under time pressure. The 2026 AICPA FAR Blueprint places revenue recognition in Area III, Select Transactions, and expects candidates to recall and apply the five-step model, determine revenue timing and amount, account for contract costs, and prepare journal entries. Because FAR is 50% multiple-choice and 50% task-based simulations, expect both a quick conceptual multiple-choice question and a multi-exhibit simulation on the same topic.
Start With The Five-Step Frame
| Step | Question | Common FAR Evidence |
|---|---|---|
| 1. Contract | Are parties committed, with identifiable rights, payment terms, substance, and probable collectibility? | Signed agreement, purchase order, cancellation terms. |
| 2. Performance obligations | Which promised goods or services are distinct? | Product list, service-level agreement, installation requirement. |
| 3. Transaction price | What consideration is expected after variable amounts and the constraint? | Bonus clause, rebate schedule, refund history. |
| 4. Allocation | How is price assigned to each obligation? | Standalone selling prices and discount facts. |
| 5. Recognition | When does control transfer (point in time or over time)? | Delivery terms, acceptance, progress measures. |
A contract modification is a change in scope, price, or both that the parties approve. Approval can be written, oral, or implied by customary business practice, but FAR facts normally make it visible. Once approved, ask two questions: did the modification add distinct goods or services, and did the price increase by an amount that reflects standalone selling price (SSP) for those added goods (plus reasonable adjustments for circumstances of the specific contract)?
Three Modification Outcomes
| Outcome | When It Applies | Accounting Result |
|---|---|---|
| Separate contract | Adds distinct goods/services at SSP. | Old contract unchanged; account for the addition as its own new contract. |
| Prospective (termination/new) | Remaining goods are distinct, but price does not reflect SSP. | Treat the old contract as terminated; allocate unrecognized + new consideration across remaining distinct goods going forward. |
| Cumulative catch-up | Remaining goods are NOT distinct (part of one partially satisfied obligation). | Update total transaction price and measure of progress; record catch-up revenue at the modification date. |
A practical hybrid exists: if a modification affects both distinct and not-yet-distinct promises, apply the prospective and catch-up rules to the respective portions.
Worked Example
A vendor agrees to deliver 100 identical units at $1,000 each. After 60 units transfer, the customer adds 40 more units at $700 each; $700 is below SSP because it reflects a concession. The 40 remaining original units plus the 40 added units (80 total) are distinct, so combine the unrecognized original consideration (40 x $1,000 = $40,000) with the new consideration (40 x $700 = $28,000) = $68,000 over 80 units = $850 per unit recognized prospectively. The 60 units already recognized are not restated.
Variable Consideration Workflow
Variable consideration includes bonuses, penalties, rebates, refunds, volume discounts, price concessions, and incentives. Estimate it using the method that best predicts the amount: expected value (probability-weighted) for a large number of outcomes, or most likely amount for a binary outcome (earn the bonus or not). Then apply the constraint: include variable consideration only to the extent it is probable that a significant revenue reversal will not occur when the uncertainty resolves.
The constraint is a reversal-risk rule, not a blanket pessimism rule. Evidence supporting inclusion: strong experience with similar contracts, short uncertainty period, outcomes within the entity's influence. Evidence supporting exclusion: a new product, volatile market prices, customer discretion, long resolution periods, or outcomes driven by third parties.
Exam Traps
- Do not confuse cash with revenue. A customer deposit is a contract liability until performance occurs.
- Do not confuse billing with a receivable. A receivable requires an unconditional right to consideration; otherwise the asset is a contract asset.
- Do not spread a discount across every promise if the facts show it relates only to specific obligations.
- For licenses, sales-based or usage-based royalties are recognized at the later of the customer's sale/usage or satisfaction of the related obligation - never accrued early.
- For a right of return, recognize revenue net of expected refunds, record a refund liability, and book an asset for the right to recover returned inventory.
Allocation And Discounts
Step 4 allocation matters more than candidates expect. Allocate the transaction price to each performance obligation in proportion to relative standalone selling price. When the sum of observable standalone prices exceeds the contract price, a discount exists. The default is to spread that discount proportionately across all obligations.
Allocate the discount entirely to one or more (but not all) obligations only when three conditions hold: the entity regularly sells each good or service separately, it regularly sells a bundle at a discount, and the bundle discount is substantially the same as the contract discount and traceable to specific obligations. A common trap places the entire discount on the obligation already satisfied to inflate current revenue.
When standalone selling price is not directly observable, estimate it. Acceptable methods include the adjusted market assessment approach, the expected cost plus a margin approach, and, only in limited cases, the residual approach (total price minus observable prices of other goods), permitted when the selling price is highly variable or uncertain.
Principal Versus Agent
Watch whether the entity is a principal (controls the good before transfer, records gross revenue) or an agent (arranges for another party to provide the good, records net commission). Indicators of control include primary responsibility for fulfillment, inventory risk before transfer, and discretion in setting price. A reseller that takes title and bears returns risk is usually a principal; a marketplace that merely connects buyer and seller is usually an agent reporting only its fee as revenue.
Simulation Checklist
- Mark every original and modified promise.
- Identify what transferred before the modification date.
- Choose separate contract, prospective, or cumulative catch-up.
- Build the transaction price with constrained variable consideration.
- Allocate price to unsatisfied or partially satisfied obligations.
- Record revenue, contract asset/liability, receivable, refund liability, and cash separately.
A supplier contracts to sell 100 identical devices for $900 each. After 40 devices are delivered, the customer adds 60 identical devices for $720 each. The added price is below standalone selling price because the supplier granted a discount unrelated to the original units. The remaining devices are distinct. How should the modification be accounted for?
A contractor will receive a $50,000 performance bonus if a project is completed by September 30. Management concludes there is a 70% probability of earning the full bonus and a 30% probability of earning no bonus. The outcome is binary, and there are no indicators of significant reversal beyond normal completion risk. What variable consideration estimate is generally most appropriate before applying allocation?