A practical night audit checklist for small hotels covers the handful of things worth checking every night, without the full back-office process larger hotels run.
A night audit at a large hotel is often a formal back-office shift with dedicated staff, but a small property doesn't need that scale to get the real value of one — catching a discrepancy, a missed charge or a sync problem while it's one night old instead of a week old. This is a checklist sized for a small hotel, guesthouse or villa operation that someone can realistically run every night.
The point of a night audit isn't closing the books with accounting precision — it's a short, consistent check that catches problems while they're still easy to fix. A reservation that didn't sync, a rate that posted wrong, a room that shows occupied when it's actually vacant — any of these are a five-minute fix the night they happen and a much longer investigation a week later once several more nights have piled on top of them.
For a small operation, the audit should take minutes, not hours, and it should be something the same person closing the front desk can actually do without specialized training.
Compare the number of occupied rooms your PMS shows against the number actually occupied — a walk-through or a quick check against housekeeping status is usually enough to catch a mismatch. Check that every arrival expected for the day actually checked in, and that no-shows are marked as such rather than left open. Confirm tomorrow's expected arrivals look correct across every channel you sell on, since a missing or duplicate reservation is far easier to catch and fix the night before than the morning a guest actually arrives.
Scan today's charges against today's folios for anything that posted to the wrong room or didn't post at all — this is the kind of small error that's trivial to fix same-day and genuinely annoying to untangle a week later. If any OTA channel had a known issue during the day — a disconnection, a rate push that failed, a modification that didn't sync — note it specifically rather than assuming it resolved itself, and check that channel's extranet directly rather than trusting your PMS's version. A short written note of anything unusual that happened during the day gives the next audit, or you a week later, something concrete to act on instead of a vague feeling that something was off.
Activity history keeps a record of who changed what and when, with 39 action types tracked for 400 days, which turns the written note at the end of a night audit into something the system already keeps automatically. Read-back verification adds a check on the channel side specifically, confirming that a rate or availability push actually landed the way it was intended rather than assuming it did because nothing errored. Together they cover a good part of what a nightly checklist is trying to catch by hand — you can see both on the public demo at try.primehostpartners.com without signing up.