Night audit reports explained: trial balance, manager's flash and the exception lists

Night audit reports are the documents a hotel produces when it closes its business day: balance reports that must agree with each other, revenue and payment reports that explain where the money came from, and exception lists that name what a person changed by hand. Each report answers one question and has one named reader the next morning.

At seven in the morning the pack is on the desk: a dozen pages, a business date on each, and a line for a signature. It is often signed before anyone has read past the totals, which means nobody read the only pages that would have caught yesterday's problem. After reading this article you will know which page answers which question, who must read each one, and in what order to read them.

What are night audit reports?#

They are the output of closing the business day: a fixed set of documents that prove the day's money balances and hand the morning its exceptions. They are a byproduct of closing, not extra work on top of it.

The business date is the day the hotel is accounting for, and it is not the clock date. It rolls forward only when night audit closes it, so every page in the pack must carry the same business date. A page printed at 23:58 and a page printed at 00:05 can belong to two different business days, and the pack must be consistent about which.

The pack has three families. Balance reports ask whether everything agrees. Revenue and payment reports ask what the money was and how it arrived. Exception reports ask what a person changed by hand. Each report has one named reader: the night auditor signs it, the income auditor checks it, the front office manager reads the operational ones, the general manager reads one page.

Format matters more than length. The same order every night, exceptions before totals, the business date and page number on every sheet, and a signature with the time it was signed. A report nobody reads stops being checked within a month, and the numbers on it drift without anyone noticing.

The order of work that produces the pack is a separate subject, covered in the night audit checklist: closing the hotel business day in order.

Which balance reports must agree before you close the day?#

The trial balance, the guest ledger, the city ledger and the deposits account must agree with each other and with the day's postings. If they do not, nothing printed above them can be trusted.

The trial balance lists every revenue and payment account with its debits and credits. It must net to zero, and each revenue line must match the departmental report that explains it. The guest ledger is the total of open in-house folios, and that total must equal the control figure the system carries; a folio left open is a balance that will still be moving tomorrow.

The city ledger holds charges moved to companies and travel agencies. A transfer must be a matched pair, out of the guest folio and into the receivable, never a deletion from one side. Deposits and advance payments are money received for stays that have not happened yet: they are a liability, not revenue, and must not be netted off against today's sales.

Foreign-currency folios must be converted at one rate used consistently across every report in the pack, so the same charge does not appear at two values. The habit that makes all of this work is comparing report to report, not report to memory, and writing a name against every difference before the day is closed. For the receivable side in detail, see hotel city ledger explained: invoicing agencies and companies.

What do the revenue reports show that the trial balance cannot?#

The trial balance gives totals. The revenue reports break the same totals by department, by market and by rate, which is where you see why the day looks the way it does.

Revenue by department splits rooms, food, beverage, spa and other income, each next to its own volume: rooms sold, covers, guests. A total without its volume cannot be checked. Revenue by market segment shows where the business came from; a segment that jumps or disappears is a question for sales, not something the night auditor can resolve at two in the morning.

The rate variance report lists rooms sold at a rate different from the one on the reservation, with the room, the booked rate, the charged rate and who changed it. Rate variance is the report that separates a decision from an error. A discount given at the desk with a name against it is a decision; the same discount without one is indistinguishable from a mistake later.

The statistics block carries rooms sold, rooms available, occupancy, average rate and revenue per available room, and its definitions must be written down once, because hotels differ on what counts as an available room. Complimentary rooms and house use are counted and reported separately, never folded into sold rooms, or every average rate in the pack is quietly wrong.

Which payment reports prove the money actually arrived?#

Payment reports sort the day's takings by type and by currency, then compare them with what the front desk counted and what the bank will settle. They answer a different question from revenue: not what was sold, but what was collected.

Payments by type separate cash, card, bank transfer, agency voucher and city ledger, because each type has its own proof and its own timing. Payments by currency keep cash counts and card settlements in the currency actually charged, so conversion differences land in a named account instead of disappearing into a total.

Card settlement compares the terminal batch total with the system's card total. A difference is either a timing issue across midnight or a missing posting, and the two are handled in completely different ways. Cash is counted against the system's cash receipts, and any over or short is recorded as over or short; absorbing it into another line hides a pattern that repeats every weekend.

An agency voucher is a promise, not a payment. It stays in the city ledger until the money arrives, and the payment report should show it as outstanding rather than settled. Card disputes arrive weeks after the stay, and the payment report of that business date is the evidence you will be asked for.

Which exception reports should never be signed unread?#

The exception lists name the transactions a person changed by hand, and they are the only pages in the pack where reading one line can change a decision. Read them before the totals, not after.

Voids and allowances are different acts: a void removes a posted charge, an allowance reduces it. Both need a reason and a name, and both are recorded as reversals rather than deletions so the trail survives. Rate overrides show who changed a rate, from what to what, and at what time; a cluster of overrides on one shift is a management question, not an audit question. The mechanics are covered in how to void a folio charge without breaking the audit trail.

Complimentary rooms and house use carry no revenue, so each one needs an approving name and a reason code, otherwise the list becomes a place to put anything. Open folios and zero-balance folios after departure are either a receivable or a mistake, and the report should say which before the guest is invoiced. A room status discrepancy means the front desk says occupied and housekeeping says vacant, or the reverse: it is a security and billing question first and a housekeeping question second.

Skippers and sleepers, a guest who left without checking out and a room that shows occupied but was not, are common practice terms. Systems label and handle them differently, so write down what yours means. Set a review line per list, such as every void above a set amount and every override, so that reading the whole thing stays possible on a busy night.

What belongs on the manager's flash report?#

One page. Yesterday's rooms sold, occupancy, average rate, revenue by main department, and the exceptions that need a decision this morning. Nothing that needs a second page belongs on it.

The flash is built after the trial balance agrees, never before, because a flash produced from an unbalanced day is a page of confident wrong numbers. Every figure carries a comparison, such as the same day last week, the budget or the same date last year, so the reader sees direction rather than a number in isolation. It includes a short forward view: rooms on the books for today and the next few days, so the morning meeting can act rather than review.

The exceptions block is three to five lines, each with an owner and the decision needed, drawn from the exception lists rather than written fresh. What to leave off: guest names, departmental detail, anything the reader cannot act on before lunch. The detail lives in the pack, and the pack is where it should be read. The flash and the night pack are different documents for different readers, and mixing them produces a page nobody finishes. For the wider morning document, see hotel daily report: what a GM's morning page should contain.

What to do next#

Read the pack in the order the questions are asked: exceptions first, because they are the only pages that change a decision, then the tie-outs that prove the day agrees, then the revenue and payment detail, and last the one page the general manager will actually use. Keep the order identical every night, name a reader for every report, and the signature at the bottom becomes a statement you can defend.

AI Otel's billing module is built on the same principle: financial records are never deleted, corrections are voided and reversed, and night audit closes the business day. If you want to see how it is built, request a briefing at https://ai-otel.com/contact.