Tips in a hotel restaurant: how each one is credited to the person who earned it and how the pool is split
In a hotel restaurant the tip arrives by four different paths, and one of them goes through the front desk. Here is how each one is recorded under the name of the person who earned it, how the shift pool is built, and which report keeps Sunday quiet.
It is Saturday night and the hotel restaurant has just closed. The terrace server says his table of eight left a generous tip on the room charge, the cashier says it is not in her close, and the front desk is already shut. Tomorrow the guest checks out and pays the tip at the hotel counter, credited to nobody. The Sunday argument starts like this, and almost always from a lack of records, not a lack of honesty.
Why a hotel tip is different
In a street restaurant the tip comes in by two paths: cash on the table or an amount added to the card. In a hotel restaurant there are two more paths, and both go through other areas of the property. The first is the room charge: the guest signs the check with a tip and everything travels to the folio, which the front desk collects days later. The second is group and banquet consumption, where the contract often already includes a service charge that is not the same as a voluntary tip.
Those two paths mean the hotel restaurant tip is collected in one place and earned in another. If the restaurant system does not record who each tip belongs to at the moment it is entered, the money reaches the hotel’s general cash without an owner, and splitting it later becomes a negotiation instead of a calculation.
The four paths of the tip
| Path | Where it is collected | When the money arrives | What the system must record |
|---|---|---|---|
| Cash on the table | At the table, to the server | Immediately | Amount declared by the server, linked to the check |
| Card or transfer | At the restaurant register | With the bank settlement | Amount on the terminal, linked to the check and the server |
| Room charge | At the front desk, on check-out | One or several days later | Signed amount, linked to the folio, the consumption and the server |
| Groups and banquets | In the event contract | When the event is settled | Service charge kept separate from the voluntary tip |
What changes between paths is the time between earning the tip and the money arriving. With cash it is zero. With a room charge it can be a week, if the guest stays seven nights. That is why attribution happens when the tip is recorded, not when it is collected: wait until collection and nobody remembers who served the table.
Attribution: every tip with a name from the first second
Attributing a tip means linking it to three things: the check that generated it, the person who served that check, and the path it came in by. When those three links exist, the server’s tip report builds itself: the sum of all tips on their checks in the period, separated by path. And the hotel restaurant report reconciles with the front desk report, because every tip on a folio has a source check.
The most neglected point is the room charge. When the guest says “To my room, please.” and writes the tip on the check line, that tip must be recorded in the restaurant system under the server’s name at that moment, with the folio number. The front desk collects it later as part of the folio and transfers it to the restaurant at close. If the room charge is a text field where only a number is typed, the tip reaches the folio with no owner. The article on why a text field is not enough (Room charge: why a text field is not enough) deals with the consumption side; what matters here is that the tip travels attached to that consumption.
A tip is not revenue
A reminder the controller will appreciate: the tip is not hotel revenue. It enters the register, is recorded, is split and leaves. It does not add to food and beverage sales, does not enter revenue per occupied room and pays commission on nothing. A system that mixes it with sales inflates restaurant revenue and complicates everyone’s filings. The guide to the shift close by revenue center (A guide to the shift close by revenue center in a hotel) shows where it is separated in the close.
The shift pool: what it is and how it is calculated
Many hotel restaurants prefer to split tips across the whole shift team, because in a hotel the server takes the table but the runner, the bartender, the busser and sometimes the room service staff hold it up. The pool is the sum of all tips for the shift, split by points according to role. The manager defines the points with the team and writes them down once; they are not renegotiated every Saturday.
- Close the shift and add up every tip recorded, by any of the four paths, that belongs to that shift.
- Subtract whatever the hotel’s policy says does not enter the pool, for example a banquet service charge if it is distributed separately.
- Add up the points of everyone who worked that shift, according to the points-by-role table.
- Divide the total pool by the total points to get the value of one point.
- Multiply the point value by each person’s points. That is what each one receives.
- Save the calculation with names, amounts and shift, and hand it over with the day’s close.
A practical detail: whoever worked half a shift receives half their points. And room charge tips enter the pool of the shift in which they were earned, even if the hotel collects them days later. If they enter the pool of the day the front desk collected them, Tuesday’s team keeps Saturday’s tip.
An illustrative example with numbers
The figures below are invented to show the calculation. They are not data from any hotel. Imagine the Saturday dinner shift in a hotel restaurant, with four servers, one bartender and one runner.
| Item | Value (illustrative example) |
|---|---|
| Cash tips for the shift | 1,500 |
| Card tips for the shift | 2,500 |
| Room charge tips for the shift | 1,500 |
| Total shift pool | 1,500 + 2,500 + 1,500 = 5,500 |
| Points: 4 servers × 1 point | 4 |
| Points: 1 bartender × 1 point | 1 |
| Points: 1 runner × 0.5 point | 0.5 |
| Total points | 5.5 |
| Value of one point | 5,500 ÷ 5.5 = 1,000 |
| Each server and the bartender | 1,000 |
| The runner | 500 |
Check the sum: four servers at 1,000 make 4,000, plus 1,000 for the bartender, plus 500 for the runner, gives 5,500, the full pool. The 1,500 from room charges is not yet cash when the shift closes; the hotel will collect it on folios during the week. That is why the calculation is saved with the shift and the payout happens when the money comes in, with the same split.
The report that prevents the argument
The weekend argument is not solved by memory or goodwill: it is solved by a report anyone on the team can read without help. One report per shift, which the manager prints or shares at close, with these columns.
- Every check of the shift with its server, its payment path and its tip, including those that went to the folio with a room number.
- Total tips by path: cash, card, room charge, banquets.
- The points of each person who worked and the point value for the shift.
- What each person is owed, with the part already paid and the part still pending collection on folios.
- Folio tips collected today by the front desk that belong to earlier shifts, with their shift of origin.
With that report, the Sunday conversation changes. It is no longer “my table left more” against “it is not in my close”. It is a line with a folio, a server and an amount, which the front desk can confirm in two minutes. And the hotel controller has what is needed to reconcile the restaurant register with the folios collected.
Rules each hotel writes once
How tips are split varies by country, property policy and what the team agrees, and the tax treatment of tips is defined by your accountant, not by this article. What is the same everywhere: the rules are written, communicated and applied the same way every day. A pool that changes depending on which manager is on duty is not a pool; it is a source of conflict with a nice name.
Write on one page: what enters the pool and what does not, points by role, how half shifts are counted, when room charge tips are paid out and who reviews the report. Put it in the restaurant office and in the system. When a new server arrives, that page is part of their first day.
Every tip in the hotel restaurant is linked to its check, its server and its path at the moment it is recorded, including the one that travels on the guest folio. The pool is split by points under written rules, and a single report per shift leaves the weekend without an argument.
What to do this week
- Write the hotel restaurant’s pool rules on one page: what enters, points by role, half shifts and when folio tips are paid out.
- Verify that every room charge tip is recorded under the server’s name and with the folio number from the restaurant, not from the front desk.
- Agree with the front desk how and when it transfers tips collected on folios to the restaurant, with their shift of origin.
- Separate tips from sales in the close, and confirm with the controller that they are not being added to food and beverage revenue.
- Print the tip report by shift this Saturday and read it with the team at close, before anyone leaves.
Inn Restaurant records every tip with its check, its server and its path, follows the one that went to the guest folio until the front desk collects it, and builds the shift pool with the rules your hotel wrote. If you want to see the report with your own team’s shifts, the fifteen-minute demo is booked on the contact page (contact).
More articles
Hotel restaurant suppliers: receiving goods, shortfalls at the door and returns
The month’s food and beverage cost is decided at the hotel’s service entrance, not in the kitchen. Here is how to receive, what to weigh, what to send back and how all of it lands in the cost of sales the controller reports.
Permissions by role in the hotel restaurant: what each person can do and what they cannot
When everyone logs into the system with the same password, nobody is responsible for anything. Here is the permission matrix for the hotel restaurant, role by role, and why room charge and voids are the two that need the most care.
Hotel purchasing and food cost: why the chef and the controller see different numbers
The chef looks at what was bought this month and sees one number. The controller looks at what was actually consumed and sees another. Neither one is wrong: they are looking at different dates in the same hotel.
Your hotel’s restaurant already sells well. Now the hotel needs to know it.
Fifteen minutes, with your menu and your tables. Nothing to install.