SWIFT Code UAE vs IBAN: Getting Inbound Wire Instructions Right

A SWIFT code is the 8 or 11-character address that identifies a bank on the global payments network — Emirates NBD Dubai is EBILAEAD, RAKBank is NRAKAEAK. It identifies the institution, never the account. The IBAN identifies the account inside it. An international wire into the UAE needs both, and neither substitutes for the other.

Every international payment into a UAE business bank account needs two pieces of routing information: a SWIFT/BIC code that addresses the bank globally, and an IBAN that addresses your specific account inside that bank. They aren’t interchangeable, and you can’t drop either one. Get one wrong and the payment lands in suspense at a correspondent bank, costs days of delay, and triggers fees the payer won’t absorb cheerfully.

The cost is rarely visible on any single transaction, which is what makes it easy to miss. A UAE SME receiving regular USD wires from international clients can lose real money over a year to correspondent fees, recall charges and FX-spread leakage that proper payment instructions would have prevented.

This guide explains how SWIFT and IBAN work for UAE business banking, the payment instructions to send to every customer, the charge basis decisions that determine who pays the correspondent fees, and the routine errors that cost real money.

What a SWIFT code actually is (the BIC, decoded)

SWIFT is the global messaging network for international bank payments. Every bank that participates has a unique Business Identifier Code (BIC), commonly called the “SWIFT code”. So when someone asks whether BIC and SWIFT are the same thing, the answer is yes — BIC is the formal name for the code and SWIFT is the network that uses it, and in day-to-day banking the two words are used interchangeably. Payers in some markets will call it a routing code, a routing number, a clearing code or a sort code instead, because that is the vocabulary their domestic system uses. Those domestic identifiers are not the same as a BIC, and a UAE inbound wire needs the BIC. If a customer asks you for a routing number, what they need from you is the SWIFT/BIC and the IBAN.

The code is either 8 or 11 characters:

• First 4: bank code (e.g. EBIL for Emirates NBD)
• Next 2: country code (AE for UAE)
• Next 2: location code (AD for Dubai, AA for Abu Dhabi)
• Optional last 3: branch code (XXX or omitted for head office)

Decode a real one and the logic is obvious. EBILAEAD breaks into EBIL (Emirates NBD’s institution code) + AE (United Arab Emirates) + AD (the Dubai location code). ADCBAEAA is ADCB + AE + AA, and that trailing AA is the Abu Dhabi location code rather than Dubai’s AD. This is why a SWIFT code tells you the bank and roughly where it sits, and tells you precisely nothing about whose account the money is for — that part is the IBAN’s job, which is the distinction the next section covers.

Common UAE bank codes

Always confirm the exact code on your bank’s account statement or current website. Branch-specific SWIFTs exist for some banks, particularly the legacy networks at Mashreq and ENBD. A code that works for one customer’s wire today may be re-pointed by the bank tomorrow if they consolidate branches — keep your payment instructions refreshed every 12 months.

The 23-character UAE IBAN format

A UAE IBAN (International Bank Account Number) is 23 characters and starts with AE. That fixed IBAN format is the same across every UAE bank, and your account number sits inside it. It encodes the country, two check digits, the bank’s identifier, and your specific account number — all in a format that international banking systems can validate before they send the wire. That is the whole of the IBAN meaning: not a separate account, just your existing account number wrapped in a standard international envelope.

Where do you find your IBAN number? It is printed on your account statement, shown in your online and mobile banking under account details, and included on the IBAN letter or account confirmation letter the bank issues on request. That letter is the version to send to a customer, because it carries the bank’s letterhead and removes any argument about whether the details were transcribed correctly. If you want to check an IBAN number before sending it out, the safest check is against the bank’s own statement rather than a third-party IBAN checker or generator — those tools validate the format and the check digits, which tells you the number is well-formed, not that it belongs to you. A well-formed IBAN pointing at the wrong account passes every automated check there is.

Example structure:

AE 07 033 1 2345678901234 56
^^  ^^  ^^^ ^^^^^^^^^^^^^^^^
|   |   |   |               
|   |   |   Specific account number (16 digits)
|   |   Bank identifier (3 digits, assigned to the bank)
|   Check digits (2 digits — calculated from the rest)
Country code (AE = United Arab Emirates)

