SCHOOL OPERATIONS · FEE CONTROLS
School Fee Collection Daily Closing: A Practical Control Checklist
A repeatable end-of-day check for school collections, receipts, payment references, exceptions and secure hand-off.
Conceptual product view · no customer records or performance figures
THE SHORT ANSWER
A daily collection close should compare recorded receipts with the school’s source evidence, confirm the correct student and fee context, identify unmatched or duplicate items and assign exceptions. Keep collection modes and settlement evidence distinct, restrict cash and financial records and document who reviewed the close. A daily check supports reconciliation; it does not prove external bank settlement.
01 / CUT-OFF & OWNERSHIP
Set a consistent end-of-day boundary and name the reviewer.
A daily close works only when staff agree which transactions belong to the day and who reviews them. Define the cut-off, the systems or records used as evidence and how late entries are handled. Without a shared boundary, two reports can legitimately show different totals while each appears final.
Separate the person collecting or entering a payment from the person who reviews the close where school controls require it. Record hand-off time and ownership, particularly when shifts change or a payment is awaiting confirmation.
02 / RECEIPTS & OBLIGATIONS
Trace each receipt to the student and fee obligation it represents.
Confirm the learner identity, relevant fee structure or instalment and amount before treating a receipt as complete. Check that the receipt reference is unique under school practice and that the period is clear. A receipt should represent what the school actually recorded, not an assumption about a transaction that has not been verified.
Review corrections, concessions and partial collections in context. Preserve the original agreement and the authorised adjustment. If the product’s receipt numbering or correction behavior is unclear, verify it before making the process depend on an assumption.
03 / COLLECTION SOURCES
Keep payment modes and external evidence distinguishable.
Cash, cheque, transfer and online payment references can arrive with different timing and evidence. Follow the school’s approved process for recording each, and do not mark an external settlement as confirmed without its authoritative source. Staff should know which evidence supports each status.
Protect cash and payment records during hand-off. Limit who can view or export transaction details and avoid sharing full references in an open group. The school’s operational collection record may support review, but it is not necessarily a bank statement or complete accounting ledger.
04 / RECONCILIATION
Compare totals, then investigate exceptions instead of posting an unexplained offset.
Compare the day’s recorded collections with the school’s source records using the same time period and categories. Identify duplicate receipts, unmatched references, delayed confirmations and differences in amount. Classify each item so staff know whether it needs research, correction or a later settlement check.
Assign an owner and next review time to every exception. Do not force the totals to match by adding a generic adjustment. Preserve enough context for the next reviewer to understand what was checked and what remains unresolved.
05 / DUES & FAMILY FOLLOW-UP
Keep outstanding balances out of the close until recent collections are checked.
A collection close may identify balances for follow-up, but first verify recent receipts, fee schedules and authorised concessions. Separate current dues from future instalments and queries under review. Avoid sending an automated or manual reminder from a stale balance list.
Use respectful, individual communication for account-specific questions and provide a school contact route. Do not expose personal balances in group notices or assume a one-way notification accepts replies.
06 / CLOSE & RETAIN
Document review completion and protect the daily record.
Record who reviewed the close, which sources were compared, whether any variance remains and how it will be carried forward. Keep a consistent daily summary so monthly reviewers can follow exceptions without reconstructing them from separate messages.
Store and retain financial records according to school policy and professional advice. Limit exports to the necessary purpose and dispose of temporary copies through approved procedures. Do not claim an external settlement or statutory reconciliation from an internal close alone.
A FIELD GUIDE FOR YOUR TEAM
The school collection close
Adapt cut-off and evidence to the school’s approved process. Keep each unresolved item visible rather than forcing totals to match.
| Lens | Question to ask | What to record |
|---|---|---|
| CUT-OFF & OWNERSHIP | Set a consistent end-of-day boundary and name the reviewer. | A stated cut-off and reviewer/hand-off owner. |
| RECEIPTS & OBLIGATIONS | Trace each receipt to the student and fee obligation it represents. | A receipt-to-student-to-obligation match. |
| COLLECTION SOURCES | Keep payment modes and external evidence distinguishable. | A source-evidence note for each collection mode. |
| RECONCILIATION | Compare totals, then investigate exceptions instead of posting an unexplained offset. | An exception register with reason, owner and next action. |
| DUES & FAMILY FOLLOW-UP | Keep outstanding balances out of the close until recent collections are checked. | A verified balance and a private, assigned follow-up where needed. |
| CLOSE & RETAIN | Document review completion and protect the daily record. | A dated close note with protected records and visible variances. |
CODEPEX IN CONTEXT
Useful guidance begins with clear scope.
School ERP declares fee structures, collection and receipt records, outstanding dues and reconciliation/reporting context. Confirm exact modes and receipt behavior. Do not imply bank reconciliation, payment-gateway settlement or accounting compliance automation unless verified.
Product-specific statements are based on the current owner-controlled capability declaration. Ask CodePex to confirm any institution-specific configuration or unlisted requirement.