PMSNiveau 2

Night Audit Process

21 min readRead by 531 hoteliers

Why the Night Audit Exists

In the early days of hospitality, before Property Management Systems existed, night auditors had one job: sit down after the front desk quietened and reconcile every folio by hand. The hotel never stops, but the accounting day has to end somewhere. Midnight was the logical choice. Most guests were asleep. The day's transactions had settled. It was the perfect window to make sense of what had happened — and to open the books on the next day.

That was the origin. The night audit emerged from a simple reality: a hotel operates around the clock, but someone still needs to close the business day at a defined point. Every guest who checked in yesterday owes for their room, their minibar, their dinner charge. Every reservation that was made needs to be reflected in today's inventory. The night audit is the mechanism that ends yesterday cleanly, posts everything outstanding, and opens the new day ready to go.

What Goes Wrong When the Audit Is Skipped

Skipping the night audit — or running it carelessly — creates three compounding problems that surface the next morning.

Lost revenue. Charges that were never posted to a guest folio are never collected. A restaurant charge missed at 11 p.m., a laundry charge left in a drawer, a long-distance call that slipped through — these bleed quietly from the till every single night. Individually small, collectively significant over a year.

Broken housekeeping schedules. Housekeeping teams rely on departure counts and room-status reports to plan their morning. If the night audit never finalised yesterday's checkouts, the team walks in blind. Rooms sit unassigned. Arriving guests find dirty rooms and no clarity on when they will be ready.

System drift. The PMS date must advance for rate plans, restrictions, and reporting to function correctly. When the audit doesn't run, yesterday's date stays open. Tomorrow's arrivals pull the wrong rates. Reports show phantom availability. Promotions misfire. The entire operational calendar runs on stale data.

The Modern Reality

Today's PMS software has automated much of the night audit process. Charges post in real time. Balances calculate automatically. Audit routines run on a schedule without manual intervention.

But automation does not eliminate the need for a human checkpoint. Someone still has to trigger the end-of-day process, confirm that it completed without errors, and handle the exceptions — the reservation that didn't sync, the payment that failed, the guest who checked in after midnight and needs their folio opened.

For independent hotels with 20 to 150 rooms, that responsibility usually falls to the night auditor — or, increasingly, to a front desk manager who sets up automated audit rules and monitors them in the morning.

The night audit exists because precision matters in a 24-hour business. The process has changed. The need has not.

Night Audit: Definition and What It Actually Does

The night audit is the end-of-day operational procedure that closes the hotel's business date in the Property Management System. It is not a financial inspection or an accounting review. It is a sequence of mechanical and administrative steps that ensure every guest account is accurate, every reservation status reflects reality, and the PMS is ready for the next business day when the front desk opens in the morning.

What the Process Does

When executed fully, the night audit performs five functions in sequence:

Closes the business date. This freezes yesterday's transactions and prevents new postings from being applied retroactively. No charge entered after this point can be assigned to yesterday's date without manual override.

Posts room charges and taxes. Any room rate, tax, or service fee that has not yet been applied to an in-house guest folio is posted automatically. This closes the gap between what a guest consumed and what they have been charged for.

Reconciles payment transactions. The audit cross-checks cash, card, and direct bill payments received throughout the day against the PMS transaction log, identifying mismatches before they become problems.

Updates reservation statuses. Arrivals who checked in are confirmed as in-house. Guests who never arrived are flagged as no-shows and assessed per the rate plan. Departures are marked out. Extensions are processed.

Advances the system date. The PMS calendar moves forward. Tomorrow's arrivals populate the expected arrivals list. New rate plans and restrictions activate. Reporting shifts to the correct period.

Business Date vs. Calendar Date

A hotel's business date does not correspond to the calendar date at midnight. It resets when the night audit runs. This is a common source of confusion for new staff. If the audit begins at 01:00, a transaction posted at 00:45 still belongs to yesterday. The system date does not advance until the audit completes — which is why early-morning arrivals on 3 January may appear under a 2 January business date until the audit has finished.

Three Approaches to Running It

Automated night audit. The PMS runs the full sequence unattended at a scheduled time, typically between midnight and 03:00. Most modern systems default to this mode. No staff presence is required, but someone must verify the audit completed successfully.

Manual night audit. Staff triggers each step individually, reviewing output in real time and resolving exceptions before proceeding. Common in smaller properties or when the PMS lacks automated routines.

