Journal Entries & Estimates
Deferred revenue journal entry with monthly recognition
Deferred revenue takes two entries: one when you bill, and one each month as you deliver. Getting each entry right is easy. The close question is whether, across every contract, they still add up to the balance on the trial balance.
When you bill before delivering: Dr Accounts receivable (or Cash, if paid first), Cr Deferred revenue.
Each month as you deliver: Dr Deferred revenue, Cr Revenue, for the part of the service delivered that month.
The check at month end: opening balance + billings − revenue recognized = closing balance, and the closing balance should match the trial balance.
Under ASC 606 the balance is called a contract liability. Plenty of ledgers still name the account deferred revenue or unearned revenue, and the entries are the same whatever the account is called. The examples below use one synthetic contract list, seven subscription and support contracts closing September 2026. It's the same list as the worked example in the deferred revenue schedule, so you can load it there and see every figure on this page.
1. The billing entry
Quillon Partners signs an annual subscription for $24,000, service from October 1, 2026 to September 30, 2027. You invoice on September 28, due on receipt, and the contract can't be cancelled. Nothing has been delivered, so none of it is revenue yet. The invoice creates a receivable and an obligation to deliver a year of service:
| Account | Debit | Credit |
|---|---|---|
| Accounts receivable | 24,000.00 | |
| Deferred revenue | 24,000.00 |
When the customer pays, cash replaces the receivable (Dr Cash, Cr Accounts receivable) and deferred revenue doesn't move. If the customer pays before you invoice, the entry is Dr Cash, Cr Deferred revenue directly.
One timing point is worth knowing before you rely on an invoice date. ASC 606 puts the liability on the books when the payment is made or is due, whichever comes first (ASC 606-10-45-2). An invoice sent before the customer is committed, while the contract can still be cancelled, doesn't create a receivable or a contract liability yet; the standard's own example of this is in ASC 606-10-55-286. Many billing systems post every invoice on the invoice date regardless. If yours does, that's a policy conversation to have once, not something to fix on close day.
2. The monthly recognition entry
For a subscription earned evenly over the service period, the monthly amount is the contract amount spread over the period. Quillon's is $24,000 ÷ 12 = $2,000 a month, starting in October. Each month:
| Account | Debit | Credit |
|---|---|---|
| Deferred revenue | 2,000.00 | |
| Subscription revenue | 2,000.00 |
In practice the month-end entry usually covers every contract at once, grouped by revenue account. For the seven contracts in the example, September's entry is:
| Account | Debit | Credit |
|---|---|---|
| Deferred revenue | 13,250.00 | |
| 4010 Subscription revenue | 12,550.00 | |
| 4020 Support revenue | 700.00 |
“Earned evenly” is an assumption, not a default. It fits subscriptions, support and other services delivered continuously. It doesn't fit usage-based fees, milestone work, or anything recognized at a point in time, and which pattern applies is a judgment for your revenue policy. Within “evenly,” you still choose between equal monthly amounts and actual days of service. The example uses equal months. Under actual days, each month's share moves with its day count (Quillon's October would be $2,038.36 rather than $2,000.00), so the two methods agree over the whole term but not month by month.
3. The roll-forward, contract by contract
Here is September for every contract on the list. Each row is its own small roll-forward, and the total row is the one that has to match the ledger.
| Contract | Aug 31 | Billed | Recognized | Sep 30 |
|---|---|---|---|---|
| Halberd Logistics, $48,000, Mar 2026 to Feb 2027 | 24,000.00 | – | 4,000.00 | 20,000.00 |
| Brightwater Dental, $12,600, Jul 2026 to Jun 2027 | 10,500.00 | – | 1,050.00 | 9,450.00 |
| Kestrel Foods, $90,000, Jan 2026 to Dec 2028 | 70,000.00 | – | 2,500.00 | 67,500.00 |
| Ostrander Group support, $8,400, Sep 2026 to Aug 2027 | 8,400.00 | – | 700.00 | 7,700.00 |
| Larchmont Clinics, $30,000, Aug 2026 to Jul 2027, billed Sep 5 | – | 30,000.00 | 5,000.00 | 25,000.00 |
| Tamsin Analytics, $6,000, Jul 2025 to Jun 2026 | – | – | – | – |
| Quillon Partners, $24,000, Oct 2026 to Sep 2027 | – | 24,000.00 | – | 24,000.00 |
| Total | 112,900.00 | 54,000.00 | 13,250.00 | 153,650.00 |
$112,900.00 + $54,000.00 − $13,250.00 = $153,650.00. That's the figure deferred revenue on the September trial balance should show. Three rows are worth a second look:
- Tamsin Analytics finished in June. It stays on the list at zero. If the ledger still carries a balance for a finished contract, the tie-out misses by exactly that amount, so finished contracts are a quick first check.
- Quillon Partners is billed but not started, so it sits at its full $24,000 with nothing recognized.
- Larchmont Clinics recognized $5,000 in September on a $2,500-a-month contract. That's the next section.
When the total doesn't match the trial balance, the contract list and the ledger disagree. The usual reasons: an invoice coded to deferred revenue that isn't on the list, a contract on the list that was never billed, a credit memo or cancellation booked to the account, last month's entry posted with a different amount, or the ledger using a different method (equal months against actual days).
4. Billed after service starts
Larchmont's service started August 1, but the invoice, due on receipt, went out September 5. If August closed with nothing booked for Larchmont, September carries two months: September's $2,500 and a $2,500 catch-up for August. That's what the schedule above does, and what the schedule tool does by default, with a flag naming the contract.
It keeps the roll-forward clean, but it may not be the right accounting. Under ASC 606, revenue for service already delivered is recognized in the month it's delivered. Until you bill, the other side is a contract asset (ASC 606-10-45-3), or a receivable if the right to payment is already unconditional and only waiting on time to pass (ASC 606-10-45-4). Ledgers often call either one unbilled receivables. Done that way, Larchmont's entries are:
| Account | Debit | Credit |
|---|---|---|
| August 31: August's service, not yet billed | ||
| Contract asset (unbilled receivable) | 2,500.00 | |
| 4010 Subscription revenue | 2,500.00 | |
| September 5: invoice the full year | ||
| Accounts receivable | 30,000.00 | |
| Contract asset (unbilled receivable) | 2,500.00 | |
| Deferred revenue | 27,500.00 | |
| September 30: September's service | ||
| Deferred revenue | 2,500.00 | |
| 4010 Subscription revenue | 2,500.00 | |
Deferred revenue still ends September at $25,000.00 for Larchmont, and the list still totals $153,650.00. What changes is which month carries the $2,500. Booked this way, September's billings into deferred revenue are $51,500.00 rather than $54,000.00, September's recognition is $10,750.00 rather than $13,250.00, and the roll-forward still works: $112,900.00 + $51,500.00 − $10,750.00 = $153,650.00.
Whether a one-month catch-up is acceptable, or August should have carried its own revenue, is a judgment about your policy and materiality. The point is to make it on purpose. If the catch-up happened because nobody noticed the late invoice, the same gap in the billing process can produce another one next month.
5. Current and non-current
On a balance sheet that separates current and non-current liabilities, the usual split is whatever will be recognized within the next 12 months; the rest is non-current. Work it contract by contract from the schedule, not as a percentage of the balance.
At September 30, 2026, every contract in the example finishes within 12 months except Kestrel Foods. Kestrel's $67,500.00 has 27 months left: October 2026 through September 2027 is 12 × $2,500 = $30,000.00 current, and the 15 months from October 2027 through December 2028 are $37,500.00 non-current. The total splits into $116,150.00 current and $37,500.00 non-current.
A prepayment that covers more than a year of service also raises the question of a significant financing component (ASC 606-10-32-15 through 32-20). The one-year practical expedient isn't available here, because most of Kestrel's service comes more than a year after it paid, so that assessment has to be made, even if it concludes there's nothing to adjust. The example leaves it out to keep the entries simple.
Some companies book the non-current portion to its own account each month; others split it only in the reporting package. Either works, as long as the split is recomputed every period rather than carried forward.
6. Explaining the movement at flux review
Deferred revenue rose $40,750.00 in September, from $112,900.00 to $153,650.00. The roll-forward is the explanation, and good commentary says so with the figures: “Up $40,750: $54,000 billed in the month (Larchmont Clinics $30,000, Quillon Partners $24,000, both annual), less $13,250 recognized, including a $2,500 August catch-up on Larchmont, billed late.” Billings less recognition equals the movement exactly, which is the check a reviewer will do. More on that in balance sheet flux analysis.
Build the full schedule
The deferred revenue schedule builds all of this from a pasted contract list: the monthly waterfall, the roll-forward checked against your trial balance, the current and non-current split, and the recognition entry grouped by revenue account. It flags contracts billed after service started, like Larchmont. Load its worked example and set the month to September 2026, and the figures above are what it returns. It runs in your browser; nothing is uploaded.
The expense-side mirror is a prepaid: Dr Prepaid expenses when paid, then Dr Expense, Cr Prepaid expenses as the service is used. The prepaid amortization schedule does the same work for that side.
The contracts and figures on this page are synthetic, and the companies don't exist.
Most of this surfaces again at flux review. The free flux template flags which balances moved enough to explain. The CloseOps Flux & Variance System ($79) starts from your trial balance instead: confirm each account's classification and it builds the income statement and balance sheet flux statements, then ranks what to investigate.
Related: the deferred revenue schedule, which builds the waterfall and roll-forward from your contracts; the prepaid amortization schedule, the same calculation from the expense side; reversing entries, including a revenue-earned-but-unbilled example; and true-ups, for when an estimate meets the actual.
Found something wrong or missing? Tell me here — anonymous, thirty seconds.