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.

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.

Step 1	Reconcile deferred revenue roll-forward to the GL
Step 2	Review contract modifications booked during the period
Step 3	Post recognition journal entries by contract line
Step 4	Review variable consideration estimates against actuals

What does a controller actually check before closing?

The four steps in the facts table above, in order — roll-forward reconciliation first, journal entries last.

Why does the order matter?

Posting journal entries before reconciling the roll-forward risks locking in an error that a five-minute reconciliation would have caught.

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

Journal entry

Month-end revenue recognition journal entry

For a $10 one-time payment recognized immediately (per Stripe's documented Revenue Recognition methodology):

Debit	Credit	Amount
Accounts Receivable	Deferred Revenue	+10.00
Cash	Accounts Receivable	+10.00
Deferred Revenue	Revenue	+10.00

Net effect: Cash +10.00, Revenue +10.00.

Frequently Asked Questions

Reviewing contract modifications — a mid-period upgrade or downgrade changes the recognition schedule and is easy to close before it's fully reflected.

By contract line — an invoice can bundle several performance obligations with different recognition schedules.

Compare the period's estimate against actual results and true up the difference before finalizing the close.

Sources

How-to

How do you calculate a contract's transaction price under ASC 606?

Transaction price is the consideration a company expects in exchange for goods or services. Start with the stated contract price, add variable consideration using the expected-value or most-likely-amount method, constrained to amounts unlikely to reverse, adjust for any significant financing component, then subtract noncash consideration and amounts payable to the customer.

Diagnostic

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.

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.