Tax on consumption posted to the folio: where it is declared and where it is collected

A hotel restaurant has a kind of sale no street restaurant knows: the one collected somewhere else, at some other time. The guest has dinner, says “To my room, please,” and the money comes in three days later through the front desk cashier. The dinner is clear. What gets tangled is the tax: who calculated it, on what base, whether the front desk applies it again, and who declares it at the end of the month.

Two moments, one tax

A charge posted to the room has two moments. The first is the sale: the server closes the check in the restaurant point of sale, the system calculates tax on the taxable base, and the ticket carries subtotal, tax and total. The second is the collection: the guest checks out, the front desk presents the folio with the room and every consumption, and collects the total.

The tax is born in the first moment and collected in the second. It is never calculated twice. That is the whole principle, and almost every problem in this area comes from forgetting it: the front desk recalculates what the restaurant already calculated, or the restaurant sends an amount without tax and the front desk does not add it, or the folio blends the hotel’s two rates into a single line.

If your hotel handles room charge as a text field where the server types a number, the amount arriving at the front desk most likely does not say whether it includes tax. So each receptionist decides. That is what has to go.

The folio does not calculate: it receives

The guest folio is a statement of account. It accumulates lines: the rate for each night, the lodging tax, Tuesday’s dinner, Wednesday’s breakfast, Thursday’s pool bar. Every line arrives already calculated by the system that generated it. The rate was calculated by the front desk system; the dinner was calculated by the restaurant point of sale.

That is why the restaurant line must reach the folio with three figures, not one: taxable base, tax and total. If only the total arrives, the front desk cannot itemize the invoice at check-out without recalculating, and recalculating goes wrong whenever the ticket carried products at different rates. If only the base arrives, someone has to remember to add the tax, and one day nobody remembers.

A verified charge, tied to the guest’s real folio rather than a typed room number, travels with its full breakdown. How that charge is built is explained on the room charge page (Room charge). Here we care about what happens when it lands.

The hotel’s rates are not the restaurant’s rates

A hotel usually lives with more than one rate. The room pays the general consumption tax and, in many places, an additional lodging tax that applies only to the room rent. The restaurant pays the general consumption tax, and in some places alcoholic beverages carry a different rate or a special excise separate from food. None of those rates is applied on top of another.

The most expensive error we have seen in operation is lodging tax applied to restaurant consumption. It happens when the front desk system treats every folio line as if it were room rent. The guest overpays without noticing, and the hotel declares and remits a tax on a base that does not exist. When the controller catches it months later, returns must be corrected and money refunded to guests you can no longer find.

What every folio line must know about itself

• Its origin: front desk, restaurant, bar, room service, pool bar, minibar or banquet. The revenue center defines the department under USALI and defines which rates apply.
• Its taxable base, with discounts and comps already deducted. What was given away is not taxed.
• Each tax separately, with its rate. A ticket with food and alcoholic beverages may carry two different taxes inside one folio line.
• The tip, outside the base. The tip is not hotel revenue and does not carry the sales tax.
• The total the guest will pay, which is the sum of the above and nothing else.

Who declares: one entity or two

There are two scenarios here and it pays to know which one your hotel is in, because it changes everything that follows.

Scenario one: the hotel and the restaurant are the same legal entity. It is the most common case in independent hotels and boutique hotels. The restaurant’s sale is the hotel’s sale, the tax is declared by the hotel, and the invoice the guest receives at check-out comes from a single issuer with every item broken out. The restaurant declares nothing on its own; it hands its sales to the controller and the controller consolidates.

Scenario two: the restaurant is operated by another entity. A concessionaire, a chef with their own company, a partner renting the space. Here the dinner tax is declared by the restaurant, not the hotel. When the guest posts to the room, the hotel only collects on the restaurant’s behalf and passes the money along later. The folio shows the line, but the invoice for the consumption is issued by the restaurant. If the hotel issues one invoice for everything, it is invoicing a sale that is not its own, and that creates a tax problem for both.