The check digits let the sending bank validate the IBAN before transmitting. Most modern banking systems reject obviously invalid IBANs at the point of entry — but a transcription error that produces a different valid IBAN will route the payment to the wrong account holder. That is when recovery gets expensive. In short, the IBAN for a UAE bank transfer is the field that has to be exactly right, because a valid-but-wrong number sails through validation and lands in someone else’s account.

What a complete inbound wire instruction looks like

A complete payment instruction template includes seven fields. Anything less and the payer’s bank will either reject the wire or send it with incomplete information that the receiving UAE bank must clarify manually.

Standard USD wire instruction

Beneficiary Name: [Exact legal name on your UAE trade licence]
Beneficiary Address: [Full UAE office address]
Beneficiary Account Number / IBAN: AE07 0331 2345 6789 0123 456
Beneficiary Bank Name: Emirates NBD PJSC
Beneficiary Bank Address: Baniyas Street, Deira, Dubai, UAE
Beneficiary Bank SWIFT/BIC: EBILAEAD
Intermediary Bank (USD): JPMorgan Chase Bank N.A., New York
Intermediary Bank SWIFT: CHASUS33
Charges: OUR
Payment Reference: [Your invoice number]

For EUR wires, the intermediary is typically Deutsche Bank Frankfurt (DEUTDEFF) or a similar Eurozone bank. For GBP wires, HSBC London (HBUKGB4B) or Barclays London. Your UAE bank publishes the current correspondent for each currency on its corporate banking site or on request from your relationship manager.

Why the intermediary matters

USD payments do not travel directly from a sender in Singapore to a receiver in the UAE. They travel through the USD clearing network, which means a correspondent bank in the United States holds the USD nostro account for your UAE bank. The wire moves from the sender’s bank to JPMorgan Chase (or similar), then JPMorgan credits your UAE bank’s USD account, then the UAE bank credits your IBAN.

If the sender’s bank doesn’t have JPMorgan in its routing table, the wire takes an extra hop through another correspondent. Each extra hop adds correspondent fees and another day or two of delay. Naming the intermediary directly on your payment instructions cuts the wire down to two clean hops.

What is a routing code in the UAE, and does one exist?

This is the question that stalls more inbound payments to UAE businesses than any other, because the answer is not the one the payer’s form is expecting.

The United States uses a nine-digit ABA routing number to identify a bank domestically. India uses an IFSC. The United Kingdom uses a six-digit sort code. The UAE does not use any of them. There is no UAE equivalent of an ABA routing number that a foreign payer can type into a field labelled “routing number”, and there is nothing to look up. When an overseas customer, a payroll platform or an accounts-payable system asks a UAE supplier for a bank account routing number, it is asking a question shaped by a different country’s payment rails.

What the payer actually needs, and what their system is trying to obtain, is the pair this article is about:

So the short answer to “what is my routing code” is: give them the SWIFT code. If their form will not accept letters in a numeric field, that is a limitation of their system, and the fix is to ask them to process it as an international wire rather than a domestic transfer — not to invent a number.

Clearing code versus SWIFT code

People reach for “clearing code” and “SWIFT code” as though they were interchangeable, and they are not. A clearing code is a domestic identifier used inside one country’s own settlement system. A SWIFT code, properly a BIC, is an international identifier registered in the SWIFT directory that works from anywhere. For money crossing a border into the UAE, the SWIFT/BIC is the operative identifier and the domestic clearing concept simply does not arise for the payer.

Inside the UAE there is a domestic identifier, but it is not something you hand to a foreign payer. Your bank is identified within the IBAN itself by the three-digit bank identifier sitting after the check digits. That is embedded in the number you are already giving out. There is nothing separate to disclose.

Salary transfers and the routing question

A common version of this comes up on payroll. An employer setting up a salary transfer, or an employee giving their details to an HR system built abroad, is asked for a routing code, and the same answer applies: the bank’s SWIFT/BIC for anything international, and the IBAN for the account. For salary transfers made within the UAE through the Wage Protection System, the employer’s bank and its WPS agent handle the routing between them from the details in the salary file — the employee provides an IBAN, not a routing number.

If a specific institution’s system insists on a value you cannot supply, get the answer from the bank rather than from a search result. Ask for a written IBAN or account confirmation letter and ask them explicitly which identifier to give a payer in that country. It is a five-minute request and it removes the guesswork permanently.

When an intermediary bank SWIFT code is needed

An intermediary or correspondent bank sits between the payer’s bank and yours when the two have no direct relationship in the currency being sent. It is common on USD payments, where the chain typically runs through a correspondent in the United States before reaching the UAE.

