GST for hotels: rooms, F&B, and the composite supply trap

Hotel GST is not complicated in principle. It goes wrong in practice for three structural reasons, and all three are fixable by architecture rather than by effort. This is a working explanation, not tax advice — your accountant remains the authority on your own return.

1. A hotel bill is not one kind of supply

A single folio routinely mixes a room night, a restaurant order, a laundry charge and possibly a banquet. These do not all sit at the same rate, and the room rate itself is banded by tariff. The moment a human being chooses the slab when posting a charge, a human being will eventually choose wrong — usually the default, usually the room slab, usually on the busiest night of the month.

The structural fix is to attach the slab to the charge type, not to the person posting it. In StayFlint a kitchen order posted to a room is taxed at the F&B rate because of what it is, and nobody is asked.

2. Room plus meals is ONE supply, not two

This is the mistake worth checking on your own bills tonight. When a room is sold with meals included — CP, MAP, AP — it is a composite supply. The room is the principal supply, and the correct treatment is a single tax line at the room slab, calculated on the combined value — and that combined value is also what decides which room-rate band applies.

Building the package price by taxing the room at the room rate, taxing the meals at the F&B rate, and adding the two together produces a different number. It is usually a smaller number, which is why it survives so long without anybody noticing.

StayFlint prices meals per head per night on top of a per-room rate and then taxes the combination as one supply, which is what meal plans are for.

3. The return should not be a rebuild

The common architecture is a billing package that issues invoices and an accounting package that produces returns, with a monthly reconciliation in between. Those two sets of numbers were never going to agree on their own, so somebody spends the first week of every month making them agree.

The alternative is one set of books. If the folio, the invoice, the night audit and GSTR-1 all read the same double-entry ledger, there is nothing to reconcile — the return is a view, not a rebuild. That is also what makes GSTR-3B honest after set-off, and what lets the system explain why an input credit was blocked instead of quietly dropping it.

The three questions to ask in a demo

1. Show me a folio with a room night and a restaurant order, and show me the two different slabs applied without anybody choosing them.
2. Sell me a room with meals for two and show me the tax lines. There should be one per night, at the room slab, on the combined value.
3. Show me GSTR-1 coming out of the same ledger the night audit closed this morning — not an export I have to reconcile.

If a vendor can do all three live, the tax side of the product is real. If tax is a separate export from a separate system, you are buying two products and a monthly reconciliation job.