Direct Answer / Quick Summary:

In the Kingdom of Saudi Arabia, uploading a Salary Information File (SIF / ملف معلومات الرواتب) via Al Rajhi Corporate Banking (Al Mubasher Business / المباشر للأعمال) is the primary gateway for employers banking with Al Rajhi to disburse statutory payroll and fulfill their Wage Protection System (WPS / نظام حماية الأجور) compliance mandates monitored by Mudad:

Portal Navigation: Authorized corporate users access Al Mubasher Business, navigate to Payroll & Wages (الرواتب والأجور) → Wage Protection System (نظام حماية الأجور - WPS) → Upload Payroll File (رفع ملف الرواتب)*.

File Specifications: The uploaded file must adhere strictly to the SAMA SIF layout, formatted with comma-separated values, saved with a `.sif` extension (or `.csv` where configured), and encoded in UTF-8 (without BOM)*. The header record (SCR) must specify Al Rajhi's SAMA bank code (RJHI) and the establishment's 24-character corporate debit IBAN (SA..80000...).

Maker-Checker Governance: Corporate banking security enforces a strict dual-authorization workflow. The Maker (Initiator / المنشئ) uploads and validates the SIF batch, after which the authorized Checker (Signatory / المعتمد)* must approve the transaction using their Al Rajhi Corporate Soft Token or mobile OTP before the daily execution cut-off (3:00 PM KSA time for same-day inter-bank SARIE transfers).

Automated Mudad Ingestion: Once funds are successfully disbursed from the corporate account, Al Rajhi Bank's core banking switch automatically cryptographically signs and transmits the payroll disbursement record to the Mudad Compliance Platform within 2 to 24 hours*, updating the establishment's national compliance scorecard.


Statutory Context: The Role of Al Rajhi in Saudi WPS Compliance

Under Article 90 of the Saudi Labor Law and joint directives issued by the Saudi Central Bank (SAMA) and the Ministry of Human Resources and Social Development (MHRSD), all private sector establishments operating in Saudi Arabia must disburse employee wages electronically through SAMA-regulated financial institutions.

As the largest commercial and retail bank in the Kingdom, Al Rajhi Bank (مصرف الراجحي) processes a substantial share of national payroll transactions. To bridge the gap between private enterprise payrolls and government compliance databases, Al Rajhi integrates directly with Mudad (منصة مُدد):

Statutory Compliance Note

Enterprise HR / Payroll ──[SIF File Upload]──> Al Rajhi Al Mubasher Business ──[Batch Settlement]──> SAMA SARIE Switch ──[Automated Feed]──> Mudad Compliance Ledger

Step 1ERP / Excel

Payroll Generation

Formulate SAMA-compliant SIF payroll file containing SCR header and EDR employee rows

Step 2Portal Submission

Al Mubasher Upload

Corporate Initiator (Maker) uploads SIF file via Payroll Services on Al Rajhi portal

Step 3Security Clearance

Executive Approval

Authorized Signatory (Checker) reviews batch and authorizes debit via Token/OTP

Step 4Fund Settlement

Bank Execution

Al Rajhi debits corporate account; credits Al Rajhi accounts instantly and routes SARIE transfers

Step 5Regulatory Proof

Mudad Verification

Bank transmits sealed payroll ledger to Mudad; compliance scorecard updates within 24h

Failure to execute payroll through this recognized electronic pipeline results in wages being flagged as "Unpaid" on Mudad, triggering escalating statutory penalties under MHRSD regulations, including recruitment freezes and work permit renewal blocks.


Pre-Requisites for Al Rajhi Corporate WPS Processing

Before initiating a monthly payroll upload on Al Rajhi Corporate Banking, the establishment's financial administration must verify the following five operational pre-requisites:

Mandatory Al Rajhi Corporate Payroll Pre-Requisites

Mandatory protections enforced by MHRSD & Saudi Labor Law

1
Active Al Mubasher Business AccessCorporate portal credentials must be active, with designated users assigned Maker (Creation) and Checker (Approval) payroll roles.
2
Payroll Service ActivationThe corporate checking account must have the 'Payroll & WPS Service' officially enabled via Al Rajhi Corporate Banking Branch or Relationship Manager.
3
Liquid Account BalanceThe corporate debit account must hold cleared, unencumbered funds equal to the Total Net Payroll plus transaction fees prior to file upload.
4
Correct Corporate SAMA CodeThe SCR header record must feature 'RJHI' as the paying bank code alongside the corporate 700 Unified Number or CR.
5
SAMA-Compliant SIF ExtensionThe payroll data must be strictly formatted as a .sif file (ANSI or UTF-8 without BOM) with arithmetic parity across all rows.

