Run a Duplicate Payment Recovery Queue Without Losing the Trail

Separate detection from recovery

Detection flags a possible duplicate. Recovery is a case with money at stake, a supplier relationship, and a deadline. Keep the two queues separate so a cleared alert is never mistaken for recovered cash. The detector should pass forward its match keys, rule or manual source, score, and detection date.

The recovery owner must be able to see why the item was flagged without rerunning the detection job. Store the matched invoice identifiers and payment references with the alert. If the flag came from a person, record who raised it and what they compared.

Qualify the duplicate before contact

Confirm the vendor, bank account, invoice number, amount, currency, payment date, and payment status. Check whether the second payment actually left the bank. A blocked, reversed, or returned item needs a different path from a settled duplicate, and treating them the same wastes treasury time.

Use the payment file reference and the bank statement line as the settlement test. A status of issued or approved is not proof that funds moved. If the bank evidence is not yet available, mark the case as unqualified and set a date to check again rather than opening a supplier conversation on assumption.

Build the recovery case file

The case should carry a unique identifier, vendor master ID, duplicate invoice IDs, payment references, amount and currency, detection date, qualification date, proposed recovery method, owner, and next action date. Add the entity and original payment run so reporting can group cases correctly.

Attach the invoice images, approval history, payment confirmation, bank line, and supplier correspondence. Keep the supplier's original message unchanged. If a credit is offered, attach the credit document and the invoice it will be applied to, not just an email promise.

Choose refund, credit, or offset

A refund fits when cash has left and the supplier agrees to return it. A credit fits when a future or open invoice exists and the supplier will apply the amount in writing. An offset fits only with written owner approval, a documented agreement, and a posting that can be traced to both invoices.

Do not offset a duplicate against a disputed invoice, another legal entity, or a different supplier account without explicit approval. Those shortcuts create a second reconciliation problem and obscure which transaction was actually recovered.

Whichever route is selected, record the expected settlement date and the person who will confirm it. A recovery case with an open method but no expected date tends to drift until the next statement cycle, when the same duplicate may be flagged again under a new case number.

Coordinate with treasury and the vendor

Treasury owns the bank trace, recall request, and settlement confirmation. AP owns the invoice evidence and the supplier conversation. Share one timeline so the supplier is not asked for the same reference twice and treasury is not surprised by a recall.

Use the established supplier contact and quote the payment reference, amount, and date. Ask the supplier to confirm what it received and how it recorded the amount. That answer determines whether a refund, credit, or reapplication is the cleanest route.

Track aging and ownership

Age each case from detection and again from the first recovery attempt. Set service levels the team can meet, such as contact within two business days, owner escalation at ten, and a written plan at thirty. Record the clock that applies so reports do not mix definitions.

Assign one owner per case and a named backup. When ownership changes, record the handoff date and the open next action. A queue with shared ownership and no named person tends to produce activity without resolution.

Protect the vendor relationship

Assume an error until the evidence shows otherwise. Most suppliers cooperate when they receive the invoice numbers, payment dates, and amounts in one message. Avoid language that accuses the supplier of taking advantage of a mistake.

Record commitments precisely. If the supplier says a refund will be issued next week, write the date and the amount, then verify it against the bank or a credit document. Do not promise a refund date that treasury has not confirmed.

Measure the queue with honest denominators

Report qualified duplicates in the period as the denominator and show open, recovered, written off, and unresolved cases. Include recovered amount, median age, and the oldest case. Do not compute a recovery rate over alerts that were never confirmed as duplicates.

Keep a separate count of prevented duplicates, such as invoices blocked before payment. Prevention is useful evidence, but it is not the same outcome as recovering cash and should not be added to the recovery total.

Review the aging list with treasury each week and agree which cases need a bank trace, which need a supplier call, and which should be written off under the approved policy. Write-off is an accounting decision, so record the approver and the reason rather than removing the case from the queue.

Close only on cleared funds or applied credit

Closure evidence is a bank credit, a supplier credit memo applied to a named invoice, or a written offset approval with a posting reference. A promise, a ticket status, or a supplier statement line is not enough on its own.

Reconcile the recovered amount to the general ledger and to the original payment. If the amount differs because of fees, currency, or a partial credit, keep the residual open with an owner. The case ends when the accounting effect is understood, not when the inbox is quiet.