Fee structures per class and session
Define what each class is billed for in each academic session, so the amount owed is derived rather than typed.
Fees, students and records in one place.
EJA FeeDesk runs the money side of a school — fee structures per class and session, what each student owes, what has been paid and what is still outstanding — alongside the student records those figures belong to.
Because it sits on the same platform as bookkeeping, every payment recorded at the bursary posts straight into the accounts instead of being re-entered from a receipt book at the end of term.
School management software is the system an institution uses to hold its student records and run its fees: who is enrolled, which class they are in, what they are billed for the session, what they have paid and what is still owed.
What separates it from a spreadsheet is that the fee structure, the payment and the ledger are the same record. A payment taken at the bursary is immediately an outstanding balance reduced and an entry in the accounts, rather than three places someone has to remember to update.
Define what each class is billed for in each academic session, so the amount owed is derived rather than typed.
Admission numbers, classes, guardians and contact details held once and carried through the student's time at the school.
Record full or partial payments against a student and see the running balance without working it out by hand.
See what every student owes across all sessions, so the bursary chases from a list rather than from memory.
Bring a whole roster in from a spreadsheet, with every row checked before anything is saved.
Fees collected post into bookkeeping as they are received, so termly reconciliation starts from complete data.
Outstanding balances are visible per student rather than buried in a receipt book, so less is written off at the end of term.
A payment is recorded once and reaches the accounts on its own, instead of being re-keyed from receipts.
What a student owes can be answered in seconds, with the payment history behind it.
Schools running more than one campus see each separately and the group together, on the same platform.
School Management is stronger connected to the modules around it. Every application shares one data layer.
It holds your student records and runs your fees: the fee structure for each class and session, what each student owes, what they have paid and what is still outstanding.
Yes. Payments are recorded against a student as they come in, full or partial, and the outstanding balance updates without anyone calculating it.
Yes. Payments post into bookkeeping as they are recorded, so the accounts and the bursary agree without a reconciliation exercise at the end of term.
Yes. A roster can be imported from a CSV or Excel file, and every row is validated before anything is saved so bad data is reported rather than stored.
Yes. Each branch keeps its own students and fee structures, and the group can be seen together on the same platform.
Start with this module alone, or switch on the rest of the EJA ecosystem as your operations grow. One platform, one login, one set of records.