Skip to main content
BlogOctober 12, 202611 min read

Deferred revenue journal entries for an annual SaaS contract, month by month

Journal entries for an annual SaaS contract billed upfront: the invoice, the cash receipt, and 12 monthly releases from deferred revenue to revenue.

Zuny FesterBy Zuny Fester, Head of Operations and Marketing
Reviewed by Zuny Fester
Published Editorial policy

Part of the revenue recognition guide.

Deferred revenue journal entries for an annual SaaS contract, month by month

For an annual SaaS contract billed upfront, three journal entries record deferred revenue: debit accounts receivable and credit deferred revenue when you invoice, debit cash and credit accounts receivable when the customer pays, and each month debit deferred revenue and credit subscription revenue for one-twelfth of the contract. For a $120,000 annual contract, that is a $120,000 invoice entry, a $120,000 cash entry, and 12 monthly releases of $10,000.

The entries are simple. Getting them right every month, for every contract, with start dates, prorations, and changes, is the part that breaks. Below is the full entry table for a $120,000 contract, the month-by-month balance, and the edge cases that trip up month-end close.

Key takeaways

• Deferred revenue is a contract liability under ASC 606: cash received or due before you deliver the service.

• You record the receivable and deferred revenue at invoicing only when the right to payment is unconditional, typically a non-cancellable contract with the invoice due; otherwise, record deferred revenue when cash arrives.

• A $120,000 annual contract releases $10,000 a month, and deferred revenue falls from $120,000 to zero over 12 months.

• Mid-month start dates need a daily proration policy, applied the same way to every contract.

• Upgrades, cancellations, and credits change the schedule, and each one must reach the revenue schedule before close.

• Loopfour, the deterministic finance workflow automation platform, posts the monthly release from the signed contract and holds the run when the invoice, schedule, and ledger disagree.

What is deferred revenue for an annual SaaS contract?

Deferred revenue is the amount a customer has paid, or owes unconditionally, for service you have not yet delivered. Under ASC 606-10-45-2, it is a contract liability: your obligation to provide the service or return the money. It is not revenue until you deliver. For the broader definition, see what deferred revenue is and why it's a liability.

For an annual subscription billed upfront, the entire annual fee starts as deferred revenue. The customer receives and consumes the service evenly over the year, so you recognize revenue ratably: one-twelfth each month, or a daily rate if your policy prorates by day.

The example contract

The worked example uses one contract. A customer signs a non-cancellable 12-month subscription for $120,000, starting January 1. You invoice the full amount on January 1 with net-30 terms. The customer pays on January 31. There is no setup fee, no discount, and no usage component. Sales tax is excluded from the transaction price under the ASC 606 policy election.

What journal entries record deferred revenue?

Three entries cover the life of the contract: the invoice, the cash receipt, and the monthly release.

Entry 1: the invoice

When you invoice a non-cancellable contract, you have an unconditional right to the payment, so you record a receivable and an equal contract liability.

DateAccountDebitCredit
Jan 1Accounts receivable$120,000
Deferred revenue$120,000

If the contract is cancellable without penalty before the service starts, the answer changes. You do not yet have an unconditional right to payment. Many teams then skip the gross-up and record deferred revenue only when cash is received. Document the policy either way.

Entry 2: the cash receipt

When the customer pays, cash replaces the receivable. Deferred revenue does not change.

DateAccountDebitCredit
Jan 31Cash$120,000
Accounts receivable$120,000

Entry 3: the monthly release

At each month-end, you move one month of service from deferred revenue to revenue: $120,000 ÷ 12 = $10,000.

DateAccountDebitCredit
Jan 31Deferred revenue$10,000
Subscription revenue$10,000

The full month-by-month entry table

Here is every entry for the contract, with the deferred revenue balance after each month-end. The balance falls by $10,000 a month and reaches zero on December 31.

DateEntryDebitCreditAmountDeferred revenue balanceCumulative revenue
Jan 1InvoiceAccounts receivableDeferred revenue$120,000$120,000$0
Jan 31Cash receiptCashAccounts receivable$120,000$120,000$0
Jan 31January releaseDeferred revenueSubscription revenue$10,000$110,000$10,000
Feb 28February releaseDeferred revenueSubscription revenue$10,000$100,000$20,000
Mar 31March releaseDeferred revenueSubscription revenue$10,000$90,000$30,000
Apr 30April releaseDeferred revenueSubscription revenue$10,000$80,000$40,000
May 31May releaseDeferred revenueSubscription revenue$10,000$70,000$50,000
Jun 30June releaseDeferred revenueSubscription revenue$10,000$60,000$60,000
Jul 31July releaseDeferred revenueSubscription revenue$10,000$50,000$70,000
Aug 31August releaseDeferred revenueSubscription revenue$10,000$40,000$80,000
Sep 30September releaseDeferred revenueSubscription revenue$10,000$30,000$90,000
Oct 31October releaseDeferred revenueSubscription revenue$10,000$20,000$100,000
Nov 30November releaseDeferred revenueSubscription revenue$10,000$10,000$110,000
Dec 31December releaseDeferred revenueSubscription revenue$10,000$0$120,000

Three checks prove the schedule is right. Total debits to deferred revenue equal total credits ($120,000 each). Cumulative revenue plus the deferred balance always equals $120,000. And the deferred revenue balance in the ledger matches the schedule at every month-end.

How do the balance sheet and income statement look?

At any month-end, the contract appears as deferred revenue on the balance sheet and subscription revenue on the income statement. At March 31, for example:

