LensReading which lens this session carries.

Standard operating procedure · FI3A · Finance

Monthly Reporting Pack

Transactional procedure owned by Management Reporting in Finance. 6 numbered steps, 1 of them a person deciding and 5 of them agent work …

Procedure code

FI3A

Transactional

Rule versions in force

v4.7 · v2.2 · v5.0

3 governing rules stacked over it

In force since

2025-06-30

Earliest effective date across those rules

Last reviewed

2026-07-25

Latest review date across those rules

Rules approved by

1

Director, Management Reporting

Rule health

3/3

0 under review · 0 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 monthly reporting pack to one repeatable standard inside Management Reporting, part of Finance.

Entry condition

Runs transactional. Starts when a request lands in the queue.

Exit condition

The unit clears distribute.

In scope

  • Every unit of monthly reporting pack raised inside Management Reporting, from the trigger below through to the final step.
  • 5 of the 6 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 4 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

Management Reporting Orchestrator

Accountable person

Director, Management Reporting

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

That team’s remit

Owns report work end to end inside Finance.

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

Autonomy

81% now · ceiling 90%

Reporting assembly and plain-language answers are the clearest agentic win in Finance.

The procedure, step by step

6 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

Report Assembly Agent

Report Assembly 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 — Financials53 minstandard 1.8 hrs5
02

Quality check

GBSgbs

Report Assembly Agent

Report Assembly 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 — Financials15 minstandard 28 min8
03

Draft narrative

Agentworkflow

Data Quality Agent

Data Quality 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.Bank Connectivity Gateway1.6 hrsstandard 2.5 hrs19
04

Controller review

HumanpolicyDecision

Director, Management Reporting

Releases: Director, Management Reporting

Work stops. Director, Management Reporting 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 report decision envelope, when confidence falls below the floor, or when a policy clause is engaged.Group ERP — Financials1.5 hrsstandard 3.0 hrs2
05

Publish

GBSgbs

Report Assembly Agent

Report Assembly 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 — Financials2.4 hrsstandard 2.9 hrs9
06

Distribute

GBSgbs

Report Assembly Agent

Report Assembly 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 — Financials1.9 hrsstandard 2.7 hrs23

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 17% of the dwellAgent1 station and 19% of the dwellShared spine4 stations and 64% of the dwell3 crossings between lanes
Human
decides
Agent
does the work
GBS
shared spine
System
attributed by rule
Group ERP — Financials
Group ERP — Financials
Bank Connectivity Gateway
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/6
the happy path, worked time0 min of 8.5 hrs
the same run against its allowance0 min of 13 hrs
Human
decides · 1
Agent
does the work · 1
GBS
shared spine · 4
run log

Nothing has happened yet.

where the worked time goes8.5 hrs a unit
Person1.5 hrs · 17%Agent1.6 hrs · 19%Shared spine5.4 hrs · 64%3 crossings between lanes
what makes this path viable
  • The lanes are the recorded lanes. 1 of the 6 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 90% autonomy ceiling and this run sits at 83% 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 Director, Management Reporting.

stays with a person
  • 04 Controller 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

6 stations, nothing waiting, nothing sent back

0 min of 8.5 hrs

now Assemble · Report Assembly Agent · 53 min

As the ledger has it

the same stations, plus 5 categories the estate already counts

0 min of 23 hrs

now Assemble · Report Assembly Agent · 53 min

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

Management Reporting Orchestrator

orchestrator

Runs the line0Sequences this line, holds its timetable and decides what has to surface to a person. Raises to Director, Management Reporting when a unit falls outside the envelope or confidence drops below the floor.

Report Assembly Agent

agent

A4% autonomy · ceiling A4%

92% clean · 7% overridden

Responsible4Runs the repeatable portion of management reporting inside the shared transaction spine at spine cost and spine controls.Escalates to Director, Management Reporting when the unit falls outside the decision envelope or confidence drops below the floor.

Data Quality Agent

agent

A4% autonomy · ceiling A4%

88% clean · 8% overridden

Responsible1Watches data & integration platform continuously. Escalates to Director, Data Platform when the unit falls outside the decision envelope or confidence drops below the floor.

Director, Management Reporting

person

Accountable and responsible1Holds 1 decision on this line. Accountable to Director, Management Reporting for the decisions held here.

Decision points and escalation

1 places this procedure stops

04 · Controller review

1.5 hrs

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

Director, Management Reporting

Handoffs out of this procedure

Nothing leaves this procedure for another function. It completes inside Management Reporting.

The rules this procedure runs inside

3 governing rules

Management Reporting Decision Envelope

active

FI3-POL-200 · envelope · vv4.7

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

Approved by Director, Management Reporting · in force 2025-09-28 · reviewed 2026-07-25

Binds Report Assembly Agent, Narrative Drafting Agent, Self-service Query Agent

US · Canada

Management Reporting Evidence Standard

active

FI3-POL-201 · evidence · vv2.2

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

Approved by Director, Management Reporting · in force 2025-09-14 · reviewed 2026-07-01

Binds Report Assembly Agent, Narrative Drafting Agent, Self-service Query Agent

US · Canada

Management Reporting Escalation Rule

active

FI3-POL-202 · escalation · vv5.0

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 Director, Management Reporting · in force 2025-06-30 · reviewed 2026-04-24

Binds Report Assembly Agent, Narrative Drafting Agent, Self-service Query Agent

US · Canada

Systems this procedure touches

2 named · 0 connected

System attribution is a rule, not a reading.

SystemVendorDomainCriticalityStepsConnection
Group ERP — FinancialsSAP S/4HANAledgercritical5modeled
Bank Connectivity GatewaySWIFT and host-to-host channelsbankingcritical1not-connected

0 of the 2 systems on this procedure is connected to the platform, and none of the twenty-six in the estate register is. 2 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

8.5 hrs

Summed from the time each step sits, standard 13.3 hrs — running at 64% of the standard.

Touchless

85%

Agent share

83%

A week

1,086

In flight

66

Effort a week

88 human minutes · 421 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

Payment above $100,000

approval

Any single payment or batch exceeding $100,000Controller and treasurer4 business hoursNo

Nonstandard journal entry

approval

Any entry outside the approved recurring library, including estimates and reservesController1 business dayNo

New or changed bank details

approval

Any change to supplier or employee banking informationTreasury and supplier master owner2 business daysNo

External disclosure or board forecast

approval

Any external report, statutory filing or board-committed forecastCFO3 business daysNo

Next to it on the same team

Management Reporting

All of Finance

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.