How do you account for a contract modification under ASC 606?

ASC 606RevenueContract modificationsUpdated October 2026
The short answer

Under ASC 606, an approved change in a contract's scope or price is a contract modification (ASC 606-10-25-10). It is a separate contract when it adds distinct goods or services priced at their standalone selling prices, adjusted for the circumstances of the contract (ASC 606-10-25-12). Otherwise the remaining goods or services decide the treatment (ASC 606-10-25-13): if they are distinct from what has already been transferred, the modification is accounted for prospectively as a termination of the old contract and creation of a new one; if they are not distinct and form part of a partially satisfied performance obligation, the modification is accounted for on a cumulative catch-up basis; and a mix of the two is handled consistently with those objectives. A subscription or service contract that is a series of distinct periods usually lands in the prospective model.

Is it a modification at all?

ASC 606-10-25-10 defines a contract modification as a change in the scope or price (or both) of a contract that is approved by the parties. It exists when the parties approve a change that creates new enforceable rights and obligations or changes existing ones. Three features of the definition matter:

  • Approval can be written, oral, or implied by customary business practice. Until the parties approve the change, the entity keeps accounting for the existing contract.
  • A modification can exist before the price is agreed. If the parties have approved a change in scope but not the corresponding price — an unpriced change order — the entity estimates the change in transaction price under the variable consideration guidance, including the constraint (ASC 606-10-25-11). A dispute about scope or price does not prevent a modification from existing, provided the new rights are enforceable.
  • Not every change in price is a modification. The resolution of variability that existed at inception — a bonus earned, a rebate tier reached — is a change in transaction price under ASC 606-10-32-42 through 32-45, not a modification. A concession the customer could have expected from the entity's past practice, or one granted because of performance problems, generally belongs to the original contract as variable consideration. Price changes driven by new market conditions that were not anticipated at inception, and are unrelated to performance issues, are more likely modifications.

The distinction is not academic: a change in transaction price is allocated on the original basis and can produce an immediate catch-up for satisfied obligations, while a modification can push the change forward into future periods.

One more boundary: contracts entered into at or near the same time with the same customer are evaluated under the combination criteria in ASC 606-10-25-9 before the modification guidance is applied. A "new" order signed alongside an amendment may in substance be part of the modification.

The decision tree

