BP finance runtime PRD surface

Tower Autonomy Atlas

A tower-wise progression from prevention and standardization to governed autonomy.

Signal
Context
Policy
Agent
Evidence
Human Gate
Control
Value
Replay
Learning
Autonomy progression
LevelMeaningDemo proof
L0 PreventEliminate avoidable work before an agent needs to run.Tolerance simulation, proactive GR prompt, structured remittance.
L0.5 StandardizeNormalize policies, taxonomies, master data, and exception types.Payment terms, deduction reason codes, customer/vendor master gates.
AL1 AssistantAgent drafts, explains, and assembles evidence; human decides.Analyst workspace recommendation and evidence drawer.
AL2 In the loopAgent prepares governed action; human approves material steps.Payment hold, dispute creation, journal draft.
AL3 On the loopAgent acts inside approved envelope; humans handle exceptions.Auto cash match after data readiness is green.
AL4 Policy onlyHumans define policy envelope; runtime executes within controls.Low-risk, evidence-complete, replayable decisions only.
Tower autonomy atlas
TowerProcessPreventableAutomatableDecision focusSystems
P2PInvoice to pay38%30%Duplicate, GR/SES, tolerance, supplier masterSAP ECC, Ariba, VIM, MDG, ServiceNow
O2CCash and credit32%33%Remittance, cash match, deductions, collectionsSAP FSCM, ECC, BlackLine, ServiceNow, UDP
R2RContinuous close28%36%Journal anomaly, accruals, reconciliation, intercompanyECC, CFIN, BlackLine, Workiva
FP&AScenario intelligence20%35%Variance bridge, forecast narrative, scenario simulationIBP, BPC, SAC, CFIN, Power BI
TreasuryLiquidity and payments18%32%Cash visibility, FX, payment risk, working capitalBottomline, bank files, FSCM, S/4 Treasury
ControlsAlways-on control22%30%SoD, SOX evidence, fraud, control replayGRC, IRM, Workiva, Evidence Fabric
P2P transaction trace

INV-88421: Preventable tolerance and missing-GR exception

Prevent upstream with tolerance simulation and GR prompt rather than manual AP exception handling.

InvoiceAriba POSAP ECC GR statusSAP VIM exceptionVendor historyTolerance policy
O2C transaction trace

O2C-NORTHWIND-38500: Unidentified cash and disputed deduction

Request remittance 48h before cash lands, apply clean match, open deduction dispute with evidence.

Bank receiptSAP FSCM open itemsCustomer masterContract termsDeduction historyRemittance request
Definition of done

Every autonomy increment must prove the same chain: signal, context, policy, agent recommendation, evidence, human gate, control outcome, value impact, replay trace, and learning signal.