Supplier master bank validation means confirming, before money moves, that the bank details stored for a vendor are real, open and actually belong to that vendor. Checking the format of a routing number is not enough. The control that stops redirected payments is matching the account to the supplier's name, at onboarding and again on every bank-detail change. For suppliers paid to an IBAN, we built Vopify to do that match in under two seconds from just a name and an IBAN.
TL;DR
- Validate every new supplier account and every bank-detail change before the first payment, and record the result in the master file.
- Format checks, prenotes and test payments show that an account exists, but a prenote does not check the name. Ownership is the gap to close.
- Confirm change requests through a contact you already hold, never through the channel the request arrived on.
- For suppliers paid by IBAN, a name-to-IBAN check returns a result in under two seconds, single or in bulk from a CSV.
- EU banks have had to offer payee verification on euro payments since 9 October 2025, so European suppliers' accounts are increasingly checked at the other end too.
Table of Contents
- What supplier master bank validation covers
- Why format checks are not enough
- What you need to collect for each payment rail
- The limits of prenotes, micro-deposits and test payments
- A step-by-step process for new suppliers
- Handling bank-detail changes
- Validate in bulk: cleaning an existing master file
- What changes when suppliers are in Europe
- What U.S. rules say about account validation
- Our perspective
- Pricing and getting started
- Common mistakes in supplier master validation
- FAQ
- Sources
What supplier master bank validation covers
Your supplier master is the table every payment run reads from. If a bank account in it is wrong, every future payment inherits the error. If it was changed by a fraudster, every future payment becomes a loss.
Validation in this context has three layers:
- Format validity. Does the routing number pass its check digit, and does the account number have a plausible structure?
- Account status. Is the account open and able to receive the payment type you plan to send?
- Ownership. Does the account belong to the legal entity on the invoice?
Nacha's account validation white paper describes validation as checking account information and whether an account can receive electronic payments. It says incorrect routing or account numbers can lead to returned ACH entries, fees, delayed supplier payments and fraud. It also recommends validating account ownership where possible, not just the account data. Most AP teams stop at layer one or two. Fraud lives in layer three.
Why format checks are not enough
The ABA routing number has a built-in check digit. The first eight digits are weighted 3, 7, 1 in repeating order, and the ninth digit must bring the weighted sum to a multiple of 10. That catches typos in a routing number. It says nothing about whether the account number exists, who holds it, or whether the supplier you know is the one who will be paid.
A fraudster who sends you new bank details will supply a routing number that passes every format test. The account is real. It just belongs to someone else. This is why validation that stops at the number itself does not protect a payment run.
What you need to collect for each payment rail
Before validating, collect the right data for the rail you will use. For domestic payments the details differ from cross-border ones.
| Rail | Core details to hold in the master file | Notes |
|---|---|---|
| ACH credit | Supplier legal name, routing number, account number, account type | Nacha's payment initiation checklist starts with verifying the receiver's account and routing numbers |
| Domestic wire | Beneficiary name, account number, nine-digit routing number, bank address | The OCC's consumer site lists the wire details required and says to confirm them before processing |
| International wire | Beneficiary name, BIC/SWIFT, and for many countries an IBAN | The U.S. does not use IBAN for domestic accounts |
Some banks use different routing numbers for ACH and for wires. Store the routing number against the rail, not against the supplier alone, so a wire number never ends up in an ACH batch by habit.
The limits of prenotes, micro-deposits and test payments
Most AP teams know three older techniques. Each has a role, and each has a limit.
Prenotes. A prenote is a zero-dollar ACH entry sent to test routing and account details. Nacha says it verifies an open account that can receive an ACH entry but does not check the name. So a prenote to a fraudster's account passes. It also takes time: commentary on the process puts it at up to three banking days.
Micro-deposits. Two small deposits show the recipient has access to the account, once they report the amounts back. That ties the account to a person who responds, but it needs the recipient's participation and several days of waiting. For a supplier in your onboarding queue, that is a delay on the very first invoice.
Test payments. Sending a small amount first works only if someone confirms receipt with the legitimate supplier, using a contact you already trust. Without that confirmation the test proves nothing about ownership.
The QuickBooks route is a good example of how these methods play out in practice. We compare the two-deposit approach with an instant name match in our walkthrough of QuickBooks vendor bank verification.
A name-matching check addresses the gap all three leave open. When you compare validation services, ask what the check actually confirms about the holder: some return only an open-or-closed status, others compare the name. For background on how identity-focused checks are evaluated more broadly, the guide on account opening fraud detection lays out how finance teams think about measuring such controls.

