10 October 2026 · Evidence
Build a WPS File That Can Be Checked
The Official Platform of the UAE Government says WPS enables MoHRE to maintain wage-payment data and monitor whether private-sector employers pay wages in full and on time. Keep the contract, salary register, WPS submission result, bank proof, correction trail and employee changes together so the payment record can be explained.
Exiloz Management & Tax Consultant · Dubai-based FTA-focused advisory · VAT, corporate tax & accounting
An accepted WPS screen is only one record
A WPS acceptance result answers one question: the system accepted a submission. It does not show, by itself, what the employer approved, which contract terms produced the amount or why a correction was made. Article 22 of Federal Decree-Law No. 33 of 2021 places the wage payment duty on the employer. The evidence file must therefore explain the payment from source agreement to actual movement of funds.
Build the folder around that trail. Keep the employment contract, approved amendment, salary register, WPS file, acceptance or rejection result, bank proof and correction approval together. A MoHRE WPS statement can help check the establishment's payment position, but it supports the underlying records rather than replacing them. Use the same period and employee reference throughout the folder.
Worked example: an approved register contains AED 72,500, including an approved unpaid-leave adjustment of AED 2,500. The amount sent is AED 72,500 minus AED 2,500, or AED 70,000. Bank proof should show AED 70,000, and the folder should contain the leave approval that explains the difference. The arithmetic is a file control, not a legal threshold.
Give every payroll question its own source
A reviewer asks what was agreed, calculated, submitted, paid and changed. Do not answer all five with one export. The contract proves the agreed wage, the salary register proves the calculation, the WPS result proves submission status and the bank record proves the movement of funds. Keeping those roles separate stops a status label from carrying more weight than the document behind it.
The mistake we see most is treating a green WPS status as proof that the whole payroll file is complete. It is not. A status can coexist with a wrong employee line, an unexplained adjustment or missing bank evidence. The reviewer should sample one employee from contract to payment, then expand the test when that sample exposes a broken link.
A correction needs its own trail. Keep the original line, reason for the error, authorising document, effective date, revised file and final payment result. If a worker's amount differs from the register, start with the contract and approved change record. Do not edit an accepted file simply to make the spreadsheet balance.
| Question | Source record | Keep with it |
|---|---|---|
| What was agreed? | Employment contract and amendment | Current signed record |
| What was calculated? | Approved salary register | Locked register and change log |
| What was submitted? | WPS file and result | Original file and status |
| What was paid? | Bank or financial-institution result | Debit or transfer proof |
| Why did it change? | Approval and effective-date record | Original and revised trail |
Keep the first version visible
The most useful evidence is often the record showing that an error was found and controlled. Save the original WPS submission before making a correction. Mark the employee line, source of the error and approving person. Then save the revised file and its result under the same payroll period. Replacing the original with a corrected copy removes the history a reviewer needs.
The supporting document depends on the cause. A new joiner needs the employment contract and joining record. A salary change needs the approved amendment and effective date. An unpaid-leave adjustment needs the leave approval. A rejected transfer needs the financial-institution message and final payment proof. Name the object in the exception record. A vague note cannot carry the explanation.
When a correction changes the total, show the arithmetic beside the approval. Write the old amount, approved adjustment and new amount rather than saving only the final spreadsheet. This lets an owner approve the change and lets a later reviewer reproduce it. The calculation belongs in the exception trail, not only in the final register.
Build a file another person can check
A monthly folder should open with the payroll period, establishment and approved owner. Put source documents first, calculation next, WPS submission after that and bank result last. Keep rejected files and corrections beside the final result, not in an email account that only one person can access. The folder should make review possible when the preparer is unavailable.
Use the same employee reference in the contract, register, WPS line, correction record and bank proof where the systems allow it. If identifiers differ, add a short cross-reference. A reviewer should not have to infer that two labels describe the same worker. That small control removes a common reason for reopening an otherwise closed payroll period.
If a query arrives today, export the current MoHRE statement, open the relevant period and trace one employee from contract to payment. That sample shows whether the folder is usable. Fix the missing link before answering every question at once. A labelled gap is easier to close than an unspoken assumption.
The law sets the duty, not a folder template
Article 22 of Federal Decree-Law No. 33 of 2021 sets the employer's wage payment duty, and Article 16 of Cabinet Resolution No. 1 of 2022 requires establishments registered with the Ministry to pay through WPS or another approved system. The public UAE Government and MoHRE material reviewed does not state one universal folder structure, naming convention or evidence index for every establishment. That practical point remains open. The employer should set its own record rule, name the owner and keep that rule with the payroll period.
We recommend retaining the original submission, bank result and every approved correction together for each payroll period. That arrangement answers the payment question without asking the preparer to reconstruct the month. It also keeps an exception visible rather than allowing a later export to hide it. The recommendation is a record control, not a claim that MoHRE issued this folder design. It gives the reviewer a fixed place to inspect the source used.
Your action is straightforward. Confirm the contract, calculation, submission, payment and reason for every change. If one link is missing, label the gap and obtain the document before closing the period. The file is ready when another person can follow the payment without a private explanation from the preparer.
Related guides
Frequently Asked Questions
For building a payroll file that can be explained.
What belongs in a WPS evidence file?
The Official Platform of the UAE Government describes WPS as a way for MoHRE to monitor wage payments. Keep the contract, salary register, WPS result, bank proof, approved deductions, correction trail and employee changes together so the payment can be traced.
Why keep the bank proof after WPS accepts the file?
The UAE Government says WPS records wage payments and monitors compliance with paying in full and on time. Bank proof connects the accepted submission to the actual debit, so a payroll reviewer can test both records rather than relying on a screen status.
How should payroll corrections be recorded?
MoHRE is the authority for WPS payment compliance. Keep the original issue, the approved correction, the effective date, the resubmission result and the final bank proof together. That record lets the employer explain why the amount changed.
Can Exiloz build the evidence file?
Exiloz can organise the salary register, WPS result, bank proof and approved changes into a monthly handover, then list missing or inconsistent records. The employer keeps responsibility for approving the payroll and retaining its official records.
Can your payroll file be checked?
Exiloz organises your payroll evidence into a monthly handover and lists the missing or inconsistent records before approval.