Back to blog
Compliance

WPS Compliance for UAE Workforce: What Attendance Records Need to Show in 2026

7 June 20267 min read

The UAE Wage Protection System (WPS) has done its job for over a decade: salaries land on time, in the right accounts, and the regulator can see it. The 2026 update tightens the link between working hours actually delivered and amounts paid. For organisations running multi-site, multi-shift workforces, the question stops being “did the salary go out?” and becomes “can you prove the hours behind it?”

This is mostly a content problem, not a procurement problem. The systems most UAE employers already use can pay people. Where they fall short is producing an attendance evidence trail that holds up to inspection.

What an inspection-ready attendance record actually looks like

Under the 2026 update, an attendance record that satisfies a WPS-linked inspection needs to demonstrate four things at the level of a single staff member, on a single day:

  • The right person was present. Not a fingerprint of unknown provenance — a verifiable, named identity.
  • At the right place. The geographic site of work, not “clocked in somewhere”.
  • At the right time. Tamper-resistant, with no plausible reason to suspect after-the-fact edits.
  • For the right duration. Including breaks, prayer time, and overtime, all accounted for.

A spreadsheet of clock-in times does not pass any of these. A fingerprint reader passes “present” and “time” but not identity (who pressed the finger?) and not place (the reader sits at a single gate). A WhatsApp screenshot of a supervisor saying “all crew on site” is not evidence.

Where most UAE setups break

Three failure modes are common:

1. The biometric is wrong

Fingerprint scanners verify the finger, not the person. If a labour gang shares scanner access, the audit log records identity by whichever ID was punched in — not whose finger was on the pad. Inspectors are increasingly sceptical of fingerprint records as identity evidence.

2. The location is wrong

Many systems record the scanner’s location, not the worker’s. If the scanner is at the project office and the worker is supposed to be at Site B, “scanned in” does not prove “at site”. WPS-linked inspections increasingly ask for the worker’s GPS at the moment of check-in.

3. The duration is wrong

Round-trip drive time, lunch breaks not deducted, prayer time double-counted — small errors compound into meaningful overpayment or underpayment. Either direction is a problem under WPS.

What a clean record looks like in practice

A 2026-compliant attendance record for a single check-in event should include:

  • Staff identifier (employer-issued)
  • Face-match confidence at the moment of check-in
  • GPS coordinates at the moment of check-in, against the configured geofence for the site
  • Device fingerprint of the phone used (so substitution can be detected)
  • Timestamp from the server, not the phone (clock-spoofing protection)
  • The shift expected, against which the check-in is matched
  • A cryptographic signature so the record cannot be silently edited later

Aiya records all seven by default. Working-hour reports roll up across days, weeks, and months; the WPS-ready export takes the rolled-up totals and reformats them for your payroll or bank gateway. The underlying record is retained for the legal period and is exportable per-staff, per-day, on demand.

What to do this quarter

  1. Audit one site for one week using your current system. Pick five staff at random and try to produce a clean inspection-ready record for each. Note where it falls short.
  2. Decide whether the gap is fixable in your current stack or requires switching the underlying attendance system. (Usually it’s the latter once you find the failure mode is structural, e.g. fingerprint readers can’t verify identity.)
  3. If switching, pick a system that records all seven fields above by default and exports cleanly into your existing WPS dispatcher. Avoid systems that promise to process WPS for you — that’s your bank’s job.

The 2026 WPS update is not a reason to panic. It is a reason to stop relying on shared scanners and paper attendance for a workforce that has already moved on to the phones in everyone’s pocket.

Frequently asked questions

Does Aiya dispatch WPS itself?+

No. Aiya produces WPS-ready exports of hours, overtime, and absences in a format your payroll system or bank WPS gateway accepts cleanly. The dispatch itself stays with your payroll provider or bank.

How long do we need to keep attendance records?+

UAE Labour Law requires employers to keep working-time records for the legally specified period. Aiya retains records by default for that full period plus a reasonable audit buffer.

What if the inspector asks for proof of a single check-in two years ago?+

Each check-in is recorded with face-match confidence, GPS coordinates, device, and time. The record is queryable per staff per day and exportable as a PDF or CSV. The biometric image itself may have been deleted under the retention policy, but the audit metadata remains.

Continue reading

This article is for informational purposes only and does not constitute legal, regulatory, or compliance advice. UAE labour, data, and tax rules can change; consult a qualified advisor for decisions specific to your organisation. Specific WPS technical specifications can change. Confirm current requirements with your bank, payroll provider, or UAE Labour Law before configuring exports.