Skip to content
Articles

IBAN Validation Limitations: What a Valid IBAN Proves

IBAN validation limitations explained: a passing checksum proves the number is well formed, not that the account exists or who holds it. See what closes the gap.

By ApioskData quality8 min read

The main IBAN validation limitations are simple to state: a format and checksum check proves the number is well formed, and nothing else. It does not show that the account exists, that it is open, or who holds it. Use validation to catch typing errors early, and get payee evidence from your bank's verification of payee and your own change controls.

  • Use IBAN validation at the point of entry, to reject mistyped or truncated numbers before they reach an invoice or a payment run.
  • Do not read "valid" as "verified". A fraudster's IBAN is exactly as valid as the supplier's.
  • Account-holder evidence comes from the payment system, not from the number. In the EU that is verification of payee, in the UK Confirmation of Payee.
  • A payee-name match still does not prove the bank details came from the real supplier. That is a process question.
  • Store the format result, the payee result and the origin of the details as separate dated observations.

What IBAN validation actually computes

Validation is arithmetic on the number itself. No bank is contacted, which is why it is fast and also why it is limited.

EU law defines an IBAN as an international payment account number identifier that unambiguously identifies an individual payment account, with its elements specified by ISO, in Article 2(15) of Regulation (EU) No 260/2012. The European Banking Authority's report on virtual IBANs summarises the ISO 13616-1 structure: a two-letter country code, two check digits, and up to 30 alphanumeric characters for the national account number, the BBAN. The SWIFT IBAN Registry, published by the registration authority for the standard, lists the format each country uses and states that the check digits are calculated with the ISO/IEC 7064 MOD 97-10 scheme.

A standard validation therefore runs these steps:

  • Country: the first two letters are a country code that uses IBANs.
  • Length and layout: the number has the length that country registered. The Bundesbank, for example, states that a German IBAN has 22 characters, made up of the country code, the check digits, an eight-digit bank sort code and a ten-digit account number.
  • Checksum: move the first four characters to the end, replace letters with numbers (A is 10, Z is 35), and divide by 97. The remainder must be 1.
  • Optional: look up the bank identifier inside the BBAN in a bank directory, where one is available.

The result is one of a small set of states: unknown country, wrong length, checksum failure, or well formed. Each is deterministic. The same input always gives the same answer.

What a valid IBAN does not establish

A passing check tells you the string could be an IBAN. Four things remain open.

  • Existence. The checksum is computed from the digits, so a number can pass without any account behind it.
  • Status. An account that was closed last month keeps a valid number.
  • Holder. The IBAN carries no name. Nothing in the number links it to a company, a registration number or a VAT number.
  • Intent. A valid IBAN that belongs to someone else passes. The check is designed to catch mistakes, not substitutions.

Two further edge cases matter for supplier checks.

The country code is not proof of where the money ends up. The EBA report describes virtual IBANs as having the same format as standard ones, which makes them indistinguishable to third parties, while payments are credited to a separate master account with its own IBAN. The report notes that a payer's payment service provider would not be able to tell that the identifier is a virtual IBAN and would not know the master account. A rule such as "the supplier is Dutch, so the IBAN must start with NL" produces both false alarms and false comfort.

Do not build IBANs from national account numbers yourself. The Bundesbank page explains that some payment service providers apply institution-specific rules when converting account numbers and sort codes to IBANs, and must disclose the method they use. A home-made conversion can produce a number that passes the checksum and is still not the account's IBAN. Ask the supplier for the IBAN as issued by their bank.

A fictional example. An accounts payable clerk receives an email that appears to come from Harrowgate Tooling GmbH, a made-up supplier, with new bank details. The new IBAN passes validation. It would: the fraudster copied it from their own banking app. The validation result was correct and irrelevant to the question that mattered, which was who sent the email.

Where account-holder evidence comes from

Evidence about the holder comes from the payee's bank, through the payment system. A validation service cannot produce it from the number.

In the EU, Regulation (EU) 2024/886 added Article 5c to Regulation 260/2012. The payer's payment service provider must verify the payee immediately after the payer provides the payee's details and before the payer is offered the option to authorise the credit transfer. The ECB's summary describes a service that informs payers of discrepancies between the account identifier and the payee name, with results of match, close match, no match or other, free of charge to the payer. Providers in euro area member states had to comply by 9 October 2025. Providers in other member states have until 9 July 2027.

