IBAN Breakdown: Decode Every Field of an International Bank Account Number

An IBAN (International Bank Account Number) looks like a long, intimidating string of letters and digits, but every character in it has a precise job. The first two letters identify the country, the next two digits are a mathematical checksum, and everything after that — the BBAN — encodes the bank, the branch, and the customer's account number according to national rules. Once you know how to read these fields, an IBAN stops being opaque and becomes a structured, verifiable address for money.

The free IBAN Breakdown tool does this decoding for you instantly. Paste any IBAN and it splits the string into its ISO 13616 components — country code, check digits, BBAN, bank code, branch code, and account number — displays each field in a color-coded segment view, and validates the number against 90+ country specifications, including the mod-97 checksum. Everything runs 100% in your browser, so sensitive account data never leaves your device.

In this guide, we'll walk through how the tool works, what each part of an IBAN actually means, how the mod-97 checksum algorithm catches typos, and the practical situations where breaking down an IBAN saves you time and money.

Why Use the IBAN Breakdown Tool?

• Understand what you're paying. Before you send an international transfer, see exactly which bank, branch, and account the IBAN points to — instead of trusting a wall of characters.
• Catch typos before they cost you. The mod-97 checksum validation flags transposed digits and mistyped characters instantly, so a bad number never reaches your bank.
• Country-aware decoding. The tool knows the BBAN structure of 90+ countries, so it can separate bank code, branch code, and account number correctly for GB, DE, FR, IT, ES, NL, and many more.
• Instant validity verdicts. Length, character set, and checksum are each checked and reported separately, telling you not just that an IBAN is invalid but why.
• Privacy by design. All parsing and validation happen client-side in your browser. No IBAN you enter is ever transmitted to a server.
• Free and unlimited. No sign-up, no quotas — break down as many IBANs as you need, whether it's one invoice or a whole vendor file.

Key Features

• Per-country intelligence. A German IBAN and a French IBAN are structured completely differently inside the BBAN. The tool applies the right template for each country — for example, France uses a 5-digit bank code, 5-digit branch code, 11-character account number, and 2 national check digits, while the Netherlands uses a 4-letter bank code and a 10-digit account number.
• Granular validation. Rather than a single pass/fail, you get three separate verdicts: length OK, charset OK, checksum OK. That granularity makes it trivial to diagnose what's wrong with a malformed number.
• Zero data exposure. Because validation is pure client-side computation, the tool is safe to use even on confidential beneficiary data.

How to Use the IBAN Breakdown Tool

1. Open the tool. Go to IBAN Breakdown in any modern browser — no installation or account required.
2. Paste your IBAN. Enter the full IBAN, with or without spaces (e.g. GB82 WEST 1234 5698 7654 32). Spaces are stripped automatically.
3. Read the segmented breakdown. The tool displays the country code, check digits, and BBAN as color-coded segments, then decodes the BBAN into bank code, branch/sort code, and account number.
4. Check the validity verdicts. Review the length, charset, and mod-97 checksum results. If any check fails, the tool tells you which one.
5. Act on the result. Copy the individual fields into your payment system, ERP, or support ticket with confidence that the number is structurally sound.

Understanding IBAN Structure: A Field-by-Field Deep Dive

Every IBAN in the world follows the same three-part skeleton defined by ISO 13616:

• Country code (2 letters). The first two characters are an ISO 3166-1 alpha-2 country code — GB for the United Kingdom, DE for Germany, FR for France. This determines the total length and the BBAN layout.
• Check digits (2 numbers). Positions 3–4 are computed with the mod-97 algorithm and protect the entire IBAN against transcription errors.
• BBAN (variable length). The Basic Bank Account Number is the country-specific tail containing the bank code, branch code, account number, and sometimes national check digits. Its format and length differ from country to country.

Here is the full breakdown of our example, GB82 WEST 1234 5698 7654 32:

Germany's DE89 3704 0044 0532 0130 00 shows a different national flavor: an 8-digit bank code (37040044) followed directly by a 10-digit account number (0532013000), with no branch code at all.

The mod-97 checksum, step by step

The check digits are not arbitrary — they are the result of a precise algorithm:

1. Rearrange. Move the first four characters (country code + check digits) to the end of the string. GB82WEST12345698765432 becomes WEST12345698765432GB82.
2. Convert letters to numbers. Replace each letter with its numeric value, where A=10, B=11, …, Z=35. WEST becomes 32142829 and GB becomes 1611, yielding the giant integer 3214282912345698765432161182.
3. Compute mod 97. Divide that number by 97 and take the remainder. If the remainder is exactly 1, the IBAN passes the checksum. For our example it does — which is why GB82… is structurally valid.

A single mistyped digit or transposed pair will almost always produce a different remainder, which is why this check catches the vast majority of manual entry errors.

IBAN lengths vary dramatically by country: Norway (NO) uses just 15 characters, while Saint Lucia (LC) uses 32. That's why "it looks too short" is never a valid reason to reject an IBAN — you need the country specification, which the tool applies automatically.

Practical Use Cases

Verifying an invoice beneficiary before a transfer

Accounts payable teams receive invoices with IBANs embedded in PDFs, often re-typed by hand. Breaking down the IBAN before releasing payment lets you confirm the country matches the supplier's address and that the checksum passes — stopping misdirected payments and the weeks-long recovery process that follows.

Debugging rejected SEPA payments

Support and treasury teams frequently see SEPA transfers bounce with cryptic "invalid beneficiary account" errors. Running the IBAN through the breakdown tool pinpoints the cause in seconds: wrong length for the country, an illegal character in the BBAN, or a failed mod-97 check — each reported as its own verdict.

Developers implementing IBAN validation

If you're building payment forms, payout systems, or banking APIs, the tool is a fast way to generate and verify test cases. Inspect how different countries structure their BBANs — Italy's check character, Spain's domestic check digits, the Netherlands' alphabetic bank code — and mirror that logic in your own validation layer.

Cleaning vendor master data

Finance teams migrating or deduplicating vendor records can use the breakdown to normalize stored IBANs, detect duplicates that differ only by spacing, and flag records whose checksum fails before they pollute a new ERP system.

Best Practices for Working with IBANs

• Always validate before you pay. A two-second checksum check is infinitely cheaper than recalling a misrouted wire transfer.
• Store IBANs without spaces. Spaces are a display convention only; keep the compact electronic format in databases and APIs.
• Respect country lengths. Never hardcode a single IBAN length — validate against the per-country specification instead.
• Use the checksum, but don't rely on it alone. Mod-97 catches most typos, but a structurally valid IBAN can still belong to the wrong person. Cross-check the beneficiary name where possible.
• Treat IBANs as sensitive data. Account numbers are personal data under many privacy regimes — use client-side tools like this one when handling them ad hoc.
• Pair IBAN with BIC. For cross-border payments outside SEPA, the IBAN usually needs to accompany a SWIFT/BIC code for the beneficiary bank.

Conclusion

An IBAN is not a random string — it's a carefully engineered, internationally standardized address for a bank account, and every field in it is checkable. Whether you're approving an invoice, debugging a failed payment, or building validation into your software, understanding the anatomy of an IBAN turns guesswork into verification.

Try the IBAN Breakdown tool now: paste any IBAN, see every field decoded in color, and get length, charset, and mod-97 verdicts instantly — all without your data ever leaving the browser.

Related Tools You Might Like

• IBAN Validator
• SWIFT/BIC Validator
• VIN Decoder

Happy decoding!