Registered country format
Each issuing country or territory has a fixed IBAN length and a published national structure. The validator compares the input with that record.
Randommer banking-format utility
IBAN Account Validator for country format and checksum checks.
Use the Randommer IBAN Account Validator to remove spaces, identify the country, compare the registered IBAN length, review the national character structure and calculate the MOD-97 checksum. The tool can help identify common typing and copying errors before you confirm payment details with the account holder or financial institution.
- 89 registered country and territory formats
- MOD-97 checksum calculation
- Browser-based responsive tool
Three parts of an IBAN check
Country registration, national structure and checksum work together.
A meaningful format review should check more than the first two letters or the total number of characters.
Character structure
The bank and account section may require digits, letters or alphanumeric characters in particular positions depending on the issuing jurisdiction.
MOD-97 checksum
The two check digits are evaluated using the international IBAN checksum calculation to identify many common transcription mistakes.
How to use the validator
Check an IBAN in four clear steps.
The result explains every major check rather than displaying only a single valid or invalid label.
-
Paste the IBAN
Enter the account identifier from the invoice, beneficiary instructions, banking document or account holder.
-
Normalize the value
Randommer removes spaces and common separators, converts letters to uppercase and identifies the first two characters as the country code.
-
Run structural checks
The tool checks the current registered length, national character pattern and whether the optional selected country matches the prefix.
-
Review the checksum
The validator calculates the MOD-97 remainder and clearly states whether the mathematically expected result is present.
What does an IBAN Account Validator actually check?
IBAN stands for International Bank Account Number. It is a standardized account identifier used to support automated domestic and cross-border payment processing in participating countries. Every IBAN starts with a two-letter country code and two check digits, followed by a country-specific Basic Bank Account Number structure.
The Randommer IBAN Account Validator uses the country formats published in the Swift IBAN Registry. This page was generated from Registry Release 102, dated June 2026, and includes 89 registered country and territory entries. Because national standards bodies and central banks can request updates, the embedded data should be reviewed when Swift publishes a newer registry.
Why IBAN lengths differ by country
The international standard defines the overall framework, but the national bank-account section is determined by the issuing country. One country may use a short numeric bank and account structure, while another may include branch codes, letters or a longer alphanumeric account reference. This is why checking only whether an IBAN is under the general maximum length is not sufficient.
How the MOD-97 checksum works
For checksum validation, the first four characters are moved to the end. Letters are converted into numbers, with A represented as 10 and Z as 35. The resulting long numeric value is processed using modulo 97. A correctly formed IBAN produces a remainder of 1.
What a successful result means
A successful result means that the country code appears in the embedded registry, the total length matches the registered format, the characters follow the published national structure and the checksum is mathematically consistent. It is useful for identifying many typing, spacing and copying errors before a payment instruction is submitted.
What a successful result does not mean
Mathematical validity does not establish that the bank account currently exists, is open, accepts a particular currency, belongs to the stated beneficiary or is safe to pay. A fabricated or outdated account identifier can still pass the structural and checksum tests.
Account-name and payee verification
Some banks and payment systems provide confirmation-of-payee or verification- of-payee services that compare an account identifier with the beneficiary name. That is a separate service performed by a payment provider or bank. A browser-based format validator does not have access to the account holder’s private banking record.
IBAN and BIC are not the same
The IBAN identifies the customer account according to the national IBAN format. A BIC, often called a SWIFT code, identifies a financial or business institution. Payment instructions may request one or both depending on the destination, channel and payment provider.
Why copied IBANs should still be confirmed
Payment-detail fraud can involve altered invoices, compromised email accounts or last-minute beneficiary changes. Even when the IBAN Account Validator reports a correct format, confirm unexpected account changes through a trusted communication channel before approving a transfer.
Keep the registry data current
Swift acts as the ISO registration authority for national IBAN formats and publishes the technical registry. When this page is maintained, compare the embedded country list, lengths and structures against the newest available registry release.
Country-format examples
IBAN lengths and structures are country specific.
The dropdown includes all 89 entries loaded from the current source registry. These examples show a selection of commonly searched formats.
United Arab Emirates (The)
23 characters · Example: AE070331234567890123456
United Kingdom
22 characters · Example: GB29NWBK60161331926819
Germany
22 characters · Example: DE89370400440532013000
France
27 characters · Example: FR1420041010050500013M02606
Italy
27 characters · Example: IT60X0542811101000000123456
Spain
24 characters · Example: ES9121000418450200051332
Netherlands (The)
18 characters · Example: NL91ABNA0417164300
Saudi Arabia
24 characters · Example: SA0380000000608010167519
Qatar
29 characters · Example: QA58DOHB00001234567890ABCDEFG
Switzerland
21 characters · Example: CH9300762011623852957
Austria
20 characters · Example: AT611904300234573201
Belgium
16 characters · Example: BE68539007547034
Registry reference: The validator data is based on Swift
IBAN Registry Release 102 – June 2026. Examples demonstrate structure and
checksum behavior; they are not payment instructions.
Common use cases
Where IBAN validation supports a careful workflow.
A format and checksum check can be a useful early control before official beneficiary confirmation and payment authorization.
Supplier Onboarding
Identify malformed account identifiers before saving supplier banking details in procurement, ERP or accounting records.
Invoice Review
Screen an IBAN copied from an invoice before comparing it with the approved supplier master data and payment instructions.
Customer Refunds
Check the structure of a refund destination before asking the bank or payment team to complete the beneficiary verification.
Form Validation
Use the same logic as a reference when designing front-end validation for payment forms, onboarding systems and internal finance applications.
Data Cleanup
Normalize spaces and casing before importing bank-account identifiers into a CRM, ERP, treasury platform or controlled spreadsheet.
Quality Assurance
Test valid and invalid examples when reviewing payment interfaces, checksum functions and error-message behavior.
Use the result correctly
A valid IBAN is not the same as a verified payee.
Separate the technical checks performed by this page from the banking and business checks required before sending funds.
The validator can confirm
- The prefix appears in the embedded Swift registry data.
- The IBAN has the expected registered length.
- The letters and digits follow the registered structure.
- The MOD-97 checksum produces the expected remainder.
- The entered value is internally consistent as an IBAN string.
The validator cannot confirm
- The account is open or able to receive a transfer.
- The IBAN belongs to the person or company named on an invoice.
- The receiving institution is trustworthy.
- The requested payment is legitimate or contractually correct.
- The account supports the intended payment type or currency.
Local
Validation
Validation
Treat every IBAN as sensitive financial information.
The validation logic in this HTML page runs in the browser and does not require an external validation API. The country registry data is embedded in the page, and the checksum calculation is performed locally.
That local design does not automatically guarantee the privacy behavior of the final published website. Analytics, session recording, advertising, tag-management tools and other third-party scripts may observe form interactions depending on their configuration.
Before launch, review every external script, avoid logging complete IBANs, mask sensitive values in error reporting and explain data handling accurately in the website’s privacy notice.
Related Randommer tools
Continue with business and data utilities.
Connect the IBAN Account Validator to related format, tax and developer tools for clearer navigation.
Check the IBAN structure before confirming the payee.
Use Randommer to identify format and checksum errors, then complete the account-holder and payment verification required by your bank or organization.
Frequently asked questions
Questions about IBAN account validation.
These answers explain the technical result and the additional checks needed before relying on payment instructions.
It checks whether the country code is supported, the total length matches the registered format, the characters follow the national structure and the MOD-97 checksum is mathematically valid.
No. It proves only that the IBAN string is structurally and mathematically consistent. It does not confirm account existence, status, ownership or payment capability.
The IBAN is rearranged, letters are converted into numeric values and the resulting number is processed modulo 97. A valid IBAN produces a remainder of 1.
Every registered country defines its own Basic Bank Account Number structure within the international IBAN framework, so the fixed total length differs between jurisdictions.
Printed IBANs are commonly grouped with spaces for readability. Electronic processing normally uses the compact form without spaces. Randommer accepts common separators and normalizes the value.
No. An IBAN identifies a customer account according to a national format. A BIC or SWIFT code identifies a financial or business institution.
The code in this page performs validation locally in the browser. Review all third-party scripts on the final website before making a complete privacy claim about the published page.
Confirm the beneficiary name and account details through your bank or approved business process, especially when payment instructions are new or have changed unexpectedly.
Financial-safety notice: This page performs technical format
and checksum validation only. Confirm beneficiary ownership and payment
instructions through a trusted bank or authorized business process before
transferring funds.