Three details in Article 5c are easy to miss:

  • For a payee that is a legal person, the check can use another identifier, such as a fiscal number or an LEI, when the payer's channel accepts it and the payee's provider holds that data element.
  • The check does not block the payment. The payer is warned and can still authorise.
  • Payers that are not consumers can opt out when they submit multiple payment orders as a package. If your payment runs go out as batch files, find out whether your organisation opted out. If it did, the name check you assume is happening may not be.

In the UK, Pay.UK describes Confirmation of Payee as an account name-checking service designed to help reduce misdirected payments. Its FAQ lists four responses (match, close match, no match and unavailable) and says the service does not automatically guarantee that a fraudulent payment will be detected.

That caveat points at the remaining gap. A payee check compares the name you typed with the account. If the name and the IBAN both came from the same forged email, they can match each other perfectly. So the last piece of evidence is procedural: where the bank details came from, and whether a change was confirmed through a contact you already held. Our supplier onboarding evidence checklist covers how that sits beside the register and screening evidence.

What to store for a supplier bank detail

Keep three observations apart: the number is well formed, the bank reported a name result, and a person confirmed the origin. Collapsing them into one "bank details verified" flag hides which one is missing.

A field-by-field checklist:

  • iban: stored as text, without spaces, exactly as supplied.
  • format_result: well formed, wrong length, checksum failure or unknown country.
  • format_checked_at: when validation ran.
  • bank_identifier: the bank code read from the BBAN, with the directory used, if any.
  • payee_check_result: match, close match, no match, other, or not performed.
  • payee_check_name: the name that was submitted for comparison.
  • payee_check_at and payee_check_channel: when, and through which bank or provider.
  • details_source: how the details arrived, for example a signed form, a portal or an email.
  • change_confirmed_by: who confirmed a change, and through which independent contact.
  • linked_entity: the registration number of the legal entity the account is supposed to belong to.

These field names are a conceptual example for your own schema. They are not an Apiosk response format.

For an AI agent that fills payment forms, the same split gives clear rules. Run format validation before anything else, since it costs nothing and fails fast. Treat a format failure as final for that input and never retry it; ask for the number again. Treat "not performed" as its own state, never as a pass. And do not let the agent write "verified" on the strength of a checksum.

When IBAN validation is the wrong tool

Validation answers a narrow question, and several common ones fall outside it:

  • Confirming that a supplier owns an account. Use the payee check in your banking channel and your change procedure.
  • Detecting a fraudulent change of bank details. The new number will be valid.
  • Deciding where an account is held. The country code does not settle it for virtual IBANs.
  • Countries that do not use IBANs. A missing IBAN is then expected, and the check does not apply.
  • Establishing that the company exists. That is a register question, covered by company verification.

Where Apiosk fits

Apiosk's identifier validation check takes a VAT number, an IBAN or a company number and reports whether it is valid, with the country and format it belongs to. The sources page lists the IBAN check among the connected sources. For an IBAN, read the result as the format evidence described above and keep the payee check with your bank as a separate step.

To validate an identifier before it reaches a payment run, start from the identifier validation page.

This article was prepared with AI assistance using the linked EUR-Lex, ECB, EBA, SWIFT, Bundesbank and Pay.UK sources and the current Apiosk product pages. It is not legal advice.

Frequently asked questions

Does a valid IBAN mean the bank account exists?

No. Validation checks the country code, the length for that country and the check digits, all of which can be computed without contacting a bank. A number can pass every one of those tests and still point to an account that was never opened or has been closed.

Can IBAN validation tell me who holds the account?

No. The IBAN contains a country code, check digits and a national account number, and no holder name. Evidence about the holder comes from the payment system, through verification of payee in the EU or Confirmation of Payee in the UK, and from your own process for confirming where the bank details came from.

Is verification of payee enough to stop invoice fraud?

Not on its own. The service compares the payee name the payer entered with the account, so if a fraudster supplies both a name and an IBAN that belong together, the result can be a match. Pay.UK says of its own service that it does not automatically guarantee that a fraudulent payment will be detected.

Should an AI agent retry a failed IBAN validation?

No. A checksum or length failure is deterministic, so the same input fails again. Return the failure reason and ask the person or the supplier for the number again. Retries belong to lookups that depend on an external service being available.