IBAN Example: 4 Synthetic Formats Explained

Quick answer: what an IBAN example means

An IBAN example is a readable sample that demonstrates the layout of an International Bank Account Number. It normally starts with a two-letter country code, followed by two international check digits, and then a country-specific Basic Bank Account Number, or BBAN. The BBAN is where bank, branch, account, and domestic-check fields vary.

A useful example teaches the pattern without pretending to be payment information. The four values on this page are synthetic test strings generated to illustrate length and checksum behavior. They are not assigned to a customer, do not prove that a bank or account exists, and should never be copied into a transfer form.

• Use an example to understand a format or document a test case.
• Use a bank-issued value when you need to receive or send money.
• Use a checker for structure and MOD-97 consistency, not for ownership verification.

Four synthetic IBAN examples by country

The table uses deliberately synthetic BBAN values. Germany and France use numeric BBAN characters in these examples, while the United Kingdom and the Netherlands show alphabetic bank identifiers. The values pass the mathematical MOD-97 check used by this site's browser tools, but that result is only a format signal.

Print spacing is included because people often search for an IBAN number example after seeing a grouped value on a statement. The electronic form removes those spaces. Always follow the receiving bank's input instructions rather than assuming a printed presentation is the stored value.

• The word TEST in two examples is a visual cue that the value is synthetic.
• Zeros are used as neutral placeholders, not as a claim about a bank's account numbering.
• A country code and correct length do not establish a real bank assignment.

How to read an IBAN example

Start from the left. The first two characters identify the registered country format. The next two digits are international check digits used by the MOD-97-10 procedure. Everything after those four characters belongs to the national BBAN. A decoder can display those visible pieces, but it cannot infer an account holder or a bank's current directory status from the string alone.

For example, the synthetic German value begins with DE36 and then continues with an 18-character BBAN. The synthetic UK value begins with GB75 and contains letters in its bank-identifier positions. Those differences are why a single universal mask is unsafe. Select the country rule first, then check the corresponding length and allowed character classes.

1. Identify the countryRead the two-letter prefix and compare it with the country rule being tested.
2. Separate the check digitsTreat the two digits after the country code as the international checksum fields.
3. Read the BBANInterpret the remaining characters using that country's bank, branch, account, and domestic-field layout.
4. Check the boundaryRemember that structural validity is not proof of an assigned or reachable account.

Why an IBAN format example changes by country

IBAN standardization does not make every national account structure identical. The shared outer layer makes international communication easier, while each registered country keeps its own BBAN length, character rules, and field boundaries. That is why a UK and German IBAN can both contain 22 characters while looking different internally.

The country directory is the right place to compare registered lengths and broad patterns. The IBAN Decoder is better when you already have a complete string and want to see its visible pieces. Do not turn the examples in this article into a name-based lookup or a way to invent payment details.

Print format vs electronic IBAN format

A printed IBAN often groups characters in blocks of four so a person can read or compare the value more easily. An electronic field normally expects the same characters without spaces. Removing presentation spaces does not change the underlying IBAN, but deleting or adding a character does.

When copying from a PDF or statement, compare the first and last characters after normalization. If a form rejects the value, check whether it expects spaces, no spaces, uppercase letters, or a specific country format. The IBAN Checker can help find length, character-pattern, and checksum problems locally in the browser.

1. Keep the originalRetain the bank-issued presentation before removing display spaces for a form.
2. Normalize only presentationRemove spaces or punctuation only when the receiving field requires the electronic form.
3. Compare boundariesCheck the prefix, final characters, account name, and selected currency before sending.
4. Confirm important paymentsUse a trusted second channel when payment instructions arrive by email or chat.

An IBAN example is not a real bank account

A checksum-valid example can still be unassigned, inactive, or unsuitable for a payment. Mathematical validity says that the characters fit a registered pattern and that the MOD-97 calculation returns the expected result. It does not query a bank, confirm a beneficiary, or prove that funds can reach the account.

This distinction matters because searchers sometimes ask for a valid IBAN example and then paste it into a real transfer. Treat every sample on this page as documentation or test data. For your own account, retrieve the value from a current statement, authenticated online banking, a mobile banking app, or the bank itself; the IBAN lookup guide explains those safer sources.

• Do not use a public example for payroll, direct debit, invoices, refunds, or international transfers.
• Do not infer an IBAN from a person's name, card number, or a partial local account number.
• Do not describe a checksum pass as proof of ownership, account existence, or payment success.
• If you need synthetic fixtures, isolate them from production payment flows and label them as test data.

When an IBAN example is useful

Examples are helpful for form design, QA cases, documentation, training, screenshots, and regression tests. A good test set includes more than one country: include a short format such as the Netherlands, a longer format such as France, numeric and alphabetic BBAN characters, print spacing, lowercase input, an altered check digit, and values that are one character too short or too long.

For development workflows, the site's IBAN Calculator can calculate check digits from a complete supported BBAN, while the Bulk IBAN Generator can create synthetic rows for QA. These tools are intentionally browser-based and should remain separate from real customer payment data.

• Documentation: show the country pattern before explaining field validation.
• QA: test normalization, length, allowed characters, and checksum errors separately.
• Training: explain why an IBAN is different from a local account number or SWIFT/BIC.
• Production: obtain current account details from the bank or account holder instead of a public example.