1. Blog
  2. Revenue recognition

How auditors test deferred revenue schedules: what to prepare

How auditors test deferred revenue: the rollforward, recalculation, contract inspection, cut-off and analytics, plus the evidence finance should prepare.

Key takeaways

  • Auditors start with a rollforward that ties opening deferred revenue, billings and revenue recognized to the closing balance in the ledger.
  • They recalculate the release for a sample of contracts, using service dates and the company's recognition policy.
  • Contract inspection checks that the schedule matches signed terms, including start dates, discounts and amendments.
  • Cut-off testing looks at invoices and credit notes around the year-end to confirm they sit in the right period.
  • Most findings come from missing service dates, unreflected amendments and manual adjustments without support.

Short answer: Auditors test deferred revenue by rolling the balance forward from the prior year, recalculating the release for a sample of contracts, inspecting the contracts and invoices behind those balances, testing cut-off around the year-end, and comparing the results with their own expectations. Finance teams that keep a customer-level schedule tied to the ledger each month, with the source documents indexed to it, usually get through this work with fewer questions.

The exact procedures depend on the audit firm, the risk assessment and the size of the balance. The approach described here is general, but it reflects the evidence most auditors ask SaaS and subscription companies to provide.

What auditors test and what to prepare

The table summarizes the main deferred revenue procedures and the evidence that supports each one. Each procedure is described in more detail below.

ProcedureWhat the auditor testsWhat to prepare
RollforwardOpening balance, billings and revenue recognized explain the closing balanceAnnual rollforward tied to the ledger, with each reconciling item explained
RecalculationThe release for sampled contracts follows the stated policyCustomer-level schedule with contract value, service dates, amount released and remaining balance
Contract inspectionThe schedule matches signed terms, amendments and invoicesContracts, amendments and invoices for the largest customers, indexed to the schedule
Cut-offInvoices and credit notes around the year-end sit in the right periodList of invoices and credit notes around the year-end, with service periods
Journal reviewManual entries to deferred revenue are supported and approvedList of manual journals to deferred revenue, with the reason and approver for each
AnalyticsMovements in the balance match changes in the businessA short explanation for each significant movement against the prior year

Why auditors focus on deferred revenue

Deferred revenue sits between billings and recognized revenue, so an error in the balance is usually an error in revenue as well. If a release is calculated over the wrong period, revenue for the year is overstated or understated by the same amount the liability is misstated.

Revenue is commonly treated as a higher-risk area in an audit, and for SaaS companies that bill in advance, deferred revenue is where most of the judgment and calculation sits. The work is guided by the company's policy under ASC 606 in the US or IFRS 15 internationally, so the first thing an auditor reads is the written revenue recognition policy. Our ASC 606 audit checklist for SaaS CFOs covers the policy side in more detail.

The rollforward: tying the schedule to the ledger

The rollforward is normally the first schedule an auditor requests, because it connects the prior-year audited balance to the current-year balance. It shows:

  1. Opening deferred revenue, agreed to last year's audited figure.
  2. Plus invoices raised for future service.
  3. Less revenue recognized in the year.
  4. Plus or minus credit notes, cancellations and other adjustments.
  5. Closing deferred revenue, agreed to the general ledger and the trial balance.

The auditor then agrees the closing balance to the customer-level schedule. If the schedule total and the ledger differ, the difference has to be explained before testing goes further. Reconciling items that are unexplained or labeled only as "adjustment" draw attention quickly. Our article on why deferred revenue reconciliation breaks covers how those differences arise.

Recalculating the release for a sample of contracts

Recalculation tests whether the schedule applies the policy correctly. The auditor selects a sample of contracts, takes the contract value and service period from the source documents, and recomputes the revenue that should have been recognized and the balance that should remain.

Illustrative example: a 12-month subscription worth $36,000 starts on March 1, 2026, invoiced in full on that date. On a straight-line monthly basis, $3,000 is recognized each month. At December 31, 2026, the auditor expects $30,000 recognized and $6,000 remaining in deferred revenue.

The table below shows what the auditor compares for that contract.

ItemAuditor's recalculationCompany scheduleDifference
Revenue recognized in 2026$30,000$30,000$0
Deferred revenue at December 31, 2026$6,000$6,000$0

Source: illustrative figures prepared for this article, not outside data.

Differences often come from the proration convention. A schedule that releases by day gives slightly different monthly figures from one that releases by whole month. Either can be acceptable if the policy states it and the schedule applies it consistently.

Inspecting contracts and invoices

Contract inspection checks that the schedule reflects the agreed terms. For each sampled item, the auditor typically compares the schedule with:

  • The signed order form or contract. Contract value, start and end dates, products and any free months or ramp pricing.
  • Amendments. Upgrades, downgrades, extensions and early terminations, and the date each took effect.
  • The invoice. Amount, date and the service period stated on the invoice.
  • Cash receipt. Where relevant, evidence that the customer paid, which supports the existence of the arrangement.

Auditors may also select items in the other direction: they start from a contract or invoice and check that it appears in the schedule. This tests completeness, the risk that some billings did not reach deferred revenue.

Testing cut-off around the year-end

Cut-off testing checks that billings, credit notes and revenue are recorded in the correct period. Auditors select invoices and credit notes raised in the days before and after the year-end and confirm the service period and posting date.

Typical cut-off issues in SaaS businesses include renewal invoices raised in December for a term starting in January, credit notes for cancellations issued after year-end that relate to the prior year, and invoices with no service dates that were recognized in full when raised.

