Payments - Introduction / Learning brief
BIC versus LEI: payment reference data
Your notes
In simple terms / 01
What this means in plain language
A BIC (Business Identifier Code) identifies a financial institution so a payment can be routed to it, while an LEI (Legal Entity Identifier) identifies a legal entity for transparency. The two are structured differently and complement each other in modern payments.
Two standard codes answer two different questions about the parties on a payment. A BIC (Business Identifier Code) answers 'which institution', it identifies a bank or financial institution so a message can be addressed and routed to the right place. An LEI (Legal Entity Identifier) answers 'which legal entity', it identifies a specific company, fund, or other organisation so that everyone can see exactly who is involved. A BIC is 8 or 11 characters and is mainly an operational, routing code used between financial institutions. An LEI is 20 characters and is a transparency code that can identify any legal entity, not only banks, and it links to public reference data such as the entity's registered name and address. The two do not compete; they complement each other. In a modern ISO 20022 (International Organization for Standardization standard 20022) payment, a BIC can route the message while an LEI states precisely who the payer or payee legally is.
Complete lesson / 02
Understand the full idea, step by step
A courier needs two things to deliver a parcel: an address that says which building, and a name that says which person inside. Payments split that same job between two codes — one that says which bank, one that says which legal entity. Mixing them up is one of the most common beginner slips, so let us hold them apart.
BIC (Business Identifier Code) — the ISO 9362 code that identifies a financial institution
A BIC identifies a financial institution. Its job is operational: it tells the network which bank a message is addressed to, so the instruction routes to the right place and, where needed, on to the right branch. It answers where does this go. Defined by the ISO 9362 standard, it is either 8 or 11 characters.
LEI (Legal Entity Identifier) — the ISO 17442 code that identifies a legal entity
An LEI identifies a legal entity — any legally distinct organisation in financial activity, not only banks but companies, funds, and public bodies. Its job is transparency: it answers who exactly is this, and it links to a public record of the entity's official name, registered address, and, where applicable, its parent. Defined by the ISO 17442 standard, it is always 20 characters, ending in two check digits calculated from the rest to catch typing errors.
How a BIC is built
- Characters 1–4
- Institution code — a short name for the bank
- Characters 5–6
- Country code, from the ISO 3166 list
- Characters 7–8
- Location code — city or processing centre
- Characters 9–11 (optional)
- Branch code; absent or 'XXX' means the head office
| BIC | LEI | |
|---|---|---|
| Identifies | A financial institution | A legal entity of any kind |
| Purpose | Routing — where does this go | Identity — who exactly is this |
| Standard | ISO 9362 | ISO 17442 |
| Length | 8 or 11 characters | Always 20 characters |
| Backed by | A directory of institutions | A public register of reference data |
You may be wondering: if a payment already carries a BIC, why add an LEI at all — can't one do both jobs?
No, because they describe different things. A BIC gets the message to the correct institution, but it says nothing certain about the company standing behind a party — and two different firms can share a similar name. An LEI pins identity down: each legal entity has exactly one, tied to a public record you can look up. A payment can carry both without conflict, one naming the bank that handles the money, the other naming the entity behind a party.
How they work together in ISO 20022
Because the two answer different questions, modern ISO 20022 (International Organization for Standardization standard 20022) messages have defined places for each. A financial institution can be identified by its BIC for routing and, alongside it, by its LEI; the ordering and beneficiary parties — the companies behind the payment — can each carry an LEI of their own. The BIC still does the operational work of reaching the correct institution. The LEI adds certainty about identity that a name alone cannot give. For screening and transparency this is the useful part: a compliance team can take a party's LEI, look it up in the public register, and confirm the legal name, address, and ownership behind it. Standards bodies have published mappings between BICs and LEIs to help institutions connect the two.
COMMON CONFUSION
“A BIC identifies a specific company or a specific account — so a BIC alone tells you exactly who you are paying.”
A BIC identifies an institution and, at most, a branch — never an account and never the customer behind a payment. It routes the message to a bank; it does not name the ordering or beneficiary company. That identity job belongs to the party's name and, increasingly, its LEI.
STRICTLY SPEAKING
Strictly speaking, an 8-character BIC names an institution and its main location, while the 11-character form adds a branch; a branch code of 'XXX', or no branch code at all, refers to the head office. And an LEI's presence is not universal — whether a given party carries one depends on the scheme and the entity. So expect to see a BIC on essentially every interbank leg, and an LEI where transparency rules or a bank's own policy call for it.
FOR NOW, REMEMBER
- A BIC (ISO 9362) identifies a financial institution and answers where a payment goes; it is 8 or 11 characters.
- An LEI (ISO 17442) identifies a legal entity and answers who is behind a party; it is always 20 characters with check digits.
- They complement rather than replace each other — BIC for routing, LEI for identity — and ISO 20022 has a place for both.
- A BIC never names an account or a customer; identity is the LEI's and the party name's job.
TRY IT YOURSELF
Kabir is reviewing a payment and wants to confirm the exact legal company behind the beneficiary, including its registered name and ownership. Which identifier serves that purpose, and why?
So far we have looked at single payments and the codes on them. But a payroll run is not one payment — it is hundreds, packed into one file. Next: how a single pain.001 carries many transactions at once.
KEEP GOINGKey takeaways / 03
Three things to remember
- 01
A BIC (Business Identifier Code) identifies a financial institution for routing and addressing between banks.
- 02
An LEI (Legal Entity Identifier) identifies a specific legal entity for transparency and links to public reference data.
- 03
The two complement each other: in an ISO 20022 payment a BIC can route the message while an LEI states who a party legally is.
Practical use cases / 04
Where you would use this
A payment system uses the BIC to address and route a message to the correct financial institution.
A compliance team uses the LEI to confirm a counterparty's legal identity against public reference data during screening.
A regulator relies on LEIs in transaction reports to see which legal entities stand behind a set of payments.
Worked example / 05
Put the idea into a real situation
Illustrative example: a fictional bank, Meridian Trust, sends a payment on behalf of a fictional company, Alder Freight Ltd, to a fictional beneficiary bank, Kestrel Union Bank. The message routes using Kestrel Union Bank's BIC (Business Identifier Code), an 11-character illustrative value such as 'KSTRGB2LXXX': 'KSTR' names the institution, 'GB' the country, '2L' the location, and 'XXX' the head office. To identify the ordering company, the same message carries Alder Freight Ltd's LEI (Legal Entity Identifier), a 20-character illustrative value such as '5493001KJTIIGC8Y1R12', which links to Alder Freight's registered legal name and address. The BIC gets the EUR 88,000.00 to the right bank; the LEI makes clear which legal entity ordered it.
Evidence & review / 07
Evidence & review
ISO 9362 BIC and ISO 17442 LEI as carried in ISO 20022 payment messages.
What this brief simplifies: Describes BIC and LEI structure and roles; does not enumerate every LEI field or every ISO 20022 element that may carry these codes, and LEI adoption varies by scheme.
Sources for this brief3
- Official requirement
SwiftRef reference data services ↗ — Swift · BIC (ISO 9362) structure
Used for public summaries of the SwiftRef directories and their delivery through files, a web application, and application programming interfaces.
- Market practice
Wolfsberg Group Payment Transparency Standards ↗ — The Wolfsberg Group
The 2023 standards replace the 2017 version and are supplemented by separate Wolfsberg guidance on roles and responsibilities in payment chains.
- Simplified educational illustration
Payments Signal editorial teaching models — Payments Signal
Used wherever diagrams, scenarios, figures, or example values are didactic constructions rather than sourced facts; every such use carries a simplifications disclosure. All people, companies, banks, and list entries in examples are fictional.