StatementLineMarch 31 amount
Balance sheetCash$120,000
Balance sheetAccounts receivable$0
Balance sheetDeferred revenue (current liability)$90,000
Income statement, year to dateSubscription revenue$30,000

Deferred revenue that will be recognized within 12 months is a current liability. For multi-year contracts billed upfront, the portion beyond 12 months is non-current. If you track many contracts, a deferred revenue waterfall schedule shows when each balance will release.

Edge cases that change the entries

The base entries hold for a clean annual contract. Real contracts add dates, changes, and credits. Each of these needs a policy applied the same way every time.

Mid-month start dates

If the contract starts mid-month, prorate the first and last months, usually by day. Suppose the same $120,000 contract starts January 15 and runs to January 14 of the following year. With a daily rate of $120,000 ÷ 365 = $328.77, January's release covers 17 days: about $5,589.04. The final partial month picks up the remainder so total revenue equals $120,000 exactly.

Pick one convention (daily, half-month, or full-month) and apply it to every contract. Mixing conventions across contracts is a common audit finding.

Monthly or quarterly billing on an annual contract

If you bill the same annual contract quarterly, each invoice creates $30,000 of deferred revenue, released at $10,000 a month. The revenue pattern is identical. Only the balance sheet changes: deferred revenue peaks at $30,000 instead of $120,000.

Upgrades and add-ons

An upgrade mid-year is a contract modification, and it changes the monthly release. For a standard SaaS upgrade, the remaining deferred balance plus the new consideration is spread over the remaining months. See our worked example of revenue recognition for a mid-term upgrade.

Cancellations and refunds

If a customer cancels and receives a refund for the unused months, reverse the unused deferred revenue against cash or a refund liability. If the contract is non-cancellable and no refund is due, keep recognizing ratably over the service period while the service remains available to the customer.

Credits and concessions

A service credit for a past outage reduces revenue; it does not simply reduce deferred revenue. Credits are variable consideration under ASC 606, and they need to reach the schedule, not just the billing system.

Where deferred revenue entries break at close

The entries break when the schedule and the ledger drift apart. Nothing in the accounting is hard. The data behind it arrives late or incomplete.

• The invoice is posted, but no revenue schedule is created, so the full $120,000 sits in deferred revenue until someone notices.

• The start date in the ERP is the invoice date, not the service start date, shifting revenue between months.

• A manual release is posted twice in the same month after a rerun.

• An upgrade is invoiced as a separate line with its own schedule while the original schedule keeps running.

These are all control failures, not accounting errors. A reconciliation of the deferred revenue balance to the schedule at every close catches them. Automating that reconciliation removes the reason they happen.

Book a workflow review to see how your deferred revenue schedule ties to the ledger today.

How to choose a way to run deferred revenue entries

Choose a method that creates the schedule from the contract, not from the invoice, and that reconciles the balance to the ledger every month. Spreadsheets work for a few dozen contracts. ERP revenue modules, such as NetSuite Advanced Revenue Management, generate revenue recognition plans from sales transactions when items and rules are configured correctly.

The weak point is the handoff into the ERP. A horizontal automation platform can move contract data and is flexible, but your team maintains the mapping and the checks. Loopfour runs predefined, programmatic steps instead. The Contract Agent reads the service dates and price from the signed contract under a confidence threshold, with low-confidence fields routed to a reviewer. Deterministic steps then compare those terms to the invoice and the ERP schedule, post or confirm the monthly release, and reconcile the deferred revenue balance. Any mismatch holds the run and goes to a named approver in Slack.

Frequently asked questions

What is the journal entry for deferred revenue? When you invoice or receive payment before providing the service, debit accounts receivable or cash and credit deferred revenue. Each period, as you provide the service, debit deferred revenue and credit revenue for the portion earned. For a $120,000 annual contract, the monthly entry is $10,000.

Is deferred revenue a debit or a credit? Deferred revenue is a liability, so it carries a credit balance. It increases with a credit when you bill or collect in advance, and it decreases with a debit when you recognize revenue.

Do you record deferred revenue when you invoice or when you get paid? Under ASC 606, you record a contract liability when payment is received or due, whichever is earlier. For a non-cancellable contract with an issued invoice, that is usually at invoicing. For a cancellable contract, many companies record it only when cash is received.

How do you calculate monthly deferred revenue recognition? Divide the contract's transaction price by the number of months in the service period, or by the number of days if you prorate daily. For a $120,000 annual contract starting on the first of the month, recognize $10,000 per month.

Is deferred revenue current or non-current? Deferred revenue expected to be recognized within 12 months of the balance sheet date is a current liability. Amounts beyond 12 months, common with multi-year upfront billing, are non-current.

Conclusion

Deferred revenue journal entries for an annual SaaS contract come down to one invoice, one cash receipt, and 12 identical releases. The accounting fits on one page. The discipline is making sure every contract gets its schedule, every change reaches it, and the balance ties to the ledger every close.

Tell us the one workflow your team dreads. We will show it running: deterministic, permissioned, and auditable.

Book a demo.

Sources

• FASB, ASU 2014-09, Revenue from Contracts with Customers (Topic 606)

• Oracle NetSuite Help, Item configuration for Advanced Revenue Management

• What is ASC 606? The five-step model, explained with SaaS examples

• How to automate ASC 606 revenue recognition without losing the audit trail

• How to automate month-end close without breaking your audit trail

• The month-end close checklist: every step, owner, and control

Sources

  1. Financial Accounting Standards Board, ASU 2014-09, Revenue from Contracts with Customers (Topic 606) (opens in a new tab).
  2. Oracle NetSuite, Item configuration for Advanced Revenue Management (opens in a new tab).