A vendor bank-change request arrives late Friday afternoon. The email looks familiar, the invoice number is real, and the sender wants payment redirected before the weekend. That is exactly the point at which accounts payable teams need to know how to spot vendor fraud: before a routine payment becomes an unrecoverable wire transfer.
Vendor fraud rarely announces itself with an obvious fake logo or poor grammar. It often exploits trusted vendor relationships, rushed onboarding, incomplete W-9 records, and payment processes built for speed without enough independent verification. The strongest defense is not a single fraud tool. It is a controlled vendor lifecycle that validates identity, tax information, ownership, and payment instructions at the right moments.
Why vendor fraud reaches accounts payable
Fraudsters target vendor records because those records sit near real money. A criminal may pose as a new supplier, impersonate an existing vendor, submit duplicate invoices, or compromise an employee email account and request an ACH or wire update. Each scheme relies on one operational weakness: someone accepts a change or payment request without verifying it through a trusted channel.
The risk rises when the same team creates vendors, approves invoices, and releases payments. Smaller organizations may not have enough staff for complete segregation of duties, while large organizations can lose visibility across decentralized business units. In both cases, clear approval rules and verifiable documentation matter more than informal familiarity.
A legitimate business can still create a compliance risk if its legal name and taxpayer identification number do not match its W-9. That mismatch may lead to a B-Notice, backup withholding work, a corrected 1099, or a payment hold. Fraud prevention and 1099 compliance should therefore operate as one vendor-validation process, not separate tasks.
How to spot vendor fraud in onboarding
The best time to stop vendor fraud is before the first invoice. A new vendor record should never be created solely from an emailed W-9, an invoice attachment, or a salesperson’s request. Treat those documents as inputs to verify, not proof by themselves.
Start by confirming that the business exists under the name it claims to use. Compare the legal business name, DBA name if applicable, business address, contact information, EIN or TIN, and payment recipient name. Minor differences are not automatically fraud. A company may use a trade name, have recently moved, or have a parent company handling payments. The issue is whether the differences are explained, documented, and independently confirmed.
Tax ID validation is especially useful here. A W-9 can be completed with a mistyped, inactive, or unrelated TIN. Vendor TIN matching checks whether the submitted name and TIN combination aligns with IRS records for reporting purposes. It does not establish that every transaction is legitimate, but it can expose a critical mismatch before the vendor is paid or reported on a 1099.
For higher-risk vendors, verify the business through a contact method obtained independently of the vendor’s request. Do not call the phone number in a suspicious email or use a link supplied by the sender. Use a known number from an existing contract, your internal vendor master, or independently researched business contact information.
Red flags that require a pause
No single warning sign proves fraud. Several together should trigger a documented review before onboarding or payment:
- A new vendor insists on urgent payment before normal onboarding is complete.
- The legal name, W-9 name, invoice name, and bank account holder do not align.
- A vendor submits a personal bank account for payments without a clear and reasonable explanation.
- The email domain differs subtly from the vendor’s known domain, such as a changed letter or extra word.
- The requested payment instructions change shortly after setup or immediately before a large payment.
- The vendor refuses a verification call or redirects every question to email.
Urgency deserves special attention. Real suppliers sometimes need expedited payment, particularly in construction, logistics, health care, or emergency procurement. The correct response is not an automatic rejection. It is an accelerated verification path with an approver who is separate from the person requesting the exception.
Verify payment changes as if they were new vendors
Existing vendors are frequently impersonated because their invoices, contacts, and business relationships already look credible. A bank-change request should be treated as a high-risk event even when it comes from a familiar email address. Email accounts can be compromised, and a fraudster may have access to invoice history and internal conversations.
Require a callback to a previously verified contact number before changing ACH or wire instructions. The caller should confirm the new bank details and the reason for the change. Record the date, contact name, phone number used, employee who completed the callback, and the approval decision. A reply to the incoming email is not an independent verification step.
Add a cooling-off period for high-dollar changes when your operations allow it. For example, payment instructions updated today may not be eligible for a wire release until the next business day or until a second approver validates the record. This creates friction, but it is targeted friction where fraud losses are most likely.
For recurring vendors, compare the bank account change with prior payment patterns. A different account is not inherently suspicious, but a sudden change combined with a new address, a new email domain, and a rushed payment request is a pattern worth escalating.
Use invoice controls that catch familiar schemes
Vendor fraud is not limited to false identities. Valid vendors can submit duplicate invoices, inflated charges, or invoices for goods and services never received. Accounts payable needs controls that compare invoices against the underlying business event.
For purchase-order environments, use a three-way match between the purchase order, receiving record, and invoice. If a service cannot be received through a standard goods-receipt workflow, require confirmation from the business owner that the service was performed. The approval should identify what was delivered, when it was delivered, and who accepted it.
Duplicate invoice checks should review more than invoice number. Fraudsters may alter one digit, remove a leading zero, or resubmit the same amount under a different invoice format. Compare vendor name, invoice amount, date range, purchase order, payment terms, and line-item descriptions. Repeated round-dollar invoices, split invoices just below approval thresholds, and unusually frequent credits can also justify review.
Do not let a legitimate vendor relationship override standard controls. Long-tenured suppliers can be impersonated, and trusted employees can make errors. Consistent controls protect the vendor as much as they protect your organization because they reduce misdirected payments and payment disputes.
Build a vendor master that can withstand review
A clean vendor master is one of the most practical fraud controls available. Limit who can create or edit vendor records, require dual approval for sensitive changes, and preserve an audit trail. The audit trail should show what changed, who changed it, when it changed, and who approved it.
Review vendor records periodically for duplicates, inactive accounts that suddenly reactivate, shared bank accounts across unrelated vendors, and records with incomplete tax documentation. The appropriate review frequency depends on payment volume and risk. A small business may review changes weekly; a large enterprise may need daily exception reporting and automated alerts.
Vendor TIN matching should be part of that record hygiene. Before 1099 filing season, bulk matching can identify name-TIN mismatches across the vendor file early enough to obtain corrected W-9 information. Waiting until forms are prepared creates avoidable rework and increases the chance of B-Notices.
EINSearch.io supports this process with instant EIN lookup, IRS TIN matching, and batch validation for teams that need to review large vendor populations without relying on manual searches. Fast validation helps teams keep onboarding moving while reserving human review for exceptions that actually require judgment.
Make escalation clear and practical
Employees miss warning signs when they are unsure who can stop a payment. Give AP staff authority to place a temporary hold when identity, tax details, or bank instructions cannot be verified. The hold should not be treated as an accusation. It is a routine control that protects both parties until the record is confirmed.
Define escalation levels in advance. A low-risk mismatch may require a corrected W-9. A suspected email compromise may require confirmation from procurement, treasury, information security, and the vendor’s known account contact. A suspected internal conflict or intentionally false invoice requires a separate investigation with preserved records.
Train employees on realistic examples from your own workflow: spoofed bank-change emails, duplicate invoice patterns, mismatched W-9s, and last-minute wire requests. Training works best when it explains the required action, not just the threat. “Call this number, document this confirmation, and obtain this approval” is more useful than “be careful.”
A vendor record should earn trust through repeatable evidence, not through a convincing email or an urgent request. When identity validation, TIN matching, payment-change callbacks, and invoice controls work together, AP can move quickly without making speed the enemy of verification.
