IBAN vs SWIFT vs BIC: Which Number Your Payment Needs

IBAN vs SWIFT vs BIC, decided by corridor: which identifier a UK, SEPA or global business payment actually needs, and what the wrong one costs you.

Nobody searches IBAN vs SWIFT vs BIC out of curiosity. They search it with a payment form open, three boxes on screen, and a supplier waiting. The definitions are the easy part: an IBAN identifies an account, a BIC identifies the institution holding it, and a SWIFT code is a BIC under a different name. The useful question is the next one. Which of them does this particular payment need, and what happens if you supply the wrong set. That answer changes by corridor, and in the euro area it changed again in October 2025. ## The short answer | | IBAN | BIC or SWIFT code | | --- | --- | --- | | Identifies | the account | the institution, optionally the branch | | Standard | ISO 13616 | ISO 9362 | | Length | 15 to 34 characters | 8 or 11 characters | | Contains a name | no | no | The ISO 13616 IBAN is built from a country code, check digits and a Basic Bank Account Number, while the ISO 9362 BIC identifies a payment service provider and potentially its branch. Length is the fastest way to tell at a glance which one a form is asking for. SWIFT is the third term and the one people misfile. It is not a competing identifier at all. It is the messaging network banks use to instruct each other, and a SWIFT code is an institution's identifier on that network rather than an account number. ## IBAN: the account, in a format another country can read An IBAN is not a new account number. It is your existing account details rewritten so that a system in another jurisdiction can parse them without a human reading the letterhead. ### What is inside one Reading left to right, the first two letters are the country of the account, the next two are check digits, and the remainder is a bank identifier followed by the domestic account number, running up to 34 characters against the fixed 8 or 11 of a SWIFT code. Those check digits do real work. They let the sending system reject a mistyped account before the money leaves, which is why a typo in an IBAN usually produces an error message rather than a lost payment. Formats are national, not universal. Each country has its own IBAN format registered under ISO 13616, and only a national standards body or a national central bank can request one, with Swift publishing the resulting registry free of charge. A 22 character UK IBAN and a 27 character French one are both correct. ### What an IBAN does not tell you Two things, and both matter commercially. It carries no name. There is no field for one anywhere in the string, which is why payee name checking had to be built as a separate mechanism entirely. It also says nothing about who holds your money. A bank, an electronic money institution and a payment institution all issue identifiers that look identical on an invoice. That distinction is worth its own read: here is what a dedicated business IBAN actually buys you. ## BIC and SWIFT code: one code, two names This is where most explainers create the confusion they set out to remove. Some claim BIC and SWIFT codes differ in structure, or that BIC is a European-only code. The standard does not support either reading. There is one code. Swift acts as the ISO registration authority for the ISO 9362 Business Identifier Code and for the ISO 13616 IBAN, so the same organisation that runs the network also maintains the registry for both identifiers. HSBC states the practical version for customers: BIC codes are also referred to as SWIFT codes because they use the SWIFT system, and they are the same thing. There is one genuine nuance, and it is not the one usually reported. Swift issues BICs in its role as registration authority, but not all BICs are connected to the Swift network, and non-connected BICs have no rights or authorisation to exchange messages over it. So a valid BIC is not by itself proof that the institution can receive a SWIFT payment. That is a question about network participation, not about the code. The anatomy is fixed: four letters for the institution, two for the country, two for the location, and an optional three for the branch. A trailing XXX means head office, which is why an 8 character and an 11 character code ending XXX point at the same place. ## Which identifier does your payment actually need Here is the part the glossaries skip. ### UK domestic: sort code and account number An IBAN is not the working identifier for a payment between two UK accounts. Faster Payments, CHAPS and Bacs address the receiving account with unique identifiers, usually a sort code and account number. Give a UK payer those two fields. Handing them an IBAN for a domestic transfer invites a manual keying error or a routing over an international rail you did not need to pay for. ### Euro inside SEPA: IBAN only For euro credit transfers and direct debits within SEPA, the IBAN is sufficient on its own. Providers resolve it to the receiving institution themselves, using directories, so the payer is not asked for a BIC. That is usually described as a convenience. It is stronger than that. Regulation (EU) No 260/2012 states that after 1 February 2016 for cross-border payment transactions, payment service providers shall not require payment service users to indicate the BIC of the payer's or the payee's provider. Known as the IBAN-only rule, it is a prohibition rather than an option. A provider making a BIC mandatory on a SEPA euro transfer is not being careful, it is out of step with the regulation. ### Non-euro, or outside SEPA: both Leave euro or leave SEPA and the BIC returns as a requirement, including for currencies other than the euro sent within the EU. The euro exception inside the EU is narrower than people assume once a bank's own rules apply. HSBC's guidance is explicit that all cross-border euro priority payments within the EU or EEA must quote the beneficiary BIC and IBAN, and a payment sent without them can be returned or rejected and a fee charged. Priority payments route over SWIFT rather than the SEPA schemes, which is exactly why the IBAN-only rule does not rescue them. ### Countries with no IBAN at all The system is regional. Banks in the United States and Canada do not have IBANs, though they recognise the format for outgoing international transfers. Paying into the US means a routing number, an account number and the bank's SWIFT code. Asking a US supplier for an IBAN they do not have is a common way to lose two days. ## What it costs when the number is wrong Two failure modes, and they are not symmetrical. The BIC is required for non-SEPA transfers, for non-euro currencies even within the EU and for SWIFT-only corporate flows, and a wrong one there makes the payment bounce, with return fees and a delay of three to ten days while the funds work their way back. Inside SEPA the same error is usually harmless, because the routing is derived from the IBAN regardless of what was typed in the BIC field. The second failure is one only businesses commit. Refusing an IBAN because of its country code is IBAN discrimination, which the European Commission defines as being unable to make or receive a SEPA credit transfer or a direct debit from an account located in another member state, and which is reported to the national competent authority where it occurred. The legal basis is Article 9 of the same 2012 regulation: neither payer nor payee may specify the member state in which the other side's account is located. If your billing system rejects a Lithuanian or Irish IBAN from an EU customer, that is a compliance problem in your own accounts receivable, not a fraud control. ## Since October 2025, the right number is no longer enough The identifiers now travel with a name check, and this is the change most comparison pages have not absorbed. Under the EU Instant Payments Regulation, Verification of Payee has been required in euro area member states since 9 October 2025, free of charge to the payer, on both standard and instant euro credit transfers, returning match, close match, no match or other before the payer confirms, with non euro area member states following on 9 July 2027. The Commission's own summary of the change puts it plainly: providers must verify that the payee's name matches the IBAN provided, and the service must be free. The UK got there first by a different route. Confirmation of Payee checks an account name for UK domestic payments, and joining it requires being an FCA or NCA regulated account holding provider with customers reachable by a sort code and account number. It is now close to universal on Faster Payments and CHAPS. The operational consequence is small and easy to get wrong. The payee name on your invoice has to match the name registered against the account behind that IBAN or sort code. If it does not, your customer sees a warning at the moment of authorising, and somebody in their finance team decides whether to proceed. Trading names, abbreviations and a recent rebrand are the usual culprits. ## What changes when the account sits with a payment institution The identifiers look identical whoever issues them, so the useful questions are about the firm behind them: which entity provides the account, whether it is a bank, and what protects the balance. We will answer that for ourselves rather than leave it implied. EXFI is a trading name of EX Financial Solutions Ltd, which is not itself authorised or regulated by the FCA and acts as a distributor; the regulated payment services are provided by Gemba Finance Limited, FCA FRN 804853, for UK customers. EX FI accounts are payment accounts, not bank accounts. They are not covered by the FSCS. Funds are safeguarded in segregated accounts under the Payment Services Regulations 2017. The mechanics of that licence are worth understanding in their own right: here is what an authorised payment institution is. The identifier also has a price attached, which is the part a definition page can never tell you. EX FI accounts hold balances in 16 or more currencies with a dedicated IBAN where applicable, reaching SWIFT, SEPA, FPS, BACS and CHAPS, with internal transfers free, SEPA and UK FPS at 0.99 GBP, international SWIFT at 26.40 GBP, and FX at 0.70 percent on majors and 0.90 percent on minors. Those numbers are the real argument for holding local details in each currency you invoice in: a euro paid to your euro IBAN over SEPA and a euro paid to your GBP account over SWIFT cost different amounts and arrive on different days. That arithmetic is the whole case for a multi currency business account, and the SWIFT side of it deserves its own treatment in cross border payments over SWIFT. ## The details to put on an invoice Give the payer everything for their corridor, once, in one block: - Payee name exactly as registered with the account provider

