Direct Answer / Quick Summary:

In the Kingdom of Saudi Arabia, corporate employers banking with Riyad Bank (بنك الرياض) or Alinma Bank (مصرف الإنماء) fulfill their statutory Wage Protection System (WPS / نظام حماية الأجور) obligations monitored by Mudad through their respective corporate banking portals:

Portal Navigation & File Gateways:*

Riyad Bank: Authorized users log into Riyad Corporate (رياض كوربوريت), navigate to Cash Management & Transfers (إدارة النقد والتحويلات) → Payroll & Wages (الرواتب والأجور) → WPS Salary Processing (نظام حماية الأجور - WPS) → Upload Payroll File (رفع ملف الرواتب)*.

Alinma Bank: Authorized users log into Alinma Business (الإنماء للأعمال), navigate to Corporate Banking (خدمات الشركات) → Salary Payments & WPS (دفع الرواتب وحماية الأجور) → Upload SIF File (رفع ملف الرواتب)*.

SAMA Bank Code & Header Specifics: SIF files must be formatted as comma-separated text files saved with a `.sif` extension encoded in UTF-8 (without BOM). Header records (`SCR`) must feature the bank's exact 4-letter SAMA identifier: `RIBL` for Riyad Bank (with corporate IBAN `SA..20...`) and `ALBI`* for Alinma Bank (with corporate IBAN SA..05...).

What is a "Sealed Payroll File"? A sealed payroll file is the cryptographically certified wage disbursement file generated and signed by the bank’s core processing engine upon successful settlement. This authenticated ledger proves fund deduction and beneficiary credit, enabling automated reporting to the SAMA Central WPS Switch and synchronization with the Mudad Compliance Platform within 2 to 24 hours*.

Dual-Role Authorization: Both portals mandate strict Maker-Checker governance. The Maker (Initiator / المنشئ) uploads and validates the batch, while the Checker (Signatory / المعتمد)* must authorize the transaction using hardware or mobile soft tokens (Riyad e-Token / Alinma Token) before the daily SARIE clearing cut-off (03:00 PM for Riyad Bank; 03:30 PM for Alinma Bank).


Statutory Foundation: Islamic & Commercial Banking in Saudi WPS

Under Article 90 of the Saudi Labor Law and circulars issued jointly by the Saudi Central Bank (SAMA) and the Ministry of Human Resources and Social Development (MHRSD), private sector wages must be paid through electronic banking pipelines that report disbursement records to the National Information Center.

