A $1 Million Warning for AP: Validate Bank Accounts Before Money Moves – Part I

A fraudulent payment can go out in minutes. Getting it back can take years, and there’s no guarantee you ever see all of it again.
A recent cyberattack on the Judiciary of Guam is a good reason for every accounts payable (AP) leader to pay attention.
According to a Pacific Daily News report, roughly $1 million stolen in a February cyberattack was wired to two JPMorgan Chase accounts, then seized by the FBI. That recovery is good news, but don’t let it distract from the real lesson: once money lands in an account a fraudster controls, getting it back means law enforcement, banks, lawyers and no small amount of luck.
The bigger point for AP departments: cybercriminals don’t need to hack a payment platform or beat a bank’s security. They just need to change where AP thinks the money is supposed to go.
Which is exactly why bank account ownership validation belongs near the top of the disbursement controls list.
Why This Incident Matters to AP Leaders
Every AP department faces the same exposure: a payment gets redirected to a criminal-controlled account, and the loss can grow substantial before anyone catches it.
Fraudsters go after the weak points in the vendor payment process. They compromise email accounts. They impersonate trusted suppliers, register lookalike domains, alter invoices, and slip in phony bank account change requests. Generative AI has only made this easier — cleaner emails, a vendor’s actual writing style, realistic-looking documents, social engineering that’s targeted and fast.
A fraudulent request can carry the right supplier name, the right invoice number, contract details, even employee contact information. It might look like it’s from an executive or a vendor contact AP has worked with for years. It might even reference a payment that’s genuinely due.
The bank account is often the only thing that’s fake.
This is why these schemes work: AP staff aren’t usually missing an obvious red flag. They’re responding to a request built to look exactly like every other request that day. There’s nothing “red” about it.
Familiarity Is Not Verification
Most organizations still lean on manual verification — a voided check, an email exchange with the supplier, a phone call, a check against the vendor master, maybe a second employee signing off.
These feel like controls. Whether they work depends on where the underlying information came from, and whether the person doing the verifying is really talking to the account’s legitimate owner.
Here’s a scenario that plays out constantly. An AP employee gets an email from what looks like a familiar vendor. It says the vendor switched banks and asks that future payments go to a new account, with a professional-looking bank letter and voided check attached. Per policy, the employee calls the number in the email to confirm. Someone answers, confirms the new details, thanks AP for moving fast.
The employee followed the process to the letter. But the email, the attachments, the phone number, and the person on the other end of the call could all have come from the same fraudster. AP didn’t skip verification — the verification just relied on a channel that was compromised from the start.
Familiarity makes this worse, not better. People let their guard down with a vendor they’ve paid for years. Criminals know this — that’s exactly why they target established relationships. A decade of history with a supplier says nothing about whether this particular bank account is real.
Validate the Account, Not Just the Request
Before money moves, one question must be answered: does this account actually belong to the person or business the organization intends to pay?
A properly formatted account number doesn’t answer that. Neither does confirming the routing number belongs to a real bank — criminals use real accounts at real institutions all the time.
Automated bank account ownership validation checks submitted account information against authoritative banking data and other trusted sources to confirm the payee actually controls it. Depending on what’s available, that can confirm:
- The routing number is valid
- The account exists and is open
- The account can receive the payment
- The account ownership matches the supplier being paid
- The submitted business name, address, Tax ID, or other identifying details match available records
- The account and routing numbers match what was submitted
- Any discrepancy gets flagged for investigation before payment goes out
That brings independent evidence into the approval process instead of relying entirely on an email, a document, or a voice on the phone from whoever’s asking for the change.
No control eliminates fraud risk on its own. But automation makes it a lot harder for an attacker to redirect a payment just by sounding convincing.
Why Automation Matters
In theory, an organization could manually verify every new supplier and every account change in detail. In practice, that doesn’t hold up. AP teams process high volumes on tight deadlines, sometimes managing thousands of vendors. Calls don’t get answered. Banks won’t disclose account details over the phone. Supplier contacts go quiet. Documents are incomplete. And as the due date closes in, the pressure shifts from “verify this properly” to “clear it and pay.”
That pressure is where things break down unevenly. One employee runs five checks; another runs one. A small vendor gets waved through faster. An urgent request from an executive skips a step. A validation that never really resolved gets marked done because the payment can’t wait any longer.
Automation removes that inconsistency. Instead of deciding case by case which vendors deserve scrutiny, organizations can require independent validation on every new payment instruction and every account change, every time. It’s also faster than phone tag and email chains, which eases the tradeoff between security and paying on time. A control that’s built into the workflow gets used. A control that depends on someone remembering five manual steps eventually doesn’t.
Continue to A $1 Million Warning for AP: Validate Bank Accounts Before Money Moves – Part II


