Why one stay can create several payment events
A hotel payment rarely happens in a single step. A booking may involve a deposit, a card check, a hold at check-in, additional room or restaurant charges, and a final payment at checkout. After that, the hotel still needs to match its records to the payment provider’s records and the money deposited in its bank account. Treating these as separate events makes both guest conversations and back-office work easier.
The property management system, or PMS, records the stay and its charges. A payment terminal or online checkout sends card transactions through a payment provider. Those systems may update at different times, so a folio marked paid does not necessarily mean the funds have reached the bank. Clear procedures should identify which system staff use to confirm each stage.
Authorizations reserve funds; they are not final charges
An authorization asks the card issuer to approve an amount. Hotels commonly use one to check that a card can cover expected charges, including an allowance for incidentals. The issuer may place a temporary hold on available funds or credit. Although the guest can see that hold in their banking app, it is not the same as a completed payment to the hotel.
The authorized amount should follow the property’s stated policy and the expected stay. If the stay is extended or charges rise, the team may need an additional authorization rather than assuming the original one will cover everything. Staff should record which folio and guest the authorization belongs to and avoid creating a new hold simply because an existing one is hard to find.
Guests benefit from a straightforward explanation at booking or check-in: what amount may be held, what the hold covers, and how the final charge will relate to it. When a hold is released, the time it takes to disappear from the guest’s account can depend on the card issuer and payment method. Staff should avoid promising an exact release time they cannot control.
Settlement turns approved transactions into payments
At checkout, the hotel confirms the folio, applies any deposit or prepaid amount, and charges the balance owed. Depending on the payment setup, a final charge may use an earlier authorization or be processed as a separate transaction. Staff should check the actual result in the payment system rather than assuming that an approved hold automatically became a payment.
Completed transactions are typically grouped and submitted for settlement. The payment provider then processes them before funds reach the hotel’s bank account. A transaction can therefore appear on a guest folio, in a settlement report and on a bank statement on different days. Refunds and voids also need careful handling: reversing a transaction before settlement can produce a different record from refunding one that has already settled.
A simple checkout control is to compare the final folio with the intended payment amount before handing over the receipt. Particular attention is useful when a reservation has been split between guests, a deposit was paid earlier, or a room charge has been transferred from another outlet. These are common points at which a correct service interaction can still produce a confusing bill.
Reconciliation connects the folio to the bank
Reconciliation answers three questions: What did the hotel say it charged? What did the payment provider process? What did the bank receive? Teams can start with the PMS or point-of-sale totals, compare them with transaction and settlement reports, and then match the resulting deposits to bank entries. The amounts may not be identical at every step because of fees, refunds, chargebacks, different settlement dates or other adjustments shown in provider reports.
Useful records include the transaction identifier, date, tender type, folio or outlet reference, gross amount, refund amount and settlement batch. Someone reviewing exceptions should be able to trace a difference to an individual transaction without relying on a guest’s card details. Unmatched items should remain on a visible exception list with an owner and a follow-up status, rather than being buried in a daily total.
For example, a restaurant charge posted to a room may be present in the PMS but absent from the card settlement report until the guest pays the final folio. That is an expected timing difference, not necessarily missing revenue. By contrast, a settled card transaction with no matching folio entry calls for investigation. Labelling the reason for each difference helps the next shift avoid repeating the same work.
Build controls that support guests and staff
Payment procedures work best when front desk, restaurant and accounting teams use consistent references and know when to escalate an exception. Set out who may adjust a folio, issue a refund, retry a failed payment and close a batch. Review unusual items promptly, especially duplicate-looking charges and payments tied to cancelled or modified bookings. Keep an audit trail so corrections can be understood later.
Handle card information only through approved payment tools, and limit access to payment records according to staff roles. Training should include how to explain a hold without calling it a charge, how to provide a clear receipt, and how to direct a guest to the right team if a bank display differs from the hotel’s records. Good payment operations are not just an accounting task: they help a guest leave with a bill they can understand and give the hotel a reliable account of what it has earned.
