Vendor Payment Fraud via Bank Account Compromise: A Growing Crisis

The Threat Landscape
The numbers are jarring. Recent industry data shows that 79 percent of organizations experienced attempted or actual payment fraud in 2024, with business email compromise schemes ranking as the top attack vector, affecting 63 percent of targeted companies. Businesses are losing roughly five percent of annual revenue to fraud, translating to median losses of $120,000 per incident. And the 2026 AFP Payments Fraud and Control Survey confirms that conditions haven’t improved: 76 percent of U.S. organizations experienced attempted or actual payments fraud in the past year.
The Stories Behind the Statistics
The Cleveland Public Library: $400,000 Gone
The Cleveland Public Library case serves as a stark reminder of the necessity of having and following internal controls. State auditors revealed that the library transferred almost $400,000 to a fraudulent account as part of a payment redirect scam. The scheme succeeded because, as State Auditor Keith Faber noted, the library failed to adopt proper verification processes for vendor information changes.
The fraudsters’ approach was deceptively simple: they impersonated a legitimate vendor and requested an update to banking details. Without adequate verification protocols in place, library staff processed the change and subsequent payments flowed directly into the criminals’ accounts. While insurance ultimately covered $350,000 of the loss and the legitimate vendor forgave another $46,405, the incident exposed critical vulnerabilities that exist in countless organizations.
Tennessee City: Phishing at the Municipal Level
The La Vergne, Tennessee, city government recently warned residents and businesses about phishing emails claiming to be from the city and requesting payments — a reminder that these schemes target organizations of all sizes.
Vendor Impersonation at Credit Unions
Fraudsters are impersonating vendors and suppliers used by credit unions. The credit unions receive a spoofed email — appearing to come from the vendor — with updated banking information for paying invoices by ACH or wire. As legitimate invoices are received from the actual vendors, payments are remitted using the updated, fraudulent banking information, allowing the fraudsters to intercept them. The fraud is typically discovered only when the actual vendor contacts the credit union inquiring about a delinquent payment. Losses have reached the mid-to-high six-figure range.
The AFP’s Real-World Example
In one AFP survey respondent’s case, a fraudster infiltrated a vendor’s email account and began sending legitimate-looking messages requesting updated banking details. The documentation appeared valid and the request followed their processes, so the payment was initiated. Vendor email compromise (VEC) is a powerful variant on business email compromise.
Why These Schemes Work
Unlike other forms of cybercrime that exploit technical flaws, business email compromise targets people. “Bad actors aren’t going after systems — they’re going after individuals,” according to Roderick Brown, Senior Vice President of Wholesale Payments Fraud Control Solutions for Truist.
Traditional accounts payable workflows — built around email communication, PDF forms and manual callbacks — were never designed for this level of risk exposure. Remote onboarding, decentralized finance teams, global vendors and digital transformation initiatives have expanded the number of touchpoints where fraud can occur.
The Nacha Compliance Imperative
This is where regulatory requirements come in — and where many organizations falling short.
The WEB Debit Account Validation Rule took effect in March 2021 and became fully enforceable in March 2022. Nacha implemented the WEB Debit Account Validation Rule to address concerns of online fraud and cut back on returns. Under this rule, every merchant that accepts ACH payments must have a checking account verification system in place as part of its “commercially reasonable fraudulent transaction detection system” to validate routing numbers and verify that checking accounts are open and in good standing.
Critically, the Nacha Operating Rules require an originator to validate the account number prior to its first use and before any change to the account number. That “change to the account number” provision is exactly the scenario exploited in the Cleveland Library case and the credit union attacks — a fraudster requests a banking detail update, and without validation, the payments are rerouted.
What validation methods are required? Organizations can choose from: an ACH prenotification, ACH micro-entry verification, or a commercially available validation service. Vendors may use pools of data, validation of online banking credentials or a combination of both methods.
What are the stakes of non-compliance? If an organization’s returns exceed pre-established levels, it can be fined and even prevented from originating any future ACH debit transactions. Beyond regulatory penalties, the financial losses from a single successful fraud incident often dwarf the cost of implementing controls.
New Nacha rules arrived in 2026. Nacha rule amendments related to monitoring for fraud became effective on March 20, 2026, with additional amendments on June 22, 2026, as part of a larger Risk Management package intended to reduce the incidence of successful fraud attempts and improve the recovery of funds after frauds have occurred.
The Bottom Line
When organizations automate vendor verification, validate bank account ownership and eliminate manual data entry, they remove the primary vulnerabilities fraudsters exploit. The Cleveland Library didn’t verify the bank account change. The credit unions didn’t verify the updated routing numbers. In each case, a simple, Nacha-mandated validation step would have prevented the fraud.
ACH originators are required to screen accounts on the first transaction and upon any changes to account details. Implementing the Nacha-required “commercially reasonable fraud detection system” enables businesses to screen web debits and detect invalid accounts.
The message from both the fraud headlines and the regulators is the same: verifying vendor bank account information — especially at the point of any change — is no longer optional. It is the minimum standard of care. Organizations that treat this as an administrative checkbox rather than a necessary internal control will continue to make the news for the wrong reasons.To learn how Nacha-preferred partner VendorInfo can automate bank account verfication to protect you from fraud, contact us.


