Payroll & WPS
How many spreadsheets does it take to run your payroll?
If the answer is more than zero, your payroll has outgrown its tools. Gross to net, WPS files and end of service, in every market you pay in.
Trusted by
A rejected wage file stops more than payroll
Every file is validated against the country format before you submit, and the employees who would cause a rejection are named before it leaves the building.
- Salary files checked against the MOHRE format before submission.
- Employees whose records would bounce are flagged, not buried.
- Qatar and Bahrain files produced the same way, with the same checks.
The number nobody wants to find at exit
End of service gratuity accrues from day one against the record, so the liability on your balance sheet is the number an employee actually leaves with.
- Gratuity accrued monthly, not reconstructed at exit.
- Sensitivity analysis against IAS 19 assumptions.
- Bahraini and expatriate entitlements calculated separately.
The errors that matter are invisible until payday
Every run is checked against the last one and against each country's rules, so an exception surfaces while there is still time to fix it.
- Variance against the previous cycle, line by line.
- Country rules applied per entity, not per spreadsheet.
- Nothing pays until a person presses approve.
Everything inside Payroll & WPS
Twelve capabilities in three groups, all reading from the same employee record.
Running the cycle
Gross to Net
Every entity, every country, one calculation engine.
Off Cycle Runs
Corrections and one off payments without a rerun.
Multi Currency
Pay in the currency the entity actually runs in.
Payslips
Published to the employee hub, in Arabic or English.
Paying and filing
WPS Files
Generated, validated and ready to submit.
Bank Files
Direct deposit files in each bank's own format.
Social Security
GOSI, SIO and the equivalent in each market.
Payroll Journals
Posted to your ledger in your own chart of accounts.
Liabilities and evidence
End of Service
Gratuity accrued from day one, not at exit.
Loans & Advances
Deducted on schedule, tracked against the record.
Payroll Reports
Cost to company, variance and journal exports.
Audit Trail
Who changed what, when, and what it was before.
Where it runs
Wolke runs payroll in 36 countries. These four are the ones with a filing regime that will reject you if you get it wrong.
United Arab Emirates
Salary files validated against the MOHRE format before you submit, with the employees who would cause a rejection flagged first.
Saudi Arabia
Contributions calculated per employee, Mudad and Qiwa filings produced from the same run, and Nitaqat banding tracked as headcount moves.
Qatar
WPS through the Ministry of Labour, with end of service gratuity accrued from day one rather than reconstructed at exit.
Bahrain
LMRA and SIO handled, with Bahraini and expatriate gratuity calculated separately on their own rules.
The other 32 markets run on the same engine. Ask us about yours.
Payroll compliance questions, answered
Yes. Wolke generates the UAE Wage Protection System salary information file from each pay run, validates it against the MOHRE format before you submit, and flags employees whose records would cause a rejection. Qatar and Bahrain WPS files are produced the same way.
Yes. GOSI contributions are calculated per employee against current bandings, and Mudad and Qiwa filings are produced from the same run. Nitaqat banding is tracked as headcount changes, so you see the effect before it becomes a problem.
It accrues monthly against the employee record from day one, on the rules of the market the employee is employed in. That means the liability on your balance sheet is the number the employee actually leaves with, and you can run a sensitivity analysis against your IAS 19 assumptions rather than guessing.
Yes. One cycle can cover every entity and every market, each on its own rules and its own calendar, all reading from the same employee record. You approve per entity or across the group.