OpenTable's 2% Service Fee on No-Shows and Deposits: A Restaurant Guide to Booking and Reconciling Payouts

You started requiring reservation deposits to stop losing money on empty tables. Now the reservation platform takes a 2% cut of the very fees that were supposed to protect you. A $50-per-person no-show charge on a party of four is $200 — except only $196 reaches your bank account, and if your books say $200, that phantom $4 multiplies across every deposit, every penalty, every prepaid event until your revenue no longer ties to your bank balance.

Here is how the fee works, whether you should absorb it or pass it to diners, and how to reconcile OpenTable payouts so your books reflect what you actually collected.

What the 2% Fee Actually Applies To​

Early in 2026, OpenTable began adding a 2% service charge on money that moves through its online payments system: no-show penalties, booking deposits, and prepaid dining experiences such as ticketed holiday events. Ordinary reservations — a guest simply booking a table — are not surcharged to the diner; restaurants continue to pay for the platform itself under their service agreement.

Three details matter for your books:

• Restaurants choose who pays. By default the restaurant absorbs the 2%. In the United States, OpenTable lets you flip a toggle to pass the fee to the guest instead.
• The choice is granular. The toggle lives at the level of each cancellation policy and each prepaid experience. You can absorb the fee on ordinary weekend bookings while passing it through on a high-value New Year's Eve tasting menu.
• It rolled out in waves. OpenTable described it as an overhaul reaching most U.S. restaurants in the second half of 2025 with the remainder following in early 2026 — so if you have not seen it yet, check your statements before assuming you are exempt.

Absorb It or Pass It Through? Run the Real Math First​

The decision looks trivial until you scale it. Consider a restaurant that collects a $25-per-person deposit on Friday and Saturday nights, averaging 40 deposit-backed covers per weekend — roughly 160 covers a month:

• Monthly deposit volume: $4,000
• 2% platform fee: $80 per month, $960 per year

That is the absorb case: just under $1,000 a year in new expense for one policy. Now add a $50-per-person no-show penalty collected ten times a month ($500), plus two prepaid wine dinners a quarter at $150 a head for 30 guests ($9,000 per event). The annual fee across all three streams lands near $1,500. Not fatal — but not nothing on restaurant margins, and it stacks on top of everything else you already pay OpenTable.

Passing the fee through avoids the cost but creates its own work:

• Disclosure becomes your job. A deposit advertised at $25 that charges $25.50 breeds chargebacks and one-star reviews if the extra fifty cents is a surprise. State the total, inclusive of fees, wherever the deposit is described — your website, the confirmation email, the cancellation policy page.
• Your refund math changes. When you refund a deposit to a guest who cancels inside the allowed window, decide in advance whether the passed-through fee is refunded too, and write that into the policy. Refunding it costs you the 2%; keeping it confuses guests. Either is defensible; ambiguity is not.
• Card processing may sit on top. Depending on how your payments are set up, the card processor's own percentage can apply to the total the guest pays — including any passed-through platform fee. Pull one real payout and trace every deduction line before you set prices, rather than assuming the 2% is the only haircut.

A sensible default for most independents: absorb the fee on standard deposits where the dollar amounts are small and goodwill matters, and pass it through on large prepaid events where the fee per ticket is material and guests already expect ticketing-style service charges.

Know Your Full OpenTable Cost Stack​

The 2% fee is one line in a stack that many operators never total up. A typical setup includes:

• Subscription: published tiers run from a $39-per-month Basic plan through $299 Core to $499 Pro, plus custom enterprise quotes.
• Per-cover fees: around $1.50 for each diner seated through OpenTable's own network, and a smaller charge (roughly $0.25 per cover or a flat monthly amount) for reservations made through your own website widget.
• Experiences and takeout: a 2% service fee already applied to prepaid experiences and takeout orders on published plans.
• The new 2%: on deposits, no-show penalties, and prepaid experiences under the 2026 overhaul.

Note what is not charged: cover fees apply to seated diners only, so a no-show that triggers a penalty does not also attract a per-cover fee. When you reconcile, that is one of the first things to verify — a seated-cover charge attached to a party that never arrived is an error worth disputing.

Add the stack up quarterly. Operators re-examining the total sometimes find that direct bookings through their own website — driven by Google, Instagram, or regulars — are paying per-cover marketplace fees for traffic they generated themselves. The fix may be marketing strategy rather than bookkeeping, but you cannot make that call without the numbers.

Book It Right: Gross vs. Net​

This is where restaurant books most often go wrong. The rule is simple: record the gross amount, then record the fee as its own expense. Never book the net payout as revenue.

Walk through a $100 deposit for a party of two, with the restaurant absorbing the 2%:

