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: When a SaaS customer cancels mid-term, revenue recognition stops when the service stops. The deferred revenue left on the balance sheet is then either reversed against the credit note and refund, or recognized as revenue if the customer forfeits it and the business owes nothing further.
The errors usually come from ledger mechanics: a credit note posted to revenue while the original invoice sits in deferred revenue, a refund agreed but not recorded at month-end, or a schedule still releasing revenue for a customer who has left. This guide walks through each case with illustrative journals.
At a glance, the journal entries for a mid-term cancellation with a full pro-rata refund. Illustrative figures: a $12,000 annual plan for 2026, invoiced on January 1 and terminated with effect from April 30, 2026.
| Date | Entry | Debit | Credit |
|---|---|---|---|
| January 1 | Annual invoice | Accounts receivable $12,000 | Deferred revenue $12,000 |
| Each month, January to April | Revenue release | Deferred revenue $1,000 | Revenue $1,000 |
| April 30 | Credit note for the unused eight months | Deferred revenue $8,000 | Accounts receivable $8,000 |
| On payment | Refund paid to the customer | Accounts receivable $8,000 | Cash $8,000 |
Before touching a schedule, establish which of three events has happened, because each has a different accounting result:
The contract, not the customer's email, decides which event it is. Check the termination clause, the refund policy and any concession agreed by sales.
A refund liability is the amount received from customers that the business expects to pay back. Under both ASC 606 and IFRS 15, revenue reflects the consideration the business expects to be entitled to, and the IFRS 15 standard describes estimating variable consideration as part of determining the transaction price. A right of refund is one form of that variability.
This matters for businesses with a money-back period on annual plans:
Illustrative example: a business invoices $120,000 of new annual plans in March 2026 with a 30-day refund right, and its own history supports an estimate that $6,000 will be refunded. It records $114,000 in deferred revenue and $6,000 as a refund liability. Revenue is recognized only from the $114,000 it expects to keep, and the estimate is trued up when the refund window closes.
A pro-rata refund returns the share of the fee that relates to the unused part of the term. The calculation should follow the same convention as the revenue schedule, so the refund and the remaining deferred revenue agree.
When the refund and the remaining deferred revenue do not agree, explain the difference. A refund larger than the balance returns fees for service already delivered, which reduces revenue.
A credit note for a canceled subscription should be posted to the same account the original invoice was posted to. In Xero and QuickBooks Online, the credit note's account code is chosen on each line, and the default is often the main revenue account. That default causes most cancellation errors.
Consider an annual invoice posted to deferred revenue on day one and released monthly by journal. If the credit note for the unused months is posted to revenue:
The fix is to code the credit note to deferred revenue for the unused portion and stop the schedule at the termination date. If invoices go straight to revenue and are deferred by journal at month-end, the credit note can go to revenue, but the deferral journal must drop the canceled contract. Our guide to deferred revenue reconciliation shows how to catch a mismatch before the close is signed off.
The remaining deferred revenue at the termination date goes one of three ways, depending on what the business owes the customer:
If the customer keeps access after giving notice, the balance keeps unwinding over the access period. A downgrade is a contract modification, not a cancellation. Our overview of revenue recognition methods covers how the schedule changes in each case.
Illustrative example: a customer pays $12,000 for an annual plan running from January 1 to December 31, 2026. The invoice is posted to deferred revenue and $1,000 is released to revenue each month. The customer terminates with effect from April 30, 2026, after four months of service. At that date, deferred revenue for the contract is $8,000.
The table below shows the journal for each of the three outcomes at April 30.
| Outcome | Debit | Credit | Revenue effect |
|---|---|---|---|
| Full pro-rata refund of $8,000 | Deferred revenue $8,000 | Accounts receivable $8,000 (credit note), then cash on payment | None |
| No refund, access ends | Deferred revenue $8,000 | Revenue $8,000 | +$8,000 in April |
| Refund $6,000, keep $2,000 termination fee | Deferred revenue $8,000 | Accounts receivable $6,000; revenue $2,000 | +$2,000 in April |
Source: illustrative figures prepared for this article; not customer data.
In each case, January to April revenue stays at $4,000, and the schedule closes from May. The steps for the original deferral are in our guide on how to record deferred revenue.
Cancellations are easy to miss because the information often sits in a support ticket or CRM note, not the ledger. A short check at each close helps:
These steps fit into a wider SaaS month-end close checklist.
ScaleXP builds month-by-month deferred revenue schedules from invoice dates, service periods and contract terms, combining invoices from Xero or QuickBooks Online with deal and contract data from HubSpot, Salesforce or Pipedrive. ScaleXP imports Xero credit notes, and when an invoice is changed or credited, the affected schedule is recalculated rather than rebuilt by hand.
ScaleXP prepares the deferred and recognized revenue journals, and they are posted once finance approves them, so finance reviews a cancellation before it reaches the ledger. Judgments such as refund liability estimates and whether retained fees are earned stay with finance. See the deferred revenue automation page for the workflow.
A SaaS cancellation unwinds cleanly when three things line up: the schedule stops when the service stops, the credit note hits the account the invoice was posted to, and the remaining deferred revenue is either reversed against the refund or recognized once the business owes nothing more. Expected refunds belong in a refund liability, not in revenue. A short cancellation check at each close keeps each one in the right period.
A refund for service already delivered reduces revenue in the period the refund is agreed, because the business is giving back consideration it had earned. A refund for the unused part of the term is different: it is charged against the remaining deferred revenue, and revenue already recognized is unchanged. Pro-rata refunds usually fall into the second case.
It depends on what the business owes. If the unused fees are refunded, the deferred revenue is reversed against the credit note. If the customer forfeits them and the business has no further obligation, the balance is generally recognized as revenue. If the customer keeps access until the end of the term, the balance continues to unwind on the original schedule.
It should go to the account the original invoice was posted to. If the annual invoice was posted to deferred revenue, code the credit note for the unused months to deferred revenue. Coding it to revenue reduces revenue that was not yet recognized and leaves the deferred revenue balance overstated until someone reconciles it.
A refund liability is consideration received or receivable that the business expects to return to the customer. It is held as a liability rather than revenue or deferred revenue. SaaS businesses with a money-back period on annual plans estimate it from their own refund history, review it each period and adjust it when the refund window closes.
No. A downgrade is a contract modification: the customer keeps a smaller service, so the business still has an obligation. The remaining price is usually spread over the remaining service period. A cancellation ends the obligation, so the schedule stops and the remaining deferred revenue is reversed, refunded or recognized, depending on the contract terms.
Sources (checked October 2026): IFRS Foundation, IFRS 15 Revenue from Contracts with Customers.
More revenue recognition scenarios
For how revenue schedules are built and updated when contracts change, see revenue recognition in ScaleXP.
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.