LensReading which lens this session carries.

Standard operating procedure · PR6A · Procurement & Source-to-Pay

Supplier Onboarding

Transactional procedure owned by Supplier Onboarding in Procurement & Source-to-Pay. 8 numbered steps, 2 of them a person deciding and 6 of them agent work …

Procedure code

PR6A

Transactional

Rule versions in force

v2.6 · v4.7 · v4.1 · v3.2

4 governing rules stacked over it

In force since

2025-06-15

Earliest effective date across those rules

Last reviewed

2026-07-07

Latest review date across those rules

Rules approved by

1

Director, Supplier Management

Rule health

3/4

0 under review · 1 superseded

There is no document register behind this header. The version, the dates and the approver names are read off the governing rules this procedure runs inside, which is the closest thing the estate holds to a document control record. Nobody wrote these procedures. There is no document library behind this page and no Word file anywhere in the estate. Every procedure below is generated from rows this platform already holds: the line and its ordered stations, the owning team and the person accountable for it, the policy items bound to that team, and the governance gates seeded against the function. The steps, the owners, the gates, the approvers, the dwell times and the volumes are read straight off those rows. The sentences that join them together are generated. Read a procedure as the estate describing itself, not as a document somebody signed.

Purpose and scope

What this procedure is for and where it stops

To run supplier onboarding to one repeatable standard inside Supplier Onboarding, part of Procurement & Source-to-Pay.

Entry condition

Runs transactional. Starts when a threshold is crossed.

Exit condition

The unit clears activate.

In scope

  • Every unit of supplier onboarding raised inside Supplier Onboarding, from the trigger below through to the final step.
  • 6 of the 8 steps, which run without a person present.
  • 2 decisions that stop the line until a named person releases it.

Out of scope

  • Anything outside the envelope set by the owning team. It leaves the line at a gate and becomes the named approver's decision.
  • Work that belongs to another function. This line hands off to ai-gbs and does not follow the unit there.
  • The 5 steps carried on the shared AI GBS spine. They are done for this line but not by this function.

Who owns it

Runs the line

Supplier Onboarding Orchestrator

Accountable person

Director, Supplier Management

The end of the escalation path. Above them sits Procurement Chief of Staff for the function.

That team’s remit

Owns supplier record work end to end inside Procurement & Source-to-Pay.

That remit describes the whole team, not this one procedure, so its counts are larger than the ones on this page.

Autonomy

78% now · ceiling 79%

Registration and screening are automated.

The procedure, step by step

8 numbered steps · 2 of them stop for a person

A step is one station on the line.

No.StepWho does itWhat happensSystem of recordTime on the stepIn flight
01

Register

GBSgbs

Registration Agent

Registration Agent performs this step unattended on the shared AI GBS transaction spine, outside the function, inside the envelope its owning team has set, and writes an evidence record naming the actor, the authority it acted under and the digests of what it read and wrote.Group ERP — Financials52 minstandard 1.5 hrs4
02

Collect documents

GBSgbs

Registration Agent

Registration Agent performs this step unattended on the shared AI GBS transaction spine, outside the function, inside the envelope its owning team has set, and writes an evidence record naming the actor, the authority it acted under and the digests of what it read and wrote.Group ERP — Financials1.6 hrsstandard 3.8 hrs23
03

Screen sanctions

GBSgbs

Registration Agent

Registration Agent performs this step unattended on the shared AI GBS transaction spine, outside the function, inside the envelope its owning team has set, and writes an evidence record naming the actor, the authority it acted under and the digests of what it read and wrote.Group ERP — Financials2.1 hrsstandard 4.5 hrs18
04

Verify bank details

HumanpolicyDecision

Director, Supplier Management

Releases: Director, Supplier Management

Work stops. Director, Supplier Management reviews what the line has produced and either releases the unit or sends it back. Nothing downstream of this step runs until that decision is made.Holds until: Held for a named human when the unit exceeds the supplier record decision envelope, when confidence falls below the floor, or when a policy clause is engaged.Group ERP — Financials1.7 hrsstandard 2.1 hrs7
05

Risk classify

Agentworkflow

Master Data Creation Agent

Master Data Creation Agent performs this step unattended at the workflow layer, inside the envelope its owning team has set, and writes an evidence record naming the actor, the authority it acted under and the digests of what it read and wrote.Group ERP — Financials2.5 hrsstandard 3.9 hrs17
06

Approve

HumanpolicyDecision

Director, Supplier Management

Releases: Director, Supplier Management

Work stops. Director, Supplier Management reviews what the line has produced and either releases the unit or sends it back. Nothing downstream of this step runs until that decision is made.Holds until: Held for a named human when the unit exceeds the supplier record decision envelope, when confidence falls below the floor, or when a policy clause is engaged.Group ERP — Financials2.4 hrsstandard 3.3 hrs4
07

