ERP & Business Systems
Payroll that clears GOSI and WPS on the first run
Your HR team is still keying salaries into a spreadsheet and re-entering them into WPS by hand. We build a payroll system that reads your Saudi obligations natively and hands your accountant one clean file each month.
2 to 4
weeks to a working first payroll run
3
platforms we build on: Odoo, Dynamics 365, Zoho
AR+EN
contracts and payslips, both languages, one record
The direct answer
This is a payroll and HR system built for how salaries actually get paid in Saudi Arabia: GOSI contributions calculated correctly, a WPS-compliant file your bank will accept, and Iqama and visa dates tracked against real expiry rules. It's for companies still running payroll in a spreadsheet, or ones whose current ERP payroll module was never actually configured for the Saudi rules.
What this removes.
WPS file gets rejected
Today
Someone builds the WPS file by hand every month and the bank kicks it back over formatting.
With the system
The system exports a WPS file in the exact format your bank expects, generated straight from payroll.
GOSI numbers don't match
Today
GOSI contributions are calculated on a side spreadsheet and don't reconcile with what payroll actually paid.
With the system
GOSI, both Saudi and non-Saudi rates, calculates inside payroll so the two numbers are always the same number.
End-of-service is a guess
Today
Gratuity gets estimated by whoever's around when someone resigns, and it's rarely right.
With the system
End-of-service is calculated from tenure and last salary the moment it's needed, no manual math.
Contracts live in Word
Today
Employment contracts sit in Word templates that drift out of sync with what payroll actually pays.
With the system
Contracts generate from the same employee record payroll runs on, in Arabic and English together.
What lands in your hands.
Payroll engine
Salary structures, allowances, deductions and GOSI configured for your workforce mix.
WPS export
Bank-format file generated from payroll every cycle, ready to submit.
End-of-service module
Gratuity calculated automatically from tenure, salary and exit type.
Bilingual documents
Contracts, payslips and letters in Arabic and English from one employee record.
Leave and attendance
Saudi leave entitlements and public holidays built into the accrual rules.
Iqama and visa tracker
Expiry alerts on Iqamas, work permits and medical insurance, before they lapse.
Systems and platforms we work with
- Odoo
- SAP
- Dynamics 365
- Oracle
- Zoho
- HubSpot
- Salesforce
Five stages. You sign off every one.
Read each stage as a small contract: what we need from you, what lands in your hands, and the sentence that has to be true before we move on.
- Payroll audit3 to 5 days
- Configuration1 to 2 weeks
- Data migration1 to 2 weeks
- Parallel run1 payroll cycle
- Live and supportedongoing
Payroll audit
3 to 5 days
We look at how you run payroll today, where GOSI and WPS numbers come from, and what your current system gets wrong.
- Share your last 2 payroll runs
- Walk us through your salary structures
- A written gap list against GOSI and WPS rules
- A fixed price and week-by-week plan
We move on when we agree on the gap list and the price in writing.
Configuration
1 to 2 weeks
We configure the platform you chose (or already own) with your salary structures, GOSI rates and leave rules.
- Confirm salary bands and allowances
- Approve leave and holiday calendar
- Payroll configured for your workforce
- GOSI and end-of-service rules set up
We move on when a test payroll run for a sample of employees comes out correct.
Data migration
1 to 2 weeks
We move employee records, salary history and contract data from your spreadsheets or old system into the new one.
- Provide current employee master data
- Review migrated records for accuracy
- Full employee data migrated and checked
- A migration log showing what moved and what didn't
We move on when you confirm the migrated data matches your source records.
Parallel run
1 payroll cycle
We run the new system alongside your existing payroll for one full cycle so nothing surprises anyone on payday.
- Run your usual payroll process one more time
- Compare both outputs with your accountant
- A side-by-side reconciliation of old vs new
- Fixes for any variance found
We move on when the parallel run matches within an agreed tolerance and you sign off.
Live and supported
ongoing
The new system runs payroll on its own. We stay on for fixes, GOSI rate updates and questions from your team.
- Run payroll each cycle
- Flag anything that looks off
- A support window for fixes and questions
- Updates when GOSI or WPS rules change
We move on when n/a, this is the ongoing stage.
Asked before signing.
How is this priced?
Fixed price for the build, quoted after the payroll audit once we know your headcount, salary structures and how many of the Saudi-specific rules apply. Ongoing support after go-live is a separate monthly line, not bundled into the build price.
Do you build this on our existing ERP or do we need a new one?
Either. If you already run Odoo, Dynamics 365 or Zoho, we build the payroll module inside it. If you don't have one yet, we help you pick a platform sized for your headcount rather than defaulting to the biggest name.
Where does our salary and Iqama data live?
In your own database, hosted where you choose. We don't hold employee data on our own servers after the project is delivered, and access follows PDPL requirements for personal data handling. Every configuration decision gets documented so you're not locked into us to make future changes.
Can this connect to our accounting system?
Yes. Payroll journal entries can post directly into your accounting module or a separate finance system, so salary expense and GOSI liability show up in your books without a manual re-entry step each month.
Ready to stop rebuilding WPS files by hand?
Tell us how you run payroll today and how many people are on it. We'll tell you honestly what's fixable and what it costs.