UAE leave policies
Annual, sick, maternity, parental, bereavement, hajj, study and unpaid, with accrual, carry-over and encashment rules set per entity.
Core HR suite
Leave & attendance
Nineteen features for the part of HR that runs every day: UAE leave policies with sick-leave tiering, split and rotating shifts, geofenced punches and overtime that reaches payroll intact.
Leave and attendance is the highest-volume thing an HR system does. It is also the module most often replaced first, because a policy engine that can't express the local rules turns into a spreadsheet within a quarter.
KLEDHR models UAE leave entitlements directly — including sick leave that pays at different rates as it progresses through its tiers — and takes attendance from the places it actually happens: a phone at a site, a biometric device at a gate, a manager's roster.
Sick-leave tiering
Sick leave that changes pay rate as it progresses is handled by the policy engine, not by a payroll adjustment someone remembers to make.
Shifts of every shape
Hourly, in-out, split and rotating patterns, with rosters published to the mobile app and changes tracked against the original.
Geofenced punches
A punch is validated against the site boundary, so a warehouse shift can only be started at the warehouse. Exceptions are flagged, not silently accepted.
Biometric & device input
Biometric terminals and mobile Face ID both feed the same timesheet, so mixed-site workforces don't need two systems.
Overtime workflows
Overtime is requested, approved and rated before it reaches payroll — with the approval attached to the hours, where an auditor expects it.
Attendance that survives a real site
Attendance systems are usually specified for an office and then deployed to a warehouse. Connectivity drops, shifts get swapped at the gate, and half the workforce doesn't sit at a desk. The design has to assume that.
- Punches captured offline on the mobile app and reconciled when the device reconnects.
- Geofence radius set per site, with a documented exception path for genuine cases.
- Roster changes, swaps and no-shows visible to the supervisor the same day.
- One timesheet per employee regardless of how the hours arrived.
The line into payroll
Leave and attendance only matter because they change pay. Unpaid leave, unapproved absence, overtime and shift allowances all land in the payroll run — and each is a place where a manual step becomes a payroll error.
- Approved overtime rated by policy and posted straight to the run.
- Unpaid leave deducted and — separately — excluded from gratuity service length.
- Absence exceptions surfaced before the run locks, not after the file is sent.
- A full trail from a punch on a phone to a line on a payslip.
Questions we get asked
- Can policies differ per entity?
- Yes, and they usually have to. Working week, accrual and encashment rules are set per entity and can be overridden per grade where your policy does that.
- Do you support biometric hardware we already own?
- Device feeds are imported into the same timesheet as mobile punches. Bring the existing terminals; we'll map their export.
- What happens when someone punches outside the geofence?
- The punch is recorded and flagged rather than rejected — with the distance and location — so a supervisor can approve a genuine case and a pattern is visible if it isn't one.
See KLEDHR on your own payroll month
A 30-minute walkthrough on a tenant we spin up for the call — bring your trickiest gratuity or WPS case.
Book a demo