Deepfake invoice scams are hitting more companies, fast. In these attacks, criminals pair convincing fake invoices with cloned voices or video of executives or vendors to rush payments. The FBI’s Internet Crime Complaint Center has documented voice cloning used in business email compromise schemes, and it warns that AI makes fraud harder to spot. That means every small business needs a clear, simple plan before the next “urgent” invoice or call arrives. (ic3.gov)
What a deepfake invoice scam looks like
Criminals blend old tricks with new tech. Common patterns include:
- An email with a realistic invoice and a follow‑up call from a “CFO” or “vendor rep.” The voice sounds right because it is cloned from public audio. The caller pushes you to wire funds now to “avoid penalties.” The FBI has described cases where voice deepfakes and spoofed video were used to direct employees to initiate transfers. (fbi.gov)
- A surprise video meeting where a still image or low‑quality video stands in for your executive, paired with a “my audio is glitchy” excuse and payment instructions in chat. (fbi.gov)
- An email claiming a supplier changed banks. The message includes real names, logos and past email threads stolen from a hacked mailbox. A “confirmation” phone call follows, using a cloned voice to seal the deal. CISA and partner agencies warn that synthetic media makes social engineering more convincing across voice, video and images. (cisa.gov)
Why these scams work
They exploit authority, urgency and routine. Invoices look normal. The voice sounds familiar. The request matches a real project. And our default is to help teammates and vendors move work forward. Attackers also time messages late in the day or before holidays, when review steps get skipped. The FTC repeatedly flags fake invoices and business impostor scams as a top threat to small firms. (ftc.gov)
Deepfake invoice scams: a layered defense that actually works
You don’t need a lab to fight synthetic media. You need friction—simple, documented steps that make it hard to move money without verification.
1) Lock down payment changes
- Always verify bank‑detail changes using a trusted, independently sourced phone number. Never use numbers from the email or invoice. Require a second person to approve the change. CISA advises using out‑of‑band communications to avoid tipping attackers and to verify sensitive actions. (cisa.gov)
- Set daily dollar limits and dual approval for wires and ACH. Add a 24‑hour hold before first payments to new or changed accounts so you can catch errors.
- Ask your bank about tools like Positive Pay and ACH debit blocks or filters. These add bank‑side friction that complements your internal checks.
2) Harden email and identity
- Turn on multifactor authentication for email, finance apps and remote access. CISA recommends phishing‑resistant MFA wherever possible. (cisa.gov)
- Implement SPF, DKIM and DMARC with a “reject” policy to block spoofed messages. CISA’s baseline guidance calls out DMARC as a key BEC countermeasure. (cisa.gov)
- Review forwarding rules and sign‑in alerts on finance mailboxes. Attackers often add silent forwarding to watch your vendor conversations.
3) Train, then rehearse
- Teach your team the three red flags: surprise urgency, secrecy, and changes to payment details. The FTC’s small‑business materials are a solid, plain‑language foundation. (ftc.gov)
- Run quick tabletop drills. Simulate a vendor‑bank‑change email and a “voice‑verified” follow‑up call. Practice saying, “We’ll call you back on a number we have on file.” CISA publishes scenarios and playbooks you can adapt for a one‑hour exercise. (cisa.gov)
4) Tighten vendor onboarding and maintenance
- Standardize onboarding. Collect bank details through a secure portal, not by email. Validate the EIN and a tax document that matches the bank account name.
- Keep a verified vendor contact card with at least two known, independently sourced phone numbers. Use it for every change request.
- Schedule periodic callbacks to your top suppliers to reconfirm remit details and contacts.
5) Expect AI in fraud—and plan for it
- Assume you will encounter cloned voices and believable fake videos. The FBI’s annual reporting documents AI‑related complaints and notes voice cloning and generative text as enablers in BEC and other scams. Don’t rely on “does it sound like them?” as a control. Require out‑of‑band callbacks and dual approval. (ic3.gov)
- Equip staff with a simple script for awkward moments: “Company policy requires me to verify this on a known number and get a second approval. I’ll call you right back.”
What to do if you get hit—or almost do
- Call your bank immediately. Ask for a recall or hold on the transfer. Speed matters.
- Report to the FBI at IC3.gov and, if money moved, contact your local FBI field office. Fast reporting improves recovery odds. (ic3.gov)
- Preserve evidence: emails with full headers, chat logs, call records, meeting invites, and the invoice file. Save originals and copies. Do not delete or forward from the compromised mailbox.
- Notify affected vendors or customers through trusted channels. If attackers were in email, they may have tampered with active threads.
- Loop in your insurer and legal counsel, if applicable, and reset credentials with MFA on any accounts that touched the incident.
Quick checklist you can copy
- Document a two‑person approval rule for wires and ACH over a set amount.
- Require out‑of‑band callbacks on vendor bank‑detail changes and high‑risk payments. Use numbers you already trust. (cisa.gov)
- Turn on MFA for email and finance systems; require phishing‑resistant methods for admins. (cisa.gov)
- Enable SPF, DKIM and DMARC at “reject.” Monitor DMARC reports monthly. (cisa.gov)
- Lock finance mailboxes: disable auto‑forwarding, review sign‑in locations weekly, and archive logs.
- Centralize vendor onboarding in a secure portal; avoid email for sensitive forms.
- Run a 60‑minute tabletop exercise each quarter. Rotate scenarios: vendor change, urgent “CEO” wire, refund scam. (cisa.gov)
- Post the “If a payment request feels urgent, pause and verify” script by every AP workstation.
Set expectations with your team and partners
Tell employees and vendors what you will never do: you will never change bank details by email alone; you will never demand secrecy on a payment; you will always call back on a known number for sensitive requests. Publishing these rules helps honest people—and it frustrates impostors. The FTC’s guidance on business impostor scams pairs well with an internal “payment policy” one‑pager you can share with suppliers. (consumer.ftc.gov)
Bottom line
Deepfake invoice scams succeed when process is vague and pressure is high. They fail when verification is automatic and quick. Put simple speed bumps—callbacks, dual approval, and strong email security—between every invoice and your cash. Then practice. The tools are free, the steps are short, and they work.
Sources
- FBI IC3 Annual Report. (ic3.gov)
- FBI Congressional Report on BEC and Real Estate Wire Fraud. (fbi.gov)
- NSA, FBI and CISA: Contextualizing Deepfake Threats to Organizations. (cisa.gov)
- CISA Cybersecurity Performance Goals: Email Security and MFA. (cisa.gov)
- FTC: Scams and Your Small Business. (ftc.gov)
- FTC Consumer Advice: Run a small business? Pay your bills, not scammers. (consumer.ftc.gov)
Featured image: Original AI-generated editorial illustration.
More From This Category
View all Business →
Windward Bio jumps in Nasdaq debut after $175M IPO

Unit prices make a smaller price tag easier to judge

Siemens Energy triples dividend, adds up to €9bn buyback after record year

Profit is not the bank balance: the timing problem behind healthy-looking sales

Thomson Reuters raises 2026 organic revenue outlook after 10% Q3 sales rise

AMD tops Q3, lifts Q4 view as data‑center sales soar 97%
Other Articles You May Like

USPS Hold Mail setup: Pause Home Delivery While You’re Away

Dolly Parton, 1946–2026: the songs, generosity and sparkle that changed the world

Free Weekly Credit Reports Help Catch Fraud—Here’s How to Use Them

iPhone RCS messaging delivers better Android chats—here’s how to enable it

Desalination has a treatment train, not just a salt-removal step


