Decision-Driven Finance
This is not an AI-agent rollout story. It is the path from current finance operations to a 2030 finance function built around continuous visibility, continuous controls, continuous forecasting, governed action, and human accountability.
Finance was built around transactions, reconciliations, reporting cycles, periodic controls, and periodic forecasts. BP now operates in a world of data explosion, complexity explosion, decision-speed expectations, and workforce evolution. Additional human effort does not scale.
Finance becomes a decision system.
The missing middle between today's process model and the future-state North Star is the operating mechanism. bp Sphere makes future finance possible by continuously turning events into governed decisions.
| Runtime Layer | What It Does | BP Example |
|---|---|---|
| Signals | Detect what changed | Invoice created, journal posted, forecast driver moved, credit exposure breached. |
| Context | Understand what changed | Resolve supplier, customer, legal entity, asset, contract, cost center, owner, history. |
| Policies | Determine what is allowed | Apply authority matrix, SOX, accounting policy, procurement policy, treasury limits. |
| Evidence | Prove why action is needed | Attach records, documents, approvals, calculations, lineage, and source freshness. |
| Agents | Perform investigation | Specialized agents gather evidence, evaluate policy, simulate impact, and draft actions. |
| Decisions | Recommend action | Create decision crates with impact, alternatives, confidence, owner, and replay. |
| Supervisors | Approve high-impact actions | Humans approve, reject, modify, or override with a reason code. |
| Learning | Improve outcomes | Capture outcomes, overrides, root causes, and reusable patterns. |
This is the operating mechanism underneath the transformation story. The figures below are generated from the Enterprise Decision Runtime service on request: event correlation, policy simulation, learning metrics, agent guardrails, and audit export.
Hardening stance: missing evidence, low source confidence, and write-back attempts fail closed to human supervision. Learning is measured and replay-backed; it cannot silently change policy or autonomy.
Tomorrow's BP workshop data should replace these workshop-input fields. The page is structured so current-state numbers become a transformation baseline rather than a generic AI vision.
| Area | Metric 1 | Metric 2 | Metric 3 | Metric 4 |
|---|---|---|---|---|
| P2P | Invoices: 120M | Touchless: 25% | Manual interventions: 35-40M | Duplicate detection: reactive |
| O2C | DSO: 45 days | Collections effort: large | Disputes: high | Credit monitoring: periodic |
| R2R | Journal volume: 10M | Close cycle: 8 days | Manual reconciliations: large | Intercompany exceptions: significant |
| FP&A | Forecast cycle: monthly | Forecast effort: high | Scenario generation: limited | Narratives: manual |
| Treasury | Liquidity visibility: delayed | Exposure management: reactive | Counterparty visibility: fragmented | Policy monitoring: periodic |
| Controls | Execution: periodic | Coverage: sample based | Findings: reactive | Evidence assembly: manual |
These are not people problems. They are structural problems created by fragmented context, process-centric operating models, delayed controls, and slow decision formation.
| Barrier | Why it matters |
|---|---|
| Fragmented Context | SAP, Ariba, BlackLine, Databricks, documents, email, spreadsheets, and workflow queues do not naturally explain one decision together. |
| Process-Based Operating Model | Teams optimize tasks, queues, and SLAs, but nobody continuously optimizes the enterprise decisions those tasks support. |
| Human Coordination Dependency | Humans compensate for system complexity by chasing approvals, gathering evidence, resolving ambiguity, and reconciling definitions. |
| Control Lag | Issues are often detected after financial, cash, supplier, customer, audit, or operational impact has already occurred. |
| Decision Latency | Data exists, but context, evidence, policy interpretation, and recommended action arrive too late. |
This is the center of the future-finance story: Events -> Signals -> Context -> Policies -> Evidence -> Agents -> Decisions -> Actions -> Learning. Continuous close, controls, forecasting, treasury, and working capital all become outcomes of the same decision runtime.
The dashboard is not the product. The runtime is the product. Every future finance outcome emerges from this operating model.
Each mission moves from process execution to decision intelligence. This makes the North Star practical instead of aspirational.
| Mission | Current Orientation | Future Orientation | What bp Sphere Adds |
|---|---|---|---|
| P2P | Invoice processing | Working capital optimization | Duplicate prevention, payment timing, supplier evidence, policy-backed release decisions. |
| R2R | Close execution | Continuous assurance | Journal, reconciliation, intercompany, disclosure, and control readiness updated continuously. |
| FP&A | Forecast generation | Capital allocation intelligence | Driver attribution, scenario simulation, board narrative, and investment recommendations. |
| Treasury | Exposure reporting | Liquidity optimization | Cash, FX, covenant, counterparty, and payment-sequencing decisions continuously evaluated. |
| O2C | Collections follow-up | Customer value and risk intelligence | Exposure, payment behavior, disputes, external risk, and collection actions prioritized. |
| Controls | Periodic testing | Preventive control intelligence | Every material transaction evaluated through policy, evidence, action, and replay. |
Continuous Procure To Pay
Today: Invoice arrives -> human validates -> human escalates -> human investigates -> payment.
Future: Invoice event -> agent validation -> policy validation -> evidence pack -> exception classification -> supervisor approval -> action.
Continuous Revenue & Credit
Today: Credit risk is reviewed periodically; collections and disputes are reactive.
Future: Counterparty, market, payment, exposure, and external-risk signals continuously update credit decisions.
Continuous Close
Today: Close starts after period end, with a surge of reconciliation, review, evidence, and coordination work.
Future: Close is always running. Journals, reconciliations, intercompany, controls, disclosures, and variances update readiness continuously.
Continuous Treasury
Today: Liquidity, FX, exposure, and counterparty views are assembled through delayed reporting and manual coordination.
Future: Cash, liquidity, FX, covenant, counterparty, and treasury policy signals continuously update recommended actions.
Continuous Planning
Today: Forecasting is episodic; scenarios are expensive; narratives are manual.
Future: Commodity, production, market, operating, project, and capital events continuously update forecasts, scenarios, recommendations, and narratives.
Continuous Controls
Today: Controls are sample based, periodic, manually tested, and often detective.
Future: Every transaction is evaluated through policy, control, evidence, decision, action, and replay before impact where possible.
Proof point for “the books close themselves”: readiness is continuously recalculated by agents monitoring journals, reconciliations, disclosures, controls, and intercompany balances.
| Readiness Dimension | Score | How It Updates |
|---|---|---|
| Enterprise Close Readiness | 97.2% | Continuously recalculated from journals, reconciliations, intercompany, controls, disclosures, and evidence. |
| Journal Readiness | 96.8% | Large and unusual postings reviewed before close surge. |
| Reconciliation Readiness | 94.6% | BlackLine exceptions and subledger breaks linked to entity-level readiness. |
| Disclosure Readiness | 91.5% | Material events, provisions, and supporting evidence tracked before period end. |
| Control Readiness | 98.1% | SOX and approval controls evaluated continuously against transactions. |
| Intercompany Readiness | 93.4% | Mismatches linked to entities, owners, and recommended clearing actions. |
Evidence is not a slide claim. Every major decision should open an evidence pack, policy result, transaction lineage, document view, approval state, and replay trail.
| Layer | Example | Coverage | Credibility Proof |
|---|---|---|---|
| Decision | Duplicate invoice hold | INV-LIVE-DUP-1778594510 | Open payment decision crate. |
| Evidence Pack | Invoice, PO, GR, supplier bank record, payment history | 6 source records | Every record has source, timestamp, and lineage. |
| Policies | Duplicate Payment Control, Payment Authority Matrix | 2 policies | Rules and result visible. |
| Transactions | SAP invoice, Ariba PO, payment run candidate | 3 transactions | Record-level drilldown, not a summary only. |
| Documents | Contract clause, supplier proof, approval note | 3 documents | Relevant clause or field highlighted. |
| Approvals | Supervisor approval pending | 1 open approval | Human accountability remains visible. |
| Replay | Signal -> context -> evidence -> policy -> recommendation -> action | Replay ready | Audit can reconstruct why the recommendation was formed. |
The future-state claim is not “data is unified.” The more credible claim is “context is unified.” bp Sphere resolves business meaning across records, documents, policies, owners, decisions, and actions.
| Object | Relationships | Why It Matters |
|---|---|---|
| Invoice | Supplier, PO, contract, payment, policy, evidence | Explains why an invoice is safe, risky, duplicate, off-contract, or blocked. |
| Supplier | Contracts, bank details, cyber risk, disputes, late invoices, payment history | Explains supplier-level operational and financial exposure. |
| Journal | Entity, account, cost center, prior journals, close task, SOX control | Explains close risk and required accounting review. |
| Asset | Project, maintenance event, contract, cost center, provision, journal | Explains asset-level finance impact. |
| Policy | Control, decision, approver, evidence requirement, action boundary | Explains what the system may recommend, draft, or execute. |
| Decision | Signal, context, evidence, policies, agents, action, replay, outcome | Turns fragmented data into an auditable decision object. |
The workforce story becomes tangible when each role shows current activities, future activities, agent support, and decision responsibilities.
| Role Page | Current Activities | Future Activities | Agent Support |
|---|---|---|---|
| P2P Analyst 2030 | Matching, coding, validation, approval chasing. | Reviews risk signals, approves payment recommendations, manages supplier exceptions. | Invoice Agent, Matching Agent, Evidence Agent, Policy Agent, Supplier Risk Agent. |
| Controller 2030 | Journal reviews, reconciliations, close coordination, report preparation. | Supervises continuous close, accounting risk, control exceptions, and evidence readiness. | Journal Agent, Reconciliation Agent, Close Readiness Agent, Control Agent, Evidence Agent. |
| Treasury Analyst 2030 | Liquidity reporting, exposure compilation, manual policy checks. | Supervises cash actions, FX exposure, covenant risk, and counterparty signals. | Liquidity Agent, FX Agent, Exposure Agent, Covenant Agent, Counterparty Agent. |
| FP&A Partner 2030 | Collects data, builds forecasts, runs spreadsheet scenarios, writes narratives. | Runs strategic scenarios, challenges assumptions, evaluates capital options, advises leaders. | Forecast Agent, Scenario Agent, Driver Agent, Commodity Agent, Narrative Agent. |
| Current Role | Current Work | Future Role | Future Work |
|---|---|---|---|
| Current P2P Analyst | Matches invoices, investigates exceptions, chases approvals. | Future Decision Analyst | Reviews signals, approves recommendations, manages supplier risk, improves working capital. |
| Current Controller | Reviews journals, runs reconciliations, coordinates close, prepares reports. | Future Controller | Supervises continuous close, reviews escalations, governs accounting risk. |
| Current FP&A Analyst | Builds reports, collects data, creates forecasts, prepares narratives. | Future Performance Strategist | Runs scenarios, evaluates opportunities, allocates capital, challenges assumptions. |
| Current Manager | Coordinates workflow, clears backlogs, escalates issues. | Future Decision Orchestrator | Manages mission health, agent performance, policy exceptions, and value delivery. |
This answers “who actually performs the work?” The estate is grouped by mission and backed by agent inventory, owners, policies, permissions, evidence sources, replay, and runtime metrics.
| Mission | Agent Family |
|---|---|
| P2P | Invoice Agent, Matching Agent, Duplicate Agent, Supplier Agent, Payment Agent, Policy Agent, Evidence Agent |
| O2C | Credit Agent, Collections Agent, Dispute Agent, Customer Risk Agent, Exposure Agent, Evidence Agent |
| R2R | Journal Agent, Reconciliation Agent, Close Agent, Disclosure Agent, Intercompany Agent, Control Agent |
| Treasury | Liquidity Agent, FX Agent, Hedge Agent, Covenant Agent, Counterparty Agent, Cash Forecast Agent |
| FP&A | Forecast Agent, Scenario Agent, Driver Attribution Agent, Commodity Agent, Narrative Agent, Capital Allocation Agent |
| Controls | Control Agent, Authority Agent, SoD Agent, Fraud Agent, Audit Agent, Policy Agent |
| Platform | Context Agent, Evidence Agent, Replay Agent, Learning Agent, Runtime Agent, Cost Governance Agent |
The maturity view becomes actionable when each gap links to required capabilities, data, technology, change, and agents.
| Dimension | Current | Target | Gap | Required Capabilities |
|---|---|---|---|---|
| Close | 2.1 | 4.5 | High | Continuous close, journal intelligence, reconciliation monitoring, evidence packs, control readiness. |
| Controls | 3.0 | 4.5 | Medium | Policy runtime, preventive controls, 100% transaction evaluation, replay, audit evidence. |
| Insight | 2.2 | 4.8 | High | Driver attribution, scenarios, decision crates, executive narratives, learning memory. |
| Working Capital | 2.4 | 4.4 | High | P2P/O2C/Treasury signals, payment timing, collections prioritization, liquidity intelligence. |
| Evidence | 2.0 | 4.7 | High | Evidence vault, source lineage, document extraction, evidence packs, replay. |
| Agent Governance | 2.5 | 4.5 | Medium | Agent inventory, owners, policies, permissions, certifications, runtime metrics. |
| Fabric | Question Answered | BP Workshop Proof |
|---|---|---|
| Identity Fabric | Who is acting? | Human and agent identities, roles, permissions, token lifecycle, and approval authority. |
| Context Fabric | What do they know? | Enterprise memory across suppliers, customers, contracts, assets, cost centers, entities, policies, and history. |
| Policy Fabric | What is allowed? | Approval rules, SOX controls, authority matrix, data access, write-back boundaries, and escalation rules. |
| Evidence Fabric | Why is it justified? | Source records, documents, lineage, hashes, evidence packs, and audit-ready support. |
| Agent Fabric | How is work performed? | Specialized agents that investigate, analyze, coordinate, simulate, explain, and draft actions. |
| Object Fabric | How is the enterprise understood? | Canonical objects such as invoice, supplier, customer, journal, payment, exposure, control, decision, and action. |
| Adapter Fabric | How is BP connected? | Representative workshop adapters now; production connectors to SAP, CFIN, S4, Ariba, Databricks, BlackLine, treasury, documents. |
| Trust & Resilience Fabric | How is the platform governed? | Replay, audit, observability, model routing, cost controls, security events, DR, and kill-switch controls. |
| Horizon | Timing | Capability Stage | What Changes |
|---|---|---|---|
| Horizon 1 | 0-12 months | Decision Intelligence | Read-only agents, evidence packs, recommendations, supervisor approvals, replay. |
| Horizon 2 | 12-24 months | Governed Action | Controlled write-back, workflow execution, draft journals, draft approvals, policy gates. |
| Horizon 3 | 24-36 months | Continuous Operations | Continuous close, continuous controls, continuous forecasting, continuous treasury, cross-functional orchestration. |
| Horizon 4 | 36+ months | Autonomous Finance | Policy-bound autonomous execution, self-healing operations, autonomous controls, human supervision. |
| Value Lever | Current Value | How it is created |
|---|---|---|
| Hours eliminated | Workshop input required | Populate after BP current-state workshop. |
| Close reduction | Workshop input required | Driven by continuous close readiness and exception prevention. |
| Working capital impact | Workshop input required | Driven by payment timing, collections, inventory, and commitment intelligence. |
| DSO impact | Workshop input required | Driven by dynamic credit, dispute, and collections prioritization. |
| Control coverage | Target 100% | Every material transaction evaluated by policy, control, evidence, and replay. |
| Forecast accuracy | Workshop input required | Driven by continuous signals, driver attribution, and scenario coverage. |
| Productivity gains | Workshop input required | Driven by reduced investigation, coordination, evidence gathering, and rework. |
| Risk reduction | Workshop input required | Driven by preventive controls, predictive risk, and continuous monitoring. |
The CFO no longer reviews static reports. The CFO supervises finance health, risk, cash, close, forecasts, controls, value, autonomy, agent activity, recommendations, and required decisions.
Destination message: the future finance organization is not a collection of processes. It is a continuously learning decision system powered by signals, context, evidence, policies, agents, and human accountability.
This is the workshop conversion layer. Once BP provides current-state data, each row becomes a BP-specific roadmap item rather than a generic AI transformation claim.
| Area | Current State | Target State | Gap | Required Capabilities | Required Data | Required Process Changes | Required Technology Changes | Expected Value |
|---|---|---|---|---|---|---|---|---|
| P2P | High-volume invoices, 35% manual interventions, reactive duplicate detection. | Continuous P2P with preventive duplicate controls and governed payment actions. | Manual evidence gathering, approval chasing, supplier ambiguity, delayed exception classification. | Duplicate prevention, policy validation, evidence packs, supervisor action queue, payment orchestration. | SAP invoices, Ariba POs, supplier master, payment terms, approval matrix, duplicate history. | Move AP analysts from transaction validation to exception governance and supplier decision management. | SAP/Ariba adapters, evidence vault, policy runtime, action runtime, replay store. | Lower duplicate risk, faster cycle time, improved working capital, reduced manual effort. |
| O2C | DSO around 45 days, manual collections prioritization, fragmented disputes. | Continuous credit, collections, dispute, and exposure intelligence. | Risk detected late, disputes require manual investigation, collection actions not optimized. | Dynamic credit scoring, counterparty monitoring, collection prioritization, dispute evidence packs. | AR, customer master, payments, credit limits, external ratings, commodity exposure, contracts. | Move analysts from chasing collections to customer-risk and cash-acceleration decisions. | S4/AR adapter, Salesforce/customer adapter, external risk feeds, policy runtime, action workflow. | DSO reduction, bad-debt reduction, faster cash recovery, better exposure quality. |
| R2R / Close | 8-day close, high journal review effort, manual reconciliations, intercompany exceptions. | Continuous close readiness with issues resolved before period end. | Close discovers issues late; controllers coordinate evidence, journals, reconciliations, and controls manually. | Journal intelligence, reconciliation monitoring, intercompany matching, control readiness, close forecast. | S4/CFIN journals, BlackLine reconciliations, entity hierarchy, close calendar, policies, supporting documents. | Move controllers from close execution to accounting-risk and close-readiness supervision. | S4/CFIN adapter, BlackLine adapter, evidence fabric, control fabric, readiness engine. | Shorter close, lower reconciliation effort, improved audit readiness, reduced close stress. |
| FP&A | Monthly forecasts, manual scenarios, manual executive narratives. | Continuous forecasting, on-demand scenarios, driver attribution, board-ready narratives. | Forecasts become stale quickly; scenario generation is slow and dependent on spreadsheet work. | Forecast agents, driver attribution, scenario studio, commodity sensitivity, narrative generation. | SAP actuals, planning data, Databricks features, commodity feeds, FX, project systems, production signals. | Move FP&A from report builders to performance strategists and capital-allocation advisors. | Planning adapter, Databricks adapter, market-data adapters, scenario engine, model routing. | Forecast accuracy, faster scenario response, stronger capital allocation, better executive decisions. |
| Treasury | Delayed liquidity visibility, reactive FX/exposure management, periodic policy monitoring. | Continuous liquidity, exposure, counterparty, covenant, and cash-decision intelligence. | Cash and exposure signals arrive late; treasury actions require manual reconciliation of multiple sources. | Liquidity intelligence, FX exposure monitoring, covenant checks, payment sequencing, hedge recommendations. | Treasury systems, bank feeds, FX feeds, payment schedules, cash forecasts, counterparty data. | Move treasury teams from reporting liquidity to supervising cash and risk actions. | Treasury adapter, bank/FX feeds, policy runtime, scenario engine, action workflow. | Better liquidity headroom, faster risk response, cash optimization, reduced covenant exposure. |
| Controls | Sampling-based assurance, periodic testing, reactive findings. | Continuous controls with 100% transaction evaluation where policy requires it. | Control failures often appear after impact; audit evidence is assembled manually. | Policy enforcement, authority checks, SoD validation, evidence generation, preventive blocks. | Control registry, policies, transactions, identities, approval history, audit findings. | Move control owners from testing samples to governing preventive control intelligence. | Policy fabric, identity fabric, evidence fabric, audit/replay runtime, security gateway. | Higher control coverage, fewer failures, reduced audit effort, stronger trust. |
Click a mission row. This is the workshop bridge from current state to required capabilities, BP inputs, and expected value.
| Mission | Current State | Required Capabilities | Required BP Inputs | Expected Value |
|---|---|---|---|---|
| P2P | Manual interventions, duplicate risk, approval bottlenecks. | Duplicate detection, evidence packs, policy gates, payment actions. | SAP invoices, Ariba POs, supplier master, payment terms, policies, approval matrix. | Duplicate prevention, cycle-time reduction, working-capital improvement. |
| O2C | DSO, disputes, credit exposure, collection effort. | Dynamic credit, collections intelligence, dispute resolution, exposure monitoring. | Customer master, AR, payments, credit limits, external risk, contracts. | DSO reduction, bad-debt reduction, cash acceleration. |
| R2R | Close cycle, journal effort, reconciliations, intercompany breaks. | Continuous close, journal intelligence, reconciliation monitoring, control readiness. | S4/CFIN journals, BlackLine, entity hierarchy, policies, evidence docs. | Close compression, audit readiness, lower reconciliation effort. |
| FP&A | Forecast effort, scenario latency, manual narratives. | Continuous forecasting, scenario studio, driver attribution, narrative generation. | Planning data, SAP actuals, Databricks, commodity feeds, project systems. | Forecast accuracy, faster decisions, better capital allocation. |
| Treasury | Delayed liquidity visibility, reactive exposure management. | Continuous cash, liquidity, FX, counterparty, and covenant intelligence. | Treasury systems, banks, FX feeds, cash forecasts, payment schedules. | Liquidity headroom, risk reduction, cash optimization. |
| Controls | Periodic testing, sample coverage, reactive findings. | Continuous controls, policy enforcement, evidence, preventive actions. | Control registry, policies, transactions, identities, audit findings. | 100% coverage, fewer failures, reduced audit effort. |