
It's Thursday afternoon.
A small business accounting manager receives an email from a familiar vendor.
The company has worked with this vendor for years.
The message references an existing invoice and explains that the vendor recently changed banks.
There's a polite request to update the payment details before processing the next transfer.
Everything looks normal.
The vendor's name is familiar.
The amount matches an expected payment.
The email even appears to be part of an existing conversation.
The accounting manager prepares to update the bank information.
Then something makes them hesitate.
Why would a longtime vendor change payment instructions without mentioning it through any other channel?
Instead of processing the request, the manager calls the vendor using a phone number already saved in the company's records.
The vendor has no idea what they're talking about.
The email was fraudulent.
Sometimes, one of the most important cybersecurity decisions a business makes is choosing to verify something that appears completely routine.
This is the challenge posed by business email compromise, a type of fraud that can target companies of virtually any size.
Business email compromise, often called BEC, is a form of fraud in which criminals impersonate trusted business contacts or misuse compromised communications to request money, information, or other unauthorized actions.
The attacker may pretend to be:
Some attacks involve fake email addresses that closely resemble legitimate ones.
Others involve access to an actual compromised account.
That distinction matters.
An email may look convincing because it comes from a familiar conversation or seemingly legitimate account, not because the recipient failed to notice an obvious spelling mistake.
The FBI's Business Email Compromise guidance describes scenarios involving fraudulent invoices, executive impersonation, and altered payment instructions.
Businesses receive invoices every day.
Accounting teams need to process payments, respond to vendors, and support normal operations.
The process is repetitive, which can make a routine-looking request easier to accept.
Imagine a growing company that works with several suppliers.
The accounting team receives an invoice from a vendor it knows well.
The amount is expected.
The project is real.
And the payment deadline is approaching.
The only unusual detail is a request to send the money to a different bank account.
If the company treats this as a normal administrative change, the fraud may succeed without anyone clicking a malicious link or downloading a suspicious attachment.
Not every cyber-related financial scam begins with a technical alert. Some begin with an ordinary business request that hasn't been independently verified.
A vendor suddenly requests a new bank account, payment destination, or payment method.
The change may be legitimate.
However, it should be confirmed through an independent, trusted communication channel before payment details are updated.
A message claims that payment must be completed immediately to avoid a penalty, service interruption, or other consequence.
Urgency alone doesn't prove fraud, but pressure to bypass normal verification procedures is a warning sign.
An email asks an employee to skip a required approval because a manager is traveling, unavailable, or handling something confidential.
Organizations should be particularly cautious when a request attempts to override normal financial controls.
An email address may closely resemble a legitimate address while containing a small difference.
However, a correct-looking address doesn't guarantee legitimacy because genuine accounts can also be compromised.
A familiar contact may suddenly request secrecy, insist on using a different communication channel, or ask for sensitive information unrelated to the normal business relationship.
The correct response is to verify the request rather than assume the sender is trustworthy.
One of the most effective practical habits is verifying changes to vendor payment instructions through an independent channel.
Here's what that can look like.
An accounting employee receives an email requesting a bank account change.
They do not use the phone number included in that email.
Instead, they retrieve the vendor's previously verified contact information from the company's established records.
They call the vendor and confirm whether the requested change is authentic.
The organization documents the verification and follows its normal approval procedures before updating payment information.
The goal is to prevent a fraudulent email conversation from becoming the only evidence used to authorize a financial transaction.
If email is the channel that may be compromised, email alone should not be the method used to verify the request.
The FBI recommends independently verifying payment and purchase requests, particularly when account numbers or payment procedures change.
Protecting financial workflows requires more than installing an email filtering tool.
Technical safeguards are important, but business processes also need attention.
Enable appropriate multifactor authentication, maintain secure account configurations, and review suspicious sign-in activity.
Organizations should use phishing-resistant authentication methods where appropriate and supported.
Define who can approve payments, create vendors, and change existing payment instructions.
For higher-risk transactions, consider requiring an additional authorized employee to review the request.
Where staffing permits, avoid allowing one person to receive a payment change request, update banking details, and approve the resulting transfer without another review.
Smaller businesses may need alternative controls that fit their team size.
Awareness training should include realistic situations involving invoices, vendors, executives, and payment changes.
Employees should know that a familiar-looking email isn't always reliable evidence.
Someone who notices an unusual payment request should know whom to contact.
The organization should encourage reporting and verification instead of rewarding employees solely for processing requests quickly.
If a business believes money was transferred because of a fraudulent request, prompt action is important.
The organization should immediately contact its financial institution, explain the suspected fraud, and ask about available recovery or recall procedures.
It should also notify its internal security or IT response team.
If an email account may have been compromised, the organization should investigate and secure the affected accounts using its established incident response process.
For U.S. incidents, the FBI recommends reporting business email compromise to the Internet Crime Complaint Center.
Relevant transaction details, emails, records, and communications should be preserved for the investigation.
Recovery cannot be guaranteed, so employees should avoid delaying the initial report while waiting to collect every detail.
For a related guide, see Clicked a Phishing Link at Work? What Your Business Should Do Next.
Before approving a change to vendor banking information, ask:
These questions are designed to create a repeatable process that doesn't depend entirely on one employee noticing something unusual.
An important lesson from business email compromise is that cybersecurity isn't limited to software and devices.
An IT team may manage account protection and investigate suspicious activity.
Accounting may manage vendor information and financial transactions.
Leadership may define approval limits and risk tolerances.
Each department handles a different part of the same business risk.
If the teams don't coordinate, gaps can develop between otherwise reasonable procedures.
For example, email security tools might identify some suspicious messages, but accounting still needs a reliable process for verifying changes to payment details.
Likewise, a financial approval process may be well documented, but account compromise could expose sensitive communications unless appropriate security controls are maintained.
The strongest approach combines technical protection with clear operational responsibilities.
At V.I. Experts, we help small and medium-sized businesses strengthen their technology environments through proactive cybersecurity, monitoring, endpoint protection, and expert IT support.
Our Security IT for SMB services focus on protecting the systems and business information organizations depend on.
For a broader starting point, explore our article Small Business IT Security: The First 30 Days That Can Strengthen Your Defenses.
Phishing broadly involves deceptive messages intended to trick recipients into unsafe actions. Business email compromise often involves impersonating trusted business contacts or using compromised accounts to obtain money, sensitive information, or unauthorized approvals. The two can overlap.
Yes. Some incidents involve fraudulent requests for payment changes or other actions without requiring the recipient to open a malicious attachment.
No. MFA helps protect accounts, but fraudulent messages can also rely on impersonation, compromised sessions, social engineering, or other techniques. Independent payment verification remains important.
Contact the vendor through a previously established and trusted communication method, confirm the requested change with an authorized representative, and follow documented internal approval procedures.
Contact its financial institution immediately, notify relevant internal teams, preserve the available evidence, investigate potentially compromised accounts, and report the incident to the appropriate authorities.
Business email compromise can exploit normal business routines.
Employees receive invoices.
Managers approve payments.
Suppliers update their information.
None of these activities is unusual.
But when a request involves money, sensitive information, or an unexpected change, verification deserves priority over speed.
A simple phone call through a trusted channel can prevent a suspicious message from becoming an expensive business mistake.
Because sometimes, protecting your business begins with the confidence to say: "Before we proceed, let's verify this."