Record for this area

Supplier onboarding

The path from what a machine is documented doing to the party holding the record that makes the result official, with how well each step is backed. Where the sources settled nothing, the step says so.

What a machine is documented doing

Established by the evidence. EXECUTION on O-1 by three offerings; none evidences setting admission status; none evidences any operation on a block or hold state
The record it touches

Established by the evidence. O-1 supplier master record; O-2 spend-authorized business relationship; O-5 screening status; O-7 supplier block/hold state
What still has to happen first

Established by the evidence. WITHHELD RATHER THAN ABSENT - the spend-authorized relationship is maintained as None unless a separate human approval is given

Assumed, because nothing says otherwise no document describes a step here; that it stops is inferred from nothing saying otherwise The agentic capabilities never reach the object at all

the application automatically creates the supplier in the Supplier Master
the source's own words, quoted exactly
What makes the change count

Established by the evidence. The IRS prescribes Form W-9; Companies House prescribes the registration state
Who holds the official record

Established by the evidence. Oracle's Supplier Master and the customer's ERP hold O-1; the UK debarment list, EU Annex I, EDES and the World Bank listing hold O-5
What the area relies on

Established by the evidence. UK debarment list under the Procurement Act 2023, Part 3, Chapter 6, Section 62; System for Award Management (SAM.gov) entity registration; Annex I to Council Regulation (EU) No 269/2014 — list of persons and entities subject to restrictive measures; Early Detection and Exclusion System (EDES) database of excluded persons and entities; UK register of companies — legal-entity registration state; Listing of Ineligible Firms & Individuals

The action that makes it official Creation of the supplier record in the Supplier Master (O-1); publication on the debarment list (O-5/O-7) Done by SOFTWARE for O-1; a Minister of the Crown for O-5. It counts because of a record state held by the vendor's own master. A machine can do this, on a path the buyer configured in advance rather than by any judgement of its own.

What this area could not settle

What could this area not settle?

What this area recorded against its own findings, in its own words.

Recorded against itself by this area

5 vendor hosts blocked; 22 nil routes; the buying organisation's own ERP or MDM is ABSENT from the infrastructure examined entirely (NR-22), which is the one custodian that could refute the area's central claim

7 dated acts by institutions or vendors

22 searches recorded here that found nothing

6 capabilities examined

8 systems examined

Can the act be undone, and by whom?

not observable We looked and the sources we inspected did not settle it.

Question by question

What did the evidence settle, dimension by dimension?

Eighteen structural dimensions, each carrying its own evidence state and what it does not establish.

