Use the booking as the organising reference, while keeping each collection, supplier payment and refund as a separate record.
A booking rarely means one transaction
A travel business may collect a deposit, request the remaining balance, pay accommodation and transport suppliers, and later handle a partial cancellation. These are related events, but they should not be collapsed into one paid-or-unpaid flag. Start with a booking reference that survives itinerary changes and remains searchable by operations, support and finance.
Make each collection understandable
For an assisted booking, a payment link can help the customer complete a specific request without a custom checkout. A website can instead use hosted checkout. In either case, record whether the collection is a deposit, a balance or an additional service. For an illustrative ₹30,000 booking with a ₹10,000 deposit, the booking system should calculate the remaining balance; a payment provider should not be assumed to own that business calculation.
Keep supplier payments separate
An incoming customer payment is different from an outgoing hotel or transport payment. Retain the supplier invoice, approval and payout reference independently, then associate them with the booking. Before sending funds, check beneficiary information and whether the selected payout method is enabled. Do not infer automatic splitting, escrow or supplier settlement from a general collections-and-payouts feature list.
Plan cancellation decisions explicitly
Your cancellation policy determines eligibility and the amount to return. Record that decision before creating a refund. Keep the original payment reference and the separate refund identifier together so the team can explain what was requested and what has completed. If the original booking was paid in several instalments, investigate which payments the approved refund relates to.
Connect the workflow with ZytePe
ZytePe’s travel solution brings attention to booking collections, approved supplier payouts and payment-status visibility. Pair the enabled payment tools with your reservation system, which remains responsible for itinerary, pricing and cancellation decisions. Review the full deposit-to-refund process with your team before integration, including pending payments and interrupted requests.
Sources & further reading
Industry references support the concepts above. ZytePe capabilities and integration details are described in the linked product documentation.