Checking an IBAN by name: why banks no longer do it automatically, and how to handle it yourself

Since 2024, Dutch banks no longer automatically verify the account holder's name against an IBAN for every payment. For business finance teams, that's a real risk — here's how to tackle it practically.

Until a few years ago, your bank automatically checked whether the name you entered matched the IBAN on every transfer. Since the introduction of SEPA Instant and the wider rollout of real-time payments, that check has disappeared in many scenarios. For consumers the inconvenience is usually minor; for business finance teams it's a serious risk — particularly with direct debit batches, bulk creditor file updates, and invoice fraud.

What changed?

The European payment standard SEPA Instant requires banks to process transfers within 10 seconds. A full name-IBAN match — which historically worked well for Dutch accounts because the bank has access to the counterparty's records — no longer fits within that time window for every scenario. From 2024, a European alternative is therefore mandatory: Verification of Payee (VoP). VoP does perform a match, but returns a less detailed result ("close match" vs "exact match" vs "no match"), and the level of detail varies by bank.

Why is this a problem for SMB finance teams?

• Creditor updates — a supplier emails a new account number; your administration updates it without further checks; the next invoice payment goes straight to a fraudster. Commonly known as "CEO fraud" or "invoice spoofing".
• Bulk uploads in accounting packages — when importing 100 new debtors, the check is usually only syntactic (is the IBAN format correct?), not whether the name actually matches.
• Payroll batches and one-off payments — a typo in an IBAN can send a payment to an unintended account. Recovery is possible but time-consuming (the account holder must cooperate).

What can you do yourself?

The Dutch Tax Authority, the Chamber of Commerce, and the banks themselves all recommend three layers:

1. Syntactic validation — check whether the IBAN conforms to the correct format (length, check digits). This catches typos only, not fraud.
2. Name-IBAN match (heuristic) — for Dutch IBANs, there are public services and commercial tools that return a match score based on past payments and Chamber of Commerce data. Not 100% conclusive, but it does raise a flag.
3. Verification of Payee at the point of transfer — if your bank supports it, use it. When in doubt, call the supplier on a number you already have on file (not one from the suspicious email).

Practical policy for an SMB finance team

Four agreements that make the difference:

• A change to a creditor's IBAN is never processed based on email alone — confirmation via a separate channel (phone, in person) is always required.
• On the first invoice from a new supplier, the IBAN is checked both visually and automatically for a name match.
• For direct debit batches: every batch file is validated for the syntactic correctness of all IBANs before submission.
• All checks are logged so that, in the event of an incident, you can demonstrate exactly which verification was carried out.

What our tool does

Our IBAN check performs syntactic validation plus a heuristic name-IBAN match for Dutch accounts. It's a tool — not a bank guarantee — but it prevents the most common errors in administration imports. For business use, you can upload a batch file and receive a match score with explanation for each row.

In practice, fraud is stopped by combining a tool with clear internal procedures. Either one on its own is not enough.