Most payroll errors are visible the day before payday, if anyone looks. A doubled overtime entry. A housing allowance that silently dropped to zero. A leaver who is still in the run. A new joiner paid a full month for twelve days of work. None of these are hard to spot. They are simply not spotted, because the only check most teams run is “does the total look about right?”.
In the UAE that matters more than elsewhere, because once the WPS file is submitted and the bank moves the money, a mistake is harder to correct and quicker to become a dispute. This guide explains what a salary reconciliation should compare, how to handle joiners, leavers and bank changes, and shows a worked month-on-month example you can copy.
What is salary reconciliation?
Salary reconciliation is the check you run on a completed payroll before it is paid, comparing this month's run to last month's line by line: headcount, gross and net by department, every salary component per employee, joiners, leavers and payment-method changes. Its purpose is to explain every movement and catch errors before money leaves the bank.
The key word is before. A reconciliation done after payday is an audit. A reconciliation done before payday is a control.
Why reconcile before payday, not after?
Because in the UAE the WPS file is generated from the final payroll and submitted to the bank. Once salaries are processed, correcting an error may require recovery, an additional payment or an adjustment in a later payroll period, depending on the processing stage and the bank or exchange house, and it often creates an employee dispute. A pre-payday reconciliation is the last point where a mistake costs nothing.
Three things change once payroll is released:
The money has moved. Depending on the processing stage, an overpayment may need to be recovered and an underpayment may need an additional payment or a later-period adjustment.
The WPS record exists. Depending on whether the file has been generated, uploaded, accepted or funded, a correction may mean an adjustment in a later payroll period rather than a clean run.
Trust is spent. A worker who receives the wrong amount remembers it longer than a worker who was paid correctly.
Reconciliation should be completed after payroll processing and before the run is locked and the WPS/SIF file is generated. It is one of the payroll controls every UAE finance manager should demand.
What should a salary reconciliation compare?
A complete reconciliation compares this month to last month at three levels: the company and department totals (gross, net, headcount), each employee's individual salary components (basic, allowances, overtime, deductions), and the HR events that should explain any movement (joiners, leavers, unpaid absence, salary changes, payment-method changes). Anything that moved without a matching event is a query.
The checklist, top down:
| Level | Compare | A movement is fine when |
|---|---|---|
| Company | Total gross, total net, headcount | Explained by the department lines below |
| Department | Gross, net, headcount, deltas vs last month | Explained by joiners, leavers or documented changes |
| Employee | Every component side by side with last month | There is a salary change, absence, overtime record or approved adjustment behind it |
| Payment | Payment method and bank details vs last month | The change was requested and the new account is verified |
| Joiners | Date of joining, prorated days, first-month components | Days match the joining date |
| Leavers | Date of leaving, last payroll month, final settlement | The leaver is in this run only if they were employed in it |
| Totals | Earnings + additions − deductions = net | The net foots to the amount going into the WPS file |
The last row is easy to skip and is the one that catches formula errors: if earnings minus deductions do not equal the net you are about to pay, something in the run is wrong even if every individual line looks plausible.
Worked example: a month-on-month reconciliation
Start with the department view. Where headcount and net move together, the change is usually explained by joiners or leavers. Where net moves but headcount does not, look inside the department at individual components. The example below shows one clean department, two explained movements and one that needs a query.
Department summary (illustrative figures, AED):
| Department | Net last month | Net this month | Change | Headcount | Explanation |
|---|---|---|---|---|---|
| Operations | 210,000 | 231,500 | +21,500 (+10.2%) | 42 → 45 | 3 joiners on prorated days, plus overtime. Explained. |
| Admin | 84,000 | 84,000 | 0 | 12 → 12 | No movement. Clean. |
| Finance | 61,000 | 52,400 | −8,600 (−14.1%) | 8 → 7 | 1 leaver, left on the 12th, prorated. Explained; check the final settlement is handled separately. |
| Sales | 95,000 | 107,250 | +12,250 (+12.9%) | 10 → 10 | Same headcount, net up 12.9%. Query. |
Sales is the one to open up. Same ten people, twelve thousand more. That is either commission that is genuinely due or an error, and the department total cannot tell you which. The employee listing can.
Employee listing, Sales department, components that moved:
| Employee | Component | Last month | This month | Effect on net pay | Finding |
|---|---|---|---|---|---|
| S-1042 | Overtime | 850 | 1,700 | +850 | Exactly double. Likely a duplicated entry. Query before pay. |
| S-1088 | Housing allowance | 3,000 | 0 | −3,000 | Allowance dropped with no salary change on file. Error, restore. |
| S-1091 | Commission | 0 | 15,000 | +15,000 | Approved commission schedule on file. Explained. |
| S-1101 | Payment method | Bank A | Bank B | Changed | New IBAN. Verify before the SIF is built. |
| S-1115 | Absent-day deduction | 0 | 600 | −600 | Three absent days. Matches attendance records. Explained. |
Net effect of the queries: an overpayment of 850 and an underpayment of 3,000 caught before payday, and a bank change verified before it reached the WPS file. The 15,000 commission was real. Without the employee-level view, the department total of +12,250 looked roughly like “commission month” and all three problems would have gone through. The four amounts above (+850, −3,000, +15,000 and −600) sum exactly to that +12,250; the bank change carries no amount.
How do you handle joiners and leavers in the reconciliation?
Identify joiners by their date of joining and leavers by their date of leaving, not by comparing which names appear in each month. Joiners should be paid for days from the joining date only. Leavers should appear only in the months they were employed, with a clear last payroll month, and their final settlement handled as a separate calculation.
Two mistakes are common here:
Set-difference joiners and leavers. Comparing this month's name list to last month's produces false joiners (someone returning from unpaid leave) and false leavers (someone on a full month of approved leave). Use the actual joining and leaving dates.
Leavers that linger. A person who left on the 12th of last month should not be in this month's run at all. A clear "last payroll month" on the leaver record prevents a second payment, and the reconciliation should show prior-month leavers as leavers, not as existing staff who happen to have zero pay.
For how the leaver's end-of-service is provisioned and settled, see EOSB accrual for finance teams.
Common salary reconciliation mistakes
The usual failures are reconciling after the WPS file has gone, comparing totals only and never opening the employee lines, identifying joiners and leavers by name-matching instead of dates, ignoring payment-method and bank changes, and reconciling against a run that can still be edited, so the numbers checked are not the numbers paid.
Reconciling after the fact. The check happens once the money has moved, which makes it a report, not a control.
Totals only. The department total hides a doubled overtime entry and a dropped allowance that cancel each other out.
Name-matching joiners and leavers. Produces noise and misses real cases.
Skipping the bank check. A changed IBAN is the single most consequential line in the run and the easiest to miss.
No locked baseline. If the run can still be edited after the reconciliation, the reconciled figures and the paid figures can differ.
How HRX360 does it: the Salary Review workbook
HRX360's Salary Review is a pre-lock check that generates a multi-sheet Excel workbook comparing this month's run to last month's: a summary with department deltas and joiners and leavers, an employee listing with every component side by side and drift highlighted, one sheet per payment method, and dedicated joiner and leaver sheets. Run it, resolve the queries, then lock and generate the WPS file.
What is in the workbook:
Summary sheet: total payout this month versus last, gross, net and headcount deltas per department, a breakdown by payment method, and new joiners and leavers for the month.
Employee listing: current and previous month side by side for every employee, ordered by employee code, with per-component drift highlighted, payment-method changes flagged, bank columns on every sheet, days worked, absent days and the absent-day deduction shown, and a Total Earnings + Additions − Deductions = Net bridge so each row foots.
One sheet per payment method: so the bank-transfer population and any cash or cheque population reconcile separately.
New Joiners and Leavers sheets: joiners identified by date of joining with a prorata label, leavers by their real leaving date with a Last Payroll Date column; prior-month leavers read as leavers, not as existing staff.
Footing summary and bracketed deductions: so the workbook totals tie to the run that will produce the SIF.
Then the sequence that keeps the reconciled figures and the paid figures identical: review the workbook, fix the queries, lock the run, and generate the WPS-ready SIF file from that locked run. Once the reviewed run is locked, the checked payroll figures cannot be changed without following the controlled unlock or reprocessing process. The export is named by company, month and year, ready for the month-end pack alongside the payroll journal voucher.
Salary Review is part of HRX360's payroll software, within HR software built for the UAE. If the SIF is rejected after all that, see why SIF files get rejected.
Reconcile before you pay, not after
HRX360's Salary Review compares every pay run to last month, by department, by employee and by payment method, and flags what moved, so you lock a run you have already checked and generate the WPS file from it. Full UAE payroll with Salary Review, WPS/SIF and gratuity is on the Professional plan, from AED 10 per employee per month, billed annually.
Frequently asked questions
What is salary reconciliation in payroll?
It is the pre-payment check that compares a completed payroll run to the previous month at company, department and employee level, so every movement is explained by a real event (a joiner, a leaver, absence, a salary change or an approved adjustment) before any money is paid.
When should payroll be reconciled?
After the run is complete and before it is locked and released. In the UAE that means before the WPS SIF file is generated, because once salaries are processed, correcting an error may require recovery, an additional payment or an adjustment in a later payroll period.
What should a payroll reconciliation checklist include?
Headcount and net by department versus last month, every salary component per employee side by side, joiners by date of joining with prorated days, leavers by date of leaving with a last payroll month, payment-method and bank changes, and a totals check that earnings minus deductions equals the net being paid.
How do you identify joiners and leavers correctly?
By date of joining and date of leaving, not by comparing name lists between months. Name-matching creates false joiners and leavers whenever someone is on a full month of leave, and misses cases where a leaver is still in the run.
Why do payment-method changes matter in reconciliation?
Because a changed bank account is the most consequential single line in the run: if the new IBAN is incorrect or unverified, the payment may fail or be routed incorrectly. Every payment-method change should be confirmed before the SIF is built.
Does HRX360 reconcile payroll automatically?
HRX360's Salary Review generates the full month-on-month workbook (summary, employee listing with drift highlighting, per-payment-method sheets, joiners and leavers) as a pre-lock step. A person reviews the flagged movements, then locks the run and generates the WPS file from it. Full payroll with Salary Review is on the Professional plan.