Supplier-to-first-payment records: a sample metadata packet for Coupa, Oracle and Outlook

Short answer

A referral partner can describe a company's supplier-to-first-payment history without seeing a supplier record: which system approves new suppliers, which records bank-detail changes and their approvals, where callbacks and requests are kept, how long each source is retained, how many suppliers are onboarded a year, and who owns each step. The question that separates a complete history from a partial one is what happens when a supplier's bank details change after it was approved.

Visual briefFull-size diagram
A decision tree starts at a bank change requested after supplier approval and splits into three routes: an Oracle change request with approver and audit history, a Coupa update held for customer approval, and an import that raises no change request and leaves only an email callback before the first payment.
Illustrative. Three routes to the same first payment; only two leave an approval record.

The business task: pay a new supplier once, to the right account

Between approving a new supplier and paying its first invoice, a company has to confirm who the supplier is, record where the money should go, and check any change to those bank details before money moves. Procurement usually owns the first step, accounts payable the second and third, and the evidence of a callback or a supplier's request often ends up in a shared mailbox. The business question is whether, for any supplier, the company can show who approved it, who validated each bank change and which account the first settlement went to.

That chain is a known target for fraud. The FBI's IC3 has warned about business email compromise and advises verifying payment changes by phone using previously known numbers, not numbers supplied in the request. Companies that follow that advice tend to leave a record of each callback somewhere, which is exactly what the packet asks about.

What metadata can a referral partner collect about supplier-to-first-payment without reading private content?

A short packet, filled in from conversation with the AP manager or procurement lead:

  • Systems and roles. Coupa for onboarding and supplier-submitted changes; Oracle for supplier master, bank accounts and payments; Outlook for the AP shared mailbox. Note any other tool that touches bank details.
  • Periods. When each system went live, and what happened to the history from the previous system.
  • Volumes. New suppliers per year, bank changes per year, payment runs per month. Rough figures are enough.
  • Routes. Which routes can change bank details: change request, portal update, import, integration. Ask which is most common.
  • Audit settings. Whether supplier audit history is enabled, since when, and whether bank fields are masked.
  • Mail retention. The retention rule for the AP shared mailbox, and whether callback notes are filed anywhere else.
  • Owners. Procurement for onboarding, the AP manager for changes and payments, IT for mailbox retention.
  • Unknowns. Mark anything the client is unsure about, especially whether imports have ever been used for bank changes.

A sample packet (Illustrative)

The values describe a fictional 420-person distributor. Replace them with your client's answers.

Packet fieldCoupa (onboarding)Oracle (bank-change validation and settlement)Outlook (callbacks and requests)
Object typesSupplier registrations, payment account submissionsSupplier master, bank account change requests, paymentsAP shared mailbox messages, callback notes
Years held2019 to today2017 to todayMailbox retention set by IT
Rough volumeAbout 600 new suppliers a yearAbout 250 bank changes a yearNot counted
Approval markerPayment account held for customer reviewChange request approver; audit history if enabledNone; free text only
OwnerProcurement operations leadAP managerIT messaging admin
UnknownShare of changes submitted through the portalWhether imports were ever used for bank changesWhether callback notes are filed elsewhere

Each cell reflects documented behavior: Coupa holds supplier payment details in pending review until the customer approves them; Oracle can route bank account changes through a change request, keeps audit history only when audit policies are enabled, and does not raise change requests for import or REST updates; and Exchange Online keeps message trace data for 90 days, which says nothing about how long the mailbox itself is kept.

The bank change after approval

The graphic shows three routes for one bank change after a supplier was approved on January 8, all reaching a first payment on February 2 (Illustrative). Only two leave an approval record. Ask the AP manager which routes their company allows and how often each is used, and note the answer. Do not ask how controls work in detail; that belongs in SourceX's review under the company's own security rules.

The Outlook inventory template covers mailbox fields in more detail, and procurement and vendor workflows describes the wider record set. If the company is replacing its ERP, the ERP replacement handoff checklist flags which history tends to be left behind.

Who can sponsor the introduction

Supplier records sit with procurement, payments with finance and mail with IT, so the sponsor is normally the CFO, and the CEO, usually the owner at an owner-led company, authorizes a licensing discussion. An AP manager can tell you everything in the packet; they usually cannot authorize licensing payment control records.

Check before introducing:

  • 50+ full-time employees at peak, contractors excluded, with a documented operating history.
  • The company controls these records and its supplier contracts do not prohibit licensing derived data.
  • A finance executive agrees to a first call.
  • 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.

Unknown until SourceX reviews it: what must be excluded for security reasons, how supplier and employee details are de-identified, which periods a buyer would value and what the company would be paid. Bank details and control specifics would be handled under the company's own security review, and a company may reasonably keep parts of this record set out of scope. If the company you have in mind is one of your own suppliers, read can I refer a supplier my company buys from first. The systems hub lists other record locations.

Go deeper on supplier-to-first-payment records

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 which routes can change a supplier's bank details and name the finance executive who owns them, register as a partner, confirm who qualifies and read the terms before you introduce them.

  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 this page about introducing suppliers to SourceX?

No. It is about introducing a company whose own records describe how it onboards and pays its suppliers. If you want to introduce a supplier your company buys from, a separate question page covers that.

Should bank details ever appear in an introduction?

Never. Bank numbers, supplier contacts and the specifics of payment controls stay with the company. An introduction needs counts, date ranges, system names, the approval route and the owner, nothing more.

Do email records really matter if the ERP has an audit trail?

Often they hold the only evidence of the callback, the supplier's request and the reason for an exception. Whether any of it can be included is decided later under the company's own security and privacy review.

Sources

  1. refer.sourcex.si/terms
  2. docs.oracle.com/en/cloud/saas/procurement/26a/oaprc/internal…
  3. docs.oracle.com/en/cloud/saas/procurement/25d/oaprc/supplier…
  4. compass.coupa.com/en-us/products/product-documentation/supplie…
  5. learn.microsoft.com/en-us/exchange/monitoring/trace-an-email-mes…
  6. ic3.gov/PSA/2016/PSA160614

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