The engineer’s beer: the consumption that must not land on the company invoice

Tuesday, eight thirty in the evening. The hotel restaurant has eleven tables going and a maintenance engineer, sent by a company with an agreement, is having dinner alone at table four. He orders a steak, a salad and two beers. When he is done he says "To my room, please." That check has one line that must not land on the company invoice, and nobody in the restaurant should have to remember that.

The whole case

The engineer’s company services industrial plants and sends technicians to your city almost every week. It signed an agreement with the hotel that covers the room, breakfast and dinner for each technician, with a cap per dinner, and expressly excludes alcoholic drinks. The engineer has been in house three nights and has had dinner in the restaurant on every one of them.

The numbers below are made up to show the calculation. The steak costs 260, the salad 90 and the two beers 110. The check adds up to 460. The agreement cap per dinner is 400. The covered items are the steak and the salad, 350, which fits under the cap and goes to the company. The beers, 110, go to the engineer’s personal account and he pays for them on check-out.

There are three parties at that table even though only one is visible. The engineer wants a quiet dinner and to sign once. His company wants a clean invoice that its purchasing department approves without questions. The hotel wants to collect the full 460, from whoever owes it, without absorbing anything and without arguing with anyone. All three can be satisfied at once, but not if the rule depends on who waited the table.

When the server has to remember

First scenario: the server is new and does not know there is an agreement. He posts the 460 to the room with a note that says agreement. The next day the front desk sends everything to the company account. Three weeks later, the company’s purchasing department receives an invoice with two beers on it and returns the whole thing. Now the hotel controller has to open that invoice, find the ticket, separate 110, re-invoice and apologize. The engineer is already in another city and nobody is going to charge him for the beers.

Second scenario: the server has years in the restaurant and does remember. He splits the check in two by hand: one with the steak and the salad, another with the beers. The guest signs twice. The suggested gratuity is calculated twice. The register ends up with two tickets for a single table, and when the second one is posted to the personal account someone keys 101 instead of 110. The shift close is off by nine and the manager spends half an hour finding out why.

The problem is not the server, neither the new one nor the experienced one. The problem is that the agreement rule lives in one person’s head instead of living in the system that closes the check. The server page (Server) says it another way: the best server in the hotel is the one who does not have to remember anything beyond the table.

When the system remembers

Now the same dinner with the rule written into the agreement. The server opens the check, rings up steak, salad and two beers, and on closing chooses room charge. The system asks for the room, verifies against the front desk that the engineer exists, is in house and that his booking carries his company’s agreement. All of it on screen, in seconds, without calling anyone.

On confirmation, every line travels to the payer it belongs to according to the rule: steak and salad to the agreement account, beers to the personal account. One check, one signature. On the guest folio two charges appear with the same time, the same revenue center and the same server, one labeled agreement and one without the label. The server does not even need to know an alcohol rule existed; all he saw was a confirmation.

The difference between typing a room number into a text field and verifying the folio in real time is explained on the room charge page (Room charge). For this case, the part that matters is the second half: the folio carries the agreement, and the agreement carries its rules.

One check, one folio, three documents

Notice that all three documents come from the same event: one dinner, captured once. Nobody rewrites anything. The check is what the guest saw, the folio is what the front desk collects and the statement is what the company pays. If any of the three were produced by hand, sooner or later it would stop matching the other two.

What the company sees at month end

The statement the company receives lists every agreement charge of the month: date, technician’s name, revenue center, category and covered amount. Behind every line there is a ticket signed by the technician himself. The purchasing department does not need to call the hotel to ask what each item was, because each item comes explained.

Whatever fell outside the agreement, like the beers, does not appear on that statement. It appears on the hotel’s internal report as excluded by rule, with the reason, so the controller knows how much consumption from agreement travelers was collected directly from the guest. The reports page (Reports) shows how that separation feeds the food and beverage report by segment: corporate sales on one side, direct guest sales on the other.

And if the engineer refuses to pay for the beers

It happens, and more often than you would think. The engineer arrives at the front desk at six in the morning, sees a charge for 110 and says his company pays for everything. The front desk opens the folio and shows the personal charge: it comes with the ticket he signed, the time and the agreement rule that excludes it. It is not the receptionist’s opinion or a decision the hotel made that morning. It is what his company signed.

If the engineer insists, the conversation is between him and his company, not between him and your hotel. And if the company, a month later, decides to cover alcohol up to a certain cap because its technicians complained, the change is made in the agreement rule, not on the product or the menu. The next day it applies at every table, with every server.

Signs that your hotel depends on the server’s memory

• There is a sheet at the restaurant register listing companies with agreements and their rules, written by hand.
• The front desk calls the restaurant in the mornings to ask what each charge from the night before was.
• Invoices to companies go out late because someone reviews ticket by ticket before sending them.
• Over the last year, beers, wines or desserts have been absorbed to avoid arguing with the client.
• The server asks the guest whether that goes to the company, and the guest decides.
• When a new server joins, training includes memorizing which company covers what.

The same case multiplied by a month

Let us keep going with invented figures to see the size of the matter. The company sends eight technicians a month, each stays four nights and has dinner every night at the hotel restaurant: 32 dinners. If the average covered amount per dinner is 320, the company statement adds up to 10,240. If 20 of those 32 dinners included alcohol at an average of 90, personal consumption for the month is 1,800.

Those 1,800 have three possible destinations. They are collected from the technician on check-out, which is the right one. They are sent by mistake to the company, which returns them and generates re-invoicing work. Or they are absorbed to avoid an argument, and over twelve months that is 21,600 that left the restaurant without anyone deciding it. The figure is not the point; the point is that, without the rule in the system, you do not even know which of the three destinations each beer took.

What to do this week

1. Ask the front desk how many calls to the restaurant they made last week to clarify agreement charges.
2. Review the last three invoices to companies and look for any alcohol line that slipped through.
3. Calculate, with your own numbers, how much excluded consumption was absorbed last month to avoid an argument.
4. Write the alcohol rule of every active agreement in a single sentence and verify the system can apply it.
5. Run a test dinner with a fictitious folio from a company with an agreement and confirm two charges come out.

Inn Restaurant ties every check to the guest folio and applies the agreement rules on closing, so the engineer’s beer reaches his personal account without anyone remembering anything. If you want to see the full path with one of your hotel’s agreements, the 15-minute demo is booked on the contact page (contact).