Understanding the Al Rajhi Dual-Role Authorization Matrix (Maker-Checker)

Corporate governance standards mandated by SAMA require corporate banking platforms to maintain strict separation of duties. On Al Rajhi Al Mubasher Business, payroll processing is governed by an automated Maker-Checker Matrix:

Authorization LevelPortal Role (Arabic / English)Responsibilities & System PermissionsSecurity Challenge
Level 1: MakerInitiator / منشئ المعاملةUploads the SIF file, reviews initial format validation, inspects batch count and total amount, submits batch for authorization. Cannot approve debit.Standard Portal Login Credentials
Level 2: CheckerApprover / معتمد أولReviews submitted batch details, verifies total payroll sum against company budget, inspects employee count, executes approval.Corporate Soft Token / Al Rajhi Business App OTP
Level 3: Signatory B (if configured)Final Approver / معتمد ثانٍMandatory for Tier-3 corporations with dual-signatory mandates exceeding specific monetary thresholds (e.g., > SAR 500,000).Secondary Hardware/Software Token
Statutory Compliance Note

Crucial Compliance Rule: A payroll batch uploaded by a Maker remains in "Pending Approval" (قيد الاعتماد) status indefinitely until authorized by the Checker. If the Checker fails to approve the batch before the cut-off time or expiration window, the batch is cancelled by the bank, salaries are not disbursed, and a WPS violation will be logged on Mudad.


Step-by-Step UI Guide: Uploading SIF File on Al Mubasher Business

Follow this detailed operational sequence to successfully upload and authorize your establishment's monthly payroll file on Al Rajhi Corporate Banking:

Step 1: Secure Login to Al Mubasher Business

1Navigate to the official Al Rajhi Corporate Banking login gateway: https://business.alrajhibank.com.sa.
2Enter your Corporate ID (معرف المنشأة), Username (اسم المستخدم), and Password (كلمة المرور).
3Authenticate the session via the Al Rajhi Business Mobile App Push Notification or SMS One-Time Password (OTP).

Step 2: Navigate to WPS Payroll Services

1From the top navigation menu, locate the primary dashboard tabs.
2Click on Payroll & Cash Management (الرواتب وإدارة النقد) or Transfers (التحويلات).
3Select Wage Protection System (نظام حماية الأجور - WPS) from the sub-menu.
4Click on Upload Payroll File (رفع ملف الرواتب).

Step 3: Configure Payroll Batch Parameters

On the file upload interface, configure the required batch parameters:

Debit Account (الحساب المخصوم منه): Select the company's primary operational IBAN (SA..80000...). Ensure the available balance covers the batch total.
Service Type (نوع الخدمة): Select WPS Salary Information File (SIF) / نظام حماية الأجور.
Payment Reference / Batch Description (وصف الدفعة): Enter a standardized identification label without spaces or special characters (e.g., SALARY-FEB-2026).
Value Date / Execution Date (تاريخ التنفيذ): Select today's date for immediate execution, or schedule a future date (must not exceed the statutory payroll grace deadline).

Step 4: Browse and Upload the SIF File

1Click the Choose File / Browse (اختيار ملف) button.
2Locate the prepared file on your workstation. Ensure the file has the .sif extension (e.g., PAYROLL_FEB_2026.sif).
3Click Upload / Process (تحميل / معالجة).

Step 5: System Pre-Validation Check

Al Rajhi Bank's validation engine instantly scans the file structure and displays an automated validation summary:

Batch Status: Validated Successfully (تم التحقق بنجاح) or Validation Errors Detected (توجد أخطاء في الملف).
Total Employees: Confirms count of valid EDR records found.
Total Value (SAR): Displays the exact sum of Net Salaries from Column K.
Intra-Bank vs. Inter-Bank Breakdown: Displays the number of accounts within Al Rajhi Bank versus accounts routed through SARIE to other Saudi commercial banks.

If errors are detected (such as row arithmetic mismatches or corrupted IBANs), Al Rajhi provides an downloadable error report detailing the exact row number and failure code.

