Restaurant Reservation Deposits and No-Show Fees: The Deferred Revenue Guide

A party of eight books your best table on a Saturday night, you turn away three other groups to hold it, and then nobody shows up. No call, no text, no table. Multiply that by a few times a month and you're not looking at an annoying inconvenience — you're looking at real, recurring revenue loss. Industry estimates put the cost of restaurant no-shows at roughly $16 billion a year across the U.S. alone.

That's why reservation deposits have gone from a white-tablecloth curiosity to a mainstream tool at everything from tasting-menu destinations to neighborhood bistros with a popular brunch. But charging a deposit creates a bookkeeping problem most restaurant owners never anticipated: that money isn't revenue the moment it hits your bank account. And when a guest doesn't show up, the accounting for what happens to their deposit is more nuanced than "we keep it, so it's income."

Get this wrong and you'll misstate your monthly P&L, overpay estimated taxes on cash you may have to refund, or — worse — get flagged in an audit for recognizing revenue before you've actually earned it.

Why Restaurants Are Charging Deposits in the First Place​

The logic is straightforward: when a reservation costs a diner nothing, it costs them nothing to skip it. Platforms that require a card on file or an upfront deposit see dramatically lower no-show rates — some report figures around 1–2%, versus an industry norm closer to 15–20% for reservations with no financial commitment attached.

Typical deposit structures fall into a few patterns:

• Casual dining (average check $40–$70 per person): $10–$25 per person, mainly to filter out low-intent bookings.
• Premium dining (average check $100+): $25–$50 per person, or sometimes a flat per-table minimum.
• Large parties, private rooms, and peak periods (holidays, Valentine's Day, prix-fixe events): 30–50% of the expected bill, or a fixed deposit in the hundreds of dollars.

The deposit typically works one of three ways once the guest arrives or doesn't:

1. Applied to the bill — the diner shows up, and the deposit is credited toward their check.
2. Refunded on cancellation — if the guest cancels within a stated window (48 hours is common), some or all of the deposit comes back.
3. Forfeited on no-show — if the guest doesn't cancel and doesn't show, the restaurant keeps the deposit, provided the policy was clearly disclosed and agreed to at the time of booking.

That third scenario is where the accounting gets interesting.

Deferred Revenue: The Deposit Isn't Yours Yet​

The moment a guest pays a $50 deposit for a table next Friday, you have their cash — but you haven't earned it. Under standard accrual accounting (and under ASC 606, the revenue recognition framework that governs how U.S. businesses record income), a prepayment for a future service is a liability, not revenue. Accountants call this deferred revenue or a contract liability.

Here's the entry when the deposit is collected:

Debit:  Cash                          $50
Credit: Deferred Revenue (liability)  $50

Notice what's missing: no revenue account is touched yet. That's the point. You're holding the guest's money in trust against a future obligation — seating them and serving them a meal.

When the guest shows up and dines, you reverse the liability and recognize revenue, typically netted against their actual bill:

Debit:  Deferred Revenue    $50
Credit: Food & Beverage Revenue   $50 (as part of the full ticket)

If a restaurant instead recorded every deposit as revenue on the day it was collected, its monthly P&L would swing wildly based on how many future reservations happened to be booked that month — completely disconnected from how many guests actually walked through the door and were served. That's exactly the kind of premature revenue recognition that makes a bookkeeping system (and a set of financial statements) unreliable.

What Happens When the Guest Doesn't Show: Breakage Accounting​

Forfeited no-show deposits are conceptually similar to unredeemed gift card balances — an area accountants have a well-established term for: breakage. Breakage is the portion of a prepaid, deferred-revenue balance that a business ultimately gets to keep because the customer never claims the underlying good or service.

Once a no-show is confirmed and your stated cancellation window has closed without a legitimate exception, the deposit converts from a liability into earned revenue:

Debit:  Deferred Revenue         $50
Credit: No-Show / Forfeited Deposit Revenue   $50

Two things matter here for keeping your books defensible:

1. Track forfeited deposits separately from food and beverage sales. Don't just dump no-show revenue into your regular sales account. A distinct "forfeited deposit revenue" or "cancellation fee income" line lets you (and your accountant, and if it ever comes to it, an auditor) see at a glance how much of your top line came from tables you never actually served. This also matters for sales tax — a forfeited deposit for a service never rendered is often not subject to sales tax the way a meal is, depending on your state, so commingling the two can create a tax liability you don't actually owe.

2. Don't recognize the forfeiture before the cancellation window closes. If your policy gives guests until 6 p.m. the day of the reservation to cancel with a partial refund, the deposit is still a liability at 5:59 p.m. Recognizing it as revenue earlier — say, at the moment of booking — overstates income in whatever period you happened to collect the cash, and understates it in the period the no-show actually occurred.

For restaurants running a high volume of deposit-based bookings (a popular brunch spot, a holiday prix-fixe program, a private events calendar), it's worth estimating a breakage rate — the percentage of deposits you expect to forfeit based on historical no-show data — the same way large gift card issuers estimate what percentage of card balances will never be redeemed. That lets you recognize a portion of expected breakage revenue on a rolling basis rather than waiting for each individual no-show to be confirmed, which smooths your monthly numbers and better reflects economic reality.

Reconciling Deposits Across Reservation Platforms​

If you're taking deposits through OpenTable, Resy, or Tock rather than directly, there's a second layer of bookkeeping most owners underestimate: the deposit that hits your books isn't the deposit the platform actually charged the guest.

These platforms typically:

• Charge a payment processing fee on the deposit itself
• Deduct their own per-cover or subscription fees from your payout, sometimes on a delayed schedule
• Batch multiple nights' worth of deposits, refunds, and forfeitures into a single periodic payout

That means your bank deposit for "Tuesday's payout" is a net figure that already has fees and refunds baked in — not a clean 1:1 match to the deposits your reservation system shows as collected that week. Reconciling this properly means:

1. Pulling the platform's itemized transaction report (not just the net payout amount)
2. Recording the gross deposit as deferred revenue, the platform fee as a separate expense, and any refunds as reversals — rather than just booking whatever number landed in your bank account
3. Doing this reconciliation at least weekly, since deposit forfeiture disputes (a guest claims they cancelled in time; your system shows they didn't) are much easier to resolve with a fresh paper trail than a month-old one

Skipping this step is how restaurants end up with a deferred revenue balance on their books that quietly drifts out of sync with what guests are actually owed — a liability account nobody is watching, until a guest disputes a charge and there's no clean record to point to.

Why This Matters Beyond Just "Getting the Books Right"​

Beyond avoiding an accounting headache, tracking deposits correctly gives you real operating data: how much of your revenue depends on service you actually deliver versus penalty fees, whether your no-show rate is trending up or down after a policy change, and whether a given platform's fees are eating more of your deposit revenue than it's worth. None of that is visible if forfeited deposits are buried inside your general sales total.

Clear, auditable records also matter the moment a guest disputes a forfeited deposit with their credit card company — a chargeback you can only win with a documented policy, a timestamped booking confirmation, and books that show exactly when the liability converted to revenue and why.

Keep Your Restaurant's Books as Organized as Your Reservation Book​

Deposits, forfeitures, and platform-fee reconciliation are exactly the kind of layered, easy-to-get-wrong bookkeeping that benefits from records you can actually audit line by line. Beancount.io offers plain-text accounting that keeps every deferred revenue entry, forfeiture, and platform fee transparent and version-controlled — no black box, no proprietary lock-in, just a ledger you and your accountant can both read. Get started for free and bring the same precision to your books that you bring to your dining room.