This comparison is part of the supplier-to-first-payment guide. Here one Illustrative vendor is read twice: first as the payables team's export row, then with the surrounding context restored.
Before: the payables export row on its own
A fictional 610-person food manufacturer approves a new packaging vendor, V-33150, in March. Its bank details change once before the first invoice is paid.
What the Oracle export says about V-33150:
| Field | Value in the export |
|---|---|
| Vendor | V-33150, created March 4 |
| Bank account | Current account ending 4471 (masked) |
| Account history | One prior account, replaced March 19 |
| How the change was saved | Last updated by an integration user |
| Change request | None |
| First payment | March 28, cleared |
A reader of this row concludes that a vendor was set up, its bank account changed once, and it was paid without trouble. That conclusion is plausible and possibly right. But the row cannot say whether anyone checked the March 19 change. "Last updated by an integration user" and "no change request" fit a careful process and a careless one equally well. Oracle's documentation explains why: supplier bank account changes can require approval through a change request, but creation and updates through import and REST services do not raise change requests. The absence of a request is a property of the entry route, not evidence of a skipped check.
After: the same vendor with portal and inbox context
Add the Coupa supplier portal and the AP shared inbox in Outlook, and the same three weeks read as one history (Illustrative).
| Date | Source | What it adds |
|---|---|---|
| March 2 | Coupa | Registration approved by the procurement lead, with the approver's name |
| March 4 | Oracle | Vendor V-33150 created from the approved registration |
| March 17 | Coupa | Vendor's portal user submits new bank details after a change of bank; details held in pending review |
| March 17 | Coupa | Bank letter uploaded as proof |
| March 18 | Outlook | AP clerk's note: verification call made to the phone number on file, change confirmed |
| March 18 | Coupa | AP manager approves the pending payment account |
| March 19 | Oracle | Integration copies the approved account into the vendor master |
| March 28 | Oracle | First payment released and cleared |
Now the change has a requester, a proof document, a verification call and an approver. Coupa's documentation describes this behavior: supplier payment account details must be approved by the customer before payment and sit in pending review until then, and a supplier changing bank information needs multi-factor authentication and may have to upload proof such as a voided check or bank letter. None of that reaches the Oracle row, because the integration that carried the approved account across carried no reference to the approval.
What the payables row loses, and where each piece lives
| Question a reviewer would ask | Oracle export alone | Where the context lives | How long it tends to survive |
|---|---|---|---|
| When was the vendor approved, and by whom? | Creation date only | Coupa registration approval | As long as the portal history is kept |
| Did bank details change before the first payment? | Yes, if audit history was on | Oracle audit history; Coupa payment account history | From the date audit policies were enabled |
| Who asked for the change? | No | Coupa portal user, or the email sender | Portal history; mailbox retention rule |
| Was the change verified, and how? | No | Clerk's note in the shared inbox | Mailbox retention rule |
| Was proof collected? | No | Bank letter in Coupa or an email attachment | Portal or mailbox retention |
| Which route was used to save it? | Partly: the user who saved it | Integration logs, change request records | Varies |
| Was the first payment correct? | Payment status | Payment status plus the verification behind it | Finance retention policy |
Three rows explain most lost context: the requester, the verification and the proof. Each lives outside the ERP. Oracle's audit documentation adds a limit even inside it: audit history has to be enabled through audit policies, masking shows only masked account numbers, and bank account owners, intermediary accounts and attachments are not audit-tracked.
The inbox rows carry a retention question. Microsoft documents that Exchange Online message trace data is kept for 90 days and that this period cannot be changed. Message trace is delivery metadata, not mailbox content, and mailbox retention is a separate policy. So ask what the retention rule is for the AP shared inbox, because that rule decides how far back the verification evidence goes.
The bank change after approval: why the gap sits there
Companies tend to document onboarding carefully, because it is a planned step with a named approver. A bank change two weeks later is unplanned, arrives by portal or email, and is often handled by whoever is on AP that day. That is why the context gap concentrates there. The record chain names the key that would join each hop, and the completeness checklist scores whether a company's history carries it.
For a partner, the useful output is a sentence such as "portal approvals and proof documents from 2020; verification notes in the shared inbox, kept three years; Oracle audit history on since 2022." The broader question of what data tends to be missing is covered in what data is missing from AI training.
Scoping the gap with the company's owners
Ask each owner which rows of the gap table their system fills, and from which year: the procurement lead for registrations and portal approvals, the AP manager for bank changes, verification notes and payments, and the IT messaging admin for inbox retention. None of them needs to show a record.
The company baseline: 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license the records, and an authorized contact: the CEO, or the owner in an owner-run company. 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 vendor and employee details would be de-identified, and what a buyer would want. Bank details and control specifics never pass through the partner. If the client runs a different ERP, the same gap applies; the NetSuite partner page and NetSuite data after cancellation cover that side, and what a referral partner is explains the role.
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's owners can say which rows of the gap table their systems fill, and since when, register as a partner, check who qualifies and read the terms before you introduce the finance executive.