This worked case is part of the supplier onboarding exceptions guide. It follows one Illustrative case from request to the ninetieth day, decision by decision, and ends with questions that help an advisor spot similar files at a client.
The setup: a new supplier that looks like an old one
Illustrative. A fictional 450-person food packaging manufacturer wants to add a resin supplier. Its vendor master already contains a supplier whose legal name differs by one letter and a suffix ("Supply LLC" against "Supplies Inc"). Nobody yet knows whether the two are the same company, an affiliate, or unrelated businesses with similar names.
This is a real judgment, not a formality. If the request is a duplicate and gets approved, payments can be split across two records and spend reporting breaks. If it is a different company and gets merged, invoices go to the wrong legal entity. Either mistake is expensive, and only evidence settles it.
Decision by decision (Illustrative)
All days, names and outcomes are invented for this page.
| Day | Who decided | What they decided | Record left behind |
|---|---|---|---|
| 1 | Buyer in procurement | Request the new supplier | Supplier request in the portal |
| 1 | Supplier operations analyst | Pause: the duplicate check lists the existing supplier as a likely match | Duplicate-check result naming the match |
| 2 | Supplier operations analyst | Ask the supplier for a W-9, certificate of formation and remittance letter | Document request with due date |
| 3 | Compliance analyst | Review a potential sanctions match on the new name, scored below an exact hit | Screening record |
| 5 | Compliance analyst | Clear it as a false positive after comparing address, country and registration | Screening disposition with reason |
| 6 | AP tax specialist | Run the name and TIN through TIN Matching; result code 0, a TIN different from the existing supplier's | TIN check result |
| 8 | AP specialist | Confirm bank details by calling a number from an independent source | Bank verification note |
| 9 | Supplier operations head | Accept as a separate legal entity, linked to the existing record as an affiliate | Acceptance note with approver |
| 90 | AP | Confirm the first three invoices paid to the new entity, none against the older one | Payment history |
Nine steps, six roles across three teams, nine records. A vendor master that shows only "active, day 9" hides every decision that made the case worth studying.
Why each step is defensible
Each step reflects documented tool behavior, which is why the sequence can be checked rather than taken on trust.
- The pause on day 1. SAP's Ariba documentation describes approvers of an external supplier request seeing existing suppliers that match it, so they can deny duplicates and approve only genuinely new suppliers. The duplicate-check result is the record of that prompt.
- The screening review on days 3 to 5. OFAC's Sanctions List Search applies fuzzy logic to the name field only. A score of 100 is an exact match; lower scores are potential matches, and OFAC says users must set their own thresholds because it cannot recommend one. A near-name hit therefore always needs a human disposition, and the reason written on day 5 is the evidence.
- The tax check on day 6. IRS TIN Matching lets payers that file information returns check a name and TIN combination. Code 0 means the combination matches IRS records; code 3 means it does not. A different, matching TIN is the strongest single sign that two similar names are two companies.
- The callback on day 8. Calling a number found independently, not one on the remittance letter, follows the separate trail described in vendor bank account change verification.
SAPThe day-90 row is the checked result. Without it, the file proves only that someone decided. With it, the file shows the decision held in practice.
What makes this sequence useful evidence
Records like these capture a judgment with a verifiable answer: same company or not, cleared or not, accepted or not, each with its supporting evidence and a named approver. That is uncommon in business data, where most records show only the final state. A trail from flag to evidence to decision to outcome documents how a company handles cases its procedures did not resolve automatically, which is the kind of multi-step work record SourceX licenses from companies for AI training and evaluation. Whether a given company's files can be licensed depends on its rights review, not on how useful the records look. The logistics exceptions guide applies the same problem, action and result test to shipments.
The weak points are predictable. The duplicate-check result is often shown on screen and never logged. Screening dispositions may record "cleared" with no reason. The callback may live only in an AP specialist's notebook. The system map for onboarding records shows which identifiers tie these pieces together and where the chain usually breaks.
Spotting similar cases at a client
A supplier management advisor can find cases like this without opening one file. Ask the supplier operations head:
- Roughly how many onboarding requests a year are paused, and for what reasons?
- When the portal flags a likely duplicate, is the flag and the approver's response stored?
- Do screening dispositions carry a written reason, and which team keeps them?
- Is the TIN check result recorded as a code, or only as a checkbox?
- Are affiliate links between supplier records captured when a near-duplicate is accepted?
- How many years of paused and rejected requests still exist?
A company that can answer most of these with "yes, since about 2019" is describing a strong exception history. If the client is actually a supplier you buy from, read whether you can refer a supplier your company buys from first.
Qualification and what stays unknown
The introduced company needs 50+ full-time employees at peak (contractors excluded), documented operating history, rights to license 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 90% of the data is in English.
Unknown until SourceX reviews it: whether screening and tax records can be included at all, how supplier identities would be de-identified, which cases a buyer would want and whether an offer follows. Partners never handle the files; discovery stays at what, how much, how long, which system and who owns it. For who should receive the introduction, see who can license onboarding exception records, and the onboarding referral brief template puts the answers on one page.
Next step
Refer a company. Earn up to $100,000. Default reward: 25% of Actual Supplier Payout, capped at $100,000 cumulatively per referred company. Eligibility and payment conditions apply, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.
If a client can trace its paused onboarding cases from flag to acceptance with a reason at each step, register as a partner, check it against who qualifies and read the program terms before introducing its supplier operations head.