A deposit taken at the time of booking can protect a hotel's cash flow, but poor handling can lead to duplicate charges, incorrect refunds and folio balance disputes. A sound process involves more than taking payment. The property should define in advance which sales terms require a deposit, when and how much is due, which reservation receives the money, what happens on cancellation and how the deposit moves to the folio at check-in. This guide presents a control flow that works independently of individual PMS screen names.

What you will learn in this article
  • Define each deposit rule with an amount or percentage, due date, currency, sales terms and cancellation policy.
  • Match every collected deposit to the reservation, payment transaction and any applicable deposit request; do not post it early or twice as room revenue.
  • Do not delete refunds, forfeitures or transfers to another reservation; preserve the user, date, amount, reason and corresponding transaction reference.

Start the deposit rule with the sales terms

Make the first decision when defining the booking terms, not at the payment screen. State clearly whether the deposit is a fixed amount, a percentage of the stay total or the value of a set number of nights. Also specify the due date, accepted currency, payment method, refund terms and what happens if payment is not received. This keeps front desk agents from having to interpret each booking individually.

In Oracle OPERA Cloud, deposit rules can be linked to a rate code, reservation type or individual reservation, and the system applies an order of precedence. RoomFollow or another PMS may use different labels. What matters is making the applicable rule visible when more than one reaches the same booking, so staff do not have to guess the calculation. If a campaign, channel or group contract differs from the general rule, link that exception to the reservation record.

  • The deposit amount, percentage or number-of-nights equivalent was defined.
  • The due date and the event from which it is calculated were specified.
  • The currency, payment method and cancellation terms matched the sales terms.
  • The team knows which rule takes precedence when rules conflict.

Link the payment to the correct reservation and request

Recording only the amount is not enough when a payment arrives. Keep the reservation number, paying person or organization, payment method, currency, transaction date, bank or payment-provider reference and processing user together. Missing descriptions on bank transfers, virtual POS payments or agency payments can cause money to be linked to the wrong reservation. Hold unmatched amounts on a temporary review list and do not convert them to room revenue before verification.

Oracle's current deposit screen allows a payment to be allocated to a specific deposit request or recorded as unallocated. That distinction matters operationally: money may have been received before staff know which scheduled request it satisfies. Show unallocated amounts on the daily follow-up list and calculate the remaining deposit balance in real time to prevent collecting the same request twice. Any generated receipt should remain accessible with the transaction.

  • The payment was matched to the reservation and deposit request.
  • The relationship was recorded when the payer and guest were different.
  • The transaction reference, currency and user details were preserved.
  • Unmatched and overdue deposits are tracked on separate lists.

Do not confuse deposits with room revenue

Operationally, a collected deposit is a prepayment linked to a reservation; it is not the same event as posting a room night that has occurred. Posting all future room charges as revenue when the deposit is received can create duplicate revenue and an incorrect balance when the room rate posts again at check-in or during night audit. The PMS should track the deposit account separately from revenue and payment transactions on the guest folio.

Accounting and electronic-document treatment may vary by country, the property's contracts and its accountant's advice; this guide is not tax or accounting advice. The operational distinction should still be clear: show the deposit source, available balance and the stay to which it was applied. Room revenue should arise under the property's defined business-date and posting rules, while the deposit should move to the folio at the appropriate time as a payment against the balance.

  • The deposit account and room revenue were kept in separate transaction types.
  • Night-audit room postings were neither skipped nor duplicated because of the deposit.
  • Applied and unapplied deposit balances were shown separately.
  • Accounting and electronic-document rules were confirmed with an authorized financial adviser.

Do not put sensitive card data in notes

Use a compliant payment provider that supplies a payment link, virtual POS or token when taking a card deposit. Copying the full card number into a reservation note, shift log, screenshot or email does not simplify the process; it increases breach risk. PCI SSC requires the card number to be masked on screens, reports and receipts unless there is a business need to display it. Limit access to roles with an explicit business need.

A CVV or similar card verification code must not be stored after authorization, even in encrypted form. The guest's permission does not change that prohibition. A payment-provider transaction ID, masked card details, outcome and amount are sufficient for the PMS record. Do not mark a failed or pending transaction as collected; record each retry with a new transaction reference.

  • The card number is displayed only in the required masked form.
  • CVV is not stored in any note, log or database.
  • Successful, failed and pending payment states are kept separate.
  • Every retry carries its own payment-provider reference.

