Why familiar email threads are not enough
Business email compromise can involve a compromised mailbox, a lookalike domain or an impersonator entering an existing conversation. A message may appear consistent with the normal supplier relationship while requesting a change to payment details.
Replying to the same thread is not independent verification. If the mailbox or conversation is compromised, the attacker may be able to influence the reply as well.
Create a separate verification path
For bank-detail changes or unusual payment instructions, use a trusted telephone number or contact route already held in the supplier master record or independently verified source. Do not use contact details supplied only in the change request.
Define who may request, verify and approve a change. Where practical, separate those responsibilities and require a second authorised review for high-risk changes.
Preserve evidence and make escalation simple
Record the request, verification method, people involved, time, outcome and supporting evidence. Make it easy for staff to pause a transaction and escalate a mismatch without fear of blame.
Review exceptions, near misses and repeated patterns. A process that exists only in a policy document is unlikely to help under pressure.
Combine technical and process controls
Email authentication, anti-phishing controls, suspicious-message reporting and identity security can reduce exposure, but they do not replace independent payment verification.
Test the process using authorised simulations and confirm how suspicious messages are triaged, investigated and closed.
Treat payment-detail changes as high-risk instructions: verify through a separate trusted channel, separate duties and preserve the evidence.