The daily problems

Where the work usually goes wrong.

01

Fee collection is chased by hand

Who has paid which instalment, and who is late, is rebuilt from bank statements and messages.

02

Contracts follow the academic term

Teaching staff, part-time instructors and administrative staff have different contracts, leave rules and payment dates.

03

Families ask the same questions

Dates, fees, documents and procedures are answered again by the front desk, in Arabic and in English.

04

Enrolment lives in spreadsheets

Records of students, classes and cohorts are kept by several people in several files.

05

Children's data needs care

Student records include minors' personal data, and who can see them has to be limited by role.

Saudi requirements

What the software handles for you.

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.

RequirementWhat 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-invoicingInvoicing 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, SaudizationContributions, salary files and headcount tracking for teaching and administrative staff.

Saudi compliance

How a project starts

From first call to a working system.

The 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.

  1. Separate the two halves

    Administration (finance, staff) is common ground; the student side (enrolment, classes) is specific. We scope them separately.

  2. Start with fees and staff

    Fee invoicing and payroll go first and can be tested against a past term.

  3. Design the student side with your office

    The people who handle enrolment today walk us through the real cases, including the awkward ones.

  4. Add portals once the records are accurate

    A parent or student view comes after the underlying records are accurate.

Questions

What buyers in this sector ask.

Do you offer a student information system?

Not as a ready-made product. Enrolment, classes and records are built to order and scoped in a written proposal.

Can parents pay fees online?

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.

Can communications go out in Arabic and English?

Yes. Documents and screens are designed for both languages from the start.

Can one system serve several campuses?

It can be structured that way. How campuses, budgets and users are separated is confirmed at scoping.