Fake invoices and urgent payments

Why this page exists

• A fake invoice can look very convincing; the IBAN, the channel and the urgency are the points to check.

Situations often seen

• unpaid invoice suspension
• changed IBAN invoice
• Telenet urgent invoice
• Doccle suspicious invoice

What the fraudster is trying to get

• In cases linked to the invoice payment request, the aim is generally to trigger action before you have time to check: click, pay, share a code or open access to an account.
• Urgency, fear of losing something and imitation of a well-known organisation are used to reduce your vigilance. None of these elements proves that the request is real.

Check through an independent channel

• Do not start from the message you received. Open the official website or app yourself, or use a number already shown on a reliable document.
• Compare the sender, the exact domain, the beneficiary and the action requested. One consistent detail is not enough if the rest of the process leaves the official channel.

What to do now

• Compare the IBAN with an older reliable invoice.
• Open the official customer area.
• Call the provider using an official number.

If you have already interacted

• Stop the exchange. Change the login details you entered through the official app or website and enable two-factor authentication when it is available.
• Contact your bank quickly if a payment, card, IBAN, code or validation is involved. Keep useful evidence for a report.

Scope of this hub

• This hub covers changed IBANs, fake invoices, invented reminders and provider fraud.
• Fraud against the CEO is related but separate: it impersonates an authority to force an exceptional operation.

Triage and urgency level

• Compare the beneficiary, IBAN, reference and contact details with previous documents.
• A transfer to the wrong account must be reported immediately to the bank and to the real provider.

Limit of this classification

• This hub does not confirm the identity or reliability of a contact. For this family, the first check remains the following: Compare the beneficiary, IBAN, reference and contact details with previous documents.
• A situation can belong to several families. Go to the dossier whose dangerous action matches the real case: Fraud against the CEO is related but separate: it impersonates an authority to force an exceptional operation.

Limits of this page

• This page does not prove that a message is safe and does not replace your bank, the police, Safeonweb, a platform or a public service.
• A scam may be new, very well written or described with too little context. Use the result as decision support, not as absolute certainty.
• Before taking a final action, checking through the official channel matters more than the appearance of the received message.

Check through an official channel

• Type the service address yourself or open the official app. Do not use a phone number, link or QR code from the suspicious message to verify the situation.
• When money, card details, a code or account access are involved, the safety action comes first. The analysis can then help organise the evidence.

How to read the result

• A low number of signals does not mean that everything is safe. It only means that this page or analysis did not find decisive evidence with the information available.
• Focus on the requested action: paying, sharing a code, installing an app, approving a bank action or leaving an official platform. That action matters more than a logo, sender name or polished wording.
• If the situation feels urgent, step away from the received message first. Then check calmly through a channel you already trusted before the message arrived.

Belgian reading of this situation

• For the invoice payment request, focus on the relevant Belgian next step: open the official channel yourself, contact the bank, use Safeonweb or preserve evidence.
• The right decision for the invoice payment request depends on what has already happened. Reading a message is not the same as clicking, paying, sharing a code or granting remote access.

What to do now without panic

• If the invoice payment request worries you, choose the next step from the requested action: clicking, paying, sharing a code, installing an app, sending a document or approving account access. Do not rely only on the logo or sender name.
• When the invoice payment request involves an urgent, financial or hard-to-undo action, StopArnaques treats the situation as something that must be checked first. Polished wording, a familiar brand or a realistic amount does not make the request reliable by itself.
• If you already acted in a case involving the invoice payment request, the order matters more than the label: contact the bank, platform or official service first, preserve evidence next, then compare the situation with similar campaigns.

What can be legitimate

• For the invoice payment request, some notifications can be real: a delivery, invoice, administrative document, payment request, security alert or platform message. This is why this page does not claim that every similar message is automatically a scam.
• The difference in a the invoice payment request case is verification. A real request should be visible through the app, portal, customer area or phone number that you open yourself, not only through a link, QR code or number included in the suspicious message.
• If the official environment does not show the same request about the invoice payment request, amount, reference or beneficiary, it is safer to stop and report or verify the case before continuing.

Limits and responsibility

• For the invoice payment request, StopArnaques helps explain signals and choose safer actions, but it does not replace your bank, the police, Safeonweb, the FPS Economy, a platform or the organisation concerned.
• A result about the invoice payment request may remain uncertain when the text is too short, when context is missing or when the fraud uses a new variant. In that situation, slow down, verify independently and avoid any irreversible action.
• If the invoice payment request involves a payment, code, card, identity document, itsme approval, banking app or remote access, the protective action comes first. Do not wait for a perfect label if harm may already be possible.

Keep evidence and report

• For the invoice payment request, keep the message, date, channel, visible sender, neutralised link and useful screenshots. Do not publish personal data or clickable suspicious links on social media.
• Report the invoice payment request to the relevant channel when appropriate, for example Safeonweb for suspicious messages, the platform for account abuse and your bank when money or payment details are involved.
• This evidence about the invoice payment request can also help link a campaign to a case later without storing raw personal data. That matters if the system is to improve without exposing users unnecessarily.

Frequently asked questions

Useful official sources

• SPF Économie - Fraude à la facture - link checked on 2026-09-17
• Febelfin - Fraude à la facture - link checked on 2026-09-17
• Bancontact Company - Ensemble contre la fraude aux paiements - link checked on 2026-09-17
• SPF Économie - Victime d'une arnaque ? Que faire ? - link checked on 2026-09-17
• SPF Économie - Comment reconnaître une arnaque ou un arnaqueur ? - link checked on 2026-09-17