bp Sphere Value Attribution

P2P live incident context · Value Attribution

CASE-P2P-000001 · Vendor unknown vendor · $0

Governed duplicate-settlement exception

This surface is anchored to the same live duplicate-settlement incident as the P2P mission page. $0 is the duplicate-linked value on this incident. $8.4M is the replayable duplicate/exception value traced across the last 90 days. 0 similar incidents already exist for this vendor in governed tenant memory.

Mission Decision Evidence Replay

Incident-scoped value view

No canonical value-event record exists yet for this selected case. The platform is showing the selected incident value under protection from the P2P case context, not an enterprise rollup and not attested realized value.

Value Attribution Proof

Refreshed: 2026-07-18 22:57 UTC

SOURCE

P2P_SELECTED_CASE_CONTEXT + Decision Ledger

Scope: P2P live incident CASE-P2P-000001

POLICY

Policy-gated decisions contributing to value

EVIDENCE

Evidence packs tied to value outcomes

RECORDS

1 governed decisions

ACTION

Review decision ledger

Selected Case Value Under Protection

$8,434,134

1 selected case with evidence and policy context

HYBRID

Incident-scoped value; canonical realized value requires a scoped ValueEventRecord.

Enterprise Value Attribution Engine

The platform treats value as a governed runtime asset: Activity → Decision → Outcome → Value Event → Financial Impact. Realized value, estimated value, and predicted value stay separated so CFO reporting does not become a vanity metric.

Activity

Decision

Outcome

Value Event

Financial Impact

Evidence

Replay

Value Ontology

Category	Calculation basis	Credibility rule
Human Effort Replacement	baseline time -> actual time -> minutes saved	Estimated until time telemetry is measured
Human Effort Augmentation	investigation time reduced while human remains accountable	Estimated / measured by case duration
Value Leakage Prevention	loss avoided from duplicate, overpayment, credit, or revenue leakage	Measured only after outcome is recorded
Working Capital Improvement	cash timing, DSO/DPO, discount, payment sequencing impact	Measured or predicted; never mixed
Control Value	control failures, audit findings, exception volume reduced	Measured by control trend
Decision Quality	accuracy, default rate, false positives, rework, reversals	Measured by outcome learning

Confidence Classes

Class	Definition	Reporting rule
Measured	Actual outcome recorded by SOR or controller-attested ledger event	Allowed in realized-value totals
Estimated	Approved baseline-to-actual calculation with evidence and assumptions	Shown separately with calculation method
Predicted	Scenario, simulation, or recommendation value before outcome	Not counted as realized value

Value Command Hierarchy

Level	Example	Attribution basis
Activity	Invoice match, journal review, receipt follow-up	baseline and actual effort
Decision	Hold invoice, release payment, approve journal	outcome and financial impact
Case	Invoice investigation or close exception	all decisions in the case
User	Analyst or supervisor	hours saved, risk contained, cases resolved
Team	P2P / R2R / Treasury team	aggregate governed outcomes
Function	FB&T tower or finance process	cost, risk, working capital, control trend
Enterprise / CFO	Finance organization	cost reduction, risk reduction, cash improvement

Runtime Value Events By Type

Value type	Reportable	Events	Measured	Estimated
No canonical value events have been recorded yet.

Value Event Drill Path

Type	Amount	Class	Reported	Decision	Proof
No canonical value-event drill path is available yet.

Evidence & Attribution

Every value stream links to governed decisions and evidence packs.

Source systems: SAP AP/FI for invoice and payment outcomes, Ariba for contract and supplier commitments, Payment Hub for release/hold status, Databricks for curated value features, policy runtime for control outcome, and replay ledger for decision proof.

Decision Ledger → Evidence Packs →

Attribution Logic

Selected-case value under protection from incident context; not counted as realized value until a scoped ValueEventRecord exists.

Source table: p2p_selected_case_context · Last attributed execution: 2026-07-18 22:57 UTC.

Source fields: live execution rollups use iaf_agent_executions.value_generated_usd; compact-SOR proof cases use named value_protected_usd rows and remain labeled separately.

Counterfactual baseline: same decision set with no execution value recorded. Only evidence-backed outcomes are included.

Required value-event proof: decision ID, outcome, transaction, evidence refs, replay ref, confidence class, and calculation method. Linked transaction value is not counted as realized value unless a measured or controller-attested outcome exists.