Service GB4C
Intercompany Settlement
Runs transactional. Starts when a request lands in the queue. It runs 5,336 times a week across 5 stations. No station stops for a person and 5 are done by an agent, 3 of them on the shared spine.
Runs a week
5,336
183 in flight right now.
Stations
5
0 person · 2 agent · 3 spine
Agent share of steps
100%
Autonomy on this service is set at 79% against a ceiling of 89%.
Decisions a person makes
0
Nothing on this service waits for a person.
Touchless
83%
Share of runs that complete without anybody opening them.
Timetable against actual
6.7h
Actual 7.5h, 0.8h over the timetable.
Operations
The lane diagram
Read it left to right. more
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 | Match | GBS | Journal Entry Agent | gbs | 24m | 32m | 46 | Group ERP — Financials |
| 2 | Dispute route | Agent | Reconciliation Agent | workflow | 2h 28m | 5h 17m | 33 | Enterprise Data Warehouse |
| 3 | Resolve | Agent | Intercompany Agent | workflow | 36m | 1h 3m | 35 | Group ERP — Financials |
| 4 | Net | GBS | Journal Entry Agent | gbs | 3h 8m | 4h 4m | 39 | Group ERP — Financials |
| 5 | Settle | GBS | Journal Entry Agent | gbs | 1h 12m | 1h 58m | 30 | 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
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
5 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
5 stations, nothing waiting, nothing sent back
0 min of 7.8 hrs
now Match · Journal Entry Agent · 24 min
As the ledger has it
the same stations, plus 3 categories the estate already counts
0 min of 13 hrs
now Match · Journal Entry Agent · 24 min
What breaks, and where it is counted
No break below was chosen. more
What the two runs say together
3 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
2 systems attributed
0 of 2 returning records
Group ERP — Financials
SAP S/4HANA · ledger · bidirectional · critical
4 of 5 stations attributed here · would write back
Enterprise Data Warehouse
Snowflake · analytics · inbound · critical
1 of 5 stations attributed here · read only
System attribution is a rule, not a reading. more
Who runs it
Orchestration and accountability
- Orchestrated by
- Record-to-Report Tower Orchestrator
- That orchestrator’s remit
- Owns reconciliation work end to end inside AI GBS & Global Business Services. Runs 4 lines across 25 stations, drains the repeatable share into the R2R tower, and holds 4 human gates.
- Accountable person
- Tower Lead, Record-to-Report
- Sub-function
- R2R Control Tower
- Shared spine tower
- r2r
- Hand-over points
- None — this service stays inside its function
Other services in this sub-function
3 alongside this one
What this page is and is not
This is a catalogue of the modeled estate. more