Blog›Basics

Night Audit: Handling OTA Reservation Exceptions — Unpaid, Modified, Duplicated

A night audit routine that specifically checks for unpaid, modified and duplicated OTA reservations catches problems before they reach a guest at the front desk.

The Prime Host Partners team18 Nov 2026 · 7 min read

A night audit that only confirms the day's charges and occupancy misses a specific category of problem that's easy to overlook: OTA reservations that are unpaid when they shouldn't be, modified without the change reaching your PMS, or duplicated across channels. This covers building that check into your existing audit routine.

Full guide on this topic
Why these three exceptions deserve their own check

A standard night audit reconciles room revenue, occupancy and charges for the day, which is necessary but doesn't specifically surface a reservation sitting unpaid when your policy expected payment, a modification that never synced from the OTA, or a booking that exists twice because it arrived through two channels for the same guest. Each of these can pass through a standard audit unnoticed because the numbers can still look approximately correct even with one of these problems present.

Catching them at night audit, while the day's activity is still fresh, is far easier than discovering one of them when a guest arrives expecting different dates or a different price than what's actually on file.

What each exception actually looks like

An unpaid reservation that should have been paid usually traces back to a payment that failed silently on the OTA's side, or a booking type where payment is collected at the property but wasn't actually taken. A modification exception shows up as a reservation whose dates, rate or occupancy in your PMS no longer match what the OTA's extranet currently shows, because the change message didn't sync. A duplicate typically happens when a guest books the same stay through two different channels, or a modification was processed as a new booking rather than an edit, leaving two records for one actual stay.

Where to look for each exception type
1Unpaid reservationsCheck bookings flagged as requiring payment against your payment log for the day — anything missing a matching payment is worth a direct check with the OTA.
2Modified reservationsSpot-check a sample of today's arrivals against their current status in each OTA's extranet, not just your PMS record.
3Duplicated reservationsLook for two reservations with the same guest name and overlapping dates, especially from different channels.
Building the check into your existing audit

Add a short, specific step to your night audit routine: for tomorrow's arrivals and any reservation modified today, confirm payment status, current dates and rate directly against the source OTA's extranet rather than trusting the PMS record alone. This doesn't need to cover every reservation in the system — focusing on upcoming arrivals and anything flagged as recently changed covers the cases most likely to become a front-desk problem.

A night audit that only checks the math misses the one thing that actually surprises a guest at check-in — a reservation that quietly stopped matching reality.
Making the exception check routine
Check payment status for upcoming arrivals that require prepayment, against your actual payment log, not an assumption.
Spot-check recently modified reservations against the OTA's current extranet record, not just your PMS.
Scan for duplicate reservations by guest name and overlapping dates, especially across different channels.
Resolve any exception found before the guest arrives, not after, since that's when it becomes a real problem.
Keep a short log of exceptions found each night, so a recurring pattern on one channel becomes visible over time.
How Prime Host stops this from happening again

The physical no-double-booking guarantee at the database level prevents one specific version of the duplicate problem outright — two overlapping bookings for the same room can't be saved, by construction. For supported channels, a booking a channel failed to deliver, or a modification that didn't sync, can be recovered automatically rather than waiting for a night audit to catch it. Activity history also helps trace exactly when and how a duplicate or stale reservation appeared. You can see these in the public demo at try.primehostpartners.com without signing up.

Frequently asked
How much time should a night audit exception check add?
If limited to upcoming arrivals and recently modified reservations rather than the full reservation list, it's a short, focused addition rather than a full re-audit.
What's the most common cause of a duplicate OTA reservation?
A guest booking the same stay through two channels, or a modification being processed as a new booking rather than an edit to the existing one.
Should every unpaid reservation be treated as an error?
Not necessarily — some booking types legitimately collect payment at the property. The check is whether it's unpaid when your policy expected payment to have already been taken.
Want to see all of this working for real?
Walk through the actual system in read-only mode. Nothing to fill in.

Read next

© 2026 Prime Host Partners
Privacy PolicyTerms of Service