
An IBAN is not the same as a regular account number, although it often contains the domestic account number inside a longer international format. A normal account number identifies your account within a local banking system; an IBAN identifies a bank account in a standardized cross-border format that may include a country code, check digits, bank code, branch code and local account number. You usually need an IBAN for transfers to many European and SEPA countries, while transfers to the U.S., Canada, Australia and other non-IBAN markets often require a local account number plus routing details or SWIFT/BIC. The safest approach is to follow the destination country and form fields exactly.

No, an IBAN is not the same as a standard account number. An account number identifies one bank account inside a domestic banking system, while an IBAN is a standardized international account identifier used to help process cross-border payments more consistently. In many IBAN countries, your domestic account number is embedded inside the IBAN, but you should not shorten the IBAN, split it, or replace it with the account number unless the bank or payment platform clearly asks you to do so.
The confusion usually starts when a transfer form asks for “IBAN / Account Number” in one field. This does not always mean the two are identical. It often means the platform supports more than one destination type: if the recipient account is in an IBAN country, enter the IBAN; if the recipient account is in a non-IBAN country, enter the local account number required by that country.
According to SWIFT, IBAN stands for International Bank Account Number and is designed to facilitate automated processing of cross-border payment transactions. That purpose is different from a domestic account number, which is mainly used by one country’s banking system or by one bank’s internal account structure.
A practical way to think about it:
| Identifier | What it identifies | Typical use | Example field wording |
|---|---|---|---|
| IBAN | A bank account in an IBAN country | International and SEPA transfers | IBAN, Account IBAN |
| Account number | A specific account at a bank | Domestic payments and some wires | Account Number |
| SWIFT/BIC | A bank or financial institution | Cross-border bank routing | SWIFT, BIC |
| Routing/sort code | Bank or branch in a local system | Country-specific payments | ABA, Sort Code, BSB, Transit |
Banks and transfer platforms use different labels. One app may say “Recipient Account,” another may say “IBAN,” and a corporate payment system may say “Account Identifier.” In Europe, the IBAN may be the main account field for cross-border transfers. In the U.S., the same form may require an account number, SWIFT code and routing number instead.
This is why you should not ask only, “What is my account number?” The better question is, “What identifier does this payment route require?” If you are paying a supplier in Germany, the invoice will likely show an IBAN. If you are receiving money into a U.S. checking account, your bank will usually provide an account number and wire instructions instead of an IBAN.
If the recipient bank gives you an IBAN, copy the full IBAN exactly from online banking, a bank statement or an invoice. If the recipient bank does not issue IBANs, do not try to create one yourself from the account number. Use the local account number and the bank routing information requested by the form.
This difference matters because payment forms often validate length and structure. A German IBAN, a French IBAN and a U.K. IBAN do not have the same format. A U.S. account number does not become an IBAN just because the transfer is international.
Summary: An IBAN and an account number are connected but not interchangeable. The account number is usually the local identifier for the recipient account, while the IBAN is a wider international format that may include that account number plus country-specific routing information and check digits. When a form asks for IBAN, enter the full IBAN from the bank source. When a form asks for account number in a non-IBAN country, enter the domestic account number and complete the additional bank routing fields. The safest rule is to read the destination country, payment type and field label before entering any number.

