Corpay

IBAN vs SWIFT Code: Which Does Your Payment Need?

Category:Payments Automation, AP Automation
Updated:2026-11-17
Author:David Luther
hero_iban-vs-swift-code

An IBAN identifies a bank account, a SWIFT code identifies the bank that holds it, and an ABA routing number identifies a US bank inside US payment systems. A wire to a European supplier usually needs the first two.

The IBAN vs SWIFT code question tends to reach AP the same way. A new supplier in Germany returns an onboarding form with both fields filled in, your bank's wire screen labels things differently, and nobody is sure which number goes where. A wrong identifier rarely fails loudly. The payment gets delayed, returned, or parked in review, and then the vendor calls AP. Which identifiers you need comes down to where the vendor's bank sits and which rail carries the payment.

Key Takeaways

  • An IBAN identifies one account and a SWIFT code (BIC) identifies one bank, so the two aren't interchangeable, and many international wires ask for both.

  • Every IBAN starts with a two-letter country code and two check digits, and each country fixes its own length in Swift's IBAN registry.

  • US accounts don't have IBANs. Domestic payments run on an ABA routing number plus an account number, and a US bank uses its BIC for international wires.

  • EU law bars payment providers from requiring a BIC on covered euro transfers, but the bank sending your wire still sets its own required fields.

  • Format checks catch typos, not fraud, so confirm every new or changed bank account by calling a number you already hold.

Is an IBAN the same as a SWIFT code?

No. An IBAN identifies a single bank account, while a SWIFT code, formally a Business Identifier Code or BIC, identifies the bank or branch that holds it. That's why a wire to a European supplier usually carries both. One tells the network which bank, and the other tells that bank which account.

Identifier

What it identifies

Issued or governed by

Length

Where it's used

IBAN

One bank account, with the country and usually a bank code built in

ISO 13616, with Swift as registration authority for national formats

Fixed by each country

Countries that have a national format in the IBAN registry

SWIFT code (BIC)

A bank or other institution, and optionally one branch

ISO 9362, with Swift issuing codes as registration authority

8 characters, or 11 with a branch

International wires and bank-to-bank messages

ABA routing number

A US financial institution

American Bankers Association, with LexisNexis Risk Solutions as registrar

Nine digits

US wires, ACH, and checks

Data from Swift's IBAN and BIC standards pages and the American Bankers Association.

A BIC on its own gets a payment to the right bank with no account to credit. An IBAN often carries a national bank code inside it, Germany's included, yet your sending bank's wire form may still want the BIC as a separate field, and that form decides.

What is a SWIFT or BIC code?

A SWIFT code is the everyday name for a Business Identifier Code. According to Swift's BIC standard page, the BIC is defined by ISO 9362 and issued by Swift as the standard's registration authority, and it has four parts.

  • Four alphanumeric characters for the business party prefix, which identifies the institution

  • Two letters for the ISO 3166-1 country code, such as US or DE

  • Two alphanumeric characters for the business party suffix

  • An optional three-character branch identifier at the end

Written out, the shape is AAAA BB CC DDD with no spaces. An 8-character code points at the institution as a whole, and an 11-character code points at a branch. If your bank's wire screen insists on 11 characters and the vendor gave you 8, ask your bank how it wants the gap filled rather than padding the field yourself.

Not every BIC can receive network traffic. Swift calls a BIC with network access connected and one that exists for reference only non-connected, so when a lookup shows a non-connected BIC, ask the vendor how their bank expects to be paid.

What does an IBAN look like in different countries?

An IBAN starts with a two-letter country code and two check digits, then a national account block whose length and layout each country sets. ISO 13616 defines that structure, Swift publishes the national formats as the IBAN Registry, and only a national standards body or central bank can request a format, according to Swift's IBAN standards page.

Every IBAN breaks into the same three pieces.

  • A two-letter country code, such as DE or FR

  • Two check digits calculated from the rest of the number

  • A national block, often a bank code followed by the account number

The IBAN Registry file lists 89 country entries, and lengths run from 15 to 33 characters. Germany's format, for example, puts an 8-digit bank code and then a 10-digit account number after the DE prefix and its check digits.

