Comps posted to the folio: how to record them so they leave a trail instead of a hole

A hotel restaurant gives food away every day, and almost always for a good reason: the guest waited forty minutes, the manager hosted the agency that brings groups, the general manager had dinner with a supplier. Giving is not the problem. The problem is that in many hotels the comp is settled with a word to the server and never reaches the folio or the report. At month end the food cost went up, sales did not, and nobody can explain the gap.

What a comp is and what it is not

A comp is real consumption the hotel decides not to charge. The dish was cooked, the drink was poured, the table was occupied and the server did the work. The only difference from a normal sale is that the hotel absorbs the amount instead of the guest. That is why a comp carries exactly the cost of a sale and a revenue of zero.

It helps to separate it from three things that look like it. It is not a commercial discount, which lowers the price but still collects something. It is not a void, which belongs to an item that was never consumed or was rung by mistake. And it is not the breakfast included in the rate, which is already paid inside the room price even though the folio shows it at zero. Each of those four figures is recorded differently and lands on a different line of the report.

When the point of sale folds all four into a single “no charge” button, the controller gets a number that cannot be read. When the comp has its own record type, with its reason and its author, the same report says how much was given away, why, and who decided.

The three kinds of comp that exist in a hotel

In practice almost every comp in a hotel restaurant falls into one of three families. Naming them in the policy is worth the effort, because each has a natural approver and a different reasonable limit.

• Service recovery: the guest had a bad experience and the hotel makes up for it. A dessert, a bottle of wine, the whole dinner. The manager on duty approves it, and the reason should describe the problem, not just say “complaint”.
• Business relations: the sales manager hosts the agency, the wedding planner or the coordinator from the company with a corporate agreement. Sales or general management approves it, and the reason should name the account being courted.
• Internal consumption: management, partners or the owner eat at the restaurant. It is not a sale and not a complaint; it is a hotel expense that must be flagged as such so it does not contaminate either the sales or the cost of the revenue center.

A fourth family, the employee meal, in most hotels does not go through the restaurant but through the staff canteen. If in your hotel it does go through the restaurant, treat it as internal consumption with its own reason code.

Why an unrecorded comp costs twice

The first loss is the obvious one: the cost of the dish left the storeroom and no sale replaced it. The second is less visible and more expensive: without a record, the month’s food cost rises with no explanation. The chef insists there was no waste, the manager swears nothing was given away, and the controller ends up adjusting inventory by hand to make it balance. That adjustment also hides theft, receiving errors and over-portioning.

A third loss shows up over time: the informal comp becomes a habit. What started as a manager’s gesture ends up as a right that servers claim for their tables, the captain’s friends and the front desk’s acquaintances. When the comp leaves a trail, the gesture still exists but stops being invisible, and that alone moderates it.

The five pieces of data every comp must carry

A well-recorded comp is a one hundred percent discount applied to a check that already existed, with five mandatory fields. If any is missing, the check should not close.

1. Who approved it. Not who keyed it. The server applies the comp because someone with permission approved it, and the system must ask for that person’s code or fingerprint at the moment.
2. Why. A reason picked from a short list (service recovery, business relations, internal consumption) plus a one-line free note. The list is for adding up; the note is for understanding.
3. How much. The menu value of what was given away, before the discount. If the comp is recorded at zero from the start, you will never know what it was worth.
4. To whom. The guest folio if the person is staying, the company account if it is a guest of the agreement, or an internal hotel account if it is management consumption. A comp with no destination is a sale that evaporated.
5. Where. The revenue center: restaurant, bar, pool, room service. The late bar has a different relationship with comps than the breakfast coffee shop, and the report has to be able to separate them.

What happens on the guest folio

This is the part many hotels get wrong. A comp to an in-house guest must reach the folio as a charge with value and, in the same operation, a discount for the same amount. The folio balance does not change; the guest pays nothing. But the folio shows the gesture: “Dinner, compliments of the hotel, 0.00”. That has two effects an omitted charge never has.

The first is commercial: the guest sees, in writing, that the hotel gave something. A service recovery nobody sees recovers nothing. The second is control: the night auditor can match every restaurant comp against a real folio, a live stay that night and an approver with permission. A comp to an empty room is an alarm that only rings if the comp went through the folio, as the room charge page explains (Room charge).

When the guest is not staying at the hotel, the destination is the company account under the agreement or the internal account. The mechanism is the same: charge with value, discount for the total, zero balance, full trail. What must never exist is a check closed “as a comp” with no destination, because that is the one a server can open for his own table.

An illustrative example with numbers

The figures below are made up to show the calculation. They do not describe any real hotel. Picture a sixty-room hotel, one month of operation and a restaurant that recorded every comp with a reason.

With a complete record, the controller now knows three things. The hotel gave away 12,600 at menu value, that cost 4,410 in ingredients, and almost half of the value given away was for service complaints. That last one is the most useful: eighteen service recoveries in a month is not a restaurant problem, it is an operations problem someone needs to go and look at.

Without the record, those 4,410 would show up as a food cost variance, and the conversation in the meeting would be about waste and portions, not about the eighteen complaints.

What the report should show and the controller should check

The next-day comps report is short and takes five minutes if it has the right structure. The reports page (Reports) shows how it is built under the hospitality standard; what follows is what the controller should look for in it every morning.

• Comps by approver: if one person concentrates most of them, ask why.
• Comps by revenue center: the late bar is usually where the most is given away and where the least trail used to remain.
• Comps with no folio or destination account: should be zero. Each one is a direct question to the shift manager.
• Comps to rooms that were not occupied that night: also zero, and if one appears, it is the morning’s priority.
• Repeated reasons with the same note: “complaint” ten times with no detail is a policy nobody is following.
• Month-to-date value against the limit management set, by comp family.

The comp policy on a single page

You do not need a manual. You need one sheet that says who can approve each family, up to what amount per event, up to what amount per month, and which reason gets captured. That sheet is signed, pinned in the manager’s office and configured in the point of sale as permissions, not as goodwill. Three or four people in the hotel hold the permission to apply a comp; everyone else can request one, not apply it.

A sensible policy also says what is not a comp. The dessert a server gives away “because they were leaving” is not a service recovery, and if the manager did not approve it, it is deducted from the server or recorded as internal consumption under his name. It sounds harsh, but it is what makes the policy real.

What to do this week

1. Write on one sheet the three comp families in your hotel, who approves each and the cap per event and per month.
2. Check who currently holds the permission to apply one hundred percent discounts in the point of sale and remove it from anyone not on the sheet.
3. Configure the short list of reasons and make the one-line free note mandatory.
4. Ask the night auditor to add the day’s comps to the morning review, alongside room charges.
5. At month end, compare the value of comps against food cost and take the result to the meeting with the chef and the manager.

In Inn Restaurant a comp is a discount with permission, reason and author that reaches the guest folio or the destination account and appears in the next morning’s report, the one the controller reviews (Controller). If you want to see how one is approved at the table and how it reads the next day, the fifteen-minute demo (contact) starts right there.