Hybrid. The PMS auto-posts charges and reconciles transactions, but a staff member reviews the output, confirms the date advance, and handles flagged exceptions manually. This is the most common approach for independent hotels with 20 to 150 rooms.

No-Shows in This Context

A no-show is a reservation where the arrival date matches today but the guest never checked in. The night audit detects these automatically, applies the no-show fee defined in the rate plan, and updates the reservation status. This step protects revenue that would otherwise be written off without documentation.

Not an Accounting Audit

The night audit is an operational process, not a financial inspection. It does not verify compliance with accounting standards, audit petty cash, or produce a balance sheet. Those functions belong to the property's accounting or finance team and typically occur on a different schedule.

How It Works: The Night Audit Step by Step

The night audit is not a single action — it is a sequence of steps that must run in a specific order. Each step feeds into the next. Skipping one creates gaps that surface as billing errors, reporting gaps, or system drift by morning. Below is the complete operational sequence, as it would play out in most modern PMS environments, including systems like Elyra where the heavy lifting is automated.

Step 1 — Pre-audit check. Before anything runs, the night auditor confirms that all check-ins and check-outs for the day are complete. Any arrival who has not been assigned a room, or any departure whose folio has not been closed, must be resolved manually before the audit begins. Skipping this step means the audit posts charges to the wrong folios or leaves reservations in limbo. It takes ten minutes to check. It takes an hour to untangle later.

Step 2 — Transaction freeze. New charges are temporarily suspended while the audit runs. This is a critical window. If a charge posts mid-audit — a late restaurant charge, a room service call — the system may double-post it or miss it entirely depending on timing. The freeze ensures that the transaction log is clean and complete when the reconciliation step runs. In most modern PMS platforms, this happens automatically. In manual setups, it requires discipline — staff must wait until the audit is complete before posting anything new.

Step 3 — Room charge posting. The PMS reads every in-house folio, identifies the rate plan attached to each reservation, and posts the room rate plus applicable taxes. This is the step that most directly protects revenue. A guest who checked in three days ago and never received a charge will receive one now — covering tonight. In systems like Elyra, this step runs automatically at the scheduled audit time with no manual intervention required.

Step 4 — No-show processing. The system scans all reservations with an arrival date of today that have no check-in recorded. Each is flagged, assessed the no-show fee defined in its rate plan, and marked with a no-show status. This is not optional cleanup — it is revenue recovery. Without this step, that fee is simply written off.

Step 5 — Reconciliation. Total room charges, additional charges, and payments received throughout the day are compared against the PMS transaction log. Cash totals are tallied. Card payments are verified against the payment gateway. Direct billing accounts are checked against the ledger. Any discrepancy is flagged for review. In automated systems, this runs as part of the nightly sequence. In hybrid setups, the auditor reviews the output before approving the close.

Step 6 — Report generation. The system produces the night audit report — often called the manager's flash, daily report, or end-of-day summary. This document is the operational snapshot of the business day. It typically includes the night's occupancy rate, total revenue, average daily rate, no-show count, outstanding balances by folio, and a transaction summary broken down by payment type. Management reviews it before the morning briefing. Housekeeping reviews it for room status. It is the document that tells the next shift what happened and what needs attention.

Step 7 — System date rollover. The PMS advances from yesterday's business date to today's. Once this completes, all rate plans, availability settings, and restrictions shift to the new period. Tomorrow's expected arrivals populate the dashboard. The calendar is live for the new day. This is the point at which the PMS is officially in a new business date — even if the clock on the wall reads 01:30.

Step 8 — Audit close. The night auditor signs off on the completed audit, either by entering a close confirmation in the PMS or by acknowledging the auto-closed log entry. This creates an audit trail — a timestamped record that the process ran, what it reported, and who was responsible. In automated environments, the system logs the close automatically. In manual or hybrid environments, this is the auditor's final accountability step. Once signed off, the front desk reopens for the new business day.

Best Practices for a Reliable Night Audit

A clean night audit is not about doing more — it is about doing the right things at the right time. The practices below reduce errors, protect revenue, and make the process repeatable regardless of who is running it.

Set a fixed audit time and protect it. The business date should close at the same time every day. Consistency eliminates the drift that causes rate plans, restrictions, and availability to misfire at unexpected moments. Most properties choose a window between 00:00 and 03:00, when traffic is lowest and the last transactions have settled. Once set, treat this slot as inviolable. If a late checkout or group arrival requires flexibility, log an exception — but do not let routine operations slide the audit window arbitrarily.

