Who pays the deposit on a group booking?

A deposit deadline can quietly turn one friend into the group’s lender. Before anyone fronts money, agree the collection process, what the deposit secures and what happens if someone does not follow through.

In this guide: Agree collection deadlines, responsibility and repayment before one person fronts the cost.

1. Identify the actual deposit terms

Record the amount, currency, deadline, refund conditions and booking holder. Distinguish a refundable security hold from a part-payment of the trip price.

2. Collect commitments before advancing money

Agree each person’s share and payment timing. If someone voluntarily fronts the amount, document reimbursement expectations and the limit they are comfortable with. Do not assume the person with the available card can absorb everyone else’s delay.

3. Keep payment evidence separate from promises

Record what has actually been paid and received. A budget entry or a yes vote is not a completed transfer. Pause booking if the agreed collection condition is not met.

Worked example: what this looks like

Fictional scenario—not a real customer story or executed AI result.

A fictional accommodation deposit is AUD 600 for six travellers. The crew agrees AUD 100 each before the booking deadline. Five contributions arrive; the organiser does not silently lend the sixth. They contact that traveller and either explicitly agree a short advance or hold the booking process. The later balance deadline is recorded separately.

Keep estimates, commitments and actual payments distinct

Use three columns in the shared record: proposed allowance, accepted commitment and actual amount paid. They answer different questions. A budget tells you what the crew intends to spend; a supplier confirmation shows what was purchased; a payment record shows who supplied the money.

Always preserve the original currency and label any conversion basis. Keep refundable holds and expected refunds separate from final consumed costs. Otherwise a tidy-looking total can conceal a temporary funding need or money that has not actually returned.

When someone queries a number, show the underlying receipt, participants and agreed allocation method. Correct missing facts before discussing fairness. If the disagreement is about the method itself, pause the affected allocation and agree it explicitly rather than quietly changing everyone’s share.

A message or brief you can copy

Replace the bracketed fields with your own details. Read the complete text before sending it; copying it here does not send a message or perform an action.

Deposit required: [amount] by [supplier cutoff]. Your agreed share: [amount], due to [booker] by [earlier time]. Refund conditions: [verified terms]. Booking proceeds when [collection condition]. Any advance needs a separate explicit agreement.

Before you call it settled

• The total matches its component amounts and currency.
• Payers, beneficiaries and the allocation method are visible.
• Estimates, refundable holds and actual payments are separate.
• The exact supplier terms have been checked before committing.
• Everyone affected has agreed to the relevant cost boundary.

Clear deposit handling protects friendships as much as cash flow. Nobody should discover they financed the holiday only after the supplier has been paid.

Put the decision somewhere useful

Keep the agreed plan and the information needed to act on it together in Limbo. Save the useful outcome of the conversation—not every abandoned option—and make clear what is still awaiting confirmation.

Sources and further reading

• Limbo: tracking trip costs
• ACCC: travel delays and cancellations

These references support the workflow and further checks; fictional examples are authored illustrations, not evidence of live prices, bookings or customer outcomes.

Keep planning

• Build an AI trip plan you can actually use
• Group-trip planning guide