How do I account for a mid-contract downgrade or seat reduction under ASC 606?

Why a downgrade isn't just the upgrade logic run backward

ASC 606-10-25-13's first branch — treat the modification as a separate contract — only applies when the change adds distinct goods or services priced at their standalone selling price. A downgrade or seat reduction doesn't add anything; it removes scope. That branch of the framework is never in play for a pure reduction, which is the main way this differs from the upgrade case: an upgrade has to clear the "is the new price at SSP" test before anything else, but a downgrade skips straight to the question of whether the remaining goods or services are distinct from what's already been delivered.

Why SaaS subscriptions usually land on prospective treatment

A SaaS subscription is typically accounted for as a series of distinct time increments (each day or month of access is its own distinct service, satisfied over time) rather than one indivisible obligation. That series treatment is what makes the remaining, not-yet-delivered days of service distinct from the days already delivered before the modification — which is exactly the condition ASC 606-10-25-13(a) requires for prospective accounting: treat it as if the original contract terminated at the modification date and a new one began, covering only the remaining term at the new, reduced consideration.

When a downgrade gets cumulative catch-up instead

The prospective outcome isn't automatic for every downgrade — it follows from the remaining goods or services being distinct from what's already been delivered. A single, non-series obligation partway through delivery — a custom implementation project that's 60% complete when the customer descopes part of the remaining work — doesn't have that same distinct-increment structure. There, the remaining work isn't cleanly separable from work already performed, so the modification is instead treated as part of the original contract: recalculate the total transaction price and performance-completion percentage, and record the difference as an immediate cumulative catch-up adjustment in the current period, the same mechanism used for other non-distinct modifications.

What changes operationally, not just on the schedule

Prospective treatment means revenue already recognized before the modification date doesn't get restated — the reduced consideration only affects recognition from the modification date forward. That's a meaningfully different operational trigger than cumulative catch-up, which requires an immediate one-time adjustment the moment the modification is approved. Getting the distinct-vs-not-distinct call wrong doesn't just misstate the schedule going forward; it also means either a catch-up adjustment that shouldn't have happened, or a missing one that should have.