Subscriptions rarely stay the same for a full term. Customers add seats in month four, move to a higher plan in month seven, renew early to lock a price, or ask to downgrade. Each of these is a contract modification under ASC 606, and the accounting depends on what changed and at what price.
The three paths
ASC 606 gives three ways to account for a modification:
| Situation | Accounting |
|---|---|
| Adds distinct goods or services at a price reflecting their standalone selling price | Treat as a separate contract; the original contract is unchanged |
| Remaining services are distinct from those already delivered (but the price does not reflect SSP) | Treat as termination of the old contract and creation of a new one: remaining consideration is recognized over the remaining services |
| Remaining services are not distinct | Cumulative catch-up adjustment to revenue recognized to date |
Most SaaS subscriptions deliver a series of distinct monthly service periods, so the second path (prospective treatment) is common for upgrades and downgrades, while seat add-ons at list price follow the first.
Worked examples
Seat add-on at list price. A customer on a $120,000 annual contract adds 20 seats in month four at the same per-seat price, prorated for the remaining nine months: $18,000. Treat it as a separate contract and recognize $2,000 a month for nine months alongside the original $10,000 a month.
Upgrade with a discount. In month seven the customer moves to a higher plan worth $180,000 a year, with the incremental price discounted below standalone value as a retention incentive. Account for it prospectively: take the unrecognized consideration from the original contract plus the new consideration and recognize the total ratably over the remaining term.
Downgrade. The customer reduces seats at renewal. That is simply a new, smaller contract. A mid-term downgrade with no refund is recognized prospectively; a refund for unused service reduces revenue or deferred revenue.
Early renewal. A customer signs a new two-year term six months before the current term ends, at a new price. The existing term continues; the new term's consideration is recognized when that service begins, unless the new terms change the remaining months of the current term, in which case those months are adjusted prospectively.
Why billing proration is not the GAAP answer
Billing systems prorate to calculate what to invoice. GAAP asks a different question: how much consideration relates to the remaining performance obligations, and when are they satisfied? The invoice amount and the revenue pattern often match for simple seat adds, and often do not for discounted upgrades and multi-element changes.
Making it repeatable
- Write a modification policy with examples of your common change types.
- Record modifications as amendments linked to the original contract in the billing system.
- Have the revenue schedule pick up the modification date and recalculate remaining recognition.
- Flag modifications with non-standard discounts for review at close.
ARR treatment
In the ARR bridge, upgrades and add-ons are expansion; downgrades are contraction. Early renewals with a price increase add expansion when the new price takes effect, not when the contract is signed.
Sources
Questions founders ask
Is a mid-term seat add-on a new contract?
It is accounted for as a separate contract when it adds distinct services at a price that reflects their standalone selling price. Otherwise it is treated as a modification of the existing contract.
How is a downgrade handled?
Usually prospectively: the remaining consideration is recognized over the remaining service period. A refund or credit for past service is accounted for as a reduction of revenue.
