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: Revenue cut-off errors happen when revenue lands in the wrong period: invoices dated in one period for service in another, renewals billed early, contracts not signed by period end, usage delivered but not billed, and credit notes raised after the close for problems that existed before it. Auditors test cut-off by matching revenue around the period end to contracts, service dates and later credits.
In a SaaS business, the invoice date is a poor guide to the period, because billing runs ahead of or behind the service. A cut-off review that starts from service dates and contract status, rather than invoice dates, can catch these errors before the audit does. This article walks through the five common errors and ends with a cut-off checklist.
Revenue cut-off is the test that revenue is recorded in the period in which it was earned, no earlier and no later. Under ASC 606 and IFRS 15, revenue is recognized as the business transfers the promised service to the customer, so for a subscription the period is set by when access is provided, not when the invoice is raised or the cash arrives.
That makes cut-off in SaaS mainly a balance-sheet question. Revenue billed ahead of service belongs in deferred revenue; revenue earned ahead of billing belongs in accrued revenue. When either balance is wrong at the period end, revenue is wrong by the same amount. That is why auditors pay attention to the deferred revenue roll-forward and to transactions in the days either side of the year-end.
A common cut-off error is an invoice whose date and service period fall in different periods, posted straight to revenue. Common examples:
The test is to sort invoices around the period end by service period, not by date, and check that each one sits in deferred revenue, revenue or accrued revenue according to the service delivered by the period end.
An early renewal moves billing earlier but does not move revenue. A customer whose term ends on January 31 may sign a renewal and be invoiced in December. The renewal term starts on February 1, so the renewal invoice belongs entirely in deferred revenue at December 31.
Three variations cause errors:
Revenue depends on a contract existing. Under both standards, the first step is to identify a contract with the customer, and a contract counts for revenue purposes only when it is approved by both parties and creates enforceable rights and obligations. A deal marked closed-won in the CRM, but not signed by the customer by the period end, may not meet that test.
Points to check at the period end:
Where a contract was not enforceable at the period end, the usual result is that revenue for service already provided waits until the contract exists, and amounts received are held as a liability. The details depend on the facts; agree them with your auditors. The ASC 606 audit checklist for SaaS CFOs covers contract documentation in more depth.
Usage-based fees earned before the period end are revenue in that period, even when the invoice follows weeks later. Overage charges, transaction fees and seat true-ups billed in arrears are the usual sources.
Usage fees often include variable amounts. Where the final amount is uncertain at the period end, the estimate should reflect the amount the business expects to be entitled to, which the IFRS 15 standard describes as estimating variable consideration.
A credit note raised in January can still belong to December. If it corrects a billing error, settles a dispute about December service or compensates for a service failure that occurred in December, the condition existed at the period end and the closed period may need adjusting.
The review covers credit notes raised between the period end and the date the accounts are finalized:
Auditors commonly select post-period-end credit notes for testing for this reason.
The table below summarizes the tests for each area, the evidence to keep and the usual adjustment.
| Area | Test | Evidence | Usual adjustment |
|---|---|---|---|
| Invoices around period end | Compare invoice date with service period | Invoice lines with service dates | Move to deferred or accrued revenue |
| Annual invoices | Confirm coding to deferred revenue | Deferred revenue schedule | Reclassify from revenue |
| Early renewals | Check schedule starts at new term | Renewal order form | Defer renewal fee in full |
| Contracts | Confirm signed and approved by period end | Signed order forms, CRM close dates | Defer revenue until enforceable |
| Usage | Measure usage to the last day | Usage report at period end | Accrue unbilled revenue |
| Credit notes | Review credits after period end | Credit notes with reasons | Adjust the closed period |
| Balances | Reconcile deferred revenue roll-forward | Opening, movements, closing | Investigate unexplained differences |
Source: ScaleXP summary of common SaaS revenue cut-off tests; not an audit standard.
Keep the evidence with the close file. The article on what auditors accept as a close audit trail describes what reviewers look for, and our guide to deferred revenue reconciliation covers the roll-forward.
ScaleXP builds ASC 606 and IFRS 15 revenue schedules from existing invoices in Xero or QuickBooks Online and from deals in HubSpot, Salesforce or Pipedrive. Revenue is spread across the service months rather than booked on the invoice date, and deferred revenue schedules roll forward monthly with opening, movement and closing balances.
ScaleXP prepares the revenue journals, and they are posted once finance approves them. Credit notes, renewals, amendments and unusual terms are flagged for review, which brings several of the cut-off areas above to finance before the close. Contract existence and post-period-end judgments stay with finance and your auditors. See the revenue recognition automation page for the workflow.
SaaS revenue cut-off errors come from five places: invoices whose dates and service periods differ, early renewals, contracts not enforceable at period end, unbilled usage and credit notes raised after the close. Each is found by starting from service dates and contract status rather than invoice dates. Run the checklist before each year-end and quarter-end, and keep the evidence with the close file.
Revenue cut-off is the audit test that revenue is recorded in the period it was earned. For SaaS, auditors match invoices, contracts and credit notes around the period end to service dates, and check that amounts billed in advance sit in deferred revenue and amounts earned but not billed sit in accrued revenue. Errors in either balance misstate revenue by the same amount.
No, not if the renewal term starts after the year-end. The renewal fee relates to service in the new term, so the full invoice sits in deferred revenue at the year-end and is recognized over the new term. Only an upgrade delivered from the signature date could put part of the renewal into the current period, which needs separate review.
Usually not for that period. Revenue requires a contract that is approved and enforceable, so service provided before the signature generally waits until the contract exists. Amounts already received are held as a liability. The answer depends on the facts, including whether an earlier written agreement was enforceable, so document the position and agree it with your auditors.
They can. If the credit note corrects an error or resolves a problem that existed before the year-end, such as a billing mistake or a service failure in December, the prior year may need adjusting. If it reflects a new event after the year-end, such as a goodwill gesture for a later issue, it belongs in the new period.
Usage delivered before the period end is revenue in that period, even if the invoice is raised afterwards. Measure usage to the last day of the period, record the unbilled amount as accrued revenue and reverse the accrual when the invoice is issued. Where the final amount is uncertain, estimate the amount you expect to be entitled to.
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.