# Duplicate payment recovery: a system map | SourceX

Canonical: https://refer.sourcex.si/guides/duplicate-payment-recovery-records-across-systems
Last updated: 2026-11-04

To reconstruct a duplicate payment recovery across systems you need four joins: the supplier to its vendor records, each invoice to its payment, the payment to the vendor correspondence, and the credit or refund to the payment it offsets. The AP platform holds captured invoices, the ERP holds vendor master, payments and credits, and the shared mailbox holds the reasoning. The joins survive only where both sides recorded the same identifier. The weakest is often the vendor itself, when one supplier exists under two vendor IDs.

This system map is part of the [duplicate payment recovery guide](/guides/workflow-duplicate-payment-recovery), which follows one paid-twice invoice from match to credit. This page does a different job: it shows which system holds each record, which key ties them together, and who runs each system.

## Six systems and the record each holds

A mid-sized company typically spreads one recovery across six places. The table is the map.

| System | Record it holds | Linking key it shares | Usual owner |
|---|---|---|---|
| AP capture platform | Invoice images, captured fields, rejected and resubmitted versions, approval route | Vendor ID, invoice number, internal document number | AP manager |
| ERP vendor master | Vendor records with tax ID, remit-to address, bank account, change history | Vendor ID, tax ID, bank account | Vendor master team or controller |
| ERP payables | Posted invoices, payment runs, payment lines, credit memos, applications | Document number, payment run ID, credit memo number | Controller |
| Bank remittance and payment files | Payment confirmations and remittance advice | Payment reference, amount, value date | Treasury |
| Shared AP mailbox | Recovery requests, supplier confirmations, statements | Invoice number or vendor name in the subject | AP director, administered by IT |
| Recovery log or audit tool | Match results, the rule that flagged each pair, case status, close notes | Both document numbers, case ID | AP lead or an outside audit firm |

The ERP is the spine for money, but not for reasoning. A posted credit memo proves money came back; only the mailbox and the recovery log say why the supplier agreed.

## The linking keys between them

Each join needs an identifier recorded on both sides at the time. Here is what each depends on and where it usually breaks.

| Join | Key on one side | Key on the other side | Where it breaks |
|---|---|---|---|
| Supplier to vendor records | Tax ID and bank account on each vendor record | The same values on a second vendor record | Two vendor IDs created with slightly different names; nobody compares tax IDs |
| Invoice to payment | Internal document number | Payment line in the run | AP platform retired with only header data migrated |
| Invoice to its duplicate | Vendor, amount and invoice date | The same values on the second invoice | Reference field cleaned or overwritten in migration |
| Payment to correspondence | Invoice number or payment reference | Email subject or body | Threads kept in personal mailboxes |
| Credit to the duplicate payment | Credit memo number and the document it settles | The original payment line | Credit applied as a generic adjustment with no link |
| Case to outcome | Case ID in the recovery log | Close note, approver and date | Recovery tracked in a personal spreadsheet |

Invoice-level duplicate checks usually compare documents within one vendor. When the same supplier sits under two vendor IDs, those checks have nothing to compare, and the duplicate is found later by someone matching on tax ID, bank account or amount across vendors. Supplier onboarding controls do not always close the gap. SAP documents that in Ariba external supplier requests, approvers see existing suppliers that match a request so they can deny duplicates, but custom checks do not match against data that arrives through data import or ERP integration. A bulk load after an acquisition is exactly that kind of arrival.

## One fully joined case: one supplier, two vendor records (Illustrative)

A fictional 380-person food equipment manufacturer acquires a smaller plant and loads its supplier list into the ERP. A corrugated packaging supplier already exists as vendor V-0412; the plant's file adds it again as V-2207, with an abbreviated name. Every identifier below is invented.