Create master data

GBSgbs

Registration Agent

Registration Agent performs this step unattended on the shared AI GBS transaction spine, outside the function, inside the envelope its owning team has set, and writes an evidence record naming the actor, the authority it acted under and the digests of what it read and wrote.Hands off to ai-gbsGroup ERP — Financials52 minstandard 1.9 hrs26
08

Activate

GBSgbs

Registration Agent

Registration Agent performs this step unattended on the shared AI GBS transaction spine, outside the function, inside the envelope its owning team has set, and writes an evidence record naming the actor, the authority it acted under and the digests of what it read and wrote.Group ERP — Financials2.3 hrsstandard 5.0 hrs39

The swimlane

The same steps, laid out by who is holding the work

Three lanes: a person deciding, an agent working, and the shared services spine.

Person2 stations and 28% of the dwellAgent1 station and 18% of the dwellShared spine5 stations and 54% of the dwell4 crossings between lanes
Human
decides
Agent
does the work
GBS
shared spine
System
attributed by rule
Group ERP — Financials
Group ERP — Financials
Group ERP — Financials
Group ERP — Financials
Group ERP — Financials
Group ERP — Financials
Group ERP — Financials
Group ERP — Financials
Click any station to see who does it, what it costs in time, the rule that gates it and the system attributed to it.

Run the procedure

One unit walked along that swimlane on the happy viable agentified path

Press run and a single unit enters at station 01. Each station takes exactly the dwell this platform records for it and is held by whoever the estate says holds it.

speed
worked clock
00:00
allowance clock
00:00
stations cleared
0/8
the happy path, worked time0 min of 14 hrs
the same run against its allowance0 min of 26 hrs
Human
decides · 2
Agent
does the work · 1
GBS
shared spine · 5
run log

Nothing has happened yet.

where the worked time goes14 hrs a unit
Person4.0 hrs · 28%Agent2.5 hrs · 18%Shared spine7.7 hrs · 54%4 crossings between lanes
what makes this path viable
  • The lanes are the recorded lanes. 2 of the 8 stations stop for a person and every one of them still does on this run.
  • Every one of the 2 decisions is still taken by the people who hold them. The happy path is that each one is released first time, not that it is skipped.
  • The owning team is held to a 79% autonomy ceiling and this run sits at 72% unattended, inside it.
  • 1 system is attributed across the stations, and 0 of them are connected. Nothing in this run has been watched executing against a real system of record.
what would have to change

Nothing moves. 72% of the worked time already runs unattended and the owning team is held to a 79% ceiling, so the next decision cannot be handed over until somebody raises that ceiling.

stays with a person
  • 04 Verify bank details — Handing this over would put 83% of the worked time in the unattended lane, past the 79% ceiling this team is held to.
  • 06 Approve — The last decision on the line. Something on every procedure ends with a person, so this one is never offered.
what this run is, and what it is not

This is a run, not a forecast.

Happy means nothing goes wrong: no station raises an exception, no gate sends the unit back, no rework loop fires and nothing sits in a queue between stations.

The second clock is the allowance.

A decision may be handed to the agent lane only if two things hold …

The run reads the station rows only.

What this run does not model: arrival patterns, contention between procedures for the same person, shift patterns, weekends, learning curves, and the cost of anything.

Run it again, going wrong

The same unit, the same stations, broken the way the estate already records breaking

This is the same unit on the same stations, breaking.

No break below was chosen.

One play head, two tracks, the same scale. The clean run stops when it runs out of stations; the other one keeps going.

As written

8 stations, nothing waiting, nothing sent back

0 min of 14 hrs

now Register · Registration Agent · 52 min

As the ledger has it

the same stations, plus 4 categories the estate already counts

0 min of 34 hrs

now Register · Registration Agent · 52 min

personagentshared spinework the break addsnobody working it

What breaks, and where it is counted

No break below was chosen.

What the two runs say together

4 counted categories land on this procedure.

What this run cannot claim

These breaks are shown together on one unit so the shape of a bad day fits on one screen.

Two clocks run. Worked time is the sum of the time the work is actually being done …

Roles and responsibilities

4 named parties

The responsibility grid is assigned by a rule, not lifted from a chart.

PartyRACIStepsDutyEscalates to

Supplier Onboarding Orchestrator

orchestrator

Runs the line0Sequences this line, holds its timetable and decides what has to surface to a person. Raises to Director, Supplier Management when a unit falls outside the envelope or confidence drops below the floor.

Registration Agent

agent

A3% autonomy · ceiling A3%

92% clean · 1% overridden

Responsible5Runs the repeatable portion of meetings & events inside the shared transaction spine at spine cost and spine controls.Escalates to Director, Corporate Events when the unit falls outside the decision envelope or confidence drops below the floor.

Director, Supplier Management

person

