The catalogue Procurement & Source-to-PayPayment InterlockTransactional

Service PR10A

Payment Run

Runs transactional. Starts when a scheduled window opens. It runs 2,973 times a week across 7 stations. 2 of those stations stop for a person and 5 are done by an agent, 5 of them on the shared spine.

Runs a week

2,973

102 in flight right now.

Stations

2 person · 0 agent · 5 spine

Agent share of steps

71%

Autonomy on this service is set at 77% against a ceiling of 78%.

Decisions a person makes

Held by Director, Payment Operations.

Touchless

79%

Share of runs that complete without anybody opening them.

Timetable against actual

13.3h

Actual 16.9h, 3.6h over the timetable.

Operations

The lane diagram

Read it left to right. more

Person2 stations and 17% of the dwellAgent0 stations and 0% of the dwellShared spine5 stations and 83% of the dwell2 crossings between lanes

Human

decides

Agent

does the work

GBS

shared spine

System

attributed by rule

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.

Operations

Every station in order

The same stations as a list, with the dwell the estate records against each one and the system a station of that shape would touch.

#	Station	Lane	Who	Layer	Dwell	Target	In flight	System
1	Select due	GBS	Payment Proposal Agent	gbs	57m	2h 1m	28	Group ERP — Financials
2	Optimize discount	GBS	Payment Proposal Agent	gbs	2h 55m	5h 25m	14	Group ERP — Financials
3	Fraud screen	GBS	Payment Proposal Agent	gbs	2h 57m	5h 35m	17	Group ERP — Financials
4	Treasury check Held for a named human when the unit exceeds the payment run decision envelope, when confidence falls below the floor, or when a policy clause is engaged. Hands over at finance	Human	Director, Payment Operations	policy	1h 33m	3h 2m	0	Group ERP — Financials
5	Approve run Held for a named human when the unit exceeds the payment run decision envelope, when confidence falls below the floor, or when a policy clause is engaged.	Human	Director, Payment Operations	policy	59m	1h 54m	2	Group ERP — Financials
6	Execute	GBS	Payment Proposal Agent	gbs	2h 37m	3h 9m	16	Group ERP — Financials
7	Remittance advice	GBS	Payment Proposal Agent	gbs	3h 8m	6h 43m	25	Group ERP — Financials

Operations

Run it

Change the volume, move the autonomy line, release a gate, and watch what happens to the hours in each lane and to the time it takes one run to get through. more

Move something

Demand100%

2,973 a week is what the estate records. more

Decisions handed to agents0 of 2

Cheapest decision first. The last gate never moves: something on this service always ends with a person.

People on the gates216 people

Each one is assumed to have 2,100 productive minutes a week, which is 35 hours.

Agent speed100%

100% is the dwell the estate records today. more

Person time a week

7,531.6h

2,973 items at 152 minutes of decision each.

Agent time a week

37,360.7h

754 minutes an item, which does not compete for a person.

Gate load

100%

Inside capacity, with 28.4h of headroom.

Stations without a person

71%

2 gates left on 7 stations.

Where an item spends its time

17% waiting on a person

83% in the agent lane

An item now takes 906 minutes of worked time end to end against 906 in the recorded estate, a change of +0%. This is worked time, not calendar time: nothing here models a queue or a weekend.

What this model is, on Payment Run

The simulation is arithmetic on the estate, not a queueing model. more

How it runs

Run it again, going wrong

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

7 stations, walked twice

Once clean, once with the categories the estate counts

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

No break below was chosen. more

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 15 hrs

now Select due · Payment Proposal Agent · 57 min

As the ledger has it

the same stations, plus 4 categories the estate already counts

0 min of 34 hrs

now Select due · Payment Proposal Agent · 57 min

personagentshared spinework the break addsnobody working it

What breaks, and where it is counted

No break below was chosen. more

What the two runs say together

4 counted categories land on this procedure. more

What this run cannot claim

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

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

Live observability

Systems this service would touch

Attributed by rule from the function's system list. more

1 systems attributed

0 of 1 returning records

The system register

Group ERP — Financials

SAP S/4HANA · ledger · bidirectional · critical

modeled

7 of 7 stations attributed here · would write back

System attribution is a rule, not a reading. more

Who runs it

Orchestration and accountability

Orchestrated by: Payment Interlock Orchestrator
That orchestrator’s remit: Owns payment run work end to end inside Procurement & Source-to-Pay. Runs 3 lines across 16 stations, drains the repeatable share into the S2P tower, and holds 4 human gates.
Accountable person: Director, Payment Operations
Sub-function: Payment Interlock
Shared spine tower: s2p
Hand-over points: finance

Other services in this sub-function

2 alongside this one

Urgent PaymentPR10B Term OptimizationPR10C

What this page is and is not

This is a catalogue of the modeled estate. more