Service level · Tower to function
Source-to-Pay invoice cycle time
Source-to-Pay Tower
Committed level
26 hrs
cycle-time at or below target · rolling 30 days, 95th percentile
Attainment
96.3%
worst period 93.3%
Consequence of a miss
Service credit
capped at 15%
Breaches
1
0 with remediation still open
Credit
$3.6k
$0 of it actually paid
The commitment
Who owes what to whom
TypeOperational level
Owed byAI GBS — Source-to-Pay Tower
Owed toProcurement, Finance, Supply Chain, Administration
Measurement windowRolling 30 days, 95th percentile
Effective fromFeb 19, 2026
Next reviewOct 29, 2026
Signature
Named and dated
Signed byTobias Renn
RoleDirector, Business Finance
Signed onFeb 11, 2026
A signature makes this level a commitment somebody can be held to. Without one it is a target that reads like a commitment.
How it is measured
From the work ledger
Measured from invoice receipt timestamp to payment instruction, excluding supplier-side holds.
source erp-fin
What a miss costs
Service credit
A miss returns 5% of the monthly tower charge to each receiving function, apportioned by transaction share.
5% of monthly tower charge per breached month, capped at 15% a quarter.
Attainment by period
6 measured periods · floor at 95%
2025 Q4
93.3%
28.3 hrs · target missed
2026 Q1
95.9%
26.1 hrs · target missed
2026 Q2
97.7%
24.6 hrs · target met
Jun 2026
95.9%
26.1 hrs · target missed
Jul 2026
97.1%
25.1 hrs · target met
Aug 2026
97.6%
24.7 hrs · target met
The bar scale starts at 85% rather than zero, because every value on a service level sits in the last few points and a zero-based axis would flatten the only part of the range anyone argues about. The floor line is attainment below 95%, which is what opens a breach.
Breach history
1 recorded miss
BRC-00062025 Q4 · occurred Dec 29, 2025 · detected 8 months ago
measured 28.3 against 26.0
missed by 8.7%
2,086 units affected
open 10.0 hrs
Intake quarantine held 340 items over the weekend because the release decision needs a named human and none was rostered.
contributing: Detection lag of 20 hours before anyone was paged · Measured from the work unit ledger
Intake data qualityDisputed · $3.6kClosed
no owner assigned · remediation due Feb 12, 2026 · closed
Agree the root-cause taxonomy with the tower so that a disputed cause has a defined resolution path instead of stalling.
What this record is, and what it is not
Drill results are measured against a modeled estate on a rehearsal calendar of our own making. Recovery times here are real measurements of a simulation, not evidence that a customer's production estate recovers in the same time.
Attainment, breach detail and credit on this record are modeled. The structure — a named counterparty, a measurement basis that can be checked, a signature, a review date, a consequence, and a breach ledger that records the cause rather than the excuse — is the part intended to survive contact with a real estate.