Analytical procedures on deferred revenue

Analytical procedures compare the balance with an expectation the auditor builds independently. Common approaches include:

  • Comparing deferred revenue with the prior year and with billings, and asking about movements that do not match changes in the business.
  • Comparing monthly recognized revenue with the release implied by the opening balance and new billings.
  • Reviewing the balance by customer for unusual items, such as negative balances or balances on contracts that have ended.

Analytics rarely replace tests of detail on a material balance, but they direct the auditor's attention, and a clear explanation for each significant movement saves time.

Evidence finance should have ready

A prepared-by-client list for deferred revenue usually includes the following. Having it ready at the start of fieldwork is the most effective way to shorten the audit.

  • The written revenue recognition policy, including the proration convention.
  • The annual rollforward, tied to the ledger, with each reconciling item explained.
  • The customer-level schedule at year-end, with contract value, service dates, amount released and remaining balance.
  • Contracts, amendments and invoices for the largest customers, indexed to the schedule.
  • A list of manual journals posted to deferred revenue, with the reason and approver for each.
  • A list of invoices and credit notes around the year-end, with their service periods.

The approval trail matters as much as the numbers. Our article on what auditors accept as an audit trail explains what reviewers look for when journals are prepared by software.

Common audit findings on deferred revenue

The same findings appear repeatedly in deferred revenue testing. Most are process issues rather than policy disagreements.

  • Missing service dates. Invoices without a start and end date are recognized on the invoice date or by guesswork.
  • Amendments not reflected. An upgrade or early termination changes the contract, but the schedule keeps the original terms.
  • Unsupported manual adjustments. Top-side journals to deferred revenue with no link to a contract or invoice.
  • Schedule not tied to the ledger. The spreadsheet total and the ledger balance differ, and the difference has been carried forward.
  • Inconsistent proration. Some contracts released by day, others by month, with no stated policy.

How ScaleXP supports deferred revenue audit preparation

ScaleXP builds month-by-month deferred revenue schedules from invoices in Xero or QuickBooks, by customer, product and contract. Service dates can come from the invoice or from CRM data in HubSpot, Salesforce or Pipedrive, and schedules with missing dates, unusual billing terms or amendments are flagged for finance review. When an invoice changes, the schedule is recalculated.

In the ScaleXP demo company below, the deferred revenue journal shows for each month how invoiced revenue is deferred to the balance sheet, released as invoices reach their recognition months, and adjusted for accrued revenue.

ScaleXP deferred revenue calculation: invoiced, deferred, released, accrued and recognized revenue for three months

ScaleXP prepares the deferred revenue and recognized revenue journals, and they are posted once finance approves them. Opening, movement and closing balances reconcile to the journals in the ledger, and each figure drills down to its source invoice, which is the evidence auditors sample. Every journal includes a full audit trail, downloadable as a spreadsheet, and auditors can have read-only access. Read more about deferred revenue schedules and journals in ScaleXP.

Conclusion

Auditors test deferred revenue through a rollforward, recalculation, contract and invoice inspection, cut-off testing and analytics. Each procedure is easier to support when the customer-level schedule ties to the ledger every month, service dates come from the source documents, and every adjustment has a reason and an approver.

Frequently asked questions

What do auditors ask for when testing deferred revenue?

Auditors usually ask for the revenue recognition policy, an annual rollforward of deferred revenue tied to the ledger, and a customer-level schedule at year-end. They then request contracts, amendments and invoices for a sample of customers, plus invoices and credit notes around the year-end for cut-off testing. A list of manual journals to deferred revenue, with approvers, is also commonly requested.

What is a deferred revenue rollforward in an audit?

It is a reconciliation from the opening balance, agreed to the prior-year audited figure, to the closing balance in the ledger. It adds invoices for future service, subtracts revenue recognized and adjusts for credit notes and cancellations. Auditors use it to confirm that the movements in the year explain the change in the balance, before they test individual contracts.

How do auditors test deferred revenue cut-off?

They select invoices and credit notes recorded shortly before and after the year-end and check the service period, posting date and amount against the source documents. The aim is to confirm that revenue and deferred revenue are recorded in the correct period. Renewal invoices raised before a new term starts and late credit notes are common areas of focus.

Can deferred revenue be released by day or by month?

Both conventions are used in practice. Releasing by day spreads revenue in proportion to the days in each month, while releasing by month recognizes an equal amount each full month. The company's policy should state which convention applies, and the schedule should apply it consistently, because auditors recalculate sampled contracts using the stated method.

What are the most common deferred revenue audit adjustments?

Common adjustments relate to invoices without service dates, contract amendments that were not reflected in the schedule, and manual journals to deferred revenue without supporting documents. Differences between the schedule total and the ledger balance that were carried forward from earlier periods also lead to adjustments. Most of these are prevented by reconciling the schedule to the ledger every month.


Sources (checked October 2026): IFRS Foundation, IFRS 15 Revenue from Contracts with Customers.

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

Close-time estimator

How much of your month-end close could you automate?

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

≈ 1.5days back every month

Your 3–5 day Xero or QuickBooks close could be closer to 2.5 days

  • Prepared by ScaleXP
  • Finance review
  • Still manual
  • Accrualsnot selected
  • Prepaymentsnot selected
  • Deferred revenue≈ 1 day
  • Accrued revenue≈ 0.5 days
  • Consolidationnot selected
  • Intercompany consolidationnot selected

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