A contract modification can be a scope add, a price change, a term extension, or all three. ASC 606 covers all of them through one framework: two yes/no questions, three possible treatments. The treatment is determined by the modification's facts, not chosen by the controller. Each treatment produces a different recognition pattern, and the difference shows up in the modification-month revenue line.
The three treatments at a glance
ASC 606-10-25-10 through 25-13, summarized
The decision rule, in one tree
Two yes/no questions resolve every modification. The treatment is determined by the facts of the modification, not by the controller's preference, and the decision must be reproducible from the contract itself.
ASC 606 modification: two tests resolve every case
Three fact patterns, three treatments, three numbers
Same base contract, same modification month, yet three different month-13 revenue numbers depending purely on the facts.
The cumulative catch-up calculation
Treatment 3 is the only treatment that requires a cumulative catch-up entry. Under ASC 606-10-25-13(b), the modification is accounted for as part of the existing contract. The transaction price and the measure of progress are updated to reflect the modified terms, and the difference between revenue that should have been recognized to date and revenue actually recognized posts as a single entry in the modification period.
Formula: Catch-up = (Revised total transaction price × Measure of progress at modification date) − Revenue already recognized
Worked numbers for the Treatment 3 fact pattern above:
| # | Step | Value |
|---|---|---|
| 1 | Revised total transaction price ($12K recognized + $30K renegotiated) | $42K |
| 2 | Measure of progress (12 of 36 months) | 33.3% |
| 3 | Revenue that should have been recognized (33.3% × $42K) | $14K |
| 4 | Revenue already recognized to date | $12K |
| = | Cumulative catch-up entry posted in month 13 | +$2K |
After the catch-up, the remaining $28K amortizes over the 24 remaining months at $1.17K per month. Positive catch-ups inflate the modification period; negative catch-ups deflate it. Either way, the disclosure should explain the modification and the amount.
See it in motion
Cadel processing a modification and posting the correct treatment
Where the call goes wrong
The three common misclassifications, by treatment
What good looks like
A clean contract modification workflow runs the two tests at intake, classifies the treatment, computes the catch-up where applicable, and posts the correct journal entries with a full audit trail of which conditions were met. The treatment decision is no longer a memo someone writes the week before the auditor arrives; it's documented at the modification event with the supporting evidence attached.
The downstream effects show up in the revenue reconciliation rollforward: when a modification isn't classified correctly at intake, the rollforward stops regenerating from source and the next quarter's tie-out fails.
See how Cadel handles end-to-end revenue recognition under ASC 606, or get in touch to walk through one of your modifications in the two-test framework.