Groups and banquets: why the group statement must be ready the day they leave

A group of thirty-five people stayed three days at your hotel for a training course. It used twenty rooms, the meeting room for two days, four coffee breaks, two lunches and a closing dinner. The organizer has a bus at eleven in the morning and wants to review and sign the statement before boarding. If at that hour the front desk is still waiting for the restaurant tickets and the banquet sheet, the statement will go out by email, three days later, and with at least one argument attached.

What the group statement is

It is the document that summarizes everything the group consumed and that the company or organizer is going to pay: the room nights in the block, the meeting room rental, the food and beverage services contracted, the audiovisual equipment and any extra authorized during the event. In the hotel it is called the master account or master folio, and it is different from the personal folios of each attendee.

That distinction is the first source of conflict. The closing dinner is paid by the group. The beer that the attendee in room 214 ordered at the bar at midnight is paid by the attendee. If both go into the same drawer, someone has to separate them afterwards, and afterwards is when the attendee has already left and the organizer says that beer is not theirs.

The groups and banquets page (Groups and banquets) describes the full model. Here we care about a single idea: the statement is not assembled at the end. It assembles itself every time the group consumes something, as long as each consumption is posted against the master folio at the moment it happens.

Why it is reconciled by hand today

In most hotels a group touches four areas that close at different times with different tools. The front desk has the room block in the property system. Sales or banquets has the event contract in a separate document. The restaurant has its tickets in the point of sale. The bar has another register and sometimes another shift close. Each area closes when its turn comes, and none of them sees what the others recorded.

When the organizer asks for the statement, someone, almost always the front desk or the controller, gathers the four sources into a spreadsheet. Nights are copied from one place, tickets from another, services from the contract, and everything is added up. Every copy is a chance for error, and every error is discovered when the organizer compares against their own list and finds one coffee break too many or one dinner too few.

The result is a statement sent by email days later, with the event already cold, and a payment delayed for as long as the argument lasts. It is not a problem of slow people; it is a problem of the document being built at the end instead of being built along the way.

The master folio as the backbone

The solution has a single principle: every group consumption is tied to the master folio at the moment it happens, from the revenue center where it happens. The ten o’clock coffee break is posted in the coffee shop or in banquets as a service with its price, its headcount and its time, and goes to the master. Thursday’s lunch is posted in the restaurant as a contracted service and goes to the master. The midnight beer is posted at the bar and goes to the attendee’s personal folio, because the group contract excludes the bar.

With that, the statement exists from day one. The organizer can ask for a partial cut on the first night and see exactly what has accumulated. On departure day only that morning’s items are added and the statement is signed. There is no spreadsheet because there is nothing to gather.

An example with numbers

The numbers below are made up to show the calculation. They are not real rates or data from any hotel. The course group stays two nights, uses the meeting room for two days and contracts meals for thirty-five people.

Apart from the master, eighteen attendees consumed at the bar over the two nights for a total of 4,300 among all of them. That amount does not appear on the group statement. It appears on eighteen personal folios and was collected at the front desk from each one on check-out. The organizer never sees it, and that is why the organizer never argues about it.

Had the hotel sent the 4,300 from the bar to the master out of habit, the statement would have read 111,200, the organizer would have returned it, and those 4,300 would have ended up absorbed because the attendees were gone. The separation between master and personal is not an accounting detail; it is the difference between collecting and not collecting.

What goes to the master and what goes to the personal folio

The rule is the same as in any corporate agreement: it is written once in the group contract and the system applies it on every consumption. The usual criteria are these.

• By contracted service: coffee breaks, lunches and dinners included in the contract go to the master with the guaranteed headcount.
• By category: if the contract includes non-alcoholic drinks at meals but excludes the bar, each line is routed by its category and its revenue center.
• By cap: the contract may cover dinner up to a certain amount per person; whatever exceeds it goes to the personal folio of whoever ordered it.
• By time: what is consumed within the event program goes to the master; what is consumed outside the program goes to the personal folio, unless the organizer authorizes it.
• By authorization: the organizer can approve an extra on the spot, and that extra enters the master with their signature, not on anyone’s word.

What the organizer signs every day

A statement that is ready on departure day depends on a daily habit, not on a final push. Every day of the event the organizer should sign three things, and all three feed the master folio with no extra work.

1. The headcount confirmation for each meal service: how many people guaranteed, how many served. The service amount is calculated from that figure.
2. The consumption sheet for the banquet or coffee break, with the last-minute changes: ten more people, a service extended by half an hour, an additional bottle of wine at dinner.
3. The partial cut of the master folio at the end of the day, so that any difference is cleared up that same night and not on bus day.

With those three signatures, departure morning holds no surprises. The organizer has already seen two partial cuts, knows the running total and only reviews the last morning. It is the same logic the controller (Controller) applies to the shift close: what is reviewed daily is closed daily.

Departure day, in ten minutes

The front desk opens the master folio and sees the balance with the detail by day and by revenue center. It prints or sends the statement, the organizer reviews it against their own daily signatures, and signs the last one. If the contract requires an invoice, it comes out with the same lines, because the statement is the invoice without the stamp. The balance payment is posted against the master and the group closes. Nobody called the restaurant, nobody hunted for tickets, nobody opened a spreadsheet.

And there is a second, less visible gain. Because each service was posted in its revenue center, the group’s revenue is already separated by department for the monthly report: rooms on one side, banquets on another, restaurant on another. That is what the hospitality accounting standard asks for, and there is an explanation of why it pays off even in a small hotel (What USALI is and why it pays off even with twenty rooms).

Mistakes that delay the statement

• Posting meal services only when the event ends, instead of every day, because the final headcount might still change.
• Sending to the master everything consumed by anyone wearing a badge, bar tabs included.
• Accepting last-minute changes verbally, without the organizer’s signature, and discovering them during the final argument.
• Applying the deposit by hand in the spreadsheet instead of posting it against the master folio from the day the contract was signed.
• Keeping the event contract in a document the revenue center cannot read, so the server does not know what is included.

What to do this week

1. Take the last group your hotel hosted and measure how many days passed between its departure and the statement being sent.
2. Count how many different sources were gathered to build it: property system, contract, tickets, registers.
3. Check whether any bar or personal consumption ended up on the group account and whether it was collected or absorbed.
4. Write, for the next group, the rule of what goes to the master and what goes to the personal folio, in five lines.
5. Agree with the organizer of the next event on a signed partial cut every night.

Inn Restaurant posts every group service against the master folio from the revenue center where it happens, and routes personal items to each attendee’s folio using the contract rules. If you want to see what the statement of a real group at your hotel would look like, the 15-minute demo is booked on the contact page (contact).