Schools and training institutes in Qatar tend to accumulate software rather than choose it. A student information system bought years ago, a separate package for fee collection because the first one could not invoice properly, an HR system added when headcount grew, and accounting sitting apart from all three. Each was a sensible decision on its own day. Together they produce a finance office that spends the first week of every month reconciling systems that should never have disagreed.
Students, programmes and admissions
Student records hold enrolment history, guardian details, documents and academic progress. Programmes and student batches structure the academic year; course schedules turn that into a timetable. Admissions run as a tracked process from enquiry through application, assessment and enrolment, so prospective students are a managed pipeline rather than a shared inbox.
Fee management that posts to the ledger
This is the part that usually justifies the project. Fee structures are defined per programme and academic term, including the categories most schools actually use — tuition, transport, activities, examination — with discounts, sibling concessions and scholarships handled as rules rather than manual adjustments.
Fee invoices generate against students automatically on the schedule. Collection posts straight to the accounts. There is no export, no import and no reconciliation between a fee system and a finance system, because there is only one system. Outstanding fees by student, by batch and by programme are a live report, and follow-up is driven from it.
A portal for parents
Guardians get a portal to view outstanding fees, download receipts and see their child's records. Exactly what is exposed is configurable — most schools begin with fees only, then open up attendance and assessment once they are comfortable. It reduces front-office traffic substantially, because the majority of parent enquiries are questions the portal answers.
Attendance and assessment
Student attendance records against course schedules. Assessment supports assessment plans, criteria, grading scales and result generation, producing report cards from the data rather than from a separate spreadsheet maintained per class. We configure this to how your academic team already works; imposing a different academic model on teachers is the fastest way to have a system quietly abandoned.
Faculty HR, payroll and WPS
Faculty and administrative staff run on Frappe HR on the same installation: employee records, contracts, leave with the school calendar, end-of-service gratuity, and payroll producing a WPS-compliant salary file for your bank. Payroll posts to the same ledger that fee collection posts to, so the two sides of a school's finances finally meet in one place.
Accounting built for the way schools are funded
Standard ERPNext accounting underneath — multi-currency where fees are paid from abroad, cost centres by department or campus, budgets against them, and financial statements in the structure your auditors and your board expect. Groups operating more than one campus or entity run them as separate companies with consolidated reporting.
No per-student, per-user licence
Education software is commonly priced per student or per user, which means a good year for admissions is also a larger software bill, and giving every teacher access is a budget decision. ERPNext and Frappe HR are open source under GPLv3 — you pay for implementation, hosting and support, never for the right to add a student record or a teacher login.
How the project usually runs
Schools have a hard constraint most businesses do not: the academic calendar. Go-live has to land between terms, and fee cut-over has to align with a billing cycle. We plan backwards from that. A typical sequence is accounting and fee management first, timed to a term boundary, then HR and payroll, then the academic modules — attendance and assessment — from the start of the following academic year. The implementation page covers the general shape, and data migration matters here because student and fee history has to come across cleanly.
Frequently asked questions
-
Does this replace our separate fee collection system?
That is usually the main reason schools move. Fee structures are defined per programme and academic term, invoices generate against students automatically, and collection posts directly to the ledger. There is no month-end exercise reconciling a fee system against the accounts, because they are the same system.
-
Can parents see fees and make payments?
Yes, through a portal where guardians can view outstanding fees, download receipts and see their child's records. What is exposed is configurable — most schools start with fees and gradually open up attendance and assessment.
-
Does it handle faculty payroll and WPS?
Yes, through Frappe HR on the same installation. Faculty and administrative staff payroll runs in the same system as fee collection, produces a WPS-compliant salary file for your bank, and posts to the same ledger. Schools typically run three disconnected systems for fees, HR and accounts — this collapses them into one.
-
Can we track attendance and assessment?
Yes. Student attendance is recorded against course schedules, and assessment supports assessment plans, criteria, grading scales and result generation. How much you use depends on how your academic team already works; we configure to that rather than imposing a model.
-
Is this suitable for a training institute rather than a school?
Yes. Programmes, batches, course schedules and fee structures map onto short courses and certifications as readily as onto academic years. Training institutes usually need lighter academic features and heavier invoicing and CRM, which is a configuration difference rather than a different product.
GET STARTED
Book a demo for your school
Tell us your student numbers, how fees are billed today and which systems you are running — we will show you the consolidated version.