How are contract modifications accounted for under ASC 606?

Under ASC 606 Contract Modifications, a change in the scope or price of a contract is accounted for as either a new separate contract or a modification of the existing contract, depending on whether the change adds distinct goods or services at their standalone selling price. 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. Approval can be written, oral, or implied by customary business practice — but unapproved changes create a variable consideration question, not a modification. - New separate contract (ASC 606-10-25-12): Treat the modification as an entirely new, independent contract when (1) the modification adds one or more distinct goods or services (as defined in ASC 606-10-25-19 through 25-22), AND (2) the price of those goods or services reflects their standalone selling price. Revenue from the original contract continues unchanged; the new contract is accounted for prospectively going forward. - Prospective modification — termination and replacement (ASC 606-10-25-13(a)): If the remaining goods or services are distinct from those already transferred but the price does NOT reflect standalone selling price, terminate the original contract and create a new one. The transaction price is the sum of: (i) the consideration promised in the modification, plus (ii) any unsatisfied performance obligations from the original contract. Revenue is recognized prospectively on the new blended arrangement. - Cumulative catch-up adjustment (ASC 606-10-25-13(b)): If the remaining goods or services are not distinct (i.e., they form part of a single performance obligation already partially satisfied), treat the modification as if it were part of the original contract. Adjust revenue recognized to date using a cumulative catch-up entry — recognize the difference between revenue that should have been recognized under the modified terms and what was actually recognized, in the period the modification is approved.

If a contract modification is approved mid-period, how should cumulative catch-up revenue be presented in the income statement — separately or blended with regular revenue?

Now assume instead the modification involved adding more hours to an already-in-progress software implementation (a single, non-distinct performance obligation). If total expected costs increase and the modification changes the measure of progress, a cumulative catch-up applies: | Account | Dr | Cr | |---|---|---| | Contract Asset | 3,200 | | | Revenue — Implementation Services | | 3,200 | (Represents the incremental revenue earned to date under revised completion percentage.) - Conflating "approved" with "signed": Practitioners often wait for a written change order before recording a modification, missing oral or implied approvals that trigger accounting consequences immediately under ASC 606-10-25-10. Failure to identify timely modifications distorts period revenue. - Misclassifying distinct vs. non-distinct goods: Incorrectly determining that additional goods are not distinct leads entities to apply cumulative catch-up when the prospective approach is required — a frequent audit finding that can accelerate or defer significant revenue.

How does a contract modification interact with variable consideration constraints under ASC 606-10-32-11 through 32-16?

- Ignoring the standalone selling price test: Even when new goods are distinct, the treatment pivots entirely on whether the incremental price reflects standalone selling price. Using list price as a proxy for SSP without proper analysis (ASC 606-10-32-31 through 32-35) is an audit red flag and a common CPA exam trap. - ASC 606-10-25-10: Definition and approval threshold for contract modifications - ASC 606-10-25-12: Criteria for accounting as a new separate contract - ASC 606-10-25-13: Prospective and cumulative catch-up approaches for existing contract modifications - ASC 606-10-25-14: Guidance on mixed modifications with both distinct and non-distinct elements - ASC 606-10-32-31 through 32-35: Standalone selling price estimation methods

ASC 606 Contract Modifications

ASC 606 Contract Modifications — Core Rule

Under ASC 606 Contract Modifications, a change in the scope or price of a contract is accounted for as either a new separate contract or a modification of the existing contract, depending on whether the change adds distinct goods or services at their standalone selling price.

How ASC 606 Contract Modifications Works

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. Approval can be written, oral, or implied by customary business practice — but unapproved changes create a variable consideration question, not a modification.

Three accounting treatments apply

New separate contract (ASC 606-10-25-12): Treat the modification as an entirely new, independent contract when (1) the modification adds one or more distinct goods or services (as defined in ASC 606-10-25-19 through 25-22), AND (2) the price of those goods or services reflects their standalone selling price. Revenue from the original contract continues unchanged; the new contract is accounted for prospectively going forward.

Prospective modification — termination and replacement (ASC 606-10-25-13(a)): If the remaining goods or services are distinct from those already transferred but the price does NOT reflect standalone selling price, terminate the original contract and create a new one. The transaction price is the sum of: (i) the consideration promised in the modification, plus (ii) any unsatisfied performance obligations from the original contract. Revenue is recognized prospectively on the new blended arrangement.

Cumulative catch-up adjustment (ASC 606-10-25-13(b)): If the remaining goods or services are not distinct (i.e., they form part of a single performance obligation already partially satisfied), treat the modification as if it were part of the original contract. Adjust revenue recognized to date using a cumulative catch-up entry — recognize the difference between revenue that should have been recognized under the modified terms and what was actually recognized, in the period the modification is approved.

Mixed modifications (ASC 606-10-25-14): Some modifications include both distinct and non-distinct elements. In those cases, split the modification — apply the termination-and-replacement approach to the distinct portion and the cumulative catch-up approach to the non-distinct portion.

Disclosure: Entities must disclose judgments made in determining whether a modification creates a new contract or changes an existing one (ASC 606-10-50-17 through 50-20), particularly when these judgments materially affect the timing and amount of revenue.

ASC 606 Contract Modifications — Practical Example

Scenario: A SaaS company contracts to deliver 12 months of software access for $120,000 ($10,000/month). After month 4 (revenue recognized: $40,000), the customer requests an additional module for months 5–12 for an extra $6,400 total — but the standalone selling price of that module would be $8,000. Because the new module is distinct but not at standalone selling price, the company applies the prospective termination-and-replacement approach (ASC 606-10-25-13(a)).

Remaining consideration: Original unearned $80,000 + modification $6,400 = $86,400 recognized over 8 remaining months = $10,800/month.

Month 5 entry (and each subsequent month):

Account	Dr	Cr
Accounts Receivable	10,800
Revenue — SaaS Subscriptions		10,800

Now assume instead the modification involved adding more hours to an already-in-progress software implementation (a single, non-distinct performance obligation). If total expected costs increase and the modification changes the measure of progress, a cumulative catch-up applies:

Account	Dr	Cr
Contract Asset	3,200
Revenue — Implementation Services		3,200

(Represents the incremental revenue earned to date under revised completion percentage.)

ASC 606 Contract Modifications — Common Pitfalls

Conflating "approved" with "signed": Practitioners often wait for a written change order before recording a modification, missing oral or implied approvals that trigger accounting consequences immediately under ASC 606-10-25-10. Failure to identify timely modifications distorts period revenue.

Misclassifying distinct vs. non-distinct goods: Incorrectly determining that additional goods are not distinct leads entities to apply cumulative catch-up when the prospective approach is required — a frequent audit finding that can accelerate or defer significant revenue.

Ignoring the standalone selling price test: Even when new goods are distinct, the treatment pivots entirely on whether the incremental price reflects standalone selling price. Using list price as a proxy for SSP without proper analysis (ASC 606-10-32-31 through 32-35) is an audit red flag and a common CPA exam trap.

ASC 606 Contract Modifications — Key Paragraphs

ASC 606-10-25-10: Definition and approval threshold for contract modifications
ASC 606-10-25-12: Criteria for accounting as a new separate contract
ASC 606-10-25-13: Prospective and cumulative catch-up approaches for existing contract modifications
ASC 606-10-25-14: Guidance on mixed modifications with both distinct and non-distinct elements
ASC 606-10-32-31 through 32-35: Standalone selling price estimation methods