Insights

What does a hotel PMS without night audit actually do at midnight?

"No night audit" sounds like a feature only an auditor could love, until you have waited for one. The morning report that is really yesterday's. The system that freezes at 2 a.m. while a batch runs. The posting error found a day late, after the guest has checked out. Here is what the night audit was for, why it exists in most systems, and what replaces it when the PMS posts everything the moment it happens.

The pain: the day does not exist until the batch says so

Everyone waits for the roll. Room charges, taxes and the day's revenue post in one run after midnight. Until it finishes, the owner's dashboard shows the day before, the group P&L is a day stale, and the accounts team starts its morning by checking whether the batch completed.

The system goes away. In many properties the night audit locks the front desk for thirty to sixty minutes. A late arrival stands at the counter while the clerk explains that the computer is "closing the day".

Errors are found the next day. A rate typed wrong at 3 p.m. is harmless until the batch multiplies it across the folio. By the time the night auditor sees it, the guest has had breakfast on the wrong rate and the correction is a reversal, not a fix.

The night shift is data processing. The most experienced person on the overnight team spends the shift running reports, matching totals and waiting for progress bars, rather than looking at exceptions.

Why it happens: batch architecture, inherited

The night audit is not a hospitality tradition. It is a software design. Older systems queued transactions through the day and posted them to accounts in one end-of-day run because that was how databases were used when the systems were written. A PMS built on that model has to stop the world to close the day, and every report, dashboard and ledger figure inherits the delay. "Automated night audit" in such a system means the batch starts itself; it still runs, still locks, and the day still does not exist until it finishes.

How WinX does it: every posting is already in the ledger

• Charges post when they happen. A check-in, a restaurant bill, a spa treatment, a park ticket charged to the room: each one hits the guest folio and the general ledger at the same moment, from the same database. There is no queue waiting for midnight. This is what makes the P&L on the day possible.
• The date rolls itself, without locking. At the property's business-day boundary WinX posts the night's room charge and taxes to every in-house folio, flags no-shows and produces the close-of-day reports. Nobody presses a button and the front desk keeps working through it. A 2 a.m. arrival is checked in at 2 a.m.
• Reports are current at any hour. Occupancy, revenue, arrivals and the reception board read the live data, so a 4 p.m. figure is a 4 p.m. figure, not last night's.
• Errors surface the same shift. Because a wrong rate is on the folio and in the ledger immediately, the evening supervisor sees it in the rate check before the guest sleeps on it.
• The night team reviews instead of processes. What remains for the overnight shift is the part that needs judgement: no-shows, rate exceptions, cash counts, house-use rooms, the deposit that did not arrive. The reports that used to be the shift's output are already there when it starts.
• The audit trail is continuous. Every posting carries who, when and from which screen, so an auditor reads a sequence of events rather than a batch log.

Proven where the day never ends

Manila Ocean Park and Hotel H2O run a hotel, an oceanarium and around 40 outlets on one WinX installation with guests on site from early morning to late night; there is no quiet hour in which to lock the system, so there is none. Petronas Pengerang posts more than 1,000 rooms' worth of charges a night; done as a batch that would be the longest hour of the day, done as it happens it is nothing at all.

Common questions

Is there a night audit in WinX at all?

There is an automatic date roll-over: at the business-day boundary WinX posts the night's room charge and taxes to in-house folios, flags no-shows and produces the close-of-day reports. There is no manual batch to run and nothing locks. Every other transaction has already posted to the folio and ledger at the moment it happened.

When are room charges posted, and can a guest check in during the roll?

Room charges and taxes post automatically at the date roll for every in-house folio; everything else posts in real time. The roll does not lock the system, so a late arrival is checked in normally while it runs.

Can I run revenue or occupancy reports before the day closes?

Yes. Reports read live data, so a figure at 4 p.m. reflects everything posted up to 4 p.m. There is no end-of-day run that the numbers wait for.

What does the night shift do if there is no batch to run?

Controls rather than processing: no-shows, rate exceptions, cash counts, house-use rooms, missing deposits. The reports that used to be produced by the audit run are already there when the shift starts.

Does this depend on being cloud-hosted?

No. WinX is the same system cloud-hosted, on-premise or hybrid, and the real-time posting model is the same in every case.

Related: P&L on the day, not at month-end · Real-time availability vs allotments · Outdated AR when accounting is disconnected · WinX PMS