IBAN (UAE)

The International Bank Account Number — UAE's standardised 23-character bank account identifier required for WPS, IBFT, and virtually every inter-bank transaction. Format: 'AE' + 2 check digits + 3-character bank code + 16-digit account identifier.

Detailed Definition

An IBAN (International Bank Account Number) is the standardised account identifier required for inter-bank payments in the UAE since 2011. The IBAN replaced the legacy account-number system that varied across banks, providing a unified format that supports automated payment routing, validation, and error detection. For HR and payroll teams, IBAN is critical: a single mistyped IBAN in a WPS Salary Information File can cause the entire SIF to be rejected, delaying payroll for the whole establishment. Understanding IBAN structure, validation logic, and common error patterns is operationally essential.

**UAE IBAN structure.** The UAE IBAN is 23 characters long, structured as follows: (1) **2 letters** — country code, always 'AE' for UAE-issued IBANs. (2) **2 digits** — check digits computed using the ISO 13616 IBAN check algorithm. (3) **3 digits** — bank identifier (different banks have different codes; e.g., 030 for Emirates NBD, 033 for Mashreq, 060 for ADCB, 035 for FAB). (4) **16 digits** — the customer's specific account number within that bank. Example: `AE070331234567890123456` — where 'AE' is country, '07' is check digits, '033' is the bank (Mashreq), and '1234567890123456' is the account number.

**Why IBAN matters.** Several UAE financial workflows require the IBAN as the primary account identifier. (1) **WPS SIF files** — every employee row in the SIF must include the employee's IBAN. (2) **IBFT transfers** — the receiving account is identified by IBAN. (3) **SWIFT international transfers** — the IBAN is included in the beneficiary identifier for incoming international wires. (4) **Government salary disbursements** — for UAE Nationals receiving Nafis top-ups, the IBAN is the destination. (5) **Corporate vendor payments** — vendor payments use IBAN-based routing. The universal use of IBAN means any errors propagate widely.

**Validation logic.** IBAN validation runs through several checks. (1) **Length check** — UAE IBANs must be exactly 23 characters. (2) **Country prefix** — must start with 'AE'. (3) **Check-digit verification** — the 2 check digits at positions 3-4 are computed from the rest of the IBAN using ISO 13616 modulo-97 algorithm; a check-digit mismatch indicates a typo or corruption. (4) **Bank code validation** — the 3-digit bank identifier must match a recognised UAE bank. (5) **Account-number format** — though primarily numeric, some specific patterns may indicate invalid accounts. Modern HR systems run all five validations on IBAN import or entry, catching errors before they propagate to payment files.

**Common IBAN errors.** (1) **Typos in the account-number portion** — caught by check-digit validation if the typo affects the algorithmic relationship. (2) **Confusion between IBAN and account number** — the customer's debit card shows their account number, not the IBAN; many employees provide the wrong identifier when asked for an IBAN. The IBAN is typically found in the bank's mobile app under 'My Account Details' or in account opening documents. (3) **Bank-code-account mismatch** — copying an IBAN from one bank's portal but entering an account number that doesn't match. (4) **Spaces and formatting** — IBANs are sometimes printed with spaces every 4 characters for readability (`AE07 0331 2345 6789 0123 456`); HR systems should strip whitespace on import. (5) **Old IBAN after account closure** — employees who switch banks but provide their old IBAN cause WPS rejections.

**Onboarding workflows.** Best practice during employee onboarding is to (1) explicitly ask for the IBAN (not the account number), (2) provide instructions on how to find the IBAN in the bank's mobile app or statement, (3) validate the IBAN programmatically on entry, (4) confirm the IBAN belongs to a UAE bank that accepts WPS, (5) verify the account holder name matches the employee's registered name (some banks require exact matches), (6) capture the IBAN in the HR system before the first payroll cycle. Skipping this validation creates WPS rejections and delayed first paychecks.

**IBAN lookup channels.** UAE residents can typically find their IBAN through (1) the bank's mobile app — usually under account details or transfer-related screens, (2) the bank's internet banking portal — same locations, (3) bank statements — printed at the top of monthly statements, (4) account-opening documentation — provided when the account was first opened, (5) bank branch — staff can print or display the IBAN on request. Banks generally do not display IBANs on debit cards (cards show only the account number), which is a common source of confusion.

**IBAN for non-UAE banks.** Some employees may have salary accounts with international banks operating UAE branches (HSBC, Citi, Standard Chartered, Mashreq's UAE-ex-pat banking). These banks issue UAE IBANs in the standard format. Employees with offshore accounts (Channel Islands, Singapore, Switzerland) cannot receive WPS payments to those accounts — WPS requires a UAE-issued IBAN. Employees should establish a UAE bank account during onboarding before the first payroll cycle.

**IBAN privacy and security.** The IBAN is not particularly sensitive in itself — knowing an IBAN does not allow unauthorised debits — but it is personal data under PDPL (UAE Personal Data Protection Law) and should be handled appropriately. HR systems should restrict IBAN visibility to authorised payroll staff, encrypt IBAN data at rest and in transit, and audit-log access to IBAN information.

**IBAN changes during employment.** Employees occasionally change banks during their UAE tenure — for better service, lower fees, or simply because a new bank entered the market. When an employee changes IBAN, the HR system should (1) validate the new IBAN, (2) confirm the change in writing with the employee, (3) update the IBAN before the next WPS cycle so the new account receives the salary, (4) retain the historical IBAN in the employee record for audit purposes. Coordinating the timing matters: if the change happens after WPS file generation but before submission, regenerate the SIF rather than editing manually.

**Common compliance traps.** First, accepting an account number instead of an IBAN, leading to WPS rejection. Second, failing to validate IBAN structure on entry. Third, not updating the IBAN promptly when employees change banks. Fourth, transcribing IBANs manually from paper documents and introducing typos. Fifth, treating IBAN as non-sensitive when it is in fact personal data subject to PDPL.

**Automation through Peoplifi.** Peoplifi validates IBAN format on entry — length, country prefix, check digits, bank code — and refuses to save invalid IBANs without explicit override and warning. The validation runs both at single-employee onboarding and at bulk-import time. Generated WPS SIFs and IBFT files use the validated IBAN, eliminating most rejection causes. Audit logs track every IBAN change with timestamp and authorising user.

Automate IBAN (UAE) with Peoplifi

Peoplifi handles UAE payroll (WPS, end-of-service gratuity, Emiratisation, GPSSA), ZKTeco / Suprema biometric attendance, and IBFT bank-sheet export in one platform — so concepts like IBAN (UAE) stay handled, not stuck in spreadsheets.