Payroll · Bureau
You own the submission. We own the calculation.
Calculation-only payroll for operators with their own entities in MENA. Drop a diff, get a complete payroll pack back, sign off, submit. The engine sits with us; the relationship sits with you.
Drop a monthly diff in the shared drive. We run it through the in-Kingdom engine and return a complete payroll pack — gross-to-net, statutory schedules, WPS file, EOSB liability, variance report. You sign off, you submit, you keep the relationship with the authorities, the bank, and your auditor.
Ownership split
You own. We own.
The line between what stays with you and what we run is explicit. No grey area, no creep.
- Your legal entity and your registrations
- Submission to GOSI, WPS, Mudad, GPSSA, SSC, and the rest
- The bank account and the funding of every cycle
- Sign-off on every payroll run before it leaves your team
- Your relationship with the authorities and your auditor
- Employee queries — payslip, leave, benefits, comp
- The statutory engine and every calculation it runs
- The variance report flagged before sign-off, not after
- WPS / SIF / Mudad-compatible bank file generation
- EOSB liability movement on every run
- The audit trail of every input and every line
- In-Kingdom hosting on Oracle Cloud for Saudi clients
The pack
What we deliver every cycle
One consistent pack, every cycle, every country. Your sign-off and approval flow stays the same regardless of which markets are in this run.
- Gross-to-net register — per employee, per cycle
- Statutory schedules — every country's authority output
- WPS / SIF file — bank-ready format
- EOSB liability movement — accrual deltas, not just balances
- Variance report — flagged anomalies before you sign off
- Payslip data — raw or PDF
- Bank file in your bank's required format
Boundaries
What we don't do
The boundary lines are deliberate. They're how the bureau model stays light-touch.
- We don't submit to GOSI, Mudad, WPS, GPSSA, or any other authority on your behalf. Your registrations stay yours.
- We don't operate your bank account. Bank files arrive in your inbox; you fund the cycle.
- We don't manage employee queries. Payslip questions, leave balance questions, and benefits questions go to your team — not ours.
- We don't reformat your inputs to fit our system. We adapt to your file structure during onboarding.
Infrastructure
Where the calculations actually run
Oracle Cloud. For Saudi clients, in-Kingdom on the Riyadh and Jeddah regions, aligned to Saudi PDPL. For the wider MENA estate, in the regional Oracle data centres — payroll data does not leave the GCC for in-region clients. Database is Google Cloud SQL for Postgres for the platform itself; client payroll data sits on the in-Kingdom Oracle estate.
Compare
Bureau, Managed Payroll, or EOR
Bureau is the lightest-touch model. Managed Payroll covers the full cycle. EOR covers the employment relationship too.
| Dimension | Payroll Bureau | Managed Payroll | EOR |
|---|---|---|---|
| For whom | Operators with their own entities who want calculations and engine, not a system change | Operators who want their full payroll cycle run on a connected platform | Operators hiring people in countries where they don't have an entity |
| Best for scale | Any size — works at five employees and at five thousand-plus in a single country | Best for operators who want one connected workflow across payroll, HRIS, and EOR — not three separate handoffs | Per-employee model — typically one to fifty employees per country before entity setup is the better economics |
| Who is the legal employer? | You (your existing entity) | You (your existing entity) | Global Kinect's local entity |
| Who submits to the authorities? | You — to GOSI, WPS, Mudad, GPSSA, SSC, and the rest | We can, where the operator framework permits — otherwise you | We do — every authority, every cycle |
| Who sponsors the visa? | Not applicable — your entity already does | You | We do |
| Who manages employee queries? | Your team | Configurable — your team or ours | Our team |
| Where data lives | Oracle Cloud, in-Kingdom for Saudi clients | Oracle Cloud, in-Kingdom for Saudi clients | Oracle Cloud, in-Kingdom for Saudi clients |
| Commitment shape | Calculation-only — light touch | Full platform engagement | Full employment relationship |
| What you submit to us | Monthly diff in shared drive | Diff or live edits in the platform | Hires, terminations, comp changes |
| What we return | Payroll pack: register, statutory schedules, WPS file, EOSB, variance | Same pack plus platform state, HRIS data, EOR cascades | Same pack plus contracts, visas, benefits |
FAQ
Common questions about Payroll Bureau
What's in the payroll pack?
Gross-to-net register, the statutory schedule for the relevant authority, the WPS or SIF bank file, EOSB liability movement, a variance report, and payslip data. Pack structure stays consistent month to month so your sign-off and approval flow doesn't change.
What input format do you accept?
Whatever you currently use. We adapt to your file structure during onboarding — typically a CSV or Excel diff with new joiners, leavers, and any compensation or allowance changes for the cycle. No template enforcement.
Where is my payroll data hosted?
Oracle Cloud. In-Kingdom — Riyadh and Jeddah — for Saudi clients, aligned to Saudi PDPL. For other MENA clients the data sits in the regional Oracle estate and stays inside the GCC.
Who submits to GOSI, WPS, Mudad, GPSSA, and the rest?
You do. Bureau is calculation-only — we generate the statutory file, you submit through your own portal access. Your sponsorship and registrations stay with you. If you want submission handled on your behalf, that's the Managed Payroll model.
Can I move from my current bureau to Global Kinect?
Yes. Most takeovers run two to three cycles, depending on data quality, statutory complexity, and the cooperation of your current provider. We scope timing and cutover plan in the first conversation.
How do you handle mid-cycle changes?
Joiners, leavers, salary or allowance changes, and one-off adjustments flow into the next cycle's diff. The variance report flags anything material before sign-off so corrections don't surface after the run is locked.