Preventing duplicate invoices in Exact Online: 3 checks before booking
Duplicate invoices do not arise through carelessness but through reminders, forwarding and multiple mailboxes. Three checks before booking, instead of a search after the fact.
A duplicate purchase invoice is rarely the fault of whoever books it. The supplier sends a payment reminder with the invoice attached again. A colleague forwards the same email you already had. An invoice arrives first as a PDF and a week later through Peppol. Whoever books the second version sees nothing odd about it, and the error only surfaces at payment, or worse, at the year-end close when the supplier balance does not add up. In this article: how duplicate invoices arise, why a check after the fact comes too late, and which three checks the Purchase Invoices module runs before anything is booked.
Why checking afterwards does not work
Most duplicate invoice checks run on the bookkeeping itself: a report that searches per supplier for two entries with the same number or amount. That is useful, but it catches the error after it has been made. The invoice is booked by then, perhaps already paid, and reversing it costs a credit entry, an email to the supplier and sometimes a refund that takes months.
The moment to check is before booking, at the point the invoice comes in. That is only possible if the intake itself does the check, and that is exactly what the module does.
Check 1: has this file already been processed?
The first check looks at the file itself. A unique fingerprint is calculated for every PDF, and if exactly the same PDF comes in again, it is stopped before anything is read. This catches the classic cases: a forwarded email with a duplicate attachment, a reminder with the same PDF, two colleagues forwarding the same invoice.
This check is hard: the second PDF does not enter the work queue, you only see a notification about it.
Check 2: is this invoice already in Exact?
A reminder usually does not contain the same PDF but a newly generated one. The fingerprint then differs while the content is the same. That is why the second check looks in your administration: does a purchase entry with this invoice number already exist for this supplier? If so, the invoice is blocked and put before you, with the existing entry alongside.
Below that sits a softer variant. If there is an entry for the same supplier with the same amount and the same invoice date, but a different (or missing) number, you get a warning instead of a block. That is deliberate: two identical amounts on one day are suspicious, but not impossible, for example with a supplier that invoices per location.
If the module cannot reach Exact for a moment, that does not count as "no duplicate found". You then get a notification that the check could not be done, instead of a green tick that means nothing.
Check 3: and across your other administrations?
Anyone with multiple companies knows it: an invoice that lands in the wrong administration, and once more in the right one. The third check therefore also looks at the invoices being handled or just booked in your other administrations. Same supplier, same number, different company: that is a warning you want to see before both are paid.
What you do with a notification
When a block occurs, you see the new invoice next to the existing entry in the control centre. If it really is a duplicate, you reject it with the reason "duplicate", and that is your trail for later. If it turns out to be a different invoice, for example because the supplier accidentally used the same number twice, you release it with one click and it continues on to the posting proposal. That release is recorded, including who did it and when.
If you want to be stricter, you can set the workflow so that even the soft warning holds an invoice until someone has looked at it. For an organisation with a single bookkeeper that is usually excessive, but for a team with several approvers it is useful.
Benefits and points of attention
The benefit is not only that you never pay an invoice twice. It is also that your supplier balance is correct, that you have no searching to do at year-end, and that an approver can reject an invoice with a reason everyone understands.
Two limitations. The check in Exact looks at purchase entries, so an invoice that someone once entered manually in another journal falls outside its view. And a supplier who does not keep invoice numbers unique will trigger false alarms, which is more of a conversation with that supplier than something software can solve.
Ready to get started? Start your free trial →
Try these questions in your own AI assistant
- "Which purchase invoices have been blocked as duplicates this month?"
- "Is there already an invoice from this supplier with this number in the administration?"
- "Show the invoices that came in across two administrations at the same time."
Frequently asked questions
Usually through a payment reminder with the invoice attached, a forwarded email with a duplicate attachment, the same invoice sent both as a PDF and via Peppol, or an invoice that ends up in two administrations. Rarely through sloppy bookkeeping.
Exact Online warns you when you manually enter an invoice number that already exists for the same supplier. An invoice with a newly generated PDF, a different number or in another administration falls outside this. The Purchase Invoices module checks before booking on file, on number, on amount plus date and across administrations.
An identical file or an existing invoice number is blocked and presented to you alongside the existing booking. You reject it or release it with a single click, and that choice is recorded. A match on amount and date only gives a warning.
Yes. The module also looks at invoices from the same supplier with the same number in your other administrations, so an invoice that accidentally arrives in two companies is not paid twice.
Yes. If a supplier accidentally uses the same number twice, you release the invoice in the control centre and it moves on to the booking proposal. The release is recorded with name and time.