Admissions
How a bursar can reconcile admissions and enrollment
How a bursar can reconcile admissions and enrollment through offers, deposits, payments, refunds, identity, permissions, integrations, and family communication.
Separate commercial statuses
An approved decision, an offer, an accepted offer, an expected payment, a received payment, a reconciled payment, and an enrolled student are different events. Define each status, owner, evidence, and downstream handoff.
This prevents a payment problem from being mistaken for an admissions decision problem or an accepted offer from being treated as a complete enrollment.
Reconcile identity and exceptions
Match applicants, guardians, siblings, offers, payment references, receipts, refunds, withdrawals, and student records using approved rules. Test duplicate payment, unmatched payment, changed offer, changed guardian, late payment, and withdrawal.
Record source, target, reason, owner, evidence, correction, and family message. Do not fix an uncertain match by broadening access.
Review controls and cost
Specify who can view, create, edit, approve, publish, export, correct, archive, and delete offers, payment records, receipts, and refunds. GOV.UK guidance recommends minimum necessary data, access control, security, supplier accountability, incidents, and end-of-contract handling.
The U.S. Department of Education data-quality guidance connects business rules, validation, infrastructure, and professional learning. Include payment, integration, support, export, and contract-end costs in the review.
Report and improve
Review expected, received, reconciled, corrected, refunded, and unresolved items. Measure correction effort, family questions, support demand, access exceptions, and the intended outcome at 30, 60, and 90 days.
Make the next action clear
Use this guidance to improve one bounded part of how a bursar can reconcile school admissions software. Name the owner, affected record, evidence needed, and review date. Keep the test small enough for admissions staff to complete and specific enough for a later audit.
Check both an ordinary application and one meaningful exception. If either depends on undocumented knowledge, add the missing definition, training note, permission rule, or support route before calling the next step ready.
Record what changed, what remains manual, and who reviews the result before the next admissions cycle.

