Service charge and tip: why guests end up paying both

A common floor practice, where it comes from, and why it costs far more than it collects.

Watch a table close on a Saturday night and you'll see it.

The bill goes down. The server mentions, helpfully, that a service charge has been added — and adds that of course, if the guest would like to tip directly, they're welcome to.

The guest is mid-conversation. The bill is in a folder. The service charge is one line sitting among the taxes. They don't register it. They leave a tip on top.

They have now paid twice for the same meal. Often 20% or more, when they meant to leave 10%.

They find out at home

Not at the table. At home, going through the bill. Or three weeks later, looking at a card statement.

And what they take from it isn't I misread a line. It's that restaurant charged me twice.

That's the part worth sitting with. The guest who gets caught by this is never the one who scrutinises the bill. It's the one who wasn't checking — which is to say, the one who trusted you, and the one who was going to tip well anyway. You have taken your most generous guest and given them a specific story to tell about your restaurant.

Most of them will never tell you

This is the expensive part, and it doesn't show up anywhere you're looking.

A guest who feels overcharged rarely calls to complain. There's nothing to complain about, exactly — the charge was disclosed, the tip was their own choice, and arguing about it means admitting they weren't paying attention. So they say nothing.

What they do instead is quietly downgrade you. Not to bad restaurant. To something more corrosive: the place that's a bit sharp with the bill. And that judgement is stickier than a complaint about a cold starter, because a cold starter is a bad night and this feels like a policy.

Watch what it does to the decisions that follow. They stop suggesting you for the group dinner, because now they'd be exposing friends to it. They stop bringing clients. When they do come back, they read the bill line by line, and they don't tip — not out of anger, but because they've learned to be careful with you. A guest who is being careful is no longer a regular. They're just a transaction.

The maths is unkind. You collected an extra ₹300 once, from someone who might have spent ₹40,000 with you over three years and brought four other people with them.

And you'll never see the loss, because it arrives as an absence. No review, no complaint, no chargeback. Just a table that doesn't get booked, by someone you'd have described as a happy customer.

Where it actually comes from

Almost nobody is doing this to squeeze an extra few hundred rupees. It comes from somewhere more understandable.

Service charge goes to the house. In plenty of restaurants it then reaches staff slowly, partially, or on a schedule nobody has explained. A server who has watched that happen for a year has every reason to prefer cash in hand, and mentioning the tip option is how they get there.

So the practice isn't really about the guest at all. It's an internal pay and distribution problem, being solved on the floor, at the guest's expense.

And it lands on the guest because the guest is the only person in the transaction who doesn't know how the pool works.

What it costs

Disputes. A guest who feels double-charged sometimes calls their bank instead of you. That becomes a chargeback weeks later, with a fee attached, and a charge the guest can plausibly say they never agreed to is hard to defend.

Reviews, from the few who do speak. "They add a service charge and then ask for a tip" is a sentence other diners recognise instantly. It's specific, it's credible, and it doesn't fade. Treat every one you see as representing a dozen guests who left without saying anything.

Staff trust. A system where servers feel they have to work around the bill to be paid properly isn't stable. The good ones notice first and leave first.

And the charge itself may not be lawful. Since the Delhi High Court's March 2025 ruling, a service charge added by default is outside the CCPA guidelines — and enforcement has been active through 2026. Telling a guest about the charge afterwards doesn't fix it. It demonstrates the charge went on before anyone asked.

The fix isn't a better script

You could train servers to mention it more clearly. That treats the symptom.

The actual fix is one of two things, and you probably already know which one applies to your restaurant.

Ask before you add it. A real question, before the bill prints: "There's an optional service charge — leave it on, or take it off?" One sentence. Whatever the guest says, no comment. A guest who has been asked cannot be double-charged, because they know exactly what's on the bill.

Or fix the distribution. If service charge is meant to reach your staff, publish how much and how often, and pay it on schedule. Servers who trust the pool stop needing to route around it — and the practice disappears without anyone being trained out of it.

Most restaurants doing this need both.

The rules on service charge, how tips should flow through your POS, and what to do about the tip pool: [read the full guide to service charge and tips].