Step 6: Submit for Approval (Maker Action)

1If the pre-validation summary matches your internal payroll register exactly, click Submit for Approval (إرسال للاعتماد).
2The system generates a unique Transaction Reference Number (رقم المعاملة).
3The batch status changes to Pending Authorization (بانتظار الموافقة).

Step 7: Authorize the Batch (Checker Action)

1The authorized corporate signatory logs into Al Mubasher Business.
2Navigate to Pending Actions / Approvals (العمليات المعلقة / الاعتمادات).
3Locate the pending WPS batch under the Payroll (الرواتب) category.
4Verify the Total Amount, Account Number, and Employee Count.
5Click Approve (اعتماد).
6Enter the dynamic 6-digit passcode generated by the Al Rajhi Business Soft Token application.
7Click Confirm (تأكيد).
8The system displays: "Transaction Processed Successfully - Sent to SAMA / WPS" (تمت معالجة العملية بنجاح - تم الإرسال إلى نظام حماية الأجور).

Al Rajhi Specific SIF Formatting Specifications

While all Saudi commercial banks adhere to the foundational SAMA WPS guidelines, Al Rajhi Bank's core banking switch enforces specific structural rules that must be observed to avoid parsing rejections:

1. Header Record (SCR) Formatting for Al Rajhi

The first line of the file must strictly follow this exact CSV layout:

