What a master account is in a hotel and which restaurant charges belong in it

A twenty-room group arrives at your hotel on a Tuesday. They are there for a company training, and the company pays. In the restaurant, the first dinner ends with the question that defines the week: “does this go to the group account or are you charging me?”. If the server answers from memory, or asks the guest, the hotel will argue that answer with the company when the statement arrives. The master account exists so that a rule answers that question, not a person.

What a master account is

A master account is a folio that belongs not to a guest but to a group, a company or an event. It gathers rooms, function spaces and consumption that a third party will pay, and it has its own rules: what can be charged, up to how much, who approves it and how it is settled. It lives from the moment the group contract is signed until the company pays the statement, and it can last much longer than any guest’s stay.

What sets it apart from the personal folio is simple: the personal folio is paid by the person sleeping in the room; the master account is paid by someone who is almost never at the table. That distance between who consumes and who pays is why the master account needs written rules, not just a name at the front desk.

When a master account exists

Large groups are not the only ones that have one. Almost any hotel with a restaurant opens master accounts several times a month, even if it does not call them that.

• Groups with blocked rooms: conventions, training courses, sports teams, airline crews. The company or the organizer pays for lodging and, sometimes, certain meals.
• Weddings and social events: the family or the couple pays for the venue, the banquet and a block of rooms; the guests pay for everything else.
• Permanent corporate agreements: the company has an account open all year, and every traveler who arrives with a booking hangs from it under the terms of the agreement.
• Agencies and tour operators: the agency pays for lodging and the contracted meal plan; the guest pays for any consumption outside the plan.

In all four cases there are two different payers for the same person sitting at the same table, and the restaurant has to know, when the check closes, which of the two owns each line. The company accounts page (Master accounts and agreements) describes how that split is configured by category.

The border between the master account and the personal folio

The hotel does not define the border; the group contract or the company agreement does. But there is a pattern that repeats in most agreements, and it serves as a starting point when the contract says nothing.

The rule that avoids the most disputes is the one on alcohol: to the personal folio unless the contract says otherwise. The second is the cap per person per day: what fits under the cap goes to the master, what exceeds it is separated on the same check and goes to the folio of whoever consumed it. The piece on how to write a corporate agreement (How to write a hotel corporate agreement that does not end in a dispute) explains how to put those two rules in writing before the group arrives.

The rules every master account must have

A master account without rules is an open folio anyone can post to. Before the first guest of the group arrives, the account must have five things defined and captured in the system, not in the manager’s memory.

1. Who approves. The group coordinator, by name, and a second person in case the coordinator is away. Nobody else can approve a charge the contract does not cover.
2. Which categories are in. Food yes, alcohol no, room service no, for example. Defined by product category, not by dish, so the rule keeps working when the menu changes.
3. Up to how much. A cap per person per day, or per event, or a global cap for the whole stay. The system checks it on every check close and separates the excess.
4. At what hours and in which revenue center. The group dinner in the restaurant is in; the same dinner at the pool bar at midnight is not.
5. How it settles. Thirty-day credit, deposit with a running balance, or payment at the close of the event. And who at the company receives the statement.

With those five rules captured, the server decides nothing. Pick the room, the system knows the room belongs to the group, applies the rule to every line of the check and separates what goes to the master from what goes to the personal folio. If the coordinator wants an exception, it is approved with a code and recorded with a reason.

How it should flow in the restaurant

At the table, the correct flow has three steps and none depends on the server remembering the contract. First, the server identifies the guest’s room, as with any room charge. Second, the system shows that the room belongs to the group’s master account and what it covers. Third, on closing, the check splits itself: covered lines go to the master and the rest to the personal folio, and the guest signs only for theirs.

What to avoid is the reverse flow, where the server closes everything to the master “because it is the group” and the controller separates it by hand at the end. That work, done a week later with paper tickets, is where the adjustments the company will question are born. The groups and banquets page (Groups and banquets) shows how the master account looks from the point of sale when the split happens at the table.

An illustrative example with numbers

The figures below are invented to show the calculation and belong to no hotel and no client. Picture a twenty-room group, one person per room, three nights, with this contract: breakfast and dinner to the master account with a cap of 500 per person per day; alcohol and room service to the personal folio.

Now picture that one night one of the guests has a 700 dinner instead of 300. With the cap of 500 per day and a 150 breakfast already consumed, 350 remained for dinner. The check splits at the table: 350 to the master and 350 to the personal folio. The guest signs for 350, the company sees 350, and nobody argues at the end because the rule was applied when it happened, with the ticket in front of everyone.

Without the rule in the system, that same consumption would have been charged in full to the master, the company would have received a statement for 27,350, and the coordinator would have asked for an explanation of the 350 in an email the hotel takes a week to answer.

Frequent mistakes with the master account

• Opening it the day the group arrives. It should exist from the moment the contract is signed, so that deposits, the room block and the coordinator’s first consumption land in it from the start.
• Defining the rules by dish instead of by category. When the menu changes, the rule stops applying and nobody notices.
• Letting the guest decide at the table what goes to the master. The guest does not know the contract and will always prefer the company to pay.
• Posting everything to the master and separating later. Adjustments made days later, without the ticket, are the ones the company questions.
• Not naming who approves exceptions. Without an approver, every server ends up being one.
• Sending the statement without detail by room and by day. The company needs to match it against its attendee list, and if it cannot, it does not pay.

At the close: the statement the company will review

The master account ends in a document: the statement the company receives. It is the moment when everything done right or wrong in the restaurant becomes visible to someone outside. A good statement shows every charge with date, revenue center, room and person, grouped by day, with adjustments and their reasons in plain view, and with the cap applied line by line.

If the statement is a single figure per item, the company will ask for the detail, and the hotel will take days to assemble it. If the detail comes out of the system exactly as it was recorded at the table, the company matches it against its list in an afternoon and pays. That difference, between collecting in thirty days or in ninety, is the financial argument for a well-run master account.

What to do this week

1. Take the next group arriving at your hotel and read its contract looking for the five rules: approver, categories, cap, hours and settlement. Note the ones that are missing.
2. Write the alcohol rule and the room service rule in one line each and confirm them with the coordinator before arrival.
3. Capture the master account in the system with those rules before the first guest arrives, not on arrival day.
4. Check how the group’s rooms look on the server’s screen: if they do not say they belong to a master account, the server will decide from memory.
5. Pull the last statement you sent to a company and count how many clarification emails it generated. That number is your starting point.

In Inn Restaurant the master account lives from the contract, with rules by category, cap and approver that the system applies on every check at the table, separating what goes to the company from what goes to the corporate traveler’s personal folio (Corporate traveler). If you want to see a group dinner split at the moment and how it reads later on the statement, the fifteen-minute demo (contact) shows it with a sample group.