Payroll data that reaches every Saudi platform in the right shape

A Saudi employer's payroll is not one task. Salaries move through the banking system under the wage protection arrangement. Social insurance contributions go through GOSI. Employment contracts and labor records live on Qiwa. Mudad supports wage protection and contract documentation workflows. Each has its own screens, its own data fields and its own rules, and each is owned by a different body.

Most trouble starts before any platform is touched. The employee record is weak: an old IBAN, a missing identity number, a salary split that differs between HR and finance. The most valuable first step is a clean employee master record with agreed fields and a named owner. Everything else is prepared from it.

We are specific about what we build. This is a custom integration and HR workflow service. It is not a packaged HRMS, and it does not replace your accounting system. If you already run an HR tool, we connect to it. If you run spreadsheets, we build the thin application that replaces them. Access to GOSI, Qiwa, Mudad and your bank is granted by each of them to your company. We do not hold it for you.

The design follows the data, not the platform names. First we map where each field originates: HR for contract and title, attendance for days worked, finance for allowances and deductions. Then we define the rules that turn those inputs into pay components, contribution bases and the file or record each platform needs.

Platforms offer different routes. Some accept uploaded files in a defined layout. Others expose services to registered organizations. Some are used through the web portal by a named user. We check what each currently offers your company type, build against the published documentation, and say plainly when a step stays manual. A good design makes the manual step fast and verified rather than pretending it is automated.

Every pay run goes through the same sequence: collect inputs, validate, calculate, review, generate outputs, submit, reconcile. A validation step catches the usual causes of rejection before submission: a mismatched identity number, an invalid bank account, a period overlap. Errors land in a queue with a clear owner. Indicative timelines are four to twelve weeks, driven by the number of source systems and how clean the data is.

Payroll data is among the most sensitive a company holds. Under the Personal Data Protection Law it is personal data, so access is role-based, exports are logged and retention is defined. Pay data should be visible to the few people who need it, and every change should leave a record of who made it and why.

Segregation of duties matters as much as encryption. The person who prepares a pay run should not be the one who approves it. We build approval steps into the workflow and make them configurable, so a small company can run with two roles and a larger one with several. Where your policy requires it, hosting can be inside the Kingdom.

Rules and platforms change. A new field, a changed file layout or a revised process can break an integration overnight. We keep each platform behind its own adapter, so a change is made in one place and tested before the next pay run. We also keep a calendar of recurring deadlines on your side, so a missed registration renewal does not surprise you. After launch we monitor runs and keep the integration current.