Vendor Document Fraud: Edited Bank Details and Certificates
Vendor document fraud usually hides in the gaps between documents. Which fields to compare, what a mismatch looks like and what the reviewer does next.

Summarize this article with
Vendor document fraud in onboarding rarely means a fully invented supplier. More often it is a genuine supplier file with two or three fields edited: a new IBAN on a bank letter, a different company name on an insurance certificate, an expiry date moved forward on a compliance document. The edit is invisible when you read one document at a time. It shows up only when you compare a field on one document with the same field on another document, or with an official register.
This article sets out those comparisons for a UK-based accounts payable or procurement team: 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 Kingdom unless stated.
Why single-document review misses tampered supplier files
A tampered supplier file passes single-document review because each edited document is internally coherent. A bank letter with a swapped account number still has a logo, a date and a signature block. A certificate with a changed policy period still looks like a certificate.
The FBI IC3 2024 Annual Report reports business email compromise, which includes requests to change a supplier's payment details, as a recurring category of complaints, which is why the bank-detail change is the highest-value field to protect. The edit is cheap for the fraudster and the payment is irreversible once it clears.
Reviewers on finance forums often ask the same thing: "A supplier emailed us new bank details and the PDF looks fine. How do I know it is real?" The honest answer is that the PDF cannot tell you. The checks below can, because they move the question out of the document and into a comparison.
The cross-checks that matter
Five comparisons cover most tampering in a vendor onboarding file. 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 name and sort code/account number (bank letter or invoice) | Name returned by the payee bank check; supplier master record | Close match or no match; holder is a person, not the company; bank in a different country from the supplier | Hold the change; phone the supplier on a number from your own records |
| Legal name and company number (certificate, invoice header) | Companies House record | Name differs by one word; company dissolved; number belongs to another entity | Request a corrected document and the explanation in writing |
| VAT number (invoice, onboarding form) | HMRC VAT number check | Number invalid, or registered to a different trading name | Pause onboarding; ask for the VAT registration certificate |
| Policyholder name and policy period (insurance certificate) | Insurer or broker confirmation; company name on the extract | Policyholder is a group entity or a different company; period starts after the contract date | Ask the broker to confirm directly, not through the supplier |
| Issue date and creator metadata (any PDF) | Claimed issue date and issuing body | File modified long after the issue date; editing software in the producer field | Escalate; request the document again from the issuer |
Bank details against the payee check
A bank letter or invoice footer is compared with the account holder name that the payee's bank returns. In the UK this is Confirmation of Payee, a Pay.UK service in which your bank sends the name, sort code and account number to the recipient's bank, which returns match, close match, no match or unable to check.
Confirmation of Payee compares the name you typed with the name on the account; it does not tell you whether the supplier actually asked for the change. A fraudster who controls an account named "Hartwell Components Ltd" will get a full match. For a business account, the name to enter is the registered or a trading name on the account.
For euro payments to suppliers in the euro area, the equivalent is Verification of Payee under Regulation (EU) 2024/886, which applies to payment providers from 9 October 2025 and matches the payee name against the IBAN. Same limit: it matches name to account, not request to authorisation.
What the reviewer does on a mismatch:
- Do not pay to the new account and do not reply to the email that carried the change.
- Call the supplier on the number already in your vendor master data, not the number in the request.
- Record who confirmed what, and require a second approver before the master record is changed.
Company identity against the register
The legal name and company number on a certificate or letterhead are compared with the Companies House record: registered name, company number, status, registered office. A register lookup confirms that the entity exists and what it is called. It does not confirm that the PDF in front of you was issued by it.
Typical tampering: a certificate of incorporation reissued with a longer, more credible name; a number copied from a dormant company; an address that matches a virtual office used by many unrelated entities. Our guide to company identity consistency across supplier documents shows the field-by-field version of this check.
Tax identifiers
A UK VAT number on an invoice or onboarding form is checked with the HMRC VAT number check, which returns the registered name and address for a valid number. Compare that name with the contracting entity and the account holder name. A valid number registered to a different business is a common sign of a borrowed identifier.
Certificates: dates and issuers
Compliance and insurance certificates are edited most often on dates, names and cover amounts. The comparison is between the document and its issuer, never between the document and itself.
| Certificate | Fields to compare | Common edit |
|---|---|---|
| Public or employer's liability insurance certificate | Policyholder, policy number, period, limit of indemnity | Period extended; limit raised |
| ISO or similar quality certificate | Company name, scope, certificate number, expiry | Scope widened; expiry moved |
| Health and safety or accreditation certificate | Holder name, scheme number, validity | Number from another holder |
| Tax or compliance letter | Entity name, reference, issue date | Date refreshed on an old letter |
For each, the reviewer asks the issuer (insurer, certification body, scheme operator) to confirm the number and dates, using contact details found independently. Our checklist on fake certificates of insurance covers the insurance case in more depth, and the supplier certificate expiry tracking article explains when to re-check.
File-level signals
A PDF's own metadata can contradict its story. A bank letter said to be issued on 3 March but last saved six months later in a consumer editing tool deserves a question. These signals are indicators, not proof: legitimate systems also re-save files, and a clean file proves nothing. Treat them as a reason to compare more closely, and see detecting PDF metadata tampering for what the fields mean.
AI-generation signals can be added as a complement to your existing controls; CheckFile's AI document detection page describes that approach and its limits.
A repeatable onboarding sequence
Run the comparisons in a fixed order so that no step is skipped under time pressure:
- Identity first: company number and legal name against the register.
- Tax identifiers against the tax authority check.
- Bank details against the payee check and the master record, with a call-back for any change request.
- Certificates against their issuers, with dates compared to the contract start.
- File-level review of anything that failed or looks edited.
- Record the result, the sources and the reviewer.
The same sequence applies to a bank-detail change on an existing supplier. Treat the change request as a new onboarding of the bank account. The wider context is in the industry document verification guide and the supplier onboarding documents checklist.
Where software helps and where it does not
Software can extract the fields, compare them across documents in a file and flag the mismatches for a human. CheckFile describes what a check compares (names, dates, identifiers, bank details across documents) and where the result needs a person to decide. It does not prove that a document is authentic, and it does not replace the call-back to the supplier. See how CheckFile handles data and pricing.
If your team receives supplier files by email and compares them by eye, the AI-generation signals and consistency checks are a practical starting point.
Frequently Asked Questions
Does Confirmation of Payee protect me from a fake bank-detail change?
Only partly. It confirms the name matches the account at the receiving bank, but a fraudster can open an account in a similar or even identical trading name. Always combine it with a call-back on a known number.
What should I do if the account holder name is a close match?
Treat it as a mismatch until proven otherwise. Ask the supplier, via your own records, to confirm the exact account name and the reason for the change, and keep the written answer on file.
Is a Companies House check enough to verify a supplier?
It confirms the entity exists, its status and its registered name. It does not show that the certificates or bank letter in the file came from that entity, so documents still need to be compared with each other and their issuers.
Which document edits are most common in vendor files?
Bank account numbers on letters and invoices, names and dates on insurance and compliance certificates, and company numbers borrowed from other entities. All three are caught by comparing fields across documents.
How often should supplier bank details be re-verified?
Re-verify on every change request and at each certificate renewal. A change request should go through the same sequence as a new onboarding.
For where this fits in the CheckFile offering, see our AI and deepfake detection approach.
Stay informed
Get our compliance insights and practical guides delivered to your inbox.