ASC 606 Contract Modifications: Separate Contract, Prospective, or Catch-Up
How to apply the two tests that determine whether a contract modification is a separate contract, a prospective change, or a cumulative catch-up adjustment under ASC 606.
Part 1: Fundamentals & the Five-Step Model · Part 2: Worked Examples · Part 3: Variable Consideration · Part 4: Contract Modifications · Part 5: Principal vs. Agent · Part 6: Licensing & Royalties
Quick Summary
- What counts: a contract modification is any change in the scope or price (or both) of a contract approved by both parties, whether in writing, by oral agreement, or implied by customary business practices.
- Three accounting outcomes: a modification is accounted for as a separate contract, as a termination of the old contract plus a new one (prospectively), or as part of the original contract (cumulative catch-up) — the outcome depends on two specific tests.
- Test 1 — Separate contract: applies only when the modification adds distinct goods or services priced at their standalone selling price (reflecting the specific contract’s circumstances).
- Test 2 — Remaining goods distinct or not: for modifications that aren’t separate contracts, whether the remaining goods or services are distinct from those already transferred determines a prospective vs. cumulative catch-up treatment.
- Judgment-heavy: unpriced change orders, scope changes negotiated over time, and partial terminations all require careful analysis of what was actually approved and when.
What Is a Contract Modification?
A contract modification is a change in the scope or price (or both) of a contract that is approved by the parties — whether that approval is in writing, oral, or implied by the parties’ customary business practices. Until a modification is approved, an entity continues to apply ASC 606 to the existing contract, without giving accounting effect to a potential or pending change; enforceable rights and obligations still matter, even ahead of a fully documented amendment.
Test 1: Is It a Separate Contract?
A contract modification is accounted for as a wholly separate contract — with no effect on the original contract’s accounting — only when both of the following are true: the modification adds distinct promised goods or services, and the price of the contract increases by an amount that reflects the entity’s standalone selling price of the additional goods or services (adjusted, as appropriate, for circumstances of that particular contract, such as an existing customer discount that doesn’t require renegotiating the whole relationship).
A SaaS vendor’s existing contract is expanded mid-term to add a distinct module at that module’s standalone selling price. Because the addition is distinct and priced at standalone selling price, it’s accounted for as a new, separate contract — the original contract’s revenue pattern is untouched.
Test 2: If Not Separate — Are the Remaining Goods Distinct?
When a modification isn’t accounted for as a separate contract, the entity evaluates whether the remaining goods or services to be transferred (as of the modification date) are distinct from those already transferred to the customer:
- Remaining goods/services are distinct: the modification is treated as a termination of the original contract and creation of a new contract. Remaining consideration (unrecognized transaction price from the original contract, plus any additional consideration from the modification) is allocated to the remaining performance obligations on a prospective basis — prior periods are not restated.
- Remaining goods/services are not distinct: they form part of a single, partially satisfied performance obligation that continues after the modification. The modification is accounted for on a cumulative catch-up basis — the transaction price and measure of progress are updated, and the effect on revenue already recognized is recognized immediately as an adjustment in the period of the modification.
Worked Example: Cumulative Catch-Up
A contractor is building a single, highly integrated facility for $4,000,000, with the entire project treated as one performance obligation recognized over time based on costs incurred. At the point the contractor has incurred $1,000,000 of costs against a $3,200,000 total estimated cost (31.25% complete), the customer approves a scope change adding $800,000 of price for additional integrated work that isn’t distinct from the work already underway — costs are expected to rise to $4,000,000 total.
Because the additional work isn’t distinct from the original scope, this is a cumulative catch-up. The updated transaction price is $4,800,000, and updated percent complete is $1,000,000 ÷ $4,000,000 = 25%. Cumulative revenue that should have been recognized to date is 25% × $4,800,000 = $1,200,000. If $1,250,000 had already been recognized under the original terms (31.25% × $4,000,000), the contractor would record a one-time revenue reduction of $50,000 in the period of modification to true the cumulative amount down to $1,200,000; if less had been recognized, the contractor would record a catch-up increase instead.
Unapproved Change Orders and Claims
Contractors and other entities that regularly negotiate scope changes need a process for evaluating unpriced or pending change orders — work performed before final price agreement. Revenue for such work is only recognized to the extent a modification (even an implied one, evidenced by the parties’ conduct) meets the general contract-existence criteria and the transaction price, including any variable consideration for the unpriced portion, can be estimated and isn’t fully constrained.
Common Pitfalls
- Treating every price change as a separate contract: the separate-contract test requires BOTH that the addition is distinct AND priced at standalone selling price — a discount granted for schedule reasons alone doesn’t qualify.
- Missing implied modifications: failing to recognize that a change approved only through conduct (not a signed amendment) still triggers modification accounting once it’s clear the parties have approved a change in scope or price.
- Restating prior periods: the prospective treatment for distinct remaining goods/services does not restate prior period revenue — only the cumulative catch-up treatment adjusts revenue already recognized, and only in the current period.
- Ignoring unpriced change orders: not evaluating whether work performed ahead of a final price agreement already meets the criteria to recognize some revenue, particularly on long-term contracts.
Navigating a Contract Modification or Change Order?
From classifying the modification type to recalculating transaction price and progress, our team can help you get the accounting right. Contact our Financial Advisory team today.
