Public blockchain data only — we never ask for seed phrases, private keys or upfront fees.
No wallet data stored Runs in your browser
All guides
Business Fraud 2026-11-11 · 12 min read

Fake Invoice Scam: How to Spot the Swap and Recover the Payment

A fake invoice scam does not ask you to pay a stranger. It asks you to pay a supplier you already pay, into an account you have never used. That is why it works on careful people: the invoice is expected, the amount is plausible, and the only thing that changed is a bank detail buried in the footer. Fake invoices are built to survive a quick glance, and the email header test explains how to spot one and what recovery looks like afterwards.

Fake invoice scam: an invoice on a dark desk beside a laptop glowing with an email thread

Fake Invoice Scam. One Line Changed, Everything Else Real

Safety note: we never guarantee recovery and never ask for seed phrases, private keys, crypto payments or upfront unlocking fees. Anyone who does is running a second scam.
The short version

The Short Version: Fake Invoice Scam

  • Invoice fraud changes one field — the bank details — on an invoice you were already expecting.
  • The recall window is hours, and it depends on whether the receiving account still holds the funds.
  • Verify any change of bank details by phone, using a number from your own records, never the invoice.
  • BEC and invoice fraud together accounted for $2.77 billion in IC3-reported losses in 2024.

The short answer: one field changed

Invoice fraud is a small edit inside a familiar document. Everything about the invoice is genuine — the logo, the reference number, the amount, the contact name — except the account it asks you to pay.

What looks normalWhat was changedHow to catch it
Supplier name, logo, addressNothing—
Invoice number and amountNothing, or a small increaseCompare against the purchase order
Bank details in the footerEverythingCallback on a number from your own records
Reply-to addressOften a lookalike domainInspect the full header, not the display name

That is the whole attack. It requires no malware, no password and no technical skill beyond registering a similar domain and copying a PDF. It works because accounts-payable teams process volume, and a change of bank details is a routine event that happens for legitimate reasons too.

The one control that stops it: any change of bank details triggers a callback to a number from your own vendor records. Never a number supplied in the email or on the invoice.

What the IC3 data shows about invoice and BEC fraud

Invoice redirection is counted inside the business email compromise category, which is why the numbers are so large relative to the number of complaints.

  • The IC3 recorded 21,442 BEC complaints and $2.77 billion in losses in 2024 — an average above $129,000 per complaint.
  • BEC has cost more than $17 billion since the category was first tracked in 2015, with roughly $8.5 billion of that in 2022–2024 alone.
  • Total reported cybercrime losses reached $16.6 billion in 2024, with BEC accounting for more than 17% of the total.

The average loss is what makes this an organisational problem rather than a consumer one. A single redirected invoice can exceed a small company's annual profit, which is why the response has to involve the bank, the insurer and often law enforcement on the same day.

Fake invoice scam: the five-step invoice redirection chain and where verification breaks it
The five-step redirection chain, and the single point where a callback breaks it.

The first business day: recall, then verify

Work down this list in order. The first two steps are time-critical; the rest can follow.

1. Call your bank and request a recall

Ask for the fraud team and say: "We paid an invoice to a fraudulent beneficiary account as a result of invoice redirection fraud. We are requesting an immediate recall and a fraud hold on the receiving account."

Have the payment reference, amount, date and beneficiary details ready. If the funds are still in the receiving account, a recall is realistic. If they have moved, the bank will say so.

2. Call the real supplier on a number you already had

Not the number on the invoice. Ask whether they changed banks, and whether they know their domain or mailbox is being impersonated. They may be a victim too, and they may have other customers who have already paid.

3. Preserve the fraudulent invoice and its headers

Save the original message as an .eml, keep the PDF, and record the sending IP and reply-to domain from the header. This is the evidence your insurer and the police will want.

4. Check whether other invoices were affected

Search accounts payable for the same beneficiary details, the same reply-to domain, and any other payment made in the same window. Invoice fraud is rarely a single attempt.

5. Notify your insurer and file with the IC3

Crime or cyber policies usually require prompt notice. Then file at ic3.gov with the invoice, the payment confirmation and the header evidence.

What a recall can and cannot achieve

Funds positionRealistic outcomeWho decides
Still in the beneficiary accountRecall often succeeds, minus feesReceiving bank's fraud team
Withdrawn within hoursRecall fails; recovery needs a criminal caseReceiving bank, then law enforcement
Beneficiary is a mule accountPartial recovery if frozen before withdrawalReceiving bank, on a fraud-hold request

Speed is the only variable you control. Invoice fraudsters typically move funds within hours of receipt, which is why the bank call should happen before the internal investigation, not after it.

