Restaurant advance payment policy in India: how much to charge, how to refund

Every restaurateur in India knows the scenario: a 20-guest birthday booking for Saturday night, confirmed over WhatsApp, menu discussed, tables blocked. Then nobody comes, the phone goes unanswered, and the food, the staffing and the turned-away walk-ins are all sunk cost. An advance payment is the standard Indian answer, and the country's top tables already use it: Indian Accent in New Delhi asks for ₹1,000 per guest to confirm a reservation, and Masque in Mumbai requires an advance deposit to confirm all tables.

The hard part is not deciding whether to take an advance. It is the policy around it: how much to charge for which bookings, how to collect it when card holds are not an option for most Indian restaurants, what the law actually says, and how to write a refund ladder that protects your revenue without burning a guest relationship. This guide covers all of it, with templates you can adapt. We build a free reservation system with no commission, so we spend a lot of time on exactly this problem; the advice below works whether or not you ever use our product.

One terminology note before we start. Guests will sometimes call it a token advance, and you may see "cover charge" used loosely. In India a cover charge is something else entirely: a minimum spend collected upfront and redeemed against the food and beverage bill, not a refundable deposit. This article is about the booking advance: an amount collected to confirm a reservation, adjusted against the bill when the party shows up, and partly or fully forfeited when it does not.

When should a restaurant take a booking advance?

Not for every table. An advance on a weekday deuce creates friction for no real protection. The cases where an advance earns its keep are the ones where an empty table genuinely hurts:

• Groups of 10 or more. A large table blocks a meaningful share of your covers, often needs extra staffing and advance prep, and is the hardest booking to backfill at short notice. This is the universal trigger, and the logic applies everywhere, as our global guide to large group bookings explains. In India the group booking is also where the cancellation usually arrives last minute, over the same WhatsApp thread the booking came from.
• Festive and peak nights. New Year's Eve is the extreme case: most metro venues sell prepaid packages outright rather than take open bookings. Diwali-week corporate dinners, Valentine's Day and wedding-season weekends all justify advances on bookings you would accept free on a normal Tuesday.
• Tasting menus and chef's counters. When the kitchen buys and preps per confirmed seat, a no-show is a direct food cost loss, not just lost revenue. This is why India's tasting-menu rooms were the first movers on deposits.
• Private dining and buyouts. A private room or full buyout is a booking you cannot partially recover; treat it like the event business it is, with a signed confirmation and a staged advance. Our guide to private dining and events covers the event side in detail.

For everything else, reminders and a clear cancellation policy do most of the work at much lower friction. We cover that full toolkit in our article on reducing no-shows in Indian restaurants.

How much advance should you charge?

There are two models that work in India, and plenty of restaurants run both at once: flat per-head for fixed menus, percentage slabs for group bookings.

Flat per-head advances

A flat amount per guest is simple to communicate and simple to refund. Indian Accent's published policy is the reference point: ₹1,000 per guest, adjusted against the bill, forfeited on cancellation under 24 hours or no-show. Scale the figure to your average per cover: an advance of roughly 25 to 50 percent of your APC (average per cover) is enough to make a guest think twice without feeling like a ransom. For a CDR (casual dining restaurant) with an APC of ₹800, that is ₹200 to ₹400 per head on the bookings that need one; a fine-dining room at ₹3,000 per cover can comfortably ask ₹1,000.

Percentage slabs for group bookings

For groups, a percentage of the estimated bill scales better than a flat fee. The most widely circulated Indian slab structure comes from DineCard's group booking guide, which is vendor guidance rather than law, but a reasonable starting grid:

• 10 to 15 guests: 30 percent advance, or a ₹500 per person minimum
• 16 to 30 guests: 50 percent advance, with the menu confirmed in writing
• 30+ guests: 50 to 100 percent advance, with a signed booking agreement

The same guide suggests firmer terms on peak days. Treat every number in a grid like this as a starting point to adapt to your format and city, not a standard: no Indian industry body has published one. One figure you will see quoted around this topic, a claim that large bookings without deposits see 15 to 25 percent no-show rates, is that vendor's own estimate; no published Indian no-show statistic from a primary source exists.

Whatever you choose, put a ceiling on it. An advance that approximates your real loss from an empty table is defensible; an advance engineered to profit from cancellations is not, legally or commercially.

Is a non-refundable advance legal in India?

Mostly yes, with two important qualifications, and one myth to clear up first: there is no Indian statute, no CCPA guideline and no published court ruling specifically on restaurant booking advances or no-show fees. Anyone telling you a specific law caps or bans them is wrong. What governs the advance is general contract and consumer law.

The anchor is Section 74 of the Indian Contract Act, 1872: when a contract names a sum payable on breach, the other party can recover reasonable compensation not exceeding that sum. The Supreme Court's reading in Kailash Nath Associates v. DDA (2015) is the one to internalise: a genuine pre-estimate of the damage, fixed by both parties, can be kept in full; a punitive amount far beyond any plausible loss can be cut down to reasonable compensation, and compensation generally presupposes that some actual loss occurred. A ₹500 per head advance forfeited when a Saturday table of 12 goes empty sits comfortably inside that; keeping a ₹50,000 advance when the guest cancelled ten days out and you resold the room does not.

The second layer is the Consumer Protection Act, 2019, which lets consumer commissions strike down unfair contract terms, including charges "wholly disproportionate" to the loss, and unfair trade practices. The lesson from the CCPA's service-charge enforcement is directly transferable even though it concerned a different charge: what regulators punished was charging by default, without disclosure or consent. Applied to advances, that means:

1. Disclose before confirmation. The amount, the cancellation cut-offs and the refund terms must reach the guest before they pay, in writing: a WhatsApp message, a line on the booking form, a policy on your booking page. A policy produced after the dispute protects nothing.
2. Keep it proportionate. Tie the forfeiture to the real loss window. Losing the full advance for a cancellation 15 minutes before the slot is fair; losing it for a cancellation a week out is hard to defend.

A disappointed guest's realistic escalation path is the National Consumer Helpline (1915) and then a District Consumer Commission, where filing is cheap. A written, proportionate, pre-disclosed policy is what wins that argument before it starts. For the general principles of writing cancellation terms, see our guide to restaurant cancellation policies.

How to collect the advance: UPI links, mandates and bank transfer

India's collection rails are different from the West's, and better in some ways. What you will not be using is the card-on-file hold that American and European restaurants lean on: since the RBI's card tokenisation rules took effect on 1 October 2022, merchants and gateways cannot store card numbers, so the classic "we keep your card and charge you if you no-show" flow is effectively out of reach for an independent Indian restaurant. We explain how card holds work elsewhere in our guide to credit card holds for reservations; in India, you build the policy on UPI instead.

UPI payment links: the default rail

The standard flow today: guest asks for a date on WhatsApp or the phone, you quote the advance and the terms, you send a payment link from Razorpay, Paytm or PhonePe for Business, and the booking is confirmed when the payment lands. The link gives you a timestamped record of the amount and an audit trail, which cash never does. Send the written terms in the same message as the link, so disclosure and payment are inseparable. This is exactly how the top end already operates: Indian Accent collects its per-guest advance through an online payment flow at booking time.

UPI one-time mandates: block now, debit later

The newer option is the UPI one-time mandate, productised by gateways such as Razorpay, Pine Labs, PayU and Cashfree: the amount (up to ₹1 lakh) is blocked in the guest's account rather than debited, and you capture it only if the no-show happens, or release it when the party arrives. It is the closest Indian equivalent of a card hold, the guest's money never actually moves unless the table goes empty, and it is the same mechanism Indians already know from IPO applications. It needs a gateway integration rather than a simple link, so today it is most practical for venues already running online payments, but it is where Indian no-show protection is heading.

Bank transfer, and the one rail to avoid

For weddings, corporate bookings and buyouts, companies will often insist on NEFT/IMPS transfer against a proforma invoice; that is fine, just slower, so set your confirmation deadline accordingly. The rail to avoid is cash: no trail, no proof of what was agreed, and the first thing a consumer commission will ask for is the paper.

Writing the refund ladder

A refund ladder is the heart of the policy: it converts "non-refundable" from a blanket threat into a fair, graduated schedule that tracks your actual ability to resell the table.

A template you can adapt

For a group booking of 10 or more:

Tighten the windows for peak nights (New Year's Eve packages are routinely non-refundable outright, and guests accept that) and loosen them for quiet weekdays. Three details make the ladder work in practice:

• The reschedule row matters most. A large share of group "cancellations" in India are really date changes for a family function that moved. Letting the advance travel to a new date, once, keeps the revenue and the relationship, and costs you almost nothing.
• Put a partial-show rule in writing. If 12 of 20 guests arrive, do you adjust the full advance against the bill or forfeit the per-head advance of the absentees? Either is defensible; silence is not.
• Refund fast when the ladder says refund. The service-charge crackdown started with refund complaints on the national helpline. A refund paid the same day via the same UPI rail is the cheapest dispute insurance there is.

Adjust the advance against the bill, visibly

When the party shows up, the advance should appear as a clearly labelled deduction on the final bill, and the guest should get a receipt for the advance at collection time, via WhatsApp or email, stating the booking date, party size and terms. An advance the guest cannot see coming off the bill feels like a hidden charge, which is precisely the pattern Indian consumer regulators have been punishing. And remember GST applies to the supply you actually make; your accountant will want advances and adjustments cleanly recorded, which is one more argument for links over cash.

Festive clustering: when advances stop being optional

The Indian calendar concentrates group demand brutally. Wedding-season dates cluster on muhurat days, so a handful of auspicious dates in November to February each carry several times a normal weekend's private-dining demand. Diwali week stacks corporate dinners into a fortnight. New Year's Eve in the metros and in Goa is sold as prepaid packages weeks in advance precisely because an empty table that night is unrecoverable. On these dates, an advance is not a defensive measure, it is the only rational way to allocate scarce capacity: the booking that pays an advance is the booking that is real. We cover the full seasonal playbook, including how to run prepaid ticketed nights without an aggregator, in our guide to festive season restaurant bookings in India.

Make the advance part of the booking flow, not a chore

Everything above works with a diary, WhatsApp and a payments app. The failure mode is operational: the advance that never got requested because service was busy, the terms that lived in one manager's chat thread, the double-booked muhurat Saturday.

This is the part a reservation system fixes. With ViteUneTable, the free version gives you an unlimited online reservation book with your own booking page (guest pages in 37 languages, useful in Goa and the metros), and custom questions at booking time, so a group request arrives with the headcount, occasion and menu preferences already captured, and your advance policy displayed before the guest confirms. You then collect the advance exactly as described above, with a UPI payment link sent from your own payments provider, and note it on the booking. The free version has 0% commission and no per-cover fees, permanently. The Standard pack at 29 € a month excluding tax (about ₹3,150 at October 2026 rates) adds automatic email reminders; the Anti No-Show pack at 49 € (about ₹5,300) adds a card guarantee through a bank imprint, which, given the RBI rules above, is most useful for premium venues and international guests who book with cards, and can cut no-shows by up to 95% where it applies. Let's be honest: ViteUneTable does not process UPI advances or mandates itself, and billing is in euros; for a mostly domestic clientele, the free reservation book plus your own UPI links is the combination to start with, and it costs nothing to try.

Frequently asked questions

How much advance should a restaurant take for a group booking in India?

A common starting grid: 30 percent of the estimated bill (or ₹500 per head minimum) for 10 to 15 guests, 50 percent for 16 to 30 guests, and 50 to 100 percent with a signed agreement beyond 30 guests. Per-head flat advances also work: Indian Accent charges ₹1,000 per guest. Calibrate to your average per cover and keep the amount close to your real loss from an empty table.

Is it legal for a restaurant to keep a booking advance in India?

Yes, if the terms were disclosed in writing before payment and the forfeited amount is a reasonable pre-estimate of the real loss. There is no India-specific statute or court ruling on restaurant advances; Section 74 of the Contract Act, 1872 governs, and the Consumer Protection Act, 2019 can strike down disproportionate or hidden terms. Disclose first, keep it proportionate, refund promptly when your own ladder says so.

How do Indian restaurants collect booking advances?

Mostly through UPI payment links from Razorpay, Paytm or PhonePe for Business, sent in the same WhatsApp message as the written terms. UPI one-time mandates, which block the amount without debiting it until a no-show occurs, are the emerging alternative. Bank transfer suits corporate bookings. Avoid cash: you want a timestamped trail.

Is a booking advance the same as a cover charge?

No. In India a cover charge is a minimum spend collected upfront and redeemed against the food and beverage bill, with any unspent difference not refunded. A booking advance confirms a reservation, is adjusted against the bill when the party arrives, and follows a refund ladder when it cancels.

Should the advance be refunded if the guest reschedules?

The guest-friendly and revenue-smart answer is to carry the advance to the new date, once, when the reschedule is requested with reasonable notice (24 to 72 hours). Many Indian group cancellations are really date changes; a carried advance keeps the booking, the money and the relationship.

Do small restaurants need advances at all?

Only on the bookings that can hurt: groups of 10+, festive and peak nights, and any fixed menu prepped per seat. For everyday tables, confirmations, reminders and a published cancellation policy prevent most no-shows with far less friction.