Duplicate payment recovery records: what a useful exception history contains

Short answer

The records that explain a duplicate payment recovery are the invoice pair, the match that found the duplicate and the rule behind it, the payment lines for both payments, the vendor correspondence, the credit memo or refund that brought the money back, and the close note or rule change that followed. Together they show the problem, the authorized action and the checked result. A partner describes those record classes, systems and years, never the records themselves, and introduces the person who can authorize a licensing discussion.

Visual briefFull-size diagram
Two invoice cards compared field by field: vendor, amount and date match, the reference number differs, so the check passes it; below, the recovery chain runs from second payment to audit match, vendor confirmation and an applied credit memo.
Illustrative case: a resubmitted invoice with a changed reference number, paid twice and recovered by credit memo.

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:

  1. The invoice pair, as captured and approved in the AP platform, with both reference numbers.
  2. Both payment lines, with run IDs and value dates, from the ERP.
  3. The match result, naming the rule that flagged the pair, from a recovery spreadsheet or audit tool.
  4. Vendor correspondence: the request, the supplier's confirmation and the agreed remedy, usually in a shared AP mailbox.
  5. The recovery entry: a credit memo, a refund receipt or a netting against a later invoice, in the ERP.
  6. 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.

DateRecordSystemWhat it showsOwner
Mar 3Original invoice 40418, $18,640.00AP platform (capture and approval)The legitimate charge and its approval routeAP manager
Mar 17Resubmitted invoice 40418-R, $18,640.00AP platformThe same charge under a new referenceAP manager
Mar 31Payment run line for 40418ERP (payables and bank)First payment, with run ID and value dateController
Apr 14Payment run line for 40418-RERPThe duplicate paymentController
Jun 6Match result: same vendor, amount and date, references differRecovery spreadsheet or audit toolHow the duplicate was found and by which ruleAP lead
Jun 9 to Jun 16Email thread with supplier's receivables teamShared AP mailboxThe ask, the supplier's confirmation, the agreed remedyAP specialist
Jun 30Credit memo CM-2291 for $18,640.00 applied to the next invoiceERPThe recovered amount and how it was settledController
Jul 2Close note and rule change: strip suffixes like "-R" before matchingAP platform configuration logThe accepted outcome and the fixAP 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.

TestStrong historyWeak history
Can a case be followed end to end?Match result cites both invoice and payment IDsRecovered amounts booked with no link to the original pair
Is the reason recorded?Match rule or reviewer note says why the pair was flaggedOnly "duplicate" in a status field
Is the vendor exchange kept?Threads in a shared mailbox, filed by vendor or caseIn personal mailboxes of staff who have left
Is the outcome checked?Credit or refund reconciled and signed offCredit requested, no confirmation recorded
Did anything change?Rule or vendor master changes logged with datesNo record of what was learned
How many years and cases?Several years, a countable number of recoveries per yearA 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

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.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

Does recovered-credit history only matter if the company used a recovery audit firm?

No. Internal recoveries handled by AP staff produce the same chain: the match, the vendor exchange, the credit and the sign-off. If an outside audit firm did the work, its contract decides who owns the working papers, which is a question for the rights review.

Are duplicates that were blocked before payment useful too?

They show the control working, which is worth counting. The paid-and-recovered cases are usually more informative, because they record a miss, a judgment about what happened and a checked recovery. Describe the two groups separately.

Can a partner send SourceX a sample of the duplicate payment log?

No. Partners describe the records at metadata level only: record classes, systems, years covered and who owns them. Any sample or export happens later, under an agreement, with the company's authorization.

Sources

  1. help.sap.com/docs/SAP_ERP_SPV/98eed63ea3a544af84eb972dc68…
  2. learn.microsoft.com/en-us/dynamics365/finance/accounts-payable/v…
  3. learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/dat…
  4. irs.gov/businesses/small-businesses-self-employed/ho…
  5. refer.sourcex.si/terms

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment