Deferred revenue journal entry: How to record unearned revenue

- What is deferred revenue?
- Is deferred revenue a liability or an asset?
- Deferred revenue vs. unearned, accrued revenue, and deferred expenses
- How deferred revenue works in accrual accounting
- How to record a deferred revenue journal entry
- Deferred revenue journal entry examples
- How to manage deferred revenue
- How to avoid common journal entry mistakes
- Deferred revenue and financial reporting
- Keep deferred revenue schedules current with Ramp Stack

A deferred revenue journal entry records cash you receive before delivering a product or service and recognizes that revenue only as you fulfill the obligation. In practice, this happens in two steps: you first record the payment as deferred revenue, then reclassify it to earned revenue over time.
Recording these entries correctly keeps revenue timing accurate and ensures your financial statements reflect what your business has actually earned.
What is deferred revenue?
Deferred revenue is cash you receive from a customer for a product or service you'll deliver in the future, recorded as a liability until you earn it. It's also called unearned revenue, and because you still owe the customer that product or service, it sits on your balance sheet rather than as income.
In accrual accounting, prepaid funds increase your cash balance but don't count as revenue on the income statement until you deliver the goods or services. That's why deferred revenue often improves short-term cash flow without immediately increasing reported revenue.
If the product or service is never delivered, the payment must be returned to the customer. Until your obligation is fulfilled, deferred revenue represents money you've collected but haven't yet earned.
Is deferred revenue a liability or an asset?
Deferred revenue is a liability, not an asset, because you still owe the customer the goods or service they paid for. It represents an obligation to deliver, not value you've earned.
On the balance sheet, that liability is either current or non-current based on a 12-month threshold. If you'll fulfill the obligation within a year, classify it as a current liability. If delivery extends beyond 12 months, such as a multi-year subscription, the portion earned later is a non-current (long-term) liability.
This is the opposite of accounts receivable. Accounts receivable is an asset because it's money owed to you for work you've already delivered. Deferred revenue is cash you've received before delivering anything.
Deferred revenue vs. unearned, accrued revenue, and deferred expenses
Deferred revenue is easy to confuse with related accounting concepts that move cash and recognition in different directions. The table below shows how each one is classified and when it hits your income statement.
| Concept | What it is | Asset or liability | When recognized |
|---|---|---|---|
| Deferred (unearned) revenue | Cash received before you deliver | Liability | As you deliver over time |
| Accrued revenue | Revenue earned but not yet billed or received | Asset | When earned, before cash arrives |
| Deferred expense | Cash you paid for a future benefit | Asset | As you consume the benefit |
Deferred vs. unearned revenue
Deferred revenue and unearned revenue are the same thing. "Unearned revenue" is the older term, while "deferred revenue" is more common in SaaS and subscription businesses, and the unearned revenue journal entry records the same two-step movement from liability to earned revenue.
Deferred vs. accrued revenue
Deferred revenue is cash you receive before you deliver, so it's a liability. Accrued revenue is the reverse: revenue you've earned but haven't yet billed or collected, so it's an asset. For example, a customer prepaying $1,000 for next quarter's service creates deferred revenue, while finishing $1,000 of consulting work you haven't invoiced yet creates accrued revenue.
Deferred revenue vs. deferred expenses
Deferred revenue is prepaid income you still owe, so it's a liability. A deferred (or prepaid) expense is money you paid for a future benefit, so it's an asset. If a customer prepays you $1,000 for services, that's deferred revenue; if you prepay $750 of rent, that's a deferred expense.
How deferred revenue works in accrual accounting
Accrual accounting recognizes revenue when your company earns it, not when you receive cash. This approach follows the revenue recognition principle, which requires revenue to be recorded in the period when goods or services are delivered. Under GAAP, this is governed by ASC 606, which recognizes revenue when you satisfy a performance obligation, not when the cash arrives.
Deferred revenue fits naturally into this framework. When cash comes in before delivery, you record it as a liability. As you fulfill the contract over time, you reduce that liability and recognize revenue gradually.
This treatment also supports the matching principle. Revenue is recognized in the same periods as the costs incurred to deliver the product or service, which leads to more accurate profitability reporting. A $12,000 annual contract shows the full cash inflow on day one, but revenue is recognized evenly at $1,000 a month as you deliver, so your income statement reflects delivery rather than payment timing.
| Accrual accounting | Cash accounting |
|---|---|
| Recognizes revenue when earned | Recognizes revenue when you receive cash |
| Uses deferred revenue for prepayments | No deferred revenue account |
| Required under generally accepted accounting principles (GAAP) for most businesses | Common for very small businesses |
Cash accounting differs from accrual accounting because it does not account for deferred revenue. As a result, income can appear inflated in periods with large upfront payments, even though the underlying obligations have not yet been fulfilled.
How to record a deferred revenue journal entry
A deferred revenue journal entry always follows the same logic: record cash as a liability when payment is received, then recognize revenue as the obligation is fulfilled.
Recording deferred revenue isn't complicated, but consistency matters. Each entry serves a specific purpose, and skipping steps can lead to misstatements that compound over time.
Step 1: Record the cash as deferred revenue
When you first receive payment, you haven't earned the revenue yet. You record the cash and set up a deferred revenue liability.
| Account | Debit | Credit |
|---|---|---|
| Cash | X | |
| Deferred revenue | X |
For example, a customer prepays $12,000 for a 12-month subscription. You would record it as:
| Account | Debit | Credit |
|---|---|---|
| Cash | $12,000 | |
| Deferred revenue | $12,000 |
At this point, no revenue is recognized on the income statement.
Step 2: Recognize revenue over time
As you deliver the service, you recognize revenue by reducing deferred revenue and increasing earned revenue.
| Account | Debit | Credit |
|---|---|---|
| Deferred revenue | X | |
| Revenue | X |
For the annual subscription, you divide the total amount received by 12 to calculate monthly revenue:
$12,000 / 12 months = $1,000 per month
Each month, you record:
| Account | Debit | Credit |
|---|---|---|
| Deferred revenue | $1,000 | |
| Revenue | $1,000 |
You continue until the deferred revenue balance reaches zero.
Step 3: Adjust journal entries
At the end of each period, you make adjusting entries to reflect progress that hasn't yet been recorded. Common adjustments include:
- Partial fulfillment, which requires prorating revenue based on time or usage
- Refunds and cancellations, which reverse deferred revenue and, if needed, previously recognized revenue
- Contract modifications, which require updating the remaining deferred revenue schedule to reflect new terms
Deferred revenue journal entry examples
Deferred revenue journal entries are easier to understand when you see how upfront payments move from liabilities to earned revenue over time. These examples show how timing affects journal entries across common business scenarios:
SaaS subscription
A software-as-a-service (SaaS) company sells a 6-month software subscription for $12,000, paid upfront.
Initial entry:
| Account | Debit | Credit |
|---|---|---|
| Cash | $12,000 | |
| Deferred revenue | $12,000 |
Monthly entry (6 months):
| Account | Debit | Credit |
|---|---|---|
| Deferred revenue | $2,000 | |
| Subscription revenue | $2,000 |
A simple T-account view helps visualize this:
| Debit | Credit |
|---|---|
| $2,000 (Month 1 recognition) | $12,000 (Initial payment) |
| $2,000 (Month 2 recognition) | |
| $2,000 (Month 3 recognition) | |
| $2,000 (Month 4 recognition) | |
| $2,000 (Month 5 recognition) | |
| $2,000 (Month 6 recognition) | |
| Total debits: $12,000 | Total credits: $12,000 |
Service contract
A consulting firm signs a 6-month service contract for $6,000, billed upfront.
Initial entry:
| Account | Debit | Credit |
|---|---|---|
| Cash | $6,000 | |
| Deferred revenue | $6,000 |
Monthly recognition is $6,000 / 6 = $1,000 per month:
| Account | Debit | Credit |
|---|---|---|
| Deferred revenue | $1,000 | |
| Service revenue | $1,000 |
After 6 months, deferred revenue is fully recognized.
Product deposit
A customer places a $3,000 deposit on a custom product.
Initial entry:
| Account | Debit | Credit |
|---|---|---|
| Cash | $3,000 | |
| Deferred revenue | $3,000 |
Upon delivery:
| Account | Debit | Credit |
|---|---|---|
| Deferred revenue | $3,000 | |
| Product revenue | $3,000 |
Revenue recognition occurs at delivery, not when payment is received.
How to manage deferred revenue
Managing deferred revenue becomes more complex as transaction volume grows. Clear policies, reliable tracking, and automation help reduce errors, support compliance, and keep financial reporting consistent.
Set clear revenue recognition policies
Written policies define when your company earns revenue and how it should be measured. These policies create consistency across contracts and teams and reduce judgment calls during month-end close. Clear documentation also supports audits and helps new team members apply revenue recognition rules correctly as the business scales.
Build recognition schedules and tracking systems
Deferred revenue requires schedules that map revenue recognition to time or performance milestones. Without structured tracking, it's easy to miss monthly entries or recognize too much revenue at once. Reliable systems make revenue recognition repeatable. They support accurate forecasting, consistent journal entries, and fewer last-minute adjustments during close.
Keep documentation for audit trails
Contracts, invoices, and recognition schedules should link directly to journal entries. Strong documentation supports compliance, speeds up audits, and reduces back-and-forth with auditors. Clear audit trails also make internal reviews more efficient and lower the risk of errors going unnoticed.
Review and reconcile deferred revenue accounts regularly
Monthly payment reconciliations help catch issues early. Regular reviews confirm that deferred revenue balances reflect outstanding obligations rather than outdated contracts or missed adjustments. Consistent reconciliation also improves forecasting by keeping deferred revenue balances accurate and current. Automated reconciliation surfaces variances faster than manual review, and Webflow cut its credit card reconciliation time 75% with Ramp.
Use accounting software features for automation
Manual deferred revenue tracking does not scale. Automation helps generate journal entries, apply recognition schedules, and sync data across billing and accounting systems. Ramp's Accounting Agent auto-codes every transaction to your ERP and codes 3.5x more transactions automatically than rules-only tools, with confidence, rationale, and override on every decision so your team keeps full control.
How to avoid common journal entry mistakes
Deferred revenue errors usually stem from timing or classification issues. To avoid misstating revenue or liabilities, entries should always reflect when obligations are fulfilled rather than when cash moves.
Watch for these common issues and how to prevent them:
- Recording deferred revenue as immediate income: Always confirm whether goods or services have been delivered before recognizing revenue, even if payment is received upfront
- Forgetting to recognize revenue over the service period: Use revenue recognition schedules tied to contract terms so deferred balances are reduced consistently each period
- Misclassifying deferred revenue on financial statements: Review balance sheet classifications regularly to ensure deferred revenue is recorded as a liability until earned
- Failing to adjust for contract modifications or cancellations: Revisit deferred revenue schedules whenever contracts change to reflect updated timing, scope, or refund obligations
Deferred revenue and financial reporting
Deferred revenue affects all three financial statements by separating cash collection from revenue recognition. This distinction helps ensure financial reports reflect actual performance rather than payment timing.
On the balance sheet, deferred revenue appears as a current or long-term liability depending on when the obligation will be fulfilled, following the same 12-month classification rule covered earlier. On the income statement, it determines when revenue is recognized, smoothing income over the period services are delivered. On the cash flow statement, deferred revenue explains why cash received may not match reported revenue.
Because revenue is recognized as you deliver rather than when cash lands, a single large prepayment shows up as steady monthly revenue instead of one lumpy spike, which makes period-over-period performance easier to compare.
Deferred revenue also matters for financial analysis:
- It impacts current ratios and working capital
- It affects revenue growth trends and comparability across periods
- It influences the predictability of future earnings
Keep deferred revenue schedules current with Ramp Stack
Most deferred revenue schedules live in spreadsheets that someone rolls forward by hand each month. A missed recognition entry or a contract change that never reaches the schedule throws off the liability balance, and you usually find it during reconciliation.
Ramp Stack lets your team deploy agents to build deferred revenue schedules and prepare recognition entries for your review. Agents pull contracts and billing data from your accounting system and source documents, then lay out the schedule in a native, formula-backed workbook you can inspect and edit. Every session produces an exportable Session Audit Log, and nothing syncs to your accounting system until an accountant approves it.
Here's what deferred revenue work looks like with Stack:
- Prepare each period's recognition entry: Agents draft the debit to deferred revenue and credit to revenue straight from the schedule, ready for your approval.
- Update schedules when contracts change: Describe an upgrade or cancellation, and the agent revises the remaining schedule and drafts the adjusting entry.
- Reconcile the balance every month: The agent compares your general ledger balance to the schedule and flags differences for you to investigate.
- Keep an audit trail for every entry: Each approved entry links back to the Stack session that produced it, so you can trace the posted number to the work behind it.
- Write your recognition policy once: Save your process in plain English as a skill, and the agent follows it every close.
Try Stack for free to see how companies are running recurring schedules and reconciliations up to 9x faster.

FAQs
When you receive payment before delivering, you debit Cash and credit Deferred revenue. As you fulfill the obligation, you debit Deferred revenue and credit Revenue.
Unearned revenue uses the same entries as deferred revenue: debit Cash and credit Deferred (unearned) revenue on payment, then debit Deferred revenue and credit Revenue as you earn it.
Record it as a liability when you collect the cash, then move it to earned revenue in each period as you deliver the product or service.
The initial double entry is a debit to Cash and a credit to Deferred revenue. The recognition double entry is a debit to Deferred revenue and a credit to Revenue.
“I assumed I would have to choose between speed and control. What I found is that you can have both. A well-designed system takes friction out, for the finance function and for everyone else.”
Justin Webster
CFO, Denver Broncos

“A well-run district should not have to choose between getting work done at the school site and keeping control of the dollars behind it. We're not hiring more people to do more jobs, so we have to be smarter about the process. With Ramp, the purchase, the receipt, and the record stay together from the start. ”
Nick Brizeno
Director of Purchasing, San Marcos Unified School District

“In senior living, scale only works if the communities still feel personal. We needed the back office to carry more of the complexity, not the people serving residents. Ramp helped us build that infrastructure, so the experience in the community could stay human.”
Ryan Cole
CFO, Agemark Senior Living

“AI is moving faster than the finance context around it. Prices change, models change, and the value is not always obvious from an invoice. We needed enough detail to know which bets deserved more investment — and which ones did not.”
Greg Cooley
Controller, AngelList

“Invoices, cards, tokens. The categories change but the principle doesn't: know where the money is going, remove the work around it, and make sure the spend is worth it.”
Maciej Mylik. Finance
ElevenLabs

“We weren’t trying to retrofit an old finance system. We had a blank canvas, and Ramp gave us the foundation to build a global finance function of the future.”
Justin Dourado
Director of Finance, Othership

“There's just no surprises anymore. No more waiting two months to find out how a job did. We know how it's doing as it's happening.”
Erich Kuss
Financial Systems Manager, Infinity Home Services

“More token spend isn’t proof that AI is working. Less isn’t proof that it isn’t. What matters is whether we’re buying the right level of intelligence for the work. Ramp lets us make that judgment in the same place we manage every other type of spend.”
Cody Nutt
Senior Director of Business Systems, Daxko


