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.
- Timetable Generator
- Features
- Learner fees
Learner fees
Issue fees to learners, record what has been paid and see what is still outstanding.
OverviewDraft Fees×
Timetable Generator · Learner fees
New
Draft Fees
Approval conditions
| Learner | Description | Amount | Due date | |
|---|---|---|---|---|
| LRN-95134 | Draft fss-469 | 270 | 11 Oct | |
| LRN-74013 | Draft fss-681 | 280 | 07 Oct | |
| LRN-29320 | Draft fss-402 | 530 | 04 Oct | |
| LRN-29677 | Draft fss-913 | 720 | 24 Oct | |
| LRN-63629 | Draft fss-687 | 680 | 03 Oct |
6 of 6 records
Draft fss-469Fees · FSS-27465
LearnerLRN-95134
Amount270
Due date11 Oct
What you can do
Keep each learner's balance explainable
Fees are charged to learners: a course fee, a lab fee, an exam fee. Each fee has a description, a due date, an amount, the amount paid so far and a status: Draft, Issued, part paid, Paid or Voided. The Finance Officer prepares fees as Draft, issues them, and records payments as they arrive.
A fee is part paid when some money has come in and Paid when the paid amount reaches the full amount. A fee raised in error is Voided and stays on record, so the learner’s account can always be explained. Payments themselves are taken through your payment provider or finance system; the paid amount is recorded here.
How the work is organized
- Draft, then issue. Fees are prepared as Draft and issued once checked.
- Track what is paid. The paid amount grows with each payment. Part payments stay visible until the fee is settled.
- Void instead of deleting. A fee raised in error is Voided and remains on the learner’s record.
What to agree during setup
Agree the fee types and their standard amounts for each course. Agree due dates and how far ahead fees are issued. Decide how refunds for withdrawals are handled in your finance system. Agree how often paid amounts are updated from your payment provider.
Check the handoff on an actual case
A learner enrolls in Data Analysis 101. The Finance Officer drafts a course fee of 600 USD due February 1 and a lab fee of 80 USD, checks them and issues both. The learner pays 300 USD on January 25; the course fee moves to part paid with 300 paid. A further 300 arrives on February 20 and it becomes Paid.
The lab fee was charged to the wrong learner. The officer voids it and issues a new lab fee to the correct learner. Both learners’ accounts still explain every line.
Rehearse this during setup with a handful of learners from last term. Issue their fees, record a part payment and a full payment, and void one fee raised in error. Then compare the outstanding total with your finance system. The two figures should agree before the first live term, and any difference should trace to a payment that has not yet been recorded here.
What your team sees
- Outstanding Fees — Issued and part-paid fees with amount, paid amount and due date.
- Draft Fees — Fees prepared but not yet issued.
Follow the work through
- Fee issue to payment: Issue the fee and record payment.
Connect your payment provider before the first term.
What it keeps track of
Data model- Fees
- Learner fees with amount, paid amount and status.
- Learners
- Learners enrolled in courses.
- Enrollments
- Learner to course enrollment lifecycle.
Who uses it
Permissions- Finance Officer
- Issues fees, records payments and voids errors.
- Academic Administrator
- Reads outstanding fees when a learner asks.
- Admin
- Corrects records and access.
Set up Timetable Generator your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.