
A school admissions portal should take a family from first enquiry to a paid, confirmed place in one connected journey. Families apply, upload documents, book assessments, accept offers and pay fees online, and always see where they stand. Behind it, admissions and finance work from one back office, and every payment posts straight to the ERP.
Most UAE schools already have parts of this: an online form here, a payment link there, a spreadsheet in the middle. The gaps between those parts are where applications stall, payments go unmatched and parents start calling.
This guide sets out what a good portal does at each stage, what to put in your RFP and where these projects usually go wrong. It draws on what we have learned working alongside Emirates National Schools since 2021 on admissions, fee payments and a parent portal connected to Dynamics 365 Finance.
It should run the whole admissions cycle, not just collect forms. A complete online admission system for schools does five jobs:
If a portal stops at the first job, your staff do the other four by email and spreadsheet. That is the setup most schools are trying to leave.
The test of a good portal is simple: at every stage, each team sees what it needs without asking another team.
| Stage | What families see | What admissions sees | What finance sees |
|---|---|---|---|
| Application | A short form in the family's own language, saved as they go | New applications by grade, with completeness | Application fee received or pending |
| Documents | A checklist with each item marked received, accepted or needs action | Documents to review, with reasons for any rejection | Nothing yet |
| Assessment | A booking link and a confirmed slot | The assessment calendar and results | Nothing yet |
| Decision and offer | The offer, its deadline and what to do next | Offers sent, accepted, declined, and the waiting list | Expected registration fees |
| Seat confirmation | A payment page and an instant receipt | Places confirmed per grade | Registration fee matched to the student |
| Tuition and services | Statements, due dates and online payment | Enrolled students | Every payment posted to the ERP |
| Enrolment | A welcome and the first-day details | The student handed to the SIS | The student account set up in finance |
Documents should be checked once, in one place, against a list that matches the grade and the family's situation. Each document needs its own status, so a parent can replace one rejected passport copy without starting again. Staff should see why a file was rejected and who rejected it.
Approvals belong in the portal, not in email threads. Define who can accept, decline or waitlist at each step, and keep an audit trail of every decision. Waiting lists should follow written rules, such as sibling priority where your policy allows it, so offers are consistent and easy to explain to parents.
A school fee payment portal is only as good as its link to the ERP. Every payment should carry the student, the fee type and the term, so it can be matched and posted without anyone re-keying it.
Plan for the fee types you actually charge:
The flow runs from the payment gateway (or a platform such as Noqodi) to automatic reconciliation, then to posting in Dynamics 365 or NetSuite. Finance should see exceptions, not every transaction. We cover the integration patterns in more detail on our ERP integration page.
No, and it should not try to. Most schools run PowerSchool, iSAMS or OpenApply, and those systems do their own jobs well. The portal connects to them.
The important decision is which system owns each piece of data. Agree it early: the SIS owns the student record, the ERP owns the money, the portal owns the journey in between. When that is written down, integrations stay simple and data stops drifting between systems.
Parents in the UAE apply on their phones, in the languages they read best. That depends on the school: a French-curriculum school needs French, and international schools may need several more. Arabic needs a proper right-to-left layout, and every language needs reviewed wording, not a machine translation of the English screens.
Admissions files hold sensitive data about children and families. Under the UAE Personal Data Protection Law, collect only what you need, limit access by role, set retention rules and agree in your contract where data is stored and who can reach it.
A clear RFP gets you comparable proposals. Ask every vendor to show how they handle:
The same few mistakes come up again and again:
Can it work with our current student information system? Yes. A good portal connects to PowerSchool, iSAMS or OpenApply rather than replacing them.
Do fee payments post to our ERP automatically? They should. Payments reconcile and post to Dynamics 365 or NetSuite as they happen, and finance reviews only the exceptions.
Can parents apply in their own language? Yes. Portals can run in Arabic, English, French or whichever languages your families use, with right-to-left layouts for Arabic.
How long does a project take? It depends on scope. After a discovery session, the milestones and dates should be agreed in writing before any build starts.
Start with a discovery session. We map your current journey, the systems involved and where time is lost, then agree a written scope with a fixed price.
See how we approach school admissions and fee payments, or book a discovery session.