Accountable and responsible2Holds 2 decisions on this line. Accountable to Director, Supplier Management for the decisions held here.

Master Data Creation Agent

agent

A3% autonomy · ceiling A3%

90% clean · 6% overridden

Responsible1Executes the supplier onboarding step it owns, posts its evidence, and hands the unit to the next stage.Escalates to Director, Supplier Management when the unit falls outside the decision envelope or confidence drops below the floor.

Decision points and escalation

2 places this procedure stops

04 · Verify bank details

1.7 hrs

Held for a named human when the unit exceeds the supplier record decision envelope, when confidence falls below the floor, or when a policy clause is engaged.

Director, Supplier Management

06 · Approve

2.4 hrs

Held for a named human when the unit exceeds the supplier record decision envelope, when confidence falls below the floor, or when a policy clause is engaged.

Director, Supplier Management

Handoffs out of this procedure

Step 07 Create master data passes the work to ai-gbs.

The rules this procedure runs inside

4 governing rules

Supplier Onboarding Decision Envelope

active

PR6-POL-200 · envelope · vv2.6

Agents in this lane may act without a human when the supplier record sits inside the stated value, risk and confidence envelope.

Approved by Director, Supplier Management · in force 2026-06-30 · reviewed 2026-05-18

Binds Registration Agent, Due Diligence Agent, Sanctions & Screening Agent, Master Data Creation Agent

LATAM · US

Supplier Onboarding Evidence Standard

active

PR6-POL-201 · evidence · vv4.7

Every autonomous decision writes inputs, the rule version applied, the model and prompt version, the output and a reversal path.

Approved by Director, Supplier Management · in force 2026-07-02 · reviewed 2026-05-30

Binds Registration Agent, Due Diligence Agent, Sanctions & Screening Agent, Master Data Creation Agent

EU · UK · US

Supplier Onboarding Escalation Rule

active

PR6-POL-202 · escalation · vv4.1

Escalation is mandatory when confidence falls below the floor, when two options sit inside the confidence band, or when a break condition on a ratified position fires.

Approved by Director, Supplier Management · in force 2025-06-15 · reviewed 2026-07-07

Binds Registration Agent, Due Diligence Agent, Sanctions & Screening Agent, Master Data Creation Agent

APAC

Supplier Onboarding Autonomy Ceiling

superseded

PR6-POL-203 · ceiling · vv3.2

The ceiling for this lane is 79 on the platform scale.

Approved by Director, Supplier Management · in force 2026-05-26 · reviewed 2026-07-05

Binds Registration Agent, Due Diligence Agent, Sanctions & Screening Agent, Master Data Creation Agent

EU · UK · US

Systems this procedure touches

1 named · 0 connected

System attribution is a rule, not a reading.

SystemVendorDomainCriticalityStepsConnection
Group ERP — FinancialsSAP S/4HANAledgercritical8modeled

0 of the 1 systems on this procedure is connected to the platform, and none of the twenty-six in the estate register is. 1 of them are marked as taking a write back, which is a property of the system, not a live path from here.

How it performs

End to end

14.3 hrs

Summed from the time each step sits, standard 26.1 hrs — running at 55% of the standard.

Touchless

83%

Agent share

75%

A week

6,190

In flight

138

Effort a week

243 human minutes · 615 agent minutes

Volume multiplied by the time on each step.

Assurance over this procedure

4 governance gates sit above it

The twenty-four controls and eighteen exception classes in this platform are held at estate level …

GateWhat trips itWho releases itClockWaivable

Purchase order above $25,000

approval

Any PO above $25,000 or off approved catalog or unbudgetedCategory manager1 business dayNo

New supplier or bank-detail change

approval

Supplier onboarding or any change to payment banking detailsProcurement controller2 business daysNo

Payment above $100,000

approval

Payment release above $100,000Finance controllerPayment runNo

Single-source award or critical negotiation

escalation

Single-source exception or any negotiation affecting critical supplyChief Procurement Officer3 business daysNo

What this document is and is not

These procedures describe the modeled estate.

Actions

What is waiting on a person

What one procedure document gives you, and what to check before you treat it as the standard.

Operations

What this desk is allowed to start

A surface that only reports is not operable.

Trigger and bound

A procedure document prints purpose, scope, entry and exit, the numbered steps with the actor on each, the roles and their RACI position, the swimlane, the decision points and escalation, the handoffs, the governing rules with version and approver, the systems by rule and the timings.

Live observability

What the record shows right now

The whole library, by lane, so a single document can be read against the estate it came from.

Current distribution

2,748 steps

Agent, inside the function1,38951%
Agent, on the shared spine85131%
Person deciding at a gate50818%

Is policy and strategy coming to fruition

Whether the written intent is holding here

Half. The document is complete and every actor on it is measured

Not holding on the record

A procedure here carries a version, an approver, an in-force date and a last-review date.