How to close a group account with no-show adjustments without rebuilding the whole statement

It is nine at night in your hotel restaurant. The company group that booked dinner for 24 people is seated, and the captain counts 22. Two empty chairs, two menus the kitchen already prepared, and a question that will reach the controller tomorrow: do we bill 24 or 22? The right answer is not a number. It is a procedure that leaves a trail.

Why no-shows break the statement

A group is sold in advance: so many people, such a menu, such a price per person. The statement is built from those figures the moment the contract is signed. When fewer people arrive, the temptation is to delete the original and recapture everything with the real number. It is what a rushed cashier does, and it produces three problems.

The first is that history is lost: nobody can later see what was contracted, what was served and why it changed. The second is that the guarantee is lost: if the contract said a minimum would be billed, recapturing with 22 gives away money the hotel had the right to collect. The third is that reconciliation is lost: the kitchen prepared 24 menus, the night’s food cost is for 24, and the reported revenue is for 22 with no line explaining the difference.

The solution is boring and that is why it works: the original statement is not touched, and the difference enters as a new, negative line with a reason, a date and a signature. The total reconciles because the arithmetic is visible, not because someone hid it.

Before the event: the guarantee policy

Everything that follows depends on a clause that should have been signed weeks earlier. The guarantee says how many people the group pays for even if fewer arrive. There are three common ways to write it, and the system must know which one applies to each group before the first plate is served.

The guarantee with tolerance is the one that prevents the most disputes, because it shares the risk: the group does not pay for empty chairs beyond a margin, and the hotel does not absorb a massive last-minute cancellation. What matters is that the percentage is written down, that the controller approved it and that the point of sale has it loaded on the group’s master account, as recommended in the article on how to write an agreement that does not generate disputes (How to write a hotel corporate agreement that does not end in a dispute).

The seven steps to close with an adjustment

This is the full procedure, from the moment the captain counts the chairs to the moment the controller locks the account. Every step leaves a record; none replaces the previous one.

1. Freeze the original statement. What was contracted (24 people × price per person) stays as the first section of the account. It is not edited, deleted or recaptured.
2. Record actual attendance with evidence. The captain counts, the group coordinator confirms, and both names go on the account along with the time. If the group signed an attendance list, attach it.
3. Apply the guarantee policy. The system compares actual attendance against the guaranteed minimum and determines how many people are billed. This calculation must be automatic and visible, not mental.
4. Capture the adjustment as a line with a reason. A negative line for the difference between what was contracted and what is billable, with the reason "no-shows" and the name of the approver. Never a generic discount with no explanation.
5. Add the day’s extras. Bottles, additional desserts and the extra hour of service enter as new lines, with their own approval, after the adjustment and not mixed with it.
6. Check the arithmetic out loud. Contracted, minus adjustment, plus extras, minus deposit, equals balance. If any number does not come out of that sum, something went in the wrong place.
7. Send the statement and lock the account. The group receives the document with every line visible. From that moment, any change requires a new credit note, not an edit.

An illustrative example with numbers

The figures below are invented to show the calculation. They are not from any hotel or any group; they only serve to follow the seven steps with a calculator.

An example group contracted dinner for 24 people at 380 per person, with a guarantee with 90 % tolerance. Twenty-two arrived. During dinner they ordered six bottles of wine at 420 each, approved by the group coordinator. At signing they left a deposit of 4,000.

The guaranteed minimum is 24 × 0.90 = 21.6 people. Since actual attendance was 22, and 22 is greater than 21.6, 22 are billed. The no-show adjustment is 2 people × 380 = 760, negative. Had 20 arrived, the minimum of 21.6 would round up to 22 and the adjustment would have been the same: the tolerance protects the hotel exactly there.

Look at what the adjustment line achieves. The group sees that 24 were contracted, that two no-shows were recognized and that 22 were billed, exactly what the contract says. The controller sees that the kitchen prepared 24 menus at a cost of 24 and that revenue was for 22, with 760 explained. And nobody had to recapture anything: the original is still there, with one line on top.

The adjustment line: anatomy of a good one and a bad one

A well-captured adjustment answers five questions without anyone having to pick up the phone: how much, why, who approved it, when, and against which original line. A badly captured adjustment answers only the first and leaves the other four for next week’s argument.

• Good: "No-show adjustment: 2 people × 380 = -760. Actual attendance 22 of 24, confirmed by captain and coordinator at 21:10. Approved by: F&B manager."
• Bad: "Discount -760." No reason, no name, no time. On Monday the group asks whether it was for the no-shows or for a service complaint, and nobody knows.
• Good: the adjustment points to the line "Contracted dinner 24 × 380" and the system shows the net of the two together.
• Bad: the adjustment was applied as a percentage of the total, wine included, and now the discount is larger than the two dinners that were never served.
• Good: the adjustment has its own type ("no-shows") that the controller can add up at month-end to know how much the hotel did not bill for this reason.
• Bad: the adjustment was recorded as a courtesy, and in the monthly report it looks as if the hotel gave away two dinners by choice.

When the group also stays at the hotel

Many groups that dine in the hotel restaurant also sleep in the hotel, and no-shows at dinner are usually no-shows in the rooms. Here you need two master accounts that talk to each other: the room block’s, managed by the front desk, and the food and beverage event’s, managed by the restaurant. The person who did not arrive has to be missing from both, with the same reason and the same date.

If the group contract also covers individual consumption, such as next morning’s breakfast, those charges are born on each guest’s folio and transferred to the master account with a reason. And if the absent person had a reserved room that was billed under the cancellation policy, that charge belongs to the block’s account, not the event’s. Mixing them produces a statement the group cannot read and therefore does not pay on time. The groups and banquets page (Groups and banquets) describes how the two accounts are kept apart.

What the controller checks before locking

Closing a group does not end when the statement is printed. It ends when the controller checks it against three sources and locks the account so nobody can edit it afterwards. The three sources are the contract, the confirmed attendance and the kitchen’s consumption for the night.

Against the contract, the controller verifies that the price per person, the guarantee and the deposit match. Against attendance, that the billed count respects the guarantee and that the adjustment line has a reason and a signature. Against the kitchen, that the menus prepared were the ones contracted, so the day’s food cost is explained by the adjustment and does not look like waste. When all three reconcile, lock. When they do not, the account stays open with a note, and the statement is not sent until it is resolved.

That lock matters more than it seems. A statement that can be edited after it is sent is a worthless document: the group does not know whether what it received is still true, and the hotel cannot prove what it sent. A locked account with subsequent credit notes, on the other hand, tells the whole story in order.

What to do this week

1. Open the contract for the next group and find the guarantee clause. If it does not exist or does not state a percentage, fix it before the group arrives.
2. Define with the food and beverage manager who can approve a no-show adjustment and up to what amount without going through the controller.
3. Create in the system an adjustment type called "no-shows", separate from courtesy and discount, so the monthly report shows it on its own.
4. Agree with the captain and the front desk on the exact moment attendance is counted and who signs the account. Without that moment, the figure is always debatable.
5. Review the last three group closings and look for adjustments without a reason or recaptured accounts. Each one is revenue that was probably billed wrong.
6. Prepare the statement template with the seven lines from the example, so the next closing is filled in rather than improvised.

Inn Restaurant keeps the group’s original statement, applies the contract guarantee and captures the no-show adjustment as a line with a reason and a signature, so the balance explains itself. If you want to see the full closing with a test group, the fifteen-minute demo is scheduled on the contact page (contact).