ARTICLE · Payment Platforms

Education and Training Institution Collection: Prepaid Fund Supervision, Lesson Consumption, and Refunds

Collecting tuition at a training institution does not end when the money arrives. The real chain runs from funds entering a supervised account, through gradual release as lessons are consumed, to refunds calculated on the unconsumed balance. This article explains how three constraints shape system design, why lesson batches must be modelled separately, and where the popular refund formula breaks down.

2026-11-09 16IDC

Education and Training Institution Collection: Prepaid Fund Supervision, Lesson Consumption, and Refunds

Collecting tuition at a training institution is not an action that ends when the money arrives; it is a chain that runs from funds entering the account to amounts being released as lessons are consumed. Collection design for outright online course purchase, recorded content and membership subscriptions is covered in the knowledge payment site collection guide, and automatic membership renewal in the membership auto-renewal collection guide. The boundary of this article is prepaid collection at institutions that teach mainly offline and charge by lesson consumption; it does not repeat the outright purchase or subscription models.

1. Three Constraints Acting on Training Collection

Why the Three Constraints Conflict

Any one of the three constraints ignored will force a rebuild within six months of launch.

The first is the regulatory constraint. Prepaid tuition falls under fund supervision in many jurisdictions. Money in a dedicated account is not freely available to the operator but is released gradually as lessons are consumed or training progresses. How much sits in the account and how much can be used become two different numbers.

The second is the channel constraint. Payment institutions verify entity qualification and business scope when onboarding a merchant. Education and training is a supervised category, and the contracting entity, settlement account and actual business scenario must agree. Signing with entity A, collecting with entity B and invoicing with entity C is a clear anomaly to channel risk controls.

The third is the tax constraint. Prepaid tuition is a liability on receipt and becomes revenue only as lessons are consumed. Invoicing, collection and recognition can all fall on different dates, and a system that records only a paid flag cannot produce a contract liability balance at month end.

The three constraints collide on the same field. The operator wants cash it can use on arrival, the regulator wants release according to progress, and tax wants recognition according to performance. The job of the collection system is not to remove the conflict but to record all three views so each party gets the number it needs.

Collection step Constraint source System requirement
Student payment Regulatory: prepaid fund supervision Separate amounts collected, supervised and released
Receiving account Regulatory: payee must match licensed operator Bind entity details to licence and settlement account
Payment channel Channel: merchant qualification and scope Merchant entity, industry category and business agree
Attendance deduction Regulatory: release by lesson or progress Model balance and attendance ledger separately
Refund Regulatory and tax: unconsumed lessons Refund details traceable to lesson batches
Invoicing Tax: invoice timing and recognition rhythm Invoices correspond to attendance records

2. The Logic of Prepaid Fund Supervision

Supervised Accounts and Actually Available Cash

The mechanism reduces to one sentence: tuition enters a dedicated account first and is released to the operator's usable account as consumption progresses. The purpose is direct, to stop the operator from spending months of future tuition at once and losing the ability to refund undelivered courses.

For the system, the critical point is that the same money has two identities. On the student side it is already paid; on the operator side it may still be unavailable. A single balance field leaves finance and operations permanently disagreeing, ending in two ledgers that do not accept each other.

The data model must therefore answer three questions for any student: how much has been consumed, how much is still supervised, and how much has been released but not consumed. The three must sum to the total paid, and every attendance or release operation must change at least one of them.

Four Things the System Must Record

First, supervision attribution: which supervised account and which campus or entity each payment belongs to. A multi-campus operator that records only the top entity cannot tell which account a refund should leave from.

Second, release rules: whether release follows lessons or progress, what triggers it, and who initiates it. These belong in configuration, not in the memory of individual staff.

Third, the release ledger: every release needs its own record with the linked attendance entry, the amount, the timestamp and the operator. The release ledger is the only self-proving evidence in an audit.

Fourth, state consistency: attendance, release and refund all change balances and must be concurrency safe. Two staff refunding and deducting for the same student simultaneously will corrupt the balance without locking and idempotency, and the error is hard to detect afterwards. Implementation detail is in the order number and idempotency design guide.

3. Payee and Account Structure

Payee Must Match the Licensed Operator

Regulation requires the collecting entity to match the licence holder. This looks like a qualification matter but directly affects channel availability. If a group parent company signs and collects while a licensed subsidiary delivers the training, funds ownership and responsibility separate as soon as a refund dispute appears.

The system should model the entity as a first-class object: name, unified social credit code, licence details, the receiving account and the invoice header. Students choose a campus or a course, and the system derives the payee rather than letting staff decide at the counter which account to use.

