A practical sequence for settling a reservation's payment, whether it's fully prepaid, pay at hotel, or split into a partial deposit and a balance.
Settling payment on a reservation sounds like one action, but it actually changes shape depending on whether the guest prepaid in full, is paying at the property, or put down a partial deposit with a balance due later. This walks through each case as a concrete sequence of steps, so settlement stops being something staff figure out differently each time.
A fully prepaid reservation, whether collected by an OTA or through your own booking engine, is mostly a verification task by the time the guest arrives — confirming the amount received matches what's owed, with nothing left to collect at the property. A pay-at-hotel reservation is the opposite: nothing has been collected yet, and settlement is the entire collection event happening at check-in or checkout. A deposit-plus-balance reservation sits in between, with part of the money settled early and the rest pending until a later point you've agreed with the guest.
Treating all three the same way at the front desk is where mistakes happen — asking a prepaid guest to pay again, or forgetting to collect a balance that was never actually settled.
For a fully prepaid reservation, check the payment record or channel payout status to confirm the full amount was actually received, not just that the reservation shows as confirmed. For pay-at-hotel, settle at the point you've decided — check-in or checkout — and record the method used, since cash, card and bank transfer each need a different confirmation trail. For deposit-plus-balance, confirm the deposit was received when the reservation was made, then settle the remaining balance at the agreed point, flagging the reservation clearly if the balance is still outstanding as the stay approaches.
For OTA-collected bookings, the extranet's own payment or payout status is the most reliable source, since your PMS may only be showing a copy of that status rather than a live figure. For direct bookings through your booking engine, check the payment link or gateway dashboard for the transaction's actual state rather than assuming a confirmed reservation means the payment cleared. For any balance still outstanding close to arrival, flag it clearly in the reservation record so front desk staff aren't settling it for the first time at check-in with no warning.
Bank-level reconciliation matches payout batches against what was actually collected and computes the expected payment date for Booking.com, which removes the guesswork from confirming a prepaid reservation actually settled. For deposits and policy-driven collections, structuring the workflow around staff permissions means only the right people are adjusting balances or recording payments, with activity history keeping a record of who did what. If settlement steps are getting mixed up across your team, that structure is the fix — you can see it on the public demo at try.primehostpartners.com without signing up.