Verification of Payee checks that the payee name matches the account holder before a transfer is sent. For supplier payment runs, every new or changed bank detail gets a name check, so teams need clean vendor data, a rule for close and no-match results, and time built into each run.
Key takeaways
- Verification of Payee adds a name check before a credit transfer is sent, so a mismatched supplier payment can be stopped or reviewed before funds move.
- Every new or changed supplier bank detail is a potential exception, which makes vendor master data quality the main driver of manual work.
- A close match or no-match result is a decision point for the payer, and it should never be bypassed silently in a batch.
- Payment runs need a named exception queue, an owner and a cut-off time so that flagged payments still meet their due dates.
What is Verification of Payee?
Verification of Payee is a name check that the payer's bank runs before it sends a euro credit transfer. The payer enters a beneficiary name and an IBAN, the bank compares that name with the account holder recorded by the payee's bank, and the payer receives one of three results: a match, a close match, or no match.
The obligation comes from EU law rather than from a single bank or payment scheme. Regulation (EU) 2024/886, known as the Instant Payments Regulation, amends Regulation (EU) No 260/2012 (the SEPA Regulation) and sets duties for payment service providers in the euro area, including the verification duty for regular credit transfers, which applies from 9 October 2025 under the text. Read the regulation itself for scope, exemptions and timing: Regulation (EU) 2024/886 on EUR-Lex.
This article is general information and not legal or tax advice. Rui Codex provides technical implementation support for the systems that carry these checks, and does not give legal or compliance advice.
The check runs per payment instruction, not per file. A batch of supplier invoices therefore becomes a set of individual name results, and the data in your payment file must be accurate enough to be verified one payee at a time. A business payer that submits several payment orders as a package can opt out of the check: Article 5c(6) of Regulation (EU) No 260/2012, inserted by Regulation (EU) 2024/886, requires payment service providers to offer payment service users that are not consumers that option.
Does Verification of Payee change supplier payment runs?
Yes. The check turns a payment run from a purely technical file transfer into a workflow with a review step, because some payments will not return a clean match and must be handled before release.
Three things change in practice. First, the name in your payment file becomes a control point: a supplier invoiced under a trading name but holding its account under its legal form can produce a close match. Second, timing becomes less predictable, since a run that used to release in one step now has an exception stage. Third, responsibility shifts, because the payer must decide how to treat each non-match and that decision needs a named owner.
The benefit is fewer misdirected payments and a clearer audit trail. The cost is manual review of exceptions, which grows with the number of supplier bank changes and name inconsistencies rather than with the number of invoices.
How does the name check work inside a payment run?
The check runs when the payment instruction is submitted, before authorisation, and it returns one result for each payee. The sequence below applies in general terms, although the details depend on your bank and channel.
- Your ERP or payment tool produces the payment file with the beneficiary name, IBAN and payment reference.
- The file is submitted through the bank channel, and the bank runs the verification before the instruction is authorised.
- A match lets the payment continue. A close match gives the payer a suggested name to accept or correct. A no match requires the payer to decide whether to proceed.
- Your system records the result against the payment ID, so the audit trail shows who approved any exception.
The exact response depends on the bank, the channel and the file format. Some channels return results per instruction, while others require a separate status query, so confirm with your bank how results come back for bulk files. Design the process around the slowest or least convenient channel, not the most convenient one.
When does a supplier payment fail the name check?
A payment is flagged when the beneficiary name you send does not match the account holder closely enough. This usually comes from the data you hold, not from the bank, so the cause is often inside your own vendor records.
- The legal form and the trading name differ, for example a company name without its legal suffix.
- Abbreviations, punctuation, spacing or diacritics differ between your record and the bank's record.
- The supplier changed its bank details by email or on an invoice without an update to the master record.
- The account belongs to a different entity in the same group or to a factoring partner.
- A manual entry introduced a typing error in the name or the IBAN.
Each cause fails differently. Normalising names consistently fixes the formatting cases, but it cannot fix a different legal entity, and it can wrongly merge two suppliers with similar names. Strict pre-checking catches more problems but creates more holds, while lenient matching in your own system reduces holds and hides the cases the bank will flag. A workable position is to normalise names the same way every time, then treat any remaining close match as a review item rather than an automatic accept.
What should be fixed in vendor master data first?
Fix the supplier record before the next run: the legal name, the IBAN, a verified change history and one owner for bank changes. Without these, every run creates avoidable exceptions.
- Store the legal name exactly as the supplier's bank holds it, and keep the trading name in a separate field.
- Require a written bank change request and verify it by calling a number already on file, not one given in the request.
- Lock bank fields to a controlled workflow so that invoices and emails cannot change them directly.
- Record the verification result and the reviewer on every payment that was held.
- Review dormant suppliers before each run, since stale records generate most avoidable no-match results.
Hypothetical examples of a supplier payment run
Here are two hypothetical scenarios:
Scenario one: a changed bank account
Prefer a delivered project to a scenario? Read the case study: EveryTranslate, an AI-powered translation platform.
A supplier emails a new IBAN with a request to update its details. The team changes the record without a call-back, the next run includes the new account, and the stored name differs from the account holder by a legal suffix. The result is a close match. Because the change was never verified, the right response is to hold the payment and confirm the details through a known contact, not to accept the suggested name.
Scenario two: a no-match on a former trading name
A payee record still uses a trading name the supplier stopped using after a restructuring. The payment returns no match and appears in the exception queue with its owner. The team checks the supplier's current registration, corrects the master record, and releases the payment before its due date. The record change is logged so the next run does not repeat the problem.
Where does the check fit in ERP and bank integrations?
The check belongs in the step where payment files are created, and the results should be written back to the payment record. In most setups, the ERP produces the file and the bank channel returns the result, so the integration must carry names and IBANs unchanged, read the outcome, and hold the payment in an exception state.
Rui Codex offers ERP and CRM integration and system integration work for businesses in Belgium, the Netherlands and Luxembourg, and this kind of data flow falls within that scope. If exception handling needs routing rules, notifications or approval steps, the AI automation service page describes the workflow work involved. Delivered projects are described on the case studies page.
Frequently Asked Questions
Is Verification of Payee required for supplier payments?
Yes, for euro credit transfers sent by payment service providers in the euro area, under the timetable in Regulation (EU) 2024/886. The duty sits with the payer's bank before the payment is sent, so supplier payments in euro from euro-area accounts are covered. Check the regulation text for scope, exemptions and the dates that apply to other member states, and ask your bank how it implements the check.
What does a close match mean for a supplier payment?
A close match means the name is similar to the account holder but not identical, so the payer should confirm the correct legal name before releasing the payment. Do not accept the suggested name without checking it against the supplier's registration or a verified document on file. If the difference is only a legal suffix or punctuation, record the reason and proceed. If it suggests a different entity, hold the payment and verify through a known contact.
Does a no-match result always block a payment?
No, a no-match does not block a payment automatically, but it places the decision with the payer. Your own policy should define who can approve a payment with no match and what evidence they need, because the bank's warning is not a reason to proceed on its own. In practice, most no-match payments should wait until the bank details have been verified.
Do we need to change our ERP to handle the check?
Not always, but the payment file and the exception process usually need changes. The ERP must send names and IBANs without altering them and must store the result against each payment. If the current software cannot hold an exception state, the work tends to move into spreadsheets, which is where errors usually appear.
Conclusion
Verification of Payee changes supplier payment runs by adding a name check to every instruction, which makes bank details and vendor data a control point. The practical work is clean master data, a defined response to close and no-match results, and an exception queue that keeps payments on schedule. Rui Codex provides technical implementation support for these integrations. You can request a project consultation at https://ruicodex.com/Contact or email info@ruicodex.com to discuss your project.
Sources
- Regulation (EU) 2024/886 on EUR-Lex - Publications Office of the European Union