Belgium IBAN Generator
Free test BE IBANs: 16 characters, official registry format, valid check digits.
Belgium IBAN generator
16-character format, official registry structure.
Same country + seed + row order gives the same test values. Leave blank for random samples. Seed algorithm: v1. Do not enter personal data.
Belgium IBAN format
A Belgium IBAN is 16 characters long: the BE country code, 2 check digits, and a 12-character BBAN (3 digits + 7 digits + 2 digits). Here is how a generated test IBAN breaks down:
| Part | Example | Format |
|---|---|---|
| Country code | BE | 2 letters (ISO 3166) |
| Check digits | 43 | 2 digits: mod-97 checksum |
| Bank code | 370 | 3 digits |
| Account number | 472614783 | 7 digits + 2 digits |
Full test IBAN: BE43 3704 7261 4783 (random test value)
About Belgium IBANs
- Belgium's IBAN is only 16 characters: the shortest widely-used format in Europe.
- The 12-digit BBAN is itself a national account number with its own mod-97 check: the last two digits equal 97 minus the first ten mod 97 (or 0 maps to 97).
- Belgian IBANs are all-numeric after the country code.
Use test Belgium IBANs for
- Testing payment forms that accept Belgium bank details.
- QA fixtures and demo data with the correct 16-character structure.
- Validating your own mod-97 implementation against known-correct outputs.
Country-specific testing notes
Belgium uses domestic check digits at the end of the national account structure. This generator does not calculate that domestic rule, so a local format pass is not a Belgian account-validation pass.
Test more than the happy path
Generate with seed country-regression-v1, preserve the selected country and quantity, then run again to reproduce the same rows. Include an invalid-checksum input and a shorter input in your form tests. The versioned fixture pack supplies expected results for the implemented format checks.
Interpret the result correctly
Our checks cover the registered length, character pattern and international check digits. They do not certify domestic checksums, reserved-value rules, active bank codes, account existence or recipient ownership. Use bank-issued details for payments and your provider’s documented sandbox values for integration tests.