Night Audit Reconciliation Checklist

It covers the overnight close steps a hotel front office or night auditor uses to verify guest folio postings, reconcile revenue, confirm balances, and complete the system day-close. It is meant to produce a clear audit trail for the business date rollover, not a generic housekeeping or maintenance checklist. Use it when the property needs a repeatable close process with verification steps and a defined DRI. It is especially useful when multiple systems feed the folio or when manual adjustments are common.

This template is typically run once per business day during the night audit window, usually after the last expected postings and before the new business date opens. If your property has split shifts or late-arriving charges, you can add a recurrence tied to the nightly close window and a cutoff time. The key is consistency: the checklist should run at the same point in the close process every day. If a property closes multiple revenue streams separately, create a separate checklist item for each close point.

The night auditor is usually the DRI, with the front office manager or accounting lead as the escalation contact for blocking exceptions. In smaller properties, the front desk supervisor may own the review and sign-off. The important part is that one person is accountable for completion and one person is accountable for exception resolution. Avoid shared ownership without a clear handoff, because that often leaves unresolved folio discrepancies at rollover.

Yes, because it creates a consistent record of what was verified before the business date closed. Hotels often need evidence that revenue postings, adjustments, and rollovers were checked in a repeatable way, especially when internal audit or finance reviews the close. This template supports that by using independently verifiable checklist items and a clear verification step. It does not replace accounting controls, but it helps document that the operational close was performed.

The most common mistake is combining several actions into one checklist item, which makes it hard to tell what actually passed or failed. Another mistake is marking every issue as critical, which hides the few exceptions that truly block close. Teams also forget to include a verification step for manual postings, cash drops, or no-show adjustments. Finally, some properties run the checklist without a clear cutoff time, which leads to rework when late charges appear after reconciliation.

Yes, and you should. Add checklist items for the specific folio sources, payment terminals, revenue buckets, and reports your property uses, such as room charges, incidentals, restaurant postings, or package inclusions. You can also add links or references to the exact PMS, POS, or accounting reports that the night auditor must review. Keep each item independently verifiable so the checklist still works if one system is offline or delayed.

Ad hoc closeouts depend on memory and habit, which makes missed postings and inconsistent handoffs more likely. A checklist turns the close into a repeatable runbook with clear task types, priorities, and verification steps. That matters when the shift is busy, the property is short-staffed, or multiple revenue sources need reconciliation. The template is designed to reduce ambiguity, not to add extra paperwork.

Treat the discrepancy as blocking only if it affects the ability to close the business date or creates a compliance risk. Otherwise, record it as a non-blocking exception, assign a DRI, and route it for follow-up before the next shift handoff. The checklist should capture the exact report, folio, or transaction that failed verification so the next person can resolve it quickly. If the issue repeats, add a new checklist item or a separate escalation step rather than relying on memory.