| Step | System | Record | Key carried forward |
|---|---|---|---|
| 1 | ERP vendor master | V-2207 created during the plant onboarding, same tax ID and bank account as V-0412 | Tax ID, bank account |
| 2 | AP capture platform | Invoice 88310 for $9,412.50 captured against V-0412 and approved | V-0412, invoice 88310 |
| 3 | AP capture platform | A copy of invoice 88310 arrives at the plant's address and is captured against V-2207 | V-2207, invoice 88310 |
| 4 | ERP payables | Both invoices paid in different payment runs, nine days apart | Payment runs PR-1140 and PR-1146 |
| 5 | Recovery log | Quarterly review matches on tax ID, amount and invoice number across vendors; case opened | Case R-063, both document numbers |
| 6 | Shared AP mailbox | Request to the supplier citing both payment references; supplier confirms and offers a credit | Invoice 88310 in the subject |
| 7 | ERP payables | Credit memo for $9,412.50 applied against the supplier's next invoice | Credit memo number, settled document |
| 8 | ERP vendor master | V-2207 blocked and merged into V-0412; change logged with user and date | Vendor change history |

The tax ID and bank account are what make this case reconstructable; the invoice number links the two captures, and the case ID links the recovery log to the email and the credit. Step 8 matters as much as the money. It records what the company learned. If the vendor merge was done without a change log, the history shows a credit and two vendor records, but not that anyone fixed the cause.

## What the export has to keep for the joins to survive

The joins above depend on fields that system migrations often drop. When a company is moving systems, the questions are about these fields, not about volumes.

- **Vendor change history.** Some ERPs log who changed which field and when. NetSuite, for example, documents that system notes record the time of a change, the user, the field and the old and new values, and that they cannot be edited. Whether that history comes out with an export is a question for the company's administrator; the [NetSuite systems page](/systems/netsuite) covers that system.
- **Load keys used in past migrations.** NetSuite recommends external IDs with its upsert operation to prevent duplicate records: a matching record is updated, otherwise a new one is created. Whether the company used such keys when it loaded acquired suppliers explains why duplicate vendors exist or not, and the answer belongs on the map. The [Dynamics 365 systems page](/systems/microsoft-dynamics-365) covers another common ERP.
- **Rejected and resubmitted versions.** These usually live only in the AP capture platform. If the platform is retired with only posted invoices migrated, the join between the two captures is gone.
- **Mailbox ownership.** A shared mailbox survives staff changes; personal mailboxes may not. The preservation side is covered in [preserving duplicate payment recovery records](/guides/preserve-duplicate-payment-recovery-records).

Until the company's administrator confirms what each export includes, a partner records the answer as "unknown". Partners do not test exports or ask for samples.

## Mapping questions for the AP director

The AP director can usually answer these without opening a record:

1. Which systems hold captured invoices, vendor master, payments, credits, recovery cases and supplier email, and since which year?
2. Has the company ever merged vendor records, for example after an acquisition, and was the merge logged?
3. Does the recovery log cite both document numbers and a case ID, or only a recovered amount?
4. Are supplier recovery threads in a shared mailbox, and do they cite invoice numbers?
5. Roughly how many duplicate cases a year, and how many recovered, from a report or the log?
6. Who administers each system, and did an outside firm do any of the recovery work?

The answers feed the [duplicate payment recovery referral brief](/resources/duplicate-payment-recovery-referral-brief-template). Who can approve a licensing discussion is covered in [who can license duplicate payment recovery records](/questions/who-can-license-duplicate-payment-recovery-records), and the wider family of AP exceptions is on the [accounts payable exception handling page](/data-types/accounts-payable-exception-handling-process).

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. Partners sign the Channel Partner Agreement before submitting and never handle invoices, emails or exports. Supplier contracts may restrict how invoice data and correspondence are used, so what can be licensed, and whether any buyer wants it, stays unknown until SourceX reviews it with the company. The [referral status glossary](/resources/referral-status-glossary) explains what each stage after submission means.

## 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 the AP director confirms that recovery cases link both payments to a credit and a supplier thread, [register as a partner](/register), check the company on [who qualifies](/who-qualifies) and read the [program terms](/terms) before making the introduction.

## Sources

- https://help.sap.com/docs/ARIBA_SOURCING/f081c6c38fb7466a84d746a7998bfe0e/d586f15765bb4288bc0794e82187a59e.html
- https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_N3532463.html
- https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/chapter_158644279544.html
- https://refer.sourcex.si/terms