Country

Prefix

IBAN length

Registry example

Germany

DE

22

DE89370400440532013000

United Kingdom

GB

22

GB29NWBK60161331926819

Ireland

IE

22

See registry

France

FR

27

FR1420041010050500013M02606

Italy

IT

27

See registry

Spain

ES

24

See registry

Netherlands

NL

18

NL91ABNA0417164300

Belgium

BE

16

See registry

Data from the Swift IBAN Registry. Lengths count every character, including the country code and check digits.

Because the check digits come from the rest of the number, a single mistyped character will usually make an IBAN fail validation. That's the cheapest error check in international payments, and it runs before anything leaves your bank.

The registry has no entry for the United States, and none for Canada, Mexico, China, India, or Japan. Vendors banking in those countries have no IBAN to give you, so an onboarding form that makes the IBAN field mandatory will stall them. Build any validation rule in your ERP or vendor portal from the registry file itself, and pull it into your onboarding checklist before the next foreign vendor goes live.

Protect cash flow with modern AP

Modernize AP to cut costs, speed approvals, and mitigate payment risk — gaining the real-time visibility to protect cash flow and scale with confidence.

Download the whitepaper
protect-cashflow-with-ap.jpg

Do US banks use IBAN, SWIFT, or routing numbers?

US banks use ABA routing numbers with account numbers for domestic payments and their own BIC for international wires. US accounts don't have IBANs, so a European customer paying your company will ask for your bank's SWIFT code and your account number instead.

What is an ABA routing number?

An ABA routing number identifies a US financial institution to US payment systems, and it's the left-most number along the bottom of a check. The ABA's routing number policy breaks it into a four-digit Federal Reserve routing symbol, a four-digit ABA institution identifier, and a check digit. Numbers starting 01 through 12 belong to banks, while 61 through 72 are electronic transaction identifiers.

LexisNexis Risk Solutions registers approximately 22,000 active routing numbers, according to the American Bankers Association. It's the same number that steers an ACH payment to the right bank. Reading from the ABA's own description of its scope, a routing number tells a US system which US bank to use, so it can't stand in for a BIC or an IBAN on a wire to a foreign bank.

Which routing number goes on a wire?

Use the routing number the receiving bank lists for wires, and don't assume the ACH number will work. The registrar's file carries separate ACH and wire attributes for each routing number, so look up the wire attribute instead of copying the number off a voided check. ACH has its own safeguards, an ACH prenote and a correctly built NACHA file format among them.

Which code does a US payer need for each payment?

A US payer needs a routing number and account number for US vendors, an IBAN and usually the bank's BIC for vendors in IBAN countries, and a local account number plus BIC everywhere else. The bank sending the wire decides which fields are mandatory, so check its wire form before you set up the vendor record.

Payment

Identifiers to collect

Note

US vendor paid by ACH or check run

Routing number and account number

Confirm both in writing at onboarding

US vendor paid by domestic wire

Wire routing number and account number

Look up the wire attribute, and don't reuse the ACH number

Vendor in an IBAN country, paid by wire from a US bank

IBAN plus the vendor bank's BIC

Your bank's wire form decides whether the BIC is required

Euro transfer between SEPA accounts

IBAN

The BIC can't be required for covered euro transfers

Vendor in a country with no IBAN, such as Canada or Japan

Local account number plus the bank's BIC

Ask the vendor which local bank code their bank expects

Data from the Swift IBAN Registry, the American Bankers Association, and Regulation (EU) No 260/2012.

The first two rows cover most of a US company's payment volume, and they need the same pair that carries an ACH credit. Corpay's fully managed AP pays vendors by virtual card, ACH, or check, so a supplier paid by card doesn't need bank details on that payment at all.

Do you need a SWIFT code if you already have an IBAN? Often you do. Article 5(7) of Regulation (EU) No 260/2012 says that after Feb. 1, 2016, payment service providers can't require a payer or payee to give the BIC for the cross-border euro transfers and direct debits it covers. As far as I can tell, that rule governs euro payments inside its scope, while a wire your US bank sends still follows your bank's form.

