LensReading which lens this session carries.

Service GB4B

Balance Sheet Reconciliation

Runs transactional. Starts when a scheduled window opens. It runs 6,463 times a week across 5 stations. One of those stations stops for a person and 4 are done by an agent, 3 of them on the shared spine.

Runs a week

6,463

117 in flight right now.

Stations

5

1 person · 1 agent · 3 spine

Agent share of steps

80%

Autonomy on this service is set at 79% against a ceiling of 89%.

Decisions a person makes

1

Held by Tower Lead, Record-to-Report.

Touchless

91%

Share of runs that complete without anybody opening them.

Timetable against actual

5.7h

Actual 4.8h, 0.9h under the timetable.

Operations

The lane diagram

Read it left to right.

Person1 station and 37% of the dwellAgent1 station and 26% of the dwellShared spine3 stations and 38% of the dwell2 crossings between lanes
Human
decides
Agent
does the work
GBS
shared spine
System
attributed by rule
Group ERP — Financials
Group ERP — Financials
Group ERP — Financials
Group ERP — Financials
Enterprise Data Warehouse
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.

#StationLaneWhoLayerDwellTargetIn flightSystem
1

Pull balances

GBSJournal Entry Agentgbs1h 48m3h 49m29Group ERP — Financials
2

Auto-match

GBSJournal Entry Agentgbs22m30m36Group ERP — Financials
3

Age open items

GBSJournal Entry Agentgbs1h 58m3h 53m21Group ERP — Financials
4

Certify

Held for a named human when the unit exceeds the reconciliation decision envelope, when confidence falls below the floor, or when a policy clause is engaged.

HumanTower Lead, Record-to-Reportpolicy4h 1m6h 16m6Group ERP — Financials
5

Escalate aged

AgentClose Task Agentworkflow2h 49m4h 10m25Enterprise Data Warehouse

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.

Move something
Demand100%
6,463 a week is what the estate records.
Decisions handed to agents0 of 0
This service has at most one gate, so there is nothing to hand over without removing the last human decision.
People on the gates742 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.
Person time a week
25,959.7h
6,463 items at 241 minutes of decision each.
Agent time a week
44,917.9h
417 minutes an item, which does not compete for a person.
Gate load
100%
Inside capacity, with 10.3h of headroom.
Stations without a person
80%
1 gate left on 5 stations.
Where an item spends its time
37% waiting on a person
63% in the agent lane
An item now takes 658 minutes of worked time end to end against 658 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 Balance Sheet Reconciliation

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

How it runs

Run it again, going wrong

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

5 stations, walked twice

Once clean, once with the categories the estate counts

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

No break below was chosen.

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

now Pull balances · Journal Entry Agent · 1.8 hrs

As the ledger has it

the same stations, plus 3 categories the estate already counts

0 min of 16 hrs

now Pull balances · Journal Entry Agent · 1.8 hrs

personagentshared spinework the break addsnobody working it

What breaks, and where it is counted

No break below was chosen.

What the two runs say together

3 counted categories land on this procedure.

What this run cannot claim

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

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

Live observability

Systems this service would touch

Attributed by rule from the function's system list.

2 systems attributed

0 of 2 returning records

Group ERP — Financials

SAP S/4HANA · ledger · bidirectional · critical

modeled

4 of 5 stations attributed here · would write back

Enterprise Data Warehouse

Snowflake · analytics · inbound · critical

modeled

1 of 5 stations attributed here · read only

System attribution is a rule, not a reading.

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.