1. Blog
  2. Revenue recognition

ASC 606 contract modifications: SaaS upgrades and downgrades

How ASC 606 treats SaaS upgrades, downgrades and add-ons: separate contract, prospective or cumulative catch-up, with illustrative revenue schedules.

Key takeaways

  • A contract modification is any approved change to the scope or price of a contract, including upgrades, downgrades, add-ons and term extensions.
  • An add-on of distinct services priced at its stand-alone selling price is accounted for as a separate contract.
  • Most SaaS tier upgrades and downgrades are accounted for prospectively, with the remaining consideration spread over the remaining service.
  • A cumulative catch-up applies when the added work is part of a single obligation that is already partly delivered, such as an implementation project.
  • Recording the modification date, the new price and the stand-alone selling price evidence is what makes the treatment auditable.

Short answer: Under ASC 606, a mid-term SaaS upgrade, downgrade or add-on is a contract modification, and it is accounted for in one of three ways: as a separate contract, prospectively as if the old contract ended and a new one began, or with a cumulative catch-up adjustment. Most subscription changes fall into the first two, because each month of service is distinct from the months already delivered.

The choice changes the monthly revenue figure, the deferred revenue balance and the audit file. Finance teams at SaaS companies on Xero or QuickBooks Online meet these changes every month, often as a new quote in the CRM and a credit note or extra invoice in the ledger, so a consistent policy saves rework at the close.

At a glance, the journal entries for a mid-term upgrade. Illustrative figures: a $120,000 annual subscription invoiced on January 1, 2026, upgraded on July 1, 2026 for an additional $36,000, treated prospectively.

DateEntryDebitCredit
January 1Annual invoiceAccounts receivable $120,000Deferred revenue $120,000
Each month, January to JuneRevenue releaseDeferred revenue $10,000Revenue $10,000
July 1Upgrade invoiceAccounts receivable $36,000Deferred revenue $36,000
Each month, July to DecemberRevenue release ($60,000 plus $36,000 over six months)Deferred revenue $16,000Revenue $16,000

What counts as a contract modification in SaaS

A contract modification is a change in the scope or price of a contract, or both, that the customer and the vendor approve. Approval can be written, oral or implied by customary business practice, but it must create enforceable rights and obligations.

In a SaaS business the common modifications are:

  • Upgrades. A move to a higher tier, more seats or higher usage limits during the term.
  • Add-ons. A new module or product bought alongside the existing subscription.
  • Downgrades. Fewer seats or a lower tier, usually with a credit or a reduced future price.
  • Term changes. An early renewal or extension, often with a revised price.

A renewal at the end of the term is usually a new contract, not a modification. The analysis below applies to changes made before the existing term ends. For the wider framework, see our guide to ASC 606 revenue recognition in SaaS companies.

The three treatments and how to choose between them

ASC 606 sets out a sequence of questions. The answers decide which treatment applies, and the same model applies under IFRS 15.

The table below summarizes the three outcomes.

TreatmentWhen it appliesEffect on revenueTypical SaaS example
Separate contractAdds distinct goods or services, priced at their stand-alone selling priceOriginal contract unchanged; new contract recognized on its ownNew module bought at list price
Prospective (terminate and replace)Remaining services are distinct from those already deliveredRemaining consideration spread over remaining serviceTier upgrade, seat reduction, discounted add-on
Cumulative catch-upRemaining services are part of a single obligation already partly deliveredRevenue to date adjusted in the modification periodChange in scope of a fixed-fee implementation

Source: summary prepared for this article from the ASC 606 and IFRS 15 modification model.

The first test is whether the change adds distinct services at a price that reflects their stand-alone selling price. If both conditions are met, the change is a separate contract. If not, the second test is whether the services still to be delivered are distinct from those already delivered. For a monthly subscription service they usually are, which leads to the prospective treatment.

When an add-on is a separate contract

An add-on is a separate contract when it adds a distinct product and the price reflects what the vendor charges for that product on its own. A list-price module bought mid-term by an existing customer is the clearest case.

