Solutions › Pay & Administer
If the record is wrong, everything built on it is wrong.
Core HR, payroll, time and self-service are the least glamorous stage and the one everything else depends on. Analytics, quota reporting and learning all read from this layer, which is why fixing it first is usually the cheapest decision available.
Stage 3 of 8 · One platform, multi-entity and multi-country
Hours captured
Payroll run
Self-serviceThree things that break first
Payroll failures are rarely payroll failures. They are usually attendance, structure or filing problems that only become visible on the twenty-fifth of the month.
Hours arrive as a spreadsheet
Attendance is captured in one system, or on paper, and re-entered before the run. Every re-entry is a correction next month, and the corrections are found by employees rather than by payroll. The process is not slow because payroll is slow.
Each entity is its own island
Separate systems, separate calendars, separate rules per legal entity. Group reporting becomes a consolidation exercise in Excel, transfers between entities lose service history, and nobody can state total cost of employment without a week of work.
Self-service assumes a desk
A portal that needs a laptop and a corporate email excludes most of the workforce in a shift or site operation. Leave requests, payslips and updates route back to a supervisor, which is exactly the work self-service was bought to remove.
Go deeper
GuideChoosing the best payroll management system in the UAE
Guide · Pay & Administer
Read the resourceWhat is different about paying people in the GCC
Payroll mechanics are universal. The statutory layer around them is not, and it is the part global platforms most often leave to you.
Every state files wages its own way
All six GCC countries require salaries to be paid through a government-monitored channel, with a different platform, file format, deadline and tolerance in each, and each legal entity files separately. Three countries and four entities is twelve monthly obligations, not one.
End-of-service is a balance-sheet item
Gratuity accrues under a per-country formula from actual service and actual final pay. It has to be provisioned rather than estimated, and it has to survive a transfer between entities inside the same group, which is where most manual calculations quietly break.
The payslip has to be readable
Statutory documentation and payslips are expected in Arabic, and for much of the workforce the practical language is neither Arabic nor English. A payslip a worker cannot read becomes a question for a supervisor, every month, for every worker.
What sits where
This is the one stage that runs on a single platform. The real question is not which vendor, it is which layer you are replacing, and which you are leaving alone.
The layer we implement
One tenant holding every entity and country, so the employee record, the hours and the statutory filing are the same system rather than three that have to be reconciled.
- Core HR as the single employee record
- Payroll with per-country rules and per-entity filing
- Time, attendance, rosters and leave feeding the run directly
- Compensation and benefits against approved bands
- Social insurance and end-of-service from actual service
- Self-service on a phone or a shared device, Arabic-first
What usually stays
If a global HCM or ERP already runs group HR, finance and consolidation, replacing it is rarely the right purchase. The gap is almost always the statutory and attendance layer beneath it.
- Group HR and org hierarchy stay where they are
- Finance and GL consolidation unchanged
- Recruitment stays if recruiters are productive in it
- We integrate rather than duplicate the employee master
- Which layer moves is a scoping decision, not a default
The honest test: if your global platform already files wage protection per entity in every country you operate in, calculates gratuity from actual service, and puts an Arabic payslip on a worker’s phone, then you do not need this layer, and we would tell you so rather than sell you one. It is worth checking against those three before spending anything.
The order we would run it
One entity live and correct beats six entities half-configured. The sequence below is the one we use regardless of size.
The products behind this stage
FAQ
Frequently asked questions
What HR and finance leads ask before moving the system of record. Can’t find the answer you need?
Talk to us →How long does a payroll implementation take?
It depends on how many entities and countries are in scope and on the state of your current data, which is why we scope before quoting rather than publishing a standard number of weeks. The two things that move the date most are data quality at migration and how many distinct pay rules actually exist once documented.
Do we have to replace our global HCM?
Usually not, and we would say so. If a group system runs core HR and consolidation adequately, we implement the GCC statutory and attendance layer underneath and integrate the two. Replacing a working group platform to solve a filing problem is an expensive way to fix the wrong thing.
Can one tenant handle several countries?
Yes, and that is the point of doing it this way. Each country keeps its own rules, calendars and filing format while the group gets one employee record and one consolidated view. Entities still file separately because the regulator requires it, the difference is that you run one close rather than several.
What happens to service history when someone transfers?
Service is held continuously against the person rather than against the entity, so a transfer preserves the gratuity accrual and the leave balance. This is the case that most often breaks in a multi-system setup, and it is worth testing explicitly during a parallel run.
Will the workforce actually use self-service?
Only if it reaches them. Self-service that assumes a laptop and a corporate email excludes shift and site populations entirely, so it runs on a personal phone or a shared in-store or on-site device, in the languages the population actually reads. Where that is not true, work returns to supervisors.
Can we start with one entity and extend?
Yes, and it is what we would recommend. One entity goes live, the filing and the pay rules are proven against real cycles, then the remaining entities are added onto the same tenant. Timing for the rest is agreed after the first close rather than promised in advance.
Where this stage leads
Start from your next payroll close.
Tell us how many entities and countries you pay in, what runs attendance today, and how many corrections the last three months produced. We will tell you whether this is a payroll problem or an attendance one, and what we would fix first.