What the evidence settled for this area, question by question
Question asked	What the evidence says	What it does not tell you
consequential-object `D01`	Established by the evidence. O-1 supplier master record; O-2 spend-authorized business relationship; O-5 screening status; O-7 supplier block/hold state	Not recorded by the method used for this area
object-holder `D02`	Established by the evidence. Oracle's Supplier Master and the customer's ERP hold O-1; the UK debarment list, EU Annex I, EDES and the World Bank listing hold O-5	THE BUYER'S OWN ERP OR MDM IS ABSENT FROM POPULATION B ENTIRELY (NR-22) - the one custodian that could refute TA-06.
grammar-or-form-setter `D03`	Established by the evidence. The IRS prescribes Form W-9; Companies House prescribes the registration state	TA-05's sharpest instance: the IRS states it on the form - Give form to the requester. Do not send to the IRS.
composer `D04`	Established by the evidence. The supplier composes the form content; product automation composes the master record	Not recorded by the method used for this area
validator `D05`	Established by the evidence. The payer's own check; the investigation behind a debarment case	Not recorded by the method used for this area
binder `D06`	Established by the evidence. MACHINE-PERFORMED ON O-1 - the application automatically creates the supplier in the Supplier Master; PUBLICATION on the debarment list for O-5/O-7	ONE OF TWO AREAS where a machine performs the binding act.
deterministic-automation `D07`	Established by the evidence. YES for O-1, on a configured deterministic path: the application automatically creates the supplier in the Supplier Master	An unnamed background product workflow that claims no agent and is named as none. The artifact carries NO page-visible date and names no customer and no deployment.
agentic-capability `D08`	A source states this does not happen: A source addressed it and said no.. Named agents in the supplier portal name NO record in scope for the area anywhere in their own release documentation - the agentic capabilities never reach the object at all	Explicitly absent ON THE AREA OBJECTS, established that the agents exist. The distinction is the area's own.
furthest-deterministic-action `D09`	Established by the evidence. Creation of the supplier record in the Supplier Master - THE BINDING ACT for O-1	Not recorded by the method used for this area
furthest-agentic-action `D10`	A source states this does not happen: A source addressed it and said no.. No record in scope for the area is named in any inspected agentic release documentation	Not recorded by the method used for this area
reversibility `D11`	Not answered by the evidence we checked: We looked and the sources we inspected did not settle it.. Not coded and not observable We looked and the sources we inspected did not settle it.	Not recorded by the method used for this area
externality-radius `D12`	Established by the evidence. Publication on the UK debarment list, EU Annex I, EDES and the World Bank listing binds parties that never transact with the publishing institution	Not recorded by the method used for this area
counterparty-assent `D13`	A source states this does not happen: A source addressed it and said no.. For O-1 no counterparty assents - the application creates the record. For O-2 the buying organisation's approver is required and the relationship is maintained as None until then	WITHHELD RATHER THAN ABSENT is the area's own phrase for O-2.
rule-codifiability `D14`	Established by the evidence. For O-1 the binding act is performed by product automation without a described human judgment	Documented product behaviour is not deployment. The artifact names no customer, no deployment and no date.
institutional-closure `D15`	Established by the evidence. For O-5/O-7, independent contracting authorities must recognize the published state	Not recorded by the method used for this area
authoritative-state-centralization `D16`	Established by the evidence. SPLIT: the vendor's own Supplier Master and the customer ERP hold O-1; institutions hold O-5	5 vendor hosts blocked; 22 nil routes.
consequence-of-error `D17`	Not answered by the evidence we checked: We looked and the sources we inspected did not settle it.. What follows an erroneously created supplier master record is not established We looked and the sources we inspected did not settle it.	Not recorded by the method used for this area
accountability `D18`	Not answered by the evidence we checked: We looked and the sources we inspected did not settle it.. No stable answerable party across the object's life We looked and the sources we inspected did not settle it.	A Minister of the Crown for O-5 is a named authority for one act on one object in one jurisdiction.

Capabilities

What is each capability evidenced doing?

The mode records that a named subject performs an operation. It does not record what kind of performer that subject is, and several rows disclaim an agentic mechanism in their own limitation.

