A contract modification under ASC 606 is any change in the scope or price of a contract that is approved by both parties. How you account for it depends on whether the modification adds distinct goods or services at a price that reflects their standalone selling price. If yes, it’s a new contract. If not, it’s an adjustment to the existing contract — recognized either prospectively or through a cumulative catch-up, depending on whether the remaining goods and services are distinct from what has already transferred.
Modification guidance: ASC 606-10-25-10 through 25-13 · Distinct goods or services: ASC 606-10-25-14 through 25-22 · Modification scenarios: ASC 606-10-25-13
Contract modifications are where revenue recognition gets decided in real time and where most companies quietly accumulate accounting errors. A customer expands their subscription. A SaaS deal gets repriced mid-term. The project scope changes after delivery has started. Each of these is a modification under ASC 606, and each one triggers a classification decision that affects how much revenue you recognize and when.
The standard gives you three scenarios, and accounting differs significantly across them. Getting the scenario wrong doesn’t produce a small rounding error — it can shift material revenue between periods.
The Three Modification Scenarios
ASC 606-10-25-13 establishes three distinct accounting treatments based on two threshold questions: (1) does the modification add distinct goods or services, and (2) is the price for those goods or services commensurate with their standalone selling price (SSP)?
Scenario 1: Treat as a new contract (prospective)
The modification adds distinct goods or services, and the price reflects SSP. Account for it as if it’s a separate contract from the original. The original contract continues under its existing terms; the modification creates a new performance obligation at a new price. No adjustment to previously recognized revenue.
Example: A customer adds five more user seats to a SaaS contract at the same per-seat price charged to new customers. The new seats are distinct (same as what was already licensed), priced at SSP, a new contract accounting applies.
Scenario 2: Terminate original + create new contract (prospective)
The modification adds distinct goods or services, but the price does not reflect SSP (typically because the customer got a discount tied to the original deal). Terminate the original contract and create a new one. The remaining performance obligations from the original contract are bundled with the new obligations, and a new transaction price is allocated across all of them. No catch-up to prior-period revenue; the reallocation affects future periods only.
Example: Same SaaS expansion, but the customer negotiates a volume discount below SSP because of their existing relationship. The new seats are distinct, but the below-market pricing means you can’t treat this as a clean new contract. Terminate and replace.
Scenario 3: Modify the existing contract — cumulative catch-up
The modification doesn’t add distinct goods or services, it changes what the customer receives under the existing contract. The modification is treated as if it were part of the original contract. You recalculate the transaction price and measure progress as of the modification date and recognize a catch-up adjustment (positive or negative) immediately in the period of modification.
Example: A customer changes the configuration of a software implementation mid-project, adding functionality that’s deeply integrated with what’s already being built. The new work isn’t separable from the existing contract. Cumulative catch-up applies.
The classification decision that drives everything
The distinction between Scenarios 2 and 3, prospective vs. cumulative catch-up, hinges entirely on whether the modified goods or services are distinct from what has already transferred. That distinctness assessment is a judgment call under ASC 606-10-25-19 through 25-22. Get it wrong and you either defer revenue that should flow through immediately or accelerate revenue that should be spread prospectively.
What “Distinct” Actually Means in Practice
The distinctness test has two prongs under ASC 606-10-25-19: the customer can benefit from the good or service on its own (or together with other resources readily available), and the entity’s promise to transfer it is separately identifiable from the other promises in the contract.
The first prong is usually easy. Can the customer use this on its own? A software license is distinct on its own. A configuration that only functions within the platform you’re building for them may not be.
The second prong is where judgment lives. Separately identifiable means the promises aren’t highly interdependent or interrelated. In a SaaS context, adding user seats to an existing license is typically separately identifiable; the seats don’t change the underlying service. Adding a new module that requires significant integration with the in-flight implementation of work is a harder call. If the new work fundamentally changes what the entity promised to deliver, it’s likely not separately identifiable.
One nuance worth noting: a series of substantially identical distinct services can still be treated as a single performance obligation under ASC 606-10-25-14(a). That matters how you frame the distinctness analysis when modifications touch recurring service elements.
Document the distinctness assessment at the time of modification, not retroactively. The classification judgment belongs in the period it’s made.
Price Changes Without Scope Changes
Not every modification changes what the customer receives. Some just change the price — a mid-contract discount, a price concession, a repricing tied to market conditions.
If there’s no new scope, the modification doesn’t add distinct goods or services, so Scenario 3 applies by default: treat as a modification of the existing contract with a cumulative catch-up. The new price gets reallocated across remaining performance obligations, and you true up revenue recognized to date.
The practical trap here is treating price changes as prospective-only adjustments. A mid-contract discount that reduces the total transaction price isn’t just a “going forward” adjustment as it changes the allocation across the entire contract, including obligations already partially satisfied. The catch-up can be material, and it flows through current-period revenue, not future periods.
How Modifications Interact with Variable Consideration
Modifications and variable consideration interact in ways that compound if your systems aren’t set up to handle both simultaneously. When a contract with variable consideration is modified, you need to reassess both the modification classification and the variable consideration estimate as of the modification date. The modification might change the range of possible outcomes, affect the constraint analysis, or change which estimation method is most predictive. A performance bonus that was just above the constraint threshold under the original contract may fall below it after a scope change reduces the probability of hitting the target. The re-estimation required by the modification and the re-estimation required at each reporting period under ASC 606-10-32-14 are separate processes. Both need to happen at modification, and then the periodic re-estimation requirement continues from that point forward under the modified terms.
The bottom line: Contract modification accounting isn’t complicated in principle — three scenarios, two threshold questions.
What’s difficult is making and documenting the classification judgment at the time of modification, before the revenue implications are obvious. Build the modification assessment into your contract change management process, not as an afterthought in close. The catch-up adjustment that surprises a CFO in Q3 is almost always from a modification that was misclassified — or never classified at all — in Q1.
Frequently Asked Questions
What is a contract modification under ASC 606?
A contract modification is any change in the scope or price of a contract that is approved by both parties. Approval doesn’t require a formal amendment, or an oral agreement; email confirmation, or implied acceptance of changed terms can constitute a modification under ASC 606-10-25-10. The modification triggers a classification assessment that determines whether it’s accounted for as a new contract, a termination and replacement, or an adjustment to the existing contract.
What are the three accounting scenarios for contract modifications?
- Scenario 1: The modification adds distinct goods or services at standalone selling price — account for it as a new contract (prospective).
- Scenario 2: The modification adds distinct goods or services but not at SSP, terminate the original contract and create a new one with reallocated transaction price (prospective).
- Scenario 3: The modification doesn’t add distinct goods or services — treat it as part of the original contract and recognize a cumulative catch-up adjustment in the current period.
When does a contract modification require a cumulative catch-up adjustment?
Scenario 3 (see above).
Where the modification changes the existing contract rather than adding distinct new obligations, requires a cumulative catch-up. The transaction price is recalculated as of the modification date, reallocated across remaining performance obligations, and a true-up is recognized immediately. This includes most price-only modifications (discounts, concessions, repricings) and scope changes where the new work is not separable from what has already transferred.
How do you determine whether modified goods or services are “distinct”?
The distinctness test under ASC 606-10-25-19 has two prongs: (1) the customer can benefit from the good or service on its own or with other readily available resources, and (2) the entity’s promise to deliver it is separately identifiable from the other contract promises. In SaaS, adding user seats to an existing license is typically distinct. Adding a deeply integrated module to an in-flight implementation often is not. Document the assessment at the time of modification.
Can a verbal agreement constitute a contract modification under ASC 606?
Yes. ASC 606-10-25-10 defines a modification as a change in scope or price approved by the parties, without requiring written form. Oral agreements qualify if they create enforceable rights and obligations (ASC 606-10-25-11(a)). Emails showing clear acceptance also qualify. This creates a practical risk for companies that make informal pricing concessions or scope adjustments without formal documentation , those changes may already be modifications that require accounting treatment, whether a written amendment was executed.
For the full revenue recognition framework, see our Enterprise Revenue Recognition Guide. For a practitioner’s look at where contract modification accounting breaks down in practice, check out the Contract Modifications in Practice: Where the Accounting Breaks Down on Rev-Venue.
