LensReading which lens this session carries.

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

Requisition-to-PO

Transactional procedure owned by Requisition & PO in Procurement & Source-to-Pay. 7 numbered steps, 1 of them a person deciding and 6 of them agent work …

Procedure code

PR8A

Transactional

Rule versions in force

v4.6 · v5.7 · v4.7

3 governing rules stacked over it

In force since

2024-09-28

Earliest effective date across those rules

Last reviewed

2026-06-24

Latest review date across those rules

Rules approved by

1

Director, Procurement Operations

Rule health

3/3

0 under review · 0 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 requisition-to-po to one repeatable standard inside Requisition & PO, part of Procurement & Source-to-Pay.

Entry condition

Runs transactional. Starts when an upstream system posts an event.

Exit condition

The unit clears confirm to supplier.

In scope

  • Every unit of requisition-to-po raised inside Requisition & PO, from the trigger below through to the final step.
  • 6 of the 7 steps, which run without a person present.
  • 1 decision that stops 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 finance and does not follow the unit there.
  • The 6 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

Requisition Orchestrator

Accountable person

Director, Procurement Operations

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

That team’s remit

Owns requisition 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

81% now · ceiling 90%

Catalog buying is fully touchless inside budget and policy.

The procedure, step by step

7 numbered steps · 1 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

Request

GBSgbs

Guided Buying Agent

Guided Buying 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 — Financials35 minstandard 56 min31
02

Guide to catalog

GBSgbs

Guided Buying Agent

Guided Buying 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 — Financials3.1 hrsstandard 6.1 hrs42
03

Budget check

GBSgbs

Guided Buying Agent

Guided Buying 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 financeGroup ERP — Financials3.2 hrsstandard 7.5 hrs32
04

Policy screen

GBSgbs

Guided Buying Agent

Guided Buying 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.2 hrsstandard 3.9 hrs14
05

Route approval

HumanpolicyDecision

Director, Procurement Operations

Releases: Director, Procurement Operations

Work stops. Director, Procurement Operations 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 requisition decision envelope, when confidence falls below the floor, or when a policy clause is engaged.Group ERP — Financials2.1 hrsstandard 4.5 hrs4
06

Issue PO

GBSgbs

Guided Buying Agent

Guided Buying 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.6 hrsstandard 4.2 hrs14
07

Confirm to supplier

GBSgbs

Guided Buying Agent

Guided Buying 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 3.2 hrs5

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.

Person1 station and 13% of the dwellAgent0 stations and 0% of the dwellShared spine6 stations and 87% of the dwell2 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
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/7
the happy path, worked time0 min of 16 hrs
the same run against its allowance0 min of 30 hrs
Human
decides · 1
Agent
does the work · 0
GBS
shared spine · 6
run log

Nothing has happened yet.

where the worked time goes16 hrs a unit
Person2.1 hrs · 13%Shared spine14 hrs · 87%2 crossings between lanes
what makes this path viable
  • The lanes are the recorded lanes. 1 of the 7 stations stop for a person and every one of them still does on this run.
  • Every one of the 1 decision is still taken by the person who holds it. The happy path is that each one is released first time, not that it is skipped.
  • The owning team is held to a 90% autonomy ceiling and this run sits at 87% 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

One decision, held by Director, Procurement Operations.

stays with a person
  • 05 Route approval — 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

7 stations, nothing waiting, nothing sent back

0 min of 16 hrs

now Request · Guided Buying Agent · 35 min

As the ledger has it

the same stations, plus 3 categories the estate already counts

0 min of 21 hrs

now Request · Guided Buying Agent · 35 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

3 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

3 named parties

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

PartyRACIStepsDutyEscalates to

Requisition Orchestrator

orchestrator

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

Guided Buying Agent

agent

A4% autonomy · ceiling A4%

96% clean · 4% overridden

Responsible6Runs the repeatable portion of requisition & po inside the shared transaction spine at spine cost and spine controls.Escalates to Director, Procurement Operations when the unit falls outside the decision envelope or confidence drops below the floor.

Director, Procurement Operations

person

Accountable and responsible1Holds 1 decision on this line. Accountable to Director, Procurement Operations for the decisions held here.

Decision points and escalation

1 places this procedure stops

05 · Route approval

2.1 hrs

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

Director, Procurement Operations

Handoffs out of this procedure

Step 03 Budget check passes the work to finance.

The rules this procedure runs inside

3 governing rules

Requisition & PO Decision Envelope

active

PR8-POL-200 · envelope · vv4.6

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

Approved by Director, Procurement Operations · in force 2024-09-28 · reviewed 2026-05-01

Binds Guided Buying Agent, Catalog Match Agent, Budget Check Agent, Approval Routing Agent, PO Issuance Agent, Change Order Agent

APAC

Requisition & PO Evidence Standard

active

PR8-POL-201 · evidence · vv5.7

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

Approved by Director, Procurement Operations · in force 2025-10-11 · reviewed 2026-04-21

Binds Guided Buying Agent, Catalog Match Agent, Budget Check Agent, Approval Routing Agent, PO Issuance Agent, Change Order Agent

EU · UK · US

Requisition & PO Escalation Rule

active

PR8-POL-202 · escalation · vv4.7

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, Procurement Operations · in force 2025-02-16 · reviewed 2026-06-24

Binds Guided Buying Agent, Catalog Match Agent, Budget Check Agent, Approval Routing Agent, PO Issuance Agent, Change Order Agent

APAC

Systems this procedure touches

1 named · 0 connected

System attribution is a rule, not a reading.

SystemVendorDomainCriticalityStepsConnection
Group ERP — FinancialsSAP S/4HANAledgercritical7modeled

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

15.9 hrs

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

Touchless

88%

Agent share

86%

A week

7,758

In flight

142

Effort a week

124 human minutes · 830 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.