Bahrain has had a Wage Protection System since 2019. What changed in early 2026 is not the obligation to pay wages electronically, which already existed. What changed is how the system works and, more importantly, when compliance is verified.
The Enhanced WPS, made mandatory by the Labour Market Regulatory Authority (LMRA) from February 2026, moves salary validation to before payment, not after. That single shift has consequences for how HR and payroll teams need to structure their monthly process.
This guide covers:
- What the Enhanced WPS changes and what stays the same
- The pre-payment validation model and why it matters operationally
- The WRP role, maker-checker structure, and access requirements
- The monthly file upload obligation and what it demands of your data
- Penalties and what triggers them
- What your payroll process needs to look like going forward
Where Bahrain's approach differs from other GCC countries, those comparisons are drawn in where they add clarity.
Bahrain Enhanced WPS: Quick Summary
- Governing authority: Labour Market Regulatory Authority (LMRA), in collaboration with the Central Bank of Bahrain and BENEFIT.
- Legal foundation: Resolution No. 68 of 2019, now upgraded to the Enhanced WPS (WPS 2.0), mandatory from February 2026. WRP appointment was required by February 1, 2026, with the first mandatory filing deadline at the end of Q1 2026.
- The key change: All salary payments must go exclusively through the LMRA WPS portal. Direct bank transfers to employees are no longer permitted.
- Pre-payment validation: Payroll files are validated by LMRA before salaries are released. Errors block payment, not just flag it after the fact.
- Monthly file upload: A standardised salary file must be uploaded every month through the Expatriate Management System (EMS), even in months where nothing has changed.
- WRP and access structure: Every employer must appoint a Wages Responsible Person (WRP) with an advanced eKey. The WRP may assign up to five maker and checker roles.
- Only Fawri transfers: Salary payments under the Enhanced WPS must use Fawri Salary Transfers, ensuring same-day credit to employee accounts.
- Scope: All private sector employers in Bahrain, covering both Bahraini nationals and expatriate workers. Domestic workers are excluded from the Enhanced WPS.
- Penalties: Administrative actions and fines for non-compliance, plus restrictions on LMRA transactions, which affects work permit processing.
- greytHR covers Bahrain and the GCC: WPS file generation, configurable payroll cutoffs, GOSI calculations, EOSB calculations, and audit-ready records across GCC jurisdictions on one platform.
From Reporting Tool to Validation Gateway: The Core Shift
Bahrain's original WPS, established under Resolution No. 68 of 2019, required employers to transfer wages through licensed banks and report payment details to the LMRA. The system monitored whether payments happened. Compliance was assessed after the fact.
The Enhanced WPS changes that sequence entirely. Under WPS 2.0, salary files are submitted to the LMRA portal before payment is released. The system validates each file against LMRA-registered data: CPR numbers, IBANs, salary amounts, and employment records. Only once the file clears validation does BENEFIT, Bahrain's national payment network, transmit the funds to the approved banks for disbursement.
The practical implication is that errors which previously surfaced as post-payment discrepancies now block payment entirely. A mismatched IBAN, an incorrect salary figure, or an employee whose records are out of sync with LMRA data will cause the file to fail before a single salary is credited. Your payroll cannot go out until the data is clean.
This is meaningfully different from how most other GCC WPS frameworks operate. Kuwait, Oman, and Saudi Arabia all verify compliance after the transfer has been made, with violations triggering penalties in retrospect. Bahrain's Enhanced WPS puts the validation gate before payment, making data accuracy a prerequisite for payroll execution rather than a compliance check that runs alongside it.
The WRP Structure: Who Owns Payroll Compliance Under the New System?
One of the concrete administrative requirements of the Enhanced WPS is the appointment of a Wages Responsible Person. Every employer must designate a single WRP who holds overall accountability for WPS operations. This is not an informal role. The WRP requires an advanced eKey for biometric-secured portal access, and the appointment must be registered with the LMRA.
The WRP can then assign up to five additional users in maker and checker roles, creating a structured approval workflow for salary files before they reach the banking network. In practice, this means:
- Makers prepare and upload the salary file.
- Checkers review and approve it before submission to LMRA.
- The WRP holds overall authority and accountability for the process.
For employers where payroll has historically been handled by one person with direct bank access, this structure introduces a formal separation of duties that may require a process redesign. For larger organisations, it formalises what may already exist informally.
Non-resident employers, those who do not hold a Bahraini ID or an eKey, can designate an authorised WRP on their behalf through LMRA's eSupport function. The authorised person must hold a valid Bahraini or GCC ID and a valid advanced eKey.
The Monthly File Upload: What It Requires of Your Data
Under the Enhanced WPS, employers must upload a standardised salary file every month through the LMRA's Expatriate Management System. The critical word is every: the upload is required even in months where nothing has changed.
The salary file must be in LMRA's prescribed CSV format and contain accurate data for each employee, including:
- CPR (Central Population Registry) number
- IBAN or wallet number registered under the employer's CR in the EMS
- Salary amount, matching the contractually agreed wage
- Any deductions or partial payments, with supporting justifications
Every field is validated against LMRA-registered records before the file is approved. This means the quality of your underlying employee data is now a direct operational dependency. An employee whose IBAN has changed but whose record in the EMS has not been updated will cause a file rejection. An employee who received a salary adjustment that has not been reflected in the LMRA system creates a mismatch. It is also worth being explicit about the scope of a rejection: if validation fails for a single employee, the entire payroll file is rejected. No salaries are released until the errors are corrected and the file resubmitted. One data gap holds up the entire company's payroll. These are not edge cases; they are the kind of routine data gaps that most payroll teams manage quietly in the background.
Where a salary is not paid or is partially paid, the employer must provide a formal justification with supporting documentation, submitted directly through the portal. This replaces whatever informal explanation process existed before and creates a permanent, auditable record of every exception.
Once the file is approved, BENEFIT transmits the payment instruction to the bank. Salary credits are executed through Fawri Salary Transfers only, which ensures same-day credit to employee accounts. This is a positive for employees but means there is no overnight processing window to catch last-minute errors.
How Bahrain's Enhanced WPS Compares Across the GCC
For HR teams managing payroll across multiple GCC countries, Bahrain's Enhanced WPS has some characteristics that set it apart from its regional equivalents:
| Bahrain Enhanced WPS | Kuwait WPS | Oman WPS | |
|---|---|---|---|
| Validation timing | Pre-payment, blocks execution if errors | Post-payment monitoring per individual | Post-payment monitoring |
| Monthly file required if no changes | Yes, every month without exception | No fixed monthly file requirement | File required per payment cycle |
| Compliance level | Company level (LMRA compliance rate tracked) | Individual worker level | Company level (% of workforce) |
| Direct bank transfers | Not permitted under Enhanced WPS | Must go through Kuwaiti bank | Must go through CBO-regulated bank |
| Domestic workers | Excluded from Enhanced WPS | Separate framework applies | Separate framework applies |
The pre-payment validation model is Bahrain's most distinctive feature. In every other GCC country, an employer can in theory pay wages and deal with compliance flags afterward. In Bahrain, under the Enhanced WPS, that sequence is reversed. The system will not release payment until the file passes validation. There is no correcting afterward; the correction has to happen before.
Penalties and What Triggers Them
The LMRA has confirmed that administrative actions and fines apply for non-compliance with the Enhanced WPS. Specific fine amounts at the individual employer level have not been publicly detailed in the same way as Kuwait's per-worker figures or Oman's OMR 50 rate, but the consequences are clear in structural terms:
| Trigger | Consequence |
|---|---|
| Salary file not uploaded through the LMRA WPS portal | Non-compliance flagged; administrative action initiated |
| File uploaded but failing validation (IBAN errors, CPR mismatches, salary discrepancies) | File rejected; payment blocked until errors are corrected and resubmitted |
| Partial payments or non-payments without justification submitted | Treated as a compliance violation; employer must provide documentation through the portal |
| Persistent non-compliance | Restrictions on LMRA transactions, affecting work permit applications and renewals |
| Repeated or unresolved violations | Administrative fines and potential referral under Bahrain's Labour Law |
The most immediate operational consequence of non-compliance is restrictions on LMRA transactions. This affects the company's ability to submit and renew work permits across its entire workforce, not just for the employees whose salary triggered the issue. For businesses with ongoing recruitment or visa renewals, the exposure is broader than a per-employee fine.
What Your Payroll Process Needs to Handle Going Forward
The Enhanced WPS changes the sequence of payroll execution. Getting ready for it is less about learning new rules and more about tightening data hygiene and redesigning the approval workflow. Here is what needs to be in place:
- Register on the LMRA EMS portal: Verify your establishment details are current and correctly registered. Any discrepancy between your EMS record and the salary file will cause a validation failure.
- Appoint your WRP and configure access: Designate the Wages Responsible Person, register their advanced eKey, and assign maker and checker roles. This needs to be done before any salary file can be submitted.
- Audit your employee data: Check that every employee's CPR number, IBAN, and registered salary amount in the EMS match your payroll records. Do this before the first submission, not during it.
- Build the file early: The salary file needs to be prepared, reviewed internally, and uploaded to LMRA with enough time for validation and any resubmission before the salary due date. Last-day file submissions leave no margin for error correction.
- Submit every month without exception: Even in months where there are no changes, the file must be uploaded. Skipping a month is a compliance violation regardless of whether salaries were paid through other channels.
- Document every exception formally: Any non-payment or partial payment must be justified through the portal with supporting documentation. This is now a formal, auditable process, not an informal arrangement.
- Update the EMS for salary changes: Any pay increment, promotion, or contractual adjustment must be reflected in the EMS before the next salary file is submitted. A mismatch between EMS records and the file will fail validation.
- Verify Fawri-enabled bank accounts: Confirm that all salary payments are routed through Fawri Salary Transfers via your LMRA-registered bank or payment service provider. Direct bank transfers outside the WPS portal are not permitted.
- Align Bahraini national salaries precisely with LMRA-registered contract amounts: Under the Enhanced WPS, even small discrepancies between what is filed and what is registered can disqualify Bahraini employees from quota credit during automated reconciliation. This has direct consequences for your Bahrainisation compliance standing, separate from the wage protection violation itself.
How greytHR Supports Bahrain and GCC Payroll Compliance
greytHR is a full-suite HRMS used across the UAE, Saudi Arabia, Oman, Bahrain, Kuwait and Qatar, with its payroll engine built around each country's compliance architecture. For Bahrain specifically:
- WPS-compliant salary file generation: greytHR generates salary files in the standardised format required for LMRA EMS submission, reducing the risk of validation failure from formatting or field-level errors.
- Configurable payroll cutoff dates: Payroll processing schedules can be set to complete early enough to allow time for file preparation, internal review through the maker-checker workflow, LMRA validation, and any resubmission before the payment deadline.
- Employee data management: CPR numbers, IBANs, and salary records are maintained per employee with the accuracy that pre-payment validation demands. Salary changes are logged and can be reflected in the EMS-ready file before the next cycle.
- Deduction and exception documentation: Every partial payment, deduction, or non-payment is logged with the supporting detail needed to satisfy the portal's justification requirement.
- EOSB (Gratuity) calculations for Bahrain: Bahrain's end-of-service gratuity for non-Bahraini workers accrues at half a month's salary per year of service for the first three years, rising to one month's salary per year thereafter. greytHR handles this automatically alongside SIO contribution.
- Audit-ready records: Every payroll run, file submission, and statutory calculation is timestamped and retrievable for LMRA review.
- GCC-wide compliance on one platform: UAE MOHRE compliance, Saudi Arabia's Mudad workflows, Oman's 3-day transfer window, Kuwait AS'HAL requirements and Bahrain's Enhanced WPS, all managed within greytHR without separate tools or manual reconciliation across countries.
Whether you are configuring the Enhanced WPS from scratch or reviewing whether your existing payroll process is ready for pre-payment validation, greytHR is worth a close look.
Set up a greytHR demo with our ME expert
FAQs
What exactly changed between the original WPS and the Enhanced WPS in Bahrain?
The original WPS required employers to transfer wages through licensed banks and report to LMRA afterward. The Enhanced WPS moves validation before payment. Salary files are submitted to LMRA, validated against registered data, and only then released for disbursement.
Can we still pay salaries directly through our bank?
No. Under the Enhanced WPS, all salary payments must go through the LMRA WPS portal. Direct bank transfers to employee accounts are no longer permitted. Payment is executed through BENEFIT and Fawri Salary Transfers only.
Does the monthly file upload apply even if we have no new joiners and no salary changes?
Yes. A standardised salary file must be uploaded every month without exception, even if nothing has changed. Skipping a month is treated as non-compliance regardless of whether employees were paid through other means.
What happens if the salary file fails validation?
The file is rejected and payment is blocked. The errors must be corrected and the file resubmitted before salaries can be released. There is no payment first, fix later option under the Enhanced WPS.
Our WRP is based outside Bahrain and does not have a Bahraini ID. How do we handle this?
Non-resident employers can submit an authorisation request through LMRA's eSupport function to designate a local WRP on their behalf. The authorised person must hold a valid Bahraini or GCC ID and an advanced eKey.
Are domestic workers covered by the Enhanced WPS?
No. The Enhanced WPS explicitly excludes domestic workers. A separate framework applies for domestic worker wage protection in Bahrain.
What does a restriction on LMRA transactions mean in practice?
It prevents the company from submitting or renewing work permits through LMRA until the compliance issue is resolved. This affects the entire workforce, not just employees whose salary was the source of the violation.
Does greytHR generate salary files in the LMRA's required CSV format?
Yes. greytHR produces salary files in the standardised format required for LMRA EMS submission, including the required fields and validation checks that reduce the risk of file rejection.
About greytHR
greytHR is a full-suite HR and payroll software trusted by 30,000+ businesses and 3.25 million users across 25+ countries, including in the GCC. Carrying a 3-decade legacy, greytHR brings the entire employee lifecycle - from onboarding attendance and payroll to compliance, performance, and exit - into a single system. With built-in compliance automation, AI-powered capabilities, dedicated customer support and a mobile-first experience, greytHR helps modern HR teams move away from administrative work into strategic work, keeping the HR function scale and future-ready, always.