Resolve exceptions before the audit runs. Unresolved departures, early check-outs, and pending room moves create reconciliation errors that cascade through the system. Train the evening shift to flag these before handover. A checkout that was not closed, a reservation that was not checked in — these need manual resolution before the audit sequence begins. It takes ten minutes to close a folio properly. It takes an hour to untangle a misaligned one the next morning.

Review the night audit report every morning — before the briefing. The night audit report is not just a record. It is the operational briefing for the next shift. The GM or front desk manager should open it before the morning briefing and check occupancy, revenue, outstanding balances, and any flagged exceptions. An anomaly caught at 08:00 is fixable

Market Variations: How the Night Audit Adapts to Different Property Types

The night audit follows the same principles everywhere. The operational reality of executing it changes significantly depending on property size, guest mix, and service complexity. What works for a 30-room boutique hotel does not translate directly to a 120-room resort with three food and beverage outlets. Understanding where the differences lie helps owners and managers allocate resources correctly and avoid processes that are either over-engineered or dangerously under-equipped.

Small independent hotels — 20 to 50 rooms. Most properties in this range have no dedicated night auditor. The last front desk agent on the evening shift runs the audit before closing, typically between 23:00 and 01:00. The challenge here is not complexity — it is bandwidth. The same person who checked out a guest at 23:15 must now close folios, verify transactions, and trigger the system date advance without making errors under fatigue. Automated PMS audit is not a luxury in this context — it is the difference between a reliable close and a nightly error log. When the system handles room charge posting, no-show flagging, and date rollover automatically, the staff member's role becomes review and exception handling, which requires far less training and attention.

Mid-size independent hotels — 50 to 150 rooms. This is the range where a dedicated night auditor or night manager typically appears. The audit runs between 01:00 and 03:00, and the night auditor often covers security and emergency call duties alongside it. The night audit report here becomes a management tool, not just a system record. The general manager reviews it before the morning briefing to assess occupancy, revenue against forecast, and any unresolved folios. A modern PMS addresses the challenge of report delivery by generating and distributing the night audit report automatically to the GM's inbox or dashboard, so it is waiting before the briefing starts — no one is chasing numbers at 08:00.

Resorts and extended-stay properties. These properties carry the most complex audit profile. Guests stay longer, often on package rates that bundle room, breakfast, activities, and spa access across a single folio. Rate plans are layered, early departures are frequent, and folio corrections that seem minor can snowball over multi-week stays. The specific challenge is split-folio accuracy — when a guest charges dinner to their room, the amount must reach their folio correctly and post against the right rate plan before the audit closes. Without proper POS integration and automated charge routing, this step requires manual intervention for every F&B transaction. A modern PMS with integrated point-of-sale routing eliminates this manual step entirely by pushing charges to the correct folio automatically before the audit window opens.

Properties with 24-hour food and beverage or spa operations. The night audit cannot run until all POS terminals have closed their sessions and transferred charges to the PMS. In a hotel with a late-night bar, a 24-hour restaurant, or a spa that stays open past midnight, this creates a scheduling constraint. If the kitchen charges for a meal at 01:30 and the audit ran at 01:00, that charge does not reach the guest folio until the following night's audit — which means a guest checking out at 11:00 the next morning may not see their last meal on the bill. The solution is to enforce a POS cutoff time that precedes the audit, typically 30 to 60 minutes before the scheduled audit run. Modern PMS platforms with integrated POS allow administrators to set a hard cutoff window, after which terminals route to the next business date rather than yesterday's.

In every context, the underlying principle holds: the audit must close cleanly, with all charges routed and all statuses updated, before the system date advances. The variables are how many moving parts exist, how late they run, and how much manual intervention the PMS eliminates.

Common Mistakes That Cost Hotels Money

The night audit is straightforward in concept. In practice, small oversights compound quickly. The mistakes below are among the most expensive ones seen across independent properties — not because the audit is complicated, but because the consequences of getting it wrong are easy to underestimate until they show up as a dispute at checkout or a revenue gap in the monthly report.

Running the audit with unresolved check-ins or check-outs. The most frequent error is triggering the night audit before the evening front desk has finished processing the last guests of the day. A walk-in who arrives at midnight is checked in, but the folio is not yet posted. A guest who checked out at 22:30 still has an open folio. When the audit runs on these incomplete records, rooms remain flagged as occupied in the system. Housekeeping opens the room the next morning believing it is dirty. The arriving guest finds their reservation in limbo or is assigned a room that is still occupied. The fix is simple: the pre-audit check in Step 1 must be completed without shortcuts. If the front desk is still active, the audit waits.

