End-to-end outcomes · one chain
OI-CTR-0144 — Close to report
One close item followed from the period accrual is posted to the reported figure is certified, across every function and tower it touched. more
State
Open
The week ended before the chain could reasonably finish. more
Chain cycle
3.6 d
Wall clock, first stage start to last stage end
Of which waiting
28.7 h
33% of the chain was queue, not work
Cost to serve
$110.89
10 touches over 3 stages
A person intervened
2×
At 2 stages, marked below
Match confidence
1.00
Keyed
What this chain is, and how sure we are it is one chain
Identity, counterparty and the correlation key
The unit
No counterparty recorded
Italy · Europe · EUR
Started Thu, Aug 13, 10:15, and has not ended inside the observation window.
How the stages were joined
Keyed · 1.00
Both documents live in the same source system, so that system’s own reference carries across the join. more
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 / 5
1 function · 1 tower
2 of the 5 stages were never found; the chain stops after close task signed. That is the chain as observed, not proof the work did not happen elsewhere.
The chain, stage by stage
3 stages · 28.6 h waiting · 2.4 d in work
01Accrual posted a person intervened
CG-R2R-006188Accrual postingerp-fiFinanceR2RRina Suryanto
The chain starts here. more
In work
10.6 h
Touches
4
Handling
manual
Join
Origin
On the document
$3,081
Handoff wait before this stage: 12.3 h — nothing was being done to the close item for that time.
02Entry recorded
CG-R2R-005497Journal entryerp-fiFinanceR2R
Both documents live in erp-fi, so the system reference carries across and the link is keyed.
In work
2.3 h
Touches
0
Handling
touchless
Join
Keyed 1.00
On the document
$48,747
Handoff wait before this stage: 16.4 h — nothing was being done to the close item for that time.
03Balances agreed a person intervened
CG-R2R-005975Intercompany settlementerp-fiFinanceR2RPatrick Oyelaran
Both documents live in erp-fi, so the system reference carries across and the link is keyed.
In work
44.2 h
Touches
6
Handling
manual
Join
Keyed 1.00
On the document
$4,357
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 close item passed through. This service carries no monetary value at all — it is internal work — so no value figure is shown for it anywhere.
Where a person intervened
2 of 3 stages were not touchless
Accrual posted
manual
Rina Suryanto · Finance · Record-to-Report · 4 touches over 10.6 h
Balances agreed
manual
Patrick Oyelaran · Finance · Record-to-Report · 6 touches over 44.2 h
Across the 113 complete chains of this service the median is 1, so this one sits above the middle. A stage counts here when its handling is assisted or manual; touchless stages are excluded.
What the time and the money went on
The chain decomposed
Waiting
28.7 h
33% of elapsed time
In work
2.4 d
67% of elapsed time
Waiting and work are an exhaustive split of the 3.6 d this chain took — every hour is in one bucket or the other. The longest single wait was 16.4 h before balances agreed.
Cost to serve, $110.89
10 touches at 11 minutes of loaded time each$106.33
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. more
No stage on this chain raised an exception.
The same chain for the whole week, as a distribution
113 complete close to report chains, 10–16 August 2026
this chain sits at the 21st percentile
6
33
37
21
9
4
1
1
1
2.2 dten equal bands of chain cycle time10.9 d
Median chain
4.2 d
p25 3.7 d · p75 5.0 d
Slowest tenth
6.1 d
worst seen 10.9 d
Median waiting
2.8 d
62% of the median chain is queue
Median cost
$28.87
p90 $71.40
The mean of 4.5 d sits above the median of 4.2 d, which is why the distribution is drawn rather than reported as an average: the gap between the median and the slowest tenth is 45.0 h, and it is that tail, not the average, that customers of this service actually feel. This chain is not complete, so it is not in the 113 above. The commitment is 240 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 had not finished when the window closed, so its cycle time is a floor, not a duration — it is right-censored, and it is not counted as a breach anywhere on this platform.