Three Layers of Account Structure

The common structure has three layers: the entity layer matching licence and business licence, the campus layer matching venue, teachers and course inventory, and the class cohort layer matching specific lessons and instructors.

How funds map onto these layers determines reconciliation difficulty. Collecting by entity, accounting by campus and deducting by cohort is the cleanest arrangement. Collecting by cohort and aggregating by entity is convenient for collection but mixes cost and revenue between campuses, leaving campus managers unable to tell whether their site is profitable.

The structure also shapes refund paths. Refunds must return by the original route, so the system must remember which channel, which merchant number and which settlement account each payment used. Recording only the channel name is insufficient, since one entity may hold several merchant numbers, and using the wrong one causes failed refunds or misposted reconciliation. Channel-side detail is in the refund and settlement operations handbook.

4. Lesson Consumption and Revenue Recognition

Lesson Balance as a First-Class Citizen

The most important data in a training collection system is not the order but the lesson balance. The order records what was bought; the balance records what remains, and every refund, transfer, extension and renewal uses it as the baseline.

A single integer field is not enough. One payment may contain standard lessons, bonus lessons and event lessons with different unit prices and refund rules. One attendance event may deduct standard or bonus lessons, and the order of deduction changes the remaining value. Each batch of lessons should be an independent record carrying source order, lesson type, unit price, consumed quantity, remaining quantity and validity. Attendance and refunds act on batches and aggregate to the student.

The model looks heavier but it solves a problem nearly every institution meets: a student attends three lessons and asks for a refund, the institution cannot explain the amount, the parent rejects the institution's arithmetic, and the outcome is a compromise. With batches, the refund follows directly from the remaining records.

Attendance Records and Recognition Rhythm

Attendance records are the basis for revenue recognition. Each should carry student, cohort, lesson batch, lessons deducted, teaching date, recorder and a check-in proof. The proof may be a QR scan, face verification, teacher confirmation or parent confirmation; the form matters less than the ability to show that the service occurred.

Recognition normally follows attendance: lesson value consumed in the period becomes revenue, and the rest stays in contract liability. Finance needs a monthly consumed-value summary, and that summary must come from batches rather than order value. Dividing order value by total lessons and multiplying by consumed lessons produces systematic error whenever bonus lessons or discounts exist.

If the institution also sells online courses, that side recognises revenue on a fixed cycle like a content subscription, while the offline side remains lesson-based. Either way, the monthly performance summary needs a stable billing definition, and the system implementation is discussed in the invoicing and billing system guide.

5. Refund Calculation on Unconsumed Lessons

The Common Wrong Formula

The most common wrong formula is order value minus lessons attended multiplied by unit price. It holds only when there is one payment, no bonus lessons, no discount and no class transfer. It fails as soon as any of these appear: bonus lessons make the unit price ambiguous; a discount must be allocated across all lessons; a mid-term transfer creates two different unit prices; a supplementary payment creates multiple orders.

The consequence is not only a wrong number. When the amount the institution computes is lower than the parent's own arithmetic, the parent concludes the institution is withholding money, and complaints and public criticism usually start there. Prepaid training is a high-complaint area, and opaque refund arithmetic is a leading trigger.

The correct approach splits into three steps: determine the remaining batches and quantities, determine the unit price of each batch, and sum the unconsumed portion. If the contract provides for a handling fee or for consumed materials, that must be disclosed and recorded at the point of payment confirmation, not raised for the first time at refund.

Bonus Lessons, Discounts and Packages

The principle for bonus lessons is that they carry no standalone price, are consumed only after standard lessons run out, and are normally not refunded in cash. This must be written into the contract and distinguished by lesson type in the system, or staff will be asked where the bonus lessons went.

The principle for discounts is to allocate the discount across all lessons to produce an effective unit price. If the system stores only list price and discounted total, dividing the total by lesson count seems reasonable but leaves open what price applies to the lessons already delivered. The effective price should be generated at payment time and used in every later calculation.

The principle for packages is that each component needs its own performance progress. In a package containing lessons, materials and assessments, a student who attended lessons but never collected materials should have material cost deducted rather than a proportional lesson deduction. The clearer the split, the fewer the disputes.

6. Instalments and Subsidised Enrolment

Instalments and the Supervised Balance

Training instalments take two forms. The institution may run instalments itself, collecting monthly and carrying the credit risk; or a financial institution or lending channel may sign with the student while the institution receives the full amount up front. The accounting and regulatory treatment differs completely.

