The 85% Rule and Payroll Deductions: How Loan Recoveries, Advances and Fines Affect WPS Compliance

Four months into Ministerial Resolution No. 340 of 2026, one figure is quoted in almost every WPS explainer: an establishment is compliant if it transfers at least 85% of total wages due by the deadline. What almost none of those explainers do is answer the question a payroll team actually has — what does the 85% rule mean for the ordinary deductions I make every month? Salary advances, loan instalments, recovery of a damaged laptop: all of these reduce what lands in an employee's account. Do they put you on the wrong side of the 85% line?

The honest answer is that the rule and routine deductions interact in a way that is widely misunderstood, and at least one popular reading of it — that the rule "effectively caps deductions at 15%" — is an interpretation that deserves testing rather than repeating. This guide walks through what Resolution 340 actually establishes, how lawful deductions fit the threshold, the common scenarios with worked examples, and how to record deductions so a legitimate one never reads as an underpayment.

Informational only — not legal advice. This article is point-in-time (last updated October 2026). The specific deduction limits and article references in UAE labour law must be confirmed with a qualified legal reviewer before you rely on them; this article deliberately avoids stating limits that have not been verified. Verify the current position with MOHRE (mohre.gov.ae) or a qualified adviser before acting.

What Resolution 340 actually says about 85%

The 85% threshold is not a single test — it operates at two levels, and keeping them separate is the key to understanding deductions.

• The company-level test. An establishment is treated as compliant for the cycle if it transfers at least 85% of the total wages due by the due date. This is the headline number most coverage quotes.
• The worker-level test. For an individual employee, the worker is treated as paid where any shortfall between the full registered wage and the amount transferred arises from a lawful deduction under the Labour Law. The employee does not lose the balance — they keep the right to claim anything properly owed.

Read together, the two tests say something more precise than "you can withhold 15%." They say: pay what is due, and where you pay less than the full registered figure, the gap must be explained by a lawful, documented deduction — not by employer discretion, a cash-flow decision, or an informal arrangement.

Why "a 15% cap on deductions" is a reading, not a rule

Because the compliance threshold is 85%, some commentators have concluded that the rule "effectively caps deductions at 15% of wages." It is easy to see how that inference is drawn — but it conflates two different things: the WPS monitoring threshold (how much must move through the system to avoid a compliance flag) and the Labour Law's limits on what may be deducted from wages (how much, and for what reasons, an employer may lawfully withhold).

Those limits are set by the Labour Law's own deduction provisions, which cap certain deductions and restrict their grounds — and they are the real constraint on a loan recovery or a fine, not the 85% WPS figure. Treating the 85% threshold as the deduction limit is one commentator's shorthand; the actual ceiling on a specific deduction comes from the labour legislation, and the exact percentages and article numbers should be confirmed with your legal reviewer before you build a policy around them. This article does not assert a specific percentage cap as law, precisely because that figure is the point most often stated without verification.

The practical takeaway: a deduction is safe when it is lawful and documented, not merely when it keeps the transfer above 85%.

When a deduction becomes a "delayed wage"

The risk is not deductions themselves — it is deductions that are not lawful, not authorised, or not recorded. When monitoring sees a transferred amount below the registered wage and there is no lawful deduction on record to explain it, the gap can be read as underpayment or a delayed wage, which is exactly the outcome the 85% framework is meant to police. The same deduction can be entirely legitimate and still cause a flag if the paperwork does not travel with it.

Three things turn a legitimate deduction into a problem:

• No written authorisation from the employee for a deduction that requires consent.
• No payslip line item — the deduction is taken but not shown, so the net figure is unexplained.
• A mismatch between the payslip and the SIF — the amount transferred through WPS does not reconcile with the documented deductions, so the system sees a shortfall it cannot account for.

The common scenarios, with worked examples

The figures below are illustrative, using a registered monthly wage of AED 5,000 to show the mechanics and the 85% test. They are not legal limits — the lawful maximum for each deduction type must be confirmed with your reviewer.

The 85% line for this employee: 85% of AED 5,000 = AED 4,250. So a transfer at or above AED 4,250, with the shortfall explained by a lawful deduction, satisfies the worker-level test.

Scenario 1 — Salary advance recovery

The employee took a AED 1,000 advance last month, recovered this month by agreement.

• Registered wage: AED 5,000
• Lawful, authorised deduction: AED 1,000
• Net transferred: AED 4,000

This falls below the AED 4,250 line. It can still be compliant if the deduction is lawful and documented (a signed repayment agreement, a payslip line item), because the shortfall arises from a lawful deduction and the employee consented. But it sits below 85%, so the documentation is doing the work — without it, this reads as an underpayment. The safer practice for a large advance is to spread recovery over several months so each month's deduction is smaller and the transfer stays above the line.

Scenario 2 — Personal loan instalment

A company-facilitated loan is repaid at AED 600 per month.

• Net transferred: AED 5,000 − 600 = AED 4,400

This stays above the AED 4,250 line and, with a signed loan agreement and a payslip entry, is straightforward. The instalment amount should match exactly across the loan schedule, the payslip, and the SIF.

Scenario 3 — Unpaid-leave deduction

The employee took two days of unpaid leave in a 30-day month.

• Daily wage: AED 5,000 ÷ 30 = AED 166.67
• Deduction: 2 × AED 166.67 = AED 333.34
• Net transferred: AED 4,666.66

This is not a "deduction" in the disciplinary sense — it reflects days not worked — but it must still appear correctly, with the unpaid-leave days recorded and the SIF carrying the right unpaid-leave code so the lower figure is read as intended rather than as a shortfall.

Scenario 4 — Recovery of company property damage / a fine

A deduction for damaged equipment or a disciplinary fine is the most sensitive category, because the Labour Law restricts both the grounds and the amount, and typically requires process (investigation, notice, limits per month).

• Suppose a damage recovery of AED 400 is applied: net transferred = AED 4,600, above the line.

Even though the net clears 85% comfortably, this deduction carries the highest risk if the grounds or process are wrong. Confirm with your reviewer what the Labour Law permits for fines and damage recovery — the amount, the required process, and any monthly cap — before applying one. Clearing the 85% threshold does not make an unlawful deduction lawful.

How to record a deduction so it never reads as an underpayment

The discipline is the same for every scenario:

1. Written authorisation on file where the deduction type requires consent (advances, loans; fines and damage recovery follow their own statutory process).
2. A clear payslip line item naming the deduction and amount — never a silently reduced net.
3. SIF alignment — the amount transferred through WPS reconciles exactly with the payslip's gross, deductions, and net, so monitoring sees a complete, explained figure.
4. A documented reason and schedule for anything recovered over time, with the per-month amount matching across every record.

When those four line up, a deduction is self-explaining: the system sees the lower transfer, finds the lawful deduction behind it, and the worker-level test is satisfied. For the payslip structure this rests on — gross, basic, allowances, and how deductions should appear — see our UAE payslips and salary structure guide; for the full WPS framework the 85% test sits inside, see our UAE WPS compliance guide.

The bottom line

The 85% rule is not a licence to withhold 15%, and it is not primarily a deduction limit at all — it is a monitoring threshold that assumes any shortfall is backed by a lawful, documented deduction. Keep deductions lawful, authorised, shown on the payslip, and reconciled to the SIF, and the threshold takes care of itself. Confirm the specific legal limits for each deduction type with your reviewer rather than inferring them from the 85% figure.

Most deduction problems come down to the payslip and the SIF being built separately, so a legitimate recovery shows up as an unexplained gap. When payslips and the WPS file generate from the same payroll run, every deduction carries its authorisation and its line item into the file, and the 85% test is answered before the question is ever asked.

---

Keep every deduction documented and reconciled

RadixHR keeps payslips and SIF files matched line-for-line, so every advance, loan instalment, and lawful deduction is documented, reconciled, and WPS-ready.

Book a demo →

---

This article is for general information only and does not constitute legal or financial advice. The 85% threshold and WPS rules are set by MOHRE under Resolution 340 of 2026; the limits on and grounds for wage deductions are set by UAE labour legislation and must be confirmed with a qualified adviser. DIFC and ADGM operate separate frameworks. Verify current requirements before acting.