Back to Blog
Guide

Preventing duplicate payments and IBAN fraud on purchase invoices in Exact Online

Wouter Murmans
Wouter Murmans
Founder of Glimps
18 October 2026 6 min read

The short answer: you prevent duplicate payments and IBAN fraud by stopping an invoice before it is in your books, not at payment. In Exact Online you have purchase invoices approved before they are paid, and since October 2025 your bank checks the name against the IBAN. Glimps adds a check at the front: a possible duplicate invoice or a changed bank account stops the posting, and Glimps never pays by itself.

This guide shows how invoice fraud with a changed IBAN works, what you can do in Exact Online and at your bank yourself, and which checks are better done automatically. The sources are at the bottom, checked on 18 October 2026.

How it goes wrong

There are two ways a purchase invoice costs you money without anyone noticing:

  • The same invoice twice. The supplier sends a reminder with the invoice attached, a colleague forwards the mail, or the same PDF comes in two ways. Each copy can become its own entry, and each entry its own payment.
  • A different account number. According to the Dutch Fraudehelpdesk, criminals change the IBAN on real invoices, on paper or by email. The invoice looks right, the amount is right, only the money goes to a different account.

Both mistakes are hard to see for someone who approves dozens of invoices a day. That is exactly why you do not want them to depend on attention.

What you can do in Exact Online and at your bank

1. Have purchase invoices approved before payment

In Exact Online you can submit purchase invoices for approval to one or more users. According to Exact, payment can only be made after approval, and Exact records who approved what and when. That is your first four-eyes moment.

2. Use your bank's name check

Since October 2025, banks must check whether the name matches the IBAN on a transfer. In the Netherlands this is the IBAN-Naam Check; in Europe it is Verification of Payee. According to the Dutch Payments Association, it protects against fake invoices on behalf of a company you trust. For a payment batch, some banks make the check a choice at upload. Switch it on and do not ignore a warning.

3. Check supplier IBANs up front

The Exact App Store lists SurePay's IBAN-Naam Check portal. With it you check IBAN and account holder of suppliers, customers and employees, and of payment batches, and download the result as a PDF for your accountant.

4. Call on a new account number

Does a supplier announce a new IBAN, or is there suddenly another number on the invoice? The Fraudehelpdesk advises calling the supplier on a number you look up yourself, not the number in the mail or on the invoice.

Where it stops

Approval and the bank's name check sit at the end of the process. By then the invoice is already in your books, and it depends on the approver whether a duplicate invoice or a new account number stands out. A changed IBAN that matches the right name, for example because the supplier really changed banks, passes the name check. And a duplicate invoice with a different file name looks like a new invoice to a person.

What you want is a check at the front: before the invoice is posted, and without anyone having to think of it.

How Glimps stops it at the front

Glimps checks every purchase invoice before it reaches Exact Online. Four of the eight fixed checks stop a posting completely, whatever setting a supplier has:

  • Possible duplicate invoice. Glimps recognises the same invoice, even when it is sent again, forwarded or has another file name. The second one is not posted.
  • Duplicate check not available. If Glimps cannot run the duplicate check, it does not post either. No check means no posting.
  • Changed bank account. If the invoice shows a different IBAN from the one Glimps knows for that supplier, the invoice is prepared but not posted. Someone looks first.
  • Sum does not add up. If the lines do not add up to the total, Glimps does not post.

On top of that, the Inbox Agent sets aside an invoice from an unknown sender or with a different account number than usual, so you look at it first. Glimps never pays and never creates a payment file, so even an invoice that passes every check still goes through your own payment process and your bank's name check.

In practice: Vitacress Real processes about 750 purchase invoices a month with Glimps, from 317 suppliers, and 80 to 90% of them reach Exact Online without manual work. The checks run on every invoice. Read the Vitacress Real story.

Checklist

  1. Have purchase invoices approved in Exact Online before they are paid.
  2. Switch on the name check for every payment batch, and do not ignore a warning.
  3. Call a supplier on every new IBAN, on a number you look up yourself.
  4. Let duplicate invoices and changed account numbers be stopped automatically before they are posted.

Want to see how that works? Open the interactive demo or read which eight checks Glimps runs.

Share this article
FAQ

Frequently asked questions

Short answers to what people ask most.

Questions about your situation?

Open the demo

According to the Dutch Fraudehelpdesk, criminals change the account number on real invoices, on paper or by email. The invoice appears to come from a known supplier and the amount is right, but the money goes to a different account.

Call the supplier on a phone number you look up yourself, not the number in the mail or on the invoice. That is the advice of the Fraudehelpdesk.

Yes. You submit purchase invoices to one or more users. According to Exact, payment can only be made after approval, and Exact records who approved what and when.

A check whether the name matches the IBAN. Since October 2025, banks must run it before you confirm a transfer; in Europe it is called Verification of Payee. The Exact App Store also lists SurePay's IBAN-Naam Check portal to check suppliers and payment batches up front.

Glimps recognises the same invoice, even when it is sent again, forwarded or has another file name. A possible duplicate invoice stops the posting completely, and when the duplicate check cannot run, Glimps does not post either.

Glimps prepares the invoice but does not post it. A changed bank account is one of the eight fixed checks and stops every automatic posting, whatever setting the supplier has. Someone looks first.

No. Glimps posts purchase invoices in Exact Online, but never pays and never creates a payment file. Paying stays with you, with your own approval and your bank's name check.

At payment, the invoice is already in your books, and it depends on the approver whether a duplicate invoice or new account number stands out. A check before posting stops the mistake without anyone having to think of it.