Planning Intelligence

Treasury Intelligence

Move treasury from liquidity reporting to real-time optimization of cash, funding, exposures, and financial risk.

Core decision question
How should bp optimize liquidity, FX, debt, covenants, and hedging?

Every signal, context package, evidence pack, policy result, recommendation, human approval, action, replay, and learning artifact should serve this question.

North Star KPIs
Liquidity confidenceFX exposure reductionCovenant resilienceHedging effectivenessCash yield
Agent workforce
Liquidity Intelligence AgentFX Intelligence AgentDebt Intelligence AgentCovenant Monitoring AgentHedging Optimization Agent
Enterprise integrations
Treasury systemsBank APIsSAP S/4HANAFX feedsCommodity feedsDebt systemsDatabricksFuture UDP
Monitored domains
Cash positionLiquidity forecastFX exposureDebt portfolioCovenantsHedgesBank feesInvestments
Reference signal ticker

Signal visibility must be more than the word signal. Each mission shows reference signal counts, severity, scenario REF-TICK ID, and current blocked/recommended state. These are scenario proof shapes until connected to live traversal.

Reference signal generated from the scenario library; REF-TICK IDs show the expected production trace shape and are not attested live events.

5858 reference signals / scenario
77 exposure movements
ScenarioScenario event REF-TICK-80391 at 14:22
$340M$340M headroom movement
Reference signals and recommended responses
SignalSourceImpactRecommended response
Liquidity forecast movedTreasury system$340M headroom changeRebalance funding plan
FX exposure increasedFX feed + SAP$72M VaR movementRecommend hedge adjustment
Covenant headroom tightenedDebt system1.6x threshold watchEscalate treasury committee
Demo sequence
  1. Cash forecast changes
  2. FX moves
  3. Covenant headroom recalculates
  4. Hedge options generated
  5. Treasury action drafted
Source-system traceability for major numbers

Every major value is tied to a source system, API object, data product, or source transaction. This answers where the number came from before BP asks.

Context pack: business unit: Group Finance · cost center: CC-1042 · entity code: BP-GROUP · owner: mission runtime.

Number / metricSource system or data productRecord / API objectBusiness context
$340M headroom changesor-treasury liquidity forecastliquidity_run=LIQ-2026-0606Owner: Treasurer
$72M FX VaR movementsor-fx-rate-feed + Murex exposureexposure=FX-VAR-774Policy: Treasury hedge
1.6x covenant watchDebt system + covenant modelcovenant=COV-ND-161Steward: Treasury Risk
Evidence, policy, replay, learning, and action artifacts
Decision memory
Runtime artifactIdentifierCredibility proof
Evidence packEP-TR-80391data-evidence="pack" · source records and supporting documents
Policy IDFIN-TR-2026-08Policy runtime gate evaluated before recommendation
Replay IDREPLAY-TR-80391Replay available from signal through human judgment and action
Learningpatterns learned: 4Decision memory updates after accepted/rejected outcome
Action payloadTreasury hedge/funding workflowNext action: governed execution after approval limit $500K and human override check
Alternative actions table

Alternative actions table. This is the concrete recommendation surface: bp Sphere shows what it recommends, what it rejected, the expected value, the risk, and the action path.

Alternative actionConfidenceExpected value / impactRisk / tradeoffAction path
Adjust FX hedge90%$72M VaR reducedHedge costTreasury workflow
Rebalance debt maturity82%+$180M headroomRefinancing costTreasurer approval
Sweep idle cash93%+$6.4M yieldLiquidity buffer changeCash manager action
Runtime injection console

Use these controls during the workshop to show the mission changing state. Injection creates a named runtime event, updates mission KPI/readiness, adds a replay row, and opens the trace from signal to learning.

Mission KPI
Liquidity confidence

Awaiting scenario injection.

Mission readiness
Baseline

No injected blockers or opportunities yet.

Latest replay event
None

Click an injection below to create a replayable runtime event.

TimeEventScenarioDecision impact
--:--:--WaitingNo scenario injectedNo mission state change
Decision portfolio
DecisionImpactOwnerStatus
Adjust FX hedge$72M VaR reducedTreasury LeadHuman-approved
Rebalance debt maturity+$180M liquidity headroomTreasurerRecommended
Sweep idle cash+$6.4M yieldCash ManagerDraft action
Vertical operating-model audit

This validates that the mission is useful from frontline work through enterprise steering: Agent Runtime → Analyst → Supervisor → Function Leader/Controller → FB&T Leader → CFO.