Capabilities examined in this area
Capability	How far it goes	What it does	Human work still needed	What this does not tell you
Supplier creation post registration request approval, Oracle Fusion Cloud Procurement supplier model. PASSAGE: 'The supplier number is assigned from the next sequential number, maintained in Supplier Numbering setup.' `C-001`	performs the operation itself	Creates the supplier record in the Supplier Master and assigns it a supplier number; on approval of a separate spend authorization request, creates a supplier site per registered address. PASSAGE: 'After the spend authorization request is approved, a supplier site is created for each address in the procurement BU for which the registration request was created.'	Approval of the spend authorization request, without which the entitlement to transact is withheld. PASSAGE: 'Unless the spend authorization request is approved, the supplier's business relationship is maintained as None.'	Establishes documented product behaviour on O-1 and the withholding of O-2. Establishes NO deployment, no named customer, no date, and no operation on O-3 or O-7. T-15 note: the mode rests on the verb 'creates the supplier in the Supplier Master', not on any capability name; no agent is named in this flow and none is claimed.
Zip Supplier Onboarding, including one-click ERP supplier creation and automated supplier assessment. PASSAGE: 'Use AI to automate third-party checks like TIN, VAT, OFAC, D&B, and bank account verification' `C-002`	performs the operation itself	Creates and updates supplier records in the customer's ERP; separately runs third-party checks against tax, sanctions, business-data and bank-account sources, which are checks rather than writes.	Not stated. No passage on the inspected artifact states that a person approves a supplier record or a data update.	Establishes a claimed operation on O-1 in an unnamed ERP. Establishes NO operation on O-2, and no state change on O-3 — the bank-account item is verification, not a write. T-15 note: the mode rests on the verbs 'create and update supplier records', not on the word 'Automatically' and not on any agent name; the vendor's agent names are excluded from the mode evidence by design.
HighRadius Supplier Onboarding, including bank-account and tax verification. PASSAGE: 'Confirms the active status and legal ownership of the bank account' `C-003`	performs the operation itself	Pushes supplier details and bank information into the ERP; verifies bank-account status and ownership; checks tax data against external authorities. PASSAGE: 'Verifies against internal records or external tax authorities for compliance'	Not established. The artifact states the details pushed are 'approved' and does not state what or who approves them, which is exactly the O-2 question this area is about.	Establishes a claimed write to O-1 and O-3. Establishes NO operation on O-2 — the artifact presupposes approval without naming its source — and nothing about O-7. This is Stage 2 calibration case CAL-5 carried forward: a strong operation passage on an undated artifact.
Supplier Portal Advisor AI Agent, Oracle Fusion Cloud Procurement 25C. PASSAGE: 'The Supplier Portal Advisor AI Agent helps resolve this by providing a chat-based experience that answers policy, process, and how-to questions directly within the application based on your support content.' `C-004`	advises only	Answers policy, process and how-to questions from uploaded support content and links to documentation. PASSAGE: 'It also links to documentation when more detail is needed, improving supplier success while reducing the support burden on your team.'	All of it. Every state change on every object in section 5 remains with whatever else performs it; the artifact attributes none to this agent.	Establishes that this agent's evidenced operation is answering questions. Establishes NOTHING about the agent's quality, adoption or roadmap, and nothing about whether Oracle ships other capabilities that do act on section 5 objects — C-001 shows it does. The cutoff value is evidenced under both readings: if the agent did not exist at 2025-12-31 it was not qualified, and if it did exist its evidenced operation was advisory, so it was not qualified either way.
Not established. SAP Ariba Supplier Lifecycle and Performance, and SAP Master Data Integration supplier replication to SAP S/4HANA, were the targets; no artifact describing either was retrieved. `C-005`	the sources do not settle whether this belongs in scope	Not recorded by the method used for this area	Not recorded by the method used for this area	This row establishes nothing about SAP. It records that the area's largest expected long-standing-integration estate could not be opened. Its unresolved value is NOT a finding about the product and must never be read as one.
Not established. The Coupa Supplier Portal onboarding flow and its remit-to record were the targets. `C-006`	the sources do not settle whether this belongs in scope	Not recorded by the method used for this area	Not recorded by the method used for this area	This row establishes nothing about Coupa. The most area-relevant lead found in the whole collection — an automatically created remit-to record, which would be an operation on O-3 — could not be confirmed against an inspected artifact and is therefore not recorded as evidence anywhere in this area.

Infrastructure

Whose systems does this area run on?

What part each system plays was decided by what it does to the area's records, never by what kind of company runs it. Where the sources leave that open the entry says so, because an open question is not a kind of system.

Systems examined in this area
System	Who runs it	What part it plays	What it does to the official record
Form W-9, Request for Taxpayer Identification Number and Certification (Rev. March 2024) `C-007`	Internal Revenue Service (United States Department of the Treasury)	form-defining-body	constructs-for
UK debarment list under the Procurement Act 2023, Part 3, Chapter 6, Section 62 `C-008`	Minister of the Crown, Cabinet Office (Debarment Review Service, Government Commercial Agency)	authoritative-register	creates; holds; mutates
System for Award Management (SAM.gov) entity registration `C-009`	General Services Administration (United States)	authoritative-register	holds; accepts-or-rejects
Annex I to Council Regulation (EU) No 269/2014 — list of persons and entities subject to restrictive measures `C-010`	Council of the European Union	authoritative-register	holds; mutates
Early Detection and Exclusion System (EDES) database of excluded persons and entities `C-011`	European Commission	authoritative-register	holds
UK register of companies — legal-entity registration state `C-012`	Companies House (United Kingdom)	authoritative-register	holds; accepts-or-rejects
Listing of Ineligible Firms & Individuals `C-013`	World Bank (Office of Suspension and Debarment; Sanctions Board)	authoritative-register	creates; holds; mutates
Verification of Payee service for SEPA credit transfers `C-014`	Payment service providers in the European Union, under Regulation (EU) 2024/886	not-applicable	none-established