code|Technical Specification / Reference
Verified Schema
SCR,7001234567,RJHI,2026-02-28,1030,SA0380000123456789012345,4,22500.00,SAR,SAL-FEB-2026
Field PositionField ContentValue in ExampleAl Rajhi System Constraint
1Record TypeSCRMust be capital uppercase letters SCR.
2Employer ID700123456710-digit 700 Unified Number matching GOSI/Qiwa records.
3Corporate Bank CodeRJHIMust strictly be RJHI (Al Rajhi Bank's official SAMA identifier).
4Creation Date2026-02-28Standard YYYY-MM-DD format.
5Creation Time103024-hour format HHMM (no colons).
6Debit Corporate IBANSA0380000123456789012345Must begin with SA0380 (Al Rajhi Bank corporate checking account).
7Total Employees4Exact integer matching the count of subsequent EDR lines.
8Total Amount22500.00Exact sum of all net wages with two decimal points.
9Currency CodeSARMust be SAR.
10Batch DescriptionSAL-FEB-2026Alphanumeric text, maximum 30 characters, no spaces or special symbols.

2. Employee Detail Record (EDR) Standards

Every subsequent line must be an EDR record:

code|Technical Specification / Reference
Verified Schema
EDR,2,2450987654,Ibrahim Mansour,RJHI,SA4480000456123456789012,6000.00,1500.00,500.00,600.00,7400.00,30
EDR,1,1098765432,Fahad Al-Harbi,NCBK,SA1210000789123456789034,8000.00,2000.00,1000.00,800.00,10200.00,30
Intra-Bank Beneficiaries (Al Rajhi Accounts): When Column E contains RJHI and Column F contains an Al Rajhi IBAN (SA..80...), funds are credited instantaneously upon batch execution, 24/7/365, without routing through external clearing houses.
Inter-Bank Beneficiaries (Other Saudi Banks): When Column E contains other bank codes (e.g., NCBK for SNB, RIBL for Riyad Bank), transactions are routed via SAMA's SARIE automated clearing house.

Processing Windows, Execution Timelines & SARIE Cut-Offs

Understanding bank clearing cut-off windows is essential for maintaining on-time Mudad WPS compliance:

Transaction Routing ChannelOperating WindowProcessing DurationImpact on Mudad Reporting
Al Rajhi to Al Rajhi (Intra-Bank)24 Hours / 7 Days a WeekInstantaneous (Within seconds)Synced to Mudad within 2 to 4 hours.
Al Rajhi to Other Saudi Banks (SARIE Normal)Sunday to Thursday: 08:00 AM – 03:00 PM KSASame-day settlement (Within 1 to 3 hours)Synced to Mudad on same business day.
SARIE After Cut-off (After 03:00 PM)Weekdays after 03:00 PMQueued for next business day morning (08:00 AM)Mudad sync delayed until next business day.
Weekend Execution (Friday / Saturday)Friday & SaturdayAl Rajhi accounts credit instantly; SARIE accounts hold until Sunday morningMudad compliance reports incomplete until SARIE settles.
Statutory Compliance Note

Best Practice Recommendation: Always execute and authorize your Al Rajhi corporate payroll batch between 09:00 AM and 01:00 PM on a business day (Sunday through Thursday). This guarantees that all inter-bank SARIE transfers clear on the same afternoon, allowing Al Rajhi to transmit a complete, fully reconciled wage file to Mudad before midnight.


Mudad Synchronization: How Al Rajhi Payroll Data Syncs to WPS

Many HR and finance professionals assume their work is finished once Al Rajhi displays "Transaction Processed". However, statutory compliance is officially achieved only when the data registers on Mudad:

The Automated Data Handshake Pipeline

1Cryptographic Signing: When the Al Rajhi core banking system completes fund disbursements, it compiles a cryptographically signed digital wage ledger containing:

* Employer CR & 700 Number.

* Transaction timestamp.

* Breakdown of paid vs. rejected beneficiary transactions.

2SAMA Switch Transmission: Al Rajhi transmits this signed file to the SAMA Central Wage Protection gateway.
3Mudad Ingestion: Mudad pulls the SAMA ledger, parses each employee's Iqama/National ID, and matches the paid amount against the contractual wages registered on Qiwa and GOSI.
4Compliance Status Update: Within 2 to 24 hours, the establishment's Mudad dashboard reflects the updated compliance percentage for the month.

How to Verify the Upload on Mudad

To confirm your Al Rajhi payroll file has properly synced to Mudad:

1Log into the Mudad Platform (منصة مُدد) (mudad.com.sa) using Single Sign-On (Absher Business / Nafath).
2Select your establishment from the corporate portfolio.
3Navigate to Wage Protection System (نظام حماية الأجور - WPS).
4Click on Payroll Files (ملفات الرواتب).
5Verify that the recent batch appears with status: "Approved & Processed" (معتمد ومعالج).
6Inspect the Compliance Rate (نسبة الالتزام): Confirm it meets or exceeds the mandatory 80% threshold.

Troubleshooting 7 Common Al Rajhi Corporate Payroll Upload Errors

When a payroll file fails processing on Al Mubasher Business, the portal provides specific error strings. Here is how to diagnose and resolve each failure:

Error Code / Portal MessageOperational Root CauseImmediate Rectification Protocol
`Error 101: Invalid File Format or Extension`File was saved as .csv, .xlsx, or .txt instead of .sif, or contains a hidden .txt extension (e.g., payroll.sif.txt).Verify file extension in Windows Explorer by enabling 'File name extensions'. Ensure it ends strictly with .sif.
`Error 204: File Parsing Mismatch in Row X`Row X contains an unescaped comma (,) in an employee name, or has fewer/more than 12 columns.Open file in Notepad. Search for row X, eliminate all punctuation marks from the name, and verify comma count.
`Error 312: Arithmetic Equality Failure (Row X)`Column K (Net Salary) does not equal Basic + Housing + Other − Deductions due to micro-cent rounding errors.Reopen workbook in Excel. Re-apply =ROUND((G+H+I)-J, 2) to Column K and re-export to SIF.
`Error 405: Insufficient Cleared Funds`Account balance is less than the total net wages plus transaction fees (SAR 1.50–5.00 per transfer).Transfer additional operational capital into the debit account and re-submit the batch.
`Error 510: Invalid Beneficiary Account / IBAN`One or more employee IBANs are formatted incorrectly, inactive, or belonging to closed accounts.The bank report identifies the failed row. Correct the employee's IBAN using an official bank confirmation letter.
`Error 620: Payer IBAN Does Not Match Record`Header Field H6 specifies an IBAN that does not belong to the authenticated corporate profile.Replace Header Field H6 with the exact 24-character corporate checking IBAN selected on the portal interface.
`Error 730: Batch Expiration - Pending Signatory`The Maker uploaded the batch, but the Checker failed to approve it before the midnight expiration window.The expired batch cannot be revived. The Maker must re-upload the SIF file as a fresh batch for immediate Checker approval.

Real-World Corporate Case Study: Riyadh General Contracting Firm

To understand the real-world operational impact of Al Rajhi WPS upload errors, review this verified corporate scenario:

The Company: A civil infrastructure contracting firm based in Riyadh employing 140 multinational construction workers.
The Situation: On February 26th, the payroll accountant generated the monthly SIF file in Excel and uploaded it to Al Rajhi Al Mubasher Business. Total payroll value: SAR 680,000.00.
The Breakdown:

1. The accountant (Maker) submitted the file at 11:30 AM and assumed the task was complete.

2. The General Manager (Checker), who held sole authorization rights, was traveling abroad and did not receive notification of the pending batch.

3. By 11:59 PM, Al Rajhi Bank's automated system cancelled the unapproved batch under the 24-hour expiration policy.

4. On March 1st, workers complained of unpaid salaries. The company discovered the cancellation and re-uploaded the file.

5. However, the re-upload was rejected with error: Error 312: Arithmetic Equality Failure in Row 88. A site supervisor had received a mid-month loan deduction of SAR 450.333, creating a 1-halala rounding mismatch in Net Salary.

6. Rectifying the formula and obtaining approvals delayed final disbursement until March 12th.

The Consequences: Because payroll execution crossed the statutory grace period (10 days past month-end), Mudad automatically flagged the establishment with 0% Compliance for February. MHRSD systems initiated an automated suspension on Qiwa work permit renewals and recruitment quotas.
The Corrective Action Plan:

* Enforced strict automated Excel rounding macros (=ROUND(..., 2)) on all payroll workbooks.

* Configured dual-signatory backup roles on Al Mubasher Business, assigning secondary authorization power to the Finance Director to prevent executive bottlenecks.

Instituted a mandatory policy of executing payroll on the 25th of every month*, providing a 5-day safety cushion before statutory deadlines.


Strategic Checklist: Al Rajhi Corporate WPS Pre-Flight Protocol

Before authorizing a payroll file on Al Rajhi Al Mubasher Business, complete this 5-minute pre-flight verification:

Al Rajhi SIF Pre-Flight Protocol

Mandatory protections enforced by MHRSD & Saudi Labor Law

1
Verify Available Cleared BalanceConfirm corporate checking account contains total net wages plus buffer for transaction fees.
2
Verify Total Batch ParityEnsure Header H8 total equals internal approved gross payroll minus deductions down to the exact halala.
3
Review Inter-Bank SARIE ScheduleEnsure upload and approval occur before 03:00 PM KSA time on a business day.
4
Notify Checker ImmediatelyEnsure the authorized signatory is available with their Al Rajhi Token to authorize within 60 minutes.
5
Monitor Mudad Post-SettlementLog into Mudad 24 hours post-execution to verify that the compliance percentage reflects 100%.

Frequently Asked Questions (FAQ)

What file extension does Al Rajhi Corporate Banking require for WPS uploads?

Al Rajhi Al Mubasher Business strictly requires the `.sif` (Salary Information File) extension. If your payroll software exports the file as .csv or .txt, you must rename the file extension to .sif before attempting to upload it to the portal.

Can an employee receive their salary in a different bank than Al Rajhi?

Yes. Al Rajhi Corporate Banking processes salaries to all commercial banks licensed by SAMA in Saudi Arabia (such as SNB, Riyad Bank, Alinma, SAB, and Banque Saudi Fransi). Intra-bank transfers to Al Rajhi accounts credit instantly, while inter-bank transfers are processed via SAMA's SARIE clearing system.

What is the difference between Maker and Checker in Al Rajhi Corporate Banking?

The Maker (Initiator) is the user who uploads and prepares the payroll file on the portal, while the Checker (Signatory / Approver) is the executive authorized to review and approve the monetary debit using an authentication token or OTP. A single user cannot fulfill both roles for the same transaction under SAMA security regulations.

What happens if the Checker does not approve the payroll batch on time?

If the Checker does not authorize the uploaded batch within the platform's operational window (typically by 11:59 PM on the submission day or before the value date), Al Rajhi Bank automatically cancels the batch. The debit will not occur, salaries will remain unpaid, and the file must be re-uploaded from scratch.

How long does it take for Al Rajhi payroll to appear on Mudad?

After successful authorization and settlement by Al Rajhi Bank, the transaction data is transmitted to the SAMA WPS gateway and synchronized with Mudad within 2 to 24 hours. You can verify the updated compliance status directly on your Mudad establishment dashboard.