See how ScaleXP works with Xero or QuickBooks.
In a 15- or 30-minute demo, we’ll show the relevant workflows using example data and discuss how they could apply to your finance process. Complex requirements? Discuss them with us first.
Key takeaways
Short answer: In a non-cancelable multi-year SaaS contract with fixed annual price uplifts, the uplifts are part of a fixed transaction price, so revenue is usually recognized evenly across the term while billing steps up each year. The gap between what you bill and what you recognize sits on the balance sheet as a contract asset or deferred revenue. CPI-style escalators are different: they are variable, and the increase is usually recognized in the year it relates to.
This matters for SaaS finance teams because a three-year deal with a 5% annual uplift can produce revenue that does not match the invoices. If the ledger simply follows billing, revenue is understated in year one and overstated in year three, and the difference becomes an audit finding rather than a timing note.
An annual uplift is a contractual increase in the subscription fee at each anniversary of a multi-year agreement. SaaS contracts usually express it in one of two ways, and the accounting differs between them.
The accounting depends on whether the future amounts are fixed or variable, and on how long the contract is actually enforceable.
Under ASC 606, the transaction price is the consideration a company expects to be entitled to for the goods and services it has promised, over the enforceable term of the contract. A fixed uplift is not a future pricing decision. It is part of the price agreed at signing.
For a three-year, non-cancelable subscription, the transaction price is therefore the sum of all three years of fees. That total is then recognized as the performance obligation is satisfied. For a SaaS platform provided on the same terms each year, the obligation is typically satisfied over time, on a straight-line basis, because the customer receives the same service in each period.
The result is that the revenue pattern no longer follows the invoice pattern. Revenue is flat; billing rises. Our guide to ASC 606 revenue recognition in SaaS companies covers the five steps that sit behind this conclusion.
Illustrative example: a customer signs a three-year, non-cancelable subscription starting January 1, 2026. The fee is $100,000 for 2026, $105,000 for 2027 and $110,250 for 2028, invoiced annually in advance. Total fixed consideration is $315,250, so straight-line revenue is $105,083 a year (rounded).
The table below compares billing with revenue and shows the year-end contract balance that results.
| Year | Invoiced | Revenue recognized | Difference in year | Year-end contract asset |
|---|---|---|---|---|
| 2026 | $100,000 | $105,083 | $5,083 | $5,083 |
| 2027 | $105,000 | $105,083 | $83 | $5,166 |
| 2028 | $110,250 | $105,084 | ($5,166) | $0 |
| Total | $315,250 | $315,250 | $0 |
Source: illustrative figures prepared for this article; not customer data.
By the end of 2026 the company has recognized more revenue than it has billed, so it carries a contract asset of $5,083. In 2028 the higher invoice exceeds the year's revenue and the asset unwinds to zero. Over the full term, revenue and billing match.
Annual billing in advance adds a second layer. On January 1 each year the invoice creates a receivable and a contract liability, usually recorded as deferred revenue. Revenue is then released from that balance month by month.
In the example above, the 2026 invoice of $100,000 is fully released by mid-December, because monthly revenue is $8,757. From that point the company is recognizing revenue it has not yet billed, and the position flips from deferred revenue to a contract asset. Both balances relate to the same contract, so they are presented net for that contract rather than shown gross.
Two practical points follow for the close:
For the journal mechanics on the liability side, see the guide on how to record deferred revenue.
An escalator tied to an index is not known at signing, so it is variable consideration. A company must estimate variable consideration and include it in the transaction price only to the extent that a significant reversal of revenue is not expected when the uncertainty resolves.
For SaaS subscriptions, many companies reach a simpler outcome. A subscription is often accounted for as a series of distinct service periods. When the variable amount relates specifically to one period, such as the year a CPI increase applies to, the standards allow that amount to be allocated entirely to that period. In practice, the CPI increase is then recognized in the year it is billed, while any fixed portion of the price follows the straight-line pattern.
Illustrative example: a three-year contract at $100,000 a year plus a CPI adjustment from year two. If the 2027 adjustment is $3,000, that $3,000 is typically recognized across 2027 only, and the fixed $300,000 continues to be recognized at $100,000 a year. This conclusion depends on the contract terms, so document the reasoning and agree it with your auditors.
The straight-line answer assumes the customer is committed for the full term. If the customer can cancel at each anniversary without a substantive penalty, the enforceable contract may only be one year long, and each renewal is treated as a new contract.
That changes the schedule. With a one-year enforceable term, the 2026 fee of $100,000 is recognized in 2026, and the 2027 uplift belongs to the 2027 contract. No contract asset builds up, because there is no committed future consideration to spread.
Questions to ask about a contract before choosing the pattern:
IFRS 15 follows the same five-step model, so the conclusions above generally apply under both standards. The IFRS Foundation describes the core steps as identifying the contract and its performance obligations, determining the transaction price, allocating it, and recognizing revenue as each obligation is satisfied. It also requires that where consideration "includes a variable amount, an entity must estimate the amount of consideration" it expects to be entitled to.
The terms differ slightly. IFRS 15 refers to a contract liability where US practice often still says deferred revenue, and companies reporting under both frameworks should use consistent labels in their schedules. For a fuller comparison, see the guide to IFRS 15 revenue recognition in SaaS companies.
Under both standards, if billing and revenue diverge for well over a year, assess whether the contract contains a significant financing component and document the conclusion.
ScaleXP builds revenue schedules and journals from your invoice data in Xero or QuickBooks, using contract details from HubSpot, Salesforce or Pipedrive where they are connected. Finance sets the recognition policy for each contract type. ScaleXP prepares the revenue and deferred revenue journals, and they are posted once finance approves them.
The ScaleXP help centre walks through the setup, including a three-year contract with annual uplifts, in revenue recognition for multi-year contracts, free periods and extensions.
That keeps the billing record and the revenue record separate, which is the starting point for any uplift contract. To see how schedules and journals are built, review the revenue recognition automation for Xero and QuickBooks page and the deferred revenue schedules page.
Fixed annual uplifts in a committed multi-year contract are part of one transaction price, which is usually recognized evenly while billing rises each year. The difference is carried as a contract asset or deferred revenue and unwinds by the end of the term. Index-linked increases are variable and generally belong to the year they relate to. Check the enforceable term first, document the conclusion for each contract type, and keep billing and revenue schedules separate.
Fixed annual price increases in a non-cancelable multi-year contract are usually recognized evenly. The uplifts are part of the total transaction price, and a subscription delivered on the same terms each year is generally recognized on a straight-line basis. If the customer can cancel each year without a substantive penalty, each year is treated as its own contract and the price for that year is recognized in that year.
A contract asset arises because straight-line revenue exceeds the invoices raised in the early years. In a three-year contract billed at $100,000, $105,000 and $110,250, revenue is about $105,083 a year, so the company recognizes more than it bills in year one. The difference is a contract asset, which unwinds when the higher year-three invoice is raised.
Yes, an escalator tied to the Consumer Price Index or a similar index is variable consideration, because the amount is unknown at signing. For SaaS subscriptions treated as a series of distinct service periods, the increase can often be allocated to the period it relates to. The CPI uplift is then recognized in the year it applies, while the fixed fee follows its own pattern.
IFRS 15 and ASC 606 generally reach the same answer for multi-year contracts with uplifts, because both use the same five-step model. Fixed uplifts form part of the transaction price, and variable amounts must be estimated. Terminology differs slightly, with IFRS 15 using contract liability where US teams often say deferred revenue, so keep labels consistent across schedules.
No. ScaleXP prepares the revenue and deferred revenue journals from your invoice data, and they are posted once finance approves them. Finance decides the recognition policy for each contract type, including how multi-year uplift contracts are scheduled. ScaleXP works with Xero and QuickBooks, and can use contract data from HubSpot, Salesforce or Pipedrive.
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
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
Your 3–5 day Xero or QuickBooks close could be closer to 2.5 days
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
““Making the month-end revenue recognition process simplified.”
Revenue recognition
See how ScaleXP builds revenue schedules and journals from your invoice data.
In a 15- or 30-minute demo, we’ll show the relevant workflows using example data and discuss how they could apply to your finance process. Complex requirements? Discuss them with us first.