Duplicate payment recovery across AP platform, ERP and mailbox: a system map of records and linking keys

Short answer

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.

Visual briefFull-size diagram
A grid of six system nodes, AP capture, vendor master, ERP payables, bank remittance, AP mailbox and recovery log, with linking keys (tax ID, invoice number, payment run, credit memo) traveling between them until two vendor records resolve into one joined case.
Illustrative: one supplier set up under two vendor IDs, joined back together by tax ID and bank account.

This system map is part of the duplicate payment recovery guide, 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.

SystemRecord it holdsLinking key it sharesUsual owner
AP capture platformInvoice images, captured fields, rejected and resubmitted versions, approval routeVendor ID, invoice number, internal document numberAP manager
ERP vendor masterVendor records with tax ID, remit-to address, bank account, change historyVendor ID, tax ID, bank accountVendor master team or controller
ERP payablesPosted invoices, payment runs, payment lines, credit memos, applicationsDocument number, payment run ID, credit memo numberController
Bank remittance and payment filesPayment confirmations and remittance advicePayment reference, amount, value dateTreasury
Shared AP mailboxRecovery requests, supplier confirmations, statementsInvoice number or vendor name in the subjectAP director, administered by IT
Recovery log or audit toolMatch results, the rule that flagged each pair, case status, close notesBoth document numbers, case IDAP 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.

JoinKey on one sideKey on the other sideWhere it breaks
Supplier to vendor recordsTax ID and bank account on each vendor recordThe same values on a second vendor recordTwo vendor IDs created with slightly different names; nobody compares tax IDs
Invoice to paymentInternal document numberPayment line in the runAP platform retired with only header data migrated
Invoice to its duplicateVendor, amount and invoice dateThe same values on the second invoiceReference field cleaned or overwritten in migration
Payment to correspondenceInvoice number or payment referenceEmail subject or bodyThreads kept in personal mailboxes
Credit to the duplicate paymentCredit memo number and the document it settlesThe original payment lineCredit applied as a generic adjustment with no link
Case to outcomeCase ID in the recovery logClose note, approver and dateRecovery 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.

StepSystemRecordKey carried forward
1ERP vendor masterV-2207 created during the plant onboarding, same tax ID and bank account as V-0412Tax ID, bank account
2AP capture platformInvoice 88310 for $9,412.50 captured against V-0412 and approvedV-0412, invoice 88310
3AP capture platformA copy of invoice 88310 arrives at the plant's address and is captured against V-2207V-2207, invoice 88310
4ERP payablesBoth invoices paid in different payment runs, nine days apartPayment runs PR-1140 and PR-1146
5Recovery logQuarterly review matches on tax ID, amount and invoice number across vendors; case openedCase R-063, both document numbers
6Shared AP mailboxRequest to the supplier citing both payment references; supplier confirms and offers a creditInvoice 88310 in the subject
7ERP payablesCredit memo for $9,412.50 applied against the supplier's next invoiceCredit memo number, settled document
8ERP vendor masterV-2207 blocked and merged into V-0412; change logged with user and dateVendor 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 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 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.

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. Who can approve a licensing discussion is covered in who can license duplicate payment recovery records, and the wider family of AP exceptions is on the accounts payable exception handling page.

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 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, check the company on who qualifies and read the program terms before making the introduction.

  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

Is the ERP alone enough to reconstruct a recovery?

Usually not. The ERP holds the posted invoices, payments and credits, but often not the captured image, rejected versions or the vendor's reply. Without the mailbox and the recovery log, a reader sees a credit and cannot tell why it was issued.

What if the recovery work was done by an outside audit firm?

Then the recovery log may sit in the firm's own system, under its contract with the company. Note it on the map as a separate node with its own owner; whether those working papers can be used is a question for the rights review.

Sources

  1. help.sap.com/docs/ARIBA_SOURCING/f081c6c38fb7466a84d746a7…
  2. docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/sectio…
  3. docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/chapte…
  4. 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