Advance Payments and Deferred Revenue: When Cash Isn’t Income
- A worked example: an annual contract
- Advances for goods
- Why it matters beyond compliance
- Common mistakes
- A simple deferred revenue schedule
- More complex contracts
- Where this fits
When a customer pays before you have delivered the goods or service, the money is not yet income. It is an obligation: you owe the customer either the delivery or a refund. In the accounts it is recorded as a liability, usually called deferred revenue, unearned revenue or advances from customers, and moved into revenue as you actually deliver. A business that books upfront payments straight to sales overstates its revenue and profit in the month the cash arrives and understates them in the months it does the work.
This guide covers the principle and the entries. It does not deal with when tax is payable on advances, which follows separate rules.
A worked example: an annual contract
On 1 July, a customer pays ₹1,20,000 for a 12-month maintenance contract, running July to June. The business’s financial year ends on 31 March. Amounts here exclude any tax charged on the invoice.
Service is delivered evenly over the year, so ₹10,000 is earned each month.
On receipt, 1 July
| Account | Debit | Credit |
|---|---|---|
| Bank | ₹1,20,000 | |
| Deferred revenue (liability) | ₹1,20,000 |
At the end of each month
| Account | Debit | Credit |
|---|---|---|
| Deferred revenue | ₹10,000 | |
| Service revenue | ₹10,000 |
Position at the year-end, 31 March
| Amount | |
|---|---|
| Cash received | ₹1,20,000 |
| Revenue for July to March, 9 months | ₹90,000 |
| Deferred revenue still owed, April to June | ₹30,000 |
Illustrative figures.
This year’s profit and loss shows ₹90,000 of revenue. The balance sheet shows a liability of ₹30,000, which becomes next year’s revenue as the last three months of service are delivered.
Advances for goods
The same logic applies when a customer pays a deposit on an order. The deposit sits in an advances from customers account until the goods are delivered and the sale is recognised. At that point the advance is set against the customer’s invoice.
If the order is cancelled and the money refunded, the advance is simply reversed against the bank. It never passed through revenue, so profit is unaffected, which is exactly right.
Why it matters beyond compliance
It shows real performance. A software or services business that collects annual fees upfront can look spectacular in the month of renewals and loss-making in the months between. Deferring revenue gives a steady, accurate picture of what was actually delivered.
It shows what you still owe. Deferred revenue is work you have been paid for and have not yet done. If the business closed tomorrow, customers would expect that money back. A large and growing deferred revenue balance is good news about demand and a reminder of commitments.
It explains cash and profit moving apart. A business collecting annual fees in advance can hold far more cash than its profits suggest. The difference is the deferred revenue. Spending that cash as though it were profit is a common way for growing service businesses to run into trouble.
Common mistakes
- Booking the whole receipt as sales and never adjusting it.
- Releasing revenue on a schedule that does not match delivery. If a setup service is delivered in the first month and support over the rest of the year, the revenue pattern should follow that, not a straight line by default.
- Forgetting the release entries. A recurring monthly journal, or the software’s deferred revenue feature, prevents this.
- Netting advances against receivables from other invoices, which hides both figures.
- Not reconciling the balance. At each month-end, the deferred revenue balance should equal a list of individual contracts and the unexpired portion of each.
A simple deferred revenue schedule
For each contract, keep one row with the customer, the contract start and end dates, the total amount, revenue released to date and the balance remaining. The total of the balance column must agree with the deferred revenue account in the ledger. A spreadsheet is fine for a small number of contracts; accounting or billing software with a subscription feature is better once there are dozens.
The schedule also answers practical questions quickly. How much of next year’s revenue is already secured? Which contracts expire in the next quarter and need renewal conversations? If a customer cancels part-way and asks for a refund of the unused period, what is the unexpired amount? A business that keeps the schedule current can answer all three in minutes, and its month-end revenue figure can be trusted.
More complex contracts
Contracts that bundle several elements, such as hardware, installation and a year of support for one price, raise the question of how much of the price belongs to each element and when each is delivered. The applicable accounting standards set out how to allocate the price: Ind AS 115, Revenue from Contracts with Customers, does so in detail for companies on Ind AS, while AS 9, Revenue Recognition, which most other businesses follow, gives only limited guidance. For those contracts, agree the approach with your accountant before the first invoice goes out, because unpicking it later is much harder.
Where this fits
- The principle behind it: accrual vs cash accounting
- The expense-side equivalent: prepaid and accrued expenses
- Setting up the right ledger: chart of accounts setup
- Why cash and profit differ: how to read a cash flow statement