Bahrain WPS Payroll in Odoo: SIF Files, GOSI and End-of-Service Indemnity

WPS output

SIF file

GOSI employer, Bahraini

~12%

GOSI employer, expat

~3%

Indemnity

Accrue monthly

Test before

Real bank run

The Wage Protection System and the SIF file

The Wage Protection System requires salaries to be paid through licensed financial institutions, with each payment reported in a standardised Salary Information File (SIF). The bank validates the file before processing — an invalid file is rejected, and salaries do not go out.

This is what makes WPS different from ordinary payroll reporting. A spreadsheet can produce a payroll register. It cannot reliably produce a validated SIF, and manual SIF preparation does not scale past a handful of employees without errors.

What the SIF must carry

The precise layout is set by your bank and the central scheme, but the content consistently includes:

• Employer identifier — the company's registration and account details.
• Employee identification — CPR number, full name, and the bank account or IBAN receiving the salary.
• Salary period — the month and year being paid.
• Salary components — basic salary and allowances, broken out as the scheme requires.
• Deductions — including GOSI contributions where applicable.
• Net pay per employee and the file total.
• Payment date and any agreed variations.

GOSI social insurance

Bahraini and non-Bahraini employees are treated differently, and the difference is material to workforce cost.

Two consequences follow that belong in workforce planning rather than in payroll configuration:

• Employing Bahraini nationals carries a materially higher employer contribution. This is a genuine cost factor and should be modelled in workforce planning rather than discovered at month end.
• Bahrainisation obligations apply to many sectors alongside the contribution differential. The two interact, and neither is a payroll decision alone.

Within Odoo, GOSI must be configured as separate contribution rules for the two categories, posting to distinct liability accounts, and producing the periodic GOSI return figures without manual extraction.

End-of-service indemnity

This is the accrual most often mishandled, because it is a real liability that produces no monthly cash movement and therefore disappears from attention.

Under Bahraini labour law, an employee who leaves is entitled to an end-of-service indemnity calculated on length of service and final remuneration. The obligation builds continuously from day one of employment.

Why accrual matters

A business with twenty employees averaging five years of service carries a substantial indemnity liability that appears nowhere unless it is accrued. The consequences of not accruing are predictable:

• Profit is overstated every period, because the cost of the current period's service is not recognised.
• The liability is understated on the balance sheet, which affects audited financial statements.
• A resignation becomes a cash shock rather than the settlement of an accrued balance.
• Auditors raise it. Unrecorded employee benefit obligations are a standard audit adjustment.

Leave and other statutory entitlements

Bahraini labour law sets entitlements that must be tracked systematically rather than remembered:

• Annual leave — accruing on service length, with the rate increasing after qualifying periods.
• Sick leave — with graduated pay treatment across the entitlement period.
• Maternity leave — statutory duration and pay.
• Official holidays — with premium pay where worked.
• Notice periods and termination entitlements — which interact with the indemnity calculation.

Odoo's leave and time-off modules handle accrual and balances well once the rules are configured. The failure mode is configuring them loosely at go-live and correcting informally afterwards, which produces balances nobody trusts.

Configuring Odoo for Bahrain payroll

1. Employee master data first. CPR number, nationality, bank and IBAN, contract start date, basic salary and allowances broken out. Every downstream calculation depends on this.
2. Salary structures with basic and allowances separated, because indemnity and several statutory calculations run on basic salary.
3. GOSI contribution rules by nationality, posting to distinct liability accounts.
4. SIF export configured to your bank's specification and tested through the bank's channel.
5. Indemnity accrual journal automated monthly.
6. Leave rules reflecting statutory entitlements and accrual rates.
7. Accounting integration — the payroll journal must post automatically to the correct cost and liability accounts, not to a single clearing account.

Where it sits in the project Odoo implementation timeline in Bahrain: the 12-week plan →

The four ways Bahrain payroll goes wrong in an ERP

If Odoo payroll will not cover it

Some businesses run a dedicated Bahrain payroll product alongside Odoo for accounting. That is a legitimate choice, and often the right one where the workforce is large or the entitlement structures are complex.

The requirement is then integration rather than duplication:

• The payroll system produces the SIF and GOSI filings.
• Odoo receives a single monthly payroll journal with the correct account split.
• The indemnity liability is recorded in one place and reconciled monthly.
• Employee master data is maintained in one system of record, not two.

What must not happen is parallel manual maintenance, where headcount, salaries and balances exist in two systems and nobody can say which is correct.

General information only, not legal or payroll advice on specific facts. Contribution rates, entitlements and SIF specifications should be confirmed with the General Organisation for Social Insurance, the Ministry of Labour and your bank before configuration.