Free tier

← All guides · Freelancers & business

Invoice fraud and payment safety: what structured invoicing changes — and what it doesn't

By the Ingenious AI team · Published 14 November 2026 · Reviewed 14 November 2026

Convert an invoice free

Put this guide into practice now: convert one invoice free — validated UBL 2.1 XML plus a Factur-X PDF, with the acceptance checker for your client’s country. See pricing for bulk conversion, country rule packs and monitored clients.

Short answer

Structured invoicing removes fraud's favourite conditions: a Peppol invoice travels under a verified business identity (KYC-checked at access point registration) to a registered address, with a delivery confirmation — not as an anonymous PDF attachment anyone can fabricate. Identifiers recorded exactly and verified at onboarding defeat casual impersonation — provided your process also treats bank-detail changes as events to verify through a known contact, never as instructions inside a message.

What is the fraud surface of an invoice?

An invoice asks for money, so it attracts forgery: fabricated invoices from lookalike suppliers, genuine invoices intercepted and altered (above all, bank details), and payment-diversion messages impersonating finance teams. The structured model's defences are architectural — Peppol participants are verified businesses (the access point runs an identity check, KYC) sending under registered Peppol IDs, and sends carry confirmations — while the residual risks are procedural and belong to the parties' own verification habits.

Why PDFs are fraud's favourite format

A PDF invoice is trivially forgeable: it is a picture with a bank account number in it. The classic attack needs no intrusion — a convincing invoice from a lookalike domain, or a real invoice intercepted in a compromised mailbox with the account details swapped, and a busy payables clerk pays the wrong account in good faith. The document carries no proof of origin, so diligence means telephoning suppliers about paperwork — diligence that busy processes skip precisely when volume is high.

Notice what the attack exploits: not weak passwords but weak provenance. The invoice cannot demonstrate who sent it, and the payment instruction travels inside the same unverifiable artefact as the demand. Any system that separates identity from documents this completely will be farmed by fraudsters for as long as it remains the norm — which is one more reason the norm is being legislated away.

What the structured model changes

On Peppol, the sender is a verified business: the access point's KYC stands behind the Peppol ID, the document travels network-to-network under that identity, and the receiver's system books it against the registered participant — not against an email's display name. A fabricated 'invoice' cannot join the network without an identity, and an intercepted document cannot be quietly re-addressed, because the routing and the confirmation are properties of the network, not of an attachment.

Platform models add their own version: the invoice exists inside the national platform's perimeter, issued and retrieved through authenticated channels, so the document a buyer pays against is the document the platform holds. In both architectures, provenance stops being a matter of eyeballing letterheads. The fraudster's cheapest weapon — the plausible PDF — depreciates to scrap.

What it does not change: bank details and humans

Structured invoicing does not put bank details beyond manipulation — payment instructions still live in contracts, emails and master data, and the 'our account has changed' message still arrives, now sometimes dressed as an update to a structured process. The defence is procedural and absolute: bank details change only through a verified channel (a call to the number you already hold, never the number in the message requesting the change), recorded as an event, confirmed before the next payment. No invoice, however structured, should be able to redirect money by itself.

Humans remain the other constant: approvals can be socially engineered, and a verified invoice for fictitious work is still fictitious — validation proves consistency, not that the supply happened. Structured data narrows fraud's territory to the genuinely hard cases: invented substance and compromised processes. That is a smaller, more defensible perimeter — defended by ordinary controls (approval against orders and delivered work) rather than by document forensics.

Supplier-side hygiene that compounds

Your own contribution to the ecosystem's safety is consistency: the same identifiers, the same Peppol ID, the same bank details, the same invoice format, month after month — a pattern your clients' systems and people can recognise, against which an impostor's deviation stands out. Announce your own changes (a new account, a new entity) through multiple channels in advance, so clients can apply their verification rituals while nothing is urgent.

File delivery confirmations and keep your records exact: when a client queries a payment ('we paid invoice X to the account on it'), your archive set — the document as sent, its confirmation — answers from evidence. Suppliers with provable paperwork get the benefit of every doubt, and benefit-of-doubt, aggregated across a client base, is a real financial asset that fraud attempts spend down when they succeed against anyone.

A short doctrine for both sides of the invoice

Senders: be boringly consistent, verify your clients' identities at onboarding, and never ask for payment redirection inside a lone message. Receivers: book from structured channels where they exist, verify bank-detail changes out-of-band every time, and treat PDF-only invoices from new suppliers as a prompt for a verification call, not as paperwork. Both: keep confirmations and records as if a dispute were scheduled — because across a business's life, one always is.

The mandate era will not end invoice fraud; nothing ends a crime that follows money. It ends the era in which the crime was easy, anonymous and scalable — in which the invoice itself could not testify to its own origin. A document that can prove where it came from is a small thing. Multiplied by every invoice in Europe, it is the difference between a fraud epidemic and a fraud nuisance.

Payment-safety discipline in 5 steps

  1. Treat every bank-detail change — yours or a supplier's — as an event to verify out-of-band through a previously known contact. Never act on details inside the requesting message.
  2. Prefer structured channels (Peppol, platforms) where identity is verified and delivery is confirmed; file the confirmations.
  3. Keep your own invoicing pattern rigorously consistent: same identifiers, Peppol ID, format and details — deviations should be yours to announce, in advance, through several channels.
  4. Record identifiers and client details exactly at onboarding; mismatched identities are where both errors and fraud hide.
  5. Archive the complete set per invoice so any payment query is answered from evidence, not from memory.

Worked example: the change-of-bank email that failed

A client's payables team receives an urgent email, apparently from a regular supplier, announcing new bank details 'effective immediately — please update before paying invoice 2026-118'. The amount is real (EUR 7,260.00) because the attacker had seen the genuine invoice in a compromised thread. The payables clerk follows the standing rule instead of the email's urgency: she calls the supplier's finance contact at the number held since onboarding.

The supplier knows nothing about new details; the email's domain differs from theirs by one letter. Invoice 2026-118 — which had itself arrived as a Peppol document under the supplier's verified ID, matching the record exactly — is paid to the original account. The fraud's total yield was the cost of one phone call, because two habits held: the invoice's provenance was never in question, and bank details were never going to move on an email's say-so.

Frequently asked questions

Does Peppol eliminate invoice fraud?

No — it eliminates the anonymous, unverifiable document. Senders are KYC-verified businesses under registered IDs, with delivery confirmations. Fraud retreats to harder ground: false substance and social engineering, which process controls still govern.

Can a structured invoice's details be altered in transit?

On network and platform channels the document travels between verified participants inside the channel's perimeter — a different risk class from an emailed attachment. Your master-data discipline (out-of-band verification of changes) covers the rest.

What is the single most valuable anti-fraud habit?

Out-of-band verification of bank-detail changes, every time, without exception for urgency. It defeats the highest-yield invoice fraud pattern at the cost of a phone call.

Does validation check that an invoice is genuine?

Validation checks consistency — rules, identifiers, totals. Genuineness comes from the channel (verified identity, confirmations) and from your approval against orders and delivered work. The layers are complementary, not interchangeable.

Should I stop accepting PDF invoices from suppliers?

Treat PDF-only invoices from new or changing suppliers as a verification prompt. Where a structured channel exists between you, prefer it — provenance is the point.

Keep going

Run the free tool this guide is about: convert an invoice · acceptance checker · pricing · about EInvoice Translator · all guides

Related guides

← Back