Everybody Talks About Bank Account Verification, But…

Charles Dudley Warner famously quipped, “Everybody talks about the weather, but nobody does anything about it.” The line’s humor and construction have made it endlessly adaptable. “Everybody talks about exercise, but…” “Everybody talks about Congress, but…” What about bank account verification?
Ask any accounts payable leader whether validating vendor bank details matters, and you’ll get an emphatic yes. Ask them how consistently it happens — for every new vendor, every account change, every time — and the answer gets quieter. Not because they don’t understand the risk. Because manual bank account verification is slow, tedious and easy to shortcut when the invoice is due and the queue is backed up.
That gap between what everybody agrees should happen and what actually happens, every single time, is where fraud lives.
The Manual BAV Problem Isn’t a Knowledge Problem
Most AP and vendor master teams already know the mechanics of bank account validation: confirm the account is open, confirm it belongs to the entity you think it belongs to, confirm the routing number is valid, and do it again any time the banking details change. None of that is a secret.
The problem is throughput. A manual verification workflow typically involves some combination of:
- A phone call to the vendor at a number pulled from the invoice or email — which is exactly the channel a bank account change scam will have already compromised
- A callback to a number sourced independently, which takes time to track down and confirm
- Reviewing a voided check or bank letter, neither of which actually proves account ownership or status
- Manual cross-referencing against whatever fragmented data the organization has on file
Each of these steps takes minutes to hours per vendor. Multiplied across a vendor master with hundreds or thousands of active records — and every bank change request that arrives outside the routine onboarding flow — the arithmetic doesn’t work. Something gives. Usually it’s thoroughness: verification gets applied inconsistently, reserved for large payments, or skipped entirely when a request looks “routine.”
That inconsistency is precisely what a well-crafted vendor impersonation or fraudulent bank change request is designed to exploit. Fraud doesn’t need every transaction to slip through controls — it needs one.
What “Automated” Actually Buys You
Automated bank account verification isn’t a different control in kind — it’s the same control, applied without the fatigue, the de-prioritization and the human tendency to trust a familiar-looking email under deadline pressure. Done well, it typically checks:
- Account status — open, closed, or restricted, verified against the account-holding institution rather than a document the vendor supplied
- Ownership match — confirming the name on the account corresponds to the vendor or payee of record, not just a plausible-sounding entity
- Routing validity — confirming the routing number is active and correctly associated with the receiving institution
- Real-time or near-real-time response, rather than a verification that sits in a queue while payments continue to process against unverified details
The value isn’t just speed. It’s that automation makes the control unconditional. Every new vendor gets checked. Every bank change request gets checked, immediately, before it’s applied to the vendor master — not after the fact, once a payment has already gone out the door.
Where It Fits in the Payment Lifecycle
Automated BAV earns its keep at three points in particular:
- Vendor onboarding — validating banking details before a new vendor record is activated in the vendor master, catching errors and misrepresentations before they can ever be paid against.
- Bank account change requests — the highest-risk moment in the vendor lifecycle, and the one manual processes are most likely to shortcut under time pressure. Every change request should trigger verification, without exception, before the new details go live.
- Pre-payment screening for high-risk transactions — an added layer for large-dollar or first-time payments, even when the underlying vendor record was previously verified.
None of this replaces the need for a broader disbursement controls framework — segregation of duties, callback procedures using independently sourced contact information and staff trained to recognize social engineering. Automated BAV is a layer, not a substitute for the rest of the program. But it’s the layer that turns “we verify bank accounts” from a policy statement into something that’s true, every time, for every vendor.
So — What Are You Doing About It?
The honest answer for most organizations is: something, but not consistently and not for everything. That’s not a criticism — it’s a description of what happens when a necessary control is expensive to apply manually at scale.
Automation doesn’t make the question go away. It changes what “doing something about it” means — from a best effort applied when time allows, to a control that runs every time, whether anyone remembers to ask for it or not.


