Guide

Night Audits: A Tool for Operational Control in Hospitality

Close each business day with total confidence. A disciplined nightly audit balances every folio, detects revenue leakage, and delivers performance reports before dawn.

Nokumo Editorial · 2026-01-15 · 11 min read

What the night audit actually does

The night audit is the process that closes one hotel business day and opens the next. It runs — either manually by a night auditor or automatically by the PMS — in the early hours, typically between midnight and 6 am. The core tasks are: posting all outstanding room charges to guest folios; verifying that every charge has been applied at the correct rate; reconciling payments received against amounts owed; running the day-end rollover so the next business date is active; and generating the operational reports that management reviews in the morning. A hotel that skips or runs a sloppy night audit starts every day with unclear financial position.

Step 1: Folio reconciliation

Every active guest has a folio — a running account of charges accumulated during their stay. At night audit, the PMS posts the nightly room rate, any applicable taxes, and any charges from restaurant, spa, or ancillary services that have been transferred from point-of-sale systems. The audit step verifies that no folio has a rate discrepancy (a room booked at €120 but charged at €100), a missing tax posting, or an unlinked charge sitting in a POS queue. In properties without automated posting, this step is done manually and is the most error-prone part of the audit — a single transposition error on a group folio can take hours to unravel the next morning.

Step 2: Arrival and departure verification

The audit reconciles the reservation list against actual check-ins and check-outs for the day. No-shows — reservations where the guest did not arrive and did not cancel — must be processed: the room marked vacant, the no-show fee (if applicable) posted, and the reservation closed. Early departures must be verified and the room released. Overstays — guests who did not check out as scheduled — must be identified so the front desk can follow up. Running this step nightly prevents the accumulation of ghost reservations that distort occupancy figures and housekeeping schedules.

Step 3: Payment and deposit reconciliation

The audit verifies that all payments recorded in the PMS match the bank terminal settlement report. Any gap — a charge posted in the PMS without a corresponding terminal transaction, or vice versa — is flagged as a reconciliation exception. Credit card authorisation failures that were not caught at check-in show up here. This step is particularly important for properties with high walk-in traffic or split payments. A clean payment reconciliation means the front desk manager starts the day with a confirmed cash position, not an estimate.

Step 4: Error and fraud detection

Night audit is the control layer that catches operational errors before they compound. Patterns that surface during audit include: rate overrides applied without manager authorisation; discounts applied to rooms with no corresponding loyalty or promo code; folios with negative balances indicating a refund was processed without a corresponding original charge; and identical charges appearing twice on the same folio. A well-configured PMS audit trail flags these automatically. In a manually run audit, these are found by comparing the day's transaction log against expected posting patterns.

Step 5: Day-end rollover

Once all folios are balanced and exceptions are resolved, the PMS performs the day-end rollover: advancing the system date, resetting daily counters, and archiving the closed day's data. In automated systems this happens without staff intervention. In older property management platforms it requires a manual trigger. The rollover must complete before the first arrival of the new day — failing to roll over means new charges post to the wrong business date, creating tax reporting errors that are expensive to unwind.

Performance reports generated by the night audit

The audit produces three categories of report that management relies on: (1) financial summary — total room revenue, F&B revenue, other revenue, total tax collected, payments received, outstanding balances; (2) occupancy report — occupied rooms, vacant rooms, out-of-order rooms, arrivals, departures, no-shows, ADR, RevPAR; (3) exception report — any folio with an unresolved discrepancy, any payment reconciliation gap, any rate override requiring management review. These reports, delivered automatically to the GM inbox by 7 am, are the basis for daily briefings and revenue management decisions.

Night audit task checklist

Task	When	Owner
Post room charges to all folios	Nightly, automatic	PMS (or night auditor)
Transfer F&B / spa charges from POS	Before rollover	Night auditor
Reconcile arrivals and no-shows	Nightly	Night auditor
Verify payment terminal settlement	Nightly	Night auditor
Flag rate override exceptions	Nightly, automatic	PMS (review by GM)
Run day-end rollover	After reconciliation	PMS (automatic) or night auditor
Generate and distribute reports	Post-rollover	PMS (automated email)
Review exception report	First thing AM	Front desk manager / GM

Automating the night audit

Modern cloud PMS platforms run the night audit fully automatically. All posting, reconciliation, rollover, and report generation happens without a staff member present. The exception report is the only item requiring human review — and only when exceptions exist. For small independent hotels, this eliminates the need for a dedicated night auditor entirely. The cost saving on staffing typically covers the PMS subscription several times over. For larger properties, automation frees the overnight staff member to focus on actual guest service rather than administrative processing.

Common night audit failures and how to prevent them

The most frequent night audit problems fall into four categories. Folio posting failures occur when the PMS loses connection to a POS system and charges are not transferred before rollover — prevent this with a pre-rollover POS sync check. Rate discrepancies surface when front desk staff override rates without noting the authorisation — prevent by requiring a manager code for any rate deviation. Payment reconciliation gaps occur when offline card transactions are processed without a matching PMS entry — prevent by running a terminal report before starting the audit. Day-end rollover failures in older systems occur when the database times out — prevent by scheduling the rollover for the lowest-traffic window, typically 3–4 am.

Fiscal compliance and the night audit

In Croatia, Slovenia, and Germany, night audit outputs feed directly into fiscal compliance workflows. Every room charge must be fiscalised — submitted to the tax authority's API and assigned a fiscal receipt number — before the business day closes. In properties using Nokumo, this happens in real time as charges are posted: each folio entry is fiscalised at the moment of posting, and the audit report includes a fiscal receipt reconciliation confirming that every charge has a valid receipt number. This makes the audit report the primary evidence of compliance in a tax authority inspection.

PDF

Free Download