Salary transfer files for Jordanian banks: format, IBAN and common errors
What a bulk salary file for a bank in Jordan usually contains, how to get the format, encoding and IBANs right, and the errors that most often get a file rejected.
Most companies in Jordan with more than a handful of employees pay salaries through a bulk transfer: the payroll produces one file with every employee's account and net pay, and the finance team uploads it to the bank's corporate online banking or hands it to the bank's payroll service. When the file is right, payday takes minutes. When it is wrong, the bank rejects it, or worse, accepts it and some salaries bounce back days later. This guide explains how these files are usually built and what to check before upload. If you want the file produced straight from payroll, see salary bank files from Aspirations payroll; the net amounts themselves come from payroll.
There is no single national format
The first thing to know is that each bank defines its own salary file. Two banks may ask for the same information in a different order, with different separators, different date formats and different rules for names. Some accept Excel, some CSV, some a fixed-width text file where every field sits at an exact character position. Even within one bank, the format for the online portal can differ from the one used by the branch payroll service. The only reliable source for your format is your bank's own specification, normally given by your relationship manager or the cash management team when the payroll service is set up. Ask for it in writing, with a sample file, and keep it with your payroll procedures.
What a salary file usually contains
Most formats follow the same three-part pattern, whatever the file type.
Header
One line at the top describing the batch: the company's debit account or IBAN, the value date (the day salaries should reach employees), a batch or file reference, the currency, and often the number of records and the total amount.
Detail lines
One line per employee:
| Field | Typical content | Watch out for |
|---|---|---|
| Employee name | Name as held by the receiving bank | Arabic or Latin script, maximum length |
| IBAN | 30 characters starting with JO | Spaces, lowercase letters, old account numbers |
| Amount | Net pay in JOD | Number of decimals, decimal separator |
| Bank or branch code | Sometimes required for other banks | Must match the IBAN |
| Employee number / reference | Your internal ID | Shown on the employee's statement |
| Purpose / narrative | e.g. "Salary November 2026" | Length limits, allowed characters |
Trailer
One line at the end with control totals: the record count and the sum of amounts. The bank compares them with the detail lines; if one employee was added or removed by hand without updating the trailer, the whole file is rejected. That is deliberate, and a good reason never to edit a salary file manually.
File type: CSV, Excel or fixed width
- CSV is easy to produce and read, but watch the separator (comma or semicolon) and any comma inside names or narratives. Opening and re-saving a CSV in Excel can silently change it: leading zeros disappear and long numbers can turn into scientific notation.
- Excel templates are common for smaller payrolls. Keep the bank's template untouched; adding a column or renaming a sheet is a frequent cause of rejection.
- Fixed width text files leave no room for guessing: every field has a start position and length, numbers are padded with zeros and text with spaces. One character out of place shifts every field after it.
Arabic names and encoding
Employee names in Arabic raise an encoding question that catches many first uploads. Some bank systems expect the older Arabic Windows code page (Windows-1256), others expect UTF-8, and some accept Latin names only. A file saved in the wrong encoding shows names as question marks or strange symbols, and the bank may reject it or pass on corrupted names. Ask the bank three questions: which script, which encoding, and whether a byte-order mark (BOM) at the start of a UTF-8 file is acceptable. Then test with one or two employees before the first full payroll.
Getting IBANs right
Salaries are now normally transferred by IBAN rather than by the old local account number. A Jordanian IBAN is 30 characters, as Jordanian banks describe it: the country code JO, two check digits, a four-letter bank code, a four-digit branch code and the account number, padded to fill the remaining positions. The IBAN does not replace the account; it wraps the existing account number in a standard structure.
The two check digits make it possible to validate an IBAN before the bank does. The standard mod-97 check (from ISO 13616) catches most typing errors, such as a swapped pair of digits. Run it when an employee's IBAN is first entered, not on payday. A valid check does not prove the account belongs to the employee, so ask for the IBAN from the bank's own document, such as a bank letter or the banking app screen, rather than a number typed in a message. We could not find a published Central Bank of Jordan circular stating the length, so if your bank tells you anything different, follow your bank.
Amounts and rounding
Jordanian salaries are calculated to the fils, three decimals. Some bank formats accept three decimals, some want the amount without a decimal point (in fils), and some round to fewer decimals. Agree the rule with the bank and make sure the total in the trailer is the sum of the rounded amounts, not of the unrounded payroll figures; otherwise the control total is off by a few fils and the file fails.
The errors that get files rejected
- Record count or total in the header or trailer does not match the detail lines.
- An IBAN with spaces, lowercase letters, a missing character or a failed check.
- Wrong encoding, so Arabic names arrive garbled.
- A value date that is a weekend, an official holiday or already in the past.
- The bank's template changed by hand: extra columns, renamed headers, merged cells.
- An employee with a zero or negative net pay left in the file.
- A closed or dormant account, which usually comes back as a returned transfer a few days later.
Controls before you upload
Before upload, compare three totals: the net pay of the approved payroll, the total in the file, and the amount you expect to leave the company account. They should be identical. After the transfer, salaries payable in the books should return to zero; our guide to payroll journal entries shows the entries. Treat the file as sensitive personal data: limit who can generate and upload it, use the bank portal's maker and checker approval if it offers one, and avoid sending salary files by plain email. Jordan's Personal Data Protection Law No. 24 of 2023 applies to this kind of employee data.
When you evaluate payroll software, the bank file is one of the questions in our guide on how to choose payroll software in Jordan.
How Aspirations produces bank files
Aspirations payroll generates a salary file per bank from editable templates. Templates are seeded for a generic Jordanian layout, Arab Bank, Housing Bank, Jordan Kuwait Bank, Cairo Amman Bank and Bank al Etihad, and for Saudi payrolls WPS/Mudad SIF and CSV. Every template is confirmed with your bank during setup; none is presented as approved by a bank. IBANs are validated (mod-97 and the JO or SA structure) when the employee is saved, so errors are caught months before payday, and files are produced only from approved payroll runs. Plans are being finalised; a free trial is available.
This guide is general information. The format, encoding and cut-off times for your salary file are set by your bank, so confirm them with the bank before your first upload.