In scenario two, the restaurant system has to leave a trail of which tickets were collected through the folio, how much tax each carried, and when the hotel settled with the restaurant. Without that trail, the monthly reconciliation between the two entities turns into a spreadsheet argument. The hotel controller and the restaurant accountant must be able to read the same report; the controller page (Controller) shows what that report of charges pending settlement looks like.

An illustrative example with numbers

The figures below are made up to show the calculation. The rates are made up too; use the ones that apply in your country and your city. The point is to see where the tax gets duplicated and what it costs.

On the correct folio the guest pays 4,450. On the folio with both errors the guest pays 4,740: 290 too much for a single night with a single dinner. If that hotel posts fifty dinners a week to rooms with the same mechanics, that is 14,500 overcharged every week, declared on a base that does not exist and, in the best case, refunded with an apology letter. In the worst case, discovered by the accountant of a company with a corporate agreement who reviews every invoice.

Notice the detail: the dinner reached the folio as 1,450, a total with tax included. The front desk saw a number, assumed it was a base and applied its rates. Nobody acted in bad faith. The system never told the front desk that the number already carried tax.

Tax is not revenue: what USALI says

The hospitality accounting standard is clear: the tax you collect is not your revenue. It is money you collect on behalf of the authority and will hand over. The restaurant’s revenue is the taxable base, net of discounts and without tips. If your restaurant sales report adds the tax, your food and beverage revenue per occupied room is inflated, and every comparison you make against another period or against budget is wrong.

This has a practical consequence for room charge: the restaurant report must show the net sale of every ticket posted to the folio, and the front desk report must show the total collected with tax. The two numbers are different and both are correct. The controller reconciles them by adding tax to the first or subtracting it from the second. If either system blends base and tax, the reconciliation does not balance and nobody knows why.

The invoice at check-out

The guest wants one invoice. The corporate traveler, above all, needs dinner to appear on the same document as the room so the company reimburses it. That is reasonable, and in scenario one it is easily met: one invoice, several items, each item with its rate.

What is not reasonable is an invoice showing a single line that says “lodging” with the folio total. When dinner hides inside the room line, lodging tax is calculated on a base that includes food, and the itemization the tax authority requires disappears. The front desk system must preserve the origin of each line all the way to the invoice, and the restaurant point of sale must have delivered the breakdown from the start.

The three most frequent invoice errors

1. A single lodging line with everything inside. The breakdown is lost and a rate that does not belong is applied to the food portion.
2. A hotel invoice for consumption at a restaurant that is a separate entity. A sale that belongs to someone else gets invoiced.
3. Tip included in the taxable base. Tax is charged on money that is not a sale.

What to check in your operation

You do not need an auditor to know whether you have this problem. You need three tickets and a folio. Take three room charges from last week, with different products, and follow each one to the guest’s invoice.

• The restaurant ticket shows base, tax and total separately.
• The folio line shows the same total as the ticket, not one unit more.
• The invoice itemizes the dinner at its own rate, separate from the room.
• The lodging tax, if your city has one, appears only on the room rent.
• The restaurant sales report records the net base of those three tickets, not the total with tax.

If any of the five points fails, you have a tax leak that repeats on every room charge. And since room charge is the most important sale a hotel restaurant makes, the leak is proportional to your success. The more your guests dine with you, the bigger the problem. There are other leaks like it in the article on the eight places where consumption gets lost in a hotel (The eight places where a hotel loses food and beverage revenue).

What to do this week

1. Take three room charges from last week and follow each from ticket to invoice. Write down at which step the breakdown gets lost.
2. Ask your accountant whether the hotel and the restaurant are the same tax entity. If they are not, check who is issuing the invoice for dinners posted to the folio.
3. Verify that your city’s lodging tax, if it exists, is not being applied to any food and beverage line.
4. Confirm that the restaurant sales report shows net base rather than total with tax, and that the controller reconciles against that number.
5. Write the tax flow for room charge on one page: who calculates, who collects, who declares. Post it at the front desk and at the restaurant cashier.

Inn Restaurant sends every room charge to the guest folio with base, tax and total broken out by rate, and the restaurant report records net sales the way USALI asks. If you want to see what a ticket posted to the folio looks like and how the front desk reads it, book the fifteen-minute demo (contact).