Illustrative example: a customer on a $120,000 annual subscription from January 1, 2026 buys a reporting module on July 1, 2026 for $30,000 for the remaining six months, which is the vendor's normal price. The original contract continues at $10,000 a month. The module is recognized at $5,000 a month from July to December as its own contract.

A discount on the add-on does not automatically fail the test. Price adjustments that reflect the circumstances of the contract, such as lower selling costs for an existing customer, can still be consistent with the stand-alone selling price. A discount offered to win the deal usually is not. Keep the evidence for whichever view you take.

Upgrades: prospective treatment in practice

A tier upgrade replaces the existing service rather than adding to it, so it is usually not a separate contract. Because each remaining month of service is distinct from the months already delivered, the modification is accounted for as if the old contract ended and a new one started.

Under this treatment, the consideration not yet recognized from the original contract is added to the new consideration, and the total is recognized over the remaining service period.

Illustrative example: the same $120,000 annual subscription is upgraded to a higher tier on July 1, 2026, for an additional $36,000. At that date, $60,000 of the original price is unrecognized. The remaining consideration is $60,000 plus $36,000, or $96,000, recognized over six months.

PeriodMonthly revenueRevenue in period
January to June 2026$10,000$60,000
July to December 2026$16,000$96,000
Total$156,000

Source: illustrative figures prepared for this article; not customer data.

No revenue already recognized is restated. If the upgrade is invoiced on July 1, the new invoice adds $36,000 to deferred revenue, which is then released at the new monthly rate.

Downgrades and credits mid-term

A downgrade reduces the scope of the contract. Where the remaining months of service are distinct, it is also accounted for prospectively, and the reduced consideration is spread over the remaining term.

Illustrative example: on April 1, 2026, the customer on the $120,000 annual subscription reduces seats, and the vendor agrees to an $18,000 credit. At that date $90,000 is unrecognized. The remaining consideration is $90,000 less $18,000, or $72,000, recognized at $8,000 a month for nine months.

PeriodMonthly revenueRevenue in period
January to March 2026$10,000$30,000
April to December 2026$8,000$72,000
Total$102,000

Source: illustrative figures prepared for this article; not customer data.

If the year was invoiced in advance, the credit note reduces the receivable or creates a refund liability, and it reduces deferred revenue. The revenue recognized in January to March is not reversed. Our guide on how to record deferred revenue covers the entries.

Distinguish a downgrade from a price concession. A credit given for a service problem, with no change in scope, is usually variable consideration rather than a modification, and is assessed separately.

When a cumulative catch-up applies

A cumulative catch-up applies when the remaining work is not distinct from the work already done, because both form part of a single performance obligation that is partly satisfied. In SaaS this is rare for subscriptions but common for fixed-fee implementation or professional services projects measured over time.

Illustrative example: an implementation is priced at $40,000 and estimated at 400 hours. After 200 hours, $20,000 has been recognized. The customer then adds scope worth $12,000 and an estimated 100 hours. The new price is $52,000 and progress is 200 of 500 hours, or 40%. Revenue to date should be $20,800, so an $800 catch-up is recognized in the month of the modification, and the rest follows progress.

Records auditors expect for each modification

Auditors test modifications because they change revenue already scheduled. A consistent file for each change reduces queries at year-end:

  • Approval evidence. The signed order form or approved quote, with the effective date.
  • Treatment chosen. Separate contract, prospective or catch-up, with one line of reasoning.
  • Stand-alone selling price support. Price lists or recent sales data where the separate-contract test is used.
  • Revised schedule. The old and new revenue schedule, reconciled to deferred revenue.

The ASC 606 compliance audit checklist for SaaS covers the wider documentation set. Under IFRS 15 the evidence is the same; see the guide to IFRS 15 revenue recognition in SaaS companies.

How ScaleXP supports revenue schedules when contracts change

