# Supplier-to-first-payment completeness scorecard | SourceX

Canonical: https://refer.sourcex.si/resources/supplier-to-first-payment-completeness-checklist
Last updated: 2026-11-04

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.

This scorecard is part of the [supplier-to-first-payment guide](/guides/chain-supplier-to-first-payment). 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

| Check | Area | How to check at metadata level | Pass | Partial | Fail |
|---|---|---|---|---|---|
| 1. System years | Coverage | Ask the years held in the supplier portal, the ERP vendor master and the AP inbox | All three overlap for 3+ years | Overlap under 3 years | One source holds nothing for the period |
| 2. Change volume | Coverage | Ask roughly how many vendor bank changes happen a year | Known within a range | Known for recent years only | Unknown |
| 3. Supplier number on evidence | Linkage | Ask whether request emails and call notes carry the supplier number | Always, by rule | Sometimes | Filed by date or clerk only |
| 4. Entry route | Linkage | Ask which routes can save a bank change: change request, portal approval, import, integration | Change request or portal approval only | Portal approval copied into the ERP by hand | Imports or integrations with no request |
| 5. Timing | Timestamps | Ask whether approval dates are recorded and compared with the payment run | Approved before the run, dated | Approved the same day as payment | Approval date unknown |
| 6. Field history | Timestamps | Ask whether audit history is on for vendor bank fields, and since when | On, with a known start date | On, values masked or owner changes untracked | Never enabled |
| 7. Verification call | Outcomes | Ask where a call to a known number is logged | Logged against the change with date and caller | Mentioned in an email thread | Not recorded |
| 8. Proof document | Outcomes | Ask where a bank letter or voided check is kept | Attached in the portal | Attachment in a mailbox | None collected |
| 9. Inbox retention | Gaps | Ask the retention rule for the AP shared inbox | Known, and longer than the payment history needed | Known but short | Unknown |

## 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 took | What the trail holds | Checks it affects |
|---|---|---|
| ERP change request | Requester, approver, dates; further changes blocked while pending | 4 and 5 pass |
| Portal update, approved by the customer | Pending review, approval, often a proof document; ERP copy may lack a reference | 4 partial if copied by hand; 8 pass |
| Import or integration update | A new value and a timestamp; no request, no approver | 4 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.

| Check | Mark | Points | Note |
|---|---|---|---|
| 1. System years | Pass | 2 | Portal, ERP and inbox overlap from 2019 |
| 2. Change volume | Partial | 1 | About 300 a year, recent years only |
| 3. Supplier number on evidence | Partial | 1 | In email subjects since 2023 |
| 4. Entry route | Fail | 0 | Quarterly imports used for bulk updates |
| 5. Timing | Pass | 2 | Approval dated before each payment run |
| 6. Field history | Partial | 1 | Audit on since 2021, values masked |
| 7. Verification call | Partial | 1 | Noted in email threads, not on the change |
| 8. Proof document | Pass | 2 | Bank letters attached in the portal |
| 9. Inbox retention | Pass | 2 | Seven-year retention on the AP inbox |
| Total | 4 pass, 4 partial, 1 fail | 12 of 18 | 67% 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](/guides/supplier-to-first-payment-record-linkage) shows how the keys behind checks 3 and 4 join, the [missing-context comparison](/guides/supplier-to-first-payment-missing-context) shows what a payables export loses without them, and the [vendor bank-detail change verification](/data-types/vendor-bank-account-change-verification-process) 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](/proof/what-is-a-data-audit) and [data quality due diligence](/resources/data-quality-due-diligence); the reward mechanics are on [rewards](/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](/register), check [who qualifies](/who-qualifies) and read the [terms](/terms) before you introduce them.

## Sources

- https://www.ic3.gov/PSA/2016/PSA160614
- https://docs.oracle.com/en/cloud/saas/procurement/26a/oaprc/internal-supplier-profile-bank-account-change.html
- https://docs.oracle.com/en/cloud/saas/procurement/25d/oaprc/supplier-profile-audit-history-setup-and-reporting.html
- https://compass.coupa.com/en-us/products/product-documentation/supplier-resources/for-suppliers/coupa-supplier-portal/set-up-the-csp/financial-setup/view-and-manage-payment-method-information
- https://learn.microsoft.com/en-us/exchange/monitoring/trace-an-email-message/message-trace-faq
- https://refer.sourcex.si/terms