A step-by-step process for new suppliers
Here is a routine that works for most mid-size AP teams. Adjust the thresholds to your volume.
1. Collect details through a controlled channel
Ask the supplier to submit bank details through your onboarding form or portal, not by replying to an email thread. Collect the legal name exactly as it appears on the bank account, which is often different from the trading name on the invoice.
Where it goes wrong: details typed in from a PDF invoice. Invoices are the document a fraudster alters first.
2. Validate the format
Run the routing number check digit and confirm the account number length your bank expects. This is cheap and catches keying errors, the cause of most returned payments.
3. Validate ownership
Match the account holder name against the legal name on file. Nacha's guidance is that ownership validation, where possible, goes beyond account data. For a supplier paid to an IBAN, this is the step we built Vopify for: enter the name and the IBAN, and the match result comes back in under two seconds, for individuals and for businesses.
Where it goes wrong: treating a "close match" as a pass. A close match means the name is similar, not identical. Record it and look at the difference. A trading name versus a legal name is routine. A completely different company name is not.
4. Get independent approval
Require a second person, the checker, to approve the addition or change in the master file. The maker should not be able to release the payment as well. Citi's guidance on beneficiary change requests lists maker/checker approval among its recommended controls, along with staff training, fraud-detection software and regular control reviews.
5. Document the result
Store the validation result, date and approver against the supplier record. When an auditor or your bank asks why a payment went where it did, this record is your answer. Accounting Today's March 2026 guidance recommends documenting each verification result, making verification mandatory for every new vendor account and every bank-detail change, and re-verifying periodically.
For the full routine with examples, see our practical AP guide to validating vendor bank accounts.
Handling bank-detail changes
Changes are where most losses happen, because the supplier is already trusted and the invoice already expected. Treat any change as a new validation event.
- Hold the payment. Do not release anything to the new details until the steps below are complete.
- Call back on a known number. Citi recommends independently confirming the request with an established supplier contact, rather than trusting the channel that delivered it. Use the number in your master file, not the one in the request.
- Validate the new account against the supplier's legal name. Same ownership check as at onboarding.
- Get second-person approval before the master record is edited.
- Log it. Who asked, who confirmed, what the check returned.
We go deeper on this sequence in why AP must hold payment first on a vendor bank change, and on matching controls to scenarios in our seven AP payment verification checks.
Validate in bulk: cleaning an existing master file
New-supplier controls do nothing for the accounts already in your file. Master data accumulates years of edits, acquisitions and one-off exceptions. A periodic sweep is the standard answer, and it only works if checking is cheap enough to run across every supplier.
A practical order for a cleanup:
- Start with the highest spend. The top suppliers by annual payment volume carry the most exposure.
- Then recently changed records. Any account edited in the last 12 months is a candidate.
- Then dormant suppliers. Inactive vendors with live bank details are a favorite target for fraudulent reactivation.
- Finally, the long tail. Run the remainder in a single batch.
For suppliers paid by IBAN, Vopify accepts a CSV upload so you can check a whole list at once; see bulk IBAN verification. A risk-based approach, where the depth of checking scales with the amount and the type of change, is described in our guide on risk-based verification for AP teams.
What changes when suppliers are in Europe
If you pay suppliers in the euro area, the other end of the payment is changing in your favor. Under the EU Instant Payments Regulation, payment service providers must offer payers a verification-of-payee service that tells them of any discrepancy between the account identifier and the intended payee's name. The European Central Bank states that the verification of payee requirement applied to euro area member states from 9 October 2025, and applies to non-euro area member states from 9 July 2027. Payers receive a result of match, close match, no match or other before they send.
Two points matter to a U.S. company:
- It is an EU rule on EU payment providers. U.S. banks are not bound by it, and nothing in the U.S. system currently gives your ACH payments the same automatic name check. The Nacha guidance above is voluntary best practice for ownership validation, apart from the WEB debit rule described below.
- It sets the expectation. European suppliers and their banks are used to name checks. A U.S. payer who pays an IBAN without any name verification is the weak link in the chain.
Our work here is built around that model. Vopify checks live payment networks and covers SEPA (the Eurozone), India, Indonesia, South Korea and China (Alipay). The platform has processed over 10,000 verifications across 20 Eurozone countries. For how to handle the BIC and IBAN differences between U.S. and European records, see BIC vs SWIFT for AP teams.
What U.S. rules say about account validation
The U.S. position is a mix of rules and recommended practice, so it helps to separate them.
Nacha's WEB Debit Account Validation Rule, effective March 19, 2021, requires an originator's commercially reasonable fraudulent-transaction detection system for WEB debits to include account validation for the first use of an account number, or when it changes. At a minimum, validation means determining that the account is legitimate, open and able to accept ACH entries at the receiving bank. That rule is about consumer WEB debits, not supplier credits. But it shows where the industry has landed: first use and every change are the moments to validate.

