Duplicate payment detection that stops twins before the run and recovers the paid ones in house
Twins stopped before the payment run, paid ones recovered in house, every claim signed.
See one case, screen by screen ↓Duplicate payment detection and a recovery audit on one set of agents. It finds invoices that are the same invoice in disguise across vendor records and ledgers, holds them from the payment run before the cut-off, and for twins already paid drafts the claim with both invoices attached and follows it to the money back. The AP manager approves every claim.
How to choose AI solutions for back-office and enterprise work →
Updated
The ERP's duplicate check compares one vendor record, in one ledger, on the exact invoice number. A dropped hyphen, a misread character, a second vendor record for the same supplier, or a “past due” copy emailed to another ledger is enough to get the same invoice paid twice. A group that pays from four ledgers and 61,412 vendor records has every one of those gaps.
So the work splits in two. AP looks for exact repeats before the payment run, and an outside recovery firm audits paid invoices a year or two later and keeps a share of what it finds. In between, someone runs spreadsheet queries that return thousands of candidates, sifts them by hand, chases credits that suppliers promise and forget, and the duplicate vendor record that caused the twin stays in the master data.
Estimated split for one audit wave across four ledgers, by hand and with the solution.
Seven agents find twins across vendor records and ledgers, argue the other side, hold them from the run and recover the paid ones; a person approves every claim.
Kestrel & Vane Group pays from four ledgers. On Wednesday 14 October its AP manager has tomorrow's payment run to protect and a 24-month recovery audit to work. Here is what happens next, screen by screen, in the working solution.
Elena's twin list leads with a strip that splits the work: stop before payment, 11 twins worth $163,091.85 in Thursday's run, and already paid, 264 pairs worth $2.76M found by the 24-month audit. Each row shows both invoices joined by a band that says exactly what differs — ME-2026-0412 against ME20260412, “two hyphens dropped”.
“Show me both invoices side by side and tell me why our own check missed it.”
Run PR-WK42 holds 9,612 invoices for $148,306,422.18. The twin matcher found 17 possible twins and the skeptic cleared 6 as legitimate, such as the Strand & Copley rent. The payment guard held 9 inside its $25,000 limit and proposed 2 to Elena: Marwick Engineering at $48,600.00 and Ostrava Tooling at $31,650.00, the same invoice in two ledgers and two currencies.
The payment guard never voids or deletes an invoice, and never releases a hold.
On the recover side, the first pair is Corvane Packaging: INV-77341 and INV77341, paid 4 Sep and 15 Sep, 11 days apart. The band shows the hyphen dropped, two vendor records, a different remit-to address — and the same bank account, ••4471.
The first invoice came by EDI into Americas P01 against vendor V-100482 with PO 4500121907. A “past due” email carried the same PDF to the Atlanta team, who keyed it into the Distribution ledger without the hyphen and without the PO, against V-2207815 — a record with the same tax ID and bank. The matcher is 97% sure: invoice number 0.94, amount, date, tax ID, bank and lines 1.00, page image 0.98.
Why the ERP's own check let it through: “a different vendor record (V-2207815), in a different ledger (Distribution DST), with a different invoice number (no hyphen).”
The skeptic asks five questions and answers each from a document. Split shipment? No: one goods receipt, GR 5000388214 on 19 Aug, and no Corvane delivery at the Atlanta DC from 1 Aug to 30 Sep. Instalment? No: Corvane bills each PO once. Recurring charge? No: 41 invoices in 24 months, no two alike. Separate order? No: same lines and prices. Voided and reissued? No: both payments cleared.
“The skeptic works without seeing the matcher's score, so it argues the other side on the evidence alone.”
Tomás confirms the pair with reason code DP-03, paid to two vendor records for one supplier. At 08:53 the recovery agent drafts claim CLM-2026-0147 to Dana Whitlock, AR manager at Corvane. Corvane has $41,206.50 open in Americas P01, so it recommends an offset against INV-78112 ($27,480.00, due 22 Oct). Five attachments go with it: both invoices, both remittances and the goods receipt.
“You approve every claim before it is sent. Nothing goes to Corvane Packaging until you do.”
Elena reads the letter and the attachments, ticks that she has, and approves with CL-01 — recover by offset against open invoices. She approves claims up to $50,000; above that the group controller signs too. Nobody approves a claim for a pair they confirmed themselves.
The letter tells Corvane that unless it objects by 21 October, $23,815.00 is deducted from INV-78112 in the run of 22 Oct. The credit tracker expects Corvane's credit memo by 4 Nov: Corvane took 21 days to credit the last claim, CLM-2026-0102 for INV-75018.
The credit tracker never writes off a claim; write-offs go to the controller.
V-2207815 was created on 12 May 2025 when the Atlanta DC was onboarded, and it has now caused two twins. The steward proposes merging it into V-100482 and blocking it for posting. Vendor clean-up lists 25 suppliers set up twice, behind 59 twins and $564,621.91 paid twice; Ravi Menon, the vendor master data lead, approves each merge.
The vendor master steward never edits a vendor record.
Since go-live on 1 Sep, $1.36M in 121 twins was stopped across 7 weekly runs and $1.39M was recovered in 36 claims. At a typical 22.5% contingency an outside firm would have kept $313k. The same report splits confirmed twins by root cause: two vendor records, two ledgers, two channels, keyed or read wrongly, and credit memos not applied.
The same twin, seen by the five people who carry it — what their month looked like, and what it looks like now.
Seven agents find twins across vendor records and ledgers, argue the other side, hold them from the run and recover the paid ones; a person approves every claim.
Reads invoices, payments, credit memos, vendor records and supplier statements from the four ledgers, the AP mailbox and the bank files, and puts them in one shape.
Finds pairs that are the same invoice in disguise: near-identical numbers, swapped dates, other vendor records with the same bank or tax ID, other ledgers, other currencies, credit memos never applied.
Tries to prove each pair is legitimate: rent and lease schedules, split shipments with their own receipts, instalments in the contract, separate service periods, correct voids and reissues. Only pairs it cannot clear go on.
Holds the twin from the payment run before the cut-off, up to $25,000 on its own; above that it proposes the hold to the AP manager. Tells the run owner what was held and why.
For a paid twin, chooses offset or refund from what is open with the vendor, drafts the claim letter with both invoices and both payments attached, sends it once approved, reads the reply and proposes the next step.
Watches every claim to closure: chases on the service level, matches credit memos and refunds to claims, schedules offsets in the next run and closes the claim when the cash is back.
Finds the vendor records behind repeat twins — same tax ID, bank account or address — proposes the merge and the block, and tracks how many twins each clean-up prevents.
Approve claims and holds; the vendor master lead approves merges. The agents propose; a named person decides.
Ask about any pair, claim, vendor or payment run, or say what to chase. Every figure in the answer points to its source.
Why is Corvane INV77341 a duplicate?
It is INV-77341 paid a second time, from a second vendor record. Corvane has two records with the same tax ID and bank account: V-100482 in Americas P01 and V-2207815 in Distribution. The Atlanta team keyed a reminder PDF as INV77341, without the hyphen and without the PO. Both payments of $23,815.00 cleared to account ••4471, on 4 and 15 Sep. The skeptic found one goods receipt and no second delivery.
What does the payment guard hold in tomorrow's run?
11 twins, $163,091.85. 9 are held inside the guard's $25,000 limit; 2 wait for you: Ostrava Tooling s.r.o. $31,650.00 and Marwick Engineering $48,600.00. The skeptic cleared 6 look-alikes, including the Strand & Copley rent, so they pay as normal. Cut-off is 14:00 tomorrow.
How much have we recovered, and what is still open?
$1,392,029.79 recovered from 36 claims since 1 Sep. $830,982.98 is with vendors, $183,428.91 in 7 claims waits for your approval, and $353,740.94 in 24 pairs is not yet confirmed. At a typical 22.5% contingency an outside firm would have kept $313,207.
Which vendor records cause the most twins?
25 suppliers are set up twice. The largest by money paid twice: Ostrava Tooling s.r.o. (4 twins, $52,974.47), Mirelle Office Interiors (7 twins, $48,507.13), Halbrook Freight Lines (3 twins, $47,960.34). Merging each copy into the record that already exists stops the next twin at the source; 13 merges wait for Ravi Menon.
13 screens from the working solution, on its sample data. Pick one to see it large.
How a twin is found, cleared, held and claimed are settings. Changes go to the group controller as a new version.
| Setting | Default | Choose from |
|---|---|---|
| Invoice number | Similarity ≥ 0.85 | Separators, a dropped or added character, misread letters, swapped digits |
| Amount | Within $5.00 or 0.5% | Exact, or within a small difference for freight or tax keyed twice |
| Supplier identity | Any one of three | Same tax ID · same bank account · same name and address |
| Skeptic rules | LG-01 to LG-05 on | Recurring charge · split shipment · instalment · separate order or service period · voided and reissued · utility or telecom (off) |
| Hold a twin from a payment run | Payment guard on its own up to $25,000 | Above that, the AP manager before the run cut-off |
| Approve and send a claim | AP manager up to $50,000 | Above $50,000 and write-offs, also the group controller |
| Merge or block a vendor record | Vendor master data lead | Any amount |
| No vendor reply | 10 business days | Credit tracker chases; analyst told at 20 |
Every figure is labelled: a target the solution is built to, an estimate, a typical published result, or a proven one.
“demo” = seen in the working solution, on its sample payment data · “target” = the design goal, measured in the live solution · “estimated” = our estimate · “typical” = published figures (APQC benchmark via City of Richmond Office of the City Auditor, OCA 2026-09 — 0.08% to 2% of disbursements duplicate or erroneous; Texas Comptroller recovery audit contracts — 14% in 2012, 22.5% in 2020; Virginia recovery audit bids — 13.5% to 40%). Kestrel & Vane Group, its vendors and the people named on this page are fictional — characters and sample data in the working solution.
Duplicate payment detection and a recovery audit on one set of agents. It finds invoices that are the same invoice in disguise across vendor records and ledgers, holds them from the payment run before the cut-off, and for twins already paid drafts the claim with both invoices attached and follows it to the money back. The AP manager approves every claim.
The ERP compares one vendor record, in one ledger, on the exact invoice number. The twin matcher compares similar invoice numbers, swapped dates, amounts within a small difference, vendor records with the same tax ID, bank or address, every ledger and currency, the lines and the page image. Every pair says which control it slipped past.
A second agent, the skeptic, tries to prove each pair legitimate from a document: a lease schedule, a second goods receipt or bill of lading, a contract instalment clause, a separate service period, or a correct void and reissue. It works without seeing the matcher's score. In the sample audit it cleared 3,902 of 4,185 candidates, so 283 went to a person.
Yes. Every invoice in each payment run is screened against 24 months of payments before the cut-off. The payment guard holds twins up to $25,000 on its own and tells the run owner; above that it proposes the hold to the AP manager. It never voids or deletes an invoice, and a release needs a reason and evidence.
The recovery agent picks an offset against open invoices or a refund request, drafts the letter with both invoices and both payments attached, and sends it once the AP manager approves. It reads the vendor's reply and proposes the next step, and the credit tracker chases on the service level until the credit memo or refund is matched.
The recovery audit runs in house, across every paid invoice rather than a sample, and the claim is closed by your own team. Published contingency fees run 14% to 40% of what is recovered; in the working solution a 22.5% fee would have taken $313,207 of the $1.39M recovered.
Yes. A person confirms each paid twin, the AP manager approves every claim and every hold over $25,000, the controller signs claims over $50,000, write-offs and settings, and the vendor master data lead approves every merge. Nobody approves a claim for a pair they confirmed, and every step is on a chained audit trail.
The Agentic Solution Engine builds and deploys it from your requirements and documents — your AP policy, your ledgers and a sample of past payments — and it goes live once every quality gate has passed. First-time setup includes a back-test on 90 days of payments, so you see what it would have caught before go-live.
Blocked invoices released before late fees and supplier holds, every fix checked twice.
1-min demoVendor Payment Fraud PreventionEvery bank change proven by a call-back before a single dollar moves.
1-min demoExpense Report AuditEvery report checked, not a sample, and no forged receipt paid without proof of payment.
1-min demoWe'll run Duplicate Payment Detection & Recovery Audit on a sample of your own paid invoices and vendor records.