Is my salary data safe?

Yes. The validator runs entirely in your browser no upload, no server, no logging. Open the network tab while you use it and you'll see nothing leaving the page.

Salary Information File the standardized format Omani banks use under the Wage Protection System (WPS) to process monthly payroll. It's typically a CSV or tab-separated file with 16 fields per employee.

What are the 16 fields in an Oman SIF file?

Salary Year, Salary Month, Employee ID Type (C for Civil ID or P for Passport), Employee ID, Employee Name, Bank Code, Account Number/IBAN, Salary Frequency (M/B), Working Days, Net Salary, Basic Salary, Extra Hours, Extra Income, Deductions, Social Security Deductions, and Notes. Every row must have exactly 16 fields separated by commas or tabs.

What is the IBAN format for Omani banks?

An Omani IBAN is always 23 characters: 'OM' + 2 check digits + 3-digit bank code + 16-digit account number. Ujoor verifies length, checksum, and recognizes all 22 Omani bank codes no manual lookup needed.

What if my file has an invalid Civil ID number?

Omani Civil IDs are typically 7–9 numeric digits with no leading zeros. Ujoor flags IDs with leading zeros, non-numeric characters, unusual lengths, or duplicates across rows each error points to the exact row so you can correct it before the bank does.

Why does my SIF file need UTF-8 encoding?

Arabic employee names and special characters require UTF-8 so the bank can read them correctly. If the file uses a different encoding (like ANSI or Windows-1256), Ujoor stops validation and tells you to re-save as UTF-8. Most Omani banks mandate UTF-8 anyway.

My file uses tabs instead of commas will that work?

Yes. Ujoor auto-detects commas or tabs, and accepts .csv or .txt. UTF-8 encoding is required (most banks mandate it anyway).

Can I validate bi-weekly salary files?

Yes. Ujoor supports both Monthly (M) and Bi-weekly (B) salary frequencies. The same file cannot mix both all rows must share one frequency. Ujoor flags any mixed-frequency file before you upload it.

Which banks does it support?

All banks that follow the Central Bank of Oman's SIF v4.1 spec. The validator checks your file against that specification, not against any single bank's proprietary quirks.

Does Ujoor work with Bank Muscat, NBO, Bank Dhofar, and Sohar International?

Yes. Ujoor validates against the Central Bank of Oman's SIF v4.1 specification, which every licensed bank follows Bank Muscat, NBO, Bank Dhofar, Sohar International, Oman Arab Bank, Ahli Bank, Bank Nizwa, Meethaq, Maisarah, Al Hilal, and all other 22 banks operating in Oman.

How is the Social Protection Fund (SPF) deduction calculated?

For Omani employees, SPF is 8% of gross salary, capped at a maximum of OMR 240 per month (8% of the OMR 3,000 salary cap). Expatriates contribute at different rates. Ujoor flags any row where the Social Security Deduction doesn't match the standard rate.

What is the minimum wage for Omani nationals in WPS files?

The minimum wage for full-time Omani nationals is OMR 325 per month. Ujoor warns you when a row falls below this so you can confirm the employee is part-time, on unpaid leave, or had deductions that explain the shortfall.

Is there a maximum deduction limit in Omani payroll?

Yes. Oman Labour Law caps deductions at 50% of an employee's gross pay. Ujoor warns when deductions exceed that limit a common cause of bank rejection and a potential labour-law violation. Add a note in the Notes field explaining the deduction if it's justified.

How do I fix a rejected SIF file?

Open the file in Ujoor and every rejection reason appears inline with the exact row, field, and rule. Fix each issue in place, then download a clean file. Most common causes: invalid IBAN, duplicate employee IDs, non-UTF-8 encoding, and salary math mismatches.

The validator stays free. Paid features (payroll generation, direct bank submission) are coming later they'll be optional and separate.

Home/SIF errors/Salary month is in the future

SIF errors

Salary month is in the future

The Salary Year (field 1) and Salary Month (field 2) point to a date that is more than one month ahead of today. Regular SIF files describe salary for the current or just-passed month not a future one.

Rule: V06

Why the bank rejects this

The Wage Protection System exists to confirm that salaries for work already performed are paid on time. A future-dated file suggests either a data-entry error or an attempt to pre-register salaries for work that has not happened yet banks reject it to keep WPS reporting aligned with the labour performed.

How to fix it

Check field 1 (Salary Year) and field 2 (Salary Month) against your actual pay period. For salary covering March 2026 work paid in early April 2026, use 2026 and 3 not 2026 and 4.
Beware of year-end rollover: January salary for December work should use Year = previous year, Month = 12. A common bug flips both.
If you genuinely need to pre-fund a future salary (e.g. employee going on long leave and needing April pay in March), change the file type from regular Salary to Advance Salary with your bank's WPS portal not by keeping it as a normal SIF.
Verify your payroll system did not auto-advance the month on export. Some tools pre-fill "next month" as the default.
If the year is wrong (e.g. 2027 instead of 2026), a single cell fix in field 1 typically clears the whole file.
Re-validate with Ujoor V06 should drop below the warning threshold.

How Ujoor catches this

Ujoor compares the year and month in every row against today's date and warns the moment a file is more than a month ahead of real time with a clear note on when to use an Advance Salary file type instead. You catch the mistake before the bank does.

Validate your SIF file now

Drop your file. See every issue inline. Fix it and download a clean file all in your browser.

Try the validator