Supplier-to-first-payment record chain: the supplier number from onboarding approval through bank change to settlement

Short answer

A company connects supplier-to-first-payment records by carrying one supplier number from the onboarding approval through every bank-detail change into the payment, and by filing the change request and verification-call emails against that same number instead of leaving them in someone's inbox. Vendor master and payables records usually share the number already. Email almost never does, so the evidence that a bank change was checked is the link most likely to be missing.

Visual briefFull-size diagram
A vertical chain of six records (registration approved, vendor created, bank-change email, verification call note, bank account import, first payment) shows the email-to-import link as weak because the emails carry only a supplier name, then repaired by filing the emails under supplier number V-20417.
Illustrative chain for a fictional distributor. The weak link is a mailbox thread with no supplier number.

This record chain is part of the supplier-to-first-payment guide, which covers what a partner collects from a first conversation. This page has a narrower job: follow one vendor from approval to its first disbursement and name the key at each hop.

The keys available at each hop

Several identifiers exist between approval and settlement. Each was created for one team's purpose, and only some travel.

KeyCreated whenUsually appears inReaches email?
Registration IDA vendor registration startsSupplier portal onlyNo
Supplier numberThe vendor record is createdSupplier portal, vendor master, disbursementsOnly if staff type it
Supplier siteAn address or remit-to location is addedVendor master, invoices, disbursementsRarely
Change request numberA bank change goes through an approval workflowVendor master change historyRarely
Email threadA vendor writes in, or AP phones to verifyShared inboxYes, but carries none of the above by default
Payment numberThe payment run releases fundsDisbursements, bank fileNo

The supplier number is the natural anchor. The weak spot is the last column: the evidence of a request and a verification call lives in email, keyed by sender and subject line, not by any number the vendor master knows.

Vendor V-20417, hop by hop (Illustrative)

A fictional 420-person industrial distributor runs vendor registration in Coupa, the vendor master and payables in Oracle, and the AP shared inbox in Outlook. Vendor V-20417 is approved in January and paid for the first time in February.

StepRecordKey that points to the next stepSystem
1. ApprovalRegistration approved by procurement on January 8Registration ID mapped to supplier number V-20417Supplier portal
2. CreationVendor and site created from the registration on January 10V-20417ERP vendor master
3. RequestEmail on January 24 asks to change bank detailsVendor name in the subject line onlyShared inbox
4. Verification callAP clerk notes a call to the number on file, January 25Same email threadShared inbox
5. Bank changeBank account updated through a spreadsheet import on January 26V-20417; no change request numberERP vendor master
6. DisbursementFirst payment released to the new account on February 2Payment number and V-20417ERP payables

Every step happened, and the payment went to the right account. But steps 3 and 4 carry no supplier number, and step 5 has no approval record because of how the change was entered. Joining the January 24 request and January 25 call to the January 26 import depends on someone matching an email subject line to a vendor name. That join should be labeled unsupported until the company shows otherwise.

Five places the supplier number drops out

Five breaks recur in supplier chains. Each has a signature a partner can recognize without opening a record.

The inbox hop. Requests and verification notes arrive as email, keyed by sender and subject. Signature: a shared inbox with folders by month or by clerk, not by vendor.

The import that raises no request. Oracle's documentation says supplier bank account changes can require approval through a change request, and that further changes wait while one is pending, but that creation and updates through import and REST services do not raise change requests. Signature: bank changes with a timestamp and no change request number.

The portal approval copied by hand. Coupa's documentation says supplier payment account details must be approved by the customer before payment and sit in pending review until then, and that a supplier changing bank information needs multi-factor authentication and may have to upload proof such as a voided check or bank letter. That is a strong record in Coupa. If someone then keys the approved details into the ERP by hand, the ERP update carries no reference back to the Coupa approval. Signature: matching dates in both systems and no shared ID.

The audit history that was never on. Oracle documents that supplier audit history must be enabled through audit policies; with masking on, only masked bank account numbers and IBANs appear, and bank account owners, intermediary accounts and attachments are not audit-tracked. Signature: bank fields with a current value and no history before a certain date.

The callback note in a personal inbox. If the clerk who called back filed the note in their own mailbox, the evidence leaves with them. Signature: callback evidence that exists only for clerks still employed.

What a repaired hop looks like

For a referral, the point is not to fix anything. It is to know which hops already carry a key, from when. The repairs show what a complete hop looks like, so the company can say whether it has one.

Weak linkRepair the company may already useKey it creates
Request email to supplierSupplier number in the subject line, or a mailbox folder per supplierTyped reference on the email
Callback to bank changeCallback logged as a note on the change recordDate, caller and number dialed on the change
Import to approvalBank changes allowed only through the change request workflowChange request number
Portal approval to ERPIntegration that passes the portal approval ID to the ERPShared approval ID
Audit gapsAudit policy enabled for supplier bank fields, with a known start dateField history from that date

The dated version is the useful one: "supplier number on every request email from 2022; bank changes only through change requests from mid-2023; audit history on since 2021." The completeness checklist scores each hop as pass, partial or fail, and the missing-context comparison shows what a payables export alone cannot explain.

Owners of each hop and the open questions

Procurement owns steps 1 and 2, the AP manager owns steps 3 to 6, and IT owns the mailbox and its retention rule. Each can describe their hop from admin screens and memory. Authorizing a licensing discussion that touches payment controls takes the CEO, or the owner at an owner-led company, usually with the CFO involved.

The company baseline: 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 stay at metadata level: which hops carry a key, from which year, rough volumes and owners. They never see bank details, supplier contacts or the specifics of payment controls. Unknown until SourceX reviews it: what must be excluded for security reasons, how supplier and employee details would be de-identified, whether supplier contracts allow licensing, and what the company would be paid. For the mailbox side, see the Outlook system page, the Outlook inventory template and how Microsoft 365 advisors spot opportunities; data quality due diligence covers how linkage is assessed more generally.

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 your client can say from which year its request emails and bank changes carry the supplier number, register as a partner, confirm who qualifies and read the terms before you introduce the finance executive.

  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 supplier number enough to join everything?

It joins the procurement and payables records in most companies. It rarely reaches the mailbox, so the request and callback emails usually need a second habit: the supplier number or change reference in the subject line or a filing folder.

Can a supplier name stand in for the number?

Only as a guess. Names are spelled differently across systems and change after mergers, and two suppliers can share a trading name. Describe a name match to SourceX as a match, not a recorded link.

Does SourceX connect to Coupa, Oracle or Outlook?

Do not assume it. The tools named here are examples of where each step is commonly recorded. How any records would be prepared is decided in SourceX's review with the company.

Sources

  1. docs.oracle.com/en/cloud/saas/procurement/26a/oaprc/internal…
  2. docs.oracle.com/en/cloud/saas/procurement/25d/oaprc/supplier…
  3. compass.coupa.com/en-us/products/product-documentation/supplie…
  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