"IBAN Invalid": Fixing a Rejected Bank Transfer

You copied the IBAN from an invoice, pasted it into your bank's transfer form, and the form refuses it. Here is what that message actually checks, and the fastest order to work through the causes.

What this error actually means

When a banking app flags an IBAN as invalid before you submit, it has not contacted the receiving bank — it has run a purely local, mathematical test on the string you typed. An IBAN (ISO 13616) carries its own error detection: two check digits in positions 3 and 4, computed with the MOD-97 algorithm, plus a fixed length and layout per country. If any single character is wrong, the arithmetic fails and the form rejects the number on the spot.

"Invalid" here means malformed: the string cannot be a correctly written IBAN. It does not mean the account is closed or fraudulent — and the absence of the error does not mean the account is fine. We will come back to that gap.

The fix path, in order of likelihood

1. Clean the string first. The most common "invalid IBAN" is not a wrong digit at all — it is a paste artifact. Delete every space (IBANs are printed in blocks of four; some forms choke on them or on invisible characters from a PDF), and make every letter uppercase. Then hunt the look-alikes: letter O for zero, I or lowercase l for 1. The shape helps: the first two characters are always letters (the country code), the next two always digits — if you see DEO2..., that O is a zero.

2. Check the length against the country. Every IBAN country has one fixed length — no tolerance. A German IBAN is exactly 22 characters, French and Italian IBANs 27, Spanish 24, Dutch 18; across all countries the range runs roughly from 15 to 34. If your string is 21 characters and starts with DE, a character was lost — typically at a line break, where the invoice layout split the IBAN and one block never made it into your clipboard. Count before you retype anything.

3. Run the checksum. Paste the cleaned string into our IBAN checker. It normalizes spacing, checks country code and length, and runs the same MOD-97 test your bank runs — catching every mistyped character and every swapped adjacent pair (the math is in how check digits work). If it fails here too, a character is genuinely wrong. Do not guess which one — get the IBAN re-sent, below.

4. If the checksum passes but the payment still fails, the number is not the problem. A valid IBAN proves only that the string is internally consistent — not that the account exists or is open. If your bank accepts the transfer and the money later comes back, the receiving bank refused it: commonly a closed account, or a bank code that no longer routes anywhere after a merger. No online checker, including ours, can see account status. The fix is a conversation with the beneficiary, not another validation pass.

5. A name-mismatch warning is a different animal. Since 9 October 2025, EU regulation 2024/886 requires euro-area banks to run Verification of Payee on SEPA credit transfers, standard and instant alike: your bank asks the receiving bank whether the beneficiary name you typed matches the name registered to that IBAN, and reports match, close match, no match, or "verification not possible." A "no match" is not an invalid-IBAN error — the number is well-formed — but it warns that the account may not belong to who you intend. You can usually proceed at your own risk; the better move is to confirm the registered account-holder name with the beneficiary — even an innocent mismatch (trading name vs. legal name) is worth resolving before money moves.

What to ask the beneficiary to re-send

When cleanup did not fix a failing checksum, stop squinting at the invoice. Ask the beneficiary for three things:

• The IBAN as selectable text, copied directly out of their online banking or a bank statement — not a photo or screenshot, and not retyped by hand. Every retyping is a fresh chance for the same class of error.
• The account holder name exactly as registered with their bank, including legal form (GmbH, S.r.l., Ltd) — this is what Verification of Payee compares against.
• The BIC/SWIFT code, if the transfer leaves the SEPA area.

When you must read an IBAN off a printed or PDF invoice, do it defensively: find the country code, look up that country's fixed length, and count what is printed. Watch line endings — a break mid-IBAN is where characters go missing — and read 0/O and 1/I in context. A foreign country code is not automatically wrong (businesses can legitimately bank abroad); validate the structure, then confirm anything surprising with the beneficiary. Paying a new supplier for the first time? Test their VAT number with our VAT number validator; if that fails, see fixing a VIES "invalid VAT number" result.

What to send support if nothing works

If the cleaned string passes the IBAN checker but your bank's form still refuses it, the problem is likely on the bank's side — an outdated country table, a validation bug, or a restriction on that destination. Give support: the IBAN with spaces removed, the exact error text and where it appears (at entry, or after submission), a screenshot, the destination country, and the fact that the number passes an independent ISO 13616 structure and MOD-97 check. That last point tells the agent this is not a typo ticket.

What won't work

Two dead ends worth naming. Do not "repair" an IBAN by nudging digits until a checker accepts it — several one-character changes can each yield a checksum-valid string, and one may be a stranger's real account. And do not assume a green result from any IBAN tool — ours included — means the money will arrive: structure validation cannot see whether an account is open, whose name is on it, or whether it accepts the currency. Those answers come only from the beneficiary and the banks.

And if you are wiring money to the United States, there is no IBAN at all — US accounts use a nine-digit routing number plus an account number: see fixing an "invalid routing number" error and our routing number validator.

FAQ

Does a valid IBAN mean the bank account is open?

No. Passing the MOD-97 checksum only means the IBAN is internally consistent. It says nothing about whether the account exists, is open, or belongs to the person you think it does; a transfer to a well-formed IBAN can still be returned if the account has been closed.

My bank shows a name mismatch warning instead of an invalid IBAN error. Is the IBAN wrong?

Not necessarily. Since 9 October 2025, euro-area banks must run Verification of Payee on SEPA credit transfers, comparing the beneficiary name you typed against the name registered to that IBAN. A close-match or no-match result is a warning about the name, not a statement that the IBAN is malformed. Confirm the registered account holder name with the beneficiary before proceeding.

Why does my bank reject an IBAN that an online checker says is valid?

They test different things. A checksum tool validates structure: country code, length, and the MOD-97 remainder. Banks can also check what a checksum cannot see — whether the bank code inside the IBAN routes to a real institution, whether the account is open, whether it accepts the currency. If the structure is valid but the payment is refused or returned, the problem is on the account side, not the number's format.

Can I fix an invalid IBAN by changing one digit myself?

No. Several different single-character changes can each produce a checksum-valid string, and one of them may be someone else's real account. The only safe fix is to get the IBAN again from the source, copied by the beneficiary directly from their online banking and sent as selectable text.

This guide is for general information only and is not financial advice. IBAN structure validation confirms internal consistency, not that an account is open, correctly named, or safe to pay. Verification of Payee is implemented by individual banks and may look different in your app. Always confirm payment details with the beneficiary through a channel you trust before sending money.