Deferred revenue: Why a customer deposit is not always income yet

Cash in the bank feels like income. A contractor who collects a $5,000 deposit before starting a kitchen renovation has $5,000 more in their account than they did the day before. But under the accounting rules governing when revenue is actually recognised, that $5,000 may not be income yet on the financial statements. Whether it is taxable income in the same period is a separate question governed by a different set of rules entirely.

Getting both questions right, and keeping them separate, is what makes deferred revenue one of the more nuanced topics in small-business accounting.

What deferred revenue is on the financial statements

Under ASC 606, the core principle for revenue recognition is to depict the transfer of goods or services to customers in an amount that reflects the consideration the business expects to receive in exchange for those goods or services. ASC 606 uses the term contract liability for an obligation to transfer goods or services when the business has already received consideration or when consideration is due.

When a contractor receives a $5,000 deposit before any work begins, and no performance obligation has yet been satisfied, the correct entry is to record cash and a contract liability, not service revenue. The business has additional cash but also an obligation to perform. Until that obligation is fulfilled, the payment sits on the balance sheet as a liability.

This is commonly called deferred revenue or unearned revenue. It is not necessarily an obligation to return the same money. The contractor's liability is an obligation to provide the agreed renovation work. Whether the payment is refundable depends on the contract terms, not on its classification as deferred revenue.

When revenue is recognised: completion is not always required

The original blog stated that a contractor's deposit stays deferred until the project is "complete and accepted." That framing is too categorical and needs correction.

ASC 606 recognises revenue when, or as, performance obligations are satisfied. Satisfaction happens either at a point in time or over time. For over-time recognition, the guidance considers three criteria: whether the customer simultaneously receives and consumes the benefits of performance, whether performance creates or enhances an asset the customer controls, or whether an asset has no alternative use to the business and the business has an enforceable right to payment for performance completed to date.

A contractor working on customer-controlled property may satisfy the second criterion, which would allow revenue to be recognised progressively as work advances rather than waiting for final completion. An annual gym membership provides access over the entire year; the operator recognises revenue across the access period rather than only at year-end, because the customer receives and consumes the access benefit continuously.

The practical implication is that the right pattern of revenue recognition depends on the terms of the contract and the nature of the performance obligation, not on a blanket rule that money received in advance stays deferred until a single completion event.

Recording the full transaction, not just the deposit release

The original blog showed the deposit entry and its release but did not show the complete picture for a $20,000 job where only $5,000 was received upfront. Releasing the $5,000 liability does not by itself record the full job revenue. The remaining $15,000 must also be recognised when the corresponding performance occurs.

Assume no work occurs in October, all contracted work occurs in November, the total price is fixed, and the remaining balance becomes unconditionally due when the work is finished:

This records $20,000 of November revenue without recognising revenue again when the final receivable is collected. If performance instead spans reporting periods and qualifies for over-time recognition, revenue and the deposit's release must reflect the progress rather than waiting for a single completion event.

The tax question is separate from the financial reporting question

The most important correction in this blog concerns how deferred revenue and federal income tax interact. The financial reporting rule asks what has been transferred to the customer. The tax rule asks when the applicable method and the payment's specific characteristics require the amount to enter taxable income. These are different questions with different answers, and the financial-reporting classification as a liability does not automatically defer the tax obligation.

For cash-method taxpayers, income generally enters gross income when actually or constructively received. An advance payment for future services is therefore generally taxable in the year received, even though the work has not yet been performed. The financial statement shows a liability; the tax return may show income in the same year. These are not contradictory, because they are answering different questions under different frameworks.

For accrual-method taxpayers, the general rule is that income enters gross income when the right to receive it is fixed and the amount can be determined with reasonable accuracy. Advance payments have historically presented a complication here, because the all-events test could require inclusion before delivery. Treasury Regulation 1.451-8 provides a permitted deferral method for eligible accrual-method taxpayers. The regulation includes routes for taxpayers both with and without an applicable financial statement, so the availability of deferral is not conditioned solely on having audited financial statements. When eligible, the deferral is generally limited to the year following the receipt year. A payment received in 2026 can be deferred to 2027 at the latest under this method, even if the service will be delivered over a longer period.

The key distinction is that "not recognised as revenue yet" on the financial statements does not automatically mean "not yet taxable." Confirm the applicable tax treatment with your accountant based on your entity type, accounting method, and the specific payment terms before assuming that booking a liability on the balance sheet defers the related tax obligation.

Not every advance payment is the same

The name a payment carries does not determine its accounting or tax treatment. A payment labelled a "deposit" is not automatically nontaxable on receipt, and a payment labelled "nonrefundable" is not automatically earned for financial reporting purposes. The underlying rights and obligations govern both questions.

The Supreme Court's decision in Indianapolis Power and Light Co. illustrates the contrast. That utility required certain customers to post security for future electricity bills. Customers could recover the deposit by establishing acceptable credit, and refunds could be paid in cash or applied against bills at the customer's election. The Court held the deposits were not taxable advance payments upon receipt because the utility lacked complete dominion over the funds. The decisive question was not whether the utility could temporarily use the cash, but whether it had a guarantee of keeping it.

An ordinary advance against a fixed-price service contract differs materially from that arrangement. The contractor can generally keep the advance by fulfilling the contractual obligation. That means the advance is not a refundable security deposit, and its tax treatment follows the applicable advance-payment rules rather than the Indianapolis Power analysis.

The practical guidance is to review the actual contract terms before deciding how to classify a payment: whether performance or a refund right is the mechanism by which the customer recovers value, what the business must do to retain the amount, and when performance obligations are satisfied under ASC 606 principles.

Monthly controls that prevent misclassification

For businesses that regularly collect advances, the most reliable practice is a monthly review of the deferred revenue balance against the status of open contracts. Each open contract should have a recorded deferred revenue balance that reflects payments received but not yet earned. As work is completed and performance obligations are satisfied, the deferred revenue balance is released to service revenue. Contracts completed during the month should not carry a remaining deferred revenue balance at the close.

The monthly reconciliation also surfaces the full-job revenue picture described above: when a $5,000 deposit is released and $15,000 of additional revenue is recognised simultaneously, both entries belong in the same period and the accounts-receivable balance should reflect the $15,000 still outstanding from the customer.

How Inkle helps

Inkle Books maintains the deferred revenue balance as part of the monthly close. Advance payments received are recorded as liabilities and released to revenue as the underlying performance obligations are satisfied. This keeps the income statement accurate across periods and the balance sheet current, with deferred revenue reflecting only obligations still outstanding at the closing date.

Inkle Tax prepares federal, state, and franchise tax filings from the same ledger. Because the financial reporting treatment and the applicable tax method can produce different timing for the same advance payment, the tax preparation process accounts for both rather than assuming they align automatically.

Inkle handles bookkeeping and tax for owner-operated businesses across the US. See how it works or book a demo to talk through what your business needs.