Two rules keep this from going wrong. First, the intermediary bank SWIFT code is not a property of your account — it is a property of the corridor, so it can differ by currency and can change when your bank changes correspondent. Never copy one from an old email or a forum post. Second, ask your own bank, in writing, whether an intermediary is required for the currency your customer is sending and, if so, exactly which SWIFT code and account reference to quote. Put the answer on your standard payment instruction template alongside the IBAN and BIC, and review it once a year.

Where an intermediary is involved, the charging option matters more than usual, which is what the next section is about: each bank in the chain can take its cut from the principal unless the sender covers them.

OUR, SHA, BEN — who actually pays

Every SWIFT wire carries a charge code that determines how correspondent and beneficiary bank fees are split.

The default at most international banks is SHA. Unless you specify OUR in your payment instructions, the payer’s bank will route under SHA, and you will receive the wired amount minus whatever correspondent fees apply along the way.

For a USD 10,000 invoice payment:

• OUR: you receive the full USD 10,000; the payer’s bank charges them extra for electing OUR
• SHA: you receive USD 10,000 minus whatever correspondent and receiving fees apply; the payer’s bank charges them only their own outbound fee
• BEN: you receive USD 10,000 minus all correspondent and receiving fees, deducted before the funds reach you; the payer’s bank charges them nothing extra

For B2B invoices where the receiver expects the full amount, specify OUR. For consumer payments or low-value transfers where the payer is price-sensitive, SHA may be acceptable. BEN is almost never the right choice for UAE inbound business wires.

“

The default charge basis at most international banks is SHA. Unless you explicitly specify OUR in your payment instructions, you will receive the wired amount minus whatever correspondent fees apply along the way.

Three common inbound-wire errors

Three common errors and what they cost:

Error 1 — wrong SWIFT code

The payer enters EBILAEAD when your bank is actually Mashreq (BOMLAEAD). The wire arrives at Emirates NBD, who returns it to the sender’s bank under “beneficiary not found”. The sender’s bank holds the funds in suspense for several days, then returns with a recall fee.

Total cost: days of delay, a recall fee, plus the original transfer fee — and the payer has to resend.

Error 2 — truncated or missing intermediary

The payer’s bank does not have your UAE bank in its primary correspondent table, so it routes through a secondary correspondent which routes through a tertiary correspondent. Each hop adds its own correspondent fee.

Total cost: extra days of delay and additional correspondent fees stacked on a single wire.

Error 3 — SHA on a B2B invoice

The payer wires USD 10,000 under SHA because their system defaulted to it. You receive less than the full amount. Your bookkeeper has to chase the shortfall against the invoice for AR reconciliation.

Total cost per wire: the correspondent-fee shortfall, plus reconciliation overhead that compounds across every misdirected payment in the year.

A 30-minute fix that pays for itself

For UAE SMEs with recurring international customers, the fix is structural rather than transactional.

Step 1. Get the correct payment instructions from your bank, in writing. Include beneficiary name (exact legal name on the trade licence), beneficiary address, IBAN, bank name, bank SWIFT, intermediary bank and intermediary SWIFT for each currency you accept.

Step 2. Build one PDF template per currency. USD, EUR, GBP and CNY are the common ones. Include the OUR charge basis as a default.

Step 3. Attach the PDF to every customer onboarding email and every invoice. Make it part of your standard customer communication, not an afterthought.

Step 4. Refresh the template every 12 months or whenever your bank notifies you of a correspondent bank change. UAE banks do switch USD correspondents from time to time, and outdated payment instructions can cause real misrouting when that happens.

Step 5. Reconcile inbound wires against expected amounts monthly. Any shortfall is a charge-basis or correspondent-fee issue — address with the payer, not the bank.

One more habit worth building into the same template. When a customer tells you a wire transfer has gone out, ask them for the SWIFT copy — the MT103 confirmation their bank produces once the payment is sent. It carries the reference, the value date, the charge basis actually applied and the intermediary chain the payment took. When a payment goes missing, that document is what lets your bank trace it, and asking for it after the fact usually costs several days. Requesting it as routine turns a week of email into a single tracing request.

Our accounting and bookkeeping team handles this as part of the standard monthly cycle for SME clients with international customers. The reconciliation catches charge-basis defaults at the second occurrence and lets us redirect the customer to OUR.

Where this leaves you

