Examples

Fake invoice examples and red flags

Training improves when AP teams see realistic patterns. Fake invoice scams usually combine a normal business pretext with one or two pressure signals.

Use these examples for awareness training, then run suspicious requests through the Invoice Scam Check before payment.

Check your invoice Read FAQ

Quick answer

Realistic is the danger

The best fake invoice emails look boring. The danger is in changed payment instructions, urgency, domain mismatch, and missing verification.

Free AP Fraud SOP Kit

Turn this check into an AP policy

Get the vendor bank-change policy, callback script, approval note, incident checklist, and hold triggers for your finance team.

Get the SOP kit Future paid: saved checks, audit log, PDF reports, team templates - $19/mo teaser.

Example 1: vendor bank change

A known supplier claims their accounting team changed banks this week.

  • Red flag: new bank details by email.
  • Red flag: same-day payment pressure.
  • Control: callback on known vendor number and dual approval.

Example 2: reply-to mismatch

The From address appears corporate, but Reply-To points to a free-mail address.

  • Red flag: replies go outside the vendor domain.
  • Red flag: attacker controls the conversation after AP replies.
  • Control: start a fresh verification through known records.

Example 3: executive pressure

A CFO or CEO asks AP to process a confidential wire while unavailable.

  • Red flag: secrecy plus urgency.
  • Red flag: bypass of normal approval workflow.
  • Control: in-person or phone verification and dual approval.

Fake Invoice Examples FAQ

Do fake invoices always use bad grammar?

No. Many are polished, targeted, and based on real vendor workflows.

Can an invoice be fake if the vendor is real?

Yes. Attackers can impersonate or compromise real vendors and redirect payment instructions.