Billing a Language School: Private Lessons, Group Classes and Corporate Cohorts
Most software can take a payment. Very few can bill the way a language school actually earns money. That is the gap that quietly costs you hours every week — because a language school doesn’t have one revenue stream, it has three, and each of them needs completely different billing logic. A parent paying for a child’s after-school French course expects to tap a card or set up a Direct Debit. A retired professional taking weekly 1:1 Spanish lessons buys a pack and tops it up. A multinational that sends eight employees to a weekly Business English cohort wants a proper invoice with a purchase order number, payable in 30 days, addressed to accounts payable — not to a learner. Trying to run all three through a single billing model is where language school owners lose evenings to spreadsheets and “just following up on that invoice” emails.
This is a guide to billing those three streams cleanly, and to pulling them back into one system so you can see, at a glance, who has paid and who hasn’t — across consumer and corporate, private and group.
Why a language school is a billing edge case
A gym sells memberships. A tutoring centre sells appointments. A language school sells private tuition, scheduled group courses and invoiced corporate training — frequently to the same operation, in the same week, taught by the same language teacher. The complexity isn’t in any one of those models. It’s in running all three at once without three separate spreadsheets.
Here’s the shape of it. Your evening A2 Italian group meets weekly for a 12-week term; ten adult learners each pay a £180 term fee, some upfront, some in three monthly instalments. Your 1:1 German learners buy packs of ten lessons and rebook as they go. And your corporate clients — a law firm, a logistics company, a hospital trust — each run a closed cohort on their own schedule, billed monthly against a PO, with an attendance export attached so their L&D team can prove the training happened. Three pricing structures, two completely different payer types (the learner versus the employer), and one owner trying to reconcile it all on a Sunday night.
Challenge: A single language school can carry consumer card payments, consumer Direct Debits, prepaid lesson packs, termly instalment plans, and 30-day corporate invoices with purchase orders — simultaneously. Generic booking tools are built for one of these. The moment you need consumer self-checkout and a properly addressed B2B invoice in the same dashboard, most tools force you into manual workarounds, and the manual workarounds are where money goes missing.
Stream one: private lessons — cards, packs and Direct Debit
Private tuition is your highest-margin, lowest-volume stream, and it bills like retail. The learner (or the parent) is the payer, the amount is small enough to take on a card, and the relationship is recurring. The job here is to make paying frictionless and collection automatic.
For one-off and pack purchases, card checkout at the point of booking is the right default — the learner picks a slot, creates a booking and pays in the same flow, before they’ve left the page. For ongoing 1:1 learners on a weekly rhythm, this is where Direct Debit earns its keep. Set the learner up once on GoCardless Direct Debit and their monthly fee is pulled automatically — no expiring cards, no manual rebilling, no chasing. The full menu of payment options — Stripe cards and wallets, GoCardless Direct Debit, bank transfer — lets you attach the right method to the right product rather than forcing everyone through one checkout.
What this looks like in practice: A parent enrols their 11-year-old in a weekly after-school French course priced at £150 for the term. At checkout they choose Direct Debit and split it into three monthly instalments of £50. The first instalment is collected on enrolment; the next two pull automatically on the 1st of each month. The parent never thinks about it again, and you never send an invoice — the money simply arrives. That is the entire point of consumer billing in a language school: it should disappear into the background.
Stream two: group courses — terms, deposits and instalments
Group language courses are where term-based billing logic matters most. A language course isn’t a single transaction — it’s a block of weekly sessions tied to a calendar, often with a holiday break in the middle, frequently sold with a deposit to secure the place and an instalment plan to spread the rest.
Tie the price to the term, not to individual sessions. When you define a 12-week course running, say, mid-September to mid-December with a half-term gap, the system should know the course is 12 sessions and bill the term fee accordingly — with the option of a non-refundable deposit at enrolment to lock the seat, then the balance over two or three instalments. Proration handles the awkward cases: a learner who joins in week four of a course-based programme pays for the eight sessions remaining, not the full twelve. Registration fees, sibling discounts and coupons layer on top of the same structure.
This is also where deposits do double duty as a commitment device. A small upfront deposit dramatically reduces no-shows and last-minute drop-outs for group language classes, because the learner has skin in the game before week one. The balance can then sit on an instalment plan that the learner barely notices — the same Direct Debit machinery from your private stream, applied to a different product.
Stream three: corporate cohorts — invoices, POs and consolidated billing
This is the stream that breaks generic software, and it’s also where the largest, most reliable revenue tends to sit. Corporate billing is fundamentally different because the payer is not the learner. Eight employees attend a weekly Business English class; the company pays. That single fact changes everything about how the money is collected.
Corporate clients need real invoices — addressed to the company, not the learner — carrying a purchase order number and, often, a cost centre so their finance team can route the cost internally. They expect payment terms (Net 30 is typical), and they want one consolidated invoice for the whole cohort, not eight separate consumer receipts. Proper billing and invoicing for this stream means grouping all eight learners under a single company invoice, stamping it with the client’s PO, and exporting the attendance record alongside it so the client’s L&D team can evidence delivery against the spend.
What this looks like in practice: A logistics firm enrols a cohort of eight employees in a weekly intermediate English course. You bill the company monthly: one consolidated invoice per month, addressed to accounts payable, carrying the client’s PO number and their internal cost centre, with Net 30 terms and an attendance export attached. The eight learners never touch a payment screen — they just attend. The finance contact gets one predictable invoice a month they can pass straight through their AP system. That predictability is exactly what wins and keeps corporate contracts.
Automating reminders and chasing overdue invoices
Across all three streams, the single biggest hidden time sink isn’t taking payments — it’s chasing the ones that don’t arrive. A failed Direct Debit on a parent’s instalment. A corporate invoice sitting unpaid at day 35. A pack-buyer who meant to top up and forgot. Done by hand, this is an hour a week of awkward, easily-forgotten follow-up.
Automatic payment reminders take it off your desk entirely. Reminders fire at the right moment — before a due date as a nudge, after it as a chase — each one linked to the correct invoice and the correct amount, sent by email or WhatsApp, in the learner’s language. For consumer instalments, a friendly pre-due nudge prevents most failures before they happen. For corporate invoices, a scheduled Net 30 follow-up sequence means your largest invoices get chased politely and consistently without you writing a word — and without the relationship-damaging silence of a forgotten invoice followed by a frosty phone call.
Pulling it back into one view
Three revenue streams are only manageable if they report into one place. The reason most language school owners feel busier than their headcount justifies is that consumer payments live in one tool, corporate invoices in another, and the actual answer to “who owes us money right now?” lives in their head.
Consolidation is the real win. A single reports and dashboard view should show paid versus unpaid across every stream at once — card payments, Direct Debits, deposits, instalment plans and corporate invoices side by side — so you can see term revenue, outstanding balances and overdue corporate POs without exporting anything. This is also the practical case for proper language school software: not because any one billing model is hard, but because seeing all three together, accurately, in real time, is what turns billing from a Sunday-night chore into a glance.
That’s the difference between software that can take a payment and software that can bill a language school. One handles a transaction. The other handles your business — the private learner on Direct Debit, the term-fee group with a deposit, and the corporate cohort of eight invoiced monthly against a PO — and tells you, at any moment, exactly where your money is.
If billing across private, group and corporate streams is currently spread across spreadsheets, separate payment tools and your memory, it’s worth seeing it consolidated. Start a free trial and set up all three revenue streams in one place — no credit card needed.
