These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Education ERP
- Features
- Fees and collections
Fees and collections
Connect approved fee plans, concessions, due dates, receipts and outstanding balances.
OverviewFee plans awaiting approval×
Education ERP · Fees and collections
New
Fee plans awaiting approval
Fee plan approval waits for the bursar
| Number | Enrollment | Concession amount | Currency | Policy version | Status | |
|---|---|---|---|---|---|---|
| FP-87863 | Rohan Kapoor, systems, autumn 2026 | 230 | US dollar | Tuition policy 2026.1 | Submitted | |
| FP-17135 | Zoe Mensah, science, spring 2027 | 550 | Canadian dollar | Scholarship policy 2026.2 | Submitted | |
| FP-39623 | Rohan Kapoor, systems, autumn 2026 | 70 | Euro | Late fee policy 2025.4 | Submitted | |
| FP-44999 | Isabel Cruz, health, summer 2027 | 570 | British pound | Refund policy 2026.3 | Submitted | |
| FP-82611 | Isabel Cruz, health, summer 2027 | 710 | Australian dollar | Lab fee policy 2026.1 | Submitted |
6 of 6 records
US dollarFee plans · FP-87863
SubmittedEnrollmentRohan Kapoor, systems, autumn 2026
Concession amount230
Policy versionTuition policy 2026.1
OwnerRiya Banerjee
What you can do
Know what was charged and what was paid
A fee balance is the result of charges, concessions, credits and allocated receipts. It is not the last payment amount copied into a student record. Define a fee plan for the enrollment, retain the applicable policy version, and issue charges with their own due dates. This gives the bursar a clear explanation when a student asks why a balance is still outstanding.
How the work is organized
Record a bank or payment-provider confirmation once, then allocate that receipt to the charges it settles. Partial payments leave a visible remainder; unallocated cash stays visible until a matching decision is made. A concession needs an authorized amount, reason and owner. Withdrawal adjustments should reverse or credit the original charge so the account history still explains both the initial obligation and the correction.
- Review concessions. The bursar approves policy exceptions before revised charges are issued.
- Deduplicate payments. Use the provider reference as an idempotency key when a notification is delivered again.
- Separate a receipt from settlement. A checkout redirect or unconfirmed payment message does not settle a charge.
What to agree during setup
Bring a fee schedule, concession policy, opening student balances and a bank reconciliation sample. Test a partial receipt, an overpayment, a duplicate provider event and a withdrawal after billing. Agree who can allocate cash, approve a concession and authorize a refund. Reconcile the resulting student balances to the finance ledger at the end of the pilot.
Check the handoff on an actual case
A student pays part of a tuition charge and later makes a second payment that covers the remaining tuition and an examination fee. Keep each bank confirmation as a receipt, then record which charge each allocation settles. This lets the bursar explain the account without changing the original tuition amount or treating the second payment as a new charge.
If the payment provider sends the same confirmation again, the stable provider reference should resolve to the existing receipt. If the bank confirms an amount that cannot yet be matched, keep it in the unallocated-receipts queue. It should not disappear or be assigned to the first student with a similar name.
During the pilot, ask finance to reconcile the bank total, receipt total and allocated total separately. Ask the bursar to explain the student’s remaining balance from the actual charge and allocation history. Resolve discrepancies before enabling scheduled reminders or importing the next collection file.
Follow the work through
Collection reports should show charge due dates and payment allocation separately. Link disputed balances back to the fee-policy version and supporting documents before sending reminders.
- Application to enrollment: Move an application through a recorded admission decision into the correct academic period.
- Fee billing to reconciliation: Issue approved charges, allocate confirmed receipts and investigate the remaining balance.
Review the implementation plan and the data model before preparing your import files.
What it keeps track of
Data model- Fee plans
- Approved charge schedule and policy version for an enrollment.
- Charges
- Student fee obligations and due dates.
- Receipts
- Confirmed collection evidence against a student account.
- Receipt allocations
- Allocation of one receipt across student charges.
Who uses it
Permissions- Bursar
- Manages student accounts.
- Registrar
- Decisions supply enrollment changes but do not automatically waive a charge.
- Finance Manager
- Reviews the reconciliation and ledger posting.
Set up Education ERP your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.