The report the hotel controller wants on the first of the month, and why it arrives on the eighth

On the first day of the month the hotel controller needs the food and beverage close to build the income statement, pay commissions, invoice corporate agreements and answer the owner. And on the first day of the month, what the controller has is a promise. The report arrives on the eighth, and every day of delay has a concrete cause that can be removed.

What the requested report contains

• Net revenue by outlet: restaurant, bar, room service, pool, events, without tax or tips.
• The month’s room charges reconciled against front desk folios, with zero unexplained differences.
• Shift closes for every outlet with cash, card, folio charges and comps balanced.
• Comps and discounts with reason and approver, because they lower revenue and raise cost.
• Corporate agreement consumption by account, to invoice each company what its people consumed.
• Food and beverage cost for the month: opening inventory, purchases, closing inventory.
• Metrics: revenue per occupied room, capture, average check, covers, by outlet.

None of those pieces is hard on its own. The problem is that they live in different systems, with different cut-offs, and someone has to balance them by hand. That someone is almost always the most expensive person in the administrative department.

Anatomy of the eight days

What the table shows is that the close is not slow because of accounting. It is slow because operations did not leave the month closed. Every day is a dependency between one system that knows one part and another that knows the rest.

The dependency that eats the most days: charge reconciliation

When the room charge is a text field where the server types “214”, the point of sale does not know whether 214 was occupied, whether the guest had already checked out, or whether it was actually 241. The front desk receives the charge, attaches it to whatever folio it finds, or leaves it in a suspense account. At month end, someone has to go check by check.

A charge verified against the stay removes that reconciliation at the source: the charge is born on the right folio or it is not born at all. Another article explains why a text field is not enough (Room charge: why a text field is not enough). What matters for the close is that reconciliation stops being a task and becomes a verification that the differences are zero.

An illustrative example of the time it costs

Invented figures to show the calculation. A hotel with 1,800 room charges a month and 3 % problem charges has 54 cases to trace. If each one takes 10 minutes between finding the check, calling the front desk and correcting, that is 540 minutes: nine hours of someone who knows what they are doing, spread over two or three days because nobody has them back to back. If the system does not let a charge leave without a current folio, the 54 cases go to zero and so do the nine hours.

The other dependencies, one by one

Shift closes on paper or in different systems

If the pool bar closes in a notebook and the restaurant closes in the point of sale, the controller receives two formats and one difference. A close by outlet in the same system, with the same closing time, leaves the first of the month with every close already balanced. The guide to the shift close by outlet (A guide to the shift close by revenue center in a hotel) explains the full procedure.

Corporate agreements identified by hand

The company with an agreement that caps dinner per person needs an invoice with the detail. If the check only has the company name in a note, someone has to look for it. If the corporate account exists in the system and the check is linked to it at the moment of charging (Master accounts and agreements), the statement generates itself and the invoice goes out on day one.

Comps without a reason

A comp without a reason or an approver is a pending question. With reason and approver captured at the moment, it is a line on the report. The difference between the two is a day of the close and, over time, a leak nobody sees.

Inventory and cost

Cost of sales requires closing inventory, and inventory is counted when the month closes. This is the only thing that legitimately takes a day. What can be done is having the month’s purchases already captured and the opening inventory closed, so the day-one count is the only task left.

How it shrinks to one day

1. A daily close that leaves the day reconciled. If every day closes with verified charges, balanced closes and comps with reasons, the monthly close is the sum of thirty days already closed.
2. Room charge tied to a current folio, with no free text field. Zero orphan charges means zero reconciliation.
3. One cut-off date and time for every outlet and for the front desk, agreed in writing.
4. Corporate accounts in the system, with the check linked to the account from the moment of consumption.
5. Mandatory reason and approver on comps and discounts.
6. Purchases captured in the week they arrive, not at month end.

With that, on day one the controller opens the report, verifies that the differences are zero, receives the inventory count and closes. Day one is no longer a promise: it is a verification. And the most expensive person in the administrative department gets a week back every month for analysis instead of balancing.

What you hand the controller on day one

One sheet per outlet with net revenue, reconciled folio charges, comps with reasons, agreement consumption by account and the month’s metrics against the previous month and the same month last year. And one line that says: unexplained differences, zero. That line is what gives the controller the week back.

If the hotel reports under the hospitality standard, the same sheet slots into the food and beverage department with its outlets as lines, without re-keying anything. If it does not yet, the sheet is the first step toward getting there without changing accountants.

A close that arrives on the eighth is not an accounting problem. It is an operations problem that accounting discovers late.

What to do this week

1. Ask the controller what day the last food and beverage close arrived and where each day went. Write it down in a table like the one above.
2. Count the room charges from last month that needed correction. That number, times ten minutes each, is the cost of reconciliation.
3. Check whether every outlet closes at the same time as the front desk. If not, agree on a time and put it in writing.
4. Review how many of last month’s comps have no captured reason.
5. Pick one change from the list of six and apply it from the first day of next month.

Inn Restaurant closes the day with charges verified against the folio, closes by outlet and comps with reasons, so the monthly close the controller needs (Controller) is ready on day one. If you want to see what your hotel’s would look like, request the 15-minute demo on the contact page (contact).