Vendor Document Fraud: Edited Bank Details and Certificates
Vendor document fraud usually hides between documents. Which fields a US AP team compares, what a mismatch looks like and what the reviewer does next.

Summarize this article with
Vendor document fraud in US onboarding rarely means a fully invented company. More often it is a genuine vendor file with two or three fields edited: a new routing and account number on a voided check, a different legal name on a certificate of insurance, a policy period moved forward on an ACORD form. Each document looks fine alone. The edit shows up only when one field is compared with the same field on another document, or with an official source.
This article sets out those comparisons for an accounts payable or procurement team in the United States: which field is compared with which source, what a mismatch looks like, and what the reviewer does next.
This article is for informational purposes only and does not constitute legal, financial or regulatory advice. Position as of November 2026, United States federal level unless stated; state rules vary.
Why one-document-at-a-time review misses tampered vendor files
A tampered vendor file passes single-document review because every edited document stays coherent by itself. A voided check with a swapped account number still has the printed logo and check number. A certificate of insurance with a longer policy period still looks like a certificate.
The FBI IC3 2024 Annual Report reports business email compromise, including requests to change a vendor's payment instructions, as a recurring complaint category, and FinCEN has published advisories on the same scheme for financial institutions. Payment instructions are therefore the field to protect first: the edit costs the fraudster almost nothing and a cleared ACH or wire is hard to reverse.
Accounts payable staff often ask: "A vendor emailed new ACH details and the attachment looks right. How do I know it is real?" The attachment cannot tell you. Comparisons can.
The cross-checks that matter
Five comparisons cover most tampering. Each one names the field, the second source, the typical mismatch and the next action.
| Field on document A | Compared with | Mismatch looks like | Reviewer does next |
|---|---|---|---|
| Account holder, routing and account number (voided check, bank letter, invoice) | Vendor master record; the bank's own confirmation | Holder is an individual, not the company; bank in a different state or country; new account on an email-only request | Hold the change; call the vendor on the number already in your master file |
| Legal name and TIN (Form W-9) | State business registry record; name on the invoice and bank account | Name differs from the registry; entity type does not match the box checked; W-9 signed by someone unknown | Request a corrected W-9 and written explanation |
| Entity name and file number (articles, good standing certificate) | Secretary of State business search for the state of formation | Entity inactive or suspended; file number belongs to another entity | Ask for a current certificate obtained directly from the state |
| Named insured, policy number, period (certificate of insurance) | Insurer or the producing agent | Insured is an affiliate; period starts after the contract date; agent cannot confirm the policy | Obtain confirmation from the agent using contact details you found independently |
| Issue date and creator metadata (any PDF) | Claimed date and issuing body | File saved long after the issue date; consumer editor in the producer field | Escalate; request the document again from the issuer |
Payment details against your own records
There is no single national payee-name check in the US that this article can point to, so the control is procedural: the account in the request is compared with the account already on the vendor master record and, where the bank offers it, with the account name the bank reports. No document and no name match proves that the vendor itself asked for the change; only an out-of-band call to a known contact does.
What the reviewer does on any change request:
- Do not pay to the new account and do not reply to the email that carried the request.
- Call the vendor on the number already in the master file, never the number in the request.
- Record who confirmed what, and require a second approver before the master file is edited.
- For a first payment to a changed account, consider a small test payment only after the call-back, not instead of it.
Form W-9: name and taxpayer identification number
The IRS Form W-9 captures the vendor's name, entity classification and taxpayer identification number. Compare the name and classification with the state registry entry and with the name on the bank account. A sole proprietor operating as "Hartwell Components LLC" while the W-9 shows an individual name, or an EIN that the vendor cannot connect to the registered entity, is a mismatch to resolve before onboarding.
The W-9 is self-certified. It records what the vendor says; it is not evidence of what the IRS holds.
Entity status in the state registry
Each state keeps its own business registry, usually run by the Secretary of State. Search the state of formation for the entity's legal name, file number, status and registered agent. A registry lookup confirms the entity exists and its status. It does not confirm that a PDF good standing certificate in your file came from the state. When the stakes are high, order the certificate directly. Our article on company identity checks across supplier documents shows the field-by-field version.
Sanctions screening
US persons must not deal with parties on sanctions lists. Compare the vendor's legal name, and the names of the account holder and beneficial owners you collect, with the OFAC Sanctions List Search. A name hit is a lead for review, not a conclusion, and a clear result says nothing about document authenticity. Bank Secrecy Act program duties fall on covered financial institutions, so a non-financial vendor file is usually governed by your own policy and contract terms rather than the BSA itself; ask counsel which applies to you.
Certificates: dates and issuers
Certificates of insurance are edited most often on dates, named insured and limits. The comparison is with the insurer or producer, never with the document itself.
| Certificate | Fields to compare | Common edit |
|---|---|---|
| Certificate of insurance (ACORD form) | Named insured, policy number, effective and expiry dates, limits | Dates extended; limits raised |
| State contractor licence | Licensee name, licence number, status, classification | Number from another licensee; status shown active when suspended |
| ISO or similar quality certificate | Company name, scope, certificate number, expiry | Scope widened; expiry moved |
| Tax clearance or compliance letter | Entity, reference, issue date | Date refreshed on an old letter |
A certificate of insurance is an informational summary, not the policy; the agent can confirm that the policy exists and is in force. See our guide to fake certificates of insurance and to expiry tracking.
File-level signals
A PDF's metadata can contradict its story. A bank letter said to be issued on March 3 but last saved six months later in a consumer editing tool deserves a question. These are indicators, not proof: legitimate systems also re-save files, and a clean file proves nothing. See detecting PDF metadata tampering.
AI-generation signals can be added as a complement to your existing controls; the AI document detection page describes that approach and its limits.
A repeatable onboarding sequence
A fixed order prevents steps being skipped under time pressure:
- Identity first: legal name and file number against the state registry.
- W-9 against registry and bank account name.
- Sanctions screening on the names collected.
- Payment details against the master record, with a call-back for any change.
- Certificates against the issuer or agent, dates against the contract start.
- File-level review of anything that failed; record the result, sources and reviewer.
A change to bank details on an existing vendor follows the same sequence: treat it as onboarding a new account. See the industry document verification guide and the supplier onboarding documents checklist.
Where software helps and where it does not
Software can extract fields, compare them across the documents in a file and flag mismatches for a person. CheckFile compares names, dates, identifiers and bank details across documents; it does not prove a document is authentic and does not replace the call-back. See data security and pricing. Personal data in vendor files, such as sole proprietors' names and tax IDs, is handled under state privacy laws such as the CCPA where they apply, since there is no single federal privacy statute.
If your team receives vendor files by email and compares them by eye, AI-generation signals and consistency checks are a practical starting point.
Frequently Asked Questions
Does a voided check prove the account belongs to the vendor?
No. It shows an account number and a name as printed on an image that can be edited. Compare it with the master record and confirm by calling a known contact.
What should I do if a vendor's W-9 name does not match the registry?
Pause onboarding and ask for a corrected W-9 and an explanation, for example a doing-business-as name. Resolve the mismatch in writing before any payment.
Is a Secretary of State search enough to verify a vendor?
It confirms the entity's existence and status. It does not show that the certificates and bank letter in the file came from that entity, so the documents still need to be compared with each other and with their issuers.
Which edits are most common in vendor files?
Account numbers on bank letters and invoices, dates and named insured on certificates of insurance, and identification numbers borrowed from other entities. All three show up when fields are compared across documents.
How often should bank details be re-verified?
On every change request and at each certificate renewal. A change request goes through the same sequence as a new onboarding.
Stay informed
Get our compliance insights and practical guides delivered to your inbox.