LensReading which lens this session carries.

Standard operating procedure · GB4D · AI GBS & Global Business Services

Disclosure Drafting

Analytical procedure owned by R2R Control Tower in AI GBS & Global Business Services. 5 numbered steps, 1 of them a person deciding and 4 of them agent work …

Procedure code

GB4D

Analytical

Rule versions in force

v3.4 · v1.7 · v1.6 · v5.3

4 governing rules stacked over it

In force since

2024-10-27

Earliest effective date across those rules

Last reviewed

2026-07-15

Latest review date across those rules

Rules approved by

1

Tower Lead, Record-to-Report

Rule health

3/4

0 under review · 1 superseded

There is no document register behind this header. The version, the dates and the approver names are read off the governing rules this procedure runs inside, which is the closest thing the estate holds to a document control record. Nobody wrote these procedures. There is no document library behind this page and no Word file anywhere in the estate. Every procedure below is generated from rows this platform already holds: the line and its ordered stations, the owning team and the person accountable for it, the policy items bound to that team, and the governance gates seeded against the function. The steps, the owners, the gates, the approvers, the dwell times and the volumes are read straight off those rows. The sentences that join them together are generated. Read a procedure as the estate describing itself, not as a document somebody signed.

Purpose and scope

What this procedure is for and where it stops

To run disclosure drafting to one repeatable standard inside R2R Control Tower, part of AI GBS & Global Business Services.

Entry condition

Runs analytical. Starts when a leader asks the question.

Exit condition

The unit clears audit pack.

In scope

  • Every unit of disclosure drafting raised inside R2R Control Tower, from the trigger below through to the final step.
  • 4 of the 5 steps, which run without a person present.
  • 1 decision that stops the line until a named person releases it.

Out of scope

  • Anything outside the envelope set by the owning team. It leaves the line at a gate and becomes the named approver's decision.
  • Work that belongs to another function. This line records no handoff, so nothing leaves it mid-flow.
  • The 3 steps carried on the shared AI GBS spine. They are done for this line but not by this function.

Who owns it

Runs the line

Record-to-Report Tower Orchestrator

Accountable person

Tower Lead, Record-to-Report

The end of the escalation path. Above them sits GBS Chief of Staff for the function.

That team’s remit

Owns reconciliation work end to end inside AI GBS & Global Business Services.

That remit describes the whole team, not this one procedure, so its counts are larger than the ones on this page.

Autonomy

79% now · ceiling 89%

Reconciliation and accrual mechanics run agentic.

The procedure, step by step

5 numbered steps · 1 of them stop for a person

A step is one station on the line.

No.StepWho does itWhat happensSystem of recordTime on the stepIn flight
01

Assemble

GBSgbs

Journal Entry Agent

Journal Entry Agent performs this step unattended on the shared AI GBS transaction spine, outside the function, inside the envelope its owning team has set, and writes an evidence record naming the actor, the authority it acted under and the digests of what it read and wrote.Group ERP — Financials6.2 hrsstandard 14.3 hrs39
02

Draft

Agentworkflow

Reconciliation Agent

Reconciliation Agent performs this step unattended at the workflow layer, inside the envelope its owning team has set, and writes an evidence record naming the actor, the authority it acted under and the digests of what it read and wrote.Enterprise Data Warehouse8.1 hrsstandard 11.9 hrs33
03

Tie out

GBSgbs

Journal Entry Agent

Journal Entry Agent performs this step unattended on the shared AI GBS transaction spine, outside the function, inside the envelope its owning team has set, and writes an evidence record naming the actor, the authority it acted under and the digests of what it read and wrote.Group ERP — Financials8.8 hrsstandard 11.4 hrs20
04

Review

HumanpolicyDecision

Tower Lead, Record-to-Report

Releases: Tower Lead, Record-to-Report

Work stops. Tower Lead, Record-to-Report reviews what the line has produced and either releases the unit or sends it back. Nothing downstream of this step runs until that decision is made.Holds until: 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.Group ERP — Financials7.4 hrsstandard 10.6 hrs0
05

Audit pack

GBSgbs

Journal Entry Agent

Journal Entry Agent performs this step unattended on the shared AI GBS transaction spine, outside the function, inside the envelope its owning team has set, and writes an evidence record naming the actor, the authority it acted under and the digests of what it read and wrote.Group ERP — Financials7.8 hrsstandard 13.4 hrs35

The swimlane

The same steps, laid out by who is holding the work

Three lanes: a person deciding, an agent working, and the shared services spine.

Person1 station and 19% of the dwellAgent1 station and 21% of the dwellShared spine3 stations and 60% of the dwell4 crossings between lanes
Human
decides
Agent
does the work
GBS
shared spine
System
attributed by rule
Group ERP — Financials
Enterprise Data Warehouse
Group ERP — Financials
Group ERP — Financials
Group ERP — Financials
Click any station to see who does it, what it costs in time, the rule that gates it and the system attributed to it.

Run the procedure

One unit walked along that swimlane on the happy viable agentified path

Press run and a single unit enters at station 01. Each station takes exactly the dwell this platform records for it and is held by whoever the estate says holds it.

speed
worked clock
00:00
allowance clock
00:00
stations cleared
0/5
the happy path, worked time0 min of 38 hrs
the same run against its allowance0 min of 2.6 days
Human
decides · 1
Agent
does the work · 1
GBS
shared spine · 3
run log

Nothing has happened yet.

where the worked time goes38 hrs a unit
Person7.4 hrs · 19%Agent8.1 hrs · 21%Shared spine23 hrs · 60%4 crossings between lanes
what makes this path viable
  • The lanes are the recorded lanes. 1 of the 5 stations stop for a person and every one of them still does on this run.
  • Every one of the 1 decision is still taken by the person who holds it. The happy path is that each one is released first time, not that it is skipped.
  • The owning team is held to a 89% autonomy ceiling and this run sits at 81% unattended, inside it.
  • 2 systems are attributed across the stations, and 0 of them are connected. Nothing in this run has been watched executing against a real system of record.
what would have to change

One decision, held by Tower Lead, Record-to-Report.

stays with a person
  • 04 Review — The last decision on the line. Something on every procedure ends with a person, so this one is never offered.
what this run is, and what it is not

This is a run, not a forecast.

Happy means nothing goes wrong: no station raises an exception, no gate sends the unit back, no rework loop fires and nothing sits in a queue between stations.

The second clock is the allowance.

A decision may be handed to the agent lane only if two things hold …

The run reads the station rows only.

What this run does not model: arrival patterns, contention between procedures for the same person, shift patterns, weekends, learning curves, and the cost of anything.

Run it again, going wrong

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

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

now Assemble · Journal Entry Agent · 6.2 hrs

As the ledger has it

the same stations, plus 5 categories the estate already counts

0 min of 3.0 days

now Assemble · Journal Entry Agent · 6.2 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

5 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.

The separation register records a duty conflict against a sub-function and a named post, not against one procedure.

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

Roles and responsibilities

4 named parties

The responsibility grid is assigned by a rule, not lifted from a chart.

PartyRACIStepsDutyEscalates to

Record-to-Report Tower Orchestrator

orchestrator

Runs the line0Sequences this line, holds its timetable and decides what has to surface to a person. Raises to Tower Lead, Record-to-Report when a unit falls outside the envelope or confidence drops below the floor.

Journal Entry Agent

agent

A4% autonomy · ceiling A4%

91% clean · 8% overridden

Responsible3Runs the repeatable portion of r2r control tower inside the shared transaction spine at spine cost and spine controls.Escalates to Tower Lead, Record-to-Report when the unit falls outside the decision envelope or confidence drops below the floor.

Reconciliation Agent

agent

A4% autonomy · ceiling A4%

89% clean · 8% overridden

Responsible1Executes the r2r control tower step it owns, posts its evidence, and hands the unit to the next stage.Escalates to Tower Lead, Record-to-Report when the unit falls outside the decision envelope or confidence drops below the floor.

Tower Lead, Record-to-Report

person

Accountable and responsible1Holds 1 decision on this line. Accountable to Tower Lead, Record-to-Report for the decisions held here.

Decision points and escalation

1 places this procedure stops

04 · Review

7.4 hrs

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.

Tower Lead, Record-to-Report

Handoffs out of this procedure

Nothing leaves this procedure for another function. It completes inside R2R Control Tower.

The rules this procedure runs inside

4 governing rules

R2R Control Tower Decision Envelope

active

GB4-POL-200 · envelope · vv3.4

Agents in this lane may act without a human when the reconciliation sits inside the stated value, risk and confidence envelope.

Approved by Tower Lead, Record-to-Report · in force 2026-01-22 · reviewed 2026-05-08

Binds Journal Entry Agent, Reconciliation Agent, Intercompany Agent, Accrual Agent, Close Task Agent, Flux Analysis Agent

Global

R2R Control Tower Evidence Standard

superseded

GB4-POL-201 · evidence · vv1.7

Every autonomous decision writes inputs, the rule version applied, the model and prompt version, the output and a reversal path.

Approved by Tower Lead, Record-to-Report · in force 2025-03-14 · reviewed 2026-05-25

Binds Journal Entry Agent, Reconciliation Agent, Intercompany Agent, Accrual Agent, Close Task Agent, Flux Analysis Agent

APAC

R2R Control Tower Escalation Rule

active

GB4-POL-202 · escalation · vv1.6

Escalation is mandatory when confidence falls below the floor, when two options sit inside the confidence band, or when a break condition on a ratified position fires.

Approved by Tower Lead, Record-to-Report · in force 2025-10-04 · reviewed 2026-06-07

Binds Journal Entry Agent, Reconciliation Agent, Intercompany Agent, Accrual Agent, Close Task Agent, Flux Analysis Agent

Global

R2R Control Tower Autonomy Ceiling

active

GB4-POL-203 · ceiling · vv5.3

The ceiling for this lane is 89 on the platform scale.

Approved by Tower Lead, Record-to-Report · in force 2024-10-27 · reviewed 2026-07-15

Binds Journal Entry Agent, Reconciliation Agent, Intercompany Agent, Accrual Agent, Close Task Agent, Flux Analysis Agent

LATAM · US

Systems this procedure touches

2 named · 0 connected

System attribution is a rule, not a reading.

SystemVendorDomainCriticalityStepsConnection
Group ERP — FinancialsSAP S/4HANAledgercritical4modeled
Enterprise Data WarehouseSnowflakeanalyticscritical1modeled

0 of the 2 systems on this procedure is connected to the platform, and none of the twenty-six in the estate register is. 1 of them are marked as taking a write back, which is a property of the system, not a live path from here.

How it performs

End to end

38.3 hrs

Summed from the time each step sits, standard 2.6 days — running at 62% of the standard.

Touchless

66%

Agent share

80%

A week

14

In flight

127

Effort a week

444 human minutes · 1,854 agent minutes

Volume multiplied by the time on each step.

Assurance over this procedure

4 governance gates sit above it

The twenty-four controls and eighteen exception classes in this platform are held at estate level …

GateWhat trips itWho releases itClockWaivable

Autonomy level increase

approval

Any move of an agent or workflow to a higher autonomy bandBusiness owner and risk5 business daysNo

New data class processing

approval

Any service processing a data class not already approvedRisk and privacy officer5 business daysNo

Outsourcing or service removal

approval

Any material operating-model, sourcing or service-portfolio changeGBS executive committee10 business daysNo

Agent recertification

oversight

Quarterly evaluation of every agent against its published certification criteriaAgent governance boardQuarterlyNo

What this document is and is not

These procedures describe the modeled estate.

Actions

What is waiting on a person

What one procedure document gives you, and what to check before you treat it as the standard.

Operations

What this desk is allowed to start

A surface that only reports is not operable.

Trigger and bound

A procedure document prints purpose, scope, entry and exit, the numbered steps with the actor on each, the roles and their RACI position, the swimlane, the decision points and escalation, the handoffs, the governing rules with version and approver, the systems by rule and the timings.

Live observability

What the record shows right now

The whole library, by lane, so a single document can be read against the estate it came from.

Current distribution

2,748 steps

Agent, inside the function1,38951%
Agent, on the shared spine85131%
Person deciding at a gate50818%

Is policy and strategy coming to fruition

Whether the written intent is holding here

Half. The document is complete and every actor on it is measured

Not holding on the record

A procedure here carries a version, an approver, an in-force date and a last-review date.