•IBAN, no spaces
•BIC or SWIFT code, with the branch code if you have an 11 character one
•Sort code and account number for UK payers
•Currency, stated explicitly
•A payment reference, especially if your IBAN sits over a pooled account Then add the local details for each currency you actually receive. A German customer paying a GB IBAN in euro is a SWIFT payment with a fee and a lag. The same customer paying a euro IBAN is a SEPA transfer. Same invoice, same money, different rail, and the only thing that changed was which number you printed. ## FAQ Is a BIC the same as a SWIFT code? Yes. ISO 9362 defines a single business identifier code and Swift maintains it as registration authority, so the two names describe the same 8 or 11 character string. The nuance worth knowing is that having a BIC does not guarantee the institution is connected to the SWIFT network. Can you work out a BIC from an IBAN? Not by reading it. An IBAN contains a national bank identifier, not a BIC, so the two are linked through directories rather than by conversion. That lookup is precisely the mechanism the SEPA IBAN-only rule relies on. Do I need an IBAN to receive a payment inside the UK? No. A domestic payment over Faster Payments, CHAPS or Bacs is addressed with a sort code and account number. The IBAN matters when the payer is abroad or paying in euro. Why does my IBAN start with a different country code from my company? The country code identifies where the account sits, not where the account holder is incorporated, and formats are registered nationally. A UK company can legitimately hold a euro IBAN issued in another country, and inside the EU a counterparty may not refuse it on that basis alone. What happens if I send a payment with the wrong BIC? Outside SEPA it can bounce back, costing return fees and several days. Inside SEPA an incorrect BIC is generally ignored, because the payment is routed from the IBAN alone.