GST invoices
Room and F&B at their own slabs, applied by the charge type rather than chosen by a person.
Most hotel billing packages produce invoices and then hand the returns to a spreadsheet. StayFlint keeps a double-entry ledger underneath the hotel, so the invoice, the night audit and GSTR-1 are three views of the same books rather than three separate jobs.
The problems owners describe to us — and what StayFlint does about each one.
✕ Room and F&B sit at different slabs, and one of them gets applied by hand.
→ Each charge type carries its own slab and the invoice applies it — a kitchen order posted to a room is taxed at the F&B rate without anybody choosing.
✕ Room-plus-meals packages are taxed as two things, which is not what the return expects.
→ Room plus meals is treated as one composite supply: a single tax line per night at the room slab, on the combined value, which also decides the slab.
✕ GSTR-1 is rebuilt at month end from a report that came out of a different system.
→ GSTR-1 and GSTR-3B come out of the same ledger the night audit closes every morning — after set-off, with input credit shown and a reason given when it is blocked.
✕ Bank entries and the books drift, and reconciliation is a monthly archaeology exercise.
→ Bank reconciliation is part of the night's close, not a separate month-end project.
✕ TDS is remembered rather than recorded.
→ TDS is tracked in the ledger with Form 26Q produced from it.
Everything below is live today — nothing on this page is a promise for later.
Room and F&B at their own slabs, applied by the charge type rather than chosen by a person.
From the same double-entry ledger the night audit closes — 3B after set-off, with input credit and a reason when it is blocked.
Part of the close rather than a month-end archaeology exercise.
Tracked in the ledger and produced from it, not reconstructed from memory.
The reason hotel tax goes wrong is almost always architectural: the billing system and the accounting system are different systems, so every month somebody reconciles two sets of numbers that were never going to agree. StayFlint has one set of books. The folio, the invoice, the night audit and the return all read it.
Composite supply is the specific case worth checking in any demo. A room sold with meals is one supply, taxed once at the room slab on the combined value — and a package price built by adding two taxed components produces a different, wrong number.
Short, straight answers — and a person on WhatsApp for the rest.
Yes, from the same double-entry ledger the night audit closes each morning — not from a separate export that has to be reconciled against the invoices.
As one composite supply: a single tax line per night at the room slab, calculated on the combined value, which also determines the slab. It is not two taxed components added together.
Yes, and when a credit is blocked the system gives the reason rather than silently dropping it.
Yes — TDS is tracked in the ledger and Form 26Q is produced from it.
Yes. Accountant is a role with its own screens — the ledger, reconciliation, corporate accounts and returns — without giving away the rest of the hotel.
No call centre and no sales script — you reach the team that writes the software. Tell us your hotel's size and what you run today; we'll tell you honestly whether StayFlint fits.
The rest of the system these pieces sit inside.
A booking engine is only worth having if it shares one calendar with the front desk. Bolt a separate widget onto a websi…
The front desk is where a hotel earns its reputation and loses its evening. Everything here is built around one measurem…
A resort is not a hotel with a garden. Guests arrive on a package, eat every meal on site, spend across several outlets,…
The full picture — every module, how it is priced, and the city pages.
One WhatsApp with your property's name and room count is enough. We move your existing bookings and guests across before you go live, at no charge.