BAR · Technical Accounting and Reporting · 9 practice questions
ASC 606: Cumulative Catch-Up for Contract Modifications
Non-distinct additions to a partially satisfied over-time performance obligation require a cumulative catch-up adjustment. Below, follow BuildCo's integrated renovation modification through a cost-to-cost decision tree.
Try one first
Hint
First apply the ASC 606 modification test: are the added goods or services distinct and is the change priced at a standalone selling price? If not, use the cumulative catch-up, recompute percent complete using revised total expected costs under the cost-to-cost method before comparing to previously recognized cumulative revenue.
Answer B. Because the added HVAC and lobby work are not distinct from the original renovation and the modification is not priced at a standalone selling price, ASC 606 requires the modification to be accounted for as part of the existing contract (cumulative catch-up). Revised transaction price = $5,000,000 + $800,000 = $5,800,000; revised expected total costs = $4,000,000 + $1,000,000 = $5,000,000. Percent complete to date = $1,600,000 ÷ $5,000,000 = 32%, so cumulative revenue = 32% × $5,800,000 = $1,856,000. Because $2,000,000 had already been recognized, the catch-up is a $144,000 reduction in revenue in the period of modification.
Why not A: Tempting because the contract's scope and price increased, which in some cases results in separate-contract accounting. However, ASC 606 permits separate-contract treatment only when the additional goods or services are distinct and the price reflects their standalone selling price. The fact states the added work is not distinct and is not priced at standalone selling price, so separate-contract accounting (and leaving prior revenue unchanged) is inappropriate.
Why not C: Tempting because a candidate might view the parties' approval of additional work as creating a replacement contract and therefore account prospectively. Under ASC 606, prospective (termination-and-replacement) or prospective-only treatment is appropriate when the modification results in distinct performance obligations that do not affect revenue for goods or services already transferred. Because the added HVAC and lobby work are not distinct and must be integrated, you cannot treat the modification prospectively; you must update transaction price and total expected costs and apply the cumulative catch-up.
Why not D: Tempting because a candidate might incorrectly apply the prior 40% completion (1,600,000 ÷ 4,000,000) to the revised price, giving 40% × $5,800,000 = $2,320,000. That fails because under cost-to-cost you must update the denominator to revised total expected costs (now $5,000,000), so percent complete is 1,600,000 ÷ 5,000,000 = 32% and cumulative revenue is 32% × $5,800,000 = $1,856,000, not $2,320,000.
Decide it in order
T1BuildCo has a single renovation performance obligation satisfied over time. Approved HVAC and lobby additions must be integrated with the partially completed renovation. Are the additions distinct in the context of the contract?
YesThis non-distinct-work catch-up path does not apply. Evaluate the modification under the other ASC 606 modification guidance.NoGo to T2T2Has BuildCo already partially satisfied the single over-time performance obligation?
YesGo to T3NoUpdate the existing obligation's transaction price and progress estimates. With no performance yet transferred, there is no previously recognized revenue to adjust.T3BuildCo incurred $1,600,000 and recognized $2,000,000. Revised price = $5,000,000 + $800,000 = $5,800,000. Revised expected costs = $4,000,000 + $1,000,000 = $5,000,000. Cost-to-cost progress = 32%; revised cumulative revenue = $1,856,000. Is that below revenue already recognized?
YesRecord a downward cumulative catch-up: $1,856,000 − $2,000,000 = −$144,000. Reduce current-period revenue by $144,000.NoSubtract previously recognized revenue from revised cumulative revenue. Record an upward catch-up if positive; record no adjustment if zero.
Key points
- Remember: Integrated added work means recomputing revenue to date, not just recognizing the added contract price.
- Update both the transaction price and total expected costs under cost-to-cost.
- A higher contract price can still produce a revenue reduction when revised progress falls.
How the exam traps you
- Treat the approved HVAC and lobby additions as a separate contract. The work is not distinct because BuildCo must integrate it into the existing renovation.
- Keep the original 40% progress after increasing the contract price. Use revised expected costs: $1,600,000 ÷ $5,000,000 = 32%.
- Report $1,856,000 as the current-period adjustment. Subtract $2,000,000 already recognized. The adjustment is a $144,000 revenue reduction.
Question 2
Hint
Work the modification in two steps: first decide whether it is a separate contract, then determine whether any remaining goods are distinct from those already transferred.
Answer C. The added units are distinct, but the additional price does not reflect the standalone selling price (20 units at the current SSP of $450 would total $9,000, not $8,400). Therefore the modification is not a separate contract. Because the remaining promised goods are distinct from those already transferred, Blue accounts for the modification prospectively by combining the remaining original consideration ($30,000) with the modification price ($8,400) and allocating $38,400 over the 80 remaining units, or $480 per unit.
Why not A: This is tempting because added goods are distinct. However, a separate-contract treatment also requires that the modification price reflect the standalone selling price of the added goods. Here the added units are priced below current SSP, so the modification is not a separate contract.
Why not B: A cumulative catch-up is used when the remaining goods are not distinct from those already transferred and the modification changes the measure of progress for a single performance obligation. Here each unit is distinct, so the modification is handled prospectively rather than by restating revenue.
Why not D: This option conflates operational sequencing with the accounting model. The modification must be assessed at the modification date. Because the modification is not accounted for as a separate contract, Blue must combine and allocate the remaining consideration prospectively across the 80 remaining units rather than delaying recognition of the added units.
Question 3
Hint
First decide whether the modification is a separate contract. Then determine whether the remaining services are distinct from those already transferred before computing any revised per-visit revenue.
Answer C. The added visits are distinct, but the price increase does not reflect their standalone selling price, so the modification fails the separate-contract test. Because the remaining visits are distinct from those already transferred, the modification is accounted for prospectively as if the old contract were terminated and a new contract created under ASC 606. Seller allocates the remaining unrecognized consideration from the original contract ($200,000 − $80,000 = $120,000) plus the additional $48,000, for a total of $168,000 over 90 remaining visits = $1,866.67 per visit.
Why not A: Tempting because the added visits are distinct (one condition for separate-contract treatment). However, separate-contract accounting also requires that the price for the added goods reflect their standalone selling price (or an appropriate adjustment). The stem explicitly says the $48,000 increase does not reflect the standalone selling price, so separate-contract treatment is inappropriate.
Why not B: This distractor plays on the idea of a series being one performance obligation, but a cumulative catch-up is required only when the remaining goods or services are not distinct from those already transferred. The stem states the remaining and added visits are distinct from those already transferred, so the modification is handled prospectively, not with a catch-up.
Why not D: This choice correctly rejects separate-contract treatment but incorrectly replaces the contractually agreed additional consideration with a hypothetical current standalone selling price. When a modification is accounted for prospectively (termination and new contract), the allocation uses the remaining unrecognized consideration plus the actual additional consideration promised, not an assumed current-price amount.
Question 4
Hint
Ask two questions in order: Are the added goods distinct, and is the added price based on standalone selling price at the modification date rather than the original contract price?
Answer A. Under ASC 606, a contract modification is accounted for as a separate contract if it adds distinct goods or services and the consideration for those added goods equals their standalone selling price at the modification date. The added 30 devices are distinct and are priced at Apex's current standalone selling price of $190 each, so the modification is a separate contract. The original contract continues for the remaining 60 devices and previously recognized revenue for the 40 delivered devices is unaffected.
Why not B: Termination-and-replacement (prospective blended treatment) would be appropriate when the modification effectively replaces the existing contract or the remaining goods are not distinct in a way that justifies separate-contract treatment. Here the added devices are distinct and the consideration for them equals their standalone selling price, so you do not terminate and replace the original contract.
Why not C: A cumulative catch-up adjustment is required when a modification combines with the original contract such that previously satisfied performance obligations must be remeasured. Because each device is distinct, transferred at a point in time, and the added devices qualify as a separate contract, no catch-up to previously recognized revenue is required.
Why not D: Reallocating consideration across all units and adjusting revenue already recognized would reopen completed performance obligations. ASC 606 does not require that when the modification is accounted for as a separate contract for the added goods; previously recognized revenue for delivered devices remains unchanged.
Question 5
Hint
First determine whether the added modules are distinct in the context of the existing promise, standalone selling price alone does not decide the outcome.
Answer B. The added modules are integrated into and materially modify the same customized system (including rework), so they are not distinct from the originally promised combined output. Under ASC 606, a contract modification that does not add distinct goods or services is accounted for as part of the existing contract: the entity updates the transaction price and the measure of progress and recognizes the effect immediately as a cumulative catch-up adjustment to revenue.
Why not A: Why tempting: Candidates may overapply the standalone selling price heuristic, if the price equals standalone selling price it can appear to be a separate contract. Why wrong: ASC 606 requires assessing distinctness in the context of the contract; the modules are integrated and materially change the single performance obligation, so they fail the distinctness test even though the price equals standalone selling price.
Why not C: Why tempting: If remaining promised goods were distinct, a candidate might view the modification as replacing the original contract and account prospectively. Why wrong: The facts show an originally identified single integrated performance obligation and a modification that further changes that same obligation; this is not a termination-and-replacement scenario under ASC 606, so prospective new-contract accounting is inappropriate.
Why not D: Why tempting: Candidates sometimes confuse approved change orders with contingent or variable consideration and think recognition can be deferred. Why wrong: The parties approved both scope and price, creating an enforceable modification; ASC 606 requires accounting for an approved modification at the time of approval rather than deferring recognition until transfer.
Question 6
Hint
Apply the ASC 606 contract-modification sequence: first consider whether the added goods can be treated separately; if not, determine whether the remaining promised goods are distinct from those already transferred.
Answer A. Although the 20 added pumps are priced at their standalone selling price (which might suggest separate-contract treatment), the modification also changes the price of the remaining 60 promised pumps. Because the modification affects consideration for remaining promised goods, it cannot be treated solely as a separate contract for the added items. The remaining pumps are distinct from the 40 already delivered, so under ASC 606 the modification is accounted for prospectively as if the original contract were terminated and a new contract formed for the 80 pumps still to be delivered.
Why not B: Tempting because added goods priced at their standalone selling price often qualify as a separate contract. It is wrong here because the modification also reprices the remaining 60 promised pumps; when a modification changes consideration for remaining promised goods, you cannot treat only the additions as a separate contract.
Why not C: Tempting because the transaction price changed and catch-up adjustments apply when a modification effectively changes a single performance obligation. It fails here because the remaining pumps are distinct from the goods already transferred, so a cumulative catch-up is not appropriate and prospective accounting for the new contract is required.
Why not D: Tempting because the reduced price might look like an update to an estimate of variable consideration to be applied prospectively. However, the reduction is the result of a negotiated contract modification, not an update to an estimate, so contract-modification guidance, not a variable-consideration estimate change, governs the accounting.
Question 7
Hint
First determine whether the added months are distinct from the remaining promised services; if they are distinct, then assess whether the agreed price for the extension represents the standalone selling price in the relevant circumstances.
Answer A. ASC 606 directs a two-step assessment: (1) determine whether the added goods or services are distinct and (2) if distinct, determine whether the modification price reflects the standalone selling price of those added goods or services. The 10 added months are distinct future services, and Orion's routinely charged $42,000 for comparable 10-month extensions to existing customers (with no new setup or sales effort) is an observable price that supports treating the modification as a separate contract.
Why not B: Tempting because the original arrangement is a single series performance obligation, but cumulative catch-up applies only when the added goods or services are not distinct from those already promised. Here the 10 added months are distinct, so catch-up accounting is not the appropriate treatment.
Why not C: This distractor anchors on list price; a lower price for existing customers does not automatically require treating the change as a termination and new contract. ASC 606 allows observable prices for similar transactions (including routine prices charged to existing customers) to be persuasive evidence of standalone selling price.
Why not D: Plausible if the added services were distinct but the modification price did not reflect standalone selling price; in that scenario the entity would allocate the additional consideration prospectively. However, here the $42,000 is an observable price for similar extensions to existing customers, supporting separate-contract treatment instead of prospective reallocation.
Question 8
Hint
Decide whether the third-party module should be recognized separately when control transfers; if so, remove it from the cost-to-cost base, compute progress on the remaining performance, and then add any separately recognized amount.
Answer D. The module meets the uninstalled-materials facts and control transferred on delivery, so recognize revenue for the module at its cost of $300,000 when delivered. Exclude the module from the cost-to-cost progress measure; progress on the remaining performance = $150,000 / ($150,000 + $450,000) = 25%. Apply 25% to the remaining transaction price ($1,200,000 − $300,000 = $900,000) to get $225,000. Total recognized = $300,000 + $225,000 = $525,000 (consistent with ASC 606 uninstalled-materials treatment).
Why not A: Tempting because it equals progress on the remaining work (25% × $900,000), but it omits the separately recognized module amount ($300,000) that transferred control to the customer and should be recognized when delivered.
Why not B: This equals the module cost ($300,000) plus incurred other costs ($150,000) and reflects treating the remaining work as recognized only at cost (zero margin) rather than applying the cost-to-cost progress to the remaining transaction price, so it understates the required margin on remaining performance.
Why not C: This results from including the module in the cost-to-cost base (incurred costs $300,000 + $150,000 = $450,000 over total costs $900,000 → 50% × $1,200,000 = $600,000). That double-counts the module in progress and is incorrect because the module should be carved out and recognized at cost when control transferred.
Question 9
Hint
For a contract modification involving added goods, first decide whether the added goods are distinct, and then ask whether the added price reflects their stand-alone selling price.
Answer B. The added sensors are distinct, but the additional price ($85) does not reflect their stand-alone selling price ($90), so the modification is not a separate contract. Because the remaining performance obligations (the 80 unsatisfied sensors) are distinct from the 40 already transferred, Metro accounts for the modification prospectively, combining the remaining original consideration (60 × $100 = $6,000) with the added consideration (20 × $85 = $1,700) and allocating $7,700 across the 80 remaining sensors ($96.25 each).
Why not A: This is tempting because the added goods are distinct, but ASC 606 requires that the price for the additional goods reflect their stand-alone selling price to treat the modification as a separate contract. Here $85 is below the SSP of $90, so separate-contract treatment is inappropriate.
Why not C: Catch-up (a cumulative adjustment to revenue) is required when the remaining goods or services are not distinct from those already transferred. In this fact pattern each remaining sensor is distinct and satisfaction occurs at shipment, so the modification is handled prospectively, not by a catch-up.
Why not D: Incorrect because Metro must allocate the actual transaction price after the modification. Failing the separate-contract test does not let Metro substitute SSP for the agreed consideration; the $85 actual consideration for the added sensors must be combined with the remaining original consideration and allocated across the remaining obligations.
Common questions
When does an ASC 606 contract modification require cumulative catch-up?
When added work is not distinct and becomes part of a single, partially satisfied over-time performance obligation. BuildCo's integrated HVAC and lobby work meets that test.
How do you calculate cumulative catch-up using cost-to-cost?
Divide costs incurred by revised total expected costs, then multiply by the revised transaction price. Subtract revenue already recognized to find the adjustment.
Can a contract price increase cause a downward revenue adjustment?
Yes. BuildCo's revised progress is 32%, producing $1,856,000 of cumulative revenue despite the price increase. That is $144,000 below revenue already recognized.
Watch it solved
A full CPA BAR task-based simulation on Revenue recognition, worked step by step.
Multiple Performance Obligations & Contract Assets | CPA BAR TBS on YouTube
Practice BAR like the real exam
The free ChatCPA simulator: real exam layout, timed testlets, starting with a question on this topic. No account needed to start.
Open the free simulator →More on Revenue recognition
Questions from the ChatCPA bank of 17,658 CPA exam questions, each with a written reason for every wrong answer. ChatCPA is built by Nicholas Miller, CPA (Oregon #14907). How these pages are made. Spot an error? Tell us.