See how ScaleXP works with Xero or QuickBooks.
In a 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.
Deferred revenue represents the amount of money that has been received from customers for goods or services not yet delivered.
Deferred revenue is money a business receives in advance for products or services it has not yet delivered. It sits on the balance sheet as a liability until the work is done and the income is earned.
It is a core part of accrual accounting, which recognizes income when a company delivers value, not when it invoices or collects cash. Accountants also call the same balance unearned revenue, deferred income or revenue received in advance. The labels differ. The treatment does not.
The pattern is easiest to see in a subscription based business. If a SaaS company invoices $12,000 upfront for a 12-month subscription, none of it is income on day one. The full $12,000 goes to the balance sheet, and $1,000 is released to the income statement each month as the service is delivered. The ScaleXP deferred revenue software builds that release schedule from invoice data.
Once deferred revenue has been recorded, finance still needs a reliable schedule for recognizing it and preparing the related journals. See how ScaleXP supports revenue recognition automation.
These three terms get mixed up constantly, and only two of them describe the same thing.
| Term | What it means | Where it sits |
|---|---|---|
| Deferred revenue | Invoiced or paid, not yet delivered | Liability |
| Unearned revenue | Another name for the same balance | Liability |
| Accrued revenue | Delivered, not yet invoiced | Asset |
Accrued revenue is the mirror image. In one case the company receives in advance, in the other it delivers in advance. Confusing the two overstates income in one period and understates it in the next.
There is an expense-side equivalent too. When your own business pays for something ahead of consuming it, the cost is held as a prepayment and released over the period it covers. Same logic, opposite side of the profit and loss.
It appears on the balance sheet, not the income statement. The balance represents an obligation: customers have paid for products or services you still owe them.
Across the three financial statements it behaves like this:
Take a university that invoices students at the start of a three-month term. The fees covering future teaching are held as a liability, then released to income across the three months as the teaching happens.
Once earned, the amount moves off the balance sheet and onto the revenue line.
It is a liability. The company still owes the customer something.
Being paid does not make income earned. Cash in the bank changes the cash balance, not the revenue line. The deferred revenue liability only reduces as the company delivers and recognizes the matching revenue.
The journal entries track one thing: income moving from the balance sheet to the income statement as obligations are met. A single contract generates several.
Using the same $12,000 annual software contract:
When the invoice is issued:
| Account | Debit | Credit |
|---|---|---|
| Accounts Receivable | $12,000 | |
| Deferred Revenue | $12,000 |
Each month as $1,000 is earned:
| Account | Debit | Credit |
|---|---|---|
| Deferred Revenue | $1,000 | |
| Sales or Revenue | $1,000 |
Each monthly journal reduces the liability by $1,000 and recognizes the same amount as earned income.
Laid out across the contract year, the same $12,000 looks like this:
| Month | Recognized in the month | Recognized to date | Closing liability |
|---|---|---|---|
| At invoice | $0 | $0 | $12,000 |
| Month 1 | $1,000 | $1,000 | $11,000 |
| Month 3 | $1,000 | $3,000 | $9,000 |
| Month 6 | $1,000 | $6,000 | $6,000 |
| Month 9 | $1,000 | $9,000 | $3,000 |
| Month 12 | $1,000 | $12,000 | $0 |
Two things are worth noticing. The closing liability and the amount recognized to date always sum to the contract value, which is the check to run at every month end. And the balance only reaches zero once the last month of service has been delivered, not when the customer pays.
Evenly spread contracts are the simple case. Usage-based pricing, mid-term upgrades and contracts that start mid-month all break the straight line, and each one needs its own schedule.
At volume these schedules run to thousands of spreadsheet lines. ScaleXP automates the schedules and the journals, and there is a fuller walkthrough of recognition and reconciliation in Xero.
Yes, when the related products or services will be delivered within 12 months. It is a current liability, so it reduces net working capital.
If delivery runs beyond a year, split the balance and classify the later portion as a long-term liability. Multi-year contracts almost always need this split.
Rarely, and only briefly. It usually signals a refund or an adjustment part-way through a contract.
For example:
Reversing the three months already recognized, alongside the refund, can push the balance below zero until every entry is posted. Once the accounting is complete, no liability should remain for services the supplier no longer has to provide.
Yes. What creates the liability is the obligation, not the payment.
Invoice $12,000 upfront for a 12-month contract on 30-day terms and two things happen at once. A receivable is created, and the amount covering future service is deferred. The cash is recorded separately when it arrives.
So the balance represents invoiced amounts not yet earned. As delivery happens, the liability falls and revenue is recognized.
Both standards work the same way. Revenue is recognized when a performance obligation is satisfied, and everything invoiced ahead of that point is a contract liability. That is the accounting standards’ name for the same balance this article has been describing.
The five steps run in order:
Step 2 is where most SaaS contracts get expensive to unpick. Bundle a one-off implementation fee into an annual subscription and the two elements almost certainly earn out on different timelines: the implementation on delivery, the subscription across the year. Treating the bundle as a single line is the fastest way to a restatement.
For the detail on each standard, see IFRS 15 in SaaS companies and ASC 606 in SaaS companies, or our overview of revenue recognition for SaaS businesses.
One contract is a spreadsheet row. A few hundred contracts, each with its own start date, term and currency, is a reconciliation problem that compounds every month.
ScaleXP connects directly to Xero and QuickBooks. AI reads each invoice and extracts dates, terms, service periods, currencies and values, then builds the deferred revenue schedule and the monthly journals. Finance keeps review and approval control over everything before it posts.
That moves the whole workflow, from invoice to schedule to journal to report, onto connected financial data instead of spreadsheets, and takes days out of month end.
For a closer look at each accounting workflow, see our guides to deferred revenue in Xero and deferred revenue in QuickBooks.
Nothing. They are two names for the same liability, as are unearned revenue and revenue received in advance. UK reporting tends to favour deferred income. US reporting under ASC 606 tends to favour deferred revenue or contract liability.
As long as the obligation lasts. A monthly plan clears within weeks. A three-year licence stays partly deferred for three years, with the portion due after 12 months shown as a long-term liability.
Not directly, because the cash has usually already been collected. What it changes is the timing gap between cash and reported income, which is why a growing balance often sits alongside strong collections and modest recognized revenue.
ScaleXP connects to both and prepares the schedules and journals automatically. AI extracts invoice dates, terms, service periods, currencies and values, then finance reviews and approves before anything posts. See the Xero workflow or the QuickBooks workflow for a step-by-step view.
Under standard accounting principles, revenue is recognized when goods or services are delivered, not when the payment received lands in the bank. That is why customers who pay upfront create a liability rather than income: the cash has arrived, but the obligation has not yet been met.
For financial reporting this shows up in two places. The balance sheet carries the outstanding obligation, and the income statement recognizes the revenue only as the service period elapses. Reading the two together is the quickest way to spot a deferred revenue balance that has stopped unwinding correctly.
How ScaleXP does this
ScaleXP calculates deferred revenue from your invoices and contracts and keeps the balance sheet reconciled every month. See ScaleXP’s deferred revenue automation →
Totals at the end of December 2026. Revenue is $1,000 a month. Click any month to move through the schedule.
ScaleXP prepares the schedules and journals for every customer, invoice and invoice line item, and finance reviews and approves them before they’re posted to Xero or QuickBooks.
Book a demo →Invoiced in full at the start of the service period and recognized straight-line by whole month. Illustration only, not accounting advice.
““Making the month-end revenue recognition process simplified.”
Revenue recognition
See how ScaleXP builds revenue schedules and journals from your invoice data.
In a 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.