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.
| Key | Created when | Usually appears in | Reaches email? |
|---|---|---|---|
| Registration ID | A vendor registration starts | Supplier portal only | No |
| Supplier number | The vendor record is created | Supplier portal, vendor master, disbursements | Only if staff type it |
| Supplier site | An address or remit-to location is added | Vendor master, invoices, disbursements | Rarely |
| Change request number | A bank change goes through an approval workflow | Vendor master change history | Rarely |
| Email thread | A vendor writes in, or AP phones to verify | Shared inbox | Yes, but carries none of the above by default |
| Payment number | The payment run releases funds | Disbursements, bank file | No |
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.
| Step | Record | Key that points to the next step | System |
|---|---|---|---|
| 1. Approval | Registration approved by procurement on January 8 | Registration ID mapped to supplier number V-20417 | Supplier portal |
| 2. Creation | Vendor and site created from the registration on January 10 | V-20417 | ERP vendor master |
| 3. Request | Email on January 24 asks to change bank details | Vendor name in the subject line only | Shared inbox |
| 4. Verification call | AP clerk notes a call to the number on file, January 25 | Same email thread | Shared inbox |
| 5. Bank change | Bank account updated through a spreadsheet import on January 26 | V-20417; no change request number | ERP vendor master |
| 6. Disbursement | First payment released to the new account on February 2 | Payment number and V-20417 | ERP 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 link | Repair the company may already use | Key it creates |
|---|---|---|
| Request email to supplier | Supplier number in the subject line, or a mailbox folder per supplier | Typed reference on the email |
| Callback to bank change | Callback logged as a note on the change record | Date, caller and number dialed on the change |
| Import to approval | Bank changes allowed only through the change request workflow | Change request number |
| Portal approval to ERP | Integration that passes the portal approval ID to the ERP | Shared approval ID |
| Audit gaps | Audit policy enabled for supplier bank fields, with a known start date | Field 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.