1. Open the current OTA reservation and identify who is responsible for collecting payment.
2. Compare booked total, amount already handled, taxes, deposit, refund, and balance due.
3. Treat “paid,” “unpaid,” and “balance due” as clues until the underlying amounts agree.
4. Record one approved correction and leave finance a complete handover.
An OTA payment status mismatch in the PMS can put front-desk staff in an uncomfortable position: the OTA appears to show payment, while the PMS says the guest owes the full balance—or the PMS says paid while the channel still expects the property to collect.
The safest decision does not come from choosing one label. It comes from confirming who collected the guest's money, how much was handled, what the hotel should receive, and what remains due at the property.
Use this guide before asking the guest to pay again, refunding an amount, or marking a reservation settled.
Start With the Current OTA Reservation
Open the booking in the correct OTA property and confirm the reservation number, status, stay dates, room, rate plan, booked total, taxes, payment method, cancellation terms, and any channel payment instructions.
Look for the party responsible for collection. The guest may pay the hotel, the OTA may collect and later pay the property, or the booking may use another approved channel payment method. Do not assume the model from the OTA name alone.
Check whether the reservation was modified, cancelled, refunded, or partially adjusted after it first entered the PMS. The original payment note may no longer describe the current booking.
Record the time and current OTA status. A confirmation email saved days earlier is not enough when payment or stay details have changed.
Translate Status Labels Into Actual Amounts
Different systems can use the same word for different meanings. “Paid” may mean the guest paid the OTA, the OTA made funds available, the property collected the balance, or only a deposit was received.
Write down six amounts: booked accommodation total, taxes and property charges, amount collected by the OTA, amount collected by the hotel, refunds or adjustments, and amount still due from the guest.
Then confirm the currency. A converted channel amount and the hotel's local-currency folio can differ slightly without indicating an unpaid stay. Keep bank or conversion differences separate from the guest balance.
Do not change a PMS status merely to match the shortest label on the OTA screen. Update it only when the underlying collection responsibility and amounts are understood.
Check the PMS Reservation and Folio
Search by OTA confirmation number and confirm there is only one active PMS record. Compare source, dates, room, rate, total, taxes, deposit, payment entries, refunds, balance, and internal notes.
Look for common causes of a false balance: the channel payment was stored only in notes, a deposit was posted twice, taxes due at the property were omitted, a modification changed the total, a refund remained pending, or a duplicate reservation split the payments.
The PMS folio should distinguish room revenue from money received. A paid status does not mean every charge is room revenue, and a zero balance does not prove the hotel has received channel funds.
A clear hotel management software setup keeps the reservation, folio, payment responsibility, and audit history together so the front desk can explain the balance without opening several disconnected records.
Use a Safe Front Desk Decision
Before charging or refunding, place the booking into one of these operating outcomes:
- Guest must pay the hotel: Confirm the exact amount due, accepted method, taxes, deposit already applied, and any authorization or guarantee conditions.
- OTA collected and the hotel should not charge again: Mark the collection responsibility clearly and retain the expected channel payment or payout reference for finance.
- Partially paid: Apply the verified deposit or channel amount once and show the remaining property balance separately.
- Payment failed or remains pending: Follow the OTA and hotel procedure before cancelling, charging another method, or releasing the room.
- Refund or adjustment is pending: Keep the original charge and expected reversal traceable; do not hide it by editing room revenue.
- Status cannot be confirmed: Escalate to a manager, protect the guest from a duplicate charge, and document what must be verified.
Avoid asking the guest to solve an internal record difference. Explain only the confirmed amount and payment responsibility. If the guest presents evidence, capture it according to hotel privacy rules without copying full card details.
Smart Order can keep payment notes, booking source, guest balance, and front-desk handover connected to the same reservation.
Give Front Desk One Payment View
Use Smart Order to review OTA payment responsibility, hotel collections, and the remaining guest balance in one reservation workflow.
Correct the Record Without Hiding the Difference
Choose one person to make the correction. Add the verified payment responsibility, amount, currency, date, source, and supporting reference to the original PMS reservation.
Post a payment only when the hotel can identify a real collection. Use the correct method or channel ledger according to the property's accounting setup. Do not create a cash or card payment merely to make the balance zero.
When an OTA-collected amount is expected but not yet received by the hotel, distinguish guest settlement from hotel receivable. The guest may owe nothing at check-in even though finance still needs to match the future payout.
If a modification changed the price, retain the original and revised totals in the audit trail. If a duplicate record holds the payment, stop and resolve the duplicate before moving financial entries.
Verify Guest Communication and Shift Handover
Update the notes used by the team on duty. State what the guest owes, what the OTA handled, what the hotel expects later, what remains uncertain, and who owns the follow-up.
Cancel duplicate payment reminders or pre-arrival requests. Check-in staff using the hotel mobile app should see the same balance and collection instruction as the main front desk.
If the guest has already been charged twice, escalate immediately. Preserve both transaction references, do not promise a refund date without approval, and route the case through the responsible payment path.
The front-desk portion is complete when staff can explain the guest balance. The finance portion remains open until the bank, OTA payment record, and PMS posting agree.
Hand Finance a Reconciliation-Ready Record
Provide finance with the OTA confirmation, booking total, taxes, payment model, amount collected by each party, refund or adjustment, expected net amount, PMS postings, and guest-facing balance.
Use hotel reporting and analysis to review payment exceptions by booking source rather than treating every zero-balance folio as successfully collected revenue.
Finance should match the reservation to the payout, virtual payment, invoice, or hotel-collected transaction that applies. Front desk should not change room revenue to make a bank deposit match.
Record the cause of the mismatch: missing payment note, wrong PMS method, changed booking total, duplicate record, delayed refund, tax difference, or staff posting error. Repeated causes should become setup or training fixes.
Frequently Asked Questions
Does “paid” on an OTA always mean the hotel has the money?
No. It may mean the guest completed payment with the OTA while the hotel receives or accesses funds through a separate process.
Should front desk charge the guest when the PMS says unpaid?
Not until the current OTA reservation confirms that the property is responsible for collection and the exact balance due.
Can staff mark a booking paid to remove an alert?
Only after recording a real payment or the approved channel payment treatment. A status change without evidence hides the reconciliation problem.
What closes the incident?
The guest balance is correct, one PMS reservation holds the payment history, staff instructions agree, and finance can trace the money to its final record.