Skipping the audit entirely on a slow night. When the hotel is quiet and occupancy is low, it is tempting to let the audit slide. This is the most disruptive mistake on the list. One skipped audit breaks the business date sequence. The PMS date does not advance. Tomorrow's arrivals pull rate plans and availability from the wrong date. When the next audit runs, it must process two full days of transactions simultaneously — postings, reconciliations, no-show flags — which creates confusion, lengthens the audit window, and increases the chance of errors slipping through. The fix is discipline: no matter how quiet the night, the audit runs on schedule.

Not reviewing the no-show report. No-show fees are not applied automatically by every PMS, and not every rate plan triggers them without confirmation. Properties that skip the no-show review lose these charges every single night. A hotel with ten no-shows per week at an average rate of $120 is writing off $1,200 weekly — $62,400 annually — simply because no one checked the report. The fix is to treat the no-show report as a mandatory review item, not an optional list. Most modern PMS platforms flag no-shows in the night audit report automatically. Someone just has to look at it.

Treating the night audit report as optional. Some managers never open the daily report unless something goes wrong. This removes the only real-time diagnostic tool available to hotel operations. Revenue leaks that are visible in the report at 02:00 become guest disputes at 11:00. Overbooking signals that would have been visible in the arrivals list become full-front-desk crises. Billing errors that could be corrected before checkout require refund negotiations after the guest has left. The fix is simple: the GM or front desk manager reads the report before the morning briefing, every day, without exception.

Giving audit access to untrained staff. The night audit, once closed, is not easily reversed. A partial audit — run accidentally, run twice, or run with unresolved exceptions still open — requires manual correction by the PMS vendor or, in some systems, a data rollback that affects every transaction logged during the error window. This is not a five-minute fix. It is a support ticket that can take hours to resolve, during which the system date may still be wrong. The fix is access control: audit permissions belong to trained, accountable staff only. Backup staff should be trained on a sandbox environment, not on the live system with real reservation data at risk.

Elyra and the Night Audit: Automation That Works in Practice

Elyra handles the night audit as a fully automated sequence. The property sets a scheduled time — the default is 02:00, but this is configurable — and the system runs the complete audit cycle without a staff member present. There is no manual trigger required, no queue to clear, and no need for someone to remain at the front desk specifically to close the day.

What Elyra Automates

When the scheduled time arrives, Elyra executes the full audit sequence in order: posting room charges to every in-house folio based on the rate plan attached to each reservation, calculating taxes per the rate rules configured for each room type, flagging and processing no-shows with the applicable fee, reconciling the day's transactions, generating the end-of-day report, and advancing the system date to the next business day. Each step runs against the live reservation database. The transaction log is locked during the sequence to prevent double-posting. When it finishes, the business date has closed cleanly and the new day is open.

What the Morning Review Looks Like

The night auditor or general manager arrives to a completed audit, not a pending one. Elyra surfaces a night audit summary screen that lists the total charges posted, the number of no-shows processed and fees applied, any reservations that generated exceptions, and a direct link to the full PDF report. This is the review point — not a chase for missing data, but a check of what the system already did.

The full night audit report is also emailed automatically to the GM and any configured recipients. This means the morning review can happen before the manager is on-site, on a phone, over coffee. The report is waiting.

The Exception Log

Not everything processes without friction. Elyra maintains an exception log that flags reservations where the audit encountered a conflict — a rate plan that did not match the room type, a folio that closed with a negative balance, a charge that fell outside the standard routing rules. Rather than posting an incorrect amount and moving on, Elyra flags the reservation for manual review. The auditor sees exactly what went wrong, on which folio, before the guest checks out or the next shift begins. This is the difference between an audit that silently fails and one that surfaces problems while they are still fixable.

For Properties That Want Manual Control

Elyra supports a hybrid mode. The system auto-posts room charges and reconciles transactions, but the final audit close requires a human confirmation before the business date advances. This suits properties where management prefers a deliberate human checkpoint each morning — or where local compliance requirements demand a sign-off before the date rolls forward. The hybrid mode is configured at the property level and can be adjusted as the team's confidence in the automated process grows.

The night audit in Elyra is designed to remove the repetitive, error-prone tasks while keeping the human reviewer in the loop where it matters.