Camp tuition payment plans and deposits

Tuition rarely arrives as one payment. Families ask to split it, a deposit holds the spot, and the balance trickles in across the spring. Run that on a spreadsheet and you become the reconciliation engine — matching a charge to a row, remembering who’s behind, sending the reminder, updating the cell. None of it is hard. All of it is easy to get wrong, and a wrong number in a parent’s account is a phone call you didn’t want.

This is a guide to running camp tuition deposits, payment plans, and autopay so the balance owed is always one number — the same whether a parent reads it or you do. It works on a spreadsheet. It works better when the plan lives on the registration itself, and we’ll be plain about where that helps.

What a payment plan actually is

Strip away the spreadsheet and a payment plan is simple. It’s a deposit taken at registration, then a set of installments, each with three things: an amount, a due date, and a status. The status is one of four — pending, paid, overdue, or waived. That’s the whole model.

The trouble starts when those three things live somewhere other than the registration. The amount is in your pricing sheet, the due dates are in a calendar, the status is in your head or a column you update by hand. Now the same plan exists in three places, and the three drift. A family pays early, the spreadsheet says overdue, and you’re explaining a number that isn’t real.

When the installment schedule is part of the payment record on the registration, the plan is one object. The deposit is the first paid line. Each later installment carries its own due date and flips to paid when the charge clears. The balance owed is a sum the record computes, not a figure you maintain.

The deposit does two jobs

A deposit is the most useful payment of the season, and not because of the money. It does two jobs at once.

First, it confirms intent. A spot held for a family that registered on a whim and drifted away is a spot a committed family couldn’t take. A deposit is the small commitment that sorts real registrations from maybes — and it does it at the moment of registration, when the family is most decided.

Second, it starts the payment relationship early. The larger tuition balance is months out. The deposit gets the family’s payment method on file and the first line of the plan settled now, so the rest of the schedule has somewhere to attach. Treat the deposit as the first installment on the plan, not a separate charge you’ll match up later, and there’s nothing to reconcile — it’s already part of the same record as everything that follows.

Installments that run on a schedule

Once the deposit is in, the rest of tuition becomes a schedule. You set the installment dates and amounts; the system holds them. Each installment sits in pending until its due date, then it’s either paid or it’s overdue — and overdue is the state that costs you time.

The work in a manual plan is all in that overdue state. You scan for who’s behind, draft the reminder, send it, and check back later to see if it landed. Multiply that across a few hundred registrations in the busy spring and it’s a recurring afternoon.

Two things shrink that afternoon. The first is a clear view of which installments are overdue across every registration, so finding them is reading a list rather than scanning a spreadsheet. The second is autopay.

Autopay, and why it earns its keep

Autopay charges a saved payment method on each installment’s due date. A family turns it on per registration; from then on, the installments settle themselves on schedule. The saved card is held by the payment processor, not parked on your own records, so you’re holding a token, not a card number.

For the family, autopay is one fewer thing to remember. For you, it’s the reminder you don’t have to send and the overdue installment that never happens. The plans on autopay drop out of your chase list entirely, which leaves the short list of families who genuinely need a nudge — and that’s a far shorter list to work than “everyone with a balance.”

When autopay is off, the fallback is a reminder you can send against outstanding balances rather than a note you write from scratch each time. Either way, the schedule, the saved method, and the balance are the same record — not three tools you keep in sync by hand. That single-record idea is the same one that makes season close-out a reconciliation instead of a rebuild.

When a family needs to change the plan

Plans change. A family’s circumstances shift, a job changes, and the schedule that worked in February doesn’t work in April. The question is whether that change is a clean edit or a mess.

On a spreadsheet, a plan change is an email thread, a manual rewrite of a few cells, and a note to yourself you’ll forget. Three months later you can’t reconstruct what was agreed or when.

When the request flows through the record, a family asks for the change from their own account, it lands in your queue with the registration attached, and you approve or deny it with a note that stays on the record. The installment schedule updates in place. The plan the parent sees and the plan you bill from never diverge, because they were always the same plan. If the conversation is really about affordability rather than timing, that’s a different tool — financial aid — and it’s worth keeping the two separate so a hardship isn’t quietly absorbed into a payment plan that still doesn’t fit.

What the spreadsheet can’t give you

A spreadsheet can hold a plan. What it can’t do is keep the plan, the payments, and the balance as one truth. Every manual step — matching a charge, updating a status, sending a reminder, editing a schedule — is a place where the parent’s version and your version drift apart. Most of the season’s payment friction is that drift.

When payments live on the same camper record as the registration that owes them, the drift has nowhere to start. The deposit is the first paid line. The installments flip themselves to paid as charges clear. The balance is a sum, autopay settles the routine ones, and a plan change is an edit to one object rather than a reconciliation across three. Camp Runner is one system for that record — registration, payments, and the rest on a single camper, priced at $1.50 per active camper per month for the whole thing — and you can estimate that for your roster in about a minute.

You set the tuition and the terms. Camp Runner carries the schedule, so the balance owed is one number — the same one the family sees. Payment plans are one piece of camp payments and billing kept in step with the roster. If a stitched-together stack is what’s making that number hard to trust, joining the waitlist is where to start.