12 Common IBAN Errors That Cause Payment Rejection — and How to Fix Them
The most frequent IBAN errors in SEPA payments and e-invoices, with the exact rejection codes, root causes, and step-by-step fixes. Avoid costly returned payments and failed straight-through processing.
Why IBAN Errors Are Costly
An incorrect IBAN in a payment file means either immediate rejection by the bank's payment engine or — worse — successful routing to the wrong account. Both outcomes are costly: rejection fees, delayed payments, customer service overhead, and potential double-payment risk if the original payment is reprocessed without first confirming the erroneous one was not executed.
In e-invoicing, an incorrect IBAN in the payment instructions section of a UBL or Factur-X invoice disrupts automated straight-through processing (STP). The buyer's accounts payable system may reject the invoice for automated processing, requiring manual intervention. In an environment where e-invoicing mandates are pushing for full automation, IBAN errors are a growing source of operational inefficiency.
The 8 Most Common IBAN Errors
These errors account for the vast majority of IBAN-related payment rejections and processing failures:
Wrong country code
Using BE (Belgium) instead of NL (Netherlands), or FR instead of DE. This is often a copy-paste error from a template invoice. The country code must match the country where the bank account is held. Error detected immediately by mod-97 checksum failure.
Incorrect length
Each country has a fixed IBAN length. DE is always 22, FR is always 27, NL is always 18, BE is always 16. An IBAN of wrong length is immediately invalid. Often caused by missing or extra digit during manual entry.
Transposed digits
Swapping two adjacent digits (e.g., 12345 typed as 12354). This is the most common data entry error. The mod-97 checksum detects all transpositions of adjacent digits — a swapped pair will change the remainder from 1 to a different value.
Spaces not removed for electronic transmission
IBAN is displayed with spaces for human readability (DE89 3704 0044 0532 0130 00) but must be transmitted without spaces in SEPA XML and e-invoices (DE89370400440532013000). Spaces in XML fields cause schema validation failures.
Check digits replaced with zeros (template error)
Some ERP templates use placeholder IBANs like DE00XXXXXXXXXXXXXXXXXXX where the check digits are 00. These pass length validation but fail mod-97 checksum. Always calculate correct check digits when creating or testing IBAN templates.
Account closed or bank account number changed
The IBAN format is valid but the account no longer exists. This causes return code AC04 (Closed Account) after the payment reaches the debtor's bank. Regular supplier IBAN database updates are required to prevent AC04 returns.
Non-SEPA IBAN in a SEPA payment file
Some countries have IBAN-like formats (e.g., Lebanon LB, Qatar QA) but are not in the SEPA zone. SEPA payment files only accept IBANs from the 36 SEPA member countries. Including a non-SEPA IBAN causes scheme validation failure.
Missing or wrong BIC paired with IBAN
Since 2016, BIC is not required for intra-SEPA transactions (it is derived from the IBAN). However, some bank systems still validate the BIC/IBAN consistency. A mismatched BIC (correct IBAN but wrong bank's BIC) can cause routing failures in some older banking systems.
How to Prevent IBAN Errors in Your Processes
Prevention is far cheaper than remediation. Key prevention measures: (1) always validate IBANs at point of entry in your ERP or invoicing system — implement real-time IBAN validation in your supplier/customer master data forms; (2) never manually transcribe IBANs — use copy-paste or bank letter upload; (3) implement a bank account confirmation process for new suppliers (call the supplier to confirm the IBAN); (4) regularly clean your supplier master data by checking for closed accounts.
For developers building payment processing systems, implement IBAN validation as a service: check country code recognition, length validation against the country's expected length, character set validation, and mod-97 checksum as four independent validation steps. Return specific error codes for each failure type so the end user knows exactly what to fix.
Validate IBANs Instantly with ValidateFin
ValidateFin validates any IBAN against all 36 SEPA country formats and the mod-97 checksum instantly in your browser. Catch errors before they reach your bank.
Validate IBAN nowFrequently Asked Questions
What is the most common IBAN error in SEPA payments?
Transposed digits are statistically the most common manual entry error. However, wrong country code errors are the most costly — they can route payment to a valid account in the wrong country. Always validate IBANs with a mod-97 checksum tool before including them in payment files.
What bank return code do I get for a wrong IBAN?
AC01 (Incorrect Account Number) is returned when the IBAN format is invalid or the account does not exist at the target bank. AC04 (Closed Account) when the IBAN was once valid but the account has been closed. AM05 (Duplication) when the same transaction is submitted twice. The return code helps diagnose the specific cause.
How do I fix a payment rejected with AC01?
First, verify the IBAN using a validator (ValidateFin or your bank's tools). If the IBAN is structurally invalid (wrong checksum, wrong length), it is a data entry error — contact the payee to confirm the correct IBAN. If the IBAN is structurally valid but the account does not exist, the payee may have changed banks — request an updated IBAN.
Can I recover a payment sent to the wrong IBAN?
If the IBAN belongs to the wrong person (typo that happened to be a valid IBAN), the payer can file a recall request with their bank. Under SEPA rulebooks, the beneficiary bank must attempt to recover the funds. Recovery is not guaranteed — the unintended beneficiary must cooperate. This process can take weeks.
Why does my IBAN fail mod-97 but look correct?
A single digit error — even a transposition of adjacent digits — changes the mod-97 remainder from 1 to a different value. Common causes: a digit was misread (0 vs O, 1 vs I, 6 vs 8), a digit was omitted, or a digit was duplicated. Use ValidateFin to identify which position contains the error.
Are IBAN check digits always the 3rd and 4th characters?
Yes. The IBAN always starts with 2-letter country code followed by 2 check digits. The check digits are calculated from the BBAN and the country code using the mod-97 algorithm. They are always in positions 3-4 of the IBAN, regardless of country.
What is return code MD01 in SEPA Direct Debit?
MD01 (No Mandate) is specific to SEPA Direct Debit (pain.008), not credit transfers. It means the debtor bank has no mandate on file matching the MandateId and creditor identifier in the collection. Causes: mandate cancelled by debtor, incorrect MandateId in the pain.008, or the mandate was never registered at the debtor bank.
Can an IBAN have the correct format but be for the wrong bank?
Yes. The mod-97 checksum validates the IBAN's self-consistency (BBAN + country code), not whether the account actually exists. A structurally valid IBAN may belong to a different bank than intended, especially if manually retyped from a document. Bank verification services (IBAN name check, offered by some banks) can verify account ownership.
How do I validate IBANs in bulk?
ValidateFin validates individual IBANs instantly in the browser. For bulk validation within SEPA XML files (pain.001, pain.008), upload the file to the SEPA Validator — it checks every IBAN in the file against mod-97 and country format. For programmatic bulk validation, implement the IBAN validation algorithm in your ERP or data cleansing scripts.
Is IBAN validation enough to guarantee payment delivery?
No. IBAN validation confirms structural validity (format, checksum) but cannot confirm that the account exists, is active, or belongs to the intended payee. For high-value or first-time payments, supplement IBAN validation with bank account verification services (IBAN name check) offered by many European banks and payment service providers.