A finance manager receives a familiar invoice from a long-standing supplier. The branding looks right, the amount fits the usual pattern, and the email arrives in the middle of a busy payment run. One line says the supplier has changed its bank details. With a deadline approaching, the update is entered into the banking system and approved.
The supplier never sent that request.
This is the practical danger of business email compromise, or BEC. It doesn't usually depend on a virus appearing on a laptop. It succeeds when criminals make a fraudulent instruction look like a normal business decision, then exploit gaps in identity checks, payment approvals, and communication habits.
Table of Contents
- Understanding Business Email Compromise
- Common Attack Vectors Used by Criminals
- Financial Impact and Risks for SMEs
- Technical Controls to Block Email Fraud
- Process Hardening and Staff Training
- Incident Response Steps for Compromised Accounts
- Securing Your Business Against Future Threats
Understanding Business Email Compromise
A BEC incident often starts with a routine task rather than an obvious crisis. A finance employee receives a message that appears to come from a director, supplier, solicitor, or customer. The wording may be polished, the conversation may contain genuine details, and the request may arrive at exactly the time a payment is expected.
The criminal's objective is to influence a person with authority to transfer money or disclose sensitive information. The National Cyber Security Centre defines BEC, also called payment diversion fraud in UK guidance, as a phishing attack in which criminals trick a senior executive or budget holder into transferring funds or revealing sensitive information. The NCSC definition of business email compromise makes an important distinction. This is a fraud attack delivered through trusted communication, not just an unwanted email containing malware.
Why antivirus cannot solve the whole problem
Traditional antivirus is useful when a malicious file or programme reaches a device. It can't decide whether a genuine supplier has legitimately changed its bank account, or whether a senior manager really approved an urgent payment. If the message contains no malicious attachment and the recipient is authorised to make the transfer, the technical system may see nothing obviously dangerous.
That shifts the control point from the endpoint to the identity and process around the transaction. Your organisation needs to know:
- Who sent the request: Is the sender using the genuine account, a spoofed address, or a lookalike domain?
- What changed: Has a bank account, beneficiary, invoice, or payment instruction been altered?
- Who verified it: Did someone use a trusted, independent contact route?
- Who approved it: Was the payment reviewed by another authorised person?
Practical rule: An email can be genuine and still contain a fraudulent instruction if the sender's account has been compromised.
BEC is particularly dangerous because it fits ordinary work. Staff are trained to respond to customers, process invoices, and help directors meet deadlines. Criminals turn those strengths into weaknesses by adding urgency, secrecy, authority, or a plausible explanation for why normal checks should be skipped.
The right question isn't only, “Did our email filter catch the message?” It is, “Could someone still redirect a payment if an attacker reached a legitimate mailbox?” That question leads to stronger controls.
Common Attack Vectors Used by Criminals
Criminals generally reach a BEC outcome through one of two routes. They may take over a real account, or they may impersonate a trusted person from an address that only looks legitimate. Both approaches exploit the recipient's confidence in names, familiar conversations, and established suppliers.

Full account takeover
An attacker first captures a user's password, often through a convincing sign-in page or a message that creates an urgent reason to log in. If the account lacks effective multi-factor authentication, the criminal may then access the mailbox as the actual user.
A compromised mailbox gives the attacker valuable context. They can read previous invoices, identify who approves payments, observe the language used by a supplier, and find out when a contract or project reaches a payment stage. They can then insert a fraudulent message into an existing conversation, or wait until the right moment to send a new request.
The most concerning messages may come from the genuine address. Checking the visible sender name won't help if an authentic account has been taken over. Staff may also overlook suspicious mailbox rules, forwarding settings, or deleted messages that conceal the attack from the account owner.
Display-name spoofing and lookalike domains
Spoofing doesn't require access to the supplier's mailbox. A criminal can register or use an address that resembles the legitimate one, then select a display name matching a director or supplier contact. At a glance, the message appears familiar, while the underlying address contains a subtle variation.
A lookalike domain may replace a character, add a word, or use a different domain ending. The message may pass basic filtering because it doesn't contain malware or an obviously suspicious attachment. The recipient's attention, not the filter, becomes the final barrier.
The NCSC describes BEC in the UK as an impersonation-led business payment fraud pattern, where criminals impersonate a trusted party to induce a transfer of funds or sensitive information. The NCSC guidance on business payment fraud supports a layered response that covers mail flow, account identity, and payment approval rather than relying on spam detection alone.
For staff who handle executive impersonation and payment requests, a practical companion resource is this guide to spot and stop phishing scams. Use it to reinforce the difference between recognising suspicious wording and independently verifying a financial instruction.
Financial Impact and Risks for SMEs
BEC deserves attention from smaller firms because one diverted payment can affect payroll, supplier relationships, tax obligations, or the cash available for day-to-day operations. The loss isn't limited to the amount sent. Staff may need to investigate the incident, contact the bank, reconstruct communications, support affected suppliers, and explain why the payment process accepted the change.
UK figures show why this risk is financially material. The National Economic Crime Centre reported 4,600 BEC cases over 12 months, with £138 million in losses, equivalent to about £30,000 per case on average. The same reporting described criminals impersonating others and altering invoices to redirect payments. The UK BEC loss reporting provides a useful reminder that case volume doesn't need to be enormous for the effect on individual businesses to be severe.

