Tutoring Centre Payment and Subscription Management

Manual billing in a tutoring centre means spreadsheet package tracking, hand-raised invoices, and admin staff chasing unpaid accounts while session records live somewhere else entirely. When billing and sessions are disconnected, credits fall out of sync and reconciliation takes hours every month.

We build payment and subscription management software for tutoring centres that handles per-session billing, package credits, and recurring plans in one system. Session completion triggers the debit automatically so the balance is always current.

  • Per-session billing and session package credit tracking

  • Monthly subscription plans with automatic recurring billing

  • Failed payment retry and parent notification workflows

  • Revenue reporting by student, tutor, subject, and time period

Recognition

Sound familiar?

  • Tracking session package credits in a spreadsheet that gets out of sync the moment a session is rescheduled or cancelled?

  • Chasing unpaid invoices manually because there is no automated retry or parent notification when a payment fails?

In short

Tutoring centre payment management software handles per-session billing, session package credit tracking, monthly subscription plans with automatic recurring charges, failed payment retries, late cancellation charges, refund management, and revenue reporting by student, tutor, and subject. RaftLabs builds custom billing systems for tutoring centres that need payment collection, package balances, and session records connected in one place rather than reconciled manually across a spreadsheet and an invoicing tool.

Companies we've built for

Vodafone
Nike
Microsoft
Cisco
T-Mobile
Aldi
Heineken
GE
Tutoring businesses served across 3+ markets
3+
Week delivery for payment management systems
6-10
Software products shipped
100+
Cost delivery
Fixed

The manual billing problem in tutoring centres

Most tutoring centres start billing from a spreadsheet. Session packages get entered by hand when a parent pays. Credits deduct after each lesson, if the admin team remembers to update the row. When a session is cancelled, rescheduled, or swapped between tutors, the package balance may or may not reflect the change. By the end of the month, the spreadsheet and the session records disagree, and someone has to spend time working out which is right.

Monthly invoicing is the same problem at a different frequency. An admin team member reviews the session log, calculates what is owed, generates an invoice in a separate tool, and emails it manually. When a parent doesn't pay, the follow-up is a personal email or a phone call. There's no automated retry, no structured escalation, and no hold on sessions until the account is cleared. The centre absorbs the cost of the time spent chasing and the cost of sessions delivered against an unpaid balance.

Custom payment management software connects billing directly to the session record. A completed session debits the package or triggers the invoice automatically. A failed payment starts a retry sequence and notifies the parent without any manual intervention. Package balances, subscription status, and payment history are visible in one place for both the admin team and the parent. The work that currently requires a person is handled by the system.

What we build

  1. Per-session and package billing

    Per-session billing records a charge against each completed lesson and generates an invoice automatically from the session record, so the admin team isn't manually creating invoices after each day of sessions. Session package management allows parents to purchase a block of credits upfront: ten sessions, twenty sessions, or any volume the centre sells. The package balance stores against the student record and is visible to the admin team and the parent at any time. When a session marks complete, the credit deducts from the balance automatically without any manual entry. Low balance alerts fire when a student reaches a configurable credit threshold so the centre can prompt the parent to renew before the package runs out mid-term. Package purchase history stores against the student record so the admin team has a complete credit and transaction history for every student.

  2. Subscription and recurring plans

    Monthly subscription plans configure with the billing amount, the billing date, and the payment method stored against the student account. On the configured date, the charge processes automatically and an invoice generates and sends to the parent without any action from the admin team. Plans can set at a fixed monthly rate or calculate from a per-session rate multiplied by the sessions scheduled in the billing period, depending on how the centre structures its pricing. Subscription status, active, paused, or cancelled, is visible on the student record so the scheduler and the billing team are working from the same information. When a parent requests a pause, the plan suspends from the next billing date and reactivates on the configured restart date without manual reconfiguration. Invoices for all recurring plans store against the student and the billing period for reference and dispute resolution.

  3. Failed payment handling

    When a payment fails, card declined, insufficient funds, expired card, the system starts an automated retry sequence on the schedule configured by the centre, typically attempting again after one day, three days, and seven days before escalating. A notification goes to the parent at the point of failure explaining what happened and providing a link to update their payment method or pay manually through the parent portal. The centre is also notified so the admin team can follow up if the automated sequence doesn't resolve the balance. Session hold rules are configurable: the centre can set whether sessions continue during the retry window or place on hold until the outstanding payment resolves. Every failed attempt, notification sent, and payment resolution records against the student's billing history so there's a complete audit trail if a payment dispute arises.

  4. Refund and cancellation management

    Refund processing for unused package credits manages from the student record: the admin team initiates the refund against the remaining credit balance and the payment returns to the original payment method via the Stripe integration without requiring manual processing outside the system. Late cancellation charges apply automatically based on the notice period rules configured by the centre: a cancellation within 24 hours of a session start time triggers the configured charge and adds it to the parent's account balance for collection on the next billing cycle. Refund and cancellation rules are configurable per plan type and per student so the centre can apply different policies to different enrolment tiers. Every refund, cancellation charge, and credit adjustment records with a timestamp and the staff member who initiated the action, giving the centre a clear record for any parent dispute.

  5. Revenue reporting

    Revenue reports by student, by tutor, by subject, and by time period so the centre has a clear view of where income is generated and where it's at risk. Monthly revenue summaries show billed amount, collected amount, outstanding balance, and write-offs for the period. Aged receivables show which student accounts have outstanding balances and how long those balances have been unpaid, so collection effort directs to the highest-value and oldest accounts first. Package renewal forecasting shows how many student packages are approaching zero credits in the next 30 days so the centre can proactively prompt renewals before students stop attending. Subscription churn reporting shows which plans have been cancelled or paused in the current period and the revenue impact of those changes.

  6. Stripe integration

    Card payments for per-session invoices and package purchases process through Stripe with the parent entering card details once and the card stored securely for future charges. ACH and direct debit are available for recurring subscription plans, offering lower transaction fees for centres with high monthly billing volume. The parent-facing payment portal allows parents to view their current balance, outstanding invoices, package credits, and payment history, and to pay outstanding balances or update their payment method without contacting the centre. Stripe's webhook infrastructure means payment events, successful charge, failed charge, refund processed, update the student's billing record in real time so the admin team always has an accurate account balance. All card data handles through Stripe and never stores in the centre's system, so PCI compliance scope is limited to the integration layer.

