Security Company Payroll in the UAE: The 2026 Guide

SIRA licensing involves training, testing and issuance per guard — typically weeks. Recruitment pipelines must sequence it: offer, SIRA process, then deployment and payroll. Guards 'covering shifts while the licence processes' are unlicensed workers on your roster, and both regulators treat that as strict liability, not an admin delay.

Guards earn a basic plus site allowances that vary by posting — event sites, VIP protection and remote industrial sites command premiums. The allowance must be contractual per posting grade, not per guard by favouritism. When a guard rotates sites, the allowance follows the posting, and payroll must track the rotation.

Report posting allowances as fixed or variable lines matching the contract grade. A guard moving from a standard tower post to an event post mid-month needs a split allowance line with the rotation record as backup. Silent allowance changes look like wage manipulation in the file.

The 8-hour normal day plus 2-hour overtime cap applies inside 12-hour shifts: hours 9-10 are overtime at the statutory premium (+25%, or +50% for 10pm-4am), and hours 11-12 must be genuine breaks or the shift design is non-compliant. Most compliant operators build two paid breaks into the 12 hours and document them — the roster must show where the non-work hours are.

Guards on continuous site coverage need genuinely rotating rest days, not paper ones. A guard rostered 28 days straight is a violation regardless of site requirements — build relief guards into the contract pricing so rest days are affordable, because they are mandatory.

Sites need guarding on public holidays too. Guards working beyond normal hours on holidays earn the premium or an agreed substitute day off — record the election per guard per holiday. Blanket 'holiday worked, no premium' practices collapse on first inspection.

Guards are often hired on low basics (AED 1,500-2,000) with site allowances on top. Gratuity accrues on the basic — about AED 1,050-1,400 per year initially. That is lawful if contractual, but it weakens the guard's income evidence and retention. Some operators raise basics deliberately as a retention investment; the gratuity cost is real, but so is the turnover saving.

Guards transferring between your sites or contracts keep continuous service — only genuine termination with final settlement restarts it. 'Re-hiring' guards between client contracts to reset gratuity is transparent evasion with a paper trail.

Documented salary advances repaid in agreed instalments within legal limits are the clean deduction. Everything else — training bonds, uniform charges, damage claims — needs legal review before it touches payroll. When in doubt, the company absorbs the cost; it is cheaper than the multiplied fine.

SIRA licensing and refresher training are employer costs of doing business in guarding. Budget them per guard per year in the contract pricing, not as deductions. Guards who leave after you trained them are a commercial risk, not a payroll deduction opportunity.

Fix the 25th as your internal payroll cut-off. By that date, site and night-shift allowances figures are final, overtime sheets are signed, and leave changes, deductions and joiner/leaver updates are entered. The 26th to 28th is review time: reconcile the payroll register against the MOHRE labour contracts, prepare the SIF, and have a second pair of eyes check every leaver and joiner line — most SIF rejections trace to a worker-status error on exactly these lines. Submit through your bank or WPS agent so funds clear by the 1st. In security, the recurring squeeze is that site attendance is reported by supervisors across multiple client sites in different formats; the fix is a standing rule that no SIF leaves without the payroll register, the site and night-shift allowances worksheet, and the joiner/leaver list attached and signed off.

Four times a year, do the reconciliations the monthly rush skips. Match the payroll register against actual WPS disbursements and document every dirham of variance — lawful deductions, mid-month exits, corrected SIFs. Confirm ILOE enrolment for everyone hired that quarter. Pull the contract-renewal diary: renewals and non-renewals need decisions 60 to 90 days before expiry, not the week of. Scan leave balances for accruals building into exit liabilities. Guards rotate across client sites; quarterly reconciliation of site allowances against deployment rosters catches errors.

Once a year, revalue the gratuity provision for the financial statements, review basic-salary splits against market rates, refresh site and night-shift allowances policies and have staff re-sign them, and verify that every worker's file holds a current MOHRE contract, an Emirates ID copy, and signed pay acknowledgements. Quantify the annual-leave liability — it sits on the balance sheet whether you measure it or not. Cross-check guard licence renewals against the payroll roster — an unlicensed guard on payroll is a double violation.

One person prepares the payroll, a different person reviews and approves it — no exceptions, even in a five-person company where the reviewer is the owner. The reviewer checks four things: joiners and leavers against HR records, site and night-shift allowances against source worksheets, deductions against signed authorisations, and the SIF totals against the approved register. This single control catches the transposed salary, the leaver paid twice, and the site and night-shift allowances figure typed from the wrong month. Document the approval with a signature and date; an unsigned register is, for audit purposes, an unreviewed one.

Ghost employees — WPS records for people who left, or never existed — are the classic payroll fraud, and security is not immune. Kill it with a monthly three-way match: the payroll register against the WPS disbursement report against the attendance or deployment roster. Every name on the payroll must appear on the other two lists with a reason. Leavers must drop off all three in the same cycle. Where security uses site-based or shift-based attendance, the attendance source — not the payroll file — is the truth; site attendance is reported by supervisors across multiple client sites in different formats, so build the match around the attendance export, not around last month's payroll.

At month-end, the payroll journal must tie to the bank: gross wages, deductions, and net pay per the register should equal the WPS debit and the ledger entries, to the fils. Investigate every variance the same month — small unexplained differences compound into audit qualifications. Accrue gratuity monthly rather than annually so the provision grows smoothly and the year-end adjustment is a true-up, not a shock. Security employers who reconcile monthly close their audits faster and cheaper than those who reconstruct the year in March.

In-house payroll works when headcount is stable and simple — typically under 20 employees with fixed salaries, no site and night-shift allowances complexity, and an owner or admin who actually understands the WPS cycle. The advantages are control and speed: corrections happen the same day, and nobody knows the workforce better. The failure mode is key-person risk: when the one person who knows payroll is on leave, the SIF still has to go out by the 1st. If your security business runs payroll in-house, document the monthly routine step by step so a stand-in can execute it, and have an external reviewer check the setup annually.

Outsource when any of these are true: headcount above 30, significant site and night-shift allowances or overtime complexity, multi-site operations, or a history of late SIFs and rejections. A competent payroll provider brings the SIF discipline, the regulatory update feed (MR 340 of 2026 caught many in-house teams off guard), and the reconciliation routine as standard. The cost — typically a per-employee monthly fee — is usually less than one MOHRE fine or one month of a payroll officer's salary. For security employers, the strongest case is seasonal or project-based headcount swings, where in-house capacity is either idle or overwhelmed with no middle ground.

Insist on: a named account manager, SIF submission with same-day confirmation, a monthly reconciliation report (register vs WPS disbursement), quarterly compliance updates, and a clear liability clause for filing errors — if they file late, the contract should say who pays the fine. Retain ownership of your payroll data and the right to export it any time; providers who hold data hostage are a red flag. Review the arrangement annually against the same test: are SIFs on time, are reconciliations clean, and would you pass an inspection tomorrow? If yes, the fee is working.

The most common workable setup for a growing security business: keep attendance, site and night-shift allowances computation and approvals in-house (nobody knows the operation better), and outsource SIF filing, WPS reconciliation, gratuity provisioning journals and regulatory monitoring. This splits the work at its natural seam — operational data stays inside, compliance mechanics go to the specialist. Define the handoff precisely: what file, in what format, by what date each month, and who chases whom when it is late. Review the split yearly; as headcount grows, the outsourced portion usually grows with it, until the business is large enough to justify a full in-house payroll function again.