A Supplier Changed Bank Details. Who Verifies the Change Before Payment?

Photo: Mikhail Nilov / Pexels. Illustrative stock image.
Treat a request to change a supplier's bank details as a separate verification task before it reaches a payment run. Confirm the request through a trusted contact route already held by the business, document the result, and have the authorized reviewer approve the change. An apparently familiar email is not enough by itself.
For a small business using a fractional accounting team, this workflow needs to cross the provider boundary clearly. The supplier relationship may sit with purchasing, the record may sit with bookkeeping, and the payment approval may sit with the owner.
Separate the invoice from the payment instruction
A valid invoice and a valid destination for payment are two different questions. Staff should review the obligation to pay while separately checking any change to where the money is being sent.
The FBI's guidance on business email compromise recommends verifying changes to account numbers or payment procedures with the person making the request. This is particularly relevant when a message adds urgency or asks the recipient to bypass the normal process.
Do not use the new phone number contained in the change request as your only verification channel. Start with a trusted number or established contact method already held in the vendor record. If that information is missing, resolve the verification route before releasing the payment.
Make the handoff explicit
Write down who receives a request, who independently confirms it, who can edit the vendor record, and who approves the payment. In a small organization, some roles may overlap, but the overlap should be visible.
A fractional bookkeeper should know whether they are authorized to update banking details or only prepare the change for review. The owner should know what evidence they are expected to check before approval.
In a hypothetical South Florida importer, purchasing receives a supplier's change request while an outside accounting provider prepares the payment batch. Without a defined handoff, both may assume the other party confirmed the new instructions.
Keep a short verification record
Record the supplier name, the date of the request, the person who confirmed it, the trusted channel used, and the approval. Store sensitive payment information in the appropriate restricted system rather than copying it into a widely shared tracker.
The verification note should make the process understandable to the next reviewer. “Confirmed” alone does not show what was confirmed or how. A brief factual record is more useful than an informal reassurance in chat.
If the supplier cannot be reached, flag the item as unresolved. Give the business owner a clear explanation of the pending payment and the next step. The absence of confirmation should not quietly become approval because the invoice is overdue.
Restrict changes and review exceptions
Ask your accounting system administrator which users can create suppliers or change payment details. Match those permissions to current responsibilities, including access granted to external providers.
Where the system supports it, use separate preparation and approval steps. Review its change history when an unusual payment destination appears. Do not assume a feature exists or is enabled simply because the software is described as secure.
Pay attention to process exceptions as well as amounts. A request involving a familiar supplier and an ordinary invoice can still deserve review if the payment instructions changed unexpectedly.
Prepare the team for a suspicious request
Tell staff where to raise concerns and who can pause a payment for review. Avoid making them decide alone whether a request is fraudulent. Their immediate job is to identify an unresolved change and follow the agreed route.
If money has already been sent and the business suspects fraud, contact the financial institution promptly and follow its instructions. The FBI also provides a reporting route through the Internet Crime Complaint Center. Keep relevant records so the response team can reconstruct what happened.
Does every supplier payment need a new callback?
This article focuses on changed payment instructions and exceptions. Design the broader payment process around your business's risks and available controls. Repeatedly calling every established supplier is not a substitute for managing changes properly.
Put the control into the next payment cycle
Choose one owner for the verification workflow and walk a sample change through it with purchasing, bookkeeping, and the approver. Confirm that everyone knows when the payment is ready and when it remains on hold.
Leyda Lazo and Human Capital Consultants International (HCCI) bring an operating perspective to the responsibilities behind business processes. HRO FullScope can connect role clarity and employee training with the procedures your accounting advisers establish. Contact HCCI to discuss those handoffs.




Comments