Skip to main content
GullySystem
Education

Subscription Billing for Martial arts schools

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.

Monthly fees follow the class pass, with a family rate when siblings train together. Breaks pause the fee. Belt history and grading eligibility stay exactly as they were.

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.
Martial arts schools

How the business operates.

A martial arts school teaches karate, taekwondo, judo, kung fu or a mix. Whatever the style, a student moves through coloured belts or numbered grades, and each step needs a syllabus passed in front of an examiner.

Student ranks and belt history

Keep each student’s current belt, every earlier grade with its date and examiner, and the next grade they are working toward, so a transfer carries the whole story.

Class timetable and rosters

Set classes by age, rank and instructor, with a roll for each session and a quick sign-in for children’s classes.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Student ranks and belt history. Keep the current belt, every earlier grade with its date and examiner, and the next grade the student is working toward.
  • Class timetable and rosters. Set classes by age, rank, mat and instructor, take a roll for every session, and let a guardian sign a child in.
  • Syllabus sign-off. List the forms, techniques and sparring drills required for each belt, and mark each one when the instructor has seen it performed.
  • Grading eligibility and results. Check classes attended, forms signed off and fees paid before a student is listed, then record the pass, score and new belt.

Operational bottlenecks to check

Grading eligibility is decided from memory

The instructor recalls from memory who attends and who does not, so someone with too few classes gets put forward while a student who is truly ready is missed.

Belt history is kept in several places

The belt certificate, the register and the instructor’s notebook each hold a different date. Moving to another branch means repeating the story.

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. Trial and joining

    An enquiry becomes a trial class on a set mat. Joining brings a record, a waiver to sign and a fee plan.

  2. 2. Class and roll

    The student is placed in a class by age and rank. The instructor takes the roll, and children are signed in by a guardian.

  3. 3. Syllabus progress

    Forms and techniques are signed off against the next belt as the instructor sees them performed.

  4. 4. Grading

    The grading list is drawn from classes attended, forms signed off and the grading fee paid. The examiner records the result and the new belt.

  5. 5. Fees and sales

    Monthly fees, family plans, grading fees and uniform purchases are billed, and receipts are issued.

  6. 6. Events and instructor pay

    Students are entered in tournaments by licence and class. Instructors are paid from the classes taught.

Industry reports to connect with

  • Students ready for grading by belt
  • Attendance by class, instructor and month
  • Waivers missing or due for renewal
  • Fees due by family and month

Questions before implementation.

When should martial arts schools 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