Why doesn't deferred revenue match the general ledger?

Deferred revenue usually drifts from the general ledger when the billing system's revenue schedule isn't synced to GL journal entries, or when manual entries post outside that schedule. Reconcile the deferred revenue roll-forward against the GL trial balance at the contract-line level, not the invoice level, to find exactly where the two diverge each month.

By Zuny Fester, Head of Operations and Marketing

Reviewed by Zuny Fester

Published September 8, 2026Last reviewed September 8, 2026Editorial policy

Part of the revenue recognition guide.

Most common cause	Billing system revenue schedule not synced to GL journal entries
Second most common cause	Manual journal entries posted outside the billing system's schedule
Where to check first	Deferred revenue roll-forward vs. GL trial balance
Typical fix	Reconcile at the contract-line level, not the invoice level

What actually causes the mismatch?

Almost always a timing or mapping gap between the system that calculates the revenue schedule and the system of record for the GL.

How do you isolate where it diverges?

Roll forward deferred revenue by contract line, then diff it against the GL trial balance for the same period — see the field-mapping table below.

Next step

Map the finance workflow with the most exposure and prove the automation path.

Bring the invoice, contract, payment reconciliation, or customer finance workflow you have to defend at audit. Loopfour can map the trigger, controls, integrations, and approval loop.

Book a workflow review

Field mapping

Billing-system to GL field mapping for deferred revenue

Billing system field	GL account	Notes
Invoice line service period	Deferred revenue schedule	Drives the amortization period
Contract line amount	Deferred revenue (liability)	Recorded at invoice finalization
Recognized-to-date	Revenue	Posted per accounting period, not per invoice
Manual adjustment	Deferred revenue / Revenue	Must reference the originating contract line

Frequently Asked Questions

Rounding differences under a few dollars per contract line are common; anything systematic points to a schedule or timing bug.

Contract-line level — invoices can bundle multiple performance obligations with different schedules, which hides the real source of drift.

Compare the deferred revenue roll-forward (beginning balance plus billings minus recognized) against the GL trial balance for the same period.

Sources

Definition

What is ASC 606 revenue recognition?

ASC 606 is the FASB standard for recognizing revenue when control of a good or service transfers to the customer, for the amount expected in exchange. It uses one five-step model: identify the contract, identify performance obligations, determine the transaction price, allocate that price, and recognize revenue as each obligation is satisfied.

Integration

Which billing platforms support automated ASC 606 revenue recognition?

Stripe Billing, NetSuite, and Salesforce Revenue Cloud all offer native ASC 606 and IFRS 15 revenue recognition automation, generating deferred revenue schedules and recognition journal entries from contract and invoice data. Spreadsheet-based tracking has no native automation and carries meaningfully higher manual-error and audit risk as contract volume and complexity grow.

Role guide

How should a controller close revenue at month-end under ASC 606?

At month-end, a controller reconciles the deferred revenue roll-forward to the general ledger, reviews any contract modifications booked during the period, posts recognition journal entries by contract line rather than by invoice, and checks variable consideration estimates against actuals before closing the revenue sub-ledger for the period.