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: An annual SaaS plan billed monthly is recognized ratably over the twelve-month term, in the same way as an annual plan paid upfront. The monthly invoices decide when cash arrives and what sits on the balance sheet, not when revenue is earned.
ScaleXP builds these schedules from the invoices in Xero or QuickBooks, can spread revenue by day or by whole month, and prepares the journals, which post once finance approves.
For most annual plans billed monthly at a flat price, each month's invoice matches that month's revenue, so the schedule is simple and little or no deferred revenue builds up. The work lies in the exceptions: invoices issued before the service month starts, billing periods that do not match calendar months, discounted or ramped first months, and termination rights that shorten the contract the standards recognize.
The difference between the two plans is the length of the enforceable commitment, not the invoice frequency. On a monthly plan, the customer agrees to one month at a time and can stop at the end of any month. On an annual plan billed monthly, the customer commits to twelve months of service and agrees to pay for them in twelve installments.
That difference matters for three reasons:
Revenue is recognized ratably because a SaaS subscription is a service the customer receives continuously across the term. Under both ASC 606 and IFRS 15, revenue is recognized as the business transfers the promised service to the customer, and access to a platform is transferred over time rather than at a single point.
For a single subscription with no setup or services, the five-step model gives a straight line: the annual transaction price divided by twelve, recognized each month of the term. The billing schedule changes only the balance sheet: whether, at each month-end, the business has billed more than it has earned (deferred revenue) or earned more than it has billed (a contract asset, often called unbilled or accrued revenue). Our guide to deferred revenue versus accrued revenue covers the two balances in more detail.
An annual plan billed monthly creates no deferred revenue at month-end when three conditions hold together:
In that case, the invoice raised on January 1 for January service is fully earned by January 31, and the deferred revenue account carries no balance for that customer at month-end. Many finance teams on Xero or QuickBooks Online post these invoices directly to revenue, which is correct while the conditions hold.
The risk is that the conditions change quietly: a billing date moves to the 15th, or a sales rep gives two free months. The direct-to-revenue shortcut then misstates revenue, and the error surfaces only when someone reconciles deferred revenue. Our article on why deferred revenue reconciliations break describes how that tends to happen.
Deferred revenue or a contract asset appears whenever billing and service stop lining up within the month. The common cases are:
The first three follow the usual mechanics of recording deferred revenue. The fourth is the one most often missed.
Termination rights change the contract term because the standards look at the period in which both parties have enforceable rights and obligations, not at the label on the order form. A plan sold as "annual" is not necessarily a twelve-month contract for accounting purposes.
The questions to ask about the termination clause are:
If the enforceable term is shorter than twelve months, a discount or free period cannot be spread across months the customer has not committed to. Settle the term with your auditors first, then build the schedule. The ASC 606 guide for SaaS companies and the IFRS 15 guide for SaaS companies cover contract identification in more depth.
Illustrative example: a customer signs a non-cancellable annual plan running from January 1 to December 31, 2026. The first three months are billed at $1,500 a month as an introductory discount, and the remaining nine months at $2,500. The service is the same throughout. The transaction price is $27,000 ($4,500 plus $22,500), so revenue is $2,250 a month.
The table below shows billing, revenue and the contract asset balance at each month-end.
| Month (2026) | Invoiced | Revenue recognized | Contract asset at month-end |
|---|---|---|---|
| January | $1,500 | $2,250 | $750 |
| February | $1,500 | $2,250 | $1,500 |
| March | $1,500 | $2,250 | $2,250 |
| April | $2,500 | $2,250 | $2,000 |
| May | $2,500 | $2,250 | $1,750 |
| June | $2,500 | $2,250 | $1,500 |
| July | $2,500 | $2,250 | $1,250 |
| August | $2,500 | $2,250 | $1,000 |
| September | $2,500 | $2,250 | $750 |
| October | $2,500 | $2,250 | $500 |
| November | $2,500 | $2,250 | $250 |
| December | $2,500 | $2,250 | $0 |
| Total | $27,000 | $27,000 |
Source: illustrative figures prepared for this article; not customer data.
In January, finance records the $1,500 invoice and a further $750 of revenue against the contract asset. From April, the $250 excess billing each month reduces the contract asset until it reaches zero at the end of the term.
Two variations change the answer. If the customer could cancel without penalty after March, the discount could not be spread over the full year. If the price step reflected more seats, the steps might be separate promises priced on their own. Document both judgments before the first month closes.
ScaleXP builds revenue schedules from the invoices already in Xero or QuickBooks Online, using the service period on each invoice line. Where an invoice does not carry the contract dates, ScaleXP can read deal and contract data from HubSpot, Salesforce or Pipedrive.
From those schedules, ScaleXP prepares the deferred and recognized revenue journals each month, and they are posted once finance approves them. Credit notes, renewals, amendments and unusual terms are flagged for review, so a change to an annual plan is checked by finance rather than absorbed silently. The judgments in this article, such as the contract term and how to treat a ramp, stay with finance and your auditors. You can see the workflow on the revenue recognition automation page.
An annual plan billed monthly is recognized ratably over the contract term, exactly like an annual plan paid upfront. When the monthly fee is flat and each invoice covers the calendar month it is recorded in, revenue matches billing and no deferred revenue builds up. Discounts, ramps, advance invoices and offset billing periods break that match, and termination rights can shorten the term the schedule should run over. Decide the term, then let the schedule, not the invoice date, drive revenue.
No. Both are recognized ratably over the contract term, because the customer receives the same service in each month. The billing pattern only changes the balance sheet: an upfront annual invoice creates a large deferred revenue balance that unwinds monthly, while monthly invoices at a flat price usually leave little or no deferred revenue at month-end.
You need one whenever billing and service do not line up within the month. Flat fees invoiced for the calendar month they are recorded in can go straight to revenue. Invoices issued in advance, billing periods that cross month-ends, setup fees, free months and ramped pricing each need a schedule, so the revenue recognized each month reflects the service delivered.
Free months on a committed annual plan are usually treated as a discount on the whole contract. The total fees are spread evenly across the full term, so revenue is recognized in the free months even though nothing is billed. That creates a contract asset, which reduces as later invoices exceed monthly revenue. If the customer can cancel without penalty, the term may be shorter.
It can. If the customer can cancel at any time without a substantive penalty, the enforceable contract may only run month to month, whatever the order form says. A requirement to pay the remaining fees, or a meaningful termination charge, usually supports the full annual term. Review each clause and agree the treatment with your auditors before building schedules.
Many SaaS companies include annual plans billed monthly in ARR at their full annualized value, because the customer has committed to twelve months. ARR is a management metric, not a revenue figure under ASC 606 or IFRS 15, so define the rule once, apply it consistently and reconcile ARR movements to recognized revenue in the board pack.
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.