Every contract change creates an accounting decision. A customer renews with a tighter scope. Another adds a new service mid-year at a volume discount. A third downgrades features and takes a refund. In each case, your finance team has to answer the same question: is this a modification of the existing contract, or a new contract altogether?
Most companies answer inconsistently — the same type of change gets handled differently depending on who processes it or what they guessed last time. That inconsistency is a reliable source of audit findings and restatements. The goal of a modification policy is to make the decision repeatable.
The Two-Part Test: New Contract or Modification?
ASC 606 has a clear rule: a modification creates a separate new contract only if both conditions are true:
- The modification adds distinct goods or services that weren't in the original contract
- The price increase reflects the standalone selling price of those added goods or services
If either condition fails, it's a modification to the existing contract — not a new one. That triggers different accounting.
The second condition is where most teams go wrong. You can add a new, distinct service, but if you price it at anything less than what a customer would pay for it standalone — which happens constantly in renewals — it fails the test. The whole thing is still a modification.
Let's say you have a three-year software contract. In year two, the customer adds a data export feature. The standalone selling price for that feature is $50,000. The customer negotiates it into a broader renewal at a net increase of only $40,000. That's a modification — not a new contract — because the price doesn't reflect standalone selling price. The fact that the service is new and distinct doesn't change the conclusion.
The Three Accounting Treatments
Once you've confirmed it's a modification (not a new contract), the treatment depends on the nature of what changed.
Prospective — terminate and replace. If the remaining goods or services under the modified contract are distinct from what's already been delivered, the modification is accounted for as if the original contract were terminated and a new one created. You recalculate performance obligations using remaining deliverables and a blended transaction price. Prior-period revenue stays untouched; the adjustment flows forward.
Cumulative catch-up. If the modification changes goods or services that are not distinct from what's already been transferred — typically because it alters an in-progress obligation — you adjust revenue recognized in prior periods, with the catch-up recognized in the current period. This hits both the P&L and the balance sheet. It's the treatment teams most want to avoid, and therefore the one they misapply most often.
When portions of the modification fall into both categories. A single modification can affect both distinct remaining obligations and an in-progress non-distinct obligation. In that case, each portion is accounted for under the treatment that applies to it — prospective for the distinct piece, catch-up for the in-progress piece. This isn't a third treatment; it's the result of applying both treatments to their respective portions of the same change.
Getting the treatment wrong has real consequences. A cumulative catch-up applied as prospective means you're under-recognizing revenue in the wrong period. Prospective applied where catch-up is required leaves prior periods overstated. Neither surfaces cleanly until audit.
Where It Actually Falls Apart
Treating renewals as new contracts by default. Sales marks a three-year renewal as a "new deal." Finance doesn't run the two-part test. If the renewal adds services at a discount — which it usually does — it's a modification and needs to be accounted for as one. Skipping the test means no one catches it until an auditor does.
Using prospective treatment for everything. Prospective is simpler — no historical adjustments, no catch-ups. So teams apply it broadly, even when the facts require a cumulative catch-up. That distorts the current period and leaves prior periods misstated.
Making the call at quarter-end instead of when it happens. When an amendment comes in, finance files it and moves on. Three months later, at close, someone realizes it needs to be analyzed. The context is fuzzy, the information is scattered across email threads, and the deadline is tomorrow. Good judgment requires contemporaneous documentation — not a memo written after the fact that conveniently supports whatever treatment was already applied.
Confusing modifications with changes in variable consideration. A customer triggers a volume rebate mid-year. Is that a contract modification or a variable consideration adjustment? They're different problems with different accounting treatments, and teams mix them up regularly, especially when volume changes arrive alongside formal amendments. The analysis has to separate them.
The Fix: A Modification Policy and Real-Time Intake
You need two things: a written modification policy and a process that routes contract changes to finance the day they happen, not at quarter-end.
The policy should specify who makes the determination (finance owns the call, not sales or legal), what information is required (original contract terms, standalone selling prices for any new services, what performance obligations have already been satisfied), and which treatment applies under which conditions. Document decision trees. Make the logic repeatable.
The intake process is just as important. When a contract amendment comes in, finance shouldn't wait until close. A shared form, an email alias, a workflow — whatever fits your environment — that routes amendments to the right person the week they happen. That person documents their analysis while the context is fresh. The assessment takes an hour per modification, often less with practice.
A good place to start: pull your three messiest modifications from the last year — the ones that gave your auditor pause or where you second-guessed yourself. Walk back through the two-part test. Did you apply it at the time? Would you reach the same conclusion today? If the answer to either is no, you've found the gap. Close it with a documented decision tree before the next close cycle.
Frequently Asked Questions
When does a contract modification create a separate new contract?
Only when both conditions are satisfied simultaneously: the modification adds distinct goods or services, and the price increase equals the standalone selling price of those additions. If the pricing on the added services is anything less than SSP, the second condition fails and the whole change is a modification to the existing contract, not a new one.
What are the three accounting treatments for contract modifications?
Prospective (terminate and replace), where remaining obligations are distinct from what's already transferred. Cumulative catch-up, where the modification changes goods or services that are not distinct from what's already been delivered. And a combined approach when a single modification affects both distinct and non-distinct obligations, with each portion treated under its applicable method.
Why do teams misclassify Scenario 3 as prospective?
Prospective treatment is simpler and avoids a current-period catch-up. The misclassification usually comes from applying prospective treatment broadly without documenting the distinctness analysis. Auditors look for contemporaneous documentation of the classification decision. A memo written six months after the fact that supports the treatment already applied doesn't hold up.
Are renewals typically modifications or new contracts?
Usually modifications. Renewals frequently add services or adjust pricing at terms that don't equal SSP, which means the second condition for a separate new contract fails. The two-part test needs to be run on every renewal, even when sales marks it as a "new deal." Skipping the test is how misclassifications accumulate.
How do I separate a contract modification from a variable consideration adjustment?
Modifications are changes to contract terms agreed by the parties. Variable consideration adjustments are updates to estimates for amounts already defined in the existing contract. A volume discount that triggers a pricing tier already defined in the contract is variable consideration, not a modification. An agreed-upon price reduction outside the original terms is a modification. The original contract language controls the distinction.
