Loading this page.
Loading this page.
Upload an invoice register export. F20 compares the file against itself and surfaces the same invoice booked more than once -- exact repeats, invoice numbers that differ only by punctuation, and numbers a person mis-keyed by a single character.
Free duplicate invoice detector: compare an invoice register against itself and surface the same invoice entered more than once. Upload the file this page names, review the result in the browser, and download CSV or Excel when offered.
An invoice register with an exact duplicate pair. These are synthetic fixtures, processed in memory and never stored.
Your file is processed in memory and never stored. Nothing is written to disk, and nothing is retained after the response.
INV-1002, INV1002 and inv/1002 are treated as one invoice number. A near match -- INV-9921 against INV-992I -- is always reported at a lower risk tier than an exact one, because it may be two genuinely different invoices. Every finding is worded 'Potential anomaly requiring review.', a fact about the rows, never a conclusion about a person or a supplier.
Normalises each invoice number by upper-casing it and stripping every non-alphanumeric character, so INV-1002, INV1002, INV 1002 and inv/1002 collapse to one key — deliberately more aggressive than the shared reference matcher, because these numbers are typed by hand into two systems that disagree about punctuation. A second, coarser key folds visually confusable characters (O and 0, I and 1, S and 5) and a single-edit test catches a mis-keyed digit, and a near match is always reported at a lower risk tier than an exact one. Candidates are found by hash-keyed blocking in one pass rather than by comparing every pair, and each finding reads "Potential anomaly requiring review."
Upload the invoice register. Invoice numbers are normalised so INV-1002 and INV1002 collapse to one key. A near match is always a lower risk tier than an exact one. Every finding reads "Potential anomaly requiring review."
Open the page, drop the invoice register, and read the result in the browser. Download CSV or Excel when the tool offers those exports.
Yes. There is no charge and no account required. Every tool on F20 FinanceOps runs without signing in. A run made without an account is not recorded.
No. Uploaded files are processed in memory and dropped when the response is sent. Nothing is written to disk. They are never stored.
Have the invoice register. Invoice numbers such as INV-1002 and INV1002 collapse to one key — you do not need to normalise them first.
Treat every finding as "Potential anomaly requiring review." Then hunt duplicate payments if the same vendor was paid twice, or three-way match if the PO/GRN/invoice set is the next control.
A self-comparison of the invoice register is the cheap AP control before close. Near matches are a lower risk tier than exact ones. Every finding is a review flag, not an instruction to reverse a bill.