Duplicate Invoices
Find invoices paid twice.
- General ledger alone
- Key analysis in Purchases & payables
What it checks
- Exact: same vendor, amount, normalized invoice number.
- Fuzzy: same vendor, amount within tolerance, dates close.
How the result is read
A duplicate booked and a duplicate paid are different findings — corrected by a credit and by recovering cash respectively — so the test runs against the payment population as well as the invoice population and reports the two separately. Most raw output is false positives from three causes: recurring charges, instalments against one order, and credit notes that mirror an invoice by design.
The worksheet, on the demo engagement
Duplicate Invoices, as the application draws it for Harrow Precision Engineering Ltd, the fictional demo engagement — one row per candidate pair.
Ranked by the money each pair puts at risk, so the reader can see how few to open to cover most of it. Tiers are never added together — which pair is an exact match and which is fuzzy stays on the grid.
- Groups
- 14
- Paid twice
- 6
- Exposure
- 38.4k
Confirmed paid-twice 5,580 — recoverable overpayment.
Result grid3 rows
| Group | invoice A | invoice B | vendor | amount | dates |
|---|---|---|---|---|---|
| D-01 | PI-66201 (#A1099) | PI-66830 (#A1099) | Global Parts | 4,400 | same |
| D-02 | PI-66310 (#7741) | PI-66355 (#7741) | Meridian | 1,180 | +2d |
| D-03 | PI-66120 (#INV-2231) | PI-66480 (#INV2231) | Orion | 2,950 | same |
In the application
Duplicate Invoices is filed under Purchases & payables, index letter D. "Run all analyses" runs it with every other analysis the ledger can answer. The worksheet states the population it tested on its face — or "Not applicable" with the reason when a column it depends on is empty — and the Excel workbook the engagement exports files it under D, beside an index of the source files with their SHA-256 fingerprints.
Also listed in the application as Duplicate Payments
, Fuzzy Duplicate Invoice
.
Read it with
Run your next audit file test without the Excel crash.
One free engagement to evaluate, valid 60 days. The ledger never leaves the machine.
- 20 minutes
- Runs on a fictional engagement
- No client data required