Phase 2 - Allocation and recharge automation

PaPM Allocation and Recharge Runtime

Make allocations, recharges, bill-to-actual flows, and PaPM/SAC reporting explainable, governed, and replayable.

Business problem: Allocation and recharge processes often span SAP, PaPM, SAC, source drivers, manual assumptions, and approvals; finance needs traceable calculations, policy controls, and impact visibility. Open JSON contract Back to foundations
Runtime Hardening Proof

Execution evidence from Enterprise Decision Runtime service

This panel is generated from runtime service functions on each request: event correlation, policy simulation, learning metrics, agent guardrails, decision trace, and audit package export. It closes the view-vs-system gap by showing the platform executing, not only describing architecture.

7registered agents
5registered policies
1correlated signal(s) from 3 events
$450.0Kpolicy simulation amount
100.0%human acceptance over 2785610 decided executions (90d)
5825088decision memory records
BLOCKbad-data guardrail result
route_to_human_supervisoragent failure fallback
Live event correlation
SignalPriorityImpactEvent IDs
sig-2efe089ec8P1$1.4Mevt-001, evt-002, evt-003
Policy + guardrail hardening
ControlRuntime value
Policyhuman-approval-policy
Prior threshold$50.0K
Simulated threshold$100.0K
Outcomeescalate
Approval volume change-18%
Guardrail failuresmissing_evidence, low_source_confidence, writeback_requires_human_approval
Hallucination guardevidence_required_before_recommendation
Replay + audit export
ArtifactValue
Audit packageaudit-97ab17991395
Integrity hashc80fd1aea51cec3d76a8d2e6346938acd1938531f544f8f3f7fd3917f1d6c98c
Regulatory export readyTrue
Trace steps10
Runtime chainSignal -> Context -> Ontology -> Policy -> Evidence -> Decision -> Governance -> Action -> Replay -> Learning
Runtime APIs
Endpoint
/api/finance-foundations/runtime-proof
/api/finance-foundations/papm-allocation-recharge-runtime/runtime-proof
/api/iaf/enterprise-decision-runtime/learning-metrics
/api/iaf/enterprise-decision-runtime/agent-guardrails
/api/iaf/enterprise-decision-runtime/policy-simulation
/api/iaf/enterprise-decision-runtime/event-correlation
Hardening stance: agents fail closed to human supervision on missing evidence, low source confidence, or write-back attempts. Learning is measured, replay-backed, and cannot change policy or autonomy without approval.
North Star runtime outcome

Every recharge or allocation is tied to source drivers, calculation lineage, policy validation, evidence, downstream SAP/PaPM posting, and replay.

Core components
ComponentCapability
Allocation Driver RegistryMaintains allocation drivers, source freshness, owner, policy, and financial outcome mapping.
PaPM Calculation LineageCaptures input driver, formula, version, allocation result, posting target, and approval trail.
Recharge Validation ServiceChecks bill-to-actual variance, receiving entity, materiality, policy, and exception thresholds.
SAC Reporting ConnectorExposes calculation lineage, variance, and commentary for reporting surfaces.
Allocation ReplayReconstructs how a recharge or allocation value was formed and approved.
Success metrics
MetricTarget
Calculation lineage100% target
Recharge exception explanation95% target
Driver freshnessDaily target
Allocation replay coverage100% target
FP&A deck alignment
Target operating-model theme
SAP PaPM
Recharges
Allocations
Bill to Actual
SAC reporting
FDF PaPM integration
Agent family
AgentPurpose
Allocation Driver AgentValidates driver completeness and source freshness.
PaPM Lineage AgentExplains formula, version, input, output, and downstream impact.
Recharge Variance AgentFinds bill-to-actual breaks and recommends adjustment or escalation.
Allocation Policy AgentApplies materiality, ownership, and approval rules.
Proof links
SurfaceRoute
FP&A Command CenterOpen
R2R MissionOpen
Replay CenterOpen
Data Trust ExplorerOpen
API contract
Endpoint
/api/finance-foundations/papm-allocation-recharge-runtime
/ui/fpa-command-center
/ui/mission/r2r
Validation questions
Question
Which driver created this allocation?
Which PaPM formula and version ran?
Why did bill-to-actual variance occur?
Can this allocation be replayed and audited?