Revenue reconciliation is not the same as billing reconciliation. The three numbers an auditor wants to tie — bookings, billings, recognized revenue — measure different things at different points in the contract lifecycle. The deferred revenue rollforward is the bridge that should make them reconcile. When it doesn't, every senior accountant has the same Excel file open at close.
The four numbers in the revenue waterfall
Each number lives in a different system and serves a different audience:
The revenue waterfall — what each number measures
Bookings are a sales metric — contract value signed in the period. Billings are a treasury metric — invoices issued, regardless of when revenue will be recognized. Recognized revenue is a financial reporting metric governed by ASC 606 — earned as performance obligations are satisfied, not when cash comes in. The deferred revenue rollforward is the reconciliation that proves the others tie. Audit takes all four.
Where the reconciliation breaks
Bookings ≠ Billings. Multi-year contracts billed in installments create a natural gap. A three-year $300K contract shows up as a $300K booking in CRM. The AR module shows $100K billed in Year 1. Cancellations that don't flow back to CRM, delayed invoicing, and mid-term upgrades compound the gap. Under FASB ASC 606-10-25-10 through 25-13, contract modifications must be accounted for as either a separate contract or a modification of the existing arrangement — one of the most judgment-intensive areas of the standard — and the ones most likely to create reconciling items when they aren't captured in both systems.
Billings ≠ Revenue. Annual prepay billed upfront and recognized ratably is the clearest example: $120K invoiced on January 1, $10K recognized each month. The $110K sitting in deferred revenue at month-end is correct — but only if the rollforward captures the billing, the recognition schedule, and any mid-year modifications. Variable consideration and usage-based billing add further complexity: revenue might not be recognizable until usage is confirmed.
Revenue ≠ DR rollforward. Contract modifications not flowed through the rev rec tool are the primary culprit. A senior accountant books a manual JE to revenue for a one-time true-up. The GL moves; the rev rec engine doesn't. By quarter-end, the rollforward doesn't reconcile to the trial balance deferred revenue balance, and the reconciling JE is large enough to draw audit attention.
DR rollforward ≠ GL. Subledger close lag creates the last gap. The rev rec tool closes its period on Day 2. The GL stays open through Day 5. Late-period modifications booked to the GL after the rev rec period locks don't make it into the rollforward for that period.
The three reconciliations an auditor will ask for
Bookings to billings. For every contract signed in the period, show the billing schedule. Multi-year contracts with upfront billing reconcile differently than monthly billed contracts. The workpaper proves every signed contract either generated an invoice or has a documented future billing schedule — nothing signed and silently unbooked.
Billings to revenue — the deferred revenue rollforward. Opening deferred revenue + new billings recognized as deferred + revenue recognized − cancellations and refunds = closing deferred revenue. Every line traceable to a source contract. Every modification preserved. This is the single most-requested workpaper at any rev rec audit, and the one most likely to surface a material weakness if it can't be regenerated from source data.
Revenue to the GL. The recognized revenue on the income statement should equal the sum of all revenue JEs posted to GL revenue accounts. Trivial in concept, frequently broken in practice — because the rev rec tool posts batches at different cadences than the close calendar, and manual JEs for modifications often live outside the tool.
What good looks like
A clean revenue reconciliation has three properties: the bookings-to-billings bridge is auto-generated from the CRM and the AR module without a senior accountant joining files in Excel; the deferred revenue rollforward regenerates from source contracts and reflects all modifications since inception; and the recognized revenue number on the GL ties to the rev rec tool's output for every closed period without a reconciling JE.
The AP automation benchmarks post covers what best-in-class close cycles look like across the finance function — revenue reconciliation delays are one of the top contributors to close slippage past Day 5. The structural fix usually lives upstream in how contract modifications get captured; getting the rollforward to regenerate from source is what makes audit Day 5 stop being optimistic.
See how Cadel handles revenue recognition and reconciliation from contract event to GL — or get in touch to walk through your current deferred revenue rollforward.