Supplier-to-first-payment completeness scorecard: nine metadata checks for the late bank change, scored pass, partial or fail

Short answer

A supplier-to-first-payment trail usually breaks at a bank-detail change made after the vendor was approved and entered by a route that leaves no approval record. Companies tend to approve new vendors carefully; fewer can show the same care for a change two weeks later, just before the first payment. This scorecard turns that weak point and its neighbors into nine checks a partner can score in one call from metadata alone, each marked pass, partial or fail, with a total that describes the trail before anyone promises anything.

Visual briefFull-size diagram
Nine checks tick down a list (four pass, four partial, one fail on the entry route) while a semicircular gauge sweeps to 12 of 18 points, or 67%.
Illustrative scorecard for a fictional wholesaler. The one fail is bank changes entered by import with no change request.

This scorecard is part of the supplier-to-first-payment guide. Use it once the company has named its systems, and before you describe the opportunity to anyone.

Why this trail is worth scoring

Fraudulent payment-change requests are a long-documented business email compromise pattern. The FBI's Internet Crime Complaint Center warns about these schemes and advises that phone verification use previously known numbers, not numbers given in the email. A company that records whether it did that, for each change, holds informative decision records: who asked, what was checked, who approved and what happened to the money. A company that did the checks but recorded them nowhere holds a payment history with the decisions missing. The scorecard tells the two apart without anyone opening a vendor file.

How the scorecard works

Each check earns 2 points for a pass, 1 for a partial and 0 for a fail or unknown, for a maximum of 18. Three rules apply:

  • Metadata only. Ask whether a record exists, in which system, from which year and who owns it. If answering would mean opening a vendor record or an email, mark the check unknown.
  • Date every mark. "Pass from 2022" is a different trail from "pass since go-live." Write the year beside the mark.
  • Name the source. Record which role answered, so SourceX knows whom to ask later.

The nine checks

CheckAreaHow to check at metadata levelPassPartialFail
1. System yearsCoverageAsk the years held in the supplier portal, the ERP vendor master and the AP inboxAll three overlap for 3+ yearsOverlap under 3 yearsOne source holds nothing for the period
2. Change volumeCoverageAsk roughly how many vendor bank changes happen a yearKnown within a rangeKnown for recent years onlyUnknown
3. Supplier number on evidenceLinkageAsk whether request emails and call notes carry the supplier numberAlways, by ruleSometimesFiled by date or clerk only
4. Entry routeLinkageAsk which routes can save a bank change: change request, portal approval, import, integrationChange request or portal approval onlyPortal approval copied into the ERP by handImports or integrations with no request
5. TimingTimestampsAsk whether approval dates are recorded and compared with the payment runApproved before the run, datedApproved the same day as paymentApproval date unknown
6. Field historyTimestampsAsk whether audit history is on for vendor bank fields, and since whenOn, with a known start dateOn, values masked or owner changes untrackedNever enabled
7. Verification callOutcomesAsk where a call to a known number is loggedLogged against the change with date and callerMentioned in an email threadNot recorded
8. Proof documentOutcomesAsk where a bank letter or voided check is keptAttached in the portalAttachment in a mailboxNone collected
9. Inbox retentionGapsAsk the retention rule for the AP shared inboxKnown, and longer than the payment history neededKnown but shortUnknown

The late bank-change test

One scenario exercises most of the scorecard: a vendor's bank details change after approval and before the first payment. Vendor documentation shows why the same change can leave three very different trails.

Oracle's procurement documentation says vendor bank account changes can require approval through a change request, and further changes wait while one is pending, but that creation and updates through import and REST services do not raise change requests. Coupa's documentation says 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.

Route the change tookWhat the trail holdsChecks it affects
ERP change requestRequester, approver, dates; further changes blocked while pending4 and 5 pass
Portal update, approved by the customerPending review, approval, often a proof document; ERP copy may lack a reference4 partial if copied by hand; 8 pass
Import or integration updateA new value and a timestamp; no request, no approver4 fails; 5 usually unknown

Ask the AP manager which routes the company allows and roughly how often each is used. Do not ask how controls work in detail; that belongs in SourceX's review under the company's own security rules.

Field history: what audit settings can and cannot show

Check 6 needs care. Oracle's audit documentation says supplier audit history has to be enabled through audit policies, and that with masking on only masked bank account numbers and IBANs appear. It also says bank account owners, intermediary accounts and attachments are not audit-tracked. So a company can have audit history switched on and still be unable to show who changed an account owner or when a proof document was replaced. Score that as partial, not pass.

Check 9 has a similar trap. Microsoft documents that Exchange Online message trace data is kept for 90 days and cannot be changed. That is delivery metadata, not mailbox content; mailbox retention is a separate policy set by IT. A company that says "we can trace emails" may be describing the 90-day trace, not a retained inbox.

A scored example (Illustrative)

A fictional 380-person electrical wholesaler with about 300 vendor bank changes a year, scored from one call with its AP manager and IT admin.

CheckMarkPointsNote
1. System yearsPass2Portal, ERP and inbox overlap from 2019
2. Change volumePartial1About 300 a year, recent years only
3. Supplier number on evidencePartial1In email subjects since 2023
4. Entry routeFail0Quarterly imports used for bulk updates
5. TimingPass2Approval dated before each payment run
6. Field historyPartial1Audit on since 2021, values masked
7. Verification callPartial1Noted in email threads, not on the change
8. Proof documentPass2Bank letters attached in the portal
9. Inbox retentionPass2Seven-year retention on the AP inbox
Total4 pass, 4 partial, 1 fail12 of 1867% complete

The sentence it produces is what goes into an introduction: "Portal approvals and proof from 2019; supplier numbers on emails from 2023; imports used for some bank changes; audit history from 2021." The record chain shows how the keys behind checks 3 and 4 join, the missing-context comparison shows what a payables export loses without them, and the vendor bank-detail change verification page covers the record type on its own.

Qualifying the company behind the score

A score describes the trail; it does not qualify the company. Confirm the baseline: 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license the records, and an authorized contact: the CEO (in an owner-run company, usually the owner), with the CFO involved since these records touch payment controls. 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: which records must be excluded for security reasons, how vendor and employee details would be de-identified, whether vendor contracts allow licensing, and what the company would be paid. Partners never see bank details. For how reviews assess records more broadly, see what a data audit is and data quality due diligence; the reward mechanics are on rewards.

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 scorecard yields a dated sentence the AP manager agrees with and the CFO will take a call, register as a partner, check 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

Does a low score mean the company should not be introduced?

No. SourceX sets no pass mark. A company with a long history and a few partial checks can still be worth a conversation; the score makes sure the introduction describes the trail accurately.

Should the partner ask how payment controls work in detail?

No. Ask only whether each record exists, where, from when and who owns it. How controls operate is a security matter for the company and for SourceX's review under the company's own rules.

Why weight every check equally?

Because a partner cannot judge which gap matters most to a buyer. Equal points keep the score simple, and the per-check marks carry the detail a reviewer actually reads.

Sources

  1. ic3.gov/PSA/2016/PSA160614
  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. 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