If ASC 606 is the rule, the deferred revenue roll-forward is the proof. It is a one-page schedule that shows how the contract liability moved during the month, and it is the first thing an auditor, a diligence team or a sharp board member asks for when revenue looks too smooth or too lumpy.
The structure
| Line | What goes in it |
|---|---|
| Opening deferred revenue | Last month's closing balance, from the balance sheet |
| Plus: billings | Invoices issued in the period for future service |
| Less: revenue recognized | The portion of deferred revenue earned in the period |
| Plus or minus: adjustments | Credits, refunds, write-offs, contract modifications |
| Closing deferred revenue | Must equal the general ledger balance |
Build it by customer or by contract, not only in total. A total that ties can hide offsetting errors; a customer-level schedule cannot.
Where the numbers come from
- Billings come from the billing system (Stripe, Chargebee, Recurly, NetSuite billing or invoices issued in your accounting platform).
- Recognition comes from a revenue schedule: each contract's price spread across its service days or months.
- The GL balance comes from the balance sheet after the close.
The roll-forward is where those three systems are forced to agree.
The errors it catches
- Revenue booked at invoice. The most common SaaS error: an annual invoice credited straight to revenue. The roll-forward shows billings with no matching increase in deferred revenue.
- Missed start dates. A contract that starts mid-month recognized for the full month, or a renewal invoiced early and recognized early.
- Credits and refunds in the wrong place. A refund on an unexpired subscription reduces deferred revenue, not current revenue.
- Cancellations left on the schedule. A churned customer still amortizing revenue into future months.
- Multi-year deals booked in full. Billing three years upfront creates three years of deferred revenue, split between current and non-current on the balance sheet.
Current versus non-current
Deferred revenue expected to be recognized within twelve months is a current liability; the rest is non-current. Prepaid multi-year deals make this split material, and lenders look at it when they test working capital.
Tie-out routine at every close
- Pull billings for the period from the billing system and match the total to the AR and deferred revenue entries in the ledger.
- Run the revenue schedule and post recognition.
- Roll the balance by customer and compare closing deferred revenue to the GL.
- Investigate any customer whose remaining deferred balance does not match remaining contract value.
- Save the schedule with the close package so it can be handed to an auditor as-is.
What it tells the board
Deferred revenue growth is a leading indicator. When billings outpace recognition, you are selling more prepaid term; when the balance shrinks, renewals or prepayment terms are slipping. Paired with the ARR bridge, it explains whether growth is real and whether it is funded by customers or by the bank account.
We build the roll-forward at the customer level and run it as part of every monthly close, in whatever accounting software you already use.
Sources
Questions founders ask
Is deferred revenue a liability?
Yes. Under ASC 606 it is a contract liability: cash or a receivable recorded for service you still owe the customer.
Should deferred revenue include invoices that are not yet due?
Only if you have an unconditional right to payment, meaning the invoice has been issued and the service period has started or payment is due. Unbilled future years of a multi-year contract are disclosed as remaining performance obligations, not booked.