1. When the deposit is collected, it is not revenue yet — the meal has not been served. Record $100 as cash with an offsetting $100 deposit liability (a liability account like "Reservation Deposits Held").
2. Record the platform fee when it appears on the payout report: $2 to a "Reservation Platform Fees" expense account. Do not net it against the liability — the guest still has a $100 credit toward their meal.
3. When the party dines, move the $100 from liability to food-and-beverage revenue, and apply it against their check as the deposit terms specify.
4. When a guest no-shows and the deposit is forfeited, move the $100 from liability to revenue — many operators use a separate "No-Show and Cancellation Fees" revenue line so they can see exactly how much of their income is penalties. The $2 fee stays as expense.

If you pass the fee to the guest, the guest pays $102. Book the $100 deposit exactly as above, and book the extra $2 consistently — either as a reduction (contra-expense) to the platform-fee expense account or as fee revenue. Pick one treatment and stick with it all year; flipping mid-year makes the fee line meaningless for comparison.

Keep platform fees in their own expense account, separate from credit card processing fees. Lumping them together hides whether a rising "fees" line is your processor raising rates or your deposit program growing — two problems with opposite solutions.

The Monthly Payout Reconciliation Workflow​

Set aside thirty minutes after month-end and work this checklist:

1. Export the platform report. Pull OpenTable's payout or transaction report for the month, showing each deposit collected, each no-show charge, each refund, and each fee deducted.
2. Match payouts to the bank. Every deposit in your bank account from OpenTable should tie to one or more lines on the platform report. List any bank deposit with no matching report line, and any report payout that never arrived.
3. Verify the 2% arithmetic. Multiply each fee-bearing transaction by 2% and confirm the deducted fee. Platforms reconfigure fee settings during plan changes and feature rollouts; a wrong toggle on one experience can bleed for months.
4. Tie each transaction to a reservation record. For every no-show charge, confirm the party is marked no-show in the reservation book — not seated (which would mean a cover fee applies instead) and not cancelled inside the free window (which means the charge should not exist at all).
5. Process refunds and chargebacks. Match each refund on the platform report to a reservation record and to the bank. A refunded deposit must come out of the liability account, not out of revenue — refunding out of revenue double-counts the loss.
6. Review the fee totals against budget. Compare total platform fees — subscription, cover fees, and the 2% charges — to the prior month and to the same month last year. Investigate any jump before closing the books.

Six steps, once a month, and the phantom-revenue problem disappears.

Five Mistakes That Corrupt Restaurant Books​

• Booking net payouts as revenue. Recording $98 instead of $100 of revenue plus $2 of expense understates both lines and makes margins look better than they are.
• Burying platform fees in processing fees. One combined "fees" account conceals which vendor is getting more expensive.
• Treating forfeited deposits as a wash. A kept $100 deposit with no corresponding revenue entry leaves a stale liability on the balance sheet that grows forever.
• Forgetting the tax side of passed-through fees. Money you collect from guests and keep — including passed-through fee amounts you do not refund — is part of your gross receipts. Record it; do not treat it as an invisible reimbursement.
• Confusing service charges with tips on the payroll side. If you add an automatic gratuity or service charge to checks, the IRS treats amounts you impose on the customer as service charges — generally wages that run through payroll with withholding — not tips. That is a separate issue from OpenTable's fee, but restaurants that tighten up one part of their fee handling usually discover the other needs attention too.

Are Deposits Still Worth It After the Fee?​

For most restaurants taking deposits, yes — the math is lopsided. Industry data cited around the rise of deposit policies suggests more than one in four diners admits to having ghosted a reservation, and high-end rooms now commonly secure bookings with deposits up to $50 per person. A single saved four-top on a Saturday night covers months of 2% fees. Deposits also deter reservation scalping bots that hoard prime tables, a problem that has grown alongside online booking.

Put numbers on it: if your no-show rate was 5% on 1,000 monthly covers at a $60 average check, no-shows cost roughly $3,000 a month in lost revenue. Cutting that rate to 2% with deposits recovers about $1,800 — against platform fees measured in the tens of dollars. The fee deserves tracking, not fear.

Revisit the policy twice a year. If a deposit tier generates more complaints and refunds than the no-shows it prevents, narrow it to peak nights and large parties rather than abandoning it. Let the per-policy toggle do the work it was built for.

Keep Your Books as Tight as Your Reservation Book​

Reservation platforms keep adding fee types — cover fees, experience fees, and now a 2% charge on the deposits and penalties that protect your dining room. Each one is small; together they decide whether your profit-and-loss statement describes reality. Recording every deposit at gross, giving platform fees their own expense line, and reconciling each payout against the reservations behind it turns a growing fee stack from a slow leak into a managed cost.

As you tighten up reservation revenue, maintaining clear financial records across the whole operation is what makes the monthly review possible. Beancount.io provides plain-text accounting that gives you complete transparency and control over your financial data — no black boxes, no vendor lock-in. Get started for free and see why developers and finance professionals are switching to plain-text accounting.