ISO 9362 BIC segment anatomy and 8 vs 11 character codes
A Business Identifier Code (BIC), commonly called a SWIFT code, identifies banks and financial institutions in international messaging. As documented in the GLEIF and SWIFT BIC-to-LEI Mapping Specification, every code follows a fixed 8- or 11-character positional layout defined by ISO 9362.
Decoding institution, country, location, and branch codes
Positions 1 to 4 hold the alphanumeric institution or business party code, such as DEUT for Deutsche Bank or CHAS for JPMorgan Chase. Positions 5 and 6 store the two-letter country code, followed by a two-character location code in positions 7 and 8.
An optional three-character branch code occupies positions 9 to 11. When you click Check numbers on a single code, the results card produces a full SWIFT code breakdown, splitting these segments into a formatted string and displaying each decoded field. You can also validate bank account IBAN checksums alongside BICs before initiating international wires.
Validating ISO 3166-1 alpha-2 country prefixes locally
Because random two-letter combinations can look plausible, our validator checks positions 5 and 6 against the full ISO 3166-1 alpha-2 country registry using the browser’s Intl.DisplayNames region database. If someone enters an unassigned country pair, the error message flags positions 5 and 6 immediately.
Exactly 0 bytes of your beneficiary bank codes leave the browser during this lookup. Both 8-character primary-office codes and 11-character branch codes are normalized to uppercase with spaces stripped.
Why do location flags and missing check digits matter in ISO 9362?
Because ISO 9362 contains no mathematical check digit, a single mistyped letter in an institution prefix can still look syntactically valid. Position-level rules for location and branch characters therefore provide the primary safeguard against test codes, passive-only participants, and invalid formatting.
Spotting test, passive, and reverse-billing BIC indicators
Position 7 of a BIC must be a letter from A to Z or a digit from 2 to 9, never 0 or 1. Position 8 may be any letter except O, or the digits 0, 1, or 2.
When position 8 is 0, the decoder warns that the code is a test-and-training BIC that cannot process live funds. A 1 flags a passive SWIFT participant, while 2 marks a reverse-billing BIC. Clearing hubs such as the Deutsche Bundesbank SEPA-Clearer SCL Directory publish live routing tables for active SEPA participants.
Why branch codes cannot start with X unless XXX
An 8-character BIC represents an institution’s primary office and is equivalent to appending XXX. When an 11-character code specifies a branch, ISO 9362 forbids starting the three-character branch suffix with X unless all three characters are XXX.
Treasury teams onboarding European suppliers often pair bank-code validation with entity tax checks. Before paying French vendors, you can check 14-digit French SIRET and 9-digit SIREN numbers in the same offline workspace.
ISO 9362 position rules and common validation failures
Understanding how each character slot is constrained helps finance teams diagnose rejected wire templates quickly. Under EU SEPA Regulation (EU) No 260/2012 on EUR-Lex, IBAN-only routing applies to domestic and cross-border euro transfers inside the EEA, yet non-SEPA wires and legacy ERP feeds still validate BICs strictly.
| BIC position | Length | Permitted characters | Common validation error |
|---|---|---|---|
| Positions 1–4 (Institution) | 4 chars | A–Z, 0–9 |
Fewer than 4 characters or punctuation |
| Positions 5–6 (Country) | 2 chars | Assigned ISO 3166-1 alpha-2 | Digits or unassigned country letters |
| Position 7 (Location 1) | 1 char | A–Z, 2–9 |
Leading 0 or 1 in location |
| Position 8 (Location 2) | 1 char | A–N, P–Z, 0–9 |
Letter O or test flag 0 |
| Positions 9–11 (Branch) | 3 chars (optional) | XXX or [A–W,Y–Z,0–9][A–Z,0–9]{2} |
Starts with X (e.g. X01) or wrong length |
When preparing batch Euro payment files, you can paste validated BICs and IBANs directly into the SEPA XML generator to build ISO 20022 pain.001 or pain.008 XML payloads locally.
Batch beneficiary screening, Excel export, and compliance scope
Accounts payable teams migrating vendor master files can use this bulk BIC validator to paste up to 1,000 newline-separated codes within the 50 KB (50,000-character) input limit. Clicking Load example loads sample passing and failing codes so you can preview the batch table layout and error messages immediately.
Auditing 1,000-row payment lists with CSV and XLSX export
Multi-line checks display All, Passed, and Failed filter buttons along with a summary count of passing rows. Click Download results (CSV) for a UTF-8 BOM spreadsheet or Download Excel (.xlsx) to generate an Excel workbook inside a local Web Worker.
Tip: Use Copy formatted (
DEUT DE FF) for human-readable vendor sheets and Copy compact (DEUTDEFF) when pasting into banking portals or ERP import columns.
Format validation versus live SWIFT reachability checks
As summarized in the European Central Bank SEPA Retail Payments Overview, payment routing depends on active clearing participation in addition to valid syntax. When auditing European counterparties, you can also verify Italian supplier tax IDs locally without network calls alongside their banking codes.
This validator and guide are provided for informational purposes and format screening only, not as financial, banking, or compliance advice. Because ISO 9362 does not verify whether a BIC is active or belongs to a specific account, always confirm live routing details with your bank or a qualified financial advisor before releasing payments.