What the night audit actually does
The night audit is the point in every 24-hour cycle where a hotel closes its books on the day that just ended and opens the next one. It is not just a report someone prints at 2 a.m. It is the moment room charges and taxes get posted for every occupied room, the cashiers' work for the day gets reconciled against what they actually collected, and the property's business date moves forward. Every other report in the hotel — the daily flash, the trial balance, the manager's morning summary — reads from whatever the night audit posted, so an error here doesn't stay local. It travels into every downstream number until someone finds it.
Because the audit touches money, occupancy and accounting all at once, most of the 'audit went wrong' stories in a hotel trace back to one of three things: a folio nobody closed, a cashier shift nobody closed, or a room charge that got posted twice because the run was started twice. This checklist is built around avoiding exactly those three failure modes, in the order a night auditor actually hits them.
Before the audit: what must be true first
Everything in this section is a precondition, not part of the audit itself. Running the audit before these are clean just moves the problem one day later, with a day of interest, tax and reconciliation compounded on top of it.
- Confirm every expected arrival for the date has either checked in or been marked a no-show. A reservation sitting in limbo is a room the system still thinks is arriving, which throws off both occupancy and the accommodation charge for that night.
- Confirm every expected departure has actually checked out, or has been consciously left open (a late checkout, an extended stay). An open folio that should have closed will get another night of room charge posted onto it — correct for a stay-over, wrong for a guest who already left the building.
- Review open folios for balances that look wrong: a zero balance on a paid stay, a large balance on a guest who checked out, a folio still showing a deposit that was never applied. These are easiest to fix now, with the day's paperwork still on the desk, than three days later when nobody remembers the conversation with the guest.
- Close every cashier shift for the date. An open shift means cash, card and other tender for the day have not been reconciled against what the system expected — the audit can still run, but the day's revenue and payment totals will not tie out until that shift closes, and the gap has to be traced back manually afterward.
- Check for any pending postings — room service, minibar, restaurant charges — that staff know about but have not entered yet. Anything posted after the audit runs lands on the new business date, not the one it actually happened on.
During the audit: posting and reconciling
This is the part that actually runs as a batch process, usually with no one watching each line. It still has a clear internal order, and knowing that order is what makes the output readable when something looks off.
| Step | What happens | Why it matters |
|---|---|---|
| Room revenue posting | The room rate for every occupied room posts as a charge for the night just ending. | This is the accommodation line every other revenue report reads from. |
| Tax posting | Applicable taxes and service charges post against the room revenue just booked. | Tax has to follow the charge it's calculated from, in the same run, or the two drift apart. |
| Package and rate-code postings | Any bundled package elements (breakfast, resort fee) tied to the rate post alongside the room charge. | These are revenue too — missing them understates the day, not just the folio. |
| Cashier reconciliation | Each closed shift is checked: expected tender vs. what was actually declared and counted. | Any variance posts as an over/short, which is how the hotel keeps cash accountable per shift, not just per day. |
| System-wide balancing | Total charges, payments and taxes for the date are checked for internal consistency before the date can roll. | This is the last chance to catch a mismatch while it is still easy to trace to a specific folio or shift. |
Mukeem runs this sequence itself once everything upstream is clean — the auditor's job during the run is to watch for anything the system flags, not to post charges by hand. And the close-day step can be set to refuse to close while any cashier shift is still open, so the problem is named instead of posted around.
What to do when the audit flags an exception
A clean night is the goal, not the norm in every property, especially early after go-live or during a busy season. When the run stops on an open folio, an open shift, or a balance that will not reconcile, resist the urge to force it through — forcing a mismatched close just relocates the discrepancy into a report that is harder to search than tonight's folio list.
- Identify exactly which folio, shift or posting the exception points to — the audit should name it, not just say the totals disagree.
- Fix the root cause: close the folio properly, close the shift with the correct counted tender, or correct the misposted charge.
- Re-run the balancing check only, not the whole audit, once the fix is in — most systems let you retry the specific step that failed.
- Log what happened and what fixed it. The same exception recurring on the same room type, rate code or cashier is a pattern worth investigating, not a coincidence.
After the audit: reports, backup and the date roll
Once the audit balances, three things need to happen before the day is genuinely closed — and in most properties, in this order.
- Generate and file the standard set of reports for the date: the daily/manager report, revenue by department, and the cashier summary at minimum. These are the record of what the day actually was, independent of whatever the live system shows tomorrow.
- Take a backup of the database, or confirm the automated backup for the date completed. A night audit that ran cleanly and then lost its own output to a failed backup is a genuinely worse outcome than an audit that caught a real problem.
- Roll the business date forward. This is the step that actually reopens the property for a new day of charges — room rates, availability calculations and every date-sensitive report will now read the new date.
Why night audit errors are expensive to leave uncaught
A missed step in the night audit rarely shows up the same night. It shows up a week later, in the trial balance not balancing, or in a manager report that disagrees with the front desk's own count of who stayed. By then the folio has usually been paid and closed, the guest has checked out, and the only way to find the error is to re-audit several days by hand.
For example, a property running at, say, 40 rooms a night that misses one open-folio check might carry a single unposted room charge for two or three nights before anyone notices the balance looks off — a small amount per incident, but the investigation time to trace it back costs far more than the error itself. That is the real argument for a checklist: not that any single step is hard, but that skipping one is invisible until it isn't.
This is also where having room charges, cashier shifts and the ledger in one system, rather than three that get reconciled by hand at month-end, changes what 'catching an error' actually costs. In Mukeem, closing the day checks for postings that never reached the ledger and, when your policy requires counted drawers, for cashier shifts still open — and names the record at fault — instead of surfacing three weeks later as a line in the trial balance that could belong to any one of a hundred transactions.