Enterprise Cash Optimization
Enterprise Working Capital Intelligence
Continuously optimize cash, receivables, payables, inventory, commitments, terms, and liquidity across the enterprise.
Core decision question
How should bp optimize cash across payables, receivables, inventory, commitments, and liquidity?
Every signal, context package, evidence pack, policy result, recommendation, human approval, action, replay, and learning artifact should serve this question.
North Star KPIs
Working capital optimizationCash conversion cycle reductionLiquidity improvementForecast accuracyCapital efficiencyAgent workforce
Cash Intelligence AgentSpend Intelligence AgentCollection Intelligence AgentInventory Intelligence AgentLiquidity Intelligence AgentTreasury Intelligence AgentEnterprise integrations
SAP S/4HANAAribaTreasury systemsInventory systemsRetail systemsTrading systemsDatabricksFuture UDPMonitored domains
PayablesReceivablesInventoryCommitmentsCashLiquidityCovenantsPayment termsCollectionsTreasury windowsReference 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.
6262 reference signals / scenario
$500M$500M opportunity watch
ScenarioScenario event REF-TICK-40866 at 14:19
77 cash actions pending
Reference signals and recommended responses
| Signal | Source | Impact | Recommended response |
|---|---|---|---|
| Large procurement commitment created | Ariba + SAP | $86M future cash impact | Recalculate liquidity forecast |
| Early payment discount window opened | SAP AP | $2.4M opportunity | Recommend accelerated payment |
| Receivable aging worsened | SAP AR | DSO +3.1 days | Trigger prioritized collections |
Demo sequence
- Large commitment enters procurement
- Future cash position recalculates
- Liquidity forecast changes
- Covenant exposure checked
- Working capital impact shown
- Actions recommended before cash impact occurs
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 / metric | Source system or data product | Record / API object | Business context |
|---|---|---|---|
| $86M future cash impact | Ariba commitments + SAP AP | commitment=PO-CAP-250M-009 | Business unit: Upstream |
| $2.4M discount opportunity | SAP AP payment terms | payment_batch=AP-DISC-448 | Owner: P2P Lead |
| DSO +3.1 days | SAP AR + collections queue | customer_portfolio=O2C-AGING-771 | Owner: O2C Lead |
Evidence, policy, replay, learning, and action artifacts
Decision memory
| Runtime artifact | Identifier | Credibility proof |
|---|---|---|
| Evidence pack | EP-WC-40866 | data-evidence="pack" · source records and supporting documents |
| Policy ID | FIN-WC-2026-02 | Policy runtime gate evaluated before recommendation |
| Replay ID | REPLAY-WC-40866 | Replay available from signal through human judgment and action |
| Learning | patterns learned: 6 | Decision memory updates after accepted/rejected outcome |
| Action payload | Payment sequence / collections workflow | Next 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 action | Confidence | Expected value / impact | Risk / tradeoff | Action path |
|---|---|---|---|---|
| Delay non-critical payment batch | 87% | +$62M cash timing | Supplier sentiment | Human-approved payment sequencing |
| Accelerate discount capture | 92% | +$2.4M value | Cash outflow earlier | Treasury approval |
| Prioritize collections | 85% | -3.1 DSO days | Customer relationship risk | Collections workflow |
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
Working capital optimization
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.
| Time | Event | Scenario | Decision impact |
|---|---|---|---|
| --:--:-- | Waiting | No scenario injected | No mission state change |
Decision portfolio
| Decision | Impact | Owner | Status |
|---|---|---|---|
| Delay non-critical payment batch | +$62M cash timing | Treasury Lead | Human-approved |
| Accelerate discount capture | +$2.4M value | P2P Lead | Recommended |
| Prioritize strategic collections | -3.1 DSO days | O2C Lead | Draft 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 layer | What this layer can do | Executive credibility proof |
|---|---|---|
| Agent Runtime | Cash, spend, collection, inventory, liquidity, and treasury agents recalculate cash and working-capital state. | Commitment/collection/inventory event trace with cash, liquidity, and action impact. |
| Analyst | Understand commitment, collection, and inventory cash impacts. | Can explain why cash changed and what action improves it. |
| Supervisor | Monitor bottlenecks, overdue actions, and team follow-through. | Can manage owners and actions that affect DSO, DPO, and inventory. |
| Function Leader / Process Leader | Optimize DSO, DPO, inventory, and payment/collection policies. | Can compare business units, suppliers, customers, and trapped cash drivers. |
| FB&T Leader | View enterprise cash drivers, trapped cash, value opportunities, and mission trends. | Can answer where finance operations should intervene. |
| CFO | Identify actions that unlock $500M working capital improvement. | Can prioritize cash, liquidity, and earnings tradeoffs. |
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.
| Scenario | Inject | Expected runtime proof | Action |
|---|---|---|---|
| Large procurement commitment | $250M capital commitment | Cash forecast, liquidity, working capital, treasury impact, and recommendations update. | |
| Collections deterioration | Major customer delay | Cash, DSO, liquidity impact, and recovery recommendations are visible. | |
| Inventory build-up | Excess inventory | Cash trapped, forecast impact, and optimization recommendations are visible. |
12+ dimension BP credibility audit
| Dimension | Visible proof requirement | This mission's answer |
|---|---|---|
| Signal | Business event or market movement is visible and linked to a mission decision. | Large procurement commitment created · Scenario event REF-TICK-40866 at 14:19 |
| Context | Entity, 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. |
| Evidence | Source 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. |
| Policy | Authority, control, risk, accounting, tax, treasury, or investment policies are referenced. | Policy/runtime gate is evaluated before recommendation or action. |
| Decision | The mission produces a named decision object, not just a metric or chart. | Delay non-critical payment batch |
| Recommendation | Recommended response and alternatives are shown with impact. | Delay non-critical payment batch · confidence 87% · impact +$62M cash timing |
| Human Override | Human approval, rejection, override, or escalation path is explicit. | Approval, rejection, override reason, and escalation owner are retained in replay. |
| Action | Action payload is traceable to workflow, system update, notification, hold, hedge, or approval. | Human-approved |
| Replay | Event, 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. |
| Learning | Accepted/rejected outcomes are captured as future pattern memory. | Outcome becomes pattern memory after human decision and realized impact are known. |
| Business Impact | Financial, risk, cash, control, or value impact is quantified. | +$62M cash timing |
| Enterprise Integration | Systems of record, data products, APIs, and future UDP context layer are named. | SAP S/4HANA · Ariba · Treasury systems · Inventory systems · example: Ariba commitments + SAP AP |
| Source Drill-down | Users 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. |
| Confidence | The decision carries confidence and uncertainty drivers. | Confidence is shown in decision formation and decomposed into data freshness, evidence completeness, policy clarity, and model uncertainty. |
| Alternatives | At least two alternative actions or scenarios are available. | Delay non-critical payment batch | Accelerate discount capture | Prioritize collections |
| Audit Trail | Every material step is retained with timestamp, actor/agent, evidence, and policy result. | Timestamped audit trail spans agent, human, policy, evidence, and action events. |
| Executive Narrative | The 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 KPI | A mission-level KPI changes when the scenario changes. | Working capital optimization |
| Readiness | Readiness or confidence updates when blockers, policies, or evidence status change. | Mission readiness/confidence updates when signals, evidence, policies, or blockers change. |
| Enterprise Impact | The mission shows enterprise-level consequence beyond one transaction. | How should bp optimize cash across payables, receivables, inventory, commitments, and liquidity? |
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.