Skip to main content
GullySystem
Education

Subscription Billing for Swimming academies

Manage recurring invoice cycles and changes to customer plans.

Subscriptions

Does this function belong in your operation?

Use when customers pay recurring charges for continuing access, membership or service.

A recurring agreement starts, renews or changes.

Term passes, monthly plans and sibling discounts are billed on the swimmer’s start date. Paused terms for illness stop the charge. Reception sees who has not paid before the next class.

Bring the records the workflow depends on.

  • Subscription plans
  • Customer billing dates
  • Proration and cancellation rules

Outputs to check

  • Customer plan and cycle register
  • Recurring invoice and adjustment record
  • Overdue, paused and cancelled account list

Follow the subscription billing workflow.

Use this sequence to compare your current process with the proposed module. Agree the owner, permission and exception at each step.

  1. 1. Create the agreement

    Record the plan, start date and billing conditions.

  2. 2. Set the cycle

    Apply the approved invoice dates and proration basis.

  3. 3. Raise recurring billing

    Create the period's charges without duplicating an earlier run.

  4. 4. Track collection separately

    Link receipts or failed payment outcomes to the invoice.

  5. 5. Manage plan changes

    Record pauses, upgrades and cancellation with their billing and service-access handoffs.

Who uses the module, and who approves?

Keep responsibilities distinct even when one person holds more than one role.

Accounts assistant

Reviews recurring invoices, payment outcomes and approved plan changes before closing the billing period.

Service or delivery staff

See whose subscription is active today, which is what decides the route or the visit.

Owner

Reviews active, paused and lapsed accounts and the reasons recorded for each change.

Decide how exceptions are handled.

These business rules belong in configuration and testing. A normal transaction alone does not demonstrate that the workflow is ready.

Plan changes mid-cycle

Apply the documented proration and retain the old plan period.

Payment overdue

Follow the agreed collection and service-access policy without silently deleting the subscription.

Pause requested after billing

Review the invoice adjustment and future schedule as separate actions.

Can this work independently?

Recurring invoicing can run independently from automatic payment collection. It needs customer plans, dates and approved proration rules. Mandates or payment providers collect funds, while service-access or delivery systems decide entitlement from the agreed account state rather than assuming every raised invoice was paid.

Systems and records it connects with

  • Mandates and auto-debit: Provider-confirmed mandates and recurring collection outcomes.
  • Invoice management: Issued invoice references, line amounts and outstanding balances.
  • Payment gateways: Authorised payment attempts, outcomes and settlement references.
  • WhatsApp and SMS: Permitted message content and channel delivery responses.

Configure, test and introduce the workflow.

  • We list your plans, cycles and how customers pay. You supply the customer file. A plan sheet comes back.
  • Pauses, upgrades and grace periods are written down. You approve each rule. A sample cycle is run in a test copy. Accounts check invoices against what they would raise.
  • Debit mandates and payment links are connected. A trial payment confirms the flow. Invoices are raised by the system. Accounts watch the failed list closely.

Check the result before rollout.

Apply these checks to a sample from the agreed workflow, then repeat with an exception. Keep the expected result beside the test record.

  • Each billing period is charged as configured.
  • Plan changes apply from the agreed date.
  • Cancelled subscriptions stop future charges under the defined rule.
Swimming academies

How the business operates.

A swimming academy sells lessons, but what it really runs is a timetable of lanes. Each class has a level, an instructor, a lane and a start time, and every one of those must agree with the pool hours before a single swimmer is booked. Parents ask. They want to know where their child stands. Instructors want to know who is ready to move up. Both need a record.

Enquiries and assessment swims

Log each enquiry, book an assessment swim, record the level the instructor assigns and offer a class and lane that suit the child’s age and the family’s school-run hours. The family’s answer is kept with the enquiry. Some say yes. Some wait.

Classes, levels and lane plans

Define levels from water confidence to squad. Set class sizes by lane. Keep each lane plan by hour. Instructors and lanes are never double booked, and the head instructor can see at a glance which lanes sit empty at ten in the morning and which are full after school.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Enquiries and assessment swims. Log every enquiry with the swimmer’s age and goal, book the assessment swim, and keep the instructor’s level and notes so the placement is not repeated.
  • Swimmer files and consents. Hold date of birth, medical notes, guardian contacts, photo permission and signed consent forms for each swimmer, with renewal dates for forms that expire.
  • Levels, classes and lane plans. Define levels from water confidence to squad, set class size for each lane and hour, and prevent a lane or an instructor from being double booked.
  • Registers and attendance. Mark attendance at the poolside on a phone, with late arrivals and cancellations noted, and see attendance by class, level and swimmer.

Operational bottlenecks to check

Lane plans are drawn on a whiteboard

A lane holds one class, a lap lane for adults, or a squad set. The whiteboard shows the plan until someone rubs it out. Two instructors then arrive for the same lane. A class of six-year-olds waits on the deck, shivering in towels, while the desk looks for another free lane at that hour.

Levels are decided from memory

A child may pass the back float but not the breathing drill. Instructors remember who is close to the next level, yet no sheet lists the skills passed. A parent asks why a friend moved up first. The answer is a guess, and the guess is rarely written anywhere the head instructor could check it later in the term.

How work flows across this business

This module sits within a wider operating process. Use the sequence to identify the other teams and records affected by a change.

  1. 1. Enquiry and assessment

    A parent asks for lessons. It arrives by phone, form or message. The enquiry is noted with the swimmer’s age, an assessment swim is booked, and then the instructor enters the starting level.

  2. 2. Class and lane

    The swimmer is placed in a class at that level, on a lane and at an hour with a free place. Consent, medical details and the pass are recorded before the first lesson.

  3. 3. Lessons

    Instructors mark the register at the poolside and tick the skills practised. An absent swimmer joins the make-up list for the same level.

  4. 4. Progress

    When the skills checklist is complete, the instructor passes the swimmer to the next level. A badge is issued. A report card goes to the family.

  5. 5. Pass renewal

    Lessons used are counted against the term pass. The desk lists passes ending soon. It messages the family and posts the receipt on renewal.

  6. 6. Pool checks

    Water readings are logged at set times. Checks are quick. Anything out of range is flagged to the manager, and the entry is kept against the pool and the date.

Industry reports to connect with

  • Swimmers by level, class and lane
  • Lane use by hour, with empty places
  • Attendance by class and swimmer, with make-ups owed
  • Skills passed and badges issued by level

Questions before implementation.

When should swimming academies consider subscription billing?

Use when customers pay recurring charges for continuing access, membership or service. A recurring agreement starts, renews or changes.

What should we bring to the requirements discussion?

Bring anonymised examples of Subscription plans; Customer billing dates; Proration and cancellation rules. Show who creates, checks and changes each record. Use only records from an activity that meets the suitability conditions above.

Does this replace our existing business software?

The starting point is your current system and the gap you need to close. Manage recurring invoice cycles and changes to customer plans. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

Automatic collection is separate from recurring invoicing; contract and tax treatment require approved rules.

How are scope, price and rollout decided?

The proposal follows a review of your records, user roles, branches and existing software. Data migration, connections, training and support are scoped separately where needed. Each billing period is charged as configured. Use this check when reviewing the first working version.

Talk to us

Discuss subscription billing for your business.

Tell us which workflow needs attention and which systems your team uses. The next step is a requirements discussion and a written scope.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements