Deferred revenue accounting: entries and schedule

Deferred revenue: the short answer

Deferred revenue, also called unearned revenue, is money a business has received or invoiced for goods or services it has not yet delivered. It is recorded as a liability, not as income, and is released to revenue as the business performs. It matters because recognising cash received in advance as revenue overstates profit and hides an obligation to deliver or refund.

Under IFRS 15 Revenue from Contracts with Customers the balance is called a contract liability: an entity's obligation to transfer goods or services to a customer for which it has received consideration, or for which consideration is due (IFRS 15 para 106). Subscriptions, annual maintenance, software licences with updates, gift cards, customer deposits, season tickets and prepaid training courses all create it. This guide covers the entries, a worked monthly release schedule, the harder cases and how to keep the account reconciled.

Why deferred revenue is a liability

Revenue under IFRS 15 is recognised when, or as, the entity satisfies a performance obligation by transferring control of goods or services. Receiving cash is not a performance obligation. Until the service is delivered, the business owes the customer something: the service itself, or the money back if it cannot deliver. That obligation meets the Conceptual Framework definition of a liability.

The timing of the invoice matters for presentation. If a business invoices a non-cancellable annual contract that is due for payment before the service starts, it has an unconditional right to the cash and records a receivable and a contract liability together. If the contract is cancellable and nothing is yet due, many entities record nothing until the customer pays. Either way, revenue waits for performance.

Deferred revenue is normally a current liability because most contracts are delivered within twelve months. The part that will be earned more than twelve months after the reporting date is presented as non-current.

Basic journal entries for an annual subscription

A software company invoices a customer on 1 January for a twelve-month subscription of EUR 12,000 plus 20% VAT. VAT is not revenue and is not deferred: in most VAT systems it becomes payable on the invoice or payment, so it goes straight to the VAT account. Only the net amount is deferred. The service is delivered evenly over the year, so revenue is recognised straight-line at EUR 1,000 a month.

• 1 January, invoice: Dr Trade receivables 14,400 / Cr Contract liability (deferred revenue) 12,000 / Cr VAT payable 2,400.
• 15 January, customer pays: Dr Bank 14,400 / Cr Trade receivables 14,400.
• 31 January and every month end: Dr Contract liability 1,000 / Cr Subscription revenue 1,000.
• After twelve releases the contract liability is zero and EUR 12,000 of revenue has been recognised across the year.
• Balance sheet at 31 March: contract liability 12,000 - 3,000 = 9,000.

Worked example: a monthly release schedule

In practice a business has many contracts starting on different dates and billed on different cycles, so it keeps a deferred revenue schedule, one row per contract and one column per month, that drives the monthly release journal and supports the balance sheet. The example has three contracts. Contract A is an annual EUR 12,000 subscription billed on 1 January, released at EUR 1,000 a month. Contract B is an annual EUR 6,000 subscription billed on 1 April, released at EUR 500 a month from April. Contract C is billed quarterly in advance at EUR 900, covering March to May, then June to August, released at EUR 300 a month.

Each month the roll-forward is: opening balance, plus new billings, minus revenue released, equals closing balance. Over the six months billings total EUR 19,800 and releases total EUR 8,700, leaving EUR 11,100 deferred at 30 June. That closing balance can be proved from the contracts: six months of A (6,000), nine months of B (4,500) and two months of C (600).

• January: opening 0 + billings 12,000 (A) - released 1,000 = closing 11,000.
• February: opening 11,000 + billings 0 - released 1,000 = closing 10,000.
• March: opening 10,000 + billings 900 (C) - released 1,300 (A 1,000, C 300) = closing 9,600.
• April: opening 9,600 + billings 6,000 (B) - released 1,800 (A 1,000, B 500, C 300) = closing 13,800.
• May: opening 13,800 + billings 0 - released 1,800 = closing 12,000.
• June: opening 12,000 + billings 900 (C renewal) - released 1,800 = closing 11,100.
• Six-month totals: billings 19,800, revenue 8,700, closing deferred revenue 11,100.

Mid-month starts, daily proration and multi-year contracts

Contracts rarely start on the first of the month. Businesses choose a proration convention and apply it consistently: daily proration, a half-month convention, or start-of-next-month. Daily proration is the most accurate. A EUR 12,000 annual contract starting on 16 January, over a 365-day term, earns 12,000 x 16 / 365 = EUR 526.03 in January (16 days from the 16th to the 31st inclusive). The same contract under a full-month convention would earn EUR 1,000 in January, overstating revenue by almost half a month.

Multi-year prepayments need two extra checks. First, the split between current and non-current: a three-year contract of EUR 36,000 paid upfront has EUR 24,000 remaining after year one, of which EUR 12,000 is current and EUR 12,000 non-current. Second, a significant financing component: when payment and performance are far apart, IFRS 15 requires the transaction price to be adjusted for the time value of money. The practical expedient in IFRS 15 para 63 lets an entity ignore this when the period between payment and transfer is one year or less, so for most annual subscriptions no adjustment is needed.

Gift cards, loyalty points and upfront fees

Gift cards and prepaid vouchers are contract liabilities until redeemed. Many are never fully used, which is called breakage. If the entity expects to be entitled to a breakage amount, IFRS 15 recognises it as revenue in proportion to the pattern of rights the customer exercises; if it does not expect breakage, it recognises it only when the likelihood of the customer exercising the remaining rights becomes remote. Where unclaimed balances must be handed to a government under unclaimed property laws, that part is a liability, not breakage revenue.

Loyalty points that give a material right are a separate performance obligation. Part of the sale price is allocated to them using relative stand-alone selling prices. If a EUR 1,000 sale earns points with a stand-alone value of EUR 50 and the goods' stand-alone price is EUR 1,000, the allocation is 1,000 x 1,000 / 1,050 = EUR 952.38 to the goods and 1,000 x 50 / 1,050 = EUR 47.62 deferred for the points, released as they are redeemed.

Non-refundable upfront fees, such as joining, activation or set-up fees, rarely count as revenue on day one. Unless the fee relates to a distinct good or service transferred at the start, it is an advance payment for future services and is deferred over the period the customer is expected to benefit, which can include expected renewals.

Deferred revenue compared with related balances

Several balances sit near deferred revenue on a balance sheet and are often confused. The distinction is always the direction of the timing difference and which party owes the other.

• Deferred revenue (contract liability): cash received or due before performance; a liability.
• Accrued revenue (contract asset or unbilled receivable): performance delivered before the right to invoice; an asset.
• Trade receivable: an unconditional right to consideration, only the passage of time before payment is due; an asset.
• Customer deposit: an advance that may be refundable; a liability until applied or returned.
• Refund liability: consideration the entity expects to refund, for example on returns; a liability separate from the contract liability.
• Prepaid expense: the buyer's side of deferred revenue; an asset in the customer's books.
• Deferred income from government grants: a liability under IAS 20, not IFRS 15.

Reconciling the deferred revenue account

The deferred revenue balance in the general ledger should equal the total of the unexpired amounts in the contract schedule at every month end. Differences usually come from manual invoices that were posted straight to revenue, cancellations and refunds that were not reflected in the schedule, or release journals posted for the wrong amount. Our guide on balance sheet reconciliation explains the general approach; for deferred revenue, a few specific checks catch most errors.

Tax treatment of advance payments differs by country and can be earlier than the accounting release, which creates temporary differences and deferred tax. Keep the tax schedule separate from the IFRS schedule rather than bending one to fit the other.

• Agree the closing ledger balance to the schedule total, contract by contract where the balance is material.
• Look for negative balances on any contract, which mean revenue was released beyond what was billed.
• Test that cancelled contracts have had their remaining balance reversed or refunded.
• Scan the revenue account for invoices billed in advance but posted directly to revenue.
• Check that the current and non-current split was recalculated at the reporting date.

Deferred revenue in Skyline Nexus ERP

In Skyline Nexus ERP a final sale posts to revenue when sales auto-posting is switched on, with the revenue account chosen by the default mapping or by the product category's GL Sales Account. Revenue invoiced in advance is then deferred with a manual journal: at month end, a journal moves the unearned part from revenue to a contract liability account, and the monthly release is posted from the schedule kept alongside it. A journal must balance before it can be saved, and above the approval threshold it goes to an approver before posting.

Two features keep this manual process safe. Fiscal periods can be soft-closed or locked, so a release journal cannot be backdated into a month that has already been reported. The Trial Balance in Opening / Movement / Closing mode, and the General Ledger report for the contract liability account, give the figures to agree to the deferral schedule each month, and posted journals are corrected by reversal with a full Audit Trail.

Common mistakes with deferred revenue

Deferred revenue errors tend to inflate profit in the period cash arrives and depress it later, which is why auditors test cut-off on advance billings closely.

• Recognising an annual subscription as revenue in the month it is invoiced.
• Deferring the VAT along with the net amount instead of posting it to the VAT account.
• Treating non-refundable set-up fees as revenue on day one when no distinct service was delivered.
• Forgetting to reverse the deferred balance when a contract is cancelled or refunded.
• Presenting multi-year deferred revenue entirely as current.
• Recognising gift card breakage before there is evidence of the redemption pattern.
• Letting the ledger balance drift from the contract schedule without a monthly reconciliation.