Corporate events at the hotel: how the restaurant sells the coffee break, lunch and dinner as one package

When a company books twenty rooms and a meeting room at your hotel, it almost always brings three meal moments: the morning coffee break, lunch at midday and a closing dinner. The hotel restaurant produces them, but the sale usually stays in the sales team’s email, the account in a spreadsheet and the settlement in a last-minute negotiation with the organizer. There is a better way, and it starts with selling the three services as a single per-person package.

The event that comes in through sales and lands in the restaurant

The typical flow goes like this: the hotel’s sales team closes the group, negotiates the room rate, holds the meeting room and, at the end, asks what they are going to eat. That is where the restaurant comes in, almost always with a menu by email and a per-person price per service. The company accepts, on the day of the event the food is served, and afterwards someone tries to reconstruct what was consumed, how many people attended each service and what fell outside the agreement.

The problem is not the menu or the price. The problem is that every piece lives somewhere different: the agreement in an email, the attendee count in the organizer’s head, the extras on loose bar tickets and the rooms in the front desk system. At close, the controller has to build the bill from scraps, and every difference turns into a discount out of exhaustion.

The way to avoid it is to treat the event as what it is for the hotel restaurant: one sale with one account, many consumptions and a settlement date. That fits perfectly in a point of sale built for hotels, and that is what the rest of this article is about.

The per-person package: what is in and what is out

Selling service by service forces you to negotiate three times and count attendees three times. Selling a per-person package per day solves both: one price, one count. The typical one-day event package has the coffee break, lunch and dinner, and may include water and coffee in the meeting room all day.

What matters is writing clearly what is inside and what is outside. Inside goes what has a predictable cost: the food of each service, the soft drinks at lunch, the coffee in the meeting room. Outside goes whatever depends on each attendee’s behavior: the bar at dinner, consumption in the restaurant outside event hours, room service and the minibar in the rooms.

• Coffee break: coffee, tea, water, juice, pastries and fruit. Served in the meeting room at an agreed time and cleared at another.
• Lunch: three-course menu with two main course options, water and soft drinks. Served in the hotel restaurant or in the meeting room.
• Dinner: three-course menu, one glass of wine or a welcome drink. Open bar is quoted separately, by consumption or as an hourly bar package.
• Coffee and water in the meeting room: refilled during the day, included in the per-person price.
• Outside the package: additional alcoholic drinks, individual consumption in the restaurant and bar, room service, minibar and laundry.

That list is what later prevents the argument. If the organizer knows from the quote that the dinner bar is not included, the bar charge at the end of the event is not a surprise: it is what they signed.

The master account: one account, many consumptions

The master account is the group’s account. Everything the company agreed to pay is posted there: the attendees’ room nights if the company covers them, the meeting room, the per-person meal package and the extras the organizer authorizes. It lives tied to the group folio at the front desk and is settled at the end of the event or within the terms of the company agreement (Master accounts and agreements).

What makes the master account work is that the restaurant can post to it directly, with the same discipline it uses to post to an individual guest’s room. The server records the ten o’clock coffee break for sixty people, the system places it on the group’s master account, and the controller sees it at that moment. Nobody types it into a spreadsheet later.

Next to the master account live the personal accounts of each attendee. If an attendee orders a bottle of wine at dinner that is not in the package, that consumption goes to their room folio, not the group’s, unless the organizer authorizes it. The rule of who pays for what is defined beforehand, recorded in the system, and the server only chooses which account each item goes to (A guide to the shift close by revenue center in a hotel).

An illustrative example with numbers

The figures below are invented to show how an event is built and settled. They are not data from any hotel or any company.

Look at the guarantee. It is the number of people the company commits to pay for even if fewer show up. In the example, the guarantee was 54 and 58 came, so 58 are billed. If 50 had come, 54 would be billed. That rule, written into the quote, protects the kitchen’s production and keeps the day of the event from turning into haggling over every empty chair.

