LensReading which lens this session carries.

End-to-end outcomes · one chain

OI-ITP-0214 — Invoice to pay

One invoice followed from a supplier invoice is received to the payment clears and reconciles against the bank statement, across every function and tower it touched.

Invoice to pay — all chains
State
Closed
Every stage of the service was found and the last one finished inside the sampled week.
Chain cycle
3.1 d
Wall clock, first stage start to last stage end
Of which waiting
2.8 d
90% of the chain was queue, not work
Cost to serve
$4.56
0 touches over 3 stages
A person intervened
0×
No stage on this chain needed a person
Match confidence
0.30
Cohort

What this chain is, and how sure we are it is one chain

Identity, counterparty and the correlation key

The unit
Ashgrove Industries
Germany · Europe · EUR
Started Thu, Aug 13, 11:53, ended Sun, Aug 16, 14:58.
How the stages were joined
Cohort · 0.30
The chain crosses a boundary and no usable party join exists on either side.
A chain is only as sure as its weakest join, so the figure above is the minimum across the 2 joins below, not their average.
How much of the service ran
3 / 3
2 functions · 2 towers
Every stage the service defines was found for this unit.

The chain, stage by stage

3 stages · 2.8 d waiting · 7.5 h in work

01Invoice received
CG-S2P-004548Supplier invoiceap-automationProcurementS2P
The chain starts here.
In work
5.7 h
Touches
0
Handling
touchless
Join
Origin
On the document
$30,914
Handoff wait before this stage: 2.5 d — nothing was being done to the invoice for that time.
02Payment released
CG-S2P-004013Payment run itemtreasuryFinanceS2P
The document crosses from ap-automation into treasury, where no reference survives.
In work
51 min
Touches
0
Handling
touchless
Join
Inferred 0.76
On the document
$15,124
Handoff wait before this stage: 7.7 h — nothing was being done to the invoice for that time.
03Cash reconciled
CG-R2R-006119Bank reconciliation itembank-gatewayFinanceR2R
At least one side of this step records no party at all, so there is nothing to join on beyond place and timing.
In work
1.0 h
Touches
0
Handling
touchless
Join
Cohort 0.30
On the document
$26,262
The amounts in the right-hand column are what each document carried, and they are deliberately not added up — the same money is written down once at each of the 3 stages this invoice passed through. This service counts value once, at invoice received, which puts $30,914 against this chain.

Where a person intervened

0 of 3 stages were not touchless

No stage on this chain was handled by a person — every one ran touchless. That is unusual for invoice to pay: across its complete chains the median is 1 stage with a person in it.

What the time and the money went on

The chain decomposed

Waiting
2.8 d
90% of elapsed time
In work
7.5 h
10% of elapsed time
Waiting and work are an exhaustive split of the 3.1 d this chain took — every hour is in one bucket or the other. The longest single wait was 2.5 d before payment released.
Cost to serve, $4.56
0 touches at 11 minutes of loaded time each$0.00
3 stages of inference and system cost$4.56
Cost to serve is modeled from the touches the ledger recorded, not billed from a timesheet.
No stage on this chain raised an exception.

The same chain for the whole week, as a distribution

131 complete invoice to pay chains, 10–16 August 2026

this chain sits at the 42nd percentile
2
12
19
32
26
22
14
2
1
1
23.5 hten equal bands of chain cycle time7.0 d
Median chain
3.4 d
p25 2.8 d · p75 4.2 d
Slowest tenth
4.7 d
worst seen 7.0 d
Median waiting
2.6 d
76% of the median chain is queue
Median cost
$15.19
p90 $57.73
The mean of 3.5 d sits above the median of 3.4 d, which is why the distribution is drawn rather than reported as an average: the gap between the median and the slowest tenth is 32.1 h, and it is that tail, not the average, that customers of this service actually feel. The commitment is 168 hours; no chain started early enough in a one-week window to be judged against it.
The ledger behind these chains is one week, 10 to 16 August 2026, which is 168 hours. A chain that had not finished when the week ended is open, not late: the week simply stopped watching it. A chain whose commitment falls after the end of the week could never have been seen to miss, so its service level reads not measurable rather than holding. Nothing on these pages should be read as a monthly or annual attainment. This chain both started and finished inside that week, so its cycle time is a measurement.