The Payment Problem in Holiday Camps

Holiday camps have a uniquely difficult payment landscape. Unlike term-time classes where parents pay a fixed amount on a regular schedule, camp payments involve variable amounts (different days, different add-ons), multiple payment methods (cards, vouchers, TFC), and families with different financial arrangements (some paying upfront, others on account, some via an employer).

When you are running a camp for 80 to 120 children across a six-week summer holiday, you might process 300 to 500 individual transactions. If even 10% of those require manual chasing, reconciliation, or correction, you are spending entire evenings on invoicing instead of preparing for the next day.

Automation is not about removing the human element. It is about removing the repetitive, error-prone tasks so you can focus on the exceptions that genuinely need your attention.

Card Payment Automation

Online card payments should be your default payment method. When a parent completes a booking through your portal, the payment is taken immediately (or a deposit is taken with the balance scheduled for a future date). The booking is confirmed automatically, a receipt is emailed, and the transaction is recorded against the family's account.

Scheduled Balance Payments

Many camps take a deposit at booking (typically 20 to 25% of the total) with the balance due 14 days before camp. Your payment system should automatically charge the balance on the due date using the stored card details (with the parent's prior consent, as required by the Payment Services Regulations 2017).

If the balance payment fails (expired card, insufficient funds), the system should automatically send a payment reminder email with a link to update payment details. Only if this automated process fails should a manual follow-up be required.

Failed Payment Workflows

Set up a three-step automated workflow for failed payments:

Day 1: Automatic email notifying the parent of the failed payment with a secure link to update their card details or pay by alternative method.
Day 3: Second automatic reminder, slightly more urgent in tone, noting that the place may not be guaranteed without payment.
Day 7: Final reminder flagged to you for manual review. At this point you decide whether to release the place or extend the deadline based on the individual circumstances.

This workflow handles the vast majority of payment failures without you lifting a finger. The 5 to 10% that reach the manual review stage are the ones that genuinely need your attention.

Childcare Voucher Reconciliation

Childcare vouchers remain a significant payment method for holiday camps, even though the scheme closed to new entrants in 2018. The reconciliation challenge is that voucher payments arrive from the voucher provider (not the parent) with reference numbers that may or may not match your booking records.

Automating the Match

When a parent books and selects 'childcare voucher' as their payment method, your system should generate a unique invoice reference and instruct the parent to quote this reference when redeeming their vouchers. When the payment arrives from the voucher provider, your system matches the reference to the outstanding invoice and marks it as paid.

In practice, parents sometimes forget the reference or the voucher provider truncates it. Build a fuzzy matching system that also tries to match by amount, child surname, and date range. Flag unmatched payments for manual review rather than rejecting them.

Multi-Provider Management

You may receive voucher payments from five or six different providers (Sodexo, Edenred, Computershare, Fideliti, and others). Each has a different payment cycle and reference format. Maintain a provider register in your system that records each provider's typical payment timeline (Sodexo typically pays within 5 working days, Edenred within 10) so you can forecast cash flow accurately and identify late payments.

Tax-Free Childcare Integration

Tax-free childcare payments arrive as bank transfers from HMRC's paying agent, with a reference that includes the parent's TFC account number. As with vouchers, the key to automation is matching incoming payments to outstanding invoices.

Generate a clear payment reference for each booking and display it prominently on the invoice and in the confirmation email. Instruct parents to use this exact reference when initiating payment from their TFC account. When the payment arrives, your bank feed integration (via Stripe, GoCardless, or your accounting software) should import the transaction and attempt an automatic match.

TFC payments can take up to five working days to clear. Your system should not flag these bookings as overdue during this window. Set TFC-specific payment terms of 7 working days to avoid unnecessary reminder emails being sent to parents who have already initiated payment.

Credit Notes and Account Balances

When a parent cancels a booking and you issue a credit note (rather than a refund), that credit needs to be tracked and automatically applied to their next booking. This sounds simple but is surprisingly fiddly in practice.

Automatic Credit Application

When a parent with an outstanding credit makes a new booking, the system should display the available credit and apply it automatically to reduce the amount due. If the credit covers the full amount, no payment is taken. If it covers part, the parent pays only the difference.

Credits should have an expiry date (typically 12 months) and the system should notify parents when their credit is approaching expiry, giving them the opportunity to book before it lapses.

Sibling Discounts and Family Billing

Sibling discounts should be calculated automatically based on the number of children linked to a family account. The discount should appear on the booking summary before the parent confirms, so there are no surprises.

Consolidated Family Invoices

Parents with multiple children want a single invoice that shows all their children's bookings, the gross total, sibling discounts applied, any credits or vouchers, and the net amount due. Generating individual invoices per child creates confusion and makes it harder for parents to claim through employer schemes or TFC.

Your system should generate consolidated family invoices automatically, either at the point of booking or as a monthly statement for families on account terms.

Reporting and Cash Flow Visibility

Automated payment collection is only useful if it comes with clear reporting. At a minimum, you need:

Daily income summary: Total received today, broken down by payment method.
Outstanding balances: All unpaid invoices, aged by days overdue, with the automated chase status shown.
Voucher and TFC reconciliation: Payments received vs payments expected, with unmatched items flagged.
Forecast: Expected income for the next four weeks based on confirmed bookings and scheduled balance payments.

Every hour you spend chasing a GBP 35 payment is an hour you are not spending on safeguarding training, staff development, or improving the experience for children. Automate the routine so you can focus on what matters.

Key Takeaways

Take card payments at booking with automated balance collection on a scheduled date, and set up a three-step automated workflow for failed payments.
Generate unique invoice references for voucher and TFC payments, and build fuzzy matching to reconcile incoming payments automatically.
Track credit notes on family accounts with automatic application to future bookings and expiry notifications.
Calculate sibling discounts automatically and generate consolidated family invoices rather than per-child invoices.
Maintain real-time reporting dashboards showing daily income, outstanding balances, reconciliation status, and four-week forecasts.