An IBAN is a structured account identifier, not a decorative version of a normal account number. It normally begins with a two-letter country code, followed by two check digits and a country-specific Basic Bank Account Number, also called BBAN. The BBAN may include the bank code, branch code, domestic account number and other routing elements. This structure is why an IBAN can be validated before payment, while a plain account number may require local banking rules to interpret.
The standard IBAN format has three major parts. The first two characters are the country code. The next two characters are check digits used to validate the IBAN structure. The remaining characters form the BBAN, which is the domestic banking part of the IBAN. SWIFT’s IBAN Registry describes the ISO 13616 IBAN structure as a two-letter ISO country code, two check digits and up to thirty alphanumeric characters for the BBAN.
| IBAN part | Function | User action |
|---|---|---|
| Country code | Shows the country of the account | Do not change it |
| Check digits | Help validate the IBAN | Do not guess or edit |
| BBAN | Contains domestic bank/account details | Use the full value from the bank |
| Display spaces | Improve readability on paper | Remove only if the form requires it |
A sample U.K.-style IBAN may look like this: GB29 NWBK 6016 1331 9268 19. In that example, GB is the country code, 29 is the check digit pair, and the remaining characters carry the domestic bank and account information.
The domestic account number is often inside the IBAN, but it is not the whole IBAN. In the U.K., Pay.UK explains that the domestic part of the IBAN includes a bank code in front of the domestic sort code and account number. That means a U.K. account number can help form an IBAN, but the full IBAN also includes additional characters.
This is important when you copy details from an invoice. If the invoice gives you only a sort code and account number, that may be enough for a domestic U.K. bank transfer. If you are sending from abroad, the payer may need the IBAN and sometimes BIC. Do not try to manually convert the sort code and account number unless the bank or an officially supported banking tool provides the result.
IBANs are often printed in groups of four characters because that is easier to read. Digital forms may ask for the same IBAN without spaces. For example, the paper format may show GB29 NWBK 6016 1331 9268 19, while the electronic form may require GB29NWBK60161331926819.
| Situation | Safer action |
|---|---|
| IBAN appears in groups of four | Copy the full value, including all groups |
| Digital form rejects spaces | Remove spaces, not characters |
| Form auto-formats IBAN | Let the form format it after entry |
| IBAN contains letters | Keep letters exactly as shown |
| IBAN check fails | Recopy from bank source instead of editing manually |
Never remove the first four characters because they are not optional. The country code and check digits are part of the IBAN’s validation logic. Also avoid adding punctuation, hyphens, currency labels or extra words into the IBAN field.
Summary: An IBAN has a formal structure: country code, check digits and BBAN. The domestic account number is usually one part of the BBAN, but the full IBAN may also include local bank identifiers, branch information and country-specific routing elements. This is why an IBAN can look longer than a normal account number and why it should be copied exactly. Spaces may be removed for electronic forms, but characters should not be changed. If a form says the IBAN is invalid, the correct response is to return to the bank statement, invoice or online banking source, not to guess new digits.