Leaving the BIC off when the form wants it can cost a second set of wire fees, and the cost of a rejected payment rarely stops at the fee. Collecting both codes up front costs one extra field.

How do you check vendor bank details before you pay?

Check vendor bank details at onboarding and again at every change request, against the registry format and a phone number you already hold. Six steps cover most of it.

  1. Collect the IBAN or local account number and the bank identifier as separate fields on the onboarding form.

  2. Check that the IBAN's country prefix matches the vendor's country and the country code inside the BIC.

  3. Check the IBAN length against the registry for that country, and let the check digits catch typos.

  4. Look up the BIC and confirm that the bank name and country match what the vendor told you.

  5. Confirm the details by calling the vendor at a number you already hold, never one printed on the new form or in the email that sent it.

  6. Hold any change to bank details until a second person approves it.

Steps two through four catch transposed digits and fields pasted into the wrong box, and they'll pass a fraudster's account without complaint, because a criminal's IBAN at a real bank is perfectly well formed. Be wary of any tool that says it "validates" an IBAN unless it names the registry as its rule, and even then treat a pass as proof of format only. Only the callback and the second approver test whether the account belongs to your supplier.

That's why vendor bank verification belongs inside onboarding, and why it's worth knowing who carries the loss when a payment lands in the wrong account. The urgent email asking to update remittance details before Friday's run deserves the slowest response, and good vendor management practices make that slowness routine rather than personal.

For vendors that accept cards, Corpay's single-use virtual cards take the bank account out of the payment, which leaves no account field for a fake change request to redirect.

Protect vendor payments with Corpay AP automation

Vendor bank details are master data, and every payment rail you run inherits whatever sits in the vendor record. A mistyped account number or an unverified change request moves from the file into the payment run without anyone looking twice, and AP hears about it only when the vendor calls asking where the money went.

Corpay AP automation is fully managed AP that pays vendors by virtual card, ACH, and check from one payment file, so bank-detail changes and approvals sit in one controlled workflow instead of scattered inboxes. Teams save about 40% of the time they spend on AP processing, and most customers are live in weeks.

Corpay offers 100+ ERP integrations, including NetSuite, Sage Intacct, Microsoft Dynamics 365 Business Central, and Acumatica, so vendor records stay tied to the ERP you already run. Moving card-accepting suppliers to single-use virtual cards removes bank details from those payments and earns rebates, and Corpay pays customers $800M+ in rebates per year. It's the same logic behind broader payments automation, with fewer hand-typed fields between an approved invoice and a settled payment.

Frequently Asked Questions

Is a SWIFT code the same as a BIC?

Yes. "SWIFT code" is the common name for a Business Identifier Code, the ISO 9362 identifier that Swift issues. Wire forms and vendors use the terms interchangeably, so a field labeled "BIC" and one labeled "SWIFT code" want the same value.

Can I use a routing number for an international wire?

No. A routing number identifies a US bank to US payment systems. To pay a bank abroad, you need the beneficiary bank's BIC and either the vendor's IBAN or, where IBANs don't exist, their local account number.

How do I find a vendor's SWIFT code from their IBAN?

A bank or an IBAN lookup tool can usually resolve the bank from an IBAN, because many national formats embed a bank code. Treat the result as a lead, and confirm the BIC with the vendor on the same callback you use to confirm the account.

How long is an IBAN?

It depends on the country. Each national format in Swift's registry has one fixed length, and any other length is wrong for that country. Set your length check per country rather than against a general maximum, so short Belgian and long French IBANs both pass.

Do I need both an IBAN and a SWIFT code?

For most wires from a US bank to a vendor in an IBAN country, plan on both. The IBAN names the account and the BIC names the bank, and your bank's wire form decides which are mandatory. Collecting both at onboarding means a payment never waits on a missing field.

Headshot.JPG

David Luther

Product Marketing Program Manager
David Luther, MBA is a product marketing program manager with years of experience in commercial banking, finance, and technology sectors, with research and writing appearing in financial publications.
Payments Automation
AP Automation

Smarter payments. Stronger growth. Keep business moving.

Corpay powers payments for 800,000+ businesses worldwide. Let’s build what’s next for yours.