How to split holiday costs when people stay different numbers of nights

An equal split can become unequal when one friend stays two nights and another stays five. Start by separating costs that vary with presence from costs the group committed to regardless of attendance.

In this guide: Compare per-night, per-person and fixed-cost allocations with worked examples.

1. Classify the bill

Separate nightly accommodation, fixed booking fees and optional personal spending. Decide which parts should follow occupied nights and which parts belong to the original booking commitment.

2. Choose the allocation before paying

A person-night method can work when everyone agrees the accommodation is a shared resource. A room-night method may fit private rooms better. Neither is automatically fair in every arrangement, especially if someone’s late change leaves an already-paid room empty.

3. Reconcile the real attendance

Confirm final nights and receipts before closing the split. Record refunds and changes explicitly. Avoid changing the method after people have accepted a cost on a different basis.

Worked example: what this looks like

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

Fictional example: accommodation is AUD 900. Ana stays three nights, Bo three and Cam two, giving eight person-nights. At AUD 112.50 per person-night, Ana and Bo each pay AUD 337.50 and Cam pays AUD 225. A separate AUD 90 fixed cleaning fee is split three ways by prior agreement. Final shares are AUD 367.50, AUD 367.50 and AUD 255, totalling AUD 990. This is an agreed example, not a rule for every booking.

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.

Accommodation will be split by [person-nights / room-nights / agreed method]. Fixed fees use [basis]. Confirm your nights before [deadline]. Changes after booking will follow [agreed terms], not an automatic recalculation that transfers an unapproved cost to others.

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.

Show the calculation, not just the final number. If someone disagrees, resolve the principle first rather than arguing over cents.

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