Paying salaries in Bahrain is not a private arrangement between an employer, its bank, and its staff. It is a monthly filing to a regulator, with a named individual accountable for it and a compliance record attached to the commercial registration.
That has been the legal position since 2019. What changed recently is that the advanced version of the system became mandatory for every private sector employer, and the administrative consequences of getting it wrong now reach beyond the finance function.
This guide sets out what the system requires, who has to do what, and the mechanics that decide whether a month counts as compliant.
What the Wage Protection System is
The Wage Protection System requires employers to pay workers’ wages through banks and financial institutions that are licensed by the Central Bank of Bahrain and registered with the Labour Market Regulatory Authority. The LMRA built and runs the system.
The mechanism has two steps, and both belong to the employer:
- Submit the payroll file through the Expatriate Management System, the LMRA platform usually shortened to EMS.
- Approve the file through your designated banking channel to complete the salary transfer.
The obligation is not discharged by paying people. It is discharged by paying people through this route, in this order, on time.
What changed, and when
The system itself dates back further than most coverage suggests. It was established by Resolution No. 68 of 2019, issued by the Minister of Labour and effective 11 July 2019, with Resolution No. 22 of 2021 governing its phased implementation.
The change that matters now is the move to the advanced version. On 21 October 2025 the LMRA announced that WPS version 2 would be mandatory for all private sector employers, effective February 2026. The phased era is over. There is no remaining category of employer for whom this is optional.
Who it covers
Two answers from the LMRA’s own guidance, both wider in scope than the platform’s name suggests.
All economic sectors, without exception.
All private sector workers, both Bahraini nationals and expatriates. Worth stating plainly, because the system runs on a platform named for expatriate management, which can give the impression that Bahraini staff sit outside it. They do not.
The roles you have to appoint
This is where the system stops being a bank instruction and becomes a governance structure.
The Wages Responsible Person (WRP) is the individual the employer assigns to process and review all payroll files and their data, and to assign the other authorised users. The employer may appoint themselves. Assignment is done by logging into EMS with the advanced eKey of the commercial registration’s responsible person, then providing the WRP’s CPR number, smart card type, date of birth, block number, nationality, email and telephone number. The nominee then approves the assignment by logging in with their own eKey.
Beneath the WRP sit two optional roles:
| Role | Can do |
|---|---|
| Maker | Create worker salary profiles, initiate salary payments, add and update worker receiver account details, submit case justifications |
| Checker | Confirm salary payments, submit case justifications |
Three practical points that save time:
- Each commercial registration can assign up to five makers, five checkers, and five people holding both roles.
- Assigning them is optional. The Wages Responsible Person can perform both functions alone.
- None of these people need to be your employees. The WRP, maker and checker can be appointed regardless of whether they have an employment relationship with the commercial registration. That is what makes the function outsourceable.
Everyone in the chain needs an advanced eKey to log in and to approve their own assignment. Approval runs in a fixed sequence: the checker or the WRP approves the file first, and only then does the bank or payment service provider process it.
What you must do every month
The recurring obligations, and the mechanics that constrain them:
- Upload and confirm the salary file every single month, even if nothing has changed. Salary transfers must be confirmed monthly regardless of changes.
- You cannot reuse last month’s file. You must either upload a new one or edit and submit the current month’s.
- Watch the 15 day window. You can set the transfer date in advance, but the system accepts it only if the specified date does not exceed 15 days from the actual or approved transfer date.
- You may pay after month end, but the file must specify which month the salary relates to.
- Two months of salary can go in one file, and one employee’s monthly salary can be split across two accounts.
A file sitting in Pending Confirmation has been prepared and not approved. It does not count. Because the money can have genuinely reached employees while the file sits unapproved, paying everyone correctly and still being non-compliant are not mutually exclusive.
The social insurance dependency
There is a dependency here that sits upstream of payroll entirely.
Employees who are not registered with the Social Insurance Organisation will not appear in the payroll file at all. Neither will workers whose data is incomplete or who have no bank account entered. A worker is ready when their profile shows Profile Completed.
So a registration failure upstream in HR becomes an invisible wage compliance failure downstream. Nobody gets an error saying “you have not paid Ahmed”; Ahmed simply is not on the list. The same interdependence runs through end of service contributions to the SIO, which is a separate obligation on the same underlying registration data.
One related mechanic worth knowing: reducing a worker’s salary is not something you can simply process. You have to provide the authority with the new employment contract, and the request is reviewed and answered within the applicable service level agreement.
What fixed and variable wage mean here
The system distinguishes the two, and the definitions are the LMRA’s, not accounting convention.
Fixed wage is the amount agreed in the employment contract, received regularly regardless of hours worked or performance. It includes the basic monthly salary and a housing or transport allowance where the contract specifies these as fixed amounts.
Variable wage is the portion that moves between periods: overtime, commissions, performance bonuses and incentives, shift allowances, and holiday working compensation.
Getting the split wrong misstates the filing, and because allowances feed other calculations, an error here rarely stays contained.
What non-compliance costs
Two distinct consequences, and the second is the one that changes behaviour.
The fine. Under Article 188 of the Labour Law in the Private Sector (Law No. 36 of 2012), an employer, or anyone acting on their behalf, who violates any provision of Part Six of the Law, which governs Wages, or the Orders issued for its implementation, is liable to a fine of no less than BHD 200 and not exceeding BHD 500. Because the Wage Protection System was created by Ministerial Resolution under the Labour Law, a WPS breach is a breach of an implementing Order and falls inside that Article.
The administrative measures. Non-compliance also brings restrictions on your LMRA transactions. That is the part that hurts, because LMRA transactions are how a business manages its workforce. At that point a missed upload has stopped being a finance problem and started being an operations problem.
The system also maintains a WPS compliance percentage for each establishment, so this is a track record rather than a series of isolated events.
When the system itself fails
Worth knowing before you need it, because the instinct in a payroll emergency is to pay people some other way and explain later.
If there is a technical failure and it is not resolved within the applicable service level agreement, the LMRA announces through its approved channel that employers should switch to the manual channel. Only then do you download and prepare the salary file in the approved format and submit it to your bank, which processes the payments through Fawri.
Two protections apply for that month: the compliance percentage is not calculated, and employers are not required to justify non-payment through WPS for that period.
The order matters. The manual route opens when the LMRA says it opens, not when you decide the portal is being difficult.
What to check this month
- Confirm your Wages Responsible Person is assigned and their eKey is advanced and current. An expired eKey stops the filing, and it tends to expire quietly.
- Check whether one person is a single point of failure. If the WRP is on leave and no maker or checker exists, the month does not get filed. You are allowed five of each.
- Reconcile your SIO registrations against your payroll list, and confirm nobody is missing from the file because of incomplete data or a missing account.
- Check nothing is sitting in Pending Confirmation from a prior month.
- Diarise the filing against the 15 day window rather than against payday.
Most of this is process discipline rather than judgement, which is exactly why it slips in a business where the finance function is already stretched. We run outsourced payroll in Bahrain including WPS submissions and SIO filings, so the monthly cycle has an owner rather than a volunteer. If the underlying records are the weak point, that usually starts with the bookkeeping rather than with payroll itself.
This article is general information based on the LMRA’s Wage Protection Guideline issued October 2025, the Labour Law in the Private Sector (Law No. 36 of 2012), and public announcements as at August 2026. It is not legal or professional advice. System requirements and procedures change, and specific obligations depend on your circumstances. Confirm the current position with the LMRA before acting.