Every rupee has two sides
The night audit closes into a double-entry general ledger — per legal entity, with a chart seeded for a hotel, control accounts that must agree with the sub-ledgers, and no journal that does not balance.
"Have we added an accounting module?" We had not. Every rupee already flowed through one pipe — the folio posting, typed and categorised, settled by a named tender, closed by the night audit; the restaurant's bills; a corrected invoice through a credit note. What the books could not do was hold the other side of each of them.
The ledger
A chart of accounts seeded for a hotel — rooms revenue, food revenue, the tax liabilities by slab, the tender control accounts, receivables, payables, the bank — and a journal per closed day, written by the night audit and the outlet's day end, every line to an account, debits equal to credits or the journal is refused.
A book belongs to a legal entity
A hotel group is a holding company and its hotels are companies of their own, each with a PAN, a set of statutory books and a balance sheet the auditor signs. The ledger is per entity; a hotel belongs to one; two hotels of one company share a book.
Control accounts that must agree
Receivables, payables, the gateway, the bank, each tender: the control account in the ledger is checked against the sub-ledger it summarises, and the check is a report that says where they differ, to the rupee.
What is read from it
Trial balance, profit and loss, balance sheet, the general ledger by account, the journal by day — and every export to the accountant's own system.