How it works and examples
This is what the report looks like
What the export shows as paid twice is kept separate from what needs a closer look. Below that are the credit notes not yet offset. For each supplier there is a letter to send: the supplier chooses a credit note, an offset or a repayment.
The report comes as a PDF, and the export comes back as Excel, with the findings marked.
Open the sample report (PDF, in Dutch)Fictitious example: all names, numbers and amounts are made up. Leaving an email address is not required.
FICTIONAL EXAMPLEFacturenscan · look-back scan
Look-back scan of paid invoices
In brief
- Imported
- 4,812 invoices and 96 credit notes from 2 entities
- Duplicate according to the export
- 3 items, totalling € 5,220.30
- To check
- 2 items, totalling € 3,862.25
- Credit notes not offset
- 2 credit notes, totalling € 795.40
- Duplicate in the master data
- 2 pairs of suppliers
Item A1 · supplier 20418 · € 1,840.00
- 2026-0417paid on 20-03-2026
- 20260417paid on 24-04-2026
The numbers differ by just a hyphen. Paid twice.
What the package does and does not check
Paid on 20 March 2026
2026-0417
Paid on 24 April 2026
20260417
Many packages, by default, only look at the same invoice number at the same supplier. AFAS says so itself. We search the paid invoices for what slips through: a slightly different number, another year or another entity.
What AFAS, Microsoft, Oracle and Visma write about it themselves
In Dynamics 365 Finance, NetSuite and Visma.net, the check on duplicate invoice numbers is a setting.
A fit for companies that…
- process a lot of purchase invoices
- have more than one entity
- recently switched accounting software or took over a company
Not a fit when there is…
- only a list of supplier names, without amounts and dates
- a need for an ongoing subscription (this is a one-off scan)
- no way to export to Excel or CSV
Works with any Excel or CSV export, for example from Exact Online, AFAS, Twinfield, SAP, Moneybird, Snelstart.
How much may have been paid twice?
An estimate, not a promise.
0.05% and 0.1% are our own cautious assumptions. Vendors of this kind of scan report 0.2% and more in duplicate payments at large companies, gross. There is no figure for companies of this size. Found is not recovered: what comes back is lower, and stays unknown until the scan.
Request a scanAbout us
We have been picking through data for large organisations for 25 years. Finding duplicate invoices is what we like best: it is still fun. With a fixed method we go through the data, and one page comes back with what we found and what to do with it.
Looking beyond the scan?
A full review of master data or processes? Then book a free 30-minute conversation with Ramzy Alioui, consultant at Regency Management & Consulting and founder of Facturenscan.