Deposits, instalments and bank transfers: taking camp payments without chasing

The chasing problem

Ask any organiser what they dislike most about running camps and it is rarely the coaching. It is the spreadsheet with a column called 'Paid?' and the forty messages it takes to fill it in. A bank transfer arrives labelled 'camp', a parent swears they paid in March, a sibling discount was promised verbally, and the total in the bank never quite matches the total on the sheet.

None of this is a character flaw in parents. It is what happens when the booking and the payment live in different places. The fix is structural: decide how you want to be paid, make each payment identifiable on its own, and let the system do the matching.

Choose your rails deliberately

UK families are used to three ways of paying a club: card online, bank transfer, and cash at the desk. Each has a cost and a failure mode. You do not have to offer all three, but you should choose consciously.

• Card. Fastest to confirm, easiest for families, and the only rail that can charge an instalment later without asking. You pay a processing fee per transaction; check the current rate with your provider before pricing.
• Bank transfer. No processing fee and familiar to every parent, but it only works if every transfer can be tied to a booking without a conversation. That means a unique reference per booking and a deadline.
• Cash. Still common at the desk on day one. It is fine as long as it is recorded against the booking immediately; cash that is 'sorted later' is the source of most end-of-season discrepancies.

Deposits: hold the place, not the whole fee

A deposit does two jobs. It secures commitment from the family — people rarely drop a camp they have paid £40 towards — and it lets families book early without finding the full fee in the same month as a holiday. For a week-long camp, a deposit of roughly a quarter to a third of the price is common; the rest falls due a few weeks before the start.

Be explicit about what the deposit is. Refundable until a date? Transferable to another week? Non-refundable? Write it in the booking terms the family sees before they pay, and apply it consistently. Most disputes about deposits are really disputes about terms nobody read.

Instalments: the plan does the chasing

Instalments are where families say yes to a camp they would otherwise skip. The pattern that works is simple: a deposit on the day of booking, then a fixed number of dated payments, with the final one landing before the camp starts. Three or four payments is plenty; more than that and the admin outweighs the benefit.

The part organisers get wrong is manual instalments. If each payment depends on the parent remembering a date and initiating a transfer, you have simply multiplied the chasing problem by three. Instalments should charge the card the family saved at booking, automatically, on the due date. A failed charge should be retried and the family told, not quietly cancel the place.

• Show the full schedule before the family commits: dates and amounts, not 'three easy payments'.
• Send a reminder a few days before each charge so the money is in the account.
• Decide in advance what happens if the final instalment fails: a grace period, then the place is released.
• Keep the deposit and the instalments against the same booking so the balance is always one number.

Deadlines and holds

A booking that is not paid is not a booking; it is a held place. Holds are useful — they stop two families grabbing the last spot while one of them is still typing — but they need an expiry. For bank transfer, a deadline of a few days after booking is typical. For card, the hold only needs to last as long as the checkout.

When a deadline passes, release the place back to availability and offer it to the waitlist. Doing this reliably is the difference between a waitlist that sells places and one that just makes people cross.

Discounts, extras and the one total

Sibling discounts, early-bird pricing, lunch, kit, a second week — all of these are fine as long as they are applied on the booking page and show up in one total. A discount 'agreed by text' that is not on the booking is a reconciliation problem waiting to happen. If a family books several children, charge one total under one family reference, but keep each child as a separate booking with its own pass so the register still works per child.

Refunds and disputes without rewriting history

Refund a booking and the temptation is to edit the amount in the spreadsheet. Don't. Record the refund as a separate event — date, amount, reason — and leave the original payment alone. At the end of the season you want to be able to say 'we took £X, refunded £Y, and here is every line', not 'the numbers moved and I am fairly sure it is right'.

The same applies to card disputes. A chargeback is an event with a date and an outcome. Note it, respond with the booking record and the terms the family accepted, and keep the place's status honest in the meantime.

A pricing structure that takes care of itself

Put it together and a well-run camp's money looks like this: a public price with an early-bird window, an optional deposit-and-instalments path for week-long camps, card and bank transfer both accepted with a deadline, one total per family, and a ledger where nothing is ever edited — only added. Families understand exactly what they owe and when. You spend Sunday evening doing something else.

If you want to see how that looks in practice, FormSide's product page walks through the whole payment flow, and the free plan lets you publish a real camp with bank-transfer references and status tracking without entering a card.