Developer Tools · Batch checks

Bulk IBAN validator.

Paste a column of IBANs or open a payment-run CSV. Each row gets a pass or fail with the reason, and you can export the results. Nothing is uploaded.

Short answer: an IBAN is valid in structure when it has the right length for its country and the rearranged number leaves a remainder of 1 when divided by 97. This page applies both tests to every row against a table of 86 country lengths. It cannot say that the account exists.

Checked in your browserSources retrieved 20 October 2026

The two tests applied to every row

ISO 13616 defines the IBAN: a two-letter country code, two check digits, and a country-specific account number, to a maximum of 34 characters. The check digits are computed with the MOD 97-10 method from ISO 7064. This tool runs both layers. First the length, which is fixed for each country: 22 for Germany and the United Kingdom, 27 for France and Italy, 15 for Norway, 28 for Poland and so on. Then the checksum.

The checksum moves the first four characters to the end, replaces each letter with two digits (A is 10, B is 11, up to Z at 35), and divides the resulting long number by 97. A valid IBAN leaves 1. The tool computes the remainder digit by digit, so a 34-character IBAN needs no big-number maths and a file of 20,000 rows is checked in well under a second. Check digits 00, 01 and 99 are refused outright, since the standard's range is 02 to 98.

Worked example

GB82 WEST 1234 5698 7654 32 is the example published for the United Kingdom. It is 22 characters, the right length for GB. Rearranged it reads WEST12345698765432GB82, which becomes 3214282912345698765432161182, and that number leaves a remainder of 1 when divided by 97, so it passes.

Now swap two neighbouring digits near the end, so that ...5432 becomes ...5342, to make GB82WEST12345698765342. The length is unchanged, but the remainder is 93, so the row fails with the message MOD 97-10 check fails (remainder 93, must be 1). Drop one digit instead and the row fails earlier, on length, with the message that GB IBANs are 22 characters and this one has 21. Seeing which test failed is what lets you decide whether a typo or a truncated cell is the problem.

Countries the table does not cover

The length table has the 86 countries listed in the IBAN registry as reproduced on Wikipedia, which we fetched on 20 October 2026. The registry grows over time, and some countries use pseudo-IBANs or were added after our table. For a country code that is not in the table, the tool still runs the MOD 97-10 check and, on a pass, reports the row as passing with the note checksum only, so the length was not verified. It never marks an unknown country invalid on that basis.

The tool does not check the national account structure inside the IBAN, such as a German bank code (BLZ) or a French RIB key. Those inner formats differ by country, and a row with a correct length and checksum can still hold a bank code that no bank uses.

Using the batch controls

Paste one IBAN per line or open a .csv, .tsv or .txt file up to 5 MB. Pick the column number and tick the header box if the file has several columns, such as payee name, IBAN and amount. Lower-case letters, spaces and hyphens are accepted and normalised in the export, so you can paste IBANs as printed on an invoice. Filter to failures to build a correction list, or download the full results CSV with line numbers matching your source file.

Repeated IBANs are flagged as duplicates of an earlier row. This is a quick way to spot a payee entered twice in a payment file, though you should still use your bank's own pre-validation before submitting a batch.

Privacy

IBANs are account identifiers, and payment files can be sensitive. The list is parsed inside a sandboxed frame on this page with no network access, nothing is written to cookies or local storage, and the only output is a CSV you download yourself. The ads on the page are outside the frame.

Common mistakes

Do not read a pass as proof that an account is open: only the bank can say that. Do not paste BIC or SWIFT codes in the same column as IBANs. Do not rely on a spreadsheet to keep long numbers intact: IBANs that start with digits after the country code are text, but a column auto-formatted as a number can turn a long string into scientific notation. And remember that a few countries print IBANs with different grouping, which is why spaces are stripped before the test.

Common mix-ups

  1. ISO 13616-1:2020 International bank account number
  2. ISO/IEC 7064:2003 check character systems

Checked against these sources on .

Frequently asked questions

What does the IBAN check actually verify?

That the country code and length match, that the check digits are in the allowed range, and that the rearranged number leaves a remainder of 1 under MOD 97-10. It does not verify that the account exists.

How many countries does the length table cover?

86 countries, taken from the IBAN registry as reproduced on Wikipedia and fetched on 20 October 2026. Other country codes get a checksum-only result.

Why does an IBAN from an unlisted country pass?

If the country is not in the table, the tool cannot check length, so it reports a pass on the checksum alone and says so in the result. It does not call unlisted countries invalid.

Are spaces and lower case allowed?

Yes. Spaces, hyphens and dots are removed and letters are upper-cased before the test. The export shows the normalised IBAN.

Can I validate a whole payment file?

Yes, up to 5 MB and 50,000 rows. Choose the column that holds the IBANs and tick the header box if the first row has titles.

Does it check the BIC or the bank code?

No. It checks the IBAN as a whole only. Bank codes inside the IBAN are not validated against any bank directory.

Is my file uploaded?

No. It is read in your browser inside a frame with no network access. The only output is the CSV you download.

Why were check digits 00 or 99 rejected?

The standard's check digits range from 02 to 98. A value outside it cannot be correct even if the arithmetic happened to work.

Sources

Retrieved

Format check only — not a lookup

This page tests whether each value is structurally valid under the published rule. It does not contact any registry, bank, carrier or issuer, and a pass does not show that a number was issued, is active or belongs to anyone. Your list is processed in your browser and is not uploaded.

Advertisement
Advertisement