Verification of Payee for Finance Teams: How VoP Changes Supplier Payments

Verification of Payee (VoP) for finance teamsmeans every euro credit transfer your company sends is now name-checked against the beneficiary's bank records before execution. Since 9 October 2025, banks across the euro area run this check automatically and free of charge under the EU Instant Payments Regulation. For accounts payable, treasury, and payroll teams, VoP is both a powerful fraud control and a new operational workload: mismatched supplier names now generate warnings on payment runs that somebody has to triage. This guide covers what changes in practice and how to prepare your master data so VoP works for you instead of against you.

What Changes on Your Payment Runs Under VoP?

Before VoP, a batch of 500 supplier payments either passed format checks or bounced for technical reasons. Now each payment in that batch triggers a name verification, and the results come back in four flavours: match, close match, no match, and verification not possible. Your bank surfaces these results in the corporate banking portal or through your payment file interface. A clean run looks the same as before. A messy supplier master file produces dozens of close-match warnings per run, each one demanding a decision: proceed, investigate, or hold. Teams that did no preparation report payment runs taking hours longer because every warning interrupts straight-through processing.

Why Do Legitimate Suppliers Trigger Close-Match Warnings?

Because the name in your ERP rarely equals the legal account holder name at the bank. The most common causes:

• Trading names vs legal names.Your vendor record says "Acme Consulting", the account belongs to "Acme Consulting Services GmbH".
• Missing or wrong legal suffixes. Ltd, GmbH, S.A., B.V., Sp. z o.o. omitted, abbreviated, or attached to the wrong entity in a group.
• Factoring and payment service intermediaries. The invoice says one company, the account legally belongs to a factoring provider or a payment processor.
• Personal accounts for sole traders.The business name on the invoice, the founder's personal name on the account.
• Encoding and diacritics. Müller stored as Muller, Turkish or Polish characters stripped by a legacy ERP field.

None of these are fraud, but each one consumes triage time. The fix is a one-off cleanup: ask suppliers to confirm the exact account holder name during onboarding, store it in a dedicated field, and use that field in payment files.

How Should a Finance Team Respond to a No-Match Result?

A no match on a supplier payment is the highest-value fraud signal your bank will ever hand you, because it usually means the account exists but belongs to someone else entirely. The correct response is a fixed, written procedure: halt the payment, contact the supplier through a phone number from your master data or their official website, never through the email thread or the invoice that delivered the IBAN, and document the resolution before the payment is released or the record corrected. The majority of successful invoice fraud involves bank detail changes requested by email; a no-match result combined with an out-of-band callback defeats nearly all of it.

What Should You Fix in Your Master Data Before VoP Fixes You?

Three data-quality controls eliminate most VoP friction, and all three can run before payment day:

• Validate IBAN structure at entry. A mistyped IBAN fails MOD-97 long before it fails VoP. Checking at onboarding, with the IBAN checker for single entries or the bulk IBAN checker for a full vendor file, removes the purely technical failures from your payment runs and identifies the receiving bank.
• Capture the exact account holder name. Add it to your supplier onboarding form as a separate field with a note that it must match the bank account, not the trading name.
• Re-verify on every change. Any request to change an IBAN or account holder name is re-validated and confirmed by callback, no exceptions. Automating the structural part through the validation API keeps this control cheap enough to apply universally.

Does VoP Apply to Your Company Directly?

The legal obligation sits on payment service providers, not on corporates. You do not have to build anything, your bank performs the check. But the regulation explicitly allows corporate payers sending bulk files to opt out of VoP per batch in some implementations, and that choice deserves attention: opting out restores processing speed and silence, and with them the entire category of fraud VoP exists to stop. For most businesses the right configuration is VoP on, master data cleaned, and a triage procedure that makes warnings cheap to handle. For the full regulatory background, see what Verification of Payee is and how it works and our guide to PSD2 payee verification.

Sources & References

• Regulation (EU) 2024/886 — Instant Payments Regulation, VoP obligations and timeline
• European Payments Council — Verification of Payee scheme rulebook and participant guidance
• FATF Recommendations — Wire transfer originator and beneficiary information standards
• European Central Bank — Instant payments adoption and infrastructure

Last updated: June 2026