SaaS contracts change constantly. A customer upgrades mid-term. Another downgrades after a budget cut. A renewal comes in at a different price. Each of these is a contract modification under ASC 606 — and each one has a specific accounting treatment.
The wrong treatment means revenue in the wrong periods. The right treatment depends on answering two questions: does the modification add distinct goods or services, and are those additions priced at their stand-alone selling price?
Here's the framework from KPMG's handbook, applied to the modifications SaaS companies actually deal with.
Every contract modification falls into one of three accounting treatments. Which one applies depends on the specifics of the change.
The modification is treated as a brand new, independent contract — completely separate from the original deal. This applies when both conditions are met: (a) the modification adds distinct goods or services, AND (b) the price for those additions reflects their stand-alone selling price (adjusted for the circumstances of the contract).
Example: a customer on a $500/month plan adds a second product module at its normal $200/month price. The new module is distinct (customer can use it independently) and priced at SSP. Treat it as a separate contract. The original deal continues unchanged.
The modification is NOT a separate contract, but the remaining goods or services are distinct from what was already delivered. You effectively terminate the original contract and create a new one. Previously recognized revenue stays. The remaining consideration (unrecognized from the original contract plus any new consideration) gets allocated to the remaining obligations going forward.
This is the most common path for SaaS modifications. Why? Because SaaS is a series of distinct service periods — each month of access is distinct from the months already delivered. So when a SaaS contract is modified, the remaining services are almost always distinct from past services.
Example: customer on a $1,000/month annual SaaS plan upgrades to a $1,500/month plan after 6 months. You've recognized $6,000. Remaining consideration: $6,000 unrecognized + the $3,000 price increase for the remaining 6 months = $9,000 allocated across 6 remaining months = $1,500/month going forward.
The modification is NOT a separate contract, AND the remaining goods or services are NOT distinct from what was already delivered. You update the transaction price and measure of progress, then record a cumulative catch-up adjustment — recognizing the difference between what you've recorded so far and what you should have recorded under the revised terms.
This is rare for pure SaaS but common for software customization contracts where the modification changes an in-progress combined obligation.
If the added items are distinct and priced at SSP → separate contract. If priced at a discount → prospective treatment. The original contract's unrecognized revenue plus the new consideration gets spread across remaining periods.
A decrease in scope can never be a separate contract (nothing distinct is being added). If the remaining SaaS is distinct from past services — which it almost always is — treat prospectively. Reduce the transaction price, allocate the lower amount to remaining periods.
Customer negotiates a lower price mid-contract with no change in what you deliver. This follows the same framework as a scope decrease — it can't be a separate contract. For SaaS (remaining services are distinct from past), treat prospectively. New price applies to remaining periods.
If the renewal adds a new distinct period of SaaS at the renewal price, and that price reflects SSP, it's a separate contract. Straightforward. If the renewal price is significantly below SSP, evaluate whether the original contract contained a material right for the discounted renewal.
Customer terminates before the contract ends. If there's a termination penalty, that penalty is consideration under the modified contract. Treat as a scope decrease — prospectively allocate remaining consideration (including the penalty) to the shortened remaining period.
For every modification, ask these questions in order:
For SaaS companies, the vast majority of modifications land on prospective treatment because SaaS services are a series of distinct periods — the remaining months are always distinct from past months.
If your company routinely grants price concessions or allows mid-contract changes, those patterns can affect how you account for new contracts. A history of granting price reductions — even without formal modification — may indicate that future contracts have variable consideration from inception.
Similarly, a pattern of allowing customers to upgrade or downgrade freely suggests that those options might be implied rights in the original contract — potentially material rights that require separate accounting from day one.
Document your modification history. Auditors look at patterns, not just individual transactions.
Contract modifications require recalculating remaining consideration, reallocating to obligations, and adjusting revenue schedules — for every affected contract. At scale, this is impossible to do manually without errors.
JustPaid automatically detects contract changes, classifies the modification type, and updates revenue schedules accordingly. Upgrades, downgrades, price changes, early terminations — each follows the correct accounting path without manual intervention. The full modification history is maintained for audit documentation.
Dealing with frequent contract changes? Schedule a demo to see how JustPaid automates modification accounting.
Automate invoicing, streamline accounts receivable, and accelerate revenue with JustPaid.
Upgrades, downgrades, and renewals change your revenue recognition under ASC 606. Here's the framework for handling SaaS contract modifications correctly.
ASC 340-40 requires SaaS companies to capitalize sales commissions. Here is what to capitalize, what to expense, and the practical expedient traps.
Free trials, renewal discounts, and customer options create hidden revenue recognition traps under ASC 606. Here is what SaaS companies get wrong.
SaaS and software licenses follow completely different revenue recognition rules under ASC 606. Here's how the distinction works and why it matters for your financials.
Usage-based billing creates unique revenue recognition challenges under ASC 606 — variable consideration, royalty exceptions, and the as-invoiced expedient explained.
ASC 606 revenue recognition for SaaS companies — the 5-step model broken down with real examples. Learn when and how to recognize your revenue correctly.
Stay updated with the latest insights on AI-powered billing automation and financial operations.
Combinator (W23)
