Contract Modifications

SaaS contracts change: customers upgrade, downgrade, add seats, remove products, extend terms, or renegotiate pricing. Each modification triggers an ASC 606 analysis: is this a new contract (prospective treatment), a modification of the existing contract (cumulative catch-up), or a combination? The answer depends on whether the modification adds distinct goods/services at their standalone selling price. This is the most common judgment call in subscription revenue recognition — and the most frequently audited.

Contract Modification Decision Tree:
──────────────────────────────────────────────────────
1. Does the modification add distinct goods/services?
   No  → Treat as modification of existing contract.
         Cumulative catch-up adjustment.
   Yes → Continue to Step 2.

2. Are the additional goods/services priced at SSP?
   Yes → Treat as a separate (new) contract.
         No adjustment to existing revenue.
   No  → Treat as termination of old contract
         + creation of new blended contract.
         Cumulative catch-up to reallocate.

Example: Customer adds 50 seats mid-year.
  Seats are distinct (Step 1: Yes).
  Priced at $100/seat/month (SSP = $100).
  Step 2: Yes → Separate contract.
  Existing recognition: unchanged.
  New seats: recognized ratably from mod date.

Example: Customer upgrades tier mid-year.
  Upgrade changes the service level, not a
  distinct new service (Step 1: No).
  Treat as modification → cumulative catch-up.
  Reallocate remaining consideration over
  remaining term at new rate.