IBAN identifies the recipient account; SWIFT/BIC identifies the recipient bank or financial institution. A routing number, sort code, BSB, transit number or CLABE is usually a local banking identifier used in a specific country. These identifiers work together, but they do not replace one another. If a transfer form asks for SWIFT/BIC, do not enter IBAN. If it asks for IBAN, do not enter only the domestic account number unless the destination country does not use IBAN.
The European Payments Council explains that IBAN and BIC rely on global standards, with IBAN based on ISO 13616 and BIC based on ISO 9362. In simple terms, IBAN points to the account; BIC points to the bank or payment service provider.
| Identifier | Main question it answers | Example use |
|---|---|---|
| IBAN | Which recipient account? | Paying a European supplier |
| SWIFT/BIC | Which bank receives the message? | International wire routing |
| Account number | Which local account? | Domestic payment or non-IBAN wire |
| Local routing code | Which bank/branch in local system? | ACH, Faster Payments, BSB, transit |
Some SEPA payments may no longer require the payer to manually enter BIC, because the bank can derive routing information from IBAN. The EPC notes that the IBAN-only rule has applied for SEPA euro credit transfers and direct debits since February 2016. However, outside that context, many banks and platforms may still ask for SWIFT/BIC.
The U.S. banking system generally does not use IBAN for standard bank accounts. If you receive an international wire into a U.S. account, your bank will usually ask you to provide your account number, bank name, bank address and SWIFT code. Chase explains that it does not use IBAN and directs users receiving international wires to provide an account number and SWIFT code instead.
Bank of America also gives U.S. inbound wire instructions based on SWIFT Code, bank address and wire routing information, rather than an IBAN. U.S. Bank similarly states that for international wires, senders need to use a Swift Code instead of the routing number.
This is a frequent mistake: a non-U.S. sender asks a U.S. recipient for an IBAN because that is what their bank form expects. The recipient cannot usually provide one. In that case, the sender should choose the correct destination country or payment route and enter the U.S. account number and SWIFT details requested by the sending bank.
Different countries use different domestic identifiers. The U.K. uses sort codes and account numbers for many local payments. Australia uses BSB and account number. Canada uses transit number, institution number and account number. Mexico uses CLABE for domestic standardized account identification. The U.S. uses ABA routing numbers and account numbers for many domestic payments; the Federal Reserve’s E-Payments Routing Directory supports routing information for Fedwire and FedACH transactions.
| Destination market | Common account identifier | Common bank/routing identifier | IBAN used? |
|---|---|---|---|
| Eurozone / SEPA | IBAN | BIC may be requested | Usually yes |
| United Kingdom | IBAN for international use, account number locally | Sort code / BIC | Yes |
| United States | Account number | ABA routing / SWIFT | Usually no |
| Canada | Account number | Transit and institution number / SWIFT | Usually no |
| Australia | Account number | BSB / SWIFT | Usually no |
| Mexico | CLABE | SWIFT for some international wires | CLABE, not IBAN |
Summary: IBAN, SWIFT/BIC, routing number, sort code and account number answer different payment questions. IBAN identifies the recipient account in an international format. SWIFT/BIC identifies the bank or financial institution. Local routing codes identify banks or branches inside one country’s payment system. Account number identifies the specific account in that local system. The safest rule is to start with the destination country, then follow the payment rail: SEPA and many European transfers often need IBAN, while U.S. transfers usually need account number plus SWIFT and possibly routing details. Forcing IBAN into every international transfer can create errors.
You usually need an IBAN when the recipient bank account is in an IBAN country or when the transfer form specifically asks for IBAN. You usually need a regular account number when the destination country does not use IBAN, or when the payment is domestic and the local system uses account number plus routing details. The decision should be based on destination country, currency, payment type and platform instructions, not on whether the transfer feels “international.”
For transfers to many European countries, IBAN is the main recipient account identifier. The European Payments Council says IBAN and BIC allow the identification of accounts in SEPA countries. In practice, a SEPA credit transfer may ask for the payee name, IBAN, payment amount and reference; some banks may also request BIC, address or payment purpose depending on the platform and country.
If you are paying a supplier in Germany, France, Spain, Italy or the Netherlands, the invoice will usually show an IBAN. You should copy the full IBAN from the invoice or confirm it through a trusted channel if the payment is large or the invoice details changed recently.
For non-IBAN markets, you should expect local account details plus routing information. A U.S. recipient may provide an account number, SWIFT code, bank name and bank address. A Canadian recipient may provide institution number, transit number and account number. An Australian recipient may provide BSB and account number. These identifiers are not inferior to IBAN; they simply belong to different payment systems.
| Destination | Usually enter IBAN? | Usually enter account number? | Extra fields to check |
|---|---|---|---|
| Paying a supplier in Germany | Yes | Not separately unless requested | BIC, invoice reference |
| Receiving money in the U.S. | No | Yes | SWIFT, bank address, routing |
| Sending GBP to a U.K. account | Often yes for international transfer | Sometimes for local transfer | Sort code, BIC |
| Paying an Australian account | Usually no | Yes | BSB, SWIFT if international |
| Paying a Canadian account | Usually no | Yes | Transit and institution number |
| Brokerage deposit | Depends on platform | Depends on platform | Reference code, beneficiary name |
The biggest error in non-IBAN markets is trying to generate an IBAN from an account number and routing code. Unless the bank itself provides an IBAN, you should not create one manually.
Business and platform forms can be more confusing than bank forms because they may use broad labels. You may see “Account Identifier,” “Recipient Account,” “IBAN / Account Number,” “Local Account Number,” “Bank Routing Code” or “Beneficiary Account.” In these cases, the destination country and payment method matter more than the label alone.
For payroll, use the format your employer’s payroll provider requests. For brokerage deposits, follow the brokerage’s exact beneficiary name, reference number and bank details. For supplier payments, verify any new IBAN through a separate communication channel before sending large amounts. For platform deposits, do not replace the platform’s beneficiary information with your own guessed bank details.
A practical decision flow:
Summary: You need an IBAN when the recipient account is in an IBAN country or the form explicitly asks for IBAN. You need a regular account number when the destination country uses a local account-number system, such as the U.S., Canada or Australia. Business, payroll and brokerage forms may combine labels, so you should rely on destination country, transfer type and platform instructions. If a field says “IBAN / Account Number,” it is not saying they are the same; it is usually asking for the correct account identifier for that destination. When in doubt, ask the recipient bank or platform for exact receiving instructions.
Confusing IBAN and account number can lead to form rejection, payment delays, returned transfers, manual compliance review, intermediary bank fees or funds being sent to the wrong beneficiary. A valid-looking IBAN only confirms structure; it does not prove that the recipient is legitimate or that the invoice is genuine. Before sending money, you should verify the identifier, beneficiary name, bank name, payment purpose and any recent change to the payee’s bank details.
If you enter only a domestic account number in an IBAN field, the form may reject it because the length and check digits do not match. If you enter an IBAN into a domestic-only account field, the form may reject it because it is too long or contains letters. If you enter SWIFT/BIC where the account number should go, the payment cannot identify the recipient account.
| Mistake | Likely outcome | Prevention |
|---|---|---|
| Using account number instead of IBAN | Form rejection or returned payment | Copy full IBAN from bank source |
| Removing IBAN check digits | Invalid IBAN | Never edit the first four characters |
| Using SWIFT as account number | Failed or delayed payment | Match each field by label |
| Entering IBAN in a domestic-only field | Length or format error | Use local account number where required |
| Using old beneficiary details | Delay, return or misdirected payment | Reconfirm before large transfers |
Fees can also be affected. Returned international wires may involve sending bank fees, receiving bank fees or intermediary bank deductions. Even if the bank refunds the principal, the full amount may not return exactly as sent because fees and exchange rates can apply.
Correct account identifiers are only one part of payment screening. Banks and payment providers may also check beneficiary name, bank name, address, country, payment purpose, sanctions risk, source of funds and transaction pattern. An IBAN that passes format validation can still be held for review if the beneficiary name does not match or the payment purpose is unclear.
For business transfers, invoice reference matters. For brokerage deposits, the reference code may decide whether the deposit is matched to your account. For salary or payroll, the account holder name should match the employee name unless the payroll provider has a permitted exception. These checks are not just administrative details; they affect whether funds can be credited smoothly.
Sharing an IBAN for receiving money is common in many countries, but that does not mean you should share it carelessly. IBAN and account details can be used in fake invoice scams, business email compromise, phishing and social engineering. If a supplier suddenly changes its IBAN, verify the change through a trusted channel before sending funds.
A safe verification checklist:
Summary: A wrong IBAN, account number or routing field can cause technical failure, but transfer risk is wider than formatting. Payment may be delayed or returned if the account identifier is incomplete, if the bank cannot match the beneficiary name, if the reference is missing, or if the transaction triggers compliance review. A valid IBAN reduces some typing and structure errors, but it does not prove that the recipient is safe. You should verify the payee, use the full bank-provided identifier, confirm any changed details and keep transaction records. For large or business payments, a separate confirmation step is often worth the time.
Filling a transfer form correctly is less about memorizing acronyms and more about mapping each field to the right payment identifier. Start with the destination country and payment type, then enter IBAN, account number, SWIFT/BIC and local routing fields only where they belong. Do not generate an IBAN yourself, do not remove leading zeros, and do not use the same number in every field unless the bank or platform clearly instructs you to.
The destination country determines whether IBAN is expected. A euro payment to a SEPA country will usually use IBAN. A wire to a U.S. account usually uses account number and SWIFT. A domestic U.K. payment may use sort code and account number, while an international payment to a U.K. account may request IBAN.
| Payment type | First thing to confirm | Why it matters |
|---|---|---|
| SEPA transfer | Recipient IBAN | IBAN is the main account identifier |
| International wire | Destination country and bank | SWIFT and local details may be needed |
| Domestic transfer | Local account/routing format | IBAN may not be used locally |
| Payroll | Employer or payroll provider format | Incorrect fields may delay salary |
| Brokerage deposit | Platform beneficiary and reference | Missing reference may delay matching |
| Supplier payment | Invoice and verified bank details | Reduces fraud and misdirection risk |
If the form asks for IBAN, enter the full IBAN. If it asks for Account Number, enter the local account number. If it asks for SWIFT/BIC, enter the bank identifier. If it asks for routing number, sort code, branch code, BSB or transit number, enter the country-specific bank or branch identifier. If it asks for Reference, enter the invoice number, customer number, brokerage reference or payment memo required by the recipient.
When a form gives a combined label such as “IBAN / Account Number,” do not enter both unless the form provides separate fields. Choose the correct account identifier based on the destination country. If the recipient gives you both IBAN and domestic account number, use the one that matches the payment route.
The best source for an IBAN is the recipient’s online banking, bank statement, official invoice or bank letter. HSBC UK notes that customers can find IBAN and BIC on their bank statement and that the IBAN varies by account. This is the right mindset: use the actual account-specific IBAN, not a guessed version.
A pre-submission checklist:
If you are dealing with cross-border payments, currency conversion or investment funding in multiple markets, tools such as Swift lookup can help you check bank identifiers before you submit transfer details. You can also compare approximate currency values using real-time exchange rates, while still relying on the sending bank, receiving bank or platform for final fees and credited amount.
Summary: Correct form filling starts with the payment route. First identify the recipient country and whether the payment is SEPA, international wire, domestic transfer, payroll, supplier payment or platform deposit. Then map each field to the correct identifier: IBAN for IBAN countries, account number for local account fields, SWIFT/BIC for bank identification and routing codes for local clearing systems. Copy details from bank-controlled sources, preserve leading zeros, add references where required and save the receipt. Most transfer errors happen when users reuse one number across multiple fields or assume that IBAN and account number are identical.
When you regularly manage international transfers, currency conversion and funding for trading or payment accounts, it helps to keep a repeatable pre-transfer routine: verify the recipient country, confirm whether IBAN is required, check SWIFT/BIC, estimate the currency conversion and review fees before sending. Biya is a global multi-asset trading wallet that supports cross-border remittance scenarios and USDT conversion into major fiat currencies such as USD and HKD. For users who also trade U.S. stocks, Hong Kong stocks or digital assets, Biya can fit into a wider funding and account-management workflow. Biya’s U.S. stock trading commission is 0 USD; platform fees, external agency fees, trading activity fees, fractional-share rules, identity verification and product availability should always be checked against the platform’s actual fee disclosures, order page and local regulatory requirements.
No, an IBAN is not the same as a regular bank account number. An IBAN is a standardized international account identifier that may contain the domestic account number, but it also includes a country code, check digits and country-specific bank details.
You can use an account number instead of an IBAN only when the destination country or bank does not require IBAN. For IBAN countries, using only a domestic account number may cause rejection, delay or return. Always follow the receiving bank’s instructions.
Most U.S. bank accounts do not have IBAN numbers for incoming wires. U.S. inbound international wires usually require the recipient’s account number, bank name, SWIFT code, bank address and sometimes ABA routing details, depending on the bank and transfer type.
A transfer form asks for IBAN and SWIFT/BIC together because they identify different things. IBAN identifies the recipient account, while SWIFT/BIC identifies the recipient bank or financial institution. Some payment routes require both for routing accuracy.
Sharing an IBAN for receiving money is common in IBAN countries, but it should still be limited to trusted payers and verified invoices. Avoid posting account details publicly or sending them in suspicious conversations, especially for business payments or large transfers.
A wrong IBAN may fail validation, delay processing, trigger manual review or cause a returned payment. If the transfer has already been sent, contact the sending bank immediately with the payment reference, beneficiary details and transfer receipt.
*This article is provided for general information purposes and does not constitute legal, tax or other professional advice from BiyaPay or its subsidiaries and its affiliates, and it is not intended as a substitute for obtaining advice from a financial advisor or any other professional.
We make no representations, warranties or warranties, express or implied, as to the accuracy, completeness or timeliness of the contents of this publication.



