Between October 2013 and December 2023 the FBI's Internet Crime Complaint Center recorded 305,033 business email compromise incidents with global exposed losses of $55,499,915,582. The scheme reached all 50 states and 186 countries, with more than 140 countries receiving fraudulent transfers.
The Control Everyone Already Knows
The 2024 figures alone: 21,442 BEC complaints and $2.77 billion in losses, out of $16.6 billion reported to the centre across all crime types. BEC was seventh by complaint volume and second by dollars.
These are not novelty numbers. Payment redirection is the most expensive thing that happens to ordinary businesses, and most accountants have a client it has happened to.
The FBI's guidance on this is unglamorous and specific: use secondary channels or two-factor authentication to verify requests for changes in account information. Check the sending address carefully, especially on a phone. Watch for lookalike domains. Review accounts regularly.
That advice is sound and it predates any of this. An instruction arriving by one channel gets confirmed through a different one. A bank detail change emailed by a supplier gets confirmed by phoning the supplier.
Which is where the problem starts, because for most small businesses the second channel has always been a phone call, and a phone call is a voice.
What Changed, Precisely
It is worth being exact about this, because the vague version leads to useless advice.
AI did not make fraudsters more persuasive in general. What it did was remove two specific assumptions that a callback quietly relied on. The first is that a familiar voice identifies a familiar person. The second is that producing that voice takes effort a fraudster would not bother with for a mid-sized invoice.
Both of those were reasonable in 2019. Neither survives a technology that clones a voice from a short sample of publicly available audio, and most finance directors have a podcast appearance, a webinar recording or a conference video somewhere online.
So the callback still works as a control. Voice recognition inside the callback does not. Those are different things, and the second is what most procedures were actually depending on.
What a Rewritten Control Looks Like
The fix is not more suspicion. Suspicion does not scale and it makes people worse at their jobs. The fix is a rule about where the verification number comes from.
Verification has to run to a contact detail the firm already held before the request arrived, not one supplied in it. A number in the email signature, in the new invoice, or given by the caller is not a second channel. It is the same channel wearing a different hat. That single distinction catches most of these attacks regardless of how convincing the voice is, because the fraudster controls the message and not the vendor file.
Two additions worth making while the procedure is open. Any bank detail change goes to a named approver who is not the person who received the request. And the confirmation is written down, with who called, which number, and what was confirmed, because a control nobody recorded is a control nobody can prove operated.
None of this requires technology. It requires the vendor file to be current and reachable, which is where it usually falls apart.
Why This Lands on the Accountant
Clients do not have a controls function. They have a bookkeeper, an owner and whoever answers the phone, and the person who tells them how payments should be authorised is their accountant.
That advisory conversation is now genuinely different from the one that was correct two years ago, and the firms having it early are the ones clients remember.
MetaWurks helps with the part that makes verification actually happen rather than get skipped. It ingests a client's invoices, contracts, statements and correspondence and lets an accountant query the whole set in plain English, so establishing what this vendor has been paid, to which account, under which contract, is a question rather than an afternoon in a filing system. Documents ingested into the platform are not used to train models and are not exposed to other users, role based access controls decide who can open which client's records, and audit logs record who opened what and when.
Controls get skipped when they are slow. A verification step that takes four minutes gets done every time. One that takes forty gets done until the week it matters.
The FBI's advice did not become wrong. One convenient shortcut inside it did, and it is worth telling your clients which one before somebody finds out the expensive way.
Join the Conversation
If a supplier emailed one of your clients today with new bank details, what number would get called to check, and where would that number come from?