QuestionIf yesTreatment
1. Does the modification add distinct goods or services and increase the price by their standalone selling prices (adjusted for the contract's circumstances)?Separate contractOriginal contract unchanged; new contract accounted for on its own (ASC 606-10-25-12)
2. If not, are the remaining goods or services distinct from those already transferred?ProspectiveTerminate the old contract and create a new one; reallocate remaining consideration (ASC 606-10-25-13(a))
3. Are the remaining goods or services part of a single, partially satisfied performance obligation?Catch-upUpdate the transaction price and measure of progress; adjust revenue at the modification date (ASC 606-10-25-13(b))
4. Some of each?CombinationApply (a) and (b) to the respective parts consistently with their objectives (ASC 606-10-25-13(c))

The separate contract test

Both conditions in ASC 606-10-25-12 must be met. The added goods or services must be distinct under ASC 606-10-25-18 through 25-22, and the price increase must reflect their standalone selling prices, adjusted for the circumstances of the particular contract. The Codification's own example of an acceptable adjustment is a discount reflecting selling costs the entity avoids by selling to an existing customer. A price within the entity's normal range for comparable sales to existing customers can qualify; a deep discount that cannot be explained by those circumstances does not.

A modification that only reduces scope or only changes price can never be a separate contract — nothing distinct is added. Scope reductions and price-only changes go straight to ASC 606-10-25-13.

The prospective model

When the remaining goods or services are distinct from those already transferred, ASC 606-10-25-13(a) accounts for the modification as if the existing contract were terminated and a new contract created. The consideration allocated to the remaining performance obligations is the sum of:

  1. the consideration promised by the customer (including amounts already received) that was included in the transaction price but not yet recognized as revenue; and
  2. the consideration promised as part of the modification.

Nothing already recognized is revisited. This model also applies to a single performance obligation that is a series of distinct goods or services under ASC 606-10-25-14(b): the remaining months of a subscription are distinct from the months already delivered, so a mid-term change in a subscription is generally prospective even though the subscription is one performance obligation.

The cumulative catch-up model

When the remaining goods or services are not distinct and are part of a single performance obligation that is partially satisfied — the classic construction contract — ASC 606-10-25-13(b) treats the modification as part of the existing contract. The effect on the transaction price and on the measure of progress is recognized as an adjustment to revenue at the modification date.

Worked example 1: a SaaS subscription modified one year in

Base facts: a three-year subscription at $120,000 a year ($360,000 total), billed annually in advance. The subscription is one stand-ready performance obligation satisfied ratably — a series of distinct monthly periods — so revenue is $10,000 a month. At the start of Year 2, $120,000 has been recognized and $240,000 of the original consideration remains unrecognized. List price for additional seats is $36,000 a year per 50 seats, and the company routinely grants existing customers expansion discounts of up to about 15–20% because it avoids new-customer selling costs.

Version A — add seats at a price within the normal range

The customer adds 50 seats for the remaining 24 months at $30,000 a year (a one-sixth discount, within the normal expansion range). The seats are distinct and priced at standalone selling price as adjusted for the circumstances, so both ASC 606-10-25-12 conditions are met.

Original contract (unchanged)          $10,000 per month
New contract: $60,000 / 24 months       $2,500 per month
Total revenue, Months 13–36            $12,500 per month

Version B — add seats at a 50% discount

Same seats, but priced at $18,000 a year. The discount is outside anything the company's standalone selling price range supports, so condition (b) fails. The remaining services (24 months for the original seats plus the new seats) are distinct from the 12 months already delivered, so ASC 606-10-25-13(a) applies:

Unrecognized original consideration      $240,000
Consideration added by modification
  ($18,000 x 2 years)                      36,000
Consideration for remaining services     $276,000
Recognized over 24 months                 $11,500 per month

The effective discount on the new seats is spread over all remaining services, not just the new seats. No revenue already recognized changes.

Version C — blend and extend

Instead, the customer extends the subscription by two years (to five years in total) and the company drops the price for all four remaining years to $100,000 a year. Year 2 and Year 3 pricing is lower than originally agreed, and the extension years are priced below the $120,000 standalone selling price, so this is not a separate contract. The remaining months are distinct, so the modification is prospective:

Unrecognized original consideration      $240,000
Consideration added by modification
  ($400,000 new total - $240,000)         160,000
Consideration for remaining 48 months    $400,000
Recognized per month                       $8,333

The price cut on the original Years 2 and 3 is not a catch-up reduction; it is absorbed into the prospective rate. Here the new annual invoices happen to equal annual revenue, but if the amendment had priced the remaining years unevenly (say, $90,000 for Years 2 and 3 and $110,000 for the extension years), revenue would still be $8,333 a month and the difference would build a contract asset that later reverses.

Worked example 2: a construction change order (cumulative catch-up)

A contractor is building a laboratory for a fixed price of $5,000,000 with estimated costs of $4,000,000, recognizing revenue over time using costs incurred. When costs of $1,600,000 have been incurred (40% complete), it has recognized $2,000,000 of revenue.

The customer approves a change order for an upgraded HVAC system that is integrated into the building and is not distinct from it. The price increases by $600,000 and estimated costs increase by $400,000. Because the remaining work forms part of a single, partially satisfied performance obligation, ASC 606-10-25-13(b) applies.

Updated transaction price               $5,600,000
Updated estimated costs                 $4,400,000
Progress: $1,600,000 / $4,400,000          36.36%
Cumulative revenue: $5,600,000 x 36.36%  $2,036,364
Less: revenue recognized to date         (2,000,000)
Catch-up adjustment at modification          $36,364
Modification date
Dr. Contract asset                       36,364
Cr. Revenue                                      36,364

The catch-up can go either way: a change order with a lower margin than the base contract produces a negative adjustment, because progress falls as estimated total costs rise.

If the parties had approved the HVAC scope change but not yet agreed the price, ASC 606-10-25-11 would require the contractor to estimate the price change as variable consideration — say, a range of $400,000 to $600,000 — and include only the amount that clears the constraint in ASC 606-10-32-11, updating it as negotiations progress.

Changes in transaction price after a modification

Variable consideration that was promised before a modification and later changes needs care. ASC 606-10-32-45 generally allocates a change in transaction price that occurs after a modification to the performance obligations identified in the modified contract. The exception is a modification accounted for as a termination and new contract under ASC 606-10-25-13(a): to the extent the change is attributable to variable consideration promised before the modification, it is allocated to the performance obligations identified in the contract before the modification, which can include obligations already satisfied.

Scope reductions and partial terminations

A customer that cuts seats, cancels a phase, or shortens a term is also modifying the contract. Because nothing distinct is added, it is not a separate contract; the remaining goods or services determine whether it is prospective or catch-up. For a subscription, the remaining months are distinct, so the reduced consideration is spread over the remaining term. Contract costs capitalized under ASC 340-40 should be reassessed for impairment when the expected consideration falls.

Common pitfalls

  • Treating every amendment as a separate contract. The standalone selling price condition is a real test: document the price range and why the modified price fits it.
  • Using catch-up accounting for subscription changes. A series of distinct periods points to the prospective model even though the subscription is one performance obligation.
  • Recognizing concessions as modifications. Concessions that reflect past practice, disputes, or performance issues usually belong to the original contract as variable consideration and may require an immediate adjustment.
  • Ignoring unpriced change orders. An approved but unpriced scope change is a modification now; waiting for the final price defers revenue that the constrained estimate would support.
  • Losing the contract asset or liability. Prospective reallocation often moves revenue away from the billing schedule, and the contract balance disclosures in ASC 606-10-50-8 through 50-10, including the explanation of significant changes in contract assets and liabilities, need to reflect it.

Frequently asked questions

When is a contract modification a separate contract under ASC 606?

Only when it adds distinct goods or services and the price increases by their standalone selling prices, adjusted for the circumstances of the particular contract (ASC 606-10-25-12). A discount reflecting avoided selling costs can still qualify; a deep discount that the standalone selling price range cannot support does not.

What is the difference between the prospective and cumulative catch-up methods?

Under ASC 606-10-25-13(a), when the remaining goods or services are distinct, the remaining unrecognized consideration plus the new consideration is allocated to the remaining obligations going forward. Under ASC 606-10-25-13(b), when the remaining work is part of a partially satisfied single obligation, the updated price and progress are applied cumulatively and the difference is recognized at the modification date.

Is a SaaS upgrade accounted for prospectively?

Usually. A subscription is typically a series of distinct periods, so the remaining months are distinct from those already delivered. Unless the upgrade qualifies as a separate contract, it is accounted for as a termination and new contract, with remaining consideration recognized over the remaining term.

How do you account for an approved change order without an agreed price?

It is a contract modification once the scope change is approved and enforceable. The entity estimates the change in transaction price as variable consideration and includes it subject to the constraint (ASC 606-10-25-11), updating the estimate as the price is negotiated.

Is every price change a contract modification?

No. Resolving variability that existed at inception is a change in transaction price under ASC 606-10-32-42 through 32-45, and concessions the customer could expect from past practice or performance issues generally belong to the original contract. A modification is a change that the parties approve and that creates or changes enforceable rights and obligations.

Related guides

Run this question against the actual guidance

ResearchIQ answers it from the Big 4 handbooks plus SEC sources, with every claim cited to the page — then drafts the memo.

Try it free — no card required

This guide is an educational research starting point, not professional advice. Conclusions depend on specific facts and circumstances — consult your advisers, and verify every citation against the authoritative text.