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: At a fundraise, investors and their diligence teams check that the deferred revenue balance ties to the general ledger, to a customer-level schedule and to the contracts and invoices behind it. They also check that ARR, recognized revenue and billings reconcile to each other, and that the release pattern supports the revenue the company says it will recognize.
For a SaaS company that bills annually or quarterly in advance, deferred revenue is often the largest liability on the balance sheet. It is also one of the clearest pieces of evidence that customers have committed to future service. A balance that reconciles cleanly shortens diligence; a balance that needs explaining slows it down and raises questions about the rest of the numbers.
Deferred revenue is the amount customers have been billed, or have paid, for service the company has not yet delivered. Under ASC 606 in the US and IFRS 15 internationally, revenue is recognized as the promised service is transferred to the customer, so the unearned part of an invoice sits on the balance sheet as a liability until it is earned.
An investor reading the balance sheet looks at three things:
If the basics of recording the balance need a refresher, our guide on how to record deferred revenue walks through the journal entries.
Investors use deferred revenue as evidence that bookings are real and that future revenue is already contracted. That only holds if the balance is built from signed contracts and issued invoices, released on a consistent policy, and reconciled to the ledger.
Diligence teams are therefore less interested in the headline number than in how it was produced. A balance maintained in a spreadsheet that is adjusted by a top-side journal at quarter-end tells them that the revenue line may also need adjusting. A balance that rolls forward month by month, customer by customer, tells them the revenue line can be relied on. The same logic sits behind the wider list of what investors want to see at Series A, B and beyond.
ARR, recognized revenue and billings answer different questions, and confusing them generates diligence follow-up questions.
Illustrative example: a customer signs a 12-month contract worth $120,000, starting April 1, 2026, invoiced in full on that date. The table below shows how the same contract appears in each measure at June 30, 2026.
| Measure | What it shows | Value at June 30, 2026 |
|---|---|---|
| ARR | Annualized value of the contract in force | $120,000 |
| Billings (April to June) | Invoices raised in the quarter | $120,000 |
| Recognized revenue (April to June) | Three months of service delivered | $30,000 |
| Deferred revenue balance | Nine months of service still owed | $90,000 |
Source: illustrative figures prepared for this article, not outside data.
Investors expect the company to bridge these figures at total level: billings less revenue recognized equals the change in deferred revenue, and ARR should be explainable from the contracts that also drive the deferred revenue schedule.
The reconciliation a diligence team asks for first is the deferred revenue rollforward. For each month, it shows:
Illustrative example: an opening balance of $1,800,000, plus billings of $2,400,000, less revenue recognized of $2,100,000, gives a closing balance of $2,100,000. If the ledger shows a different figure, the difference has to be explained line by line.
The second reconciliation runs from the customer-level schedule to contracts. A diligence team will select a sample of customers and compare the schedule with the signed order form: contract value, start and end dates, billing frequency and any discounts or free months. Differences usually trace back to missing service dates on invoices, amendments that were not reflected in the schedule, or renewals billed before the new term starts. Our article on why deferred revenue reconciliation breaks covers these causes in more detail.
Most questions fall into a short list. Having a written answer to each one, with the supporting schedule, saves several rounds of follow-up.
An acquisition adds further questions, for example how deferred revenue is treated in working capital. Those are outside the scope of this article.
The following checklist covers the deferred revenue material that diligence teams most often request. Preparing it before the process starts keeps the timetable in the company's hands.
Much of this also belongs in the regular board pack. Our guide to what to include in a board pack at Series A, B and C shows where it fits.
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 or unusual terms are flagged for finance review.
In the ScaleXP demo company below, the MRR report shows the new, lost, upgraded, downgraded and reactivated MRR behind each month's movement, the same layers an ARR bridge uses.
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 figures drill down to the source invoices, which is the evidence a diligence team asks for. See how the deferred revenue schedules in ScaleXP are built.
Deferred revenue is one of the first balances a diligence team tests at a fundraise, because it links contracts, billings, cash and recognized revenue. A monthly rollforward that ties to the ledger, a customer-level schedule that ties to contracts, and a clear bridge between ARR, billings and revenue answer most of their questions before they are asked.
Yes. For SaaS companies that bill in advance, deferred revenue is often one of the largest balances, so diligence teams test it closely. They check that it ties to the general ledger, that a customer-level schedule supports it, and that a sample of customers matches the signed contracts. They also use it to understand billing terms and how much future revenue is already contracted.
ARR is the annualized value of recurring contracts in force at a date. Billings are the invoices raised in a period. Recognized revenue is the amount earned in the period as service is delivered, under ASC 606 or IFRS 15. The difference between billings and recognized revenue is the change in deferred revenue, which is why investors ask for a bridge between the three figures.
A deferred revenue rollforward is a monthly reconciliation of the balance. It starts with the opening balance, adds invoices raised for future service, subtracts revenue recognized, adjusts for credit notes and cancellations, and arrives at the closing balance. The closing figure should match the general ledger. Diligence teams usually ask for one covering at least the last two years.
The portion to be recognized within twelve months of the balance sheet date is presented as a current liability, and the remainder as non-current. Investors look at this split because a large non-current balance usually reflects multi-year prepayments. They will ask which customers prepaid, the contract terms, and whether those customers can cancel and claim a refund of the unearned amount.
Ideally, the monthly rollforward and customer-level schedule are maintained as part of the regular close, so nothing new has to be built when a raise begins. Where they do not exist, building and reconciling at least 24 months of history takes time, because each difference must be traced to invoices and contracts. Starting before the data room opens avoids doing that work under deadline.
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
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.