Duplicate payment recovery is the AP work of finding invoices paid twice and getting the money back. Most cases are dull. The useful ones are the exceptions where the standard control missed something, because the records then show people working out what happened and fixing it. The accounts payable exception handling page covers the wider family of AP exceptions; this guide is about one kind and its record chain.
Which duplicate payment recovery records help a company explain how exceptions were handled?
The useful records are the ones that let a reader follow one case from the payment that should not have happened to the money coming back. For duplicate payments that usually means six record types sitting in at least three systems:
- The invoice pair, as captured and approved in the AP platform, with both reference numbers.
- Both payment lines, with run IDs and value dates, from the ERP.
- The match result, naming the rule that flagged the pair, from a recovery spreadsheet or audit tool.
- Vendor correspondence: the request, the supplier's confirmation and the agreed remedy, usually in a shared AP mailbox.
- The recovery entry: a credit memo, a refund receipt or a netting against a later invoice, in the ERP.
- The close note and any rule change, showing what the company decided to do differently.
Here is one case, worked through record by record.
Worked case: a resubmitted invoice with a changed identifier
Illustrative. A 260-person industrial parts distributor receives invoice 40418 from a packaging supplier (vendor V-118) for $18,640.00, dated March 3. Two weeks later, before the March 31 payment run, the supplier sends it again with the reference typed as 40418-R. Vendor, amount and invoice date are identical; only the identifier changed. It is paid a second time in April. A quarterly recovery review catches it in June.
| Date | Record | System | What it shows | Owner |
|---|---|---|---|---|
| Mar 3 | Original invoice 40418, $18,640.00 | AP platform (capture and approval) | The legitimate charge and its approval route | AP manager |
| Mar 17 | Resubmitted invoice 40418-R, $18,640.00 | AP platform | The same charge under a new reference | AP manager |
| Mar 31 | Payment run line for 40418 | ERP (payables and bank) | First payment, with run ID and value date | Controller |
| Apr 14 | Payment run line for 40418-R | ERP | The duplicate payment | Controller |
| Jun 6 | Match result: same vendor, amount and date, references differ | Recovery spreadsheet or audit tool | How the duplicate was found and by which rule | AP lead |
| Jun 9 to Jun 16 | Email thread with supplier's receivables team | Shared AP mailbox | The ask, the supplier's confirmation, the agreed remedy | AP specialist |
| Jun 30 | Credit memo CM-2291 for $18,640.00 applied to the next invoice | ERP | The recovered amount and how it was settled | Controller |
| Jul 2 | Close note and rule change: strip suffixes like "-R" before matching | AP platform configuration log | The accepted outcome and the fix | AP director |
The chain has a clear initial problem (a second payment), an authorized action (a credit request approved by the AP lead), and a checked result (the credit memo in the ledger, reconciled at month-end). That is what makes it a decision record rather than a pile of invoices. Each row on its own would show very little.
Why did the standard duplicate check miss it?
Because the field that changed is one of the fields the check compares. SAP's duplicate invoice check compares vendor, currency, company code, gross amount, reference document number and invoice date (SAP), and Dynamics 365 Finance can reject an invoice whose number matches an already-posted invoice (Microsoft). When the reference is one of the compared fields, a changed reference can let a resubmission pass.
The human recovery work that follows is the part a company's history captures and a configuration file does not. The match rule that finally caught the pair, the reasoning in the vendor thread and the decision to change the rule are judgments, made by named people, with dates.
What separates a useful exception history from a pile of invoices?
Ask the AP director a few questions about the recovery history as a whole, and note the answers, not the records.
| Test | Strong history | Weak history |
|---|---|---|
| Can a case be followed end to end? | Match result cites both invoice and payment IDs | Recovered amounts booked with no link to the original pair |
| Is the reason recorded? | Match rule or reviewer note says why the pair was flagged | Only "duplicate" in a status field |
| Is the vendor exchange kept? | Threads in a shared mailbox, filed by vendor or case | In personal mailboxes of staff who have left |
| Is the outcome checked? | Credit or refund reconciled and signed off | Credit requested, no confirmation recorded |
| Did anything change? | Rule or vendor master changes logged with dates | No record of what was learned |
| How many years and cases? | Several years, a countable number of recoveries per year | A single audit project with no follow-up |
Because tax guidance generally suggests keeping records at least three years from filing, with longer periods in some situations (IRS), invoices and payments are usually still there. The match logic, the correspondence and the close notes are what thin out. Whether the ERP can export the relevant entities is a question for the company's administrator; Dynamics 365 finance and operations apps, for example, export data entities through data projects as files or a data package.
Does the company qualify, and what stays unknown?
The introduced company needs 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license the records, and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English.
Recovery records name suppliers and sometimes their staff, and vendor contracts may restrict how invoice data is used, so what can be licensed is decided in SourceX's rights review with the company. Also unknown until then: what must be de-identified, whether there is dataset demand, and any offer. Partners sign the Channel Partner Agreement before submitting, and the first valid introduction within the 90-day window is credited when the company submits a verified application. The procurement approvals guide uses the same metadata-only approach, and the industries hub lists sectors where AP exception histories are common.
Go deeper on duplicate payment recovery
- Duplicate payment recovery records across systems: a system map of the keys that join AP platform, ERP and mailbox records.
- Who can license duplicate payment recovery records: a short answer on which decision-maker to introduce.
- Preserve duplicate payment recovery records before AP automation: an inventory checklist for an AP platform change.
- Duplicate payment recovery referral brief template: a fill-in template for the introduction note.
Next step
Refer a company. No cap on rewards. Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.
If a client's recovery history passes most of the tests above, register as a partner, confirm the company against who qualifies, and read the program terms and what you need to receive a payment before you introduce the CFO.