Product
Operation types
Pricing
Compare
Resources
Log in See a 15-minute demo ESEN
Article · 9 min

Outside visitors’ consumption at a hotel: how it is separated from the guest’s

Your hotel’s restaurant sells to two different customers: the guest sleeping upstairs and the neighbor who walked in from the street. If the point of sale does not tell them apart from the first course, collection gets tangled and the per-occupied-room report says whatever it wants.

A hotel restaurant that only serves its guests is wasting half the dining room. That is why almost all of them open the door to the street: neighborhood families, nearby offices, people who come for the chef. That is good for sales and bad for reports, if the point of sale treats the outside diner and the guest from room 305 the same way. They are two different customers, with two different ways of paying and two different places in the controller’s report.

Two customers in the same dining room

The guest consumes and says “To my room, please.” Their check travels to the folio and is collected at check-out. The outside visitor consumes and pays at the table, by card or cash, and leaves. So far everything seems simple. What gets complicated is everything around it: the sales report, the cash close, revenue per occupied room, the guest’s corporate agreement, and the visitor who gives a room number that is not theirs.

The distinction is not an accounting detail. It is the difference between knowing whether your hotel’s restaurant sells to its own guest or sells to the street. Both sales are good; but they tell different stories and call for different actions. If the restaurant sells a lot to the street and little to the guest, you have an internal capture problem. If it sells a lot to the guest and little to the street, you have an empty dining room in low season. You do not know which unless you separate.

Why the per-occupied-room report gets contaminated

Food and beverage revenue per occupied room is the metric the controller and the food and beverage director look at every month. Under USALI, the numerator is all of the hotel’s food and beverage revenue, including sales to outsiders; the standard does not ask for a split. But the metric that truly says whether your guest eats with you is the one that uses guest sales only. And that one can only be calculated if every ticket knows whether it came from a guest or from an outsider.

When the point of sale does not distinguish, one of two things happens. Either all consumption is counted as if it came from guests, and the metric inflates every time the neighborhood comes to dinner. Or the restaurant manager estimates “roughly 60 % is guests” and the metric becomes an opinion. In both cases, the hotel director makes decisions about included breakfast, bar hours or company agreements based on a number that does not describe their guest. How to calculate it properly is in the piece on revenue per occupied room (How food and beverage revenue per occupied room is calculated, and what a good number looks like).

An illustrative example with numbers

The figures are made up to show the calculation; they are not data from any hotel. Imagine a 30-room hotel with 600 occupied room nights in the month and a restaurant that sold 96,000 net in that period.

Item (illustrative example)Without separatingSeparating guest and outsider
Net F&B revenue for the month96,00096,000
From guests (room charge and guests paying directly)Unknown60,000
From outside visitorsUnknown36,000
Occupied room nights600600
Total F&B revenue per occupied room96,000 ÷ 600 = 16096,000 ÷ 600 = 160
Guest F&B revenue per occupied roomAssumed 16060,000 ÷ 600 = 100
Illustrative example with invented figures. The total metric is the same in both columns; what changes is knowing how much of that consumption came from upstairs and how much from the street.

Without separating, the director believes every room night sold leaves 160 in the restaurant. Separating, they discover it leaves 100, and the other 60 comes from the neighborhood. Now suppose next month occupancy rises to 800 nights and total sales rise to 104,000: the total metric drops to 130 and everyone gets alarmed. But if guest sales were 80,000, guest revenue per occupied room held at 100. What dropped was street sales, because the dining room was full of guests. Two opposite diagnoses of the same 104,000.

How each ticket is tagged

Separation starts at the table, not in the report. Every check opened at your hotel’s restaurant must have a type from the first course, and the server sets it with a natural question: “Are you staying with us?” The answer decides the type of check, and the type of check decides the rest.

  • Guest with room charge: the check is tied to the folio after verifying the stay, and collected at check-out.
  • Guest paying directly: staying at the hotel, but prefers to pay at the table. Still guest consumption for the report, even though it does not go through the folio.
  • Outside visitor: not staying at the hotel. Pays at the table, always, and can never post to a room.
  • Agreement or company account: consumes on a corporate account, whether staying or not, under the rules the agreement sets.
  • Courtesy or internal consumption: management, staff, hotel invitees. Recorded at value and flagged as a comp so it does not inflate sales.

The second type is the one almost everyone forgets. The guest who pays by card at the table is still a guest, and their consumption counts toward knowing whether your guest eats with you. If the system only distinguishes “room charge” from “direct payment,” that guest is counted as an outsider and the metric drops for no reason. That is why the check type is defined by who the diner is, not by how they pay.

The visitor who gives a room number

Here is the most expensive risk of mixing. An outside diner finishes dinner, the server asks how they will pay, and the diner says “to 305.” If the point of sale accepts a typed number without verifying, the dinner goes to the folio of 305, the real guest disputes it at check-out, the front desk removes it because it cannot prove anything, and the restaurant gave away a dinner to someone who was not even a guest.

Verification against the folio closes that door: the system looks up the room, shows the registered guest’s name, and the server confirms it with the diner or asks for the key card. If the name does not match, there is no charge, and the diner pays at the table like any visitor. The room charge page (Room charge) explains that verification step by step. What matters here is that separating guest from outsider is not only for the report: it is the folio’s first line of defense.

How they are separated in the close and in the report

With the check type set at the table, everything else falls into place on its own. The restaurant’s cash close shows what was collected at the table: card and cash from outside visitors and from guests who paid directly. Room charges do not appear in the close as money, because the money comes in through the front desk; they appear as sales transferred to the folio, with their detail. The guide to the cash close by revenue center (A guide to the shift close by revenue center in a hotel) shows how the two parts balance.

The controller’s report, meanwhile, reads sales by diner type and by revenue center. That is where separation stops being a formality and becomes information: how much the restaurant sold to guests at breakfast, how much to outsiders at dinner, how much on agreements at weekday lunch. With that table, the director knows which shift lives on the guest and which lives on the street, and can decide hours, menu and staffing for each.

Diner typeHow they payWhere the money shows upCounts toward guest consumption
Guest with room chargeAt check-out, at the front deskFront desk cashierYes
Guest paying directlyAt the tableRestaurant closeYes
Outside visitorAt the tableRestaurant closeNo
Agreement or company accountInvoiced to the companyAccounts receivablePer the agreement
Courtesy or internalDoes not payComps reportNo
Where each diner type’s money ends up and what goes into the guest consumption metric. The type is defined by who eats, not by how they pay.

The cases that confuse people

The guest’s companion

The guest in 305 invites a friend from town to dinner. There is one check and the guest pays it, to the room or directly. For the report, all the consumption is guest consumption, because the guest generated it. There is no need to separate the friend’s dish; there is a need to record that the table was a guest table with two covers, so consumption per cover is right as well.

The company traveler who does not sleep at the hotel

A company with an agreement sends its employees to eat at your hotel’s restaurant even when they are not staying. That is agreement consumption, charged to the company account, and it is not guest consumption. If the agreement also covers travelers who do stay, the system has to distinguish the two cases: same agreement, two diner types. The company accounts page (Master accounts and agreements) details how those rules are set up.

The event in the function room

A banquet for 80 people is neither guest nor outsider: it is its own revenue center under USALI, with its own report. Do not mix it with the restaurant or count it in the restaurant’s revenue per occupied room. Even if the attendees are staying at the hotel, the event’s consumption belongs to the event.

The guest who checked out and stays for lunch

They checked out at eleven and eat at one. They no longer have an open folio. For collection it is direct payment; for the report they are still a guest of the day. A serious system tags them as a guest paying directly even though the folio is closed, if the server identifies them as a departing guest.

What the point of sale must do on its own

None of this works if it depends on the server remembering to set the type. Your hotel restaurant’s point of sale must ask for the diner type when opening the check, refuse room charge without a verified folio, tag as guest paying directly any check that was tied to a folio and then paid at the table, and carry the type all the way to the report without anyone reclassifying by hand.

And it must do so just as naturally in the restaurant, the bar, the coffee shop and the pool, because the outside visitor comes in everywhere. A separation that exists only in the main restaurant leaves the bar counting everyone who sits down as a guest.

In short

Every check at your hotel’s restaurant has a type from the first course: guest, outsider, agreement or courtesy. The type is defined by who eats, not by how they pay, and it is what lets you know whether your guest eats with you without the neighborhood inflating the number.

What to do this week

  1. Take last month’s restaurant sales report and ask how much came from guests and how much from outsiders. If the answer is an estimate, that is the finding.
  2. Check whether the point of sale allows posting to a room without verifying the guest’s name. If it does, any visitor can have dinner on 305.
  3. Define the five diner types in writing and ask the restaurant manager to explain them to every server, with the exact question they will ask.
  4. Calculate, with whatever data you have, guest revenue per occupied room for last month and compare it with the total. The gap between the two is what you were measuring wrong.
  5. Review one current corporate agreement and confirm whether it covers employees who are not staying, so the correct type can be configured.

Inn Restaurant asks for the diner type when each check is opened, verifies the folio before any room charge and carries the guest-versus-outsider split all the way to the controller’s report by revenue center. If you want to see guest revenue per occupied room separated from street sales, book the fifteen-minute demo (contact).

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.

See a 15-minute demo
We use the minimum to make the site work and to know which pages are useful. You can reject the rest.