How does SupaJack Construct correct a payroll that was already paid?
It never edits a paid run, because the WPS transfer has already left the bank. A correction records the original slip, works out the difference, and settles it as arrears owed to the employee or an overpayment to recover, through an off-cycle payment. Database constraints stop the same correction being settled twice.
On this page
Derived from what was recorded
A refund of an unpaid-leave deduction uses the per-day rate actually deducted on that payslip, not today's salary, so the employee gets back exactly what was taken.
Recovery limits
Recovering an overpayment from salary is subject to Article 25 of the labour law, which caps overpayment recovery at 20% of the wage and all deductions together at 50%.
Audit trail
The corrected payroll run is protected from deletion while corrections point to it, so the record of what was paid and what was corrected stays intact.
Related tools and guides
See payroll and WPS, time and attendance, interim payments, finance and VAT, approvals, the construction ERP overview, the buyer's guide and the answer on scheduling, BIM and safety.
Worked example
In March an employee was wrongly charged 3 unpaid days at AED 120 a day. In April a correction is raised against the March slip. The system settles AED 360 as arrears through an off-cycle payment, and the March run is unchanged.
Questions people ask
Is the original payslip changed?
No.
Can a correction be paid twice?
No. A constraint ties each correction to one settling payment.
Is overpayment recovery limited?
Yes, by Article 25 of the labour law.