A payee checker is the name check that runs before a payment leaves: your payment service provider (PSP) asks the PSP that holds the payee's account whether the name you entered matches the account holder. In the EU the check is called Verification of Payee (VoP), it runs on the SEPA scheme, and it returns one of four answers in well under a second. If you pay companies, the answer you will see most often is not match - it is close match.
That surprises people. It should not. A close match on a company is usually a naming difference, not a fraud signal, and the check is designed to surface exactly that difference so you can confirm it once and move on.
What a payee checker actually compares
It compares two strings: the name you submitted, and the name the payee's bank holds on the account. For an individual those two are usually close - a first name, a surname, maybe a middle name. For a company they are frequently written in different ways by different people at different times: the invoice, your ERP supplier record, the company register and the bank account opening form can all disagree.
The account holder is the reference
The check does not tell you what the company calls itself. It tells you what the bank holds on the account. That is the name that has to line up, and it is often the registered legal name rather than the name on the invoice.
The five reasons a company returns close match
- Trading name versus registered name - the invoice says the brand, the account says the legal entity.
- Legal form and suffix - Ltd, Limited, GmbH, S.r.l., S.p.A., B.V., AB: present on one side, missing on the other.
- Abbreviations and punctuation - '&' versus 'and', hyphens, full stops after initials, double spaces.
- Group and parent naming - the invoice carries the group brand, the account is held by a local subsidiary.
- Accents and transliteration - a name written with diacritics in one system and without them in another.
None of these is a red flag on its own. What matters is that the check shows you the difference instead of hiding it, and that you have a way to confirm the correct form.
What to do with the verified name
On a close match, a good payee checking service returns the verified name - the form held on the account - so you can confirm or correct rather than guess. That single field is the most useful part of the response, and it is worth building a habit around it.
- 1 Read the verified name and compare it with the invoice and your supplier record.
- 2 If it is the same company, accept it and store the verified form against the supplier.
- 3 If it is a different entity, stop and confirm with the supplier through a channel you already trusted - not a phone number from the email that changed the details.
- 4 Next time you pay that supplier, send the stored verified name so the check returns match cleanly.
Make the check precise with an organisation identifier
For legal persons, the scheme allows the check to use an organisation identifier - a VAT number or an LEI, for example - alongside the name. An identifier is unambiguous, so it removes most of the name-variant problem at the source. If your supplier master data holds a VAT number, send it with the name; if it does not, that is a data-quality project worth doing anyway.
Two practical notes. First, sole traders and freelancers sit between the two worlds: the account may be held in a personal name while the invoice carries a trading name, which produces close matches that look alarming and are not. Second, a company that has genuinely changed its registered name will return close match until your record catches up - the verified name tells you which case you are in.
A short checklist for supplier payments
- Send the most official name you hold, not the brand name from the invoice.
- Include the organisation identifier where you have one.
- Treat close match as a prompt to confirm, not a reason to abandon the payment.
- Store the verified name and reuse it, so repeat payments match cleanly.
- Re-verify when a supplier's bank details change, rather than re-checking every saved payee on every run.
For a business, this is not a scheme project. You do not join the SEPA VoP scheme; you call a service that is already connected to it and wire the result into the point where payments are approved - a single payee in a dashboard, or a whole payment file before release. For a bank or PSP the same logic applies inside the payment flow, with the extra work of answering requests about your own account holders.
RoxPay delivers scheme-compliant Verification of Payee through one REST API and a dashboard, returning the standardised outcomes - match, close match, no match and not available - in well under a second, with the verified name on a close match and the responding bank's BIC, for a single payment or a whole payment file.