SCHOOL OPERATIONS · FEE GOVERNANCE
How to Manage School Fee Concessions and Scholarships with Better Record Control
A practical framework for authorising fee concessions, recording their scope and period, and keeping adjustments distinct from unpaid dues.
Conceptual product view · no customer records or performance figures
THE SHORT ANSWER
Manage a concession as an authorised change to a fee obligation, not as a payment or an unexplained reduction in a balance. Define who may approve it, which student and period it covers, what reason may be recorded and how it affects the amount due. Keep supporting context access-controlled and review expiry or changes under the school’s policy.
01 / OBLIGATION & REDUCTION
A concession changes the amount due; it does not record money received.
A fee obligation describes what the school charges under its policy. A concession or scholarship can reduce that obligation for a particular student or period, but it is not the same as a payment, refund, deferral or unpaid balance. Keeping these concepts separate helps accounts staff explain a statement and prevents a management report from hiding the difference between support granted and collection received.
Agree the terms the school uses and how each is represented in its records. If a scholarship pays part of a fee through a separate arrangement, do not assume that the student-side reduction and external funding are the same transaction. The school’s finance policy should determine how the amounts are recorded and reported.
02 / AUTHORITY
Make the approval responsibility explicit before a change is entered.
Decide which role can recommend, approve and record a concession. The appropriate authority may depend on the amount, policy or circumstances; the important point is that the rule is documented and staff know when to refer a request. A verbal instruction passed through several people is difficult to verify later and can put frontline staff in the position of making a decision they are not authorised to make.
Keep the approval evidence in the school’s appropriate record system and restrict sensitive details to the people who need them. During software evaluation, ask which access controls and history are available; do not infer a multi-step approval chain from a generic permissions feature. The institution must confirm whether the product’s actual process matches its governance.
03 / SCOPE & PERIOD
Record who the decision applies to and when it should be reviewed.
A decision should identify the relevant student record and the fee period, category or instalment it affects. If the concession applies for one term rather than the whole academic year, the record needs to preserve that boundary. Otherwise a temporary arrangement may be treated as permanent or copied into the next cycle without review.
Keep the reason at the level appropriate for the school’s policy and privacy practice. Avoid capturing unnecessary personal detail in a broadly accessible field. Define when the arrangement expires, what evidence is retained and who checks for renewal. These are governance choices for the school, not assumptions about a software default.
04 / KEEP DUES DISTINCT
Do not let a concession disappear inside an outstanding balance.
An outstanding amount can mean that payment is pending, that a receipt is not yet matched or that a concession has not been applied correctly. Those cases require different action. Before contacting a family or escalating a due, check the approved concession record, the applicable fee period, collections already received and any open correction.
Reports should make it possible for authorised staff to distinguish what was originally charged, what adjustment was authorised and what remains payable under school policy. If the available report does not expose those distinctions, record that limitation and agree a complementary review process. Never alter an unpaid amount merely to make a due list appear smaller.
05 / PERIODIC REVIEW
Revisit arrangements when terms, sessions or circumstances change.
A periodic review can identify arrangements that have expired, need renewal or no longer match the current fee period. It can also catch duplicate entries and concessions carried forward accidentally. Set the review cadence and responsibility in advance; sensitive cases should be handled discreetly and consistently with school policy.
When an adjustment changes, preserve the earlier decision context and record the new scope. Do not overwrite the old amount without a clear reason and authority. Review receipts and outstanding amounts after the change so that families receive accurate information. A well-governed process supports fairness by making like cases visible without removing the judgement required for individual circumstances.
06 / COMMON CONTROL ERRORS
Look for undocumented edits, expired terms and inconsistent treatment.
Common errors include reducing a balance without recording a decision, applying one student’s arrangement to a sibling or another fee category, forgetting the applicable period, and treating an unpaid item as an approved concession. Another risk is collecting more personal information than the people reviewing fees actually need. Each weakens the school’s ability to explain what happened and who was responsible.
Use a simple control matrix: who requests, who decides, who records, who reviews and what evidence is retained. Apply it consistently and review exceptions rather than relying on informal memory. If a correction is needed, retain an explanation in the appropriate system and verify the resulting statement before communicating with the family.
07 / CHECKLIST & SOFTWARE
Test one approved adjustment from decision through reporting.
Bring a fictional case to a software discussion. Follow the original fee amount, approved adjustment, remaining amount, collection and receipt. Ask which roles can view or change each record, how a period is selected, what history remains and whether a report distinguishes concession from collection. Verify that a correction does not erase the underlying record or bypass school authority.
CodePex School ERP declares fee concession and scholarship-related handling within its fee scope. Confirm the precise fields, authorisation workflow, access and reporting behavior directly; this guide does not promise a specific approval chain or automated expiry. Keep the school’s own policy as the source for eligibility and decision rights.
A FIELD GUIDE FOR YOUR TEAM
A controlled concession decision
Keep the approval and its financial effect traceable. This checklist helps accounts and school leadership review a concession without confusing it with collection or arrears.
| Lens | Question to ask | What to record |
|---|---|---|
| Request | Which learner and fee period is involved? | Verified student and applicable fee context. |
| Decide | Who has authority under school policy? | Approval evidence and decision owner. |
| Record | What amount or category changes, and for how long? | Scope, start/end or review point, minimal reason. |
| Reconcile | What remains payable after collections and the approved adjustment? | Distinct concession, receipt and balance records. |
| Review | When will the arrangement expire or be reconsidered? | Responsible reviewer and retained history. |
CODEPEX IN CONTEXT
Useful guidance begins with clear scope.
The School ERP capability registry includes fee concessions and scholarships in the fee-administration scope. This article does not assert a particular approval chain, expiry automation or report field. Confirm the available record details and access controls with CodePex, and apply the school’s own policy for eligibility and authorisation.
Product-specific statements are based on the current owner-controlled capability declaration. Ask CodePex to confirm any institution-specific configuration or unlisted requirement.