The Invoice That Wasn't: Business Email Compromise and Payment Fraud in Service Businesses
The emai…
Searched the web, read a page
Searched the web, read a page
The email looks right. The invoice looks right. The voice on the phone sounds exactly like your partner. And the money still goes to a criminal. Here is how service businesses can make that much harder to pull off. Picture a typical service business: a staffing agency, a property manager, an IT shop, a marketing firm. Tuesday, 3:40 p.m. Your bookkeeper gets an email from a subcontractor you've paid a dozen times. Same name, same signature block, same thread as last month's job. The note is brief: they've switched banks, here are the new wire details, and could you send this one today because payroll is tight. Nothing about it feels strange. That's the problem. The scenario is illustrative, but the pattern is real. The FBI describes business email compromise in nearly the same terms: a familiar vendor sends an invoice with updated payment details, the message is fake, and the money goes to criminals. Service businesses are exposed in a particular way. You pay lots of subcontractors, freelancers, and suppliers. Many invoices are custom. Deadlines are real, and people are used to paying quickly to keep jobs moving. Every one of those habits is something an attacker can use. According to the FBI Internet Crime Complaint Center's 2025 annual report, business email compromise produced 24,768 complaints and about $3.05 billion in reported losses in 2025, up from $2.77 billion in 2024. Only investment fraud caused more reported losses. The same report shows total reported cybercrime losses topping $20.8 billion, a 26% increase over the prior year. For the first time it also tracked AI-related fraud on its own: more than 22,000 complaints and close to $900 million in losses. These are reported cases only. Plenty of businesses never file a complaint, so the actual losses are higher. Criminals often register an address one letter off from the real one. The FBI's example is john.kelly versus john.kelley. Harder to catch is a real account taken over. Through spearphishing or malware, an attacker can sit inside a legitimate mailbox, watch the billing conversations, and send a payment request at the moment it will look most normal. Nobody misspelled anything. The message really came from your vendor's account. The FTC's guide for small businesses warns about phony invoices built to look like charges for products or services you ordered. Scammers are counting on whoever pays the bills to assume the invoice is legitimate. In service businesses, where every job is a little different, a made-up line item is easy to miss. A callback used to settle the question. It doesn't anymore. The FTC has warned that a scammer can clone someone's voice from a short audio clip, such as one taken from content posted online. The agency also notes that a call sounding like your boss asking for account numbers makes people more likely to act, which is exactly why scammers use cloned voices. Owners who appear on podcasts, webinars, or social video have handed attackers plenty of sample audio. The takeaway: a voice now tells you about as much as a display name. Verify the request, not the voice. A one-time training won't solve this. A handful of written rules that people follow even when they're busy will. These are the decisions worth making this week. This is the most important rule. The FBI advises confirming any change in account numbers or payment procedures directly with the person making the request, in person or by phone. The FTC adds that you should never use the contact details in a suspicious message. Call a number already in your vendor file, from before the request came in. Do not use the number in the email signature, and do not reply to the thread. The FTC recommends clear approval procedures, set up so that an unexpected call, email, or invoice alone cannot trigger a major payment. In practice, one person updates vendor banking details and a different person approves the first payment to those new details. Set a dollar threshold above which a second approver is always required, whatever the deadline. The FTC and the FBI both identify pressure to act fast as a core warning sign. Make it explicit policy that anyone handling money can pause a payment to verify it, and that nobody will be blamed for the delay. Tell your team you will never be upset that someone called to confirm a wire. The FTC's main advice on cloned-voice calls is to ignore how convincing the voice is and confirm through a channel you already trust. Inside a business, that can mean a private phrase agreed in person and never put in email, required for any spoken request to move money or change payment details. If the caller can't produce it, hang up and call back on a known number. Many BEC cases begin with a stolen password. CISA recommends requiring multifactor authentication on email, file storage, and remote access, beginning with admin accounts and the people who handle sensitive data. CISA says any MFA beats none, but text-message and email codes can be phished, and it urges organizations to move toward phishing-resistant MFA such as FIDO security keys, noting that most hosted email systems already support it. Its small business guidance adds a practical point: enforce MFA with technical controls instead of trusting that everyone enrolled. Criminals also pretend to be you when contacting your clients. The FTC recommends using an email provider that offers authentication so receiving servers can confirm your messages are genuine. CISA's joint phishing guidance with the NSA, FBI, and MS-ISAC covers SPF, DKIM, and DMARC checks that flag spoofed senders. Ask your IT provider whether these are set up and enforced, not just published. Generic phishing videos only go so far. CISA advises making sure staff know exactly whom to tell, and how, when they spot a suspicious email. Go through a real example with the people who pay bills: a fake bank change notice, a spoofed vendor domain, a "call me right now" voicemail. Then rehearse what the verification call sounds like. Speed affects whether funds can be recovered. Do these in order: None of this requires new software. It requires deciding ahead of time, while things are calm, so nobody has to improvise under pressure at 3:40 on a Tuesday. Stop any pending payments tied to the suspicious request and call your bank right away, asking it to contact the receiving institution, as the FBI recommends. File a complaint at ic3.gov, reset credentials on the affected accounts, and check those mailboxes for rules that forward or delete messages. Base training on your actual payment process instead of generic examples. Show finance staff what a fake bank-change request looks like, practice the callback, and make sure everyone knows how to report something suspicious. CISA and the FTC both offer free small business materials you can adapt. Watch for small changes in sender addresses or domains, last-minute changes to banking details, pressure to pay immediately, requests to keep the payment quiet, and invoices for work nobody remembers ordering. The FTC also flags demands for wire transfers, cryptocurrency, or gift cards as common scam tactics. Yes. The FTC warns that a short audio clip can be enough to clone a voice. The defense is procedural: no money moves on a voice alone, and every spoken request gets verified through a callback to a known number or a pre-agreed phrase.The Invoice That Wasn't: Business Email Compromise and Payment Fraud in Service Businesses
A Tuesday afternoon, an ordinary invoice
How big the problem is
The three ways the money gets redirected
1. The look-alike or hijacked inbox
2. The fake or altered invoice
3. The voice that sounds exactly right
The decisions that actually stop it
Decision 1: Bank detail changes are never accepted through the channel that requested them
Decision 2: No single person can both change a payee and release a payment
Decision 3: Urgency and secrecy are reasons to slow down
Decision 4: Agree on verification phrases for high-risk requests
Decision 5: Lock down the inboxes that touch money
Decision 6: Protect your own domain from spoofing
Decision 7: Train for your own workflows
If money already went out: the first hour matters
A one-page payment policy you can adopt today
Frequently Asked Questions
What should I do if I suspect BEC in my organization?
How can I educate my employees about payment fraud?
Are there any specific signs of invoice fraud to look out for?
Can a voice cloning scam really fool my team?
Visuals