Preserve an audit trail for changes and reservation transfers

A deposit must not disappear when the date, room, guest or reservation number changes. When a reservation is split or moved to another record, log the source reservation, target reservation, transferred amount, currency, reason and authorized user. Deleting the old record and adding a new payment to the target breaks the link between the two transactions and makes later refunds harder to verify.

Oracle documentation treats deposit transfer as a separately authorized operation and restricts transfers for some negative-deposit or folio configurations. Your PMS may apply different conditions, so the presence of a button does not make every transfer valid. Before transfer, verify the currency, cancellation terms and owner of the target reservation; the balance left at the source should be zero or the expected amount.

  • The source and target reservation numbers appear in the same log entry.
  • The transferred amount, currency, reason and user were recorded.
  • A linked reversing entry or transfer was used instead of deletion.
  • The system blocks unauthorized and unsupported transfers.

Calculate refunds and forfeitures separately on cancellation

When a reservation is cancelled, do not assume that the entire deposit will be refunded automatically or entirely retained as revenue. First read the accepted cancellation policy and the cancellation time. Calculate the applicable penalty, refundable remainder and any deposit already applied separately. If the terms shown to the guest conflict with the PMS rule, staff should not choose silently; they should request an authorized review.

Record a refund as a separate negative payment that references the original collection. Oracle's deposit-payment guide also describes a control that can prevent the refund from exceeding the original payment. Do not treat the refund as complete before receiving the payment-provider or bank result. If a penalty is excluded from the refund, attach the basis, approval and related document; do not confuse a cash refund with an invoice or revenue transaction.

  • The cancellation time was compared with the terms accepted on the reservation.
  • The penalty and refundable amount were calculated separately.
  • The refund was linked to the original payment reference and did not exceed it.
  • The bank result, approving user and reason were logged.

Verify the folio transfer at check-in

When the guest arrives, the deposit must not be left behind on the reservation or collected a second time. The pre-check-in review should show the total received, currency used, any refund or transfer transactions and the available deposit balance. After transfer, the folio should identify the deposit's source record, preserve its payment type and recalculate the guest's remaining balance.

For a group reservation, verify whether the money was collected for the master folio, a room folio or the agency account. Applying a deposit to the wrong folio can make an unpaid room appear settled and a settled room appear to owe a balance at check-out. Cross-check the source deposit balance with the target folio transaction after transfer, and use a system lock that prevents the same amount from being applied again.

  • The available deposit balance was checked before check-in.
  • The correct room, guest, group or agency folio was selected.
  • Source and target transactions matched after the transfer.
  • The remaining balance and payment receipt were confirmed with the guest.

Make the daily deposit follow-up list part of the shift

If deposits are reviewed only when a reservation is created or cancelled, delays between those points remain invisible. Each shift should see requests due today, overdue payments, unmatched bank transactions, failed payment links, pending refunds and available deposits for upcoming arrivals. Including an owner and follow-up time prevents several employees from repeatedly contacting the same guest.

The manager view should separate collected, refunded, forfeited, transferred and unapplied deposit amounts by transaction type and currency. Totals must reconcile with folio and cashier transactions. When there is a variance, create a linked correcting entry instead of deleting history; preserve who changed which value, when and why in an immutable audit trail.

  • Requests due today and overdue requests were listed.
  • Unmatched payments and failed payment links were assigned to an owner.
  • Pending refunds were tracked with their bank result and follow-up date.
  • The deposit subledger was reconciled with folio and cashier totals.
  • Corrections were logged with the user and reason instead of being deleted.
Short answers

FAQ

Does collecting a deposit create room revenue immediately?

Operationally, a deposit is a prepayment while a room posting represents accommodation revenue that has occurred; track them separately in the PMS. Confirm the accounting and electronic-document timing with an accountant because it may vary by country, contract and property practice.

Is a deposit refunded automatically when a reservation is cancelled?

Not always. Review the accepted cancellation policy, cancellation time, applicable penalty and payment-provider result. Record the refund as a separate transaction linked to the original payment, and do not exceed that payment.

Can card details be entered in a reservation note?

Do not enter the full card number or CVV in a reservation note. Use the compliant payment provider's token or transaction reference, and mask the card number on screens, reports and receipts unless there is a business need to display it.

Sources and updates

Operational recommendations should be adapted to the property's own conditions. Information about PMS and channel workflows was checked against the official documents below on 18 September 2026.