How do I automate hotel deposits and balance payments without charging twice?
Build a payment schedule that checks what is owed, who should collect it and what has already been paid before each collection.
Automate the amount still due, with a fresh status check before every payment. Separate deposits from balances, identify whether the hotel or OTA collects, and deduct verified payments already received. Pause when a booking changes or a transaction is pending. Ask your supplier to demonstrate duplicate protection across scheduled charges, payment links and reception payments, with a clear approval process for exceptions and retries.
Define who collects each payment
For each rate plan, record the deposit amount, balance deadline, collection method and exception owner. Distinguish a payment request, which asks the guest to pay, from an automatic card charge. A sent email is not a completed payment.
For OTA reservations, identify the collection arrangement per booking. Booking.com distinguishes guest payments from partner payouts, including bank transfers and virtual credit cards (VCCs). Exclude OTA-collected accommodation from guest deposit reminders; request only separately verified guest-payable items. A delayed OTA payout does not mean the guest owes the room charge again.
For later card charges, retain permission covering the timing and amount calculation. Stripe’s guidance on future payments explains this consent requirement. Card details alone are insufficient authority for unrestricted collection; confirm your provider’s requirements.
Build a timeline around the outstanding amount
Illustrative example: a direct booking costs £600, with a 30% deposit and the balance due seven days before arrival. The guest later agrees to a £720 stay. These are fictional final guest prices including any applicable VAT, with no refunds, fees or other adjustments.
| Payment moment | Status check | Action and remaining balance |
|---|---|---|
| Booking confirmed | Hotel collects; agreed price £600; no existing successful payment. | Collect £180 deposit once. £420 remains. |
| Dates and price change | Revised price £720; £180 deposit remains allocated. | Supersede the old balance deadline. £540 remains; no second deposit. |
| 10 days before revised arrival | Guest pays an additional £60; verify the transaction and its allocation. | Record £240 paid in total. £480 remains. |
| 7 days before revised arrival | Booking active; £240 paid; no pending collection; permission still applies. | Request or collect £480. Mark paid only after confirmed success. |
| Arrival | £180 + £60 + £480 = £720 successfully collected. | £0 accommodation balance. Suppress further collection. |
Recalculate from the current booking total and verified allocated payments. Do not reuse an old scheduled amount. A pre-authorisation is a hold, not money collected; a pending payment needs investigation before another attempt.
Make repeated instructions mean “check”, not “charge again”
Idempotency means the same payment instruction can be repeated without creating another collection. Think of a unique reference for one deposit or one balance payment. If the connection drops, the software checks that instruction’s result instead of starting a fresh charge.
Stripe documents idempotency keys for this purpose. The protection has conditions and a retention period; it does not automatically cover a separate terminal payment. Your supplier must also check the booking’s payment history and prevent two collection routes acting on the same amount together.
Demo test: let a guest pay a balance link while reception attempts to collect it. Ask to see one successful collection, the updated balance and the record of the blocked or withdrawn second attempt. If this cannot be demonstrated, require a manual check before competing collection routes are used.
Set stop rules for changes and failed payments
Give reception an exception queue with a named owner. The following are acceptance criteria for your workflow, not a claim that every PMS implements them automatically.
| Exception | Required action before collecting |
|---|---|
| Changed arrival or price | Replace the old schedule, carry forward allocated payments and confirm revised terms. Withdraw or update obsolete payment links. |
| Cancelled booking | Stop scheduled accommodation collections and reminders. Review any permitted cancellation charge separately against payments already held. |
| Confirmed failed payment | Read the provider’s failure reason. Check for other successful or pending attempts. Retry only when permitted and authorised, or ask the guest to complete a secure payment. |
| Timeout or pending status | Do not treat it as a decline. Check the original transaction with the provider; hold further collection until its outcome is known. |
| Deposit already paid elsewhere | Verify and allocate the receipt before enabling automation. Record the payment; do not process it again. |
| Booking inside the payment window | Apply the agreed last-minute policy once. Check whether the initial payment already covers the balance before triggering another request. |
If authentication is required, ask the guest to complete the provider’s secure flow. A refund or disputed payment should trigger review, not an automatic replacement charge.
Test your deposit workflow with RoomRaccoon
RoomRaccoon’s UK integrated hotel payments page describes payment links, prepayment plans, VCC monitoring and payment permissions. Its hotel property management system connects reservation information with payment status and offers online check-in payment options.
The official Advance Collect documentation describes scheduled deposit requests by rate plan. It distinguishes payment during direct booking from pre-arrival requests; eligible OTA use depends on Hotel Collect settings and receipt of guest card details. This does not establish support for every deposit-plus-balance schedule.
- Confirm the UK provider, package, any upgrade and channel requirements for your exact workflow.
- Demonstrate changed dates, a prior deposit, a failed charge and an OTA-collected stay.
- Show which steps are requests, automatic charges or staff actions, and who can approve exceptions.
Bring the £720 example and your own deposit policy. Ask to see the £480 balance recalculated, the old schedule stopped and a duplicate attempt handled before deciding which steps to automate.
See how your payment workflow could connectQuestions before switching on automation
Should the balance always be a fixed percentage?
No. After amendments or extra payments, calculate the balance from what is currently owed. In the example, collecting 70% of £720 would take £504 instead of the correct £480.
Can I leave an earlier payment link active?
Only if its behaviour has been verified. Test whether it shows the current amount and prevents collection after payment or cancellation; otherwise withdraw it and issue an appropriate replacement.
What should staff check if the guest says they have paid?
Check the provider transaction, booking reference, amount and status. Resolve missing allocation or delayed confirmation before asking for another payment. An unpaid PMS balance alone is insufficient evidence of failure.
Sources and checks
Checked 10 November 2026. Provider documentation explains payment controls; it does not establish identical behaviour in every RoomRaccoon configuration.
- RoomRaccoon UK: Payments and PMS.
- RoomRaccoon Help: Advance Collect.
- Stripe: Idempotent requests, payment lifecycle and permission for future payments.
- Booking.com: payment and payout details.












