Saudi Arabia
Workforce management software built for Saudi operations
OPPERIQ is a global multi-tenant platform that arrives already configured for the Saudi working week, currency and identity documents — with the gaps stated plainly.
What ships configured for Saudi Arabia
These are tenant settings and data fields that exist in the platform today, not services delivered during implementation.
Saudi payroll defaults
New tenants are created with Saudi Arabia as the payroll country and SAR as the operating currency, so salary templates, expenses and budgets are denominated correctly from day one.
Friday–Saturday working week
The weekend is configured as Friday and Saturday by default, which means overtime, attendance tolerance and leave calculations line up with the local working week without custom setup.
Iqama and national ID tracking
Iqama and national ID numbers are first-class fields on the employee record, collected during digital onboarding and monitored by scheduled expiry alerts alongside passports and licences.
Configurable GOSI contribution rates
Employee and employer GOSI contribution rates are tenant-level settings consumed by the deduction engine, so payroll reflects your registered rates rather than a hard-coded assumption.
Regional presence
The team is reachable on a Saudi number during local business hours for evaluations, deployment planning and support.
Per-tenant locale settings
Currency, timezone and language are stored per tenant, which is what lets a group operating across the Gulf run several entities on one deployment.
What OPPERIQ does not do yet
If compliance filing is a hard requirement for your evaluation, this is the part worth reading first.
- WPS payroll file generation
- Payroll exports bank and journal files in CSV today; a dedicated WPS format is on the roadmap.
- ZATCA e-invoicing
- OPPERIQ is not a ZATCA-integrated invoicing system and does not submit tax invoices.
- Arabic interface and Hijri dates
- The interface is English-only and uses the Gregorian calendar. Arabic localisation is planned.
Regional defaults, global architecture
Saudi settings are defaults, not limits. Groups running entities across the Gulf and beyond operate them from one deployment.
Multi-tenant by architecture
One deployment serves many organisations with data scoped per tenant, so adding an entity is a provisioning step rather than a new installation.
Stateless, horizontally scalable services
The API holds no session state, so capacity is added by running more instances behind a load balancer over shared PostgreSQL and Redis.
Background processing that absorbs peaks
Bulk imports, notifications and scheduled jobs run on queues, so a month-end payroll run or a thousand-row employee import does not slow the interface.
Talk to us in the region
Bring your payroll rules, site list and reporting requirements and we will walk through how they map onto attendance, payroll and reporting.
See OPPERIQ on your own operation
A 30-minute walkthrough of the modules that match how you work — attendance, fleet, payroll and reporting. No commitment.