For supplier payments, the standard you are held to is practical. If a supplier is defrauded through your payables process, your auditors and your bank will ask what you did to confirm the account before paying. A documented validation step answers that question. Our guide to five steps to prepayment Nacha account validation covers the U.S. workflow in detail, and bank account ownership verification methods compares what each method actually proves.
Our perspective
Every AP team we talk to has a validation step. Far fewer have a validation step that answers the one question fraud depends on: whose account is this?
We built Vopify around that question. You give us a name and an IBAN, and we match them against live payment networks and return a result in under two seconds. There is no contract to sign and no integration project before your first check, and it works for individuals and businesses alike.
Speed matters more than it sounds. A check that takes three days gets skipped when a supplier is chasing payment. A check that takes two seconds gets run every time, on every change, and that is what a control is: something that happens whether or not anyone is in a hurry.
Our view is that name-to-account matching belongs at the center of the supplier master process, not at the edge of it. Format checks and callbacks still do their jobs. The name match is the step that tells you the money will land with the supplier you meant to pay.
David
Pricing and getting started
Payee verification at Vopify is priced per check, with a one-off cost of $0.70 to $1.00 per verification. If you verify steadily, the subscription plans are Starter at $240 per month, Growth at $750 per month and Scale at $2,000 per month. Single lookups work well for a new supplier, and CSV upload suits a master file review. API integration is planned for teams that need programmatic, high-volume checks.
To see how it fits your process, start at Vopify, check one supplier's name and IBAN, and compare the result against what your current process would have told you.

The same checks are available to AI assistants through Vopify MCP, for teams that run parts of their AP workflow through an assistant.
Common mistakes in supplier master validation
- Validating only at onboarding. The master file changes after day one. Re-verify on change and periodically.
- Accepting the request channel as proof. An email that asks you to change bank details cannot confirm itself.
- Storing the trading name only. Without the legal name, a name match has nothing to compare against.
- Letting one person add, change and pay. Separate the roles.
- Skipping the record. An undocumented check cannot be shown to an auditor.
FAQ
What is supplier master bank validation?
It is the process of confirming that the bank details stored for each vendor are valid and belong to that vendor, both when the vendor is added and whenever the details change. It covers format, account status and, most importantly, account ownership. Nacha recommends validating ownership where possible.
Does a prenote prove the account belongs to my supplier?
No. Nacha says a prenote verifies that an account is open and can receive an ACH entry, but it does not check the name. Use a name-matching check or an independently confirmed callback to establish ownership.
How often should I re-validate supplier bank details?
Validate every new account and every change, and re-verify the whole file periodically. Accounting Today's March 2026 guidance recommends mandatory verification for each new account and change, plus periodic re-verification. How often you sweep the full file depends on your volume and risk, with the highest-spend suppliers first.
Can I validate IBANs for European suppliers?
Yes. Enter the supplier's legal name and IBAN, and Vopify returns a match result in under two seconds. It covers the Eurozone and supports single lookups or bulk CSV uploads. Our IBAN verification page explains what is supported.
Do U.S. domestic accounts use IBANs?
No. U.S. domestic accounts are identified by a routing number and account number, and the U.S. does not use IBAN domestically. International wires commonly need a BIC/SWIFT code and, for many destination countries, an IBAN.
Sources
- Nacha, Account Validation: A Tool for Businesses to Improve ACH
- Nacha, Supplementing Fraud Detection Standards for WEB Debits
- Nacha, A Checklist Approach to Payment Initiation
- Accounting Today, Stop payment fraud before it starts
- OCC HelpWithMyBank.gov, wire transfer information
- Citi, Beneficiary Change Request best practices
- European Central Bank, Instant Payments Regulation
