Back to blog
Industry NewsOctober 11, 20265 min read

AI invoice fraud is rising in the EU: what small businesses must do now

Europol's latest data shows AI-generated invoice fraud targeting EU SMBs is accelerating. Here is what the threat looks like and how to harden your accounts payable verification before it costs you.

By ZenPay Team

Share
AI invoice fraud is rising in the EU: what small businesses must do now
Photo by Dan Nelson on Unsplash

Your accounts payable process was built to handle invoices from suppliers you know. It was not built for invoices that look identical to those suppliers but were generated by a large language model at 3am in another country.

Europol's 2024 Internet Organised Crime Threat Assessment flagged AI-assisted business email compromise (BEC) and synthetic invoice fraud as among the fastest-growing financial crime vectors targeting EU small and medium businesses. The numbers are pointed: reported BEC losses across the EU rose roughly 35% year-on-year in 2023, with SMBs accounting for a disproportionate share of victims. Large enterprises have fraud teams. You have a bookkeeper and a Tuesday afternoon.

What AI has changed about invoice fraud

Classic invoice fraud was detectable. A spoofed PDF had the wrong font, a misaligned logo, or an obviously fake VAT number. AI-generated fraudulent invoices now clear those bars easily.

The three techniques doing the most damage

Synthetic invoice generation uses publicly available invoice templates and LLM tooling to produce documents with accurate branding, correct IBAN formats, plausible invoice numbers, and matching VAT IDs scraped from the EU VIES database. The invoice looks like it came from your packaging supplier in Łódź. It didn't.

Voice-cloning confirmation calls follow the fraudulent invoice within 24 hours. A synthetic voice that sounds like your regular contact confirms the "updated bank details." This two-step attack is what elevated losses so sharply: the invoice passes visual inspection, and the follow-up call neutralises the "call to confirm" control that many SMBs rely on.

Thread hijacking intercepts or spoofs an existing email thread with a legitimate supplier, inserting a fraudulent invoice mid-conversation. Your staff sees prior legitimate emails above it. Context lends credibility.

What Europol's data actually says about who gets hit

Europol's reporting is consistent on the victim profile: companies with 10 to 50 employees, stable supplier relationships (meaning predictable, recurring invoices), and accounts payable handled by one to three people without a formal approval matrix.

That profile fits a lot of B2B owner-operators in manufacturing, professional services, and supplies distribution across Germany, France, the Netherlands, Poland, and Spain. If you run a 15-person business sending and receiving recurring invoices every month, you are the target demographic.

The median fraudulent invoice value in reported EU BEC cases sits between €8,000 and €22,000. High enough to matter. Low enough that it might not trigger a board-level review before the payment clears.

Why recurring supplier relationships are the attack surface

Fraudsters specifically target recurring invoice patterns because your team stops scrutinising them. If Supplier X sends a €4,200 invoice on the 28th of every month, and one arrives on the 26th for €4,350 with a note about "updated payment details," the delta is small enough to feel routine. That is the exploit.

The verification controls that actually work in 2025

No single control stops this. You need layered verification, and you need it documented so it survives staff turnover.

Supplier bank detail change protocol. Any request to update payment details, whether by email, PDF, or phone, requires a callback to a number stored in your system before the change was requested. Not the number in the email. Not the number on the new invoice.

Invoice cross-referencing against your own outgoing data. If you issue invoices with your own invoice numbers in sequence, you can spot anomalies on the receiving side too. A supplier invoice that references a purchase order number you don't recognise, or a VAT number that doesn't match your stored record, is a red flag.

EU VIES validation at onboarding, not just at first invoice. Spot-check existing supplier VAT numbers quarterly. Fraudsters sometimes register legitimate-looking VAT IDs in smaller EU member states and use them for a short window before the number is flagged.

Two-person approval for any invoice above a threshold. Pick a number: €3,000, €5,000. Any payment above it requires a second set of eyes. Document the threshold in your internal controls.

How most AP processes handle invoice verification

  • Invoices are stored as PDFs on local drives or email, with no audit trail of when they were sent or opened.
  • Supplier bank detail changes arrive by email with no cross-check against stored records.
  • Payment reminders are sent manually, creating gaps where fraudulent "re-send" invoices slip in.
  • No visibility into partial payments or reference mismatches until month-end reconciliation.

How ZenPay helps on the outbound side

  • Every invoice gets a unique shareable link, so your clients always open the canonical version, not a spoofed PDF.
  • Auto-reminders fire in your name on a set schedule, so clients never receive an unexpected "resend" from an unknown address.
  • Per-invoice payment tracking with reference matching flags partial payments and unmatched transfers immediately.
  • Multi-currency wallets aggregate receipts per currency, making an unexpected inbound amount easy to spot against expected totals.

Note: ZenPay secures your outbound invoicing. The inbound AP verification controls above are your internal responsibility. Both sides of the ledger matter.

What to do this week, not this quarter

Europol's recommendation to member state authorities is to push SMB fraud awareness through trade associations and chambers of commerce. That is a slow channel. The practical steps you can take before Friday:

  1. Pull your top 10 suppliers by monthly invoice value. Confirm their IBAN and VAT number against what is in VIES and your bank's stored beneficiaries.
  2. Write a one-paragraph supplier bank detail change policy. Email it to whoever approves payments. It doesn't have to be long. It has to exist.
  3. Check whether your accounting or invoicing tools give you a timestamped audit trail of sent invoices. If you cannot see when an invoice was sent and to which email address, you have a gap.
  4. Set a two-person approval rule for any payment above your chosen threshold, starting Monday.

The broader compliance angle: e-invoicing mandates help, but slowly

Several EU member states are accelerating structured e-invoicing mandates partly as an anti-fraud measure. Germany's B2B e-invoicing rollout (phased from 2025), France's Chorus Pro expansion, and Poland's KSeF system all create a government-visible invoice record that is far harder to spoof than a PDF. When an invoice must flow through a government clearance platform, a fraudulent PDF that bypasses it stands out structurally.

But most of these mandates are phased, and smaller businesses are often in the later cohorts. In the meantime, the gap between "mandate announced" and "mandate enforced for your size of company" is exactly the window fraudsters are exploiting.

Structured e-invoicing is coming. Until it covers your supplier relationships, your manual verification controls are the only thing standing between your bank account and a convincing PDF.

The underlying dynamic here is simple: AI lowered the cost of producing a convincing fraudulent invoice to near zero. Your accounts payable process was calibrated for a world where forgery required effort. Recalibrate it for a world where it doesn't.