esedark
Menu
Back to notes

places / enrolment / payments

Academy management software: enrolment, groups and payments

Follow each enrolment from a reserved place to its monthly fee and payment. Compare proposals through group transfers, partial payments and withdrawals.

Choosing academy management software means checking that an enrolment takes the right place, creates the agreed monthly fee and explains who has paid. A student record, timetable and payment list may each work well while still forcing administration to reconstruct the whole journey every month.

I would start with that journey before specifying a complete platform. This guide helps the director of a teaching academy compare an existing product, an integration or a custom component. The purchasing decision concerns students, groups and payments. It does not assess teaching materials or replace the academy's academic decisions.

Define how students, places and monthly fees relate

Separate the person, enrolment, group and payer. One student may have several enrolments; one person may pay for several students. Agreed identifiers and relationships avoid relying on a name or email address to explain a payment. Also decide who needs academic information and who needs billing details.

Write down what reserved, confirmed, waitlisted and released mean for a place. When does a reservation expire? Who can authorize exceeding capacity? What happens when a student switches groups halfway through a month? Keep the effective date alongside the applicable fee rule. Attendance, active enrolment and a paid monthly fee are different states; one should not imply another without an approved rule.

Identify which system owns each record: academy administration, payment collection and accounting. The treasury software guide covers bank settlements and reconciliation differences. This workflow starts earlier, with the enrolment that creates the fee.

Buy, integrate or build: choosing the right engagement

Existing product: if a tool covers your capacity rules, timetable, fees and exceptions, the engagement may only need configuration, migration and training. Ask for a demonstration using fictional data and your rules in the edition you would purchase. A feature list does not establish that a group transfer preserves the history you need.

Integration: when student administration and payments work separately, define what data must move, in which direction and who resolves differences. Confirm available access before pricing a connector. A file import may be enough; continuous synchronization only makes sense when the workflow needs it.

Custom component: I would consider this when verified alternatives cannot handle a necessary rule and manual handling has a documented cost or risk. Isolate that component before replacing the whole system. If configuration or an owned manual process solves the problem, new software is unnecessary. If different staff explain the rules differently, first commission a bounded definition exercise and sample validation.

An acceptance matrix for academy management software

Give each supplier the same cases. Mark each as included, configuration, additional development or excluded, then add an owner, cost and evidence still needed. These are proposed checks for evaluating offers, not results from products I have tested.

Acceptance cases from a reserved place to an explained payment
CaseRequirement to commissionAcceptance evidence
Last available placeReservation expiry and confirmation under agreed capacity rules.Two requests for the last place do not both become confirmed enrolments. One remains waitlisted; an expired reservation releases capacity.
Group transferEffective date, available capacity and fee treatment.The transfer preserves the previous group and does not occupy both places after the change. The fee adjustment follows the approved rule.
Monthly fee and discountBilling period, tariff and authorized discounts with effective dates.Generating the same period twice does not duplicate the fee. A future tariff change does not rewrite issued charges.
Shared payerExplicit allocation of a payment across enrolments and periods.A partial payment against several fees shows the amount applied and outstanding for each, without applying the full payment to every student.
Withdrawal or refundEffective date, outstanding fees and authorized adjustments.Withdrawal stops future fees according to the agreed rule; a refund retains its reference and history. Neither silently removes an outstanding balance.
Permissions and exitAccess by role and export of relationships and exceptions.A teacher sees only authorized information. Another operator can reconstruct an enrolment and its payments from the delivered export.

Also agree the number of simultaneous requests to test, acceptable synchronization delay and an exception owner. If the collection tool is disconnected, the status should remain awaiting confirmation. Sending a request must not be presented as confirmed payment.

Example: a group transfer and a partial family payment

Hypothetical example: one person pays monthly fees for two students. One student moves to a group with a different tariff during the period, and the payment received does not cover the total. Proposal A stores only a family balance. Proposal B retains the enrolment, period, applied tariff and payment allocation. They address different needs.

I would ask suppliers to reproduce the transfer using a proration rule defined by the academy, without assuming proration always applies. Administration must be able to explain which place becomes available, when the tariff changes and how much remains outstanding for each enrolment. A payment without a sufficient reference stays under review; a shared surname is not enough to allocate it.

Then repeat the payment import and correct an allocation with authorization. The evidence should show that the amount is neither collected nor applied twice, and that a correction retains its author, reason and previous values. This scenario helps accept the engagement; it is not a client case or a savings promise.

Scope, deliverables and migration

A first release might cover one location, one teaching period, agreed groups, one enrolment source and one collection tool. Include enrolments, transfers, withdrawals and an exception queue. Explicitly exclude anything outside the engagement: a learning platform, course content, academic assessment, payroll, complete accounting and additional connections. Executing payment collections needs its own scope and authorization.

Request a process map, state and relationship dictionary, fee rules, contracted configuration or code, synthetic-data test evidence, a sample export, recovery instructions and training. Define academy-controlled accounts, rights to delivered materials, source-code access where applicable and handover terms. The software quote comparison guide helps turn these into verifiable milestones.

For migration, agree a cutoff and inventory students, payers, active enrolments, reservations, issued fees, balances and pending refunds. Rehearse a sample and compare occupancy by group and outstanding amounts by enrolment, as well as totals. Do not infer an active enrolment from an old payment alone. During transition, identify which system may issue fees and retain changes needed to return to the previous system without losing work.

Implementation, maintenance and exit costs

Separate licenses, discovery, data cleanup, configuration, integration, migration, testing and training. Effort depends on locations, groups, fee rules, exceptions, historical data quality and available access. Importing names is a different deliverable from reconstructing enrolments and outstanding balances.

Compare the same period and usage assumptions. Verify whether licenses are priced per student, enrolment, location or user and how archived records are treated. Add third-party usage, hosting where relevant, support and internal review effort. The software total-cost model organizes these items without treating unknown costs as zero.

Assign responsibility for setting up the next teaching period, reviewing tariffs, handling failed imports and testing collection-provider changes. Distinguish fixing an accepted requirement from adding another location or rule. Agree support coverage, incident priorities and a manual fallback. Include exporting relationships and history, transferring accounts and revoking access when changing suppliers.

What to send me to scope the project

Describe your current tools, locations, groups, approximate student count and fee rules. Include a fictional enrolment, group transfer and payment exception, the person who approves adjustments and the next teaching-period date that constrains the project. I do not need student records, personal information or credentials for the initial discussion.

I can review a business software development or integration engagement with you, retain what works and define the first delivery. You can share your academy workflow so we can agree scope, exclusions and acceptance criteria.

Review my academy workflow