Frequently asked questions

Yes. The billing system supports all three pricing structures simultaneously because most tutoring centres offer more than one. A student on a ten-session package and a student on a monthly subscription manage within the same system, with the billing logic for each, credit deduction for the package student, automatic charge on the billing date for the subscription student, applied based on the plan type attached to the student record. The admin team doesn't need to manage different billing tools for different plan types. Revenue reporting aggregates all three structures into a single view so the centre sees total revenue, not separate figures from separate systems.

Failed payments trigger an automated retry sequence and a notification to the parent immediately at the point of failure, without any manual intervention from the admin team. The retry schedule, typically 1 day, 3 days, and 7 days, is configurable by the centre. The parent receives a notification with a link to update their payment method or pay manually via the parent portal. If the retry sequence completes without resolution, the admin team is notified so they can follow up directly. Session hold rules set by the centre: sessions can continue during the retry window or place on hold until the balance clears, depending on the centre's policy. Every step in the process, attempt, notification, resolution, logs against the student's billing record.

Yes. Late cancellation rules configure by the centre: the notice period required and the charge applied when that period is not met. When a session cancels within the configured notice window, the system applies the late cancellation charge to the student's account automatically and adds it to the next billing cycle or triggers an immediate invoice, depending on the centre's preference. The rules can set differently by plan type so a student on a monthly subscription might have a different policy from a student on a per-session arrangement. Every late cancellation charge records with the session it relates to and the timestamp of the cancellation so there's a clear record if a parent disputes the charge.

A focused payment management system, per-session billing, package credit tracking, recurring subscriptions, failed payment handling, and revenue reporting, typically runs $20,000 to $35,000. Cost depends on the number of plan types, the complexity of the cancellation and refund rules, whether the system is standalone or integrated with an existing scheduling platform, and the payment gateway configuration required. If payment management is being built as part of a broader tutoring centre platform that includes scheduling, session tracking, and parent communication, the combined platform typically runs $65,000 to $120,000. We scope every project before pricing: fixed cost, agreed before development starts.

What clients say

What our clients say

Three-year average engagement. Founders and operators describing the work in their own words. No marketing varnish.

Jennyfer Ngueno
Jennyfer Ngueno
Ivory Coast flagIvory Coast
CoFounder and CEO, Sekou

RaftLabs has been an exceptional partner. From the start, they became more than just a service provider, they embraced our vision with their expertise and dedication.

01 / 02

Related services

Talk to us about your tutoring payment management project.

Tell us how your centre handles billing today, the packages, the plans, the payment methods, and we'll tell you what we'd build.

  • Scope and cost agreed before work starts. No surprises. No obligation.
  • Working prototype within 3 weeks of kickoff.
  • Pay by milestone. You see progress before each invoice.
  • 60-day post-launch warranty. Bug fixes, UI tweaks, and deployment support. No retainer.
  • All conversations are NDA-protected.