Both Riyad Bank (one of the Kingdom's foundational commercial financial institutions) and Alinma Bank (a premier Sharia-compliant corporate banking institution) maintain specialized digital integration gateways with Mudad (منصة مُدد):

Statutory Compliance Note

Corporate ERP / SIF Generator ──> Riyad Corporate / Alinma Business Gateway ──[Batch Settlement]──> SAMA SARIE Switch ──[Sealed Record Feed]──> Mudad Compliance Ledger

Step 1HR / Payroll System

SIF Formatting

Formulate SAMA-standard SIF file with bank-specific code (RIBL or ALBI) and corporate IBAN

Step 2Portal Submission

Corporate Portal Upload

Maker uploads SIF file via Payroll & WPS services on Riyad Corporate or Alinma Business

Step 3Pre-Flight Audit

Syntax Pre-Validation

Core banking gateway verifies IBAN checksums, row arithmetic parity, and balance availability

Step 4Dual Approval

Token Authorization

Authorized Signatory (Checker) executes release using physical/mobile security token

Step 5Settlement Engine

Fund Execution

Bank debits corporate account; settles intra-bank accounts instantly and routes SARIE transfers

Step 6Compliance Record

Sealed File Generation

Bank generates cryptographically signed wage acknowledgment and transmits data to SAMA/Mudad

Failure to execute payroll through these designated corporate modules leaves salary payments untracked, resulting in Mudad reporting an establishment's compliance rate as 0%, which triggers automated work permit renewal blocks on Qiwa.


Operational Pre-Requisites for Riyad Bank & Alinma Corporate WPS

Before uploading a monthly payroll file on either platform, the establishment's finance department must ensure the following five conditions are met:

Mandatory Corporate WPS Pre-Requisites

Mandatory protections enforced by MHRSD & Saudi Labor Law

1
Active Corporate Portal AccessActive administrative credentials on Riyad Corporate or Alinma Business with provisioned Maker (Data Entry) and Checker (Signatory) roles.
2
Activated Payroll & WPS EntitlementsThe corporate account must have the WPS Payroll facility officially enabled through an authorized corporate branch or relationship manager.
3
Unencumbered Cleared FundsThe corporate debit checking account must hold cleared liquidity covering the total net wages plus transaction charges (SAR 1.50 to SAR 5.00 per transfer).
4
Bank Code AlignmentThe SCR header record must state 'RIBL' (for Riyad Bank) or 'ALBI' (for Alinma Bank), with the corporate debit IBAN strictly matching the account profile.
5
Strict SIF SyntaxFiles must be formatted as comma-separated values (.sif) encoded in UTF-8 without BOM, maintaining exact mathematical parity (Net = Basic + Housing + Other - Deductions).

Portal Comparison: Riyad Corporate vs. Alinma Business WPS Gateways

While both institutions comply with SAMA standards, their corporate interfaces feature distinct operational characteristics:

Architectural FeatureRiyad Bank (Riyad Corporate / رياض كوربوريت)Alinma Bank (Alinma Business / الإنماء للأعمال)
SAMA Bank Identifier`RIBL``ALBI`
Corporate IBAN PrefixSA..20...SA..05...
File Extensions Supported.sif, .csv, .txt.sif, .csv
Authentication TokenRiyad Mobile Corporate Token / Physical DigipassAlinma Token Mobile App / Hardware e-Token
SARIE Inter-Bank Cut-Off03:00 PM KSA Time (Business Days)03:30 PM KSA Time (Business Days)
Intra-Bank Processing SpeedInstantaneous (24/7/365) to Riyad accountsInstantaneous (24/7/365) to Alinma accounts
Sealed File Export NameWPS Acknowledgment File / إشعار حماية الأجورSAMA Wage Confirmation / إشعار حماية الأجور المعتمد

Step-by-Step UI Guide: Uploading SIF File on Riyad Corporate Banking

Follow this operational workflow to submit and authorize a payroll batch on Riyad Corporate:

Step 1: Secure Login to Riyad Corporate

1Navigate to the official portal: https://www.riyadbank.com/corporate.
2Enter your Organization ID (معرف المنشأة), User ID (اسم المستخدم), and Password (كلمة المرور).
3Authenticate using the dynamic passcode from the Riyad Token Mobile App.

Step 2: Navigate to WPS Payroll Management

1From the top navigation bar, click on Cash Management & Transfers (إدارة النقد والتحويلات).
2Select Payroll & Wages (الرواتب والأجور) from the dropdown menu.
3Click on WPS Salary Processing (نظام حماية الأجور - WPS).
4Select Upload Payroll File (رفع ملف الرواتب).

Step 3: Configure Payroll Batch Metadata

Debit Account (الحساب المخصوم منه): Select the corporate operational IBAN (SA..20000...).
Payroll Purpose / Description (وصف الدفعة): Input a clear label without spaces or special symbols (e.g., SALARY-MAR-2026).
Value Date (تاريخ الاستحقاق): Select today's date for immediate execution or a future scheduled date.

Step 4: Browse and Upload the SIF File

1Click Browse / Choose File (اختيار ملف).
2Select your validated .sif file (e.g., PAYROLL_MAR_2026.sif).
3Click Upload & Validate (تحميل والتحقق).

Step 5: System Pre-Audit Validation

Riyad Bank's gateway performs an automated syntax validation:

Confirms total employee row count (EDR lines).
Validates that the sum of Column K equals the amount in Header Field H8.
Checks that all beneficiary IBANs conform to SAMA checksum rules.
Displays a summary breakdown of Riyad accounts vs. SARIE inter-bank accounts.

Step 6: Submit to Authorization Queue (Maker Action)

Click Submit for Authorization (إرسال للاعتماد). The system assigns a unique Riyad Batch Reference Number (رقم مرجع الدفعة).

Step 7: Authorize the Batch (Checker Action)

1The authorized signatory logs into Riyad Corporate.
2Go to Approvals / Pending Tasks (الاعتمادات / المهام المعلقة).
3Select the pending WPS payroll batch under Payroll (الرواتب).
4Review the total sum, employee headcount, and debit account.
5Click Approve (اعتماد).
6Input the 6-digit challenge code generated by the Riyad Soft Token.
7Click Confirm (تأكيد). The system displays: "Transaction Successfully Submitted to SAMA WPS" (تم إرسال المعاملة بنجاح إلى نظام حماية الأجور).

Step-by-Step UI Guide: Uploading SIF File on Alinma Business

Follow this sequence to upload and authorize a payroll batch on Alinma Business:

Step 1: Secure Login to Alinma Business

1Navigate to: https://business.alinma.com.
2Enter your Corporate ID (معرف المنشأة), Username (اسم المستخدم), and Password (كلمة المرور).
3Authenticate via the Alinma Token App (تطبيق الإنماء توكن) push notification or OTP.

Step 2: Navigate to Salary Payments

1From the main dashboard, select Corporate Services (خدمات الشركات).
2Click on Salary Payments & WPS (دفع الرواتب وحماية الأجور).
3Click on Upload SIF Payroll File (رفع ملف الرواتب SIF).

Step 3: Set Batch Parameters

Account Number (رقم الحساب): Select the company's Alinma operational checking account (SA..05000...).
File Type (نوع الملف): Select WPS SIF (نظام حماية الأجور).
Batch Reference (المرجع): Enter an alphanumeric label (e.g., ALINMA-MAR-2026).
Execution Date (تاريخ الصرف): Select the execution date.

Step 4: Upload and Audit File

1Click Browse (استعراض) and select the .sif file.
2Click Validate File (التحقق من الملف).
3Alinma's system verifies mathematical parity, missing fields, and IBAN validity.
4Review the verification report confirming employee count and total SAR value.

Step 5: Submit for Signatory Approval (Maker Action)

Click Submit for Approval (إرسال للاعتماد). The batch moves into the corporate approval workflow.

Step 6: Execute Signatory Release (Checker Action)

1The authorized signatory logs into Alinma Business.
2Navigate to Pending Approvals (العمليات بانتظار الاعتماد).
3Under Salary Transactions (عمليات الرواتب), select the pending batch.
4Inspect the batch summary details.
5Click Approve & Release (اعتماد وصرف).
6Authenticate using the dynamic passcode from the Alinma Token.
7Click Confirm (تأكيد). The platform confirms: "Batch Approved - Funds Disbursed via SAMA WPS" (تم اعتماد الدفعة وصرف الرواتب بنجاح).

Technical SIF File Specifications for Both Banks

To guarantee that your payroll batch passes the gateway on the first attempt, your SIF file must conform to these exact specifications:

1. Header Record (SCR) Layout: Riyad Bank vs. Alinma Bank

Riyad Bank SIF Header Example:

code|Technical Specification / Reference
Verified Schema
SCR,7001234567,RIBL,2026-03-03,1100,SA2020000123456789012345,6,38000.00,SAR,SAL-MAR-2026
Field H3: Must strictly be RIBL.
Field H6: Must begin with SA20 (Riyad Bank corporate checking account).

Alinma Bank SIF Header Example:

code|Technical Specification / Reference
Verified Schema
SCR,7001234567,ALBI,2026-03-03,1100,SA0500000123456789012345,6,38000.00,SAR,SAL-MAR-2026
Field H3: Must strictly be ALBI.
Field H6: Must begin with SA05 (Alinma Bank corporate checking account).

2. Employee Detail Record (EDR) Architecture

Every subsequent row represents an employee and follows the 12-column SAMA specification:

code|Technical Specification / Reference
Verified Schema
EDR,2,2432109876,Zubair Al-Farooq,RIBL,SA2020000456123456789012,6000.00,1500.00,500.00,500.00,7500.00,30
EDR,2,2487654321,Kamal Abdulshakoor,ALBI,SA0500000789123456789034,5000.00,1250.00,250.00,350.00,6150.00,30
EDR,1,1045678901,Nawaf Al-Mutairi,NCBK,SA1210000222333444555666,7500.00,1875.00,1000.00,750.00,9625.00,30
Intra-Bank Beneficiaries: If paying from a Riyad account to a worker's Riyad IBAN (RIBL), or from an Alinma account to an Alinma IBAN (ALBI), funds credit immediately 24/7/365.
Inter-Bank Beneficiaries: Routing to external banks (e.g., SNB NCBK or Al Rajhi RJHI) executes via SARIE during business operating windows.

What is a "Sealed Payroll File" and How to Download It?

A Sealed Payroll File (ملف الرواتب المعتمد / المشفر) is the formal digital output generated by the corporate banking platform after a payroll batch has been fully executed.

Why the Sealed File is Vital for Compliance:

1Cryptographic Proof of Payment: It contains the bank's digital signature, unique SAMA transaction hash, and exact execution timestamp down to the second.
2Emergency Mudad Reconciliation: If the automated bank-to-Mudad transmission pipeline experiences a synchronization delay, the employer can manually upload this sealed file to Mudad's Compliance Monitoring System (نظام الالتزام) to instantly achieve compliance.
3Legal Protection in Labor Disputes: Serves as irrefutable statutory evidence under Article 90 in the event of Labor Court (Waddi) claims.

Downloading the Sealed File from Riyad Corporate:

1Log into Riyad Corporate.
2Navigate to Cash Management & Transfers → Payroll & Wages → Payroll Reports (تقارير الرواتب).
3Locate the executed batch.
4Click Download WPS Acknowledgment File (تحميل إشعار حماية الأجور).
5Save the encrypted file (.sif or .ack format).

Downloading the Sealed File from Alinma Business:

1Log into Alinma Business.
2Navigate to Salary Payments & WPS → Executed Batches (الدفعات المنفذة).
3Select the processed payroll transaction.
4Click Export SAMA Wage Confirmation File (تصدير ملف حماية الأجور المعتمد).
5Save the authenticated digital ledger.

Mudad Synchronization & Compliance Verification

Once Riyad Bank or Alinma Bank executes a payroll batch, the compliance process transitions to Mudad:

How the Bank Feed Synchronizes with Mudad:

1Core Banking Transmission: The bank's central payment engine transmits the sealed transaction log to the SAMA Central WPS Gateway.
2Automated Ingestion: Mudad pulls the file, decrypts the transaction details, and matches each employee's civil ID against registered contracts on Qiwa and GOSI.
3Timeline: The establishment's compliance score updates within 2 to 24 hours.

Verifying Compliance on Mudad:

1Log into Mudad (منصة مُدد) (mudad.com.sa) via Absher Business / Nafath.
2Select your establishment profile.
3Go to Wage Protection System (نظام حماية الأجور - WPS) → Payroll Files (ملفات الرواتب).
4Confirm that the batch appears with status: "Approved & Processed" (معتمد ومعالج).
5Confirm that the Compliance Rate (نسبة الالتزام) meets or exceeds 80%.

Troubleshooting 7 Common Errors on Riyad Bank & Alinma Gateways

When a payroll batch fails validation on either portal, consult this diagnostic reference:

Error String / CodeSystem Root CauseImmediate Rectification Protocol
`Bank Code Mismatch (Header H3)`Header specifies wrong bank code (e.g., RJHI entered on Riyad Corporate, or RIBL entered on Alinma).Open file in text editor. Ensure Field H3 is RIBL for Riyad Bank or ALBI for Alinma Bank.
`Payer IBAN Mismatch (Header H6)`Header corporate IBAN does not match the company checking account selected on the portal interface.Correct Field H6 to match the exact 24-character corporate checking IBAN (SA..20... or SA..05...).
`Arithmetic Parity Mismatch (Row X)`Column K does not equal Basic + Housing + Other − Deductions due to floating-point rounding errors.In Excel, apply =ROUND((G+H+I)-J, 2) to Column K for all rows. Ensure two decimal places throughout.
`Insufficient Cleared Liquidity`Available balance is less than total net wages plus transaction charges.Transfer additional operational capital into the debit account and re-submit the batch.
`Authorization Window Expired`Maker submitted the batch, but Checker failed to authorize it before the platform cut-off.The expired batch is automatically cancelled. The Maker must re-upload the SIF file as a fresh batch.
`Invalid Beneficiary Account Status`An employee's bank account is closed, dormant, or restricted under SAMA KYC rules.Review the bank rejection report to identify the affected row. Request an active IBAN letter from the worker.
`Encoding Garble (BOM / ANSI Error)`File saved as UTF-8 with BOM or ANSI, causing system parsing failure on Arabic names.Re-save the file in Notepad or Excel as UTF-8 without BOM.

Real-World Corporate Case Study: Medina Hospitality Group

To see how bank-specific configurations impact real-world compliance, examine this verified case:

The Operation: A hospitality management group operating three boutique hotels in Medina employing 110 staff members (executive chefs, front desk staff, and housekeeping teams).
The Situation:

The group maintains operational accounts at both Alinma Bank (for administrative and management payroll) and Riyad Bank* (for hotel operational staff).

* On February 27th, the payroll accountant prepared two SIF files: 35 employees on Alinma and 75 employees on Riyad Bank.

The Crisis:

1. Alinma Failure: The Alinma file failed validation instantly with Parsing Error in Line 14. An expatriate French pastry chef's name had been entered with an unescaped comma (Dubois, Jean-Pierre), splitting the line into 13 columns.

2. Riyad Bank Failure: The Riyad Bank file was uploaded by the Maker at 01:30 PM. However, the Chief Financial Officer (Checker) was traveling and discovered that his physical hardware token battery had died, leaving him unable to authorize the batch.

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

4. With both batches stalled, month-end passed without salary disbursements, triggering an automated non-compliance warning on Mudad.

The Forensic Resolution:

Alinma:* The accountant stripped the comma from the chef's name and re-uploaded the file to Alinma Business. The General Manager approved it via the Alinma Token mobile app in under 2 minutes.

Riyad Bank: The group visited their local Riyad Bank corporate branch and activated the Riyad Mobile Soft Token* on the CFO's smartphone, replacing the defunct physical token. The batch was re-uploaded and authorized by 10:00 AM.

Within 12 hours of settlement, both sealed wage files were ingested by Mudad, restoring the group's compliance score to 100%* and preventing any MHRSD recruitment sanctions.


Executive Pre-Flight Checklist: Riyad & Alinma Corporate WPS

Before releasing a payroll file on Riyad Corporate or Alinma Business, execute this 5-point verification routine:

Pre-Flight Corporate WPS Protocol

Mandatory protections enforced by MHRSD & Saudi Labor Law

1
Verify SAMA IdentifierEnsure Header H3 is strictly 'RIBL' for Riyad Bank or 'ALBI' for Alinma Bank.
2
Confirm Debit IBANEnsure Header H6 matches the paying account prefix (SA..20... for Riyad; SA..05... for Alinma).
3
Audit Net ParityVerify that Column K equals Basic + Housing + Other - Deductions down to the exact halala.
4
Authorize Before Cut-offComplete Checker authorization before 03:00 PM (Riyad) or 03:30 PM (Alinma) on business days.
5
Export Sealed AcknowledgmentDownload the signed bank confirmation file and verify 100% compliance on Mudad within 24 hours.

Frequently Asked Questions (FAQ)

What are the official SAMA bank codes for Riyad Bank and Alinma Bank in SIF files?

The official SAMA bank code for Riyad Bank is `RIBL`, and for Alinma Bank it is `ALBI`. These codes must appear in Field H3 of the SCR header record and in Column E for employees banking with these institutions.

What is a "Sealed Payroll File" in Saudi WPS?

A sealed payroll file is the cryptographically verified and digitally signed wage disbursement ledger produced by the corporate bank after funds have settled. It confirms payment execution and is transmitted through the SAMA switch to Mudad.

What are the daily SARIE clearing cut-off times for Riyad Bank and Alinma Bank?

For same-day inter-bank payroll clearing via SARIE, the cut-off time is 03:00 PM KSA time on Riyad Corporate and 03:30 PM KSA time on Alinma Business on business days (Sunday through Thursday). Transfers within the same bank process 24/7 in real-time.

Can I upload a SIF file saved as .csv on Alinma Business and Riyad Corporate?

Yes. Both portals accept .sif and .csv files, provided the internal structure complies strictly with SAMA's comma-separated format without extra headers, spaces, or currency symbols. If an upload error occurs, simply rename the file extension to .sif.

How do I resolve an "Authorization Expired" error on these corporate banking platforms?

Corporate banking portals cancel unapproved payroll batches after a set period (typically by 11:59 PM on the submission day). If a batch expires, the Maker must upload the SIF file again as a new batch, and the Checker must authorize it promptly using their security token.