ScaleXP builds revenue schedules and journals from your invoice data in Xero or QuickBooks, and can use deal data from HubSpot, Salesforce or Pipedrive. When an upgrade or downgrade is invoiced or credited, finance reviews the resulting schedule against the treatment it has chosen. ScaleXP prepares the revenue and deferred revenue journals, and they are posted once finance approves them.

In the ScaleXP demo company below, a customer billed $5,000 a month adds a second invoice dated May 21, 2025, so its monthly recurring revenue moves to $8,000 from May.

ScaleXP MRR report: IT Client moves from $5,000 to $8,000 after a May 2025 invoice

See how schedules and journals are built on the revenue recognition automation page, and how CRM and ledger data connect on the CRM and accounting integration page.

Conclusion

A mid-term SaaS change is a contract modification under ASC 606 and IFRS 15. Distinct add-ons at stand-alone selling price are separate contracts, most upgrades and downgrades are accounted for prospectively, and a cumulative catch-up is reserved for single obligations that are partly delivered, such as implementation projects. Choose the treatment at the modification date, document it, and update the revenue schedule before the month closes.

Frequently asked questions

How do you account for a SaaS upgrade mid-contract under ASC 606?

A mid-contract SaaS tier upgrade is usually accounted for prospectively. The unrecognized consideration from the original contract is added to the new consideration, and the total is recognized over the remaining term. Revenue already recognized is not restated. If the upgrade adds a distinct product at its stand-alone selling price, it is accounted for as a separate contract instead.

Is a downgrade a contract modification?

Yes, a downgrade that reduces seats, tier or scope with the customer's and vendor's approval is a contract modification. Where the remaining months of service are distinct, it is accounted for prospectively: the reduced remaining consideration is spread over the remaining term. A credit for a service problem with no change in scope is usually variable consideration rather than a modification.

When is a contract modification treated as a separate contract?

A modification is a separate contract when two conditions are both met. It adds goods or services that are distinct, and the price increases by an amount that reflects their stand-alone selling price, allowing for appropriate adjustments. A new module bought mid-term at list price is the common SaaS example. The original contract then continues unchanged.

What is a cumulative catch-up adjustment?

A cumulative catch-up adjustment updates revenue to date in the period a modification occurs. It applies when the remaining work is part of a single performance obligation that is already partly satisfied, such as a fixed-fee implementation. The new transaction price and revised measure of progress are applied, and the difference from revenue already recognized is booked immediately.

Are contract modifications treated the same under IFRS 15?

Yes, IFRS 15 uses the same contract modification model as ASC 606: a separate contract, a prospective treatment, or a cumulative catch-up, chosen by the same tests. Companies reporting under both standards will usually reach the same conclusion for SaaS upgrades, downgrades and add-ons. The documentation auditors expect is also broadly the same.


Sources (checked October 2026): IFRS Foundation, IFRS 15 Revenue from Contracts with Customers.


More revenue recognition scenarios

How ScaleXP does this

ScaleXP builds revenue recognition schedules from your CRM contracts and prepares the journals for Xero or QuickBooks. Finance approves them before they’re posted. See how revenue recognition works in ScaleXP

Close-time estimator

How much of your month-end close could you automate?

Your accounting system

How long does your close take today? Working days, roughly

Which of these do you still do manually? Select all that apply

Which of these takes the most time? Pick one

Your estimate

≈ 1.5days back every month

Your 3–5 day Xero or QuickBooks close could be closer to 2.5 days

  • Prepared by ScaleXP
  • Finance review
  • Still manual
  • Accrualsnot selected
  • Prepaymentsnot selected
  • Deferred revenue≈ 1 day
  • Accrued revenue≈ 0.5 days
  • Consolidationnot selected
  • Intercompany consolidationnot selected

Deferred revenue is where you would feel it first. ScaleXP prepares the schedules and journals for each task you selected from your live Xero or QuickBooks data. What stays with your team is the review and the posting decision.

Cue Technology saves 3–5 finance-team days a month. Xero customer