Nothing stalls a cross-border payment faster than the words "invalid IBAN". One bad character and your transfer bounces back days later, minus a correspondent-bank fee and a lot of goodwill. If you have ever stared at a 22-character string wondering which digit is wrong, this guide walks through the five IBAN validation errors that cause the vast majority of rejections — what they look like, why they happen, and exactly how to fix them before you hit send.
We will also cover a symptom-to-cause troubleshooting table, three real-world case studies with dollar costs, and the data on how often IBANs actually fail — so you can stop guessing and start fixing.
The 30-second version
An IBAN is rejected when it fails one of four checks: character set, country code, length, or the MOD 97 check digits. The single most common failure is a MOD 97 mismatch — almost always caused by a one-digit typo. You can catch all five errors below in seconds with our IBAN validator before you ever submit a payment.
What happens when an IBAN is rejected
When a bank receives a payment instruction, the first thing its payment engine does is run an IBAN structural validation against ISO 13616. If the IBAN fails that check, the message is rejected before any money moves — usually with a status code like AC02 ("account invalid") or AC03 ("account closed") in the ISO 20022 rejection message. The sender gets the funds returned, minus any intermediary fees that were already charged, and the whole cycle starts over.
The painful part is the latency. A rejected cross-border wire typically takes 3–7 business days to bounce back, and the sender often does not learn why until they call their bank. That is a long time to wait for a fix that takes five seconds once you know what to look for.
The 5 most common IBAN validation errors
1. Incorrect MOD 97 check digits
This is the #1 cause of IBAN rejection by a wide margin. The two digits at positions 3–4 of every IBAN are a MOD 97-10 checksum computed from the rest of the string. If even one earlier digit is mistyped, the checksum no longer matches and the IBAN is structurally invalid.
Example: a valid German IBAN is DE89 3704 0044 0532 0130 00. Change the first 3 to a 2 and you get DE89 2704 0044 0532 0130 00 — it looks almost identical, but the check digits 89 no longer match the BBAN underneath, so MOD 97 returns a remainder other than 1 and the IBAN is rejected instantly.
The good news: MOD 97 failures are the easiest error to catch before sending, because you can compute the checksum locally in your browser. Our IBAN validator does exactly this for 50+ countries.
2. Wrong IBAN length
Every country fixes a specific IBAN length — Germany is 22 characters, France 27, Italy 27, the UK 22, Norway 15. An IBAN that is too short or too long is rejected regardless of whether the check digits happen to compute.
This usually happens for one of three reasons:
- A country's IBAN was pasted from a source that truncated the last few characters (common with PDFs that wrap long strings).
- A branch suffix or BBAN field was duplicated.
- The IBAN was copied by hand and a group was skipped.
Length errors are silent because the IBAN "looks like an IBAN" — there is just the wrong amount of it. The validator catches this by comparing the actual length to the registered length for the country code in the first two positions.
3. Invalid characters or unstripped formatting
ISO 13616 allows only A–Z and 0–9. Spaces are permitted in human-readable presentation but must be stripped before validation or transmission. The most common formatting errors:
- Spaces left in the string — many bank portals reject the raw
DE89 3704 …form even though it "looks" valid. - Lowercase letters —
de893704…is technically the same IBAN, but some legacy validators are case-sensitive and reject it. - Hyphens, dashes, or dots — often introduced by spreadsheets or PDF copy-paste.
- Trailing whitespace or hidden non-breaking spaces — the single most frustrating cause, because the string looks clean.
The fix is trivial — uppercase the string and strip everything except A–Z0–9 before sending. But you would be surprised how many failed wires trace back to a copy-pasted non-breaking space.
4. Wrong or mismatched country code
The first two letters of an IBAN are an ISO 3166 country code, and the rest of the structure (length, BBAN layout) must match that country's spec. Two related failures live here:
- Unsupported country code. The IBAN starts with a country that the validator or receiving bank does not recognize as an IBAN country (e.g.
US, because the US does not use IBANs). The payment is rejected as "non-IBAN country." - Country-code / bank mismatch. The IBAN starts with, say,
FRbut the named recipient bank is in Germany. Some receiving banks flag this as suspicious and hold the payment for manual review, especially for larger amounts.
If you are sending to the United States, you do not need an IBAN at all — you need the recipient bank's SWIFT/BIC code plus their account number.
5. Confusing the IBAN with a SWIFT/BIC or account number
This is a "wrong field, wrong form" error rather than a single typo, but it accounts for a surprisingly large share of inbound support tickets. The symptoms:
- The "IBAN" field is filled with an 8- or 11-character BIC like
DEUTDEFF(that's a SWIFT code, not an IBAN). - The "IBAN" field is filled with a domestic account number that was never converted to IBAN format (common when sending to a Eurozone bank from outside the Eurozone).
- The SWIFT field holds the IBAN and vice versa.
The structural validation catches this fast — an IBAN must start with two letters followed by two digits, so a BIC like DEUTDEFF fails immediately. But the user often doesn't know which field they filled wrong, which is why a quick IBAN validation before submitting saves a phone call to the bank.
IBAN validation errors — troubleshooting table
Use this table to map the symptom you see to the underlying cause and the fix. The "frequency" column reflects the relative share of each error type reported by payment teams and indie banking tools.
| Symptom | Likely cause | Fix | Frequency |
|---|---|---|---|
| "Invalid check digits" / AC02 | MOD 97 mismatch — single typo in the BBAN | Re-request the IBAN from the recipient; re-type, don't copy | ~45–55% |
| "Invalid IBAN length" | Truncated or duplicated characters | Verify length against the country spec; re-paste from the source | ~15–20% |
| "Invalid character in IBAN" | Spaces, hyphens, lowercase, or hidden non-breaking spaces | Strip non-alphanumerics, uppercase, re-validate | ~12–18% |
| "Country not supported" / "non-IBAN country" | Country code is not an IBAN country (e.g. US) | Use SWIFT/BIC + account number instead | ~8–12% |
| "Field mismatch" / wrong-field error | SWIFT/BIC or domestic account number in the IBAN field | Move the value to the correct field; confirm with recipient | ~5–10% |
Frequency ranges are approximate, aggregated from public payment-failure reports and indie banking-tool support data. Actual shares vary by corridor and bank.
Case study 1: the one-digit typo that cost nine business days
Spanish IBAN, single transposed digit, €2,400 invoice
A UK consultancy invoices a Spanish client for €2,400. The client pastes the IBAN ES91 2100 0418 4502 0005 1332 from an old PDF. One digit in the BBAN was actually a 6 in the current account, not a 5 — a single-character transcription error.
What happened: the UK bank's payment engine ran MOD 97, the checksum failed, and the SEPA message was rejected with status AC02. The funds sat in a correspondent account for four business days before the return message reached the UK bank. The client then had to request the correct IBAN, re-type it, and resend.
The cost:
- 9 business days of total delay (4 days return + 1 day to get the right IBAN + 4 days for the second transfer to clear).
- ~€12 in correspondent-bank return fees that were not refunded.
- A late-payment clause triggered on the invoice, adding €48 in penalty interest.
The fix in hindsight: a 5-second IBAN validation before the first send would have flagged the MOD 97 failure instantly. The client could have fixed the typo and sent the same day.
Case study 2: the SEPA batch rejection that nobody noticed
Payroll run, 47 employees, one malformed IBAN rejects the whole file
A German startup runs monthly SEPA payroll for 47 employees. One employee recently switched banks and submitted a new IBAN with a non-breaking space in the middle — a common artifact of copying from a web form. The payroll file passed the company's internal spreadsheet check (which only counted characters) but failed the bank's strict ISO 13616 validation.
What happened: depending on the bank's file handling, either the entire batch is rejected or the single record is isolated and returned with a FF01 / "format error" reason. In this case the whole batch was returned, and 46 employees were paid a day late.
The cost:
- 1 day of payroll delay for the entire company.
- ~3 hours of finance-team time to diagnose, clean, and re-submit the file.
- Two employee complaints and one written HR follow-up.
The fix in hindsight: pre-validate every IBAN in the batch with a tool that strips whitespace and runs MOD 97 before submission. A bulk validator that removes non-breaking spaces would have caught the bad record before the file ever left the building.
Case study 3: the wrong-country-code silent failure
IBAN starts with "FR" but the bank is in Monaco
A US sender wires $5,000 to what they believe is a French supplier. The IBAN on the invoice starts with MC (Monaco), but the sender's accounts-payable team "corrects" it to FR because they assume Monaco uses French IBANs. Monaco does have its own ISO 3166 code and its own IBAN structure — both are 27 characters and look almost identical, but the check digits are computed against a different BBAN.
What happened: the MOD 97 check passed (because the sender also accidentally copied an FR IBAN from a different invoice), but the named recipient bank did not match the country code. The receiving bank flagged the mismatch and held the payment for manual compliance review rather than crediting it.
The cost:
- 5 business days of manual review before the bank asked for clarification.
- Another 3 days to re-verify and route correctly.
- A supplier relationship strained by an 8-day payment delay on a $5,000 invoice.
The fix in hindsight: never "correct" an IBAN's country code based on assumption. Validate the IBAN and confirm the country code matches the recipient bank's actual country. If the country code is unfamiliar, look it up — Monaco (MC), Andorra (AD), San Marino (SM), and Liechtenstein (LI) all have their own IBAN specs that are easy to mistake for a neighbor's.
The data: how often do IBANs actually fail
Hard numbers on IBAN rejection are surprisingly hard to find because banks do not publish per-error breakdowns, but several public sources give us a useful picture:
Two patterns stand out. First, IBAN validation errors are by far the most common preventable failure in cross-border payments — and unlike fraud or compliance holds, they are entirely fixable before the payment leaves your bank. Second, SEPA's enforced pre-validation is the model: by requiring IBAN format checks at the origin bank, EBA Clearing keeps SEPA rejection rates well under 1%, while non-SEPA cross-border wires fail several times more often.
The takeaway is simple: the corridors that validate IBANs before sending rarely reject. The ones that don't, reject often.
Where rejected IBANs hurt the most
Not every rejection costs the same. The damage scales with the type of payment:
| Payment type | Typical delay cost of one rejection | Why it hurts |
|---|---|---|
| Freelancer / contractor payout | Late fee + trust loss | Contractors depend on predictable cash flow; one late payment can trigger a clause |
| B2B supplier invoice | Shipment hold + late-payment penalty | Suppliers often hold the next shipment until payment clears |
| Payroll (SEPA batch) | Whole-company payroll delay | One bad record can return the entire batch |
| Tuition / education payment | Enrollment hold | Universities sometimes block registration until payment posts |
| Remittance to family | Hardship + repeat fees | Return fees fall on the sender, who can least afford them |
How to validate an IBAN before you send
The cheapest insurance against an IBAN validation error is a 5-second pre-send check. Here is the workflow that catches all five errors above:
- Strip and clean. Remove all spaces, hyphens, and non-breaking characters; uppercase everything.
- Validate structure. Confirm the first two characters are letters and the next two are digits.
- Check the country code. Make sure it is a supported IBAN country and matches the recipient bank's country.
- Verify the length. Compare the actual length to the registered length for that country.
- Run MOD 97. If the remainder is not 1, the IBAN is invalid — request it again rather than guessing.
You do not have to do any of this by hand. Our free IBAN validator runs all five checks in your browser for 50+ countries — no signup, no data uploaded — and shows you exactly which check failed so you know what to fix.
Validate your IBAN before you send
Checks format, length, country, and MOD 97 check digits for 50+ countries — 100% in your browser, no signup.
Open IBAN validator →When the IBAN is valid but the payment still fails
A valid IBAN only proves the format is correct. It does not confirm the account exists, is open, or belongs to the named recipient. A payment can still fail after passing IBAN validation for reasons like:
- Account closed or blocked — status
AC03. Only the receiving bank knows this; you cannot detect it client-side. - Name mismatch — some banks run beneficiary-name checks and hold payments where the name does not match the account.
- Sanctions or compliance review — independent of the IBAN, triggered by names or countries.
- Wrong currency or corridor — a valid IBAN does not mean the account accepts the currency you are sending.
For these, the only reliable check is a confirmation call to the recipient — and for large amounts, a small test transfer first.
Save on the transfers that do go through
Once your IBAN validates, the next decision is how you actually send the money. Traditional bank SWIFT wires stack an outbound fee ($25–$45), correspondent fees ($10–$30), and an FX markup of 2–4% — so a "successful" transfer can still quietly cost 4–6% of the amount. Services that route near the mid-market rate, like Wise, usually land closer to 0.5–1% all-in for the same corridors.
Affiliate disclosure: this is a referral link — using it may earn ibantool.com a small commission at no extra cost to you.
FAQ
- What are the most common IBAN validation errors?
- The five most common IBAN validation errors are: incorrect MOD 97 check digits, wrong IBAN length (extra or missing characters), invalid characters such as spaces or hyphens not stripped, wrong or mismatched country code, and confusing the IBAN with a SWIFT/BIC code or a domestic account number. The single most frequent cause is a MOD 97 check-digit failure, usually from a single transcription typo.
- Why is my IBAN being rejected even though it looks correct?
- An IBAN can look correct and still fail validation because the MOD 97 checksum does not match. A single mistyped digit changes the remainder and the IBAN is rejected. Other hidden causes include spaces that were not stripped, a lowercase country code, or a country code that does not match the country of the bank you are sending to.
- How often do IBAN transfers actually fail?
- Industry reports put cross-border payment first-attempt failure rates in the range of 2–5%, with the leading cause being invalid or malformed account identifiers such as IBANs. For SEPA credit transfers inside Europe the rejection rate is much lower — EBA Clearing reports figures well below 1% — because IBAN validation is enforced before the message enters the network.
- Does a valid IBAN guarantee my payment will go through?
- No. A valid IBAN only confirms the format and check digits are correct per ISO 13616. It does not confirm the account exists, is open, or belongs to the named recipient. Always confirm the full account details with the recipient before initiating a transfer.
- Can I check an IBAN before sending money?
- Yes. You can validate format, length, and MOD 97 check digits for 50+ countries with a free browser-side tool like ibantool.com/iban-validator. It runs entirely in your browser and catches the five most common validation errors before you submit a payment.
Bottom line
The five IBAN validation errors — MOD 97 check digits, length, invalid characters, wrong country code, and field confusion — cause the overwhelming majority of preventable cross-border rejections. They are also all catchable in five seconds before you hit send. Validate the IBAN, confirm the country code matches the recipient bank, and you will eliminate most of the 3–7-day return cycles that make international payments so painful.
Ready to check one now? Run your IBAN through the free IBAN validator, and if you are sending outside an IBAN country, look up the recipient bank's SWIFT/BIC code first. Both tools run 100% in your browser — no signup, no data uploaded.