Use one end-to-end duplicate-invoice event to answer the five questions technology leaders care about: is it real, how does it work, how does it integrate, how is it governed, and how does it fail safely.
bp Sphere is a governed enterprise decision runtime that connects signals, context, policies, evidence, agents, humans, and systems of record into a single accountable execution fabric.
Show the live P2P queue, case drawer, evidence pack, action surface, SAP context drawer, and replay. Avoid starting with diagrams.
After the business event lands, show agent activation, context retrieval, policy evaluation, evidence assembly, decision formation, and replay.
Show SAP ECC/S4/CFIN coexistence, Ariba, Databricks/UDP, OneData/Foundry, BlackLine, ServiceNow, and evidence storage as adapter contracts.
Show Entra-backed agent identity, AI use-case approval, Material AI gate, kill switch, policy gates, human approval, audit trail, and revocation.
Show fallback policy, human workflow, replay, recovery, and business continuity. AI is optional; continuity is not.
Every proof point links to an existing system page. This page is the presenter shell, not another architecture deck.
Open the live P2P queue and anchor on the duplicate invoice event. The point is that the demo starts from a business signal, not a chatbot prompt.
Open live P2PShow invoice, PO, receipt, prior payment, supplier history, and payment terms in the case drawer. This answers whether the agent is guessing.
Open adaptive analyst workspaceShow duplicate-payment, authority, materiality, evidence, and payment-hold policy checks. This answers how AI is controlled.
Open P2P policy pathOpen invoice, PO, receipt, prior payment, and supplier evidence through the Evidence Intelligence Runtime.
Open evidenceShow hold-payment recommendation, confidence, reasoning factors, and expected outcome before any action is taken.
Open case drawerShow analyst/supervisor boundary: hold, escalate, request evidence, open supplier, open SAP context. Human accountability remains visible.
Open supervisor queueShow that write-back is controlled: draft action, SAP context, audit record, queue impact, no autonomous payment release.
Open SAP coexistenceShow Signal -> Context -> Policy -> Evidence -> Recommendation -> Human Approval -> SAP update as an inspectable replay path.
Open replay| Topic | Show | Why it matters |
|---|---|---|
| Agent runtime | Runtime topology | State, coordination, observability, cost, ownership. |
| Data and integration | Data strategy | Protect SAP and use UDP/Databricks/OneData/Foundry correctly. |
| Identity and governance | Entra agent identity | Agents are governed identities, not anonymous bots. |
| SAP coexistence | Quantum coexistence | ECC, CFIN, and S/4 can coexist during rollout. |
| Resilience | Failure handling | Fallback, recovery, human workflow, replay. |
Only after the duplicate-invoice proof should you bridge into future finance. The credible message is that the same runtime pattern powers Continuous Accounting, Continuous Close, Driver-Based FP&A, Intercompany, and Controls.