A supplier requested new bank details? Verification starts outside the email

Finance professionals verifying a supplier change request by phone and checking records
AI-generated illustrative image.

A request to change payment details can look routine: the supplier has changed banks, the invoice has been updated and payment is due today. This is precisely when receiving the request must be kept separate from approving the change.

In Business Email Compromise, or BEC, attackers impersonate a familiar business contact or use a compromised email account to redirect funds. A recognizable name and apparently legitimate conversation are therefore insufficient to verify a change. Further information: FBI.

Verify through an established contact

Set a process in which supplier bank details cannot be changed based on email alone. Contact an authorized person using contact details verified and stored before the request arrived.

A phone number in a new signature or attachment is not an independent source. An attacker sending the request could also supply the number you are told to call. If no verified contact exists, complete verification through the existing supplier process before updating the details. Using previously known numbers is also part of the FBI’s BEC prevention guidance.

Two approvals that involve real checks

Two signatures do not help if both approvers rely on the same email. In the proposed workflow, one employee verifies the request with the supplier. A second approver checks the verification evidence and the details entered.

Integrate this into the existing supplier-update process rather than creating a separate route. Define who may request, check and approve a change. Where possible, separate making the change from approving it.

The record should answer a few clear questions: who requested it, who verified it, how the contact channel was selected and who approved it. Avoid circulating bank details in group messages or creating unnecessary copies outside the authorized system.

Handle urgency without bypassing verification

An urgent request is not necessarily fraudulent, but urgency is not a reason to skip verification. Define a backup approver and an escalation route before either is needed.

A request presented as an instruction from the CEO should follow the same process. Escalation should help secure timely verification and approval, not let one employee bypass them. If verification cannot be completed, do not finalize the change or release payment based on it.

Respond when a payment may already have been sent

If a payment may have resulted from fraud, contact the bank immediately through a known channel. Provide the transaction details and ask whether the payment can be stopped or recalled. Recovery is not guaranteed. IC3 advises contacting the bank immediately.

At the same time, involve finance and security, preserve the messages and records, and assess whether other payments linked to the request should be paused. If mailbox compromise is suspected, security should address the account and investigate the scope. Do not wait for the technical investigation before contacting the bank.

One check for the coming week

Select a recent supplier bank-detail change and see whether its verification and approval can be reconstructed. If not, that is a focused opportunity to improve coordination between finance, procurement and IT.

Cybecs can incorporate this review into CISO and risk management work, connecting technical safeguards with operational processes. Explore Cybecs services.