Fee collection is chased by hand
Who has paid which instalment, and who is late, is rebuilt from bank statements and messages.
Fees collected on a schedule, staff paid on contracts that follow a term, and families who ask the same questions every week. The business side is common; the student side is built around your institution.
Who has paid which instalment, and who is late, is rebuilt from bank statements and messages.
Teaching staff, part-time instructors and administrative staff have different contracts, leave rules and payment dates.
Dates, fees, documents and procedures are answered again by the front desk, in Arabic and in English.
Records of students, classes and cohorts are kept by several people in several files.
Student records include minors' personal data, and who can see them has to be limited by role.
These are the Saudi regimes that touch this sector, and what the software does about each. Your proposal confirms which apply to your company. This is not legal advice; confirm obligations with your adviser.
| Requirement | What the software handles |
|---|---|
| VAT at 15% | Applied per invoice line with the VAT treatment you set for your fees. Whether VAT applies to your fees depends on your licence and customers. |
| ZATCA e-invoicing | Invoicing is built to work with ZATCA e-invoicing requirements. The scope for your company is confirmed in your proposal. |
| Personal data (PDPL) | Student and parent records are personal data. Access by role, an audit trail and hosting location are agreed per project. |
| GOSI, WPS, Saudization | Contributions, salary files and headcount tracking for teaching and administrative staff. |
Finance, invoicing and approvals for the administration of the institution.
Learn morePayroll, leave, Hijri dates, hiring and attendance for teaching and administrative staff.
Learn moreAn assistant that answers parents and applicants in Arabic and English from your own published documents.
Learn moreA parent or student app or website in Arabic and English from the first screen.
Learn moreEnrolment, cohort scheduling and student records, built around how your institution works.
Learn moreThe order differs a little by sector. The principle does not: a written scope comes first, and you test with your own data before anything goes live.
Administration (finance, staff) is common ground; the student side (enrolment, classes) is specific. We scope them separately.
Fee invoicing and payroll go first and can be tested against a past term.
The people who handle enrolment today walk us through the real cases, including the awkward ones.
A parent or student view comes after the underlying records are accurate.
Not as a ready-made product. Enrolment, classes and records are built to order and scoped in a written proposal.
Online card payment needs a payment provider and an agreement with it. We scope that as an integration; it is not switched on by default.
Yes. Documents and screens are designed for both languages from the start.
It can be structured that way. How campuses, budgets and users are separated is confirmed at scoping.
A consultant from our Riyadh team replies with next steps. A written, itemised proposal follows before any work starts.