Skip to main content
GullySystem
Education

Subscription Billing for Football 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.

Monthly fees, kit charges and tournament contributions are billed to each family on the set date. Sibling concessions apply first. The accounts lead follows up where an instalment is missed.

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.
Football academies

How the business operates.

A football academy is a small organisation with registers, fees, kit and fixtures all moving at once. Nothing stands still. Players sit in age-group squads, coaches cover several squads, and the ground is shared between training and fixtures. Parents pay in instalments and expect a message the moment a session moves to another pitch or is cancelled because of rain. Messages matter.

Trials and registration

Log each trial request, the date played and the coach’s verdict. Convert an accepted child into a registered player with a consent form, medical note, emergency contacts and a squad.

Squads and age bands

Group players by birth year and ability. Move a child up a band at season change. Coaches open only their own squads, while the head of youth reads every group and can see which age bands are short of goalkeepers or a second coach.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Trial requests and verdicts. Log each trial request with birth year and position, schedule the session, and keep the verdict and notes so an offer is made to the right child.
  • Player registration and files. Hold the consent form, medical note, guardian contacts, photograph and birth date for each player, with expiry dates for forms that need renewing each season.
  • Squads and age bands. Place players in squads by birth year and ability, allow a child to train up, and keep the squad history after the season changes.
  • Training registers. Mark attendance on a phone at the touchline, note injuries and absences, and list players who have missed several sessions in a row.

Operational bottlenecks to check

Squad lists live in several notebooks

Each coach keeps a list of names for the under-ten, under-twelve and under-fourteen groups. The office keeps another. They drift apart. When a player moves up an age band, one list is updated and the others stay as they were. Match sheets then carry the wrong names. Coaches notice on the touchline.

Attendance and fee status are never read together

A player may miss six sessions in a row and still be marked as paid up. Another may attend every drill while an instalment sits overdue. The head coach and the accounts clerk work from separate sheets, so neither sees the whole child. Families drift.

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

    A trial request is logged. It carries the child’s birth year, position and the date offered. After the session, a verdict and a note are recorded against the child.

  2. 2. Registration

    An accepted child becomes a player. The consent form, medical note, guardian contacts, photograph and chosen fee plan are attached, and a squad is assigned by birth year.

  3. 3. Training

    Sessions are planned against pitch slots. Registers follow. Coaches mark them on a phone, noting injuries or absences, so the head of youth sees who is missing from which group.

  4. 4. Match day

    The fixture is entered with opponent, venue and kick-off. The squad is named, the starting eleven and substitutes are recorded, and parents get the time and meeting point.

  5. 5. Assessment

    Every term, the head coach scores technical, tactical and physical marks and adds a written note. The family receives a short report for their child.

  6. 6. Fees and season close

    Instalments fall due by plan, receipts are posted and arrears are listed. At season end, kit is counted back in and players are moved up an age band.

Industry reports to connect with

  • Players by squad and birth year, with consent forms pending
  • Training attendance by squad and by player
  • Minutes played and appearances by player across the season
  • Assessment marks by player and term

Questions before implementation.

When should football 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