Back to blog
Guide

The Guest Who Pays For Everyone

In most groups one person decides and one person settles, and they are not always the same. Getting this wrong costs the table; recording it correctly is worth more than the bill.

A table of six. One of them ordered, one of them will pay, and one of them is the reason everyone is there.

Frequently these are three different people, and the venue treats the table as a single unit called "table nine".

Why it matters operationally

The bill goes to the wrong person. Presented to whoever looks most senior, which is a guess, and getting it wrong in front of a group is a specific small humiliation that guests remember.

The upsell goes to the wrong person. Offering the next bottle to someone who is not deciding produces a no that was never theirs to give.

The record attaches to the wrong person. ⚠️ The payer goes onto the guest record because that is where the card was, and the person who actually chose the venue is not recorded at all — so next time nobody knows who to look after.

The three roles

The host. Chose the venue, made the booking, is the reason the group is here. The one who decides whether there is a next time.

The decider. Orders, sets the pace, escalates the spend. Sometimes the host, frequently not.

The payer. Settles. May be a company card, may be the person who lost a bet, may be the quietest one at the table.

⚠️ The host is the one that matters most and the one recorded least, because they do not necessarily touch the till.

How the floor already knows

The staff can identify all three within about ten minutes, without asking:

Who was greeted first and by name. Almost always the host.

Who the others look at before answering. The decider.

Who takes the folder. The payer, and this is the only one your system currently sees.

None of this requires a question. It requires somewhere to put the answer.

What to record

One field, filled at the end: who the host was.

That is enough. The payer is already captured by the transaction, the decider matters for the night and rarely afterwards, and the host is what makes the next booking possible.

Where the bill goes wrong

Two habits worth changing, both free:

Do not present the bill to anyone in particular. Place it centrally, or ask quietly. ⚠️ Guessing is a coin flip with an embarrassing downside and no upside.

Ask about splitting before the end, not at it. The worst moment to discover a group wants six separate payments is when the room is closing and there is one terminal.

The corporate case

Worth its own note, because it behaves differently.

When the payer is a company, the host is the customer and the payer is an administrator. Marketing to the card is a mistake; the person to look after is the one who chose you, and they may never appear on any receipt.

⚠️ Whether and how you may hold and use contact details differs by jurisdiction and by how they were given. Confirm before building a list from group bookings — that is a question for your counsel.

Three names, and your record holds one

Who booked
Who is hosting the evening
Who is paying

⚠️ Often the same person, frequently not. A system with one name field keeps only one of the three — and the one it keeps is usually the booker, which is the least operationally useful of them.

The floor already knows all three

Who to defer to  Who not to say the total in front of  Who to thank

⇒ ⚠️ It exists entirely in someone's head, which means it is correct tonight and gone the moment that person is off.


Three things worth writing down

Who pays
Whether the amount may be said in front of them
Who the next booking is likely to come from

⚠️ The second matters most. Getting it wrong does not cost a transaction — it can spoil the entire evening, in front of the people it was arranged for.


Where the bill actually goes wrong

Decided at the end  in front of everyone, under time pressure
Asked at the start  "will this be one bill?" — and it is settled

⚠️ One question at the beginning removes the only genuinely awkward moment of the night.   ⇒ Asked at the end, there is no good way to ask it.


The corporate case splits it further

The payer  a company
The chooser a person

⚠️ Thanks and the receipt go to different places.   ⇒ The receipt is addressed to the company; the appreciation belongs to     the individual, and doing only one of the two is why a corporate     booking does not repeat.


Do not look after only the payer

The payer decides  whether to come back
The guests decide  whether to be invited again

⚠️ Both have to be true for there to be a next time.   ⇒ A venue that focuses entirely on whoever holds the card is     optimising for one half of a two-part decision.



Whose name the record carries is a different question

 ⇒ Handled separately, in   The Guest Who Books For Someone Else.

⚠️ This page is about the bill. That one is about the record.   The person who settles and the person the record should be under are   frequently different, and each needs its own answer.


Three to hold

Share of group visits with a host recorded. The field that is almost never captured.

Repeat rate for hosts versus payers. ⚠️ If you can only see payers, this is unmeasurable — which is exactly the point.

Groups where the bill was presented to the wrong person. Not measurable directly; ask the floor once a month. They know.

Where the record has to sit

If a visit attaches to a table and a payment attaches to a card, the person who brought six people has no record at all. The system knows who paid and not who chose.

tasteck links a booking to the guest who made it and the visit to the people in it, so the host of a group is on the record even when someone else settled.

You have a detailed history of the person who happened to be holding the card.


Read next

Free, no signup, ~5 minutes

Map out your operations in 5 minutes

Eight questions cover reservations, customer management, shifts, and settlement. Results shown instantly with industry benchmark. Sales emails only if you request them.

Your answers are not stored. The assessment runs entirely in your browser.

Try tasteck free for 30 days

No credit card required. Full access to reservations, cast shifts, dispatch, and analytics.

  • No card required
  • Free data migration support
  • All features unlocked for 30 days