How the swap is delivered

  • Lookalike domain. A registered domain differs by one character, and the display name is identical to the real supplier.
  • Compromised supplier mailbox. The attacker replies inside a genuine thread, so the history and tone are real.
  • Altered PDF attachment. A genuine invoice with the bank block edited, sent from a spoofed address.
  • Phone follow-up. A caller claiming to be from the supplier "confirming" the new details, using a spoofed number.

The phone follow-up is the detail that defeats most controls, because it appears to satisfy the callback requirement. The defence is procedural: the callback must be to a number from your own records, and the person calling you is never the verification.

Inspect the header, not the name. Display names are free to set. The reply-to and the sending domain are what identify the sender.

If the payment has already left the receiving account

The objective shifts from recovery to documentation, containment and the supplier relationship.

Build the file

Original invoice, fraudulent invoice, full headers, payment confirmation, recall request and response, and a dated timeline. Your insurer will ask for exactly this.

Decide who bears the loss, with your insurer

If the supplier's mailbox was compromised, there may be a question of their liability. Do not make commitments to the supplier before your insurer has reviewed the facts.

Close the process gap that allowed it

Whatever control failed, fix it before the next payment run: a mandatory callback on bank-detail changes, dual approval above a threshold, and a vendor master file that only finance can edit.

Prevention that actually holds

  • Callback on every bank-detail change, to a number from your own vendor records, documented with who called and when.
  • Lock the vendor master file so only finance can change payment details, with a second approver.
  • Match every invoice to a purchase order and flag any amount or bank-detail variance.
  • Alert on lookalike domains for your top suppliers, and on first-time reply-to addresses in a thread.
  • Train the team on the phone follow-up — the control that most often gets bypassed.

Who ends up bearing the loss

When a redirected invoice is not recovered, the question of who absorbs it becomes a negotiation between four parties. Knowing the positions in advance keeps that negotiation short.

PartyTypical positionWhat moves them
Your businessPaid a fraudster; the supplier is still owedInsurance cover, and whether the supplier's mailbox was compromised
The supplierArgues they were not paid, unless their own mailbox was the entry pointEvidence of compromise on their side
Your insurerCovers social engineering only if the policy names itPrompt notice and a complete incident file
The receiving bankReturns funds only if they are still thereA fraud-hold request made within hours

The most common outcome is that the business bears the loss and then claims on a crime or social-engineering policy. That is why the notice deadline in your policy matters more than almost anything else you do on the day — a late notification can void cover regardless of how good the evidence is.

Check the policy wording before you need it

Two phrases decide most claims: whether "social engineering" or "fraudulent instruction" is named as a covered peril, and whether voluntary transfer of funds is excluded. Many general commercial policies exclude it; a dedicated crime policy usually includes it. Read the exclusion list now, not after an incident.

Why careful people fall for it

Because the invoice is not the attack surface — the process is. Accounts payable is designed to pay invoices, and a change of bank details is a legitimate event that happens when a supplier switches banks. A control that blocks all changes blocks real business; a control that verifies changes costs one phone call.

That is the whole lesson. Invoice fraud is not defeated by suspicion of every invoice. It is defeated by one rule applied without exception: bank details are verified by phone, on a number you already had, before any payment leaves.

Questions people ask about fake invoice scam

What is a fake invoice scam?

It is invoice redirection fraud: a genuine-looking invoice from a supplier you already pay, with the bank details changed to an account the fraudster controls. The amount and reference are usually correct, which is why it passes a casual review.

Can a fake invoice payment be recalled?

Only while the funds remain in the receiving account, which can be a matter of hours. Call your bank's fraud team immediately and ask for a recall and a fraud hold on the beneficiary account. Once withdrawn, recovery requires a criminal case.

How do I verify a supplier's change of bank details?

Call a number from your own vendor records — never a number in the email or on the invoice. Document who you spoke to and when. If the supplier calls you to confirm, that call is not verification.

Is invoice fraud the same as business email compromise?

It is usually a form of it. Invoice fraud can be delivered by a lookalike domain without any mailbox compromise, but it is counted within the BEC category because the mechanism and the loss profile are the same.

How much is lost to invoice and BEC fraud each year?

The IC3 recorded 21,442 BEC complaints and $2.77 billion in reported losses in 2024, an average above $129,000 per complaint. BEC has cost more than $17 billion since 2015.

What should I do if I think my supplier's email was hacked?

Call them on a number you already had and tell them. They may be a victim of mailbox takeover, and other customers may have already paid the fraudster. Then preserve the message headers and report to the IC3.

Next step

Capture the headers before the mailbox is cleaned

The reply-to domain and sending IP are what prove redirection — and they disappear when the message is deleted.

Related guides

Was this useful?

Information only. We never promise recovery.

Editorial note: this page is general information, not legal or financial advice. Figures are cited from the agencies named above and were accurate at the review date. Recovery outcomes vary and no result is guaranteed.