JASO INSIGHTS / MIDDLE EAST
Choosing an HRMS for a growing team in the Middle East
Start with the working day your team needs to manage. Then check the country, company and payroll requirements behind it—before choosing a system from a module list.
1. Map the locations and people before the policies.
A business with an office, a warehouse and a field team has several attendance and approval journeys. Write down where employees work, which company employs them, who approves their requests and which records finance receives. A single company setting may not describe every location.
Consider an illustrative 60-person distributor: 20 office employees, 15 warehouse employees and 25 field reps. Give the vendor one task from each group. Follow a warehouse shift that crosses midnight, an office leave request and a rep’s visit to a trade client. This is a demonstration exercise, not a JASO customer example.
2. Show the schedule change in the demonstration.
Bring the working week, holidays, shift times and attendance rules your company actually uses. If you operate across countries or change schedules during the year, ask how a change takes effect without altering the history of an earlier pay period.
Test a late check-in, a missed check-out and a corrected attendance record. Ask who can make the correction and what the manager can review afterward. A policy screen is useful only when you can follow its effect on an employee’s day.
3. Connect a field visit to a decision.
For pharma, distribution or another field-led business, attendance answers only part of the question. Ask to see the rep’s territory, assigned doctor or trade client, visit location and exception review. Then ask which clients remain unvisited in the agreed cycle.
Include a client with two locations and a visit outside the configured radius. The system should give the reviewer useful context. Location evidence supports a record; it does not prove a conversation happened. Agree how explanations and corrections will be handled.
In JASO HR, territory, client, visit and manager-review workflows sit alongside the employee foundation. Coverage analysis is scope-dependent: confirm the capability in the written proposal.
4. Check the language and devices people will use.
Ask users which interface language, date format and training material they need. If Arabic and right-to-left layouts are requirements, verify the actual screens with the vendor. An English product demonstration does not establish Arabic support.
Test representative employee devices, permissions and connectivity. Include a manager reviewing a request from a phone. Discuss offline behaviour separately and check it on the intended device rather than inferring it from a portal screenshot.
5. Keep local payroll in its own scope.
Ask your payroll provider what calculations, output files, bank submissions and wage-protection processes apply to your establishment. The UAE and Saudi Arabia have their own wage-protection programmes; the official MOHRE overview and Saudi HRSD overview illustrate why this needs country-specific review. Check current requirements with the local provider.
A currency setting or payslip screen is not evidence that those processes are supported. JASO HR’s current payroll configuration focuses on India. For a Middle Eastern rollout, confirm whether the HR workflows can operate alongside your local payroll process and separately scope any required exchange or integration.
6. Agree where employee data goes.
Ask where production records and backups are stored, who can access them, how support access works and what happens at the end of the subscription. The UAE government’s data-protection overview describes its personal-data framework, including cross-border transfers. Confirm the rules that apply to your country and establishment rather than assuming one regional policy covers every team.
Use fictional or redacted records during the first demo. Agree the actual data handover, responsibilities and access before a live pilot.
7. Put the first rollout in writing.
Choose a representative location or territory, a manager and an HR user. List the normal tasks and exceptions that must work. Confirm selected modules, setup, migration, optional reporting, training, support and any local integrations in the rollout scope.
JASO HR is available for paid rollouts, with one 10-person customer team currently on a free trial. For a Middle Eastern team, the walkthrough should establish product fit and regional scope before either side commits. Start with the workflow you want to improve and the country where it operates.
Check the product against your workflow.
See actual JASO HR portal screens with fictional demonstration data, then bring a representative task to a walkthrough. Use the rollout checklist to record the questions your team needs answered.