One Trusted Supplier Page: Verifying Payment Changes Before Money Moves

A fake invoice rarely arrives looking obviously false. It arrives with a familiar logo, a plausible reference and a request that seems routine. The weak point is usually not the software; it is the moment someone searches an inbox for bank details and finds three versions, two contacts and no clear record of which one was ever checked.

A one-page supplier file does not eliminate that risk on its own, but it makes the safe route the quick route. Rather than adding a system, it gives a small UK firm a single trusted place to look before money moves.

What the page is — and what it is not

The page is a current record for each important supplier: the details needed to pay, contact and renew. It is not a full supplier-management database, nor a substitute for accounting records. It sits alongside the ledger as a practical reference that can be opened during a payment run or when a supplier calls.

Keep one page per supplier, or one table with a page per row, depending on volume. What matters is that the same fields appear every time and that the page has an owner.

The fields worth keeping

A workable supplier page has six groups.

First, identity: legal name, trading name, company number where relevant, VAT number if supplied, and the main address.

Second, contacts: a primary commercial contact, an accounts contact and a switchboard number. Record named people and roles, not just email addresses. Include the number used for verification, which may differ from the one printed on an invoice.

Third, payment details: bank name, account name, sort code and account number, held in a secure shared location rather than an email thread. Add the date those details were last verified and the method used.

Fourth, insurance: public liability and professional indemnity expiry dates where the supplier works on site or provides advice. A simple date field is enough; the value is in seeing the expiry before it becomes a gap.

Fifth, commitments: contract renewal dates, notice periods and the person responsible for reviewing them.

Sixth, change history: date, field changed, who approved it and how it was checked. This can be a short line at the bottom of the page.

The call-back rule

The most useful control is a sentence staff can follow without interpretation: any change to bank details is verified by calling a known contact on a number already held in the supplier file. The number in the email requesting the change is not used.

That rule should apply even when the request looks urgent, even when the sender appears to be a director, and even when the new details arrive on supplier letterhead. Fraudsters rely on speed and authority. A short pause and an independent call remove both advantages.

Record the call: date, time, person spoken to and the number dialled. If the supplier cannot be reached, the payment waits. If a supplier genuinely needs to change details, ask for confirmation on letterhead or through a previously agreed channel, then verify by call. Do not accept an email alone.

For firms with more than one person in finance, a second pair of eyes before the first payment to a new account is a sensible addition. It does not need a committee; it needs a named backup.

Where the page lives

Store the supplier file in a shared drive with restricted access, not in a personal inbox. Accounting software may hold supplier records, but the one-page file is for the details that software does not always capture: verification dates, insurance expiries and the call-back trail.

The page should be available during a payment run and when a colleague is on leave. If only one person knows where to look, the control is fragile.

Keeping it current without a project

Maintenance is light if it is tied to events already happening. Add a supplier when onboarding. Update the page when a contract is renewed. Check insurance dates quarterly, perhaps alongside the regular finance review. Review bank details annually, or sooner if a supplier prompts a change.

A simple quarterly check of ten key suppliers takes less time than searching for one misplaced email during a payment run. The page also helps when a supplier asks why a payment is late: the reason is visible, and so is the next step.

The practical benefit

The file is not primarily a fraud document. It is a working reference that happens to reduce fraud risk. It answers common questions quickly: Who do we call about this invoice? When does their insurance expire? Which account did we verify, and when? Why is this payment on hold?

For a small UK firm, that is the point. Controls that depend on memory fail when the diary is full. A one-page supplier file puts the verified answer in one place and gives staff a clear rule for the one moment that matters most: before payment details change.

Fylde VA supports small firms with the administrative routine behind this work — maintaining supplier records, preparing payment runs for approval and keeping verification notes in order. The judgement and authorisation remain with the business; the file simply makes the right step easier to take.