Verification of Payee (VoP) is a check that runs before a credit transfer is authorized. It compares the name of the intended payee with the name registered to the account number you’ve entered, and tells you whether they match. If a fraudster has swapped a supplier’s IBAN for their own, or someone in your team has simply mistyped an account number, VoP flags the discrepancy before the money leaves your account.
That sounds simple, and it is. But since October 2025 it’s also a legal requirement for euro payments in the EU, and it changes how corporate payment runs work in practice. Here’s what finance and treasury teams need to know.
What the EU now requires in payment regulations
Under the EU’s Instant Payments Regulation, payment service providers in the euro area have been required to offer a Verification of Payee service since October 9, 2025. The requirement applies to both standard and instant SEPA credit transfers, and the service must be free of charge for the payer. Providers outside the euro area have until July 9, 2027 to comply.
The mechanics are standardized through a scheme run by the European Payments Council. When you initiate a payment, your bank sends the payee’s name and IBAN to the payee’s bank, which checks the details against its records and returns one of four responses within seconds:
- Match. The name and IBAN belong together. Proceed with confidence.
- Close match. The details largely align, often because of a spelling variation or a trading name. The verified name is returned so you can review it.
- No match. The name you entered doesn’t correspond to the account. A strong signal to stop and investigate.
- Verification not possible. The check couldn’t be completed, for example because the responding bank couldn’t process the request.
One detail matters more than it first appears: if you’re warned of a mismatch and choose to pay anyway, liability for a misdirected payment generally shifts to you. Corporate payers can waive the service for bulk payments, but doing so means accepting that risk consciously.
Does Verification of Payee prevent payment failures?
VoP prevents a specific and expensive category of failure: payments that technically succeed but go to the wrong recipient. A transfer sent to a mistyped IBAN doesn’t bounce back the way a misaddressed email does. Recovering it means contacting banks, filing recall requests, and often waiting weeks with no guarantee of success. VoP catches the error while it’s still free to fix.
What VoP does not do is guarantee your payment arrives. Failures caused by formatting errors, closed accounts, sanctions holds, or incorrect routing details happen after the verification step. So it’s most accurate to think of VoP as preventing misdirection rather than failure in general. Teams that want to reduce failure rates across the board still need clean vendor master data, correct payment formats, and monitoring of payment status through to settlement, which is where a dedicated payments automation platform earns its keep.
How Verification of Payee helps with fraud prevention
The fraud scenario VoP targets is invoice redirection, sometimes called authorized push payment fraud. An attacker impersonates a supplier, usually through a compromised or spoofed email account, and asks your AP team to update the supplier’s bank details. The next payment run sends real money to the attacker’s account. Because your team authorized the payment, banks have historically treated the loss as yours.
VoP interrupts this attack at the last possible moment. The attacker’s account is registered under a different name than your supplier’s, so the check returns a mismatch even when the email looked convincing and the invoice matched the purchase order. That final, automated, unforgeable comparison is something no amount of email vigilance can replicate.
It won’t catch everything. If fraudsters register an account under a name close to your supplier’s, a “close match” response still requires human judgment. And VoP does nothing about fraud that doesn’t involve changed bank details, such as fake invoices paid to a payee you’ve legitimately verified. Name matching is one control in a layered defense, not a replacement for supplier verification workflows, segregation of duties, and anomaly detection in your AP process. Our guide to evaluating AP and AR software covers how those controls fit together when you’re comparing platforms.
What Verification of Payee means for corporate payment operations
For consumers, VoP is a pop-up before a bank transfer. For a business sending thousands of payments per run, it raises practical questions.
Bulk payments produce bulk responses
A payment file with 5,000 lines may come back with dozens of close matches and a handful of no-matches. Someone has to review those exceptions before the run completes, and if your process is manual, VoP can slow payments down instead of protecting them. Payment automation that routes exceptions into a structured workflow keeps the control without the bottleneck.
Your vendor master data is now tested daily
Every legal-name variation, every trading name recorded instead of a registered name, every stale record surfaces as a close match. Companies with disciplined master data see clean match rates. Companies without it see noise, and noisy alerts get ignored. Cleaning supplier records ahead of time is the single most useful preparation.
Responses need to reach the right people
A no-match on a large payment is urgent. Your treasury and AP teams need to see verification results inside the systems they already work in, not in a separate banking portal. This is one reason more enterprises are moving payment execution out of individual bank portals and into a central layer that connects to their ERP, a shift we explored in our piece on tools that simplify enterprise finance.
How to prepare
If your organization pays suppliers in euros, VoP already applies to you through your banks. Three steps put you ahead of it:
- Audit your supplier master data. Compare recorded payee names against registered legal names. Fix the variations you find, and set an ownership process so records stay accurate.
- Decide your exception policy. Define in advance who reviews close matches, what evidence justifies proceeding, and when a no-match halts a payment run. Write it down before the first urgent Friday-afternoon payment forces an improvised decision.
- Centralize payment execution. If payments leave your organization through a patchwork of bank portals, verification results arrive in a patchwork too. A central payment platform gives you one view of every response, one exception workflow, and one audit trail.
Serrala’s payment solutions handle verification responses, sanctions screening, and format management inside SAP or as a managed cloud service, so the compliance layer runs where your payment runs do. If you’d like to see how that looks against your current setup, our team can walk you through it.
Regulation gave every business in the euro area a free fraud control. The companies that benefit most will be the ones whose data and workflows are ready to use it.
Frequently asked questions
Is Verification of Payee mandatory?
For euro payments, yes. Since October 9, 2025, payment service providers in the euro area must offer VoP for SEPA credit transfers at no cost to the payer. Providers in EU countries outside the euro area have until July 9, 2027. Corporate payers can waive the check for bulk payment files, but doing so means accepting liability for any misdirected payment the check would have caught.
What is the difference between Verification of Payee and Confirmation of Payee?
They are the same idea under two names. Confirmation of Payee (CoP) is the term used in the United Kingdom, where the scheme launched in 2020. Verification of Payee (VoP) is the term used for the EU scheme run by the European Payments Council. Both check that the account name matches the account number before a transfer is authorized. The main practical difference is scope: VoP is standardized across the euro area, while CoP is a UK domestic scheme.
What happens if the name and IBAN don’t match?
You receive a “no match” response with a recommendation not to proceed, or a “close match” response that returns the verified account name so you can review the difference. You can still choose to send the payment, but if you override a mismatch warning and the money goes astray, liability generally sits with you rather than your bank. For corporate payment runs, this makes a defined exception-review process essential.
Does Verification of Payee slow down bulk payments?
It can, if exceptions are handled manually. A large payment file may return multiple close matches and a few no-matches that someone has to review before the run completes. Routing those exceptions into a structured workflow, and keeping supplier master data clean so fewer exceptions arise, keeps the control without turning it into a bottleneck.
Does VoP work for international payments outside the EU?
The EU VoP scheme covers SEPA credit transfers in euros. Payments outside the SEPA zone are not covered by this regulation, though similar name-checking services exist in other markets. For cross-border payment security beyond name matching, sanctions screening and account validation remain separate controls.
