Bank code not recognized
The bank code in field 6 is not one of the 22 licensed banks operating in Oman. SIF bank codes are standardized SWIFT-style codes like BMUSOMRX (Bank Muscat) or NBOMOMRX (National Bank of Oman), and the bank checks them case-sensitively.
Why the bank rejects this
The bank routes the salary to the recipient bank based on this code. An unknown or misspelled code has no route, so the bank's settlement engine returns the file as malformed no transfers are attempted. A one-character typo (like BMUSOMR instead of BMUSOMRX) is enough to reject everything.
How to fix it
- Check field 6 against the official 22-code list from the Central Bank of Oman codes are case-sensitive and usually 8 characters long (some Islamic windows are 11 characters).
- Common typos: BMUSOMR (missing final X), NBOOMRX (should be NBOMOMRX), BDOFOMR (missing U). Ujoor suggests the closest match when it finds one.
- Confirm the bank code matches the bank embedded in the IBAN (field 7). A Bank Muscat IBAN paired with an NBO bank code will be rejected even if both are valid codes.
- If the employee recently switched banks, update the Bank Code, Account Number, and IBAN together not just one of them.
- If you use an Islamic window (Meethaq, Maisarah, Muzn, Al Hilal, Sohar Islamic), use the 11-character code specific to the Islamic window, not the parent bank code.
- Re-validate in Ujoor after correcting; rule V24 must pass for every row.
How Ujoor catches this
Ujoor ships with the full list of 22 Omani bank codes baked in, and rule V25 suggests the closest match when your code has a typo ("did you mean BMUSOMRX?"). You never need to hunt for the official list the validator already knows it.
Validate your SIF file now
Drop your file. See every issue inline. Fix it and download a clean file all in your browser.