Most owners who put off changing HR software are not worried about the software. They are worried about the month in the middle: the old spreadsheet half retired, the new system half loaded, and a payroll due on the 28th either way. That worry is reasonable. It is also manageable, because the work is predictable once you see it laid out.
This guide sets out what HR software implementation in the UAE involves for a small or mid-sized company: what to prepare before day one, a four-week plan tied to your payroll date, a worked example with hours per task for a 40-employee company, the mistakes that cause a bad first month, and what the same 30 days look like when you are switching to HRX360.
How long does HR software implementation take in the UAE?
For a company of up to about 100 employees, plan on one payroll cycle, roughly 30 days. The settings are the short part. What sets the pace is your own data: one clean employee list, leave balances as at a fixed date, salary by component, and bank details that match the bank. The month ends with a checked first payroll.
General guides to implementation quote anything from four weeks to six months, because they are written for companies of every size in every country. Two things make the UAE case more specific.
The payroll date is fixed. Salaries go through the Wage Protection System every month whether or not you are mid-change, so the plan has to be built backwards from your normal payroll week, not forwards from the day you sign.
The payroll file is unforgiving. The WPS salary file carries each employee's IBAN, routing code and MOL personal number. A switch that retypes those fields introduces errors the old process never had.
A company that only needs records, leave and attendance can be working in the new system well inside the month. A company that also moves payroll should give itself the full cycle, and should not shorten the last week.
What should you prepare before day one?
Prepare nine things: the employee list, document numbers with expiry dates, leave rules and balances, salary by component, payment details, the company's WPS details, the holiday calendar and approvers, attendance device details, and last month's final payroll as a comparison baseline. Most delays in the first 30 days come from one of these being incomplete, not from the software.
| What | What it should contain | The usual problem |
|---|---|---|
| Employee list | One row per person: employee code, full name as on the passport, joining date, department, designation, location, reporting manager, work email | Three spreadsheets with three versions of the same name |
| Documents | Passport, visa, Emirates ID and labour card numbers with expiry dates | Expiry dates typed as text, or missing for long-serving staff |
| Leave | Each leave type and its rules, plus every balance as at the cut-over date | Balances that include leave already booked for next month |
| Salary | Basic, housing, transport and every other allowance as separate amounts per employee | One gross figure with no split |
| Payment details | Payment method, IBAN, bank routing code and MOL personal number per employee | IBANs retyped from a printout |
| Company WPS details | Establishment (registration) number and the company bank routing code | Taken from an old SIF file without checking with the bank |
| Calendar and approvers | Weekend days, this year's public holidays, and who approves leave for each team | Approvers who have left the company |
| Attendance | Device brand and model, where each device sits, and the enrolment number of each employee | Enrolment numbers that exist only inside the device |
| Comparison baseline | Last month's final payroll, employee by employee, from the old system or spreadsheet | Only a bank total, with no employee detail |
The last row is the one companies skip. Without an employee-level record of what was paid last month, there is nothing to compare the first run against, and the first run becomes the test. If you are moving payroll part-way through a year, the cut-over detail is covered in migrating payroll mid-year without breaking WPS.
What happens in each of the four weeks?
Week one lays the foundations and cleans the data. Week two loads people, documents and leave. Week three connects attendance and brings employees in. Week four runs the first payroll, compares it with last month and locks it. Start early in a month so week four lands on your normal payroll week.
| When | Stage | What gets done | Done when |
|---|---|---|---|
| Days 1 to 5 | Foundations and data | Company profile, weekend days, financial year, departments, designations and locations, roles for HR and payroll. In parallel, clean the employee spreadsheet. | The employee list is complete and one person owns it |
| Days 6 to 12 | People, documents and leave | Import employees, enter document expiry dates, create leave types, load opening balances, set approvers. Spot-check ten employees against the source files. | Any employee you pick shows the right manager, documents and leave balance |
| Days 13 to 19 | Attendance and employee launch | Set working hours, connect devices or switch on mobile clock-in, add enrolment numbers. Send employees their sign-in email and a short note on what to use. | A week of punches is arriving and the first leave requests come through the system |
| Days 20 to 26 | First payroll | Load salaries and payment details, confirm days worked, enter the one-off amounts, process, compare to last month, fix and reprocess, then lock. | Every difference from last month has a reason written next to it |
| Days 27 to 30 | Pay and review | Generate the WPS file from the locked run, publish payslips, collect the questions from staff, and list what moves to month two. | Salaries paid on the usual date and the old spreadsheet is closed |
The order matters more than the dates. Each stage feeds the next: payroll reads days worked from attendance and unpaid days from leave, and both read the employee record. Loading salaries before the employee list is settled means loading them twice.
Notice also that employees join in week three, not week one. By then their manager, documents and leave balance are already right, so the first thing they see is correct. A wrong leave balance on day one costs more trust than a launch that comes two weeks later.
Worked example: how many hours does a 40-employee company spend?
As a planning estimate, a 40-employee trading company with records in spreadsheets and one attendance device should budget about 35 hours of its own time across the month: 22 for HR, 9 for whoever runs payroll and 4 for whoever looks after IT. About a third of that is two tasks: cleaning the employee spreadsheet and checking the first payroll.
Illustrative estimate, hours of the company's own time:
| Task | HR | Payroll | IT | Total |
|---|---|---|---|---|
| Clean and complete the employee spreadsheet | 6 | 0 | 0 | 6 |
| Company settings, lists and roles | 2 | 0 | 1 | 3 |
| Import employees and enter document expiry dates | 4 | 0 | 0 | 4 |
| Leave types, opening balances and approvers | 3 | 0 | 0 | 3 |
| Salary structures and payment details | 1 | 4 | 0 | 5 |
| Working hours, devices and enrolment numbers | 2 | 0 | 3 | 5 |
| Employee launch and first-week questions | 3 | 0 | 0 | 3 |
| First payroll with a comparison to last month | 1 | 5 | 0 | 6 |
| Total | 22 | 9 | 4 | 35 |
How to read it: these are planning figures for one example company, not measurements, and your own will differ. The shape is what carries over. The two six-hour lines (cleaning the spreadsheet and checking the first payroll) make up 12 of the 35 hours, and neither is software work. A company with a tidy employee list and a clear record of last month's pay starts with a third of the job already done. A company with neither should add time to week one, not take it from week four.
Spread over a month, 22 hours for HR is about an hour a working day. That is the honest cost of switching for a company this size, and it is worth setting against what the old process costs every month. The HR software cost guide covers the subscription side of the same sum.
What goes wrong in the first 30 days?
Five things cause most bad first months: changing policies while moving systems, paying the first payroll without comparing it to the last one, missing WPS fields, launching to employees before balances are right, and leaving the whole project with one person. None is a software fault, and each can be avoided by deciding it before day one.
Improving the rules while moving. A new system is a tempting moment to change the leave policy or the overtime method. Move first, on the rules you have today, so the first payroll can be compared like for like. Change policy in month two.
No comparison on the first run. If the first month's pay is not checked employee by employee against the previous month, an unmapped allowance is found by the employee, on payday.
Missing WPS fields. An employee without an IBAN, routing code or MOL personal number cannot be paid through the file. Find the gaps in week one, when there is time to ask the employee or the bank.
Launching to staff too early. Employees judge the system by the first number they see. Bring them in after leave balances and reporting lines have been spot-checked.
One person holds everything. If the only person who understands the setup is away in payroll week, the month slips. Give payroll its own role and its own login from the start.
Punches with no owner. A device can be connected and still produce nothing useful if employees have no enrolment number on their record. Collect the numbers before the device is linked.
Do employees and managers need training?
Employees need a sign-in and one clear message, not a course. Managers need to know where approvals arrive. The people who need real time are the two or three who will run the system: allow them a few hours in the first week to learn the monthly cycle, and make the first payroll a supervised one.
Employees: tell them what to use it for from day one (apply for leave, see their balance, check attendance, open their documents) and who to ask. Keep the old leave form closed from the same day, or both will be used.
Managers: show them one approval from start to finish. The commonest reason requests stall in month one is a manager who did not know anything was waiting.
HR and payroll: learn the order of the month, not every screen. Attendance, then one-off amounts, then the run, then the review, then the lock.
What does switching to HRX360 look like?
The plan is the same four weeks. A guided setup suggests leave types, holidays and pay periods for the UAE, your lists and employees load from Excel, and employees get an email to set their own password. The first payroll is compared with last month in Salary Review, then locked before the WPS file is generated.
What each week uses:
Week one, foundations: the guided setup proposes starting values for a UAE company, which you review. Departments, designations, locations and holidays import from the Excel or CSV file you already have: you match your columns to the HRX360 fields and check the rows before anything is written. Roles & Permissions decides who sees and does what.
Week two, people and leave: employees import from an Excel template, leave types can start from 15 ready-made templates (annual, sick, maternity, Hajj and more), and leave balances load from Excel. Document expiry dates on each record feed the expiry reminders.
Week three, attendance and staff: ZKTeco and Hikvision devices connect and push punches in, matched to each employee by enrolment number, or employees clock in from the employee app with a geo-tagged punch and photo. When an employee record is saved with an email address, HRX360 creates the portal account and emails a link to set a password, and HR can resend it from the profile.
Week four, first payroll (Professional plan): salaries and payment details import from Excel templates. The month then follows three screens in order: Payroll Attendance, Variable Salary Entry and Payroll Run. Payroll Run warns, by name, about payable employees with no saved attendance before it processes.
Review, lock and pay: a processed run is a draft you can correct and reprocess as often as needed. Salary Review produces the month-on-month workbook, the run is locked, and the WPS SIF file is generated from the locked run. Employees see the payslip only when you publish it.
For learning the system, every main screen has a built-in guide and a Take the tour button that walks round the live screen, the Learning Center is a step-by-step course from first sign-in to month-end payroll, and Ask HRX360 answers how-to questions in plain language on the screen you are on.
What is included: standard online implementation and training on every plan, covering company, leave, attendance and payroll configuration for your plan, employee imports from HRX360 templates with your prepared data, and a first payroll walkthrough on payroll plans. Custom integrations, extensive data migration and onsite services are quoted separately. Plans and inclusions are on the pricing page.
One point on plans: payroll, the WPS file and Salary Review are on Professional. On Standard, which covers records, documents, leave, attendance and the employee app, the plan above ends after week three. For the modules behind each week, see employee management, leave management, time and attendance, employee self-service and payroll software with WPS-ready SIF files. For the first-run check itself, see salary reconciliation before payday.
See your first 30 days before you commit
Bring your employee spreadsheet and your payroll date to a demo, and we will walk through the four weeks against your own data. HR, leave, attendance and the employee app are on Standard at AED 6 per employee per month. Full UAE payroll with WPS/SIF and Salary Review is on Professional at AED 14, billed annually from a 10-employee minimum, excluding 5% VAT. No setup fees.
Frequently asked questions
How long does HR software implementation take in the UAE?
For a company of up to about 100 employees with records in spreadsheets, plan on one payroll cycle, roughly 30 days. The settings are the short part. Cleaning the employee data, connecting attendance and checking the first payroll against the previous month are what set the pace.
What data do we need before we start?
One clean employee list, document numbers and expiry dates, leave balances as at the cut-over date, each employee's salary by component, bank details with the IBAN, routing code and MOL personal number, the company's WPS establishment number, the public holiday list, and last month's final payroll to compare against.
Can we switch HR software in the middle of the year?
Yes. WPS works one month at a time, so there is no need to wait for January. Choose a month with no bonus or salary review, load leave balances as at the cut-over date, and compare the first run to the last month from the old system before paying from the new one.
Do we need to run the old and new payroll side by side?
For one month, yes. Process the first month in the new system, compare it employee by employee to the last locked month from the old one, and explain every difference. That comparison is the cheapest point to find an unmapped allowance or a mistyped IBAN.
Is there a setup or implementation fee with HRX360?
No. Standard online implementation and training are included on every plan: company, leave, attendance and payroll configuration for your plan, employee imports from HRX360 templates with your prepared data, the Learning Center and Ask HRX360, and a first payroll walkthrough on payroll plans. Custom integrations, extensive data migration and onsite services are quoted separately.
Will our biometric attendance devices work?
HRX360 connects to ZKTeco and Hikvision devices, and both are in use at customer sites. Confirm your device model and its network connection before go-live, and make sure every employee who clocks has an enrolment number on their profile, because that number links each punch to the right person.
How much training do employees need?
Very little. Employees receive an email with a link to set their own password, then use the employee app for leave, attendance and documents. Plan one short message from HR explaining what to use it for, and one named person to answer questions in the first week.