Standard operating procedure · FI9A · Finance
Earnings Cycle
Transactional procedure owned by Investor Relations Support in Finance. 7 numbered steps, 3 of them a person deciding and 4 of them agent work … more
Procedure code
FI9A
Transactional
Rule versions in force
v4.5 · v1.7 · v4.8
3 governing rules stacked over it
In force since
2025-01-11
Earliest effective date across those rules
Last reviewed
2026-08-05
Latest review date across those rules
Rules approved by
1
VP Investor Relations
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 earnings cycle to one repeatable standard inside Investor Relations Support, part of Finance. more
Entry condition
Runs transactional. Starts when a scheduled window opens.
Exit condition
The unit clears release. more
In scope
- Every unit of earnings cycle raised inside Investor Relations Support, from the trigger below through to the final step.
- 4 of the 7 steps, which run without a person present.
- 3 decisions that stop 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 hands off to legal and does not follow the unit there.
- The 2 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
Investor Relations Orchestrator
Accountable person
VP Investor Relations
The end of the escalation path. Above them sits Finance Chief of Staff for the function.
That team’s remit
Owns disclosure item work end to end inside Finance. more
That remit describes the whole team, not this one procedure, so its counts are larger than the ones on this page.
Autonomy
55% now · ceiling 58%
The lowest ceiling in Finance by design. more
The procedure, step by step
7 numbered steps · 3 of them stop for a person
A step is one station on the line. more
| No. | Step | Who does it | What happens | System of record | Time on the step | In flight |
|---|---|---|---|---|---|---|
| 01 | Assemble results GBSgbs | Investor Relations Orchestrator | Investor Relations Orchestrator 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 — Financials | 1.2 hrsstandard 2.1 hrs | 39 |
| 02 | Draft script Agentworkflow | Peer Benchmark Agent | Peer Benchmark 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 Gateway | 1.2 hrsstandard 2.1 hrs | 29 |
| 03 | Consistency check GBSgbs | Peer Benchmark Agent | Peer Benchmark 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 — Financials | 1.1 hrsstandard 1.8 hrs | 44 |
| 04 | Legal review HumanpolicyDecision | VP Investor Relations Releases: VP Investor Relations | Work stops. VP Investor Relations 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 disclosure item decision envelope, when confidence falls below the floor, or when a policy clause is engaged.Hands off to legal | Group ERP — Financials | 1.1 hrsstandard 2.2 hrs | 8 |
| 05 | CFO approve HumanpolicyDecision | VP Investor Relations Releases: VP Investor Relations | Work stops. VP Investor Relations 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 disclosure item decision envelope, when confidence falls below the floor, or when a policy clause is engaged. | Group ERP — Financials | 4.1 hrsstandard 7.0 hrs | 7 |
| 06 | CEO approve HumanpolicyDecision | VP Investor Relations Releases: VP Investor Relations | Work stops. VP Investor Relations 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 disclosure item decision envelope, when confidence falls below the floor, or when a policy clause is engaged. | Group ERP — Financials | 2.6 hrsstandard 5.3 hrs | 4 |
| 07 | Release Agentworkflow | Investor Relations Orchestrator | Investor Relations Orchestrator 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 Warehouse | 56 minstandard 1.1 hrs | 32 |
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. more
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. more
Nothing has happened yet. more
- The lanes are the recorded lanes. 3 of the 7 stations stop for a person and every one of them still does on this run.
- Every one of the 3 decisions is still taken by the people who hold them. The happy path is that each one is released first time, not that it is skipped.
- The owning team is held to a 58% autonomy ceiling and this run sits at 36% unattended, inside it.
- 3 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.
1 of the 3 decisions can be handed over inside the 58% ceiling. more
- 04 Legal review — held by VP Investor Relations, 1.1 hrs a unit
- 05 CFO approve — Handing this over would put 92% of the worked time in the unattended lane, past the 58% ceiling this team is held to.
- 06 CEO approve — The last decision on the line. Something on every procedure ends with a person, so this one is never offered.
This is a run, not a forecast. more
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. more
The second clock is the allowance. more
A decision may be handed to the agent lane only if two things hold … more
The run reads the station rows only. more
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. more
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. 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
7 stations, nothing waiting, nothing sent back
0 min of 12 hrs
now Assemble results · Investor Relations Orchestrator · 1.2 hrs
As the ledger has it
the same stations, plus 5 categories the estate already counts
0 min of 39 hrs
now Assemble results · Investor Relations Orchestrator · 1.2 hrs
What breaks, and where it is counted
No break below was chosen. more
What the two runs say together
5 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
Attestations on this estate are written against intake items, not against procedures, so a step done off the platform cannot be matched to the attestation that covers it. more
Two clocks run. Worked time is the sum of the time the work is actually being done … more
Roles and responsibilities
4 named parties
The responsibility grid is assigned by a rule, not lifted from a chart. more
| Party | RACI | Steps | Duty | Escalates to |
|---|---|---|---|---|
Investor Relations Orchestrator orchestrator | Runs the line | 0 | Sequences this line, holds its timetable and decides what has to surface to a person. more | Raises to VP Investor Relations when a unit falls outside the envelope or confidence drops below the floor. |
Investor Relations Orchestrator agent A2% autonomy · ceiling A2% 89% clean · 16% overridden | Responsible | 2 | Owns the investor relations support lane end to end. more | Escalates to VP Investor Relations when the unit falls outside the decision envelope or confidence drops below the floor. |
Peer Benchmark Agent agent A2% autonomy · ceiling A2% 94% clean · 6% overridden | Responsible | 2 | Executes the investor relations support step it owns, posts its evidence, and hands the unit to the next stage. | Escalates to VP Investor Relations when the unit falls outside the decision envelope or confidence drops below the floor. |
VP Investor Relations person | Accountable and responsible | 3 | Holds 3 decisions on this line. more | Accountable to VP Investor Relations for the decisions held here. |
Decision points and escalation
3 places this procedure stops
04 · Legal review
1.1 hrsHeld for a named human when the unit exceeds the disclosure item decision envelope, when confidence falls below the floor, or when a policy clause is engaged.
VP Investor Relations
05 · CFO approve
4.1 hrsHeld for a named human when the unit exceeds the disclosure item decision envelope, when confidence falls below the floor, or when a policy clause is engaged.
VP Investor Relations
06 · CEO approve
2.6 hrsHeld for a named human when the unit exceeds the disclosure item decision envelope, when confidence falls below the floor, or when a policy clause is engaged.
VP Investor Relations
Handoffs out of this procedure
Step 04 Legal review passes the work to legal.
The rules this procedure runs inside
3 governing rules
Investor Relations Support Decision Envelope
activeFI9-POL-200 · envelope · vv4.5
Agents in this lane may act without a human when the disclosure item sits inside the stated value, risk and confidence envelope. more
Approved by VP Investor Relations · in force 2025-01-11 · reviewed 2026-07-13
Binds Consensus Tracking Agent, Peer Benchmark Agent, Question Bank Agent, Earnings Pack Agent
Global
Investor Relations Support Evidence Standard
activeFI9-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. more
Approved by VP Investor Relations · in force 2025-08-12 · reviewed 2026-07-27
Binds Consensus Tracking Agent, Peer Benchmark Agent, Question Bank Agent, Earnings Pack Agent
EU · UK · US
Investor Relations Support Escalation Rule
activeFI9-POL-202 · escalation · vv4.8
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. more
Approved by VP Investor Relations · in force 2025-02-24 · reviewed 2026-08-05
Binds Consensus Tracking Agent, Peer Benchmark Agent, Question Bank Agent, Earnings Pack Agent
Global
Systems this procedure touches
3 named · 0 connected
System attribution is a rule, not a reading. more
| System | Vendor | Domain | Criticality | Steps | Connection |
|---|---|---|---|---|---|
| Group ERP — Financials | SAP S/4HANA | ledger | critical | 5 | modeled |
| Bank Connectivity Gateway | SWIFT and host-to-host channels | banking | critical | 1 | not-connected |
| Enterprise Data Warehouse | Snowflake | analytics | critical | 1 | modeled |
0 of the 3 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
12.2 hrs
Summed from the time each step sits, standard 21.6 hrs — running at 56% of the standard.
Touchless
59%
Agent share
57%
A week
4,301
In flight
163
Effort a week
466 human minutes · 265 agent minutes
Volume multiplied by the time on each step. more
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 … more
| Gate | What trips it | Who releases it | Clock | Waivable |
|---|---|---|---|---|
Payment above $100,000 approval | Any single payment or batch exceeding $100,000 | Controller and treasurer | 4 business hours | No |
Nonstandard journal entry approval | Any entry outside the approved recurring library, including estimates and reserves | Controller | 1 business day | No |
New or changed bank details approval | Any change to supplier or employee banking information | Treasury and supplier master owner | 2 business days | No |
External disclosure or board forecast approval | Any external report, statutory filing or board-committed forecast | CFO | 3 business days | No |
Next to it on the same team
Investor Relations Support
What this document is and is not
These procedures describe the modeled estate. more
Actions
What is waiting on a person
What one procedure document gives you, and what to check before you treat it as the standard.
named approvers appear across the library
Every decision point on every procedure carries a job title, not a queue. more
steps in the library hand their unit to another function
A handoff is where a procedure stops being one team’s problem. more
controls exist in the estate, and they belong to no procedure in particular
Controls and exception classes are held estate-wide. more
Operations
What this desk is allowed to start
A surface that only reports is not operable. more
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. more
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. more
Current distribution
2,748 steps
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 more
Not holding on the record
A procedure here carries a version, an approver, an in-force date and a last-review date. more