What is vendor fraud and how do you prevent it?
Direct Answer
What is vendor fraud? Vendor fraud is any scheme that tricks an organization into paying money it does not owe, or paying the right amount to the wrong account, by abusing its relationships with suppliers.
The most damaging version today is vendor impersonation: an attacker poses as a real supplier and asks accounts payable to update the bank details on file. The next real invoice is then paid into the attacker's account.
Other types include fake invoices from vendors that do not exist, inflated or duplicate invoices, and kickback schemes between an insider and a supplier.
The single most effective control is to verify every change to payment details directly with the vendor, using contact details you already had on file, before any money moves.
Why This Problem Exists
- Accounts payable teams process many invoices and change requests, and attackers time their requests to look routine.
- Vendor impersonation often starts with a compromised or spoofed vendor email, so the request can come from what looks like the right address and reference real invoices.
- Attackers increasingly follow up by text or phone to add urgency, and those channels are rarely checked.
- Once a payment lands in a fraudulent account, it is often moved quickly and is hard to recover.
- The FBI's Internet Crime Complaint Center reports business email compromise, which includes vendor impersonation, as one of the costliest forms of cybercrime, with billions of dollars in reported losses.
How It Works Today (Current State)
- Many organizations rely on a policy to "call the vendor to confirm" bank changes, but the call is often made to a number included in the request itself.
- Verification steps are inconsistent across people and shifts, and urgent requests from senior staff often skip them.
- Email security catches some spoofed messages but not requests sent from a vendor's real, compromised account.
- Fraud is often discovered only when the real vendor asks why they have not been paid.
Better Approach (Actionable Framework)
- Require independent verification for every change to vendor payment details, using contact information already on file, never details from the request.
- Separate duties so the person who changes vendor bank details is not the person who approves payment.
- Hold payments to newly changed accounts until verification is complete, and flag first payments to new accounts for review.
- Treat urgency, secrecy and pressure to bypass the normal process as red flags, regardless of who appears to be asking.
- Train accounts payable to expect follow-up texts and calls as part of the same attack, and give them a way to report those too.
- Review the vendor master file regularly for duplicate vendors, unexpected bank changes and accounts that do not match the vendor's location.
Key Takeaways
- Vendor fraud is paying the wrong party, and vendor impersonation is the most common way it happens today.
- Changes to bank details are the moment of highest risk.
- Verify through a channel you already trust, never one supplied in the request.
- Attacks often span email, text and phone, so verification has to as well.
Where SmishAlert Fits
SmishAlert Confirm gives accounts payable a simple way to verify a payment change with the real vendor contact before money moves, and it leaves a record of who confirmed what and when.
When the request or follow-up arrives by text or phone, SmishAlert flags the suspicious message or call so the team sees the attack across channels.
Founding customers can use Confirm with outside vendors as well as inside their own organization.