Loading this page.
Loading this page.
Upload a payment register export. F20 compares the file against itself and surfaces the payments that look like the same money leaving twice -- identical vendor, amount and reference, and the weaker patterns worth a look.
Free duplicate payment detector: compare a payment register against itself and surface the same money looking like it left twice. Upload the file this page names, review the result in the browser, and download CSV or Excel when offered.
A payment 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.
Even the strongest tier means only that two rows are identical on the fields that matter -- not that anything improper happened. Every finding reads 'Potential anomaly requiring review.'; none of them instructs you to reverse, block or void a payment. The money has already left, so a wrong accusation costs a supplier relationship, not a tidy correction.
Blocks candidates on hash-keyed indices in a single pass — the same strategy the shared matching levels use — so a real register never becomes an all-pairs comparison, and a pathological cluster of payments sharing one vendor and amount is reported as an oversized cluster rather than expanded into every pair within it. Tiers run from deterministically identical on the fields that matter down to soft flags, and even the strongest tier means only that, never a verdict: every recommended action is exactly "Potential anomaly requiring review.", never an instruction to reverse, block or void a payment.
Upload the payment register. Tiers run from deterministically identical down to soft flags. Even the strongest tier is not a verdict: every recommended action is exactly "Potential anomaly requiring review."
Open the page, drop the payment 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 payment register. A cluster of payments that share one vendor and amount is reported as a cluster, not exploded into every pair. You do not need to pre-group them.
Review each finding as a potential anomaly, then reconcile AP if payments vs open bills is still open. The strongest tier is still not a verdict to void a payment.
Duplicate-payment review is a payables close control. Tiers run from deterministically identical down to soft flags. Every recommended action is exactly "Potential anomaly requiring review."