A duplicate payment is not resolved when a report finds two similar transactions. It is resolved after the team proves that one obligation was paid twice, agrees a recovery route, receives or applies the value, reconciles the records, and fixes the control gap.
Quick answer
A duplicate payment recovery process moves a case through Suspected → Validated → Contained → Resolution agreed → Recovery pending → Reconciled → Closed. Keep a suspected duplicate separate from a confirmed claim until the invoice, payment, supplier, and settlement evidence show that both payments discharged the same obligation.
First, prove that it is a duplicate
Two payments with the same amount are not automatically a duplicate. Recurring services, split deliveries, milestones, and separate legal entities can create legitimate similarities. Before contacting a supplier, compare the underlying obligation and both transactions.
- Obligation: invoice, purchase order or contract reference, receipt evidence, supplier identity, and paying entity.
- Payment evidence: payment IDs, dates, amount and currency, remittances, and settlement evidence.
- Prior resolution: open credits, refunds in transit, reversals, voids, or approved offsets.
Mark the case as Suspected until this review is complete. Do not delete an invoice or force a short payment to make the ledger look clean. If the payment has not settled, use the organization’s payment-cancellation controls rather than treating it as a recovery case.
Duplicate payment recovery matrix
| State and trigger | Owner | Required evidence | Control and next state |
|---|---|---|---|
| Suspected Report or reconciliation flags two payments. | AP analyst | Candidate payment IDs, supplier, invoice references, dates, amounts | Create a case and preserve source data. Move only after obligation-level review. |
| Validated Both payments cover one obligation. | AP lead and accounting reviewer | Invoice/PO or contract, both remittances, settlement evidence, rationale | Document amount and entity. Close false positives with a reason. |
| Contained Recovery is approved. | AP lead | Case approval, supplier contact, open-credit check | Choose refund, credit, or a policy-approved offset; check whether cancellation changes the route. |
| Resolution agreed Supplier confirms method. | Supplier owner plus AP | Written confirmation, amount, expected date, remittance or credit reference | Record the expected outcome and escalate missed commitments. |
| Recovery pending Value has not cleared. | AP analyst | Aging date, correspondence, expected reference | Review on a defined cadence; a promise is not closure. |
| Reconciled Refund or credit is received/applied. | Accounting reviewer | Bank/settlement evidence, credit application, case record | Match the recovery to the duplicate and follow company accounting policy before close. |
| Closed Records agree. | AP lead | Complete case record, reconciliation confirmation, corrective-action owner | Retain evidence and assign control remediation. |
Choose the recovery route deliberately
After validation, select a documented resolution rather than sending an informal request that can disappear in email.
- Refund: use when the supplier will return cash and finance can match the incoming value to the case.
- Supplier credit: use when a documented credit can be applied to a known future obligation. Track it until it is applied.
- Offset: use only where the company’s contract, policy, and approval rules support it. Record the approval, notice, and affected invoice.
- Cancellation or recall: if a payment has not settled, route it to the payment-cancellation process.
The accounting reviewer should determine entries under the organization’s accounting policy. This workflow controls evidence and handoffs; it is not accounting, tax, banking, or legal advice.
Worked example: a settled duplicate vendor payment
An AP analyst finds two settled payments of $8,400 tied to invoice INV-24018. The first was scheduled through an ACH run; the second was released after the invoice was re-entered with a formatting variation. The analyst gathers the invoice, purchase-order receipt, both payment references, and both remittances. The AP lead confirms that one delivery occurred and marks the case Validated.
The supplier confirms in writing that it will issue a credit memo because an approved invoice is due next month. The team records the credit reference and expected date, keeps the case in Recovery pending, and has the accounting reviewer match the applied credit to the new invoice and recovery case. Only then does the AP lead close the case and assign the root cause: the invoice-number normalization rule did not catch the formatting variation.
Make exceptions explicit
Assign an owner and review date whenever the supplier disputes the obligation, the case crosses entities or currencies, a credit has no future invoice, the recovery amount differs from the validated overpayment, or the payment state is unclear. Reopening a closed case should create a new approval event, not silently overwrite the prior conclusion.
Close the loop with prevention controls
Every confirmed duplicate is a control test. Record how it entered, which check did not fire, and who owns the corrective action. Possible follow-ups include invoice-number normalization, cross-entity checks, review of manual payment paths, clearer payment-run approvals, and a post-payment review for higher-risk suppliers.
Use duplicate invoice detection controls to stop recurrence before release. If the issue is a payment that failed to arrive, use the failed vendor payment recovery workflow. For a payment that has not settled and may still be stopped, use the vendor payment cancellation process.
Where Workhint fits
Workhint can help finance teams build a recovery work system that captures the alert, routes evidence to reviewers, records the resolution decision, assigns supplier follow-up, tracks recovery aging, and keeps an audit trail through reconciliation and close. The useful design question is: what evidence, owner, approval, exception route, and completed record are required before the case moves to the next state?
Frequently asked questions
When is a duplicate payment recovery case closed?
Close it after validation, evidence of refund, credit, or approved offset, reconciliation, required accounting handoff, and a recorded root-cause owner.
Should AP ask for a refund or credit memo?
Choose based on the supplier relationship, certainty of future obligations, and company policy. Track a credit until it is actually applied.
Who should approve recovery?
Set this in policy. Separate the analyst who identifies the issue from the reviewer who validates it, and involve the accounting owner for reconciliation decisions.
What to implement next
Start with a case record containing the two payments, one obligation, evidence checklist, recovery route, expected date, current state, owner, and reconciliation reference. Pilot it on one supplier group, review exceptions, then adjust the controls that caused confirmed cases.
Leave a Reply