To take a deposit for a tour, define the total price, the amount due now, the remaining balance and the deadline before asking the guest to pay. Keep both payments attached to one booking reference. Confirm receipt using your payment records rather than relying only on a screenshot sent in a chat.
A deposit changes the way a booking is paid. It does not remove the need to control capacity, explain the activity conditions or record what is still outstanding.
Decide exactly what the first payment covers
Choose whether your process uses a fixed amount per booking, an amount per participant or a percentage of the total. State the currency and whether any optional extras are included in that calculation. A guest should not need to infer the remaining amount. When calculating margins, distinguish booking commissions from flat fees as well as payment-processing costs.
There is no single deposit percentage that fits every activity. Consider when you must commit resources, when suppliers require payment and how much manual follow-up your team can manage. Keep the commercial decision separate from what your current software can implement.
Show the calculation plainly
Illustrative example, not a TurIA price or a recommended deposit rate: a booking totals €200 and the business chooses a €50 initial payment. After that payment is verified, €150 remains due. If the booking changes, recalculate the total and show how the amount already paid is applied.
Use one booking record with these fields:
- Booking reference and activity date.
- Total agreed price and currency.
- Verified amount received, with payment date and reference.
- Remaining balance and due date, including time zone where relevant.
- Person responsible for checking receipt and contacting the guest.
Send a clear payment summary
Adapt this operational template to the terms already agreed with the guest: After verifying the payment, show the remaining payment in the confirmation sent to your guest.
Booking [reference] — [activity and date]. Total: [amount and currency]. Initial payment due: [amount] by [deadline]. Remaining payment: [amount] by [deadline], using [method]. Booking and cancellation conditions: [link to your actual terms]. We will send confirmation when the required payment has been verified.
Explain what confirms the place and what happens when the payment deadline passes, consistently with your published terms. Do not use an automatic “fully paid” message for a booking that still has an outstanding balance.
Check the money before updating the payment status
Match each payment against the booking reference and actual transaction record. A message saying “paid” and a bank-transfer screenshot do not by themselves establish that the funds have been received. Record partial receipts without marking the full amount settled.
Before the final deadline, review outstanding balances and send a factual reminder containing the reference and amount due. If a payment is disputed or cannot be matched, investigate it before sending another payment request. After a cancellation or price change, reconcile the booking record and any refund separately.
Check that your booking tool supports the whole process
Ask for a demonstration of initial payment, remaining-balance tracking, changed participant counts, failed payments and cancellation. Support for a payment method alone does not prove that split payments or automated balance collection are available.
In TurIA — Booking System, discuss the exact payment workflow you need before adopting a deposit model. This guide describes an operational process; it does not promise automated deposit or balance collection in TurIA. Also review how to coordinate WhatsApp and website availability so payment and capacity records remain aligned.