The problem with billing group classes manually

You run a weekly guitar class, an after-school program, or a Saturday morning dance session. Every month, you send the same invoices, chase the same late payers, and manually reconcile who paid and who didn't. Meanwhile, the number of sessions in a given month varies — some months have four Tuesdays, some have five — and parents email you asking why their bill changed.

This is the core tension in group class billing: the schedule is recurring, but the manual work is also recurring. Automating it means making a few decisions upfront so the billing runs itself afterward.

Here's how to think through those decisions, regardless of what tools you're using.

Step 1: Choose your billing model before you set anything up

The single biggest source of confusion in group class billing is mixing up two fundamentally different models. Pick one before you do anything else.

Flat monthly fee (subscription)
Students pay the same amount every month, regardless of how many sessions fall in that month. A music school might charge $149/month for one class per week and $197/month for two — the fee doesn't change whether a month has four or five sessions. This is the simplest model for parents to understand and the easiest to automate, because the invoice amount never varies.

Per-session or credit-based billing
Students pay for the sessions they attend. This sounds fairer, but it creates a recurring administrative problem: months with five sessions require a different invoice than months with four. One studio discovered this the hard way — their credit-based plan worked fine for four-week months but required manual intervention every time a five-week month came around. They eventually switched to a flat monthly model to eliminate that overhead entirely.

Which should you choose?
If your classes run on a consistent weekly schedule and students commit for a term or longer, a flat monthly fee is almost always easier to automate. If attendance genuinely varies week to week (drop-in programs, flexible enrollment), a credit or pack model may be more appropriate — but expect more manual reconciliation.

Step 2: Decide your billing date and stick to it

Two common approaches:

• Bill on the 1st of each month. Clean, predictable, easy for parents to budget. If a student enrolls mid-month, you bill a prorated amount for the remainder of that month, then switch to the 1st going forward. One studio calculated their prorated rate by dividing the monthly fee by four (treating each week as one session), then multiplying by the number of remaining sessions in the month.

• Bill every four weeks. This keeps the billing cycle tied to a consistent number of sessions rather than the calendar. The downside is that the billing date drifts — a student who starts on the 3rd will eventually be billed on the 28th, then the 24th. This confuses some parents and makes cash flow harder to predict.

For most group class programs, billing on the 1st is simpler to communicate and easier to automate.

Step 3: Handle the variable-month problem explicitly

If you choose a flat monthly fee, write down your policy for months with five sessions before a parent asks. The answer is simple: the fee doesn't change. That's the whole point of a flat fee. Document it in your enrollment agreement so there's no ambiguity.

If you choose per-session billing, you need a rule for five-week months. Options:

• Charge for all five sessions (parents may push back)

• Cap billing at four sessions per month (you absorb the cost of the fifth)

• Offer the fifth session as a bonus

Whatever you decide, write it down and include it in your enrollment paperwork. The worst outcome is handling it differently each time.

Step 4: Set up auto-pay from day one

Manual invoicing is the enemy of recurring billing. Even if your invoice amounts are correct, chasing payment every month defeats the purpose of automation.

The standard approach: collect a payment method at enrollment, before the first session. One studio kept auto-pay off by default and sent invoices manually until clients submitted their payment details — this created a gap where invoices sat unpaid. A better policy is to make payment method submission a condition of enrollment, not an afterthought.

Practically, this means:

• Include a payment authorization form in your enrollment packet

• Don't confirm a spot in the class until the form is returned

• Set a clear policy on what happens if a payment fails (retry after 48 hours, then pause enrollment)

Step 5: Write a clear cancellation and proration policy

Recurring billing only works if parents know what they're committing to. Before you automate anything, write down answers to these questions:

• How much notice is required to cancel? (30 days is standard)

• Is the first month's payment refundable?

• If a student joins mid-month, how is the first invoice calculated?

• What happens if a session is cancelled by the school — is a credit issued?

One after-school program charged the full monthly fee even when school started mid-month, because their enrollment agreement made that policy explicit upfront. Parents accepted it because it was disclosed clearly, not sprung on them.

Step 6: Automate reminders, not just invoices

An invoice sent without a reminder is often an invoice paid late. Build a reminder sequence into your process:

• Send the invoice 14 days before it's due

• Send a reminder 3 days before the due date

• Send an overdue notice 1 day after the due date

One school set their invoice due date buffer to 14 days globally, which standardized their billing cycle and reduced the number of late payments they had to chase. They also set a rule to skip reminders for invoices that had already been reminded recently, to avoid annoying parents with duplicate messages.

Step 7: Test your setup with one class before rolling out

Before you automate billing for every group class, run one class through a full billing cycle manually — but following your new rules exactly. Check:

• Did the invoice amount match your policy?

• Did the billing date land correctly?

• Did the prorated first invoice calculate correctly?

• Did the reminder go out on time?

Fix any gaps before you scale. One studio discovered a rounding error in their hourly rate calculation that was generating invoices for $39.99 instead of $40.00 — a small thing, but it eroded parent trust and required manual corrections.

A note on the tool you use

The decisions above — billing model, billing date, proration policy, auto-pay rules, reminder cadence — are the hard part. The software is secondary. Once you've made these decisions in writing, any billing system worth using should be able to execute them.

Noto is built specifically for schools that run group classes alongside private lessons, and the billing logic described here — flat monthly subscriptions, prorated first invoices, auto-pay enrollment, configurable reminders — is what we designed it around. But the policies have to come from you first.