If you are a UAE SME receiving international payments, most of the value comes down to a few habits. Quote both the SWIFT and the IBAN on every payment instruction and never substitute one for the other, because the IBAN alone won’t carry an international wire and the SWIFT alone reaches the bank but not your account. Specify OUR charges on B2B invoices, which saves correspondent fees on every wire and clears the reconciliation noise out of your monthly bookkeeping. And name the intermediary bank for your USD, EUR, GBP and CNY wires, since that alone cuts the unnecessary correspondent hops and speeds up clearing time.

None of this requires a new bank or a new product. It needs a 30-minute setup of correct payment instructions, distributed once to every customer, refreshed every 12 months. The annual cost saving routinely covers the bookkeeping fee that maintains the FCY reconciliation in the first place.

If you want to extend beyond pure inbound wires, our multi-currency business account guide compares the FX spreads and FCY-holding economics at Wio, Mashreq NeoBiz, ENBD and FAB. And if you are still opening your first UAE business bank account, the UAE business bank account guide walks through the document pack and rejection-avoidance steps, while freelancers and sole establishments should start with the freelancer bank account guide.

For SMEs operating across mainland and free zones, the banking setup connects directly to UAE corporate tax and VAT compliance — the FTA reconciles bank inflows against return filings during audits.

When SWIFT isn’t the cheapest rail

For UAE-to-UAE transfers between local banks, the domestic payment rail is UAEFTS (UAE Funds Transfer System) operated by the Central Bank. Most transfers between UAE business accounts clear same-day at minimal to no cost — no SWIFT routing needed because the payment never leaves the UAE clearing network. Always confirm the receiving bank is in the UAE before defaulting to SWIFT instructions.

For UAE-to-Saudi Arabia transfers, the SARIE network is the Saudi domestic rail and most UAE banks can route AED-to-SAR transfers through SARIE without full SWIFT overhead, particularly the major banks (ENBD, FAB, ADCB). Settlement is same-day or next-day at materially lower cost than international SWIFT.

For UAE-to-GCC transfers more broadly, the AFAQ instant payment network connects GCC central banks for retail and small commercial payments. Coverage is expanding through 2026 and the cost structure is more favourable than SWIFT for smaller commercial payments.

For UAE-to-India transfers, several UAE banks (particularly RAKBank, ENBD and FAB) operate dedicated India remittance products that route through Indian domestic rails rather than full SWIFT — useful for SMEs paying Indian suppliers regularly.

The principle behind each of these alternatives is the same: SWIFT is the international default, but where a faster, cheaper, jurisdiction-specific rail exists, the cost saving is meaningful. For UAE SMEs with regular regional flows, asking the bank which rail will be used on each corridor — rather than assuming SWIFT — uncovers meaningful savings on every recurring monthly payment.

Auditing your last 12 months of wires

For SMEs already running international banking, a quick audit on the last 12 months of inbound wires usually surfaces the same handful of problems.

The most common is customers defaulting to SHA charges. Pull every inbound USD or EUR wire from the last 12 months and compare the wired amount to the invoice amount. The gap is your correspondent fee leakage, and if it shows up consistently on every wire, every customer is on SHA. The fix is one PDF template per currency, sent to every customer with the next invoice, specifying OUR.

Truncated intermediary fields are the next thing to look for. Some payer banks ignore the intermediary bank instruction even when it’s supplied and default to their own correspondent table instead. If one payer’s wires consistently arrive lighter than everyone else’s, their bank is routing through a secondary correspondent. This one is harder to fix — sometimes the only option is to give the payer your bank’s domestic-style virtual IBAN if your account supports one, such as ENBD BusinessOne FX or FAB iBusiness.

The last is reference field truncation. SWIFT MT103 reference fields are length-limited and some payer banks cut off long invoice numbers, which turns AR reconciliation into manual work. Use short, structured reference codes like INV-2026-0123 rather than long descriptive references.

A 30-minute audit on the past year’s wires typically uncovers recoverable annual leakage, almost always more than the cost of having the bookkeeper run the audit in the first place.

If you want a review of your current payment instructions, a template build-out for your invoices, or a cost analysis of your last 12 months of inbound wires, contact our team and we will run the numbers against your real flows.

Velmont Crest is a DED-licensed UAE accounting practice. Our role with banks is preparation, introduction and KYC support — not financial intermediation. We do not act as licensed financial advisers and do not represent businesses before banks in a regulated capacity.

Official references

• Central Bank of the UAE
• SWIFT — Official Site
• Federal Tax Authority — UAE
• UAE Government Portal — Banking and Loans