With self-run instalments, unpaid amounts are not tuition collected, do not enter the supervised balance and cannot be recognised as revenue. The system must separate receivable from collected-but-unconsumed: the first is a receivable, the second a contract liability. Many institutions merge them in reporting, showing healthy cash flow while usable funds sit far below the reported figure.

With financial institution instalments the institution receives the full amount and the supervision obligation matches an ordinary payment. One detail is easily missed: if the student withdraws mid-term, the refund must settle both the student's instalment contract and the institution's received funds, and mismatched timing creates a funding gap. The fund flow and multi-party settlement structure are described in the aggregate payment and split settlement guide.

Third-Party Advance and Subsidy Models

Subsidy and assistance programmes usually have a third party advancing part of the tuition, with the student covering the remainder. The system must record three components: student contribution, third-party advance and institutional discount. They behave differently on refund: the student portion returns to the student, the advance returns to the advancing party, and the discount is simply reversed.

With only a single received-amount field, a refund cannot tell who should be paid. This appears in government subsidies, corporate sponsorship and charitable programmes, usually with larger amounts and more parties, and remediation afterwards is expensive.

7. Class Transfer, Extension and Lesson Transfer

Class Transfer and Lesson Migration

Class transfer is the most frequent change operation and the heaviest load on the lesson model. Moving from class A to class B with different unit prices requires revaluing the remaining lessons; different lesson types, such as one-to-one to small group, make the conversion rule more complex.

The system should support lesson migration as an independent operation rather than zeroing class A and adding a balance to class B. Migration must retain the original batch, the new batch and the conversion ratio, or a later refund cannot be traced back to the payment that created those lessons.

Transfers also involve price differences. Moving to a more expensive class requires a supplementary payment; moving to a cheaper one requires a refund of the difference. Both enter the supervised balance and both obey refund rules. Treating a transfer as a new payment plus a partial refund is workable in accounting but pollutes the payment history with entries the student cannot interpret.

Extension and Lesson Transfer Boundaries

An extension pauses attendance and pushes the validity date out. Approval and recording are easy; the difficulty is the supervision state during the pause. Funds remain in the supervised account, unusable but not released. The system must be able to suspend release for the extension period, or an operator will keep releasing on the original schedule while the student is absent for months.

Lesson transfer means giving remaining lessons to another person. This is not encouraged under most regulatory readings, because the recipient never formed the original contract and responsibility for refunds and complaints becomes ambiguous. The system may offer the capability but must require the new student to sign a fresh contract, capture identity again, and state in the contract that the original refund rights do not travel with the transfer.

Every change operation should leave a record: type, batches before and after, conversion ratio, approver and student confirmation. That record is the strongest evidence in a refund dispute and a focus of internal audit.

8. Launch Checklist and Five Common Pitfalls

Five Common Pitfalls and Responses

Pitfall Symptom Response
Recording orders but not lesson batches Remaining value cannot be computed at refund Create batches at payment with price and type
Attendance kept in offline spreadsheets Balance and ledger diverge permanently Move attendance online with check-in proof
Bonus and standard lessons mixed Refund amounts repeatedly disputed Separate lesson types, bonus lessons unpriced
Transfer zeroes and rebuilds balances Traceability breaks, price gaps unclear Model migration separately with conversion ratio
Wrong merchant number on refund Failed refund or misposted reconciliation Record channel, merchant number and settlement account

Launch Checklist

The launch checklist should cover: generating lesson batches with effective unit price at payment; aggregating balance by student and by batch; attendance records carrying check-in proof and remaining immutable; displaying supervised and available balances separately; tracing release entries back to attendance records; computing refunds from remaining batches with bonus and discount rules applied; running transfer and extension through dedicated change flows; separating receivable, collected and unconsumed for instalments; recording channel, merchant number and settlement account on refunds; and validating entity details against the licence.

Qualification and filing requirements are covered in the payment compliance and filing guide. The most common domestic channels for training institutions are WeChat Pay and Alipay, with card-present and corporate transfer handled through the UnionPay system. When several campuses and channels must be managed together, teams usually evaluate an aggregate approach such as Ping++ that folds payment, attendance, refund and reconciliation into one interface.

A closing reminder: the value of a training collection system is not that it can take tuition but that it can state, at any moment, how many lessons each student has left and what they are worth. While that chain holds, refunds, transfers, renewals and audits are queries; once it breaks, every business action degrades into manual argument.

More payment scenarios are collected under the Payment category.

Source: 16IDC original. Capabilities and compliance requirements are subject to official channel documentation, industry regulations, and tax and accounting rules.

Original source: 16IDC ↗