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.

الرئيسية/أخطاء SIF/ترميز الملف يجب أن يكون UTF-8

أخطاء SIF

ترميز الملف يجب أن يكون UTF-8

ملف SIF حُفِظ بترميز غير UTF-8 غالبًا Windows-1256 (صفحة الرموز العربية القديمة) أو ANSI أو UTF-16 مع علامة ترتيب البايت. UTF-8 هو الترميز الوحيد الذي يضمن عبور الأسماء العربية من محلل البنك بدون تلف.

قاعدة: F08

لماذا يرفض البنك هذا؟

محلل البنك يحاول قراءة الملف كـ UTF-8 أولًا. إذا ظهرت الأحرف العربية مُشوَّشة، يتوقَّف المحلل فورًا لا يحاول ترميزات أخرى. يُرفَض الملف قبل التحقق من أي صف، فترى "ترميز الملف غير معترف به احفظ الملف بترميز UTF-8" ولا شيء غير ذلك.

كيف تُصلحه

افتح ملف SIF في Notepad++ (ويندوز) أو VS Code (أي نظام تشغيل) لا في Notepad العادي، فهو يحفظ بـ ANSI بصمت.
في Notepad++: قائمة Encoding ← "Convert to UTF-8" (لا "UTF-8 with BOM" علامة ترتيب البايت تُربك بعض البنوك). ثم File ← Save.
في VS Code: انقر على مؤشِّر الترميز في أسفل اليمين ← "Save with Encoding" ← "UTF-8" (بدون BOM).
إذا صدَّرت من Excel، استخدم File ← Save As ← "CSV UTF-8 (Comma delimited)" في Excel 2016 وما بعده. النسخ القديمة من Excel تحفظ بـ ANSI افتراضيًا افتح الناتج في Notepad++ للتأكد.
تجنَّب تصدير CSV المُضمَّن في Google Sheets للملفات العربية يُضيف أحيانًا UTF-16. نزِّل كـ .xlsx ثم صدِّر عبر أداة UTF-8 موثوقة.
ارفع الملف المُعاد حفظه في أُجور؛ يجب أن تمر القاعدة F08 ويبدأ التحقق من صفوف الملف.

كيف يكتشفها أُجور

يكتشف أُجور الترميز فور إسقاط الملف ويتوقَّف بالقاعدة F08 إذا لم يكن UTF-8 فلا تُهدر وقتًا في تصحيح صفوف مليئة بالأحرف المُشوَّشة. شاشة التوقف تُخبرك بالأداة والإعداد الصحيحين لإعادة الحفظ.

دقّق ملف SIF الآن

أفلت ملفك. شاهد كل مشكلة في مكانها. صحِّحها ونزِّل ملفًا نظيفًا كلها في متصفحك.

جرّب المدقّق