Most hotel software is designed, demoed and sold in daylight. The general manager sees the dashboard, the revenue manager sees the forecast, and the front office manager signs off on the training plan. The person who uses the system alone, at three in the morning, with nobody to ask, is rarely in the room.

That person is the night auditor. Boostpoint's night auditor job guide describes the role plainly: someone who runs a hotel alone from about eleven at night until seven in the morning, covering the front desk, security, guest service and the daily financial close. It is two jobs in one shift, usually with nobody else in the building.

This post walks through a typical overnight shift, hour by hour, using the procedures that the major PMS vendors publish in their own documentation. It is not one person's story. It is the shift as the software defines it, and what each hour tells a hotel tech company about how its product is really experienced.

Who the night auditor is

There is no separate government wage category for the job. Boostpoint notes that the US Bureau of Labor Statistics places the role within hotel, motel and resort desk clerks, which had a median of $16.86 an hour, $35,070 a year in 2025 across 264,200 positions, with about 43,600 openings a year. Boostpoint adds that the overnight openings are the hardest to fill in the whole category.

That combination matters for anyone selling software. The person closing the hotel's books every night is usually hourly, and Boostpoint notes that training a careful person on the PMS takes a couple of weeks of day shifts before they work alone. Whatever your product does at night, it does it in front of someone with limited training and no support desk down the hall. We covered the wider version of this problem in how front desk turnover affects software adoption.

The shift, hour by hour

11:00 pm: handover and the arrivals list

The shift starts with the evening team's notes and a list of guests still due to arrive. Mews' guide to the night audit describes the night auditor as being in a dual role, overseeing front desk operations while handling the financial close, and often as the sole or primary staff member on duty. Late check-ins, early checkouts, guest requests and lobby security all land on the same desk as the reconciliation.

What the software shows here is the arrivals and departures view. If it is cluttered, slow or hard to filter, the auditor feels it first, because every interruption from a guest means leaving the audit and coming back to it.

12:00 am: the business date that does not change at midnight

This is the moment that confuses most people outside hotels. In a traditional PMS, the calendar date and the hotel's business date are different things. Oracle's OPERA documentation states that OPERA has its own system date, which is not automatically changed at midnight but only after the End of Day sequence finishes. Revenues and payments posted before the sequence runs statistically belong to the old date.

So at midnight, the auditor is still working in yesterday. A guest who walks in at 12:40 am is checked in against the previous business day. Charges posted now count toward the day that is being closed. Any software that integrates with the PMS and assumes the calendar date is the business date will produce numbers that do not match the hotel's reports the next morning.

12:30 am: clearing the blockers

Before the audit can run, the system has conditions. OPERA's documentation lists them: all due-outs must be checked out or have their departure dates extended, guests who have not arrived are listed as no-shows, everyone who has arrived must be checked in, and all cashiers must be closed. OPERA also requires that all users other than the person running the End of Day sequence be logged out before it rolls the business date.

In practice this is where the night often goes wrong. A cashier left open on a day shift, a guest checked out on paper but not in the system, a stuck session on a terminal in the back office. Each one has to be found and fixed by the auditor before anything else can happen.

1:30 am: reconciliation

This is the accounting half of the job. Boostpoint lists it as posting room and tax charges, reconciling the day's revenue against the point-of-sale outlets, balancing credit card settlements against the property management system and resolving discrepancies. Mews lists the same core tasks: reviewing room revenue, food and beverage charges and incidentals, checking folios for correct rates, taxes and payments, and flagging discrepancies for follow-up.

Every integration a hotel runs shows up here. If the restaurant POS, the spa system or the payment gateway posts late, posts twice or posts to the wrong folio, the auditor is the one who finds the gap between the two totals and has to work out which system is right.

2:00 am: running the close

Once the blockers are cleared, the close runs. OPERA's End of Day sequence reconciles folios, processes credit card transactions, generates fixed charges postings, calculates daily statistics and provides a cumulative balance of accounts receivable. Its last step is closing the business day, and Oracle notes that once it is closed, no further adjustments are allowed.

Vendors have been changing how this step works. Cloudbeds' night audit update lets a property set the audit to run automatically at a custom time between 12:00 AM and 6:00 AM in 30-minute intervals, adds a manual Run Night Audit button, and restricts that permission by default to property owners and admins. It also added webhooks to notify partner systems when the night audit is completed.

Mews takes a different route. Its guide says the system automatically transitions to the next day at midnight with no 'perform night audit' button, posts charges at the time a reservation or service is created, and offers an editable history window that typically allows changes up to seven days into the past.

3:30 am: the reports

The close produces the paperwork the day team relies on. Cloudbeds' dedicated night audit reports include Expected Check-Outs, Expected Check-Ins/No-Shows, a Room Rate Variance Report, a Trial Balance and an In-House/Police Report. OPERA produces the Night Auditor's Report to the Manager, which Oracle says shows how many dollars of receivables were owed at the start of the day, how many were paid and charged, and the balance at the day's close.

These reports are often the only part of the night the general manager ever sees. If your product's data appears in them, or is missing from them, this is where the GM forms an opinion about whether your system can be trusted.

5:00 am to 7:00 am: guests, security and the handover

The early checkouts start. Boostpoint notes that some properties add breakfast setup, laundry and lobby cleaning to the shift, on top of security rounds and handling any emergency. The last task is the handover: Mews describes it as generating reports, highlighting unresolved guest issues or discrepancies and sharing updates with front desk, housekeeping and management.

What a public example shows

Mews publishes one customer example. It says Koncept Hotels, a chain with properties across three countries, had team members in some staffless hotels running night audits from their own homes, and that guests who had not arrived by 10 pm were manually checked in regardless of actual arrival, which made housekeeping figures inaccurate. After moving to automatic day transitions, Koncept's Head of Operations Daniel Hrkać is quoted as saying:

Now we don't do the night audit, we have an absolutely 100% correct housekeeping figure at the end of the month.

Whether a hotel keeps a traditional audit or drops it, the example makes the same point: the overnight process shapes data quality for the whole month, not just for one shift.

What this means if you sell hotel software

• Your integration runs on business dates, not calendar dates. If you sync with a PMS that rolls the date after the audit, test what happens to a 12:40 am booking or charge.

• Late or duplicate postings land on one person. Every POS, payment or upsell tool that posts to folios creates reconciliation work at 1:30 am if it fails quietly.

• Listen for the audit-complete signal. Where the PMS offers one, such as Cloudbeds' night audit webhook, use it to trigger your own overnight jobs instead of guessing a time.

• Design for a user with no one to ask. Error messages need to say what to do, not just what failed, because support is often asleep and the manager is off property.

• Show up in the morning reports. The GM judges the night by the reports. If your product's numbers do not reconcile with them, your renewal conversation starts with an argument.

The night shift is easy to leave out of onboarding, because nobody from the vendor is awake for it. If your onboarding plan assumes day staff and an IT contact, it is worth reading how to onboard properties with no IT staff, and making sure your demo covers the overnight use case too, as we set out in building a demo that survives operator scrutiny.

If you suspect the gaps your product leaves overnight are turning into churn or stalled renewals, a free revenue leak audit shows where your funnel and retention are losing money.

Frequently Asked Questions