bp Sphere Evidence & Trust Center

Operational evidence monitoring + audit-ready trust summary in one surface
Mode: LIVE · Data: LIVE_SOR Role: Fbt Leader
HOME → SIMULATE → DECIDE → ACT → PROVE → LEARN
🟢 AUDIT Can I trust + verify this · proof · hash · lineage · replay · policy mapping (no queue, no decisions) For action: Decisions → · For context: Mission →
P2P live incident context · Evidence Vault
INV-LIVE-DUP-1778594510 · Vendor 50020 · $482.0K
Duplicate invoice number detected for supplier; supervised containment required
This surface is anchored to the same live duplicate-settlement incident as the P2P mission page. $482.0K is the duplicate-linked value on this incident. $8.4M is the replayable duplicate/exception value traced across the last 90 days. 4 similar incidents already exist for this vendor in governed tenant memory.
MissionDecisionEvidenceReplay
Evidence
Outcome Owner trust surface
Evidence now
Evidence-ready
the trust surface now exposes audit-grade evidence and proof coverage before drill-down. The future pursuit is proof.
Lineage
Source to decision traceability
Source, policy, and evidence lineage remain attached so trust can be validated without leaving the active workflow.
Replay posture
Deterministic proof surface
Replayability and proof are first-class controls; this surface exists to answer why a decision is safe to trust. Assurance creates operational trust.
Evidence workflow
1. Every decision carries source, policy, and evidence lineage
2. Proof is available before, during, and after execution
3. Replayability is a first-class control, not an afterthought
4. Trust surfaces exist to validate decisions, not browse generic reports
HomeDecisionsEvidenceSimulation
Incident-scoped trust surface
Evidence remains pinned to the same live duplicate-settlement incident across mission, decision, and replay.
The future pursuit is proof. Assurance creates operational trust.
INV-LIVE-DUP-1778594510 for vendor 50020 carries $482.0K of duplicate-linked value. The current containment reason is: Duplicate invoice number detected for supplier; supervised containment required. $8.4M of related duplicate/exception value is replayable in the last 90 days, with 4 preserved incidents already tied to this vendor.
Incident
INV-LIVE-DUP-1778594510
Vendor
50020
Potential duplicate exposure
$482.0K
Annual duplicate avoidance
$92.8M
Duplicate evidence
Why the agent thinks this is duplicate
Duplicate Type · Potential ResubmissionDuplicate Confidence · 99%Why Flagged?
Current invoice
INV-LIVE-DUP-1778594510
Vendor: 50020
Amount: $482.0K
Matched prior invoice
INV-LIVE-DUP-1778592684
Amount: $482.0K
Invoice date: within 0 days
Vendor
50020
Amount delta
$0
Line similarity
98%
Match reason
same vendor and identical amount
Matching factors
Vendor Match
100%
Invoice Number Match
96%
Amount Match
100%
PO Match
100%
Invoice Date Similarity
100%
Line Item Similarity
98%
Duplicate Confidence
99%
Potential Duplicate Exposure
$482.0K
If released, projected spend increases $482.0K.
Expected year-end variance +12.0%
Annual Duplicate Avoidance
$92.8M
Cost center variance +9.8%
Case #1023 · Approved hold · Recovered $848.3K
Match basis
  • Vendor 50020 matched exactly across current and prior invoice.
  • Amount delta stayed at $0 against the current invoice.
  • Prior invoice was observed within 0 days in the governed duplicate-review window.
Analyst checks
  • Verify whether the supplier submitted replacement or correction paperwork after the prior invoice.
  • Confirm whether policy and evidence justify release or a continued payment hold.
Context Sources Used
  • SAP
  • Ariba
  • Vendor History
  • Prior AP Decisions
  • Invoice Archive
Policies Evaluated
  • Duplicate Invoice Policy
  • Vendor Resubmission Policy
  • Credit Memo Policy
Context Sources Used
SignalINV-LIVE-DUP-1778594510 flagged under duplicate/mismatch/exception predicates.
SystemsSAP, Ariba, Vendor History, Prior AP Decisions, Invoice Archive
Enterprise memory4 replayable incidents already involve vendor 50020.
Policies Evaluated
PolicyPOL-FINANCE-DUPLICATE
EvaluatedDuplicate Invoice Policy, Vendor Resubmission Policy, Credit Memo Policy
Confidence96%
Human approvalSupervisor required
ReplayReplay available
Source attribution and runtime
This focused audit route keeps incident identity visible while preserving enterprise trust cues: source attribution, policy runtime, evidence contract, and replay availability.
Source attributionSAP S/4HANA
Policy RuntimePolicy Runtime enforced duplicate-payment controls before write-back.
Evidence contractEvidence attached, approval trace preserved, replay available.