Invoice fraud preventionfor the payment that goes to the wrong account.Invoice fraud, also called vendor payment fraud, reroutes a real payment to a fraudster who changed the banking details by email. RankShield verifies the payee and the approval before the money moves, so a change that arrived in an inbox does not clear on its own.
A real payment, sent to the wrong bank account
Nobody breaks into your bank. The attacker changes where a legitimate payment goes, and your own team sends it.
Invoice fraud, vendor payment fraud and vendor email compromise all describe the same attack. A fraudster either spoofs a supplier’s email or takes over the supplier’s real mailbox, sends a message that the vendor’s banking details have changed, and adds a note of urgency. Your accounts payable team updates the vendor record and pays the next invoice, on time, to an account that belongs to the fraudster. The FBI’s Internet Crime Complaint Center classifies this under business email compromise, which it has called the 55 billion dollar scam based on global exposed losses from 2013 through 2023.
The reason it works is that the payment is authorized. Every fraud control your bank runs is built to catch a payment that you did not mean to make: a stolen card, a hijacked login, an unusual device. This payment is one you did mean to make, to a vendor you really owe, in an amount that matches a real invoice. The only thing wrong is the destination account, and that detail was changed through a channel your controls never inspect. That is why detection built for account takeover does not see it.
The change that no one verifies
The email looks right, the invoice is real, the deadline is Friday
The message comes from the supplier's address, or close to it. It references a genuine open invoice. It asks you to update the account before the next run. Your AP clerk updates the vendor master and schedules the payment. Two days later the real supplier asks where their money is. On a wire, RTP or FedNow, it has already settled and left the country.
Recovery is a backstop, not a control
The FBI can freeze funds when fraud is reported fast enough. Most of the money is already gone.
Source: FBI IC3 2024 Annual Report. We deliberately do not repeat the “72-hour window” figure that circulates online; it does not appear in the FBI’s report.
The control the FBI recommends, made automatic
Every authority names the same defense. The problem is that it depends on a person doing it every time.
The FBI and Nacha both name the same primary defenses against this fraud: verify any change to banking details through a second, out-of-band channel, using a phone number you already hold rather than one from the request, and require a second person to approve the release. That advice is correct. It is also manual, and manual controls fail under exactly the conditions this attack creates: urgency, a real deadline, and an understaffed accounts payable desk where one person can update a vendor and send a wire.
Verify the payee
A banking-detail change is checked against the vendor record you already trusted, not accepted because a message asked for it. The out-of-band step the FBI recommends, applied automatically.
Bind the approval
The specific payment needs proof that an authorized person approved it. Dual control that cannot be skipped when the clerk is under deadline.
Check before it moves
The verification happens before the payment settles on the rail, which is the only point where stopping it still saves the money on an irreversible rail.
Leave a receipt
Every decision produces a record of who approved what, so the AP team can show the control ran. See verifiable attestation.
Shared across the network
A payee or account flagged at one member of the RankShield Network is shared across it, so a fraudster burned at another business is known before it reaches you. Unlike a scoring consortium, every shared verdict is independently verifiable, and the signal compounds as members join.
Small and mid-sized businesses are more exposed, not less
The recommended controls assume a fraud team you do not have. This is built for the team you do.
Enterprises the size of an Accertify client have layered fraud operations. A small or mid-sized business usually has an accounts payable clerk, a manual approval chain, and a founder who can send a wire from a phone. That is not a moral failing; it is how a lean business runs. It is also why the 2026 AFP Payments Fraud survey found that 48 percent of organizations under a billion dollars in revenue took a fraud loss, and why only 17 percent of organizations overall use any automation to fight it. The manual callback the FBI recommends is the right control and the first one to get skipped when the person doing it is also doing four other jobs. Automating it is the point.
A verification vendor should be precise about its own evidence
We do not claim a large fraud-detection network, because that value comes from many participants and we are early. We do not show you customer names or loss-prevention statistics we cannot substantiate. And we do not tell you a build is cryptographically sealed to our transparency log unless it is, which our transparency page reports honestly, build by build. What we offer a small or mid-sized business today is the verification control the FBI and Nacha already recommend, automated and made unskippable, applied before the money moves.
Guides and analysis
How to stop vendor payment fraud when bank details change
How the bank-change scam works, why call-back advice fails on instant rails, and how to verify the payee before you pay.
Read the guide →Business email compromise for small business
How BEC works, the variants a small business actually sees, and the process control that stops it before settlement.
Read the guide →Accounts payable fraud: the numbers
The internal schemes (billing, check tampering), what they cost a small business, and the controls that stop them before release.
Read the guide →Check fraud in 2026: how the schemes work and what stops it
Why check fraud rises as check use falls, the FinCEN mail-theft breakdown, the Positive Pay tiers that stop most of it, and the one gap they cannot close.
Read the guide →Construction payment fraud: the top BEC target sector
Why federal data ranks contractors first, the four hops where an impostor enters the payment chain, and the check that belongs before a draw funds.
Read the guide →Nonprofit payment fraud: controls that catch both risks
The minimum control set for a small finance office, why the annual audit misses fraud, and the one step that stops the insider and the impostor.
Read the guide →Healthcare vendor payment fraud: the AP-side blind spot
The accounts-payable exposure billing compliance does not cover, what the FinCEN advisory actually addresses, and how to verify medical vendor payments.
Read the guide →Positive Pay cannot catch this
Exactly what Positive Pay covers, the authorized-payment blind spot it leaves, and how to close the gap it cannot see.
Read the guide →Payment fraud by industry: the league table
Median fraud losses by sector from FBI, FinCEN, ACFE, and AFP data, and the three traits that make an industry a target.
Read the guide →Payment fraud statistics 2026, read honestly
The FBI, AFP, and ACFE numbers sorted by what each actually measures, what is only projected, and the one event underneath them all.
Read the guide →How school districts lose millions to vendor payment fraud
The anatomy of a district vendor impersonation, why building programs are the entry point, and the verification step that stops it.
Read the guide →Related fraud we stop
ACH fraud
Unauthorized debits and originated credits on a rail with a narrow, misunderstood return window.
Read more →Accounts payable fraud
Internal billing schemes and check tampering, where approval controls fail under volume.
Read more →CEO and wire fraud
An urgent wire request that impersonates an executive and settles before anyone doubts it.
Read more →Authorized push payment fraud
A coached victim is convinced to send the money themselves, so no control is bypassed.
Read more →Deepfake payment fraud
A cloned voice or video authorizes a transfer that looks completely legitimate.
Read more →Transaction fraud prevention
Verify payer, payee, amount, and purpose before an irreversible rail settles.
Read more →Invoice and vendor fraud, answered
Every question buyers ask before they trust a payment-security platform, answered directly.
JAMIE KLONCZ · RANKSHIELD FINANCIAL ONLINEPick a question on the left, or search above. You will get the direct answer, the way an answer engine would give it.
See your payments verified before they settle.
Invoice fraud sends a real payment to the wrong account. The defense is to verify the change before it settles, automatically, on every payment. Request access and we will map it to your accounts payable process.