WPS payroll in ERPNext: how the salary file is produced

Qatar's Wage Protection System requires salaries to reach employees through the banking channel on a fixed schedule, with a salary information file submitted to the bank in a prescribed layout.

Almost every employer we meet produces that file by hand. The HR system holds the employee records, and a spreadsheet — rebuilt monthly, checked by eye — produces the file the bank actually accepts.

What the file has to contain

The header carries employer and payer identifiers. Then a row per employee: QID, visa ID, bank short name, account number or IBAN, salary frequency, number of working days, and the breakdown of basic pay, allowances and deductions.

None of that is complicated. What makes it risky is that it is retyped every month. A transposed digit in an IBAN is a salary that does not arrive, and the employee finds out before you do.

How it works when the system produces it

Salary structures are configured once against your actual pay components. Attendance — from biometric readers, access control, or mobile check-in for site staff — feeds the payroll period. Payroll runs, HR reviews it, and the WPS file exports in the correct layout.

Payroll then posts straight to the ledger, because HR and accounts are the same installation rather than two systems reconciled monthly.

Before you go live

Run a parallel payroll against a period you have already paid, and compare the output line by line against what the bank actually received. Only when those match should you cut over. We do this on every payroll implementation, and it is the check that makes go-live uneventful.