The dinner bar appears as a separate line because it was not in the package and the organizer authorized it to the master account during the event. What matters is that the authorization is recorded with a name and a time, and that the drinks were ordered in the system with the master account as destination, not in a bar notebook.

What falls outside the package and how it is recorded

No event turns out exactly as quoted. Someone asks for a vegetarian menu that was not planned, the organizer extends the coffee break, ten attendees stay at the bar until late. All of that is legitimate hotel restaurant revenue, as long as it is recorded at the moment and on the right account.

Extras authorized by the organizer

They go to the master account. They are recorded with the authorization of whoever requested them and appear in the settlement as lines separate from the package. The organizer recognizes them because they asked for them and because they see them with time and description.

Individual consumption by attendees

It goes to each attendee’s room folio, with verified room charge (Room charge). If the attendee is not staying at the hotel, they pay on the spot. The rule must be clear to the server before the event: whoever is not on the master account list pays like any other customer.

Hotel courtesies

If the manager decides to host the closing toast, it is recorded as a comp with authorization, not as a silent discount in the settlement. That way the controller knows what the client relationship cost and the organizer sees the gesture on the bill.

Settlement at the end of the event

If everything above was done in the system, the settlement is a report that gets printed or sent, with the package, the guarantee, actual attendees, authorized extras and comps. The organizer checks it against the quote, signs, and the account moves to collection according to the agreement: immediate payment, thirty-day terms or a charge to the registered corporate card.

Settlement disputes almost always have the same root: consumption nobody recorded at the time that shows up at the end as a lump sum. When every line has a time, a service, a quantity and who authorized it, the conversation changes from “we did not order this” to “yes, at nine we ordered another round”. That is why a well-fed master account is worth more than any skill at negotiating the close.

One tip that saves hours: agree with the organizer on a mid-event review. When lunch ends, show them the master account up to that point. If something does not add up, it gets corrected at three in the afternoon, not at eleven at night with the group already at the bar.

What the controller sees

For the controller, the event is banquet revenue, separate from the restaurant, the bar and room service, exactly as the hospitality accounting standard asks (What USALI is and why it pays off even with twenty rooms). If the package was recorded by service, they can split revenue between food and beverage, measure the cost of each service and know whether the coffee break was priced right.

They can also answer the question the owner asks after every event: how much did the group leave in total, adding rooms, meeting room, package and extras? That figure only exists if the hotel restaurant posted to the same master account as the front desk. With two systems, it is a manual sum that always comes out different depending on who does it.

Mistakes that cost money

• Quoting without a minimum guarantee. Without it, the kitchen produces for sixty and bills for forty-five.
• Leaving the bar open without defining which account it goes to. At the end nobody recognizes the consumption and the hotel absorbs it.
• Recording the event in a spreadsheet outside the point of sale. It never reaches the shift close, the banquet report or the settlement.
• Confusing the master account with a personal account. An attendee who charges wine to the group without authorization is a guaranteed dispute.
• Settling without a mid-event review. Every hour that passes without showing the account makes it harder for the organizer to recognize it.

What to do this week

1. Write your standard one-day event package: coffee break, lunch and dinner with a per-person price, and the list of what is excluded.
2. Add the minimum guarantee to every quote, with the rule of billing the higher of guarantee and actual attendees.
3. Set up the group’s master account in the point of sale and the rules for which consumption goes to the group and which to the attendee’s room.
4. Train the restaurant and bar team to pick the right account on every order, with recorded authorization for extras.
5. Agree with the organizer on a mid-event review of the master account and a signed settlement at the end.
6. At close, review with the controller how much the group left in total and how much of that was food and beverage.

Inn Restaurant handles the group’s master account and the attendees’ personal accounts from the same server screen, with the settlement ready at the close of the event. If corporate groups at your hotel end in a last-minute negotiation, book a 15-minute demo (contact) and build a test event with us.