Customer Deposit & Prepaid Revenue: What They Are & How to Record Them

A client's attorney sends a $25,000 retainer in November. The work starts in January and wraps up in March. Where does that $25,000 go on the November books?

If you answered "revenue," the financials are wrong. That $25,000 isn't earned yet. The client hasn't delivered any services. The money sits on the balance sheet as a liability until the work is done.

This catches people all the time. Not because they don't know accounting. Because the bank feed shows a deposit and the default reflex is to book it as income. Here's how to handle it correctly.

What is customer deposit or prepaid revenue?

Customer deposit, prepaid revenue, deferred revenue, and unearned revenue are four names for the same thing: money your client received before delivering the service or product. It's a liability on the balance sheet (not revenue on the P&L) from the moment it's received until the work is actually performed. Under ASC 606, this is called a contract liability. For accrual taxpayers, IRS §451 allows deferring income recognition on qualifying advance payments for up to one year for tax purposes. That's a book/tax difference, not a bookkeeping shortcut. The liability stays on the balance sheet until the client earns it.

Key Takeaways

• Customer deposits are balance sheet liabilities: not P&L revenue. They stay there from day one until the work is delivered.
• Four names, one concept: "customer deposit," "prepaid revenue," "deferred revenue," and "unearned revenue" all describe money received before performance.
• ASC 606 calls it a contract liability: recognition happens when (or as) the performance obligation is satisfied, not when cash changes hands.
• Most common miscoding: deposit booked as Other Income on receipt. This overstates current-period revenue and understates the liability. The error compounds if the account is never released.
• §451 creates a book/tax timing difference: accrual taxpayers can defer qualifying advance payments for one tax year, but financial statements still follow ASC 606.
• Recognition triggers differ by agreement type: retainers, flat deposits, and prepayments each have different release events under ASC 606. Know which applies before posting.

What Customer Deposits and Prepaid Revenue Actually Are

The glossary defines revenue recognition as recording income when it's earned, not when cash arrives. Customer deposits put that principle into practice.

When a client pays in advance (a $5,000 deposit on a construction project, a $25,000 legal retainer, a software subscription billed upfront for the year, or a consulting prepayment), the money is in the bank but the performance obligation hasn't been met. The business owes the client work, services, or a refund if things go sideways. That makes it a liability.

Four terms for this concept float around depending on industry and context:

• Customer deposit: common in construction, legal, and services. Often refundable if the project doesn't proceed.
• Prepaid revenue: used more in subscription and SaaS contexts. Cash received before the service period begins.
• Deferred revenue: the balance sheet account name you'll see in most accounting systems. Includes both of the above.
• Unearned revenue: interchangeable with deferred revenue. More common in older accounting textbooks and tax contexts.

They point to the same journal entry.

Why It's a Liability, Not Revenue

ASC 606 (Revenue from Contracts with Customers) requires that revenue be recognized when a performance obligation is satisfied. "Performance obligation" means the agreed-upon service or product has been delivered to the customer.

Receiving cash doesn't satisfy a performance obligation. It creates one.

Until the client's business delivers the service, the customer has a valid claim. If the project is cancelled, the deposit may need to be refunded. That's why the balance sits on the liability side of the balance sheet.

Here's how the November retainer example flows through the books.

November deposit received:

The P&L is untouched. Revenue is zero. Balance sheet shows cash up $25,000 and deferred revenue up $25,000.

March work completed:

Now the P&L sees the income in March, when the client earned it, not November, when the cash arrived.

If work was delivered incrementally (say, monthly over three months), the release would be $8,333 each month as each tranche of work was completed.

Recording the Receipt vs. the Recognition

The process has two distinct events. Bookkeepers need to track both.

Event 1: Cash received. Debit Cash, credit Deferred Revenue (or Customer Deposits, or Unearned Revenue). The account name varies by firm preference. It must be a liability account, not an income account.

Event 2: Work delivered. Debit Deferred Revenue, credit Revenue. This is the recognition event. It happens when the performance obligation is satisfied, which requires communication with the client's team. Did the project close? Was the subscription period consumed? Did the retainer get drawn down?

In practice, someone on the accounting team needs to track when work is delivered and post the release entry. It doesn't happen automatically from a bank feed. That's the workflow gap where most errors accumulate.

See the accounts receivable glossary entry for how the AR side interacts with prepaid and deposit arrangements when clients partially offset balances.

Common Miscoding Bookkeepers Catch at Year-End

Mistake 1: Deposit booked as Other Income on receipt. The bank feed shows $25,000 in. The bookkeeper codes it to "Miscellaneous Income" or "Service Revenue." Current-period P&L is overstated by $25,000. If nobody catches it before the year-end financials, the tax return reflects income that wasn't earned that year.

Mistake 2: Liability sits forever and never gets released. The deposit was recorded correctly as a liability in November. But when the work was completed in March, nobody posted the release entry. Now there's a phantom liability on the balance sheet. It keeps growing as more deposits come in. Year-end review surfaces a deferred revenue balance that's two or three times what it should be. Auditors flag it. Reconciliation takes hours.

Mistake 3: Retainer vs. deposit vs. prepayment distinctions ignored. Under ASC 606, the recognition trigger differs by agreement type.

A prepayment on a fixed service with a fixed timeline releases ratably over time as the service period passes. A flat deposit held until project completion releases all at once when the project closes. A retainer on a draw-down model releases as hours or milestones are consumed. Each invoice drawn against the retainer reduces the liability.

Treating all three the same creates either premature or delayed recognition. The engagement agreement defines which type applies. That document should be on file and referenced when posting.

Mistake 4: §451 confusion between book and tax treatment. Accrual taxpayers can elect under §451 to defer income recognition on qualifying advance payments for up to one year for tax purposes. This doesn't change the book entry. The deferred revenue liability stays on the balance sheet per ASC 606. The difference between book revenue (recognized when earned) and taxable income (deferred for one year) creates a temporary book/tax timing difference that shows up on the M-1 or M-3. Don't let the tax deferral prompt an early release of the liability on the financial statements.

See the income statement and P&L glossary entry for how premature revenue recognition flows through to net income and distorts period-over-period comparisons.

How Growthy Handles Deposit Recognition

Most bank feeds push transaction descriptions like "ACH PAYMENT 847293847 WEB" or "WIRE INCOMING $25,000" with no context about whether the payment is a deposit, a prepayment, or a revenue payment. Growthy reads the pattern of how similar transactions were categorized before and flags ambiguous ones for review rather than defaulting to an income account.

When a deposit comes in from a known client, Growthy categorizes it to the deferred revenue liability account based on prior coding. When the pattern is new or unclear, it surfaces the transaction for your review instead of guessing. You see the suggestion, confirm or correct it, and Growthy carries that forward on the next similar transaction.

The release entry (when work is delivered and the liability converts to revenue) still requires a manual prompt from the accounting team. Growthy holds the liability correctly. The recognition timing depends on information only the client's team has: project completion dates, milestone delivery, subscription periods consumed. That's the 20% where professional judgment runs the workflow.

Start with Growthy free and see how it handles your existing deposit and prepayment transactions.

FAQ

What's the difference between deferred revenue and unearned revenue?

Nothing material. They're the same concept: money received before the service or product is delivered, described with different vocabulary. Deferred revenue is more common in financial statements and accounting software. Unearned revenue appears more often in tax contexts and older accounting literature. Both are balance sheet liabilities until the related performance obligation is satisfied.

Should customer deposits always go to a liability account?

Yes, if there's any remaining performance obligation. If a client pays a deposit and the business has delivered nothing yet, it's a liability. The only exception is if the deposit is truly non-refundable and there's no future service expected (rare in practice). In those cases, there's still an ASC 606 analysis to do before recognizing revenue.

What happens to the deferred revenue account when a project is cancelled?

If the deposit is refundable and the project cancels, debit Deferred Revenue and credit Cash for the refund. If the deposit is non-refundable, the analysis depends on the contract terms and ASC 606's provisions on contract modifications and contract assets. This typically requires a judgment call. Flag it for the CPA rather than posting it as income automatically.

Does §451 apply to all advance payments?

No. The §451 one-year deferral applies to specific qualifying advance payments for services or certain goods. Not all advance payments qualify. A cash deposit held as security (not for future services) doesn't qualify. The tax advisor should confirm which payments are eligible before applying the deferral.

How does a retainer draw-down work on the books?

When a client retains a firm for $25,000 upfront, the full $25,000 goes to Deferred Revenue at receipt. As invoices are drawn against the retainer (say, $5,000 for Month 1 services), debit Deferred Revenue $5,000 and credit Revenue $5,000. The liability decreases with each draw until it reaches zero. If the retainer is exhausted and additional work is done, the client is invoiced directly and AR comes into play. See the accounts receivable entry for how that billing cycle connects.

How do I find stale deferred revenue balances in a client's books?

Pull the trial balance and look at the Deferred Revenue (or Customer Deposits or Unearned Revenue) account balance. Then pull a detail of the transactions in that account going back 12 to 24 months. Any credit entries with no offsetting debit release entry are stale. Cross-reference against the project status list or open engagements. If projects have closed and the liability wasn't released, those entries need correcting before year-end.

The entry is simple. The tracking isn't. Client deposits come in, get booked correctly as liabilities, and then sit there waiting for a release entry that depends on information nobody automatically sends to accounting. Build the habit of matching liability releases to project completions, and the year-end cleanup becomes a non-issue.

Start with Growthy free and bring the deferred revenue balance under control.