In plain words
A hotel collects deposits months before wedding banquets, refundable until a cutoff date. No revenue arises on receipt; the deposits are contract liabilities. Before the cutoff, refunds expected across a portfolio of similar bookings, based on past cancellations, are shown as a refund liability; a single large booking uses its most likely outcome instead. Revenue is recognised when the event takes place, or when a forfeit is confirmed.
Why it matters
Confusing a refundable deposit (a financial refund liability, not revenue) with a non-refundable contract liability leads to premature revenue recognition and understated liabilities, while failing to track cancellation windows means the balance sheet does not reflect real obligations to refund guests, both errors are frequent in banquet/wedding businesses with multi-month deposit and tiered cancellation cycles.
Diagnostic questions
What is the specific cancellation policy attached to each deposit, fully refundable, partially refundable up to a cutoff date, or non-refundable, and is that policy correctly reflected in how the deposit is recorded? Is the deposit still held as a contract liability, or has a portion already become variable consideration the hotel is entitled to keep because the relevant contingency has lapsed? For group bookings or weddings with milestone payment schedules, are deposits tracked and reconciled against the eventual event date rather than recognized as revenue on receipt?
Recognition
- On receipt of any deposit, first classify it by its cancellation terms in force at that date: fully refundable, partially refundable up to a cutoff date, or non-refundable.
- Record the full deposit received as a contract liability (deferred revenue) on receipt, do not recognize any revenue at this point regardless of refundability, since the service (room-nights or event) has not yet been performed.
- Separately assess, at each reporting date before the cutoff date, whether a refund liability should be recognized for the portion of deposits expected to be refunded. For a large portfolio of similar bookings, estimate it with the expected value method using historical cancellation experience; for a single significant booking, the most likely amount method usually predicts better, giving either no refund liability (cancellation not expected) or the full refundable amount (cancellation expected), not a probability-weighted fraction. The refund liability sits alongside, not instead of, the contract liability until resolved.
- As cancellation deadlines pass without cancellation, reduce/release the refund liability estimate since the amount becomes effectively non-refundable.
- On the event/stay date, recognize revenue for the full transaction price (net of any confirmed refund) as the performance obligation is satisfied, releasing the remaining contract liability.
- If the client cancels within a window that forfeits the deposit (non-refundable at that point), recognize the forfeited amount as revenue (or breakage, if governed by an expected-non-exercise pattern) at the point forfeiture is confirmed, not before.
- If the client cancels within a refundable window, reverse the contract liability and recognize the refund payable/paid, no revenue is recognized.
- Maintain a rollforward of deposits and refund liabilities by booking to support reporting-date judgments, especially for group/wedding bookings with milestone payment schedules.
Measurement
Measure the contract liability at the amount of the deposit received. Measure the refund liability (where recognized) at the amount expected to be refunded, estimated for a portfolio of similar bookings using historical cancellation/refund rates segmented by booking type (individual room vs group vs banquet/wedding), lead time to the event, and cancellation policy tier (expected value method), or, for an individual significant booking, at the most likely amount (nil or the full refundable amount); the refund liability is a financial liability measured at the expected repayment amount, not a revenue estimate. Reassess both balances at each reporting date as cancellation deadlines pass, deposits are topped up per milestone payment schedules, or actual cancellation experience updates the estimate; for milestone/progress deposit schedules on weddings or group events, track each tranche's own refundability terms since different tranches may have different cutoff dates.
Presentation & disclosure
Present contract liabilities (advance deposits) separately from trade payables and from refund liabilities on the statement of financial position or in the notes; disclose the deposit and refund liability balances at each reporting date; disclose significant payment terms (deposit percentage, milestone schedule, cancellation tiers) for material booking categories; disclose the contract liability rollforward (opening balance, additions, amounts recognized as revenue, amounts refunded/released, closing balance) and the timing expectation for revenue recognition (typically within 12 months for hospitality bookings); disclose the basis and key assumptions used to estimate refund liabilities.
Common mistakes
- Recognizing deposit revenue on receipt rather than on performance of the room-nights or event
- netting refundable and non-refundable deposits into a single balance without distinguishing the refund liability
- failing to release forfeited deposits to revenue when a guest cancels outside the refund window (leaving stale contract liabilities on the books)
- treating a cancellation fee automatically as an IAS 37 provision instead of assessing it under the IFRS 15 refund liability / contract liability model, since the obligation arises from a contract with a customer
- not tracking milestone deposit tranches separately, so an early (refundable) tranche and a later (non-refundable) tranche get the same treatment.
Simple example
A hotel in Riyadh holds deposits of SAR 50,000 each for 40 wedding banquets (SAR 2,000,000 in total) scheduled over the next four months, each refundable in full up to 30 days before the event and non-refundable thereafter. On receipt (cumulative): Dr Cash 2,000,000 Cr Contract liability – advance deposit 2,000,000 At the reporting date all 40 bookings are still within the refundable window. Historical experience for similar wedding bookings shows about 5% are cancelled within the window, so for this portfolio the hotel applies the expected value method: SAR 2,000,000 x 5% = SAR 100,000. Dr Contract liability – advance deposit 100,000 Cr Refund liability 100,000 (This reclassifies SAR 100,000 within liabilities; no revenue is recognized.) Three bookings are later cancelled within the window and SAR 150,000 is refunded: Dr Refund liability 100,000 Dr Contract liability – advance deposit 50,000 Cr Cash 150,000 The remaining 37 bookings pass their cutoff dates and the events are held as planned: Dr Contract liability – advance deposit 1,850,000 Cr Banquet revenue 1,850,000 By contrast, for a single SAR 500,000 wedding deposit with a 5% cancellation likelihood, the most likely amount is no refund, so no refund liability is recognized; a SAR 25,000 (5%) liability would describe neither possible outcome.
Professional judgment
Estimating an appropriate refund liability for partially refundable deposits close to a cutoff date, and distinguishing genuine contract liabilities from amounts that have already effectively become non-refundable fees, requires ongoing judgment as cancellation windows lapse. Key judgment drivers: how representative historical cancellation rates are for a specific segment (weddings and large corporate events can have very different, and often lower, cancellation rates than transient room bookings); whether a client relationship or informal practice of granting exceptions (e.g., goodwill refunds outside contractual terms) should be factored into the refund liability estimate even though not contractually required; how to sequence multiple deposit tranches with different cutoff dates within a single booking; and whether a group of bookings is large and homogeneous enough for the expected value method, or whether an individual significant booking should be assessed at its most likely outcome.
Source basis
IFRS 15 / IAS 37 · Revenue from Contracts with Customers / Provisions, Contingent Liabilities and Contingent Assets
Paragraph references
Verified against the official standard texts used in the IFRS Expert skill.
Related issues
Educational and navigation content only. Not professional advice. Does not reproduce official IFRS/IAS text. Consult the authoritative standards and qualified professionals; professional judgment may still be required.