Why SME processes are exposed
Many SMEs have capable people but limited separation between responsibilities. The same employee may receive an invoice, update a supplier record, and prepare a payment. A director may approve an urgent transfer while travelling, relying on a short email exchange rather than the normal process.
Deadline pressure makes that arrangement more fragile. The reported UK data noted seasonal spikes around March and November, periods when financial activity and approval pressure can increase. That doesn't mean every payment made during those periods is unsafe. It does mean that attackers can benefit when staff feel that delaying a transaction will create a bigger business problem.
The secondary risks deserve equal attention:
- Cash-flow disruption: A diverted payment may leave the business unable to meet an immediate obligation.
- Supplier conflict: A legitimate supplier may believe the customer has failed to pay, while the customer believes the invoice was settled.
- Evidence gaps: Informal approvals over email can make it difficult to establish what happened and which checks were performed.
- Underreporting: Embarrassment, uncertainty, or concern about reputational damage can delay notification and reduce the opportunity to recover funds.
The sensible response isn't to stop electronic payments. It's to add deliberate friction at the points where payment details change, urgency is unusual, or a request falls outside the established pattern.
Technical Controls to Block Email Fraud
Technical controls should make impersonation harder and account takeover less useful. They won't replace a call to a supplier, but they reduce the number of fraudulent messages that reach staff and limit what an attacker can do with a stolen password.

Start with email authentication
Ask your IT provider to review SPF, DKIM, and DMARC for every domain used by the organisation, including domains used for newsletters, ticketing systems, CRM platforms, and other third-party services.
- SPF identifies approved systems that are allowed to send mail for your domain.
- DKIM adds a cryptographic signature that helps recipients check whether the message came through an authorised service and whether its content was altered.
- DMARC connects those checks to a policy and reporting process, helping the organisation identify and deal with messages that impersonate its domain.
These controls are most useful when they are treated as an operating process rather than a one-off configuration task. The sender list must remain accurate as suppliers and platforms change. Reports should be reviewed, and enforcement should be introduced carefully so legitimate business messages aren't blocked without an owner knowing why.
Protect accounts, not just messages
Require multi-factor authentication for email, remote access, finance systems, and administrative accounts. A password alone shouldn't open a mailbox that contains invoices, supplier conversations, customer data, and executive correspondence.
MFA is not a complete answer. Staff can still approve a fraudulent payment after signing in normally, and attackers may target the second-factor process through social engineering. It does, however, make a stolen password less useful and raises the difficulty of taking over a real account.
Also ask for monitoring of:
- New mailbox forwarding rules.
- Unexpected sign-ins or unfamiliar devices.
- Changes to MFA methods and recovery details.
- Unusual access to shared mailboxes.
- Suspicious OAuth permissions and connected applications.
- Messages that contain payment instructions from newly observed domains.
For broader guidance on email controls, this practical resource explains how to spot and stop phishing scams. A managed email security service may add anti-phishing checks, URL scanning, malware filtering, encryption, archiving, and data loss prevention, but those features should support a defined payment process rather than create a false sense of safety.
Process Hardening and Staff Training
The strongest BEC control is often a simple rule that employees follow even when the mailbox is genuine: never accept a bank-detail change from the same channel that delivers the request.
A supplier's compromised account can send a perfectly authentic-looking message. SPF, DKIM, DMARC, and MFA may all be functioning correctly while the criminal uses the supplier's legitimate session. The recipient therefore needs an independent way to confirm the change.
Make verification independent
Document a callback procedure for changes to supplier bank details, payment destinations, payroll information, or standing instructions. The employee should use a telephone number already stored in the supplier record or contract, not a number included in the new email.
The caller should ask the supplier to confirm the request without reading out sensitive information supplied by the suspicious message. If the supplier says no change was requested, pause the payment, preserve the email, and escalate it as a suspected incident.
This process creates some friction. A payment may take longer, and a supplier may occasionally find the extra check inconvenient. That is a reasonable trade-off when the alternative is allowing a single compromised conversation to change where money goes.
Separate preparation from approval
Payment preparation and payment approval shouldn't sit with one person for higher-risk transactions. Set an internal threshold that requires a second authorised person to review the beneficiary, invoice history, change request, and verification note.
The second approver must be independent. Forwarding the same email and asking, “Does this look okay?” creates little protection if both people rely on the same deceptive evidence. A stronger review uses the accounting system, an established supplier record, and a separate communication route.
Training should focus on decisions rather than slogans. Show staff how criminals use:
- Urgency: “Pay this before close of business.”
- Authority: “The director has already approved it.”
- Secrecy: “Don't discuss this with the wider team.”
- Disruption: “I'm unavailable for a call, so use the new details.”
- Familiarity: A reply inserted into a genuine invoice conversation.
A good training exercise ends with one behaviour: stop, use a trusted contact method, and record who confirmed the request.
Give employees a route to report a concern without blaming them for raising a false alarm. People will bypass controls they believe are punitive or impractical. They are more likely to use a process that is quick, clear, and supported by management.
Incident Response Steps for Compromised Accounts
Treat a suspected BEC incident as both a security event and a payment emergency. Don't wait until the investigation is complete before contacting the bank or warning people who may act on further instructions.

Contain the account
Start by contacting your IT administrator or security provider through a trusted route. Reset the affected password, revoke active sessions, review MFA settings, and remove unfamiliar recovery methods. Don't use links inside the suspicious email to reach the account.
Check for forwarding rules, deleted messages, hidden folders, delegated access, and unauthorised connected applications. An attacker may have changed the mailbox so future replies are copied elsewhere or so warnings disappear from the user's view.
Investigate the payment path
Preserve the original email, headers, attachments, invoice versions, approval messages, call notes, and relevant sign-in records. Don't delete evidence while cleaning the mailbox. Export information through your normal administration tools or ask your provider to preserve it before making extensive changes.
Ask the finance team to identify every payment instruction received from the affected account or lookalike domain. Review recent supplier-detail changes and notify the people responsible for accounts payable, procurement, payroll, and treasury.
Contact the bank quickly
Call the bank's fraud department using a trusted number and explain that a payment may have been diverted through business email compromise. Request guidance on recalling or freezing the payment, and provide the transaction details as soon as they're available.
Contact the legitimate supplier or impersonated person through a known number. Warn them that their account, domain, or identity may be involved, and tell them not to trust further payment instructions until the communication channel is confirmed.
Use the following order if the situation is unfolding quickly:
- Contain: Disable or secure the affected account and stop related payments.
- Notify: Alert the bank, senior management, finance staff, IT provider, and relevant counterparties.
- Preserve: Keep emails, logs, invoices, approvals, and notes in their original form.
- Assess: Determine whether personal data or confidential information was accessed.
- Report: Seek advice on reporting to the appropriate authorities and on any data-protection notification duties.
The exact legal response depends on what information was accessed and which organisations are involved. Your solicitor, insurer, incident-response provider, and data-protection adviser should be engaged where the incident involves personal data, contractual obligations, or a material financial loss.
Securing Your Business Against Future Threats
Email security isn't a product purchase that can be marked complete. It is an ongoing discipline involving identity, mail flow, supplier records, payment approvals, access reviews, and staff behaviour.
A basic spam filter remains useful, but it answers a narrow question: does this message resemble known unwanted mail? BEC often asks a different question: does this trusted-looking request fit the person, supplier, payment, and process involved? A filter may flag a suspicious domain, but it can't independently confirm a bank-detail change with a supplier.
Review the controls that matter
Build a recurring review around the organisation's real exposure:
- Access: Remove unused accounts, review administrator privileges, and confirm that leavers lose access promptly.
- Authentication: Check MFA coverage and investigate unexpected changes to recovery details or connected applications.
- Mail flow: Review SPF, DKIM, DMARC reports, forwarding rules, shared mailboxes, and third-party senders.
- Payments: Test whether staff follow callback and dual-approval requirements under time pressure.
- Suppliers: Keep contact details and approved payment instructions in a controlled record, separate from the email thread.
- Response: Confirm who contacts the bank, who preserves evidence, and who communicates with customers and suppliers.
A local IT support provider can help connect these tasks. Look for practical assistance with Office 365 or Google Workspace, managed firewalls, identity controls, email filtering, monitoring, and incident response. The provider should explain what each control does, what it cannot do, and which business process still needs a human check.
UK evidence reinforces the need to look beyond generic phishing awareness. The Cyber Security Breaches Survey 2025 data reports that 5% of large businesses and 5% of medium businesses reported accounts or systems compromised for illicit purposes, compared with 1% overall. That distinction supports a more precise priority for growing firms: harden identities and approval processes, then use email filtering as one layer within that system.
Review your BEC controls with the same seriousness as your payment controls. If a new supplier can be added without independent verification, if one employee can alter bank details and approve the payment, or if nobody knows who should call the bank during an incident, the organisation has a process gap that software alone won't close.
Networking2000 provides UK business IT support covering email security, Office 365 and Google Workspace protection, MFA, SPF, DKIM, DMARC, managed firewalls, and practical incident guidance. If your business operates in London or Essex, visit Networking2000 to discuss a clear, jargon-free review of the controls that protect your mailboxes and payments.