Payroll computed under the law — not on a calculator
Payroll in contracting is not a fixed table. It is variable allowances, absences from a biometric device, advances in instalments, Omani/expatriate classification with different contributions, and an end-of-service formula. Ribhia computes all of it, and distributes each salary across the projects the employee worked on.
The questions it answers
The questions that make every month-end tense.
"Is this salary right?"
Every component computes from its source: the contract for basic pay, the device for absence, the advances ledger for the instalment. The payslip shows each figure and where it came from.
"Which project did payroll eat?"
Salary is distributed across the projects the employee worked on that month — so project cost includes real supervision.
"The bank rejected our transfer file"
The wage protection file is generated to that bank’s exact column template, with validation that blocks an incomplete file before export.
"What is owed if they leave?"
The calculation runs on length of service, reason for leaving and the leave balance — and the figure exists before the decision is taken.
What is inside
The whole employee lifecycle, from hire to final dues.
How it connects to the rest
No module works alone. These are the links that keep the numbers consistent.
Project costing
Distributed salary enters project cost — and that is what makes profit real rather than approximate.
Finance
An approved payroll run becomes one entry with its components and contributions.
Labour day sheets
The worker’s days on a project are the same days that set their pay and the project’s cost.
Approval
A run does not reach the bank before approval, and the approved version is sealed with a fingerprint of its figures.
One month is enough to judge
We load your employees and their components, produce a full month’s run, and you compare it against the one you have.