A plain walk-through of how a reservation's money actually moves, from the moment a guest pays to the day it settles, so you can explain any step to staff or a guest.
Collection, refund and settlement sound like three words for the same thing, but they describe three different moments in a reservation's life, and most confusion at the front desk comes from mixing them up. This lays out what happens at each stage, in order, for a small property running a mix of OTA and direct bookings.
Collection is when money actually changes hands — a card is charged, cash is handed over, or a bank transfer lands in your account. Refund is reversing part or all of a specific collection because a cancellation, a dispute or a service issue requires it. Settlement is the back-office step where you confirm what was collected, what was refunded, and what the final net figure for that reservation actually is, usually after the stay has ended or a payout batch has arrived.
A single reservation can touch all three stages weeks apart — paid at booking, modified and partially refunded a week later, then settled against a payout that lands after checkout. Treating them as one event is how a property ends up unsure what a guest actually owes or is owed.
On an OTA like Booking.com or Expedia, collection is frequently handled by the channel itself under its own payment model, and what lands in your account is a net payout rather than the guest's full charge. On a direct booking taken through your own booking engine, you are typically collecting via a payment link or asking the guest to pay at the property, which puts the full amount and the timing in your hands rather than the channel's. Pay-at-hotel or cash reservations, whatever the source, only count as collected once the money is physically received, not at the moment the reservation was made.
For every reservation, record three numbers in one place: what was originally charged, what (if anything) was refunded and when, and what the net figure actually is after both. Keep this at the reservation level, not just as a running total for the week, since a property that only tracks totals loses the ability to answer a specific guest's question about their specific booking. For channel-collected bookings, cross-check this against the payout report rather than assuming the reservation record and the payout will always describe the same number.
Bank-level reconciliation matches payout batches against what was actually collected and computes the expected payment date for channels like Booking.com, so settlement stops being a manual guess about which payout a reservation belongs to. Prime Shield adds the other half, comparing the rate you sent, the rate you intended, and what the guest actually paid, and flagging a gap worth more than 5% in plain money. If you're reconstructing this by hand every cycle, that's the structural fix — the public demo at try.primehostpartners.com is open to try without signing up.