Payroll with
control & clarity.

Detailed explanation

Payroll combines many moving inputs: joiners, leavers, attendance, unpaid leave, salary revisions, allowances, bonuses, deductions, bank changes, retro adjustments and final settlements. Manual processing can work at small scale, but the control environment becomes more important as volume and complexity grow.

What HR / Payroll should do

• Separate input, calculation, review and approval responsibilities where practical.
• Lock source data after cut-off and document late changes.
• Use reconciliation against the prior month and approved HR master data.
• Protect formulas and maintain version control.

Practical example

A salary revision is received by email after the payroll file has already been updated. Without a controlled change log, one version may include the revision while another does not. A formal exception register makes the final decision traceable.

Related knowledge

Detailed explanation

A policy may appear to be an HR-only change but can create new payroll calculations, data requirements, cut-offs or WPS implications. Payroll should understand the operational rule before the first affected cycle.

What HR / Payroll should do

• Perform a payroll-impact review before policy launch.
• Define the effective date and treatment of transition cases.
• Test calculations using sample employees.
• Communicate required input changes to managers and HR operations.

Practical example

A new unpaid-leave rule is announced mid-month. Payroll needs to know the daily-rate method, effective date, approval source and how corrections will be handled before the cut-off.

Related knowledge

Detailed explanation

Payroll questions often arise months after a payment. A good archive allows the team to reconstruct what changed, who approved it, how it was calculated and what was paid without depending on personal memory.

What HR / Payroll should do

• Archive the final approved payroll version.
• Retain supporting approvals for one-off adjustments.
• Keep bank/WPS confirmation and rejected-payment follow-up.
• Use consistent file naming and restricted access.

Practical example

An employee asks why a deduction occurred six months ago. A structured archive should allow payroll to retrieve the approval, calculation and payslip evidence quickly.

Related knowledge

Detailed explanation

Off-cycle payments can bypass the normal reconciliation and approval rhythm. That makes clear ownership, coding, approval and later reconciliation especially important.

What HR / Payroll should do

• Define which cases qualify for off-cycle payment.
• Require documented approval before processing.
• Record whether the amount must be recovered or reflected in the next payroll.
• Reconcile the off-cycle amount with the monthly payroll record.

Practical example

An urgent relocation payment is made before payroll. If it is not logged correctly, the same allowance may be paid again in the monthly run.

Related knowledge

Detailed explanation

Article 25 lists situations in which deductions may be made and places conditions or limits on them. A company rule should not be used to override the statutory framework. Payroll should identify the deduction reason, evidence and applicable cap before processing.

What HR / Payroll should do

• Identify the legal/policy basis for every deduction code.
• Keep employee authorization where required.
• Review individual and aggregate deduction limits.
• Escalate unusual deductions instead of processing them automatically.

Practical example

If several recoveries apply in the same month, payroll should not simply deduct every amount requested. The aggregate statutory limit and the specific conditions for each deduction must be checked.

Related knowledge

Detailed explanation

Payroll files can contain salary, allowances, bank details, identification data and deductions. Access should be based on job need, and exports or email attachments should be controlled carefully.

What HR / Payroll should do

• Use role-based access where systems support it.
• Avoid broad distribution lists for payroll files.
• Password-protect or use approved secure channels for sensitive exports.
• Remove unnecessary personal data from working reports.

Practical example

A payroll variance file sent to a large email group may reveal salaries to people who do not need them. The control should begin with limiting the data and recipients.

Related knowledge

Detailed explanation

Payroll validation is stronger when it is risk-based. Instead of checking only the grand total, review employee-level movements and unusual patterns such as zero pay, large net-pay changes, new bank accounts or unexpected deductions.

What HR / Payroll should do

• Compare current and prior-cycle gross and net pay.
• Review joiners, exits and employees with large variances.
• Validate bank changes independently.
• Check payroll totals against approved funding/payment values.

Practical example

An employee's net pay falls sharply because an unpaid-leave entry was duplicated. A variance threshold can flag the employee before the payroll is released.

Related knowledge

Detailed explanation

A cut-off is a control point, not just an administrative deadline. Stakeholders should know what must be submitted, who approves it, what happens to late items and who can authorize an exception.

What HR / Payroll should do

• Publish a recurring payroll calendar.
• Send targeted reminders before cut-off.
• Use an exception log after the deadline.
• Analyse recurring late submitters and root causes.

Practical example

If a manager submits an allowance after cut-off, payroll should record whether it is approved as an exception or moved to the next cycle rather than quietly editing the final file.

Related knowledge

Detailed explanation

Under Article 51, an eligible foreign full-time worker completing at least one year of continuous service receives gratuity based on the last basic wage: 21 days per year for the first five years and 30 days per year thereafter. Unpaid absence is excluded and the statutory gratuity is capped at two years' wage.

What HR / Payroll should do

• Confirm whether the employee is under the standard gratuity system or another applicable scheme.
• Use the last basic wage for the statutory calculation.
• Exclude unpaid absence from eligible service.
• Apply proportional entitlement for eligible part-years and the statutory cap.

Practical example

An employee with seven years of eligible service should not have all seven years calculated at 30 days. The first five years use the 21-day rate and the remaining eligible service uses 30 days.

Related knowledge

Detailed explanation

Article 53 requires the employer to pay the worker's wages and other entitlements within 14 days from the end of the contract. HR and payroll therefore need timely inputs from managers, IT, administration and other stakeholders.

What HR / Payroll should do

• Trigger final-settlement data collection as soon as the exit is confirmed.
• Validate last working day, leave, unpaid absence and salary basis.
• Separate lawful recoveries from unsupported deductions.
• Maintain final approval and payment evidence.

Practical example

If clearance begins only after the last working day, the organisation may lose valuable time. Starting the checklist earlier helps payroll meet the statutory timeline.

Related knowledge