Cybersecurity

Business Email Compromise: Protecting B2B Payments and Vendor Changes

Business email compromise (BEC) is a fraud pattern in which criminals use impersonation, compromised accounts or hijacked conversations to influence a payment or sensitive business action. The most important defence is not spotting a strange-looking email; it is verifying high-impact requests through a trusted process.

Digital security lock and payment card representing protection of business transactions
Digital security lock and payment card representing protection of business transactions. Image served externally; Avenqora Vortax does not host the image file.

A supplier's bank details change. A senior manager asks for an urgent transfer. A real email thread suddenly includes a new payment instruction. These situations can look routine because they use familiar names, projects and invoice language. Business email compromise exploits trust and ordinary business processes rather than relying only on obviously suspicious messages.

What is business email compromise?

BEC is a type of fraud that targets business communication and payment workflows. Criminals may spoof an address, create a look-alike domain, compromise a legitimate mailbox or enter an existing conversation. The goal is often to redirect a transfer, obtain sensitive information or persuade an employee to make an unauthorized change.

The FBI's guidance describes BEC as a scheme that can involve compromised legitimate email accounts and unauthorized transfers. The exact method varies, so a control that only looks for spelling mistakes will miss many cases.

Common BEC scenarios in B2B operations

  • Supplier bank-detail change: an attacker asks accounts payable to replace an existing beneficiary account.
  • Executive impersonation: a message appears to come from a leader requesting secrecy or rapid action.
  • Invoice interception: an attacker takes over or imitates a conversation and replaces payment instructions.
  • Payroll diversion: an employee's payment details are changed without proper identity verification.
  • Professional-services impersonation: a message appears to come from a lawyer, auditor or adviser involved in a transaction.

How a payment redirection attempt can unfold

A typical scenario begins with research into the organization, its suppliers, approval roles and payment routines. The attacker then uses a compromised account, spoofed address or look-alike domain to create a believable request. The message may arrive during a genuine invoice discussion, when the recipient is already expecting an update.

The final instruction often changes one critical detail: the bank account, payment destination, urgency or approval path. Because the rest of the conversation looks familiar, an employee may focus on finishing the task rather than validating the change.

Why email appearance is not enough

Display names can be copied. Domains can be made to look similar. A legitimate mailbox can be compromised, which means the sender address may be correct even though the request is fraudulent. Grammar and spelling are useful clues, but they are not proof of authenticity.

For high-risk actions, verify the request independently. Use a phone number or contact detail already stored in an approved supplier record, not a number included in the email requesting the change. A reply to the same conversation is not an independent verification channel.

Build a payment-change verification process

  1. Separate request from approval: the employee who receives a bank-detail change should not be the only person who authorizes it.
  2. Use a trusted contact record: call a previously verified supplier contact using the number in your system or signed contract.
  3. Record the verification: capture who confirmed the change, when it was confirmed and which source was used.
  4. Apply a second-person check: require independent review for new beneficiaries, changed account details or unusual payment amounts.
  5. Use a controlled update process: change the supplier master record only after verification and approval.
  6. Monitor exceptions: review urgent, out-of-cycle, secrecy-based or unusual payment requests.
  7. Test the process: run a safe tabletop exercise using a fictional supplier-change scenario.

Strengthen email and identity controls

Use multi-factor authentication for business mailboxes, especially accounts involved in finance, procurement and executive communication. Apply strong account recovery procedures, review mailbox forwarding rules and delegate access, and investigate unexpected changes to authentication settings.

Organizations that manage their own email domains should configure and monitor email authentication controls such as SPF, DKIM and DMARC. These controls can reduce some forms of domain spoofing, but they do not prove that every message from a legitimate mailbox is safe. They must sit alongside payment verification and account security.

What to do when a suspicious transfer is discovered

Act immediately. Contact your bank or payment provider and request that the transfer be recalled or stopped where possible. Preserve the email, headers, invoice, payment details and relevant account logs. Notify the internal finance, security and legal contacts according to the incident plan. Report the incident to the appropriate law-enforcement or cybercrime authority in your jurisdiction. In the United States, the FBI's Internet Crime Complaint Center accepts BEC reports.

Do not delete the conversation or continue corresponding with the suspected attacker. Keep communication factual and use verified contact channels to warn the genuine supplier or customer.

Questions finance and procurement teams ask

Can a message from a real supplier email account still be fraudulent?

Yes. A genuine mailbox can be compromised. A familiar sender address should not replace independent verification of a new beneficiary or payment instruction.

Does multi-factor authentication prevent every BEC attack?

No. MFA reduces the risk of unauthorized account access, but social engineering, session theft and compromised accounts can still create risk. Payment controls remain essential.

Should every invoice be verified by phone?

Organizations can use risk-based rules. A new beneficiary, changed bank details, unusual urgency or exceptional amount should trigger stronger verification than a routine payment under an established process.

Key takeaway

BEC prevention works best when trust is supported by process. Verify bank-detail changes through a known independent channel, separate payment initiation from approval, protect business email accounts and rehearse the response to a suspected diversion before money is at risk.

Sources and further reading

These primary and institutional references were consulted for factual verification. The explanations, examples and checklists above are independently written.