Night Audit Reconciliation Checklist

It covers the overnight close activities that typically happen at the front desk or in the property management system: revenue postings, folio balancing, payment settlement checks, exception review, and business date rollover. The checklist is meant to produce a verified close record, not a generic shift handoff. It is useful when you need a consistent end-of-day process with clear yes/no verification steps.

This template is usually recurring nightly, aligned to the hotel business date close. Some properties run it once per day after the last expected guest activity, while others use a later cutoff for late arrivals or outlet postings. If your operation has multiple close points, keep the main checklist nightly and add separate checklists for outlets or exceptions.

The DRI is usually the night auditor, overnight front desk lead, or accounting-adjacent operations lead, depending on property size. The person running it should be able to verify postings, identify blocking discrepancies, and escalate unresolved items before rollover. If the checklist touches multiple systems, assign clear follow-up owners for each exception.

Yes, but the scope should match the operation. Limited-service properties may only need folio reconciliation, payment settlement, and date rollover, while full-service hotels often add outlet postings, package adjustments, and more exception handling. Customize the checklist so it reflects the actual revenue sources and systems in use.

Common failures include missing late charges, duplicate postings, unsettled card batches, unbalanced folios, and rolling the business date before all required postings are complete. Another frequent issue is treating every discrepancy as blocking, which slows the close without improving accuracy. This checklist helps separate blocking items from non-blocking follow-ups.

An ad-hoc process depends on memory and usually varies by person, which makes reconciliation harder to audit and repeat. This template turns the close into a consistent task type with explicit verification steps, so the team can see what was checked, what failed, and what needs follow-up. It also makes handoffs easier when staffing changes.

Yes, and you should. Replace generic steps with the exact reports, settlement screens, and rollover actions used in your property management system, point-of-sale system, and payment gateway. Keep each checklist item independently verifiable so staff can answer yes, no, or N/A without ambiguity.

Useful integrations include the PMS, POS, payment processor, accounting export, and any ticketing or incident system used for unresolved discrepancies. If a failed verification step requires follow-up, create a linked task with a DRI and priority so it does not get lost after the close. That keeps blocking issues visible without forcing the night audit to absorb every downstream action.

Start by mapping the checklist to the current close sequence and removing any steps that do not produce a clear verification outcome. Train staff on what counts as blocking versus non-blocking, and define when the business date may roll over. Run it alongside the old process for a short period, then retire the ad-hoc version once the team trusts the new flow.