The night audit is the routine that closes one hotel business day and opens the next. It confirms that every in-house stay has been charged for the night, that guests who should have left are accounted for, and that bookings which never arrived are dealt with before the next day's work begins.
A good night audit is not a ritual performed by whoever is on the late shift. It is a short, repeatable control with a clear owner, a defined order of steps and a rule that the day does not close while a known problem remains open.
What the night audit is for
During the day, reservations change, guests extend, rooms move and charges are added to folios. Most of these actions happen under time pressure at the desk. The night audit is the moment when the property checks that the records match what actually happened before the date rolls forward.
Three questions sit at the centre of every audit. Has each guest who stayed tonight been charged for tonight? Is every guest still in the hotel expected to be here? Have bookings that did not arrive been resolved according to the property's policy? If any answer is unclear, the next morning's reports, invoices and room plans inherit the error.
Keep the purpose narrow. The audit is not the place to redesign rates or rewrite guest profiles. It closes the day; other reviews, such as the daily operations checklist, handle wider management questions.
Know your business date
Hotels work to a business date that can differ from the calendar date. A guest who checks in at 1:30 a.m. on Tuesday usually belongs to Monday's business night, because the room was sold for the night that began on Monday.
The business date moves forward only when the night audit completes. That is why the audit should run after the last expected arrivals and before early departures start, at a time the property sets and keeps consistent. If the business date is allowed to drift ahead of the real date, or to stay behind for several days, charges and reports stop lining up with what staff remember.
Write the chosen audit time into the shift procedure, and record who is responsible when the usual person is absent. A fixed time also makes it easier to notice when an audit has been skipped.
Before you start: clear the day's open items
The audit runs more smoothly when the desk has already handled the obvious exceptions. Before starting, the person responsible should check that:
- every guest who left today has been checked out, not just handed a bill;
- late arrivals expected tonight are either checked in or clearly still pending;
- room moves made during the day were recorded on the stay, not only on a note;
- payments taken at the desk were posted to the right folio;
- any charges from outlets or services that should reach a room have been reviewed.
None of this replaces the audit itself. It simply reduces the number of issues the audit will raise, so the close takes minutes rather than an hour.
Step 1: Post the room night for every in-house stay
The core of the audit is charging tonight's room rent to each stay that is in the hotel. The rate should come from the stay's agreed rate for that date, not from a figure typed in at the end of the shift.
Posting must be safe to repeat. If the audit is interrupted and run again, a stay that was already charged for the night must not be charged twice. Check this behaviour when you evaluate any PMS: ask the supplier to show what happens when an audit stops halfway and is restarted.
After posting, a quick scan of the folios with unusual balances is worthwhile. A stay with no room charge at all, or with two room charges for one night, points to a booking or posting problem that should be explained before the date closes. The guest folio guide explains how charges, payments and balances relate on a single stay.
Step 2: Resolve guests past their departure date
A guest whose booked departure has passed but who is still recorded as in-house is an overstay on paper. Sometimes the guest really extended and nobody updated the booking. Sometimes the guest left and nobody checked them out. Either way, the record is wrong.
Treat this as a blocking issue. The desk should either extend the stay, with the correct rate for the extra nights, or complete the check-out and settle the folio. Closing the day while the stay still shows the old departure date leaves the room unavailable for sale and the folio incomplete.
Step 3: Mark no-shows and expired holds
Confirmed bookings that were due to arrive on or before the business date but never checked in need a decision. Most properties mark them as no-shows during the audit, which releases the room for future dates and triggers whatever cancellation or no-show charge the booking terms allow.
Tentative holds, such as rooms kept for a guest who has not yet confirmed, should not live forever. If the hold has passed its expiry, the audit is the right moment to release it so the room returns to availability.
Apply the policy the guest actually agreed to. The audit should record the status change; any charge to the guest should follow the booking's written terms and the property's normal approval process.
Step 4: Review warnings that do not block the close
Some issues deserve attention without stopping the business date. A charge from a linked restaurant that has not yet been confirmed against a room, for example, can be followed up in the morning without holding back the whole property.
Keep blocking issues and warnings clearly separate. If everything blocks, staff learn to force the close. If nothing blocks, the audit becomes a formality. Decide in advance which problems must be fixed tonight and which can be assigned to a named person for the next day.
Step 5: Close the date and record who ran it
When the blocking issues are cleared, the audit completes and the business date moves forward by one day. The property should be able to see who ran the audit, when it finished, and what was posted or changed as part of it.
That record matters when someone later asks why a stay was charged on a particular date or why a booking became a no-show. Without it, the answer depends on memory and handwritten notes.
When the audit fails, fix the cause
An audit that cannot complete is doing its job. It has found something that would otherwise flow into tomorrow's invoices and reports. The response should be to read the listed issues, correct the underlying records and run the audit again, not to look for a way around the check.
Common causes are simple: a stay past its departure date, a charge that cannot be posted because a tax rule has not been set up for that type of charge, or a booking that was edited while the audit was running. Each has a clear fix. Record what was changed so the manager can review recurring causes and improve the daytime process that produced them.
How NivaasCloud handles the night audit
NivaasCloud runs the night audit for one property and one business date at a time. For each in-house stay it posts the room night for the business date, and a retried audit does not post the same night twice. Guests past their booked departure, and charges that cannot be posted, are recorded as blocking issues; while they remain, the business date does not advance.
Confirmed bookings that were due by the business date but never checked in are marked as no-shows, and expired tentative holds are released. Restaurant charges from a linked POS that still need attention are shown as warnings rather than blockers. A successful run moves the business date forward by one day, and the run and its issues are kept for managers to review.
See how the close connects to daily figures on the reports and analytics feature page, or book a NivaasCloud demo and run a night audit against a sample property with an overstay and a no-show.
Common questions
What time should the night audit run?
Choose a time after most late arrivals and before early departures, and keep it consistent. Many properties run it between midnight and the early hours, but the right time depends on your arrival pattern and staffing.
Can the night audit be run twice for the same date?
A completed business date should not close twice. If an audit fails or is interrupted, it should be possible to fix the issues and run it again without double-charging the night that was already posted.
Who should be allowed to run the night audit?
Limit it to staff who understand the steps and are trusted to resolve the issues it raises, such as night managers or senior reception staff. Use individual accounts so the audit record shows who closed the day.
Does a cloud PMS remove the need for a night auditor?
Software can post charges and flag exceptions, but someone still needs to decide how to resolve an overstay, a disputed no-show or a charge that will not post. The role becomes shorter and more focused rather than disappearing.