Role layerWhat this layer can doExecutive credibility proof
Agent RuntimeLiquidity, FX, debt, covenant, and hedging agents monitor treasury exposure.Treasury trace with cash, exposure, policy, hedge, and approval.
AnalystReview cash, FX, debt, and hedge signals.Can explain exposure movement.
SupervisorMonitor treasury operations workload and exceptions.Can manage unresolved treasury actions.
Function Leader / TreasurerOptimize liquidity, hedging, debt, covenants, and bank relationships.Can see risk-adjusted treasury recommendations.
FB&T LeaderUnderstand treasury contribution to cash, risk, and enterprise resilience.Can connect treasury to working capital and forecast.
CFOSteer liquidity, capital structure, and risk exposure.Can decide funding, hedge, debt, and cash actions.
Executive credibility scenarios

These are the scenarios BP can challenge live. The mission must show signal, context, evidence, policy, decision, action, replay, learning, and enterprise impact for each.

ScenarioInjectExpected runtime proofAction
Liquidity shockCash forecast moves sharplyLiquidity outlook, headroom, recommended funding actions, and replay are visible.
FX movementMaterial FX exposure shiftExposure, recommended hedge, policy, and action path are visible.
Debt covenant pressureCovenant headroom tightensDebt optimization and escalation are visible.
12+ dimension BP credibility audit
DimensionVisible proof requirementThis mission's answer
SignalBusiness event or market movement is visible and linked to a mission decision.Liquidity forecast moved · Scenario event REF-TICK-80391 at 14:22
ContextEntity, business unit, owner, system object, policy domain, and history are resolved.Resolved through enterprise context graph: owner, system object, business unit, history, and policy domain.
EvidenceSource records, documents, approvals, and source-system snapshots are inspectable.Evidence pack includes source system record, curated data snapshot, policy reference, and supporting document where applicable.
PolicyAuthority, control, risk, accounting, tax, treasury, or investment policies are referenced.Policy/runtime gate is evaluated before recommendation or action.
DecisionThe mission produces a named decision object, not just a metric or chart.Adjust FX hedge
RecommendationRecommended response and alternatives are shown with impact.Adjust FX hedge · confidence 90% · impact $72M VaR reduced
Human OverrideHuman approval, rejection, override, or escalation path is explicit.Approval, rejection, override reason, and escalation owner are retained in replay.
ActionAction payload is traceable to workflow, system update, notification, hold, hedge, or approval.Human-approved
ReplayEvent, context, evidence, policy, recommendation, human judgment, action, and outcome can be replayed.Replay captures signal, context, evidence, policy, agent output, human judgment, action, outcome, and learning.
LearningAccepted/rejected outcomes are captured as future pattern memory.Outcome becomes pattern memory after human decision and realized impact are known.
Business ImpactFinancial, risk, cash, control, or value impact is quantified.$72M VaR reduced
Enterprise IntegrationSystems of record, data products, APIs, and future UDP context layer are named.Treasury systems · Bank APIs · SAP S/4HANA · FX feeds · example: sor-treasury liquidity forecast
Source Drill-downUsers can drill from decision to source transaction, document, or curated data product.Source drill-down points to SOR/API record, Databricks/UDP data product, document, or market feed behind the decision.
ConfidenceThe decision carries confidence and uncertainty drivers.Confidence is shown in decision formation and decomposed into data freshness, evidence completeness, policy clarity, and model uncertainty.
AlternativesAt least two alternative actions or scenarios are available.Adjust FX hedge | Rebalance debt maturity | Sweep idle cash
Audit TrailEvery material step is retained with timestamp, actor/agent, evidence, and policy result.Timestamped audit trail spans agent, human, policy, evidence, and action events.
Executive NarrativeThe mission can produce an executive answer: what happened, why, what to do, and expected outcome.Narrative answers what happened, why, recommended action, value, risk, and next owner.
Mission KPIA mission-level KPI changes when the scenario changes.Liquidity confidence
ReadinessReadiness or confidence updates when blockers, policies, or evidence status change.Mission readiness/confidence updates when signals, evidence, policies, or blockers change.
Enterprise ImpactThe mission shows enterprise-level consequence beyond one transaction.How should bp optimize liquidity, FX, debt, covenants, and hedging?
Runtime architecture
SignalBusiness event, market movement, policy breach, or performance variance.
ContextEntity, asset, customer, project, policy, historical pattern, and owner resolution.
Evidence + PolicySource records, documents, controls, authority, and data-quality checks.
Decision + ActionAlternatives, confidence, financial impact, owner, action payload, and approval path.
Replay + LearningFull trace, outcome, accepted/rejected recommendation, and pattern memory.