Claims

What may be said from this area, and what may not?

Each one carries how far it is backed and, where it was recorded, the exact stronger sentence that may never be written from it.

CL-01 Observed

The United Kingdom operates a central debarment register whose entries oblige or permit every contracting authority to exclude a named supplier, and the register's approved current version, effective 17 November 2025, states on its own face that it will remain blank until a ministerial decision is made following an investigation.

The strongest thing against it None was found. The earlier Debarment List PDF versions were retrieved but yielded no extractable text (NR-21), so no earlier version was read.

What may not be said from this Never: 'the UK has debarred no suppliers', 'debarment is not being used', or any statement about the regime's effectiveness, intent or future use.

CL-02 Observed

In every case inspected in this area, the unit holding a state that alters whether a supplier may be transacted with is an institution that transacts with none of the suppliers that state binds.

The strongest thing against it The absent one. The frozen contract names the buying organisation's own ERP or MDM as a candidate holder, and no artifact naming a specific buyer's master was retrieved. If that unit were inspected the claim could fail.

What may not be said from this Never: 'authority in supplier onboarding sits with institutions', 'buyers do not hold the authoritative record', or any statement implying the estate was complete.

CL-03 Observed

Product automation that names no agent and claims none is documented creating the supplier master record itself and assigning it a number, while the state that permits transacting with that supplier is withheld pending a separate approval.

The strongest thing against it None was found. No inspected artifact describes a suite in which the same automation also sets the spend-authorized state.

What may not be said from this Never: 'ERPs automate supplier onboarding', 'creation is automated across the market', or any statement about how many buyers run this flow.

CL-04 Observed

Three participant offerings evidence writing to the supplier master record; none of the three evidences setting a supplier's admission status, and none evidences any operation on a supplier block, hold or deactivation state.

The strongest thing against it HighRadius states it pushes 'approved' supplier details without naming what approves them. If the approval were shown to be performed by the same product, the claim's second limb would weaken.

What may not be said from this Never: 'no product sets supplier admission status', 'agents cannot block suppliers', or any inference from these three to the class.

CL-05 Pattern

Across three vendors assessed independently, the artifacts that place an operation on a supplier record carry no page-visible date, and the artifacts that carry a page-visible date name no object of this area.

The strongest thing against it None was found within the retrievable vendor estate — but five vendor hosts were blocked outright, and a blocked host can neither confirm nor refute the pattern.

What may not be said from this Never: 'vendors conceal their capabilities', 'vendors do not publish dates', or any claim about vendor intent or about vendors not inspected.

CL-06 Observed

The body that prescribes the form of the taxpayer record on which a supplier's payment terms depend states on the form itself that the form is given to the requester and not sent to that body.

The strongest thing against it None was found.

What may not be said from this Never: 'tax authorities do not hold supplier data', which is false in general and is not what this evidences.

CL-07 Not established

No inspected artifact in this area evidences a machine-executed change to a supplier's admission status, to a remit-to record as a binding payment instruction, or to a supplier block, hold or deactivation state.

The strongest thing against it C-003 is the nearest approach: it evidences a push of supplier and bank details into an ERP, and fails only because the artifact does not state what approves them.

What may not be said from this Never: 'machines do not set supplier admission status', 'no agent can block a supplier', or any absence claim about the world rather than about the evidence.

CL-08 Not established

No participant offering in this area could be established as qualified at the frozen cutoff of 31 December 2025.

The strongest thing against it None applicable.

What may not be said from this Never: 'no supplier-onboarding capability existed at the end of 2025', which the evidence contradicts rather than supports.

CL-09 Hypothesis

The absence of dated vendor artifacts placing an operation on a supplier record may be a publishing practice rather than an absence of the capability, since the same vendors describe those operations plainly on undated pages.

The strongest thing against it An equally consistent explanation is that undated marketing pages describe intended rather than shipped behaviour, which would make the operation passages weaker rather than the dating practice meaningful. Nothing retrieved distinguishes the two.

What may not be said from this Never state or imply that vendors deliberately withhold dates, or that the capability is established.

CL-10 Observed

A capability shipped inside the supplier portal itself, and named as an agent, names no object of this area anywhere in its own release documentation.

The strongest thing against it None was found.

What may not be said from this Never: 'supplier-portal agents do nothing', or any evaluation of the capability's usefulness.

CL-11 Not established

No relationship is established between any institutional event in this series and any participant's behaviour.

The strongest thing against it None applicable.

What may not be said from this Never present any institutional event as a cause of, or a response to, any vendor capability.

Dated acts

What dated acts touch this area's records?

A list, in date order. It is not a timeline and carries no rate: the collection capped each publisher, so this is a floor on what was retrievable rather than a count of what occurred.

Dated acts touching this area
Date	Kind of act	Consequence recorded	Source
2025-02-24 `day precision`	institutional rule change	A central register comes into being whose entries prevent a supplier from being awarded public contracts for up to five years. PASSAGE: 'prevents the supplier from participating in any procurements or being awarded public contracts for up to 5 years'	source
2025-11-17 `day precision`	institutional rule change	The operative version of the register is approved and published with a column structure for supplier name, procurement organisation number, exclusion ground and cessation date, and with no supplier entered. PASSAGE: 'until a ministerial decision is made to add a supplier following an investigation, the list will remain blank.'	source
2024-03 `month precision`	institutional rule change	A new revision of the prescribed form becomes the current one that a payer must obtain and retain, with the payer bearing the withholding consequence of not obtaining it. PASSAGE: 'A payor must deduct, withhold, and deposit with IRS 24% of reportable payments made to that payee until the cause of the backup withholding is remedied.'	source
2025-02-24 `day precision`	institutional rule change	Named persons and entities are added to the list whose membership prohibits every EU person and company from making funds or economic resources available to them. The prohibition itself is established from the parent regulation, retrieved and inspected separately. PASSAGE: 'No funds or economic resources shall be made available, directly or indirectly, to or for the benefit of natural or legal persons, entities or bodies, or natural or legal persons, entities or bodies associated with them, as listed in Annex I.'	source
2025-05-20 `day precision`	institutional rule change	A further set of named persons and entities becomes subject to the same prohibition, on a date three months after EV-04. The register is amended repeatedly within the observation window rather than once.	source
2025-07-18 `day precision`	institutional rule change	A third amendment within the window, with adoption and Official Journal publication falling on different days, evidencing that the register's state changes on a published legal act rather than continuously.	source
2025-11-18 `day precision`	institutional rule change	A company's ability to maintain its own registration state becomes conditional on a verification step, and non-compliance is recorded against the register. PASSAGE: 'In the future, we'll publish a note against your name on the Companies House public register.'	source

Routes that returned nothing

Where did the search stop, and why?

A route that returned nothing establishes that the route returned nothing. A missing capture is a property of the archive, never a property of the world.

Retrieval routes that returned nothing
Source checked	How it failed	What was recorded
help.sap.com — SAP Ariba Cloud Integration Gateway, 'Integration Scenario: Create Supplier in SAP S/4HANA and Replicate to SAP Ariba'	Retrieved HTTP 200 but the response carried only a page title and no body content (client-rendered shell). No passage inspectable.	Not recorded by the method used for this area
community.sap.com — SAP-authored article on supplier onboarding in SAP Ariba SLP	HTTP 403 Forbidden.	Not recorded by the method used for this area
docs.coupa.com — Coupa Supplier Portal release notes (two distinct paths attempted)	Both paths returned a browser-compatibility notice and no release content.	Not recorded by the method used for this area
coupa.com — newsroom release on agentic AI capabilities	HTTP 403 Forbidden.	Not recorded by the method used for this area
oracle.com/news — Oracle press announcements on AI agents across Fusion Cloud Applications, October 2025	HTTP 403 Forbidden.	Not recorded by the method used for this area
apexanalytix.com — supplier bank account validation product estate	Retrieval aborted: 'Parse Error: Header overflow'.	Not recorded by the method used for this area
hicx.com — supplier information management and supplier master data estate	HTTP 403 Forbidden.	Not recorded by the method used for this area
ofac.treasury.gov — OFAC recent actions, US sanctions designations	Connection timed out after 60 seconds.	Not recorded by the method used for this area
consilium.europa.eu — Council press release on the 16th sanctions package	HTTP 403 Forbidden.	Not recorded by the method used for this area
federalregister.gov — DFARS final rule making CMMC status a condition of award (DFARS Case 2019-D041)	HTTP 302 redirect to unblock.federalregister.gov, an automated-access block.	Not recorded by the method used for this area
gov.uk — expected publication path for the debarment list	HTTP 404 Not Found.	Not recorded by the method used for this area
docs.oracle.com — Oracle Fusion Cloud Procurement release-readiness 'What's New' documents, 25C and 26A	Retrieved and inspected. ZERO page-visible dates of any kind, including no revision history. Release labels ('25C', '26a') are refused as dates under operating rule 4.	Not recorded by the method used for this area
zip.com/blog — 'Introducing agentic procurement orchestration', dated 10 June 2025	Retrieved and inspected. Carries a page-visible date and NO area placement: the agents named are an Intake Validation Agent, a Tariff Analysis Agent and a DORA Screening Agent, and no agent is described performing an operation on supplier master data.	Not recorded by the method used for this area
zip.com/products/supplier-onboarding	Retrieved and inspected. Places squarely on O-1 and carries NO page-visible date; only '© 2026 Zip' in the footer, which operating rule 4 refuses.	Not recorded by the method used for this area
highradius.com — supplier onboarding software	Retrieved and inspected. Places on O-1 and O-3 and carries NO page-visible date; only '© 2026 HighRadius'.	Not recorded by the method used for this area
sam.gov/announcements — 'Improvements to SAM.gov Entity Registration Process', module releases 20 June, 18 July, 15 August and 12 September 2025	Retrieved and inspected. Dated and area-placed, but the artifact states 'we are not changing the data collected', so no consequence field is non-none in substance.	Not recorded by the method used for this area
worldbank.org — Listing of Ineligible Firms & Individuals	Table 1, holding the debarment entries, is loaded client-side and did not render. Table 2 rendered and its two entries are CONDITIONAL NON-DEBARMENTS, which preserve eligibility rather than withdraw it.	Not recorded by the method used for this area
EUR-Lex — Directive (EU) 2024/1760 (corporate sustainability due diligence, 13 June 2024) and Regulation (EU) 2024/3015 (forced labour, 27 November 2024)	Both retrieved and inspected, both dated inside the window, both area-relevant. NOT admitted for two reasons: the three-event-per-actor cap for the EU institutions was already met by EV-04, EV-05 and EV-06; and neither act names the system holding the object whose state changes, which T-08 requires.	Not recorded by the method used for this area
gleif.org — Global Legal Entity Identifier Foundation press releases, 2024 and 2025	Retrieved and inspected. Nil for this area: no release concerns supplier onboarding, vendor master data, or use of the identifier in a supplier record.	Not recorded by the method used for this area
finance.ec.europa.eu — Verification of Payee under Regulation (EU) 2024/886, dated 10 October 2025	Retrieved and inspected. Dated inside the window and NOT admitted: the operation is on the payment order at the point of processing, not on the buying organisation's supplier record, so it falls to X-E.	Not recorded by the method used for this area
assets.publishing.service.gov.uk — earlier Debarment List PDF versions	Retrieved but no extractable text operators; the earlier PDF yielded font tables only.	Not recorded by the method used for this area
The buying organisation's own ERP or MDM as holder of the supplier master — a candidate infrastructure role named in the frozen contract	NIL. No inspected artifact names a specific buying organisation and the system holding its supplier master. Every candidate found was either a vendor's product description or an institutional register.	Not recorded by the method used for this area