Payroll & WPS — GCC payroll software with WPS

Payroll built for the Gulf, not adapted to it: statutory rules ship as versioned country packs (Saudi Arabia, UAE, Kuwait, Qatar, Bahrain, Oman and more), salary formulas run in a sandboxed rules engine, and every run posts to accounting automatically.

Step-by-step guides for every role

What you get

• UAE WPS SIF and Saudi Mudad bank files generated natively
• GOSI, GPSSA and end-of-service (EOSB) computed by versioned country packs
• Sandboxed salary-rule engine — customise formulas without code deployments
• AI anomaly detection: salary spikes, zero deductions, duplicate IBANs flagged before approval
• Append-only run lifecycle with immutable payslips and retro runs as deltas
• Automatic balanced journal posting to the general ledger
• Per-branch country packs — run Saudi and UAE payroll in one company

What each role gets

• Payroll manager — Drives the full monthly cycle — opening the period, computing, walking anomaly flags like salary spikes and duplicate IBANs, approving, generating WPS or Mudad bank files, and posting the balanced entry to the ledger. Spins up retro runs as their own append-only revision when a correction is needed, computes EOSB at termination per the country pack, and runs a live what-if simulator to preview rate or rule changes before they go live.
• Accountant — Receives payroll's journal entries automatically over an idempotent, event-driven pipeline — no manual re-keying, no risk of duplicates. Runs the period-end reconciliation report line-by-line against the GL, manages fiscal-period open/lock/close so payroll can post cleanly, and is the only role that can reopen a period for a late correction.
• HR manager — Feeds payroll everything it computes from — effective-dated compensation events for raises, bonuses and deductions, employee banking setup, and the offboarding wizard that fires EOSB straight into a final-settlement run. A back-dated raise triggers an automatic retro run and the termination reason drives the exact EOSB formula, all without HR ever touching a payslip directly.
• Employee — Views every payslip once it's posted, locked to the exact statutory pack version used at the time so past pay never silently changes when rates update later. Downloads bank- and embassy-ready PDFs, tracks year-to-date totals and EOSB accrual, keeps banking details current, and can raise a correction request that triggers an investigated retro run — never anyone else's numbers.
• Tenant admin — Builds the rails the payroll team runs on — installing and version-pinning country packs per branch, writing and testing the sandboxed salary-rule expressions behind every calculation, and gating which bank-file formats are available per country. Owns the feature-flag catalogue (anomaly detection, run-freeze, what-if simulator) and the permission split between payroll manager and specialist roles.

Part of one platform

Payroll & WPS is one of 30+ modules sharing the same login, the same people, the same customers and the same AI copilot — see all modules or how Tarleaks ERP compares to Odoo, ERPNext and Zoho.