Close tasks
10
Persisted close task rows for readiness and bottleneck views.
Continuous Close Intelligence Mission
Understand the operating model before opening the live use case.
Continuous Close Intelligence Mission Launch
Refreshed: 2026-07-18 22:54:12 UTC
SOURCE
bp Sphere use case launch spec + linked runtime proof surfaces
Scope: Understand → Experience → Verify
POLICY
Launch metrics are non-attestation unless a section is explicitly marked live
EVIDENCE
SAP S/4HANA, SAP ECC, BlackLine, Endur, Murex, Ariba, Maximo, document repositories, accounting policies, SOX controls, and future UDP ontology
RECORDS
Scenario orientation with downstream runtime, evidence, lineage, and read-model links
ACTION
Launch Continuous Close Intelligence
Launch Page Data Basis
T2/T3 MIXED READ MODEL
NON-ATTESTATION
FALLBACK DISCLOSED
The figures on this launch page are validation-orientation values unless a section is explicitly marked live.
They are not audit-attested SOR proof and must not be presented as production financial evidence.
A live compact read-model anchor is shown below for this launch page. Static launch metrics remain orientation-only.
Live Domain Read-Model Anchor
These values come from page-specific persisted read-models where available. Zeros mean no live rows were present, not a substituted demo value.
Close risk items
15
Close risk rows available for live risk posture.
Value at risk
$5.0M
Close value-at-risk total from risk item records.
Journal gate entries
7
Journal gate rows available for controlled posting workflows.
Source Connector Readiness Anchor
Connector dependencies are loaded from tenant domain connector manifests for finance.
This is readiness metadata, not a successful SOR call; live proof still requires read-model rows, evidence, policy, replay, or source-system response records.
Mode distribution: live: 5, local_live: 10.
finance · SAP S/4HANA
live
10 operations: get_journal_entries, post_journal_entry, get_gl_balances +7 more · freshness 60
finance · SAP S/4HANA Central Finance
live
5 operations: get_central_journal_entries, get_harmonized_trial_balance, get_replication_status +2 more · freshness 120
finance · SAP Ariba
local_live
6 operations: get_purchase_requisitions, get_purchase_orders, get_invoices +3 more · freshness 300
finance · Coupa
local_live
6 operations: get_invoices, get_purchase_orders, get_requisitions +3 more · freshness 300
finance · BlackLine
live
7 operations: get_reconciliations, get_reconciliation_detail, get_close_tasks +4 more · freshness 120
finance · HighRadius
local_live
7 operations: get_open_receivables, get_cash_applications, get_collection_worklist +4 more · freshness 180
Live Platform Proof Anchor
These counts come from persisted runtime tables. Business figures elsewhere on this launch page remain non-attestation unless separately marked live.
Agent Executions5826289
Policy Evaluation Logs21474822
Decision Ledger Records5422407
Organizational Change Records7
Value Event Records39489
Business Problem
Why this use case matters before the demo starts
bp closes across upstream, midstream, trading, refining, retail, low-carbon, joint venture, and global legal-entity structures. Controllers often discover issues late because journals, reconciliations, intercompany mismatches, provisions, trading entries, and evidence gaps are reviewed after activity has already accumulated. Continuous Close Intelligence turns every financial event into signal, context, evidence, policy, materiality assessment, readiness recalculation, governed decision, replay, and learning.
bp Sphere Decision Operating System
Continuous Close Intelligence Mission
Continuously monitor journals, reconciliations, intercompany balances, provisions, trading finance entries, controls, and evidence so close readiness updates before period end.
Enterprise Signal
Financial close readiness signal
This use case starts with a governed enterprise signal, not a generic AI prompt.
→
bp Sphere Assembles
Context + Evidence + Policy + Impact + Judgment + Memory
Source systems consulted: SAP S/4HANA, SAP ECC, BlackLine, Endur, Murex, Ariba, Maximo, document repositories, accounting policies, SOX controls, and future UDP ontology. Consequences evaluated: Close readiness, restatement avoidance, controller workload, reconciliation effort, audit readiness, SOX posture, and forecasted close time.
Context Discovery
Evidence Assembly
Policy Evaluation
Impact Analysis
Human Judgment
Decision Memory
What This Use Case Proves
1
Signal
Financial close readiness signal enters the operating model.
2
Context Discovery
SAP S/4HANA, SAP ECC, BlackLine, Endur, Murex, Ariba, Maximo, document repositories, accounting policies, SOX controls, and future UDP ontology are assembled into enterprise context.
3
Evidence & Policy
Controls and source evidence shape the decision before recommendation.
4
Impact
Close readiness, restatement avoidance, controller workload, reconciliation effort, audit readiness, SOX posture, and forecasted close time are calculated before action.
5
Human Judgment
The operator approves, overrides, escalates, or requests more evidence.
6
Decision Memory
The same runtime pattern extends to Continuous Forecast Intelligence, Dynamic Credit Intelligence, Autonomous Control Intelligence, and Enterprise Working Capital Intelligence.
Launch Metrics · Non-Attestation Unless Marked Live
Readiness Dimensions9
Close Agents10
Evidence Sources7
Policy Gates5
Replay Coverage100%
Why This Is Credible
- Every readiness number opens contributing source records, drivers, policies, and agent actions
- Every material decision exposes signal, context, evidence, policy, impact, recommendation, confidence, replay, and learning
- The flagship scenario shows a SAP journal changing readiness before certification
- Controller action remains human-controlled where materiality, policy, evidence, or authority requires judgment
Recommendation Is Not The Product.
The durable value is the governed combination of context + evidence + policy + impact + human judgment. The recommendation is merely the visible output.
The durable value is the governed combination of context + evidence + policy + impact + human judgment. The recommendation is merely the visible output.
What The Operator Needs To Answer
- What is close readiness now across enterprise, entity, journal, reconciliation, intercompany, provision, trading, control, disclosure, and evidence dimensions?
- Which financial events changed readiness and why?
- Which journals, provisions, reconciliations, intercompany breaks, or trading entries require controller judgment?
- What evidence and policies support the recommended action?
- Can the decision be replayed from source event to human outcome?
Enterprise Context Consulted
SAP S/4HANA / ECCACDOCA, BKPF, BSEG, COEP, COBK, FAGLFLEXA, universal journal, company code, GL, period, currency, cost center, profit center
BlackLineJournal workflows, account reconciliations, close tasks, certifications, open exceptions, supporting documents, and approval history
Trading platformsEndur/Murex positions, valuations, mark-to-market postings, hedge evidence, and trading finance support
Procurement and asset systemsAriba commitments, receipts, invoices, Maximo work orders, asset changes, capital projects, and AFE records
DocumentsContracts, accounting memos, approval records, policies, workpapers, engineering support, and external reports
Policy and controlsSOX controls, close certification rules, materiality thresholds, SOD, authority matrix, and evidence retention requirements
Future UDP / ontologyLegal entity, BU, asset, cost center, profit center, counterparty, contract, project, journal, account, control, policy, decision and evidence graph
How This Use Case Lands In The Room
What the user sees
Readiness KPIs, live close signals, entity heatmap, controller decision crates, evidence packs, policy results, agent trace, simulation, and replay
What the system proves
Close readiness is an output of continuous decision intelligence, not a manually assembled dashboard
Human judgment
Controllers approve, hold, override, escalate, or request evidence when policy, materiality, or support requires judgment
Why it matters
This shows how continuous close actually happens: every financial event contributes to readiness before month-end
Evidence Intelligence Fabric
Evidence Discovery Service
Discover candidate evidence across enterprise systems.
Evidence Resolution Service
Resolve authoritative records, versions, and governing precedence.
Evidence Extraction Service
Extract clauses, approvals, milestones, tolerances, and decision-ready snippets.
Evidence Lineage Service
Build cross-system provenance from source records to recommendation.
Evidence Pack Service
Package immutable decision-specific bundles for replay and audit.
Evidence Viewer
Render contracts, emails, invoices, policies, and supporting records with source proof.
Controlled Truth Sources
Close Task CalendarGL HistorySubledger SupportInvoice ArchiveContract RepositoryReconciliation WorkspaceIntercompany EliminationsTrading PositionsProvision / Actuarial PackRecharge LedgerController NotesSOX Control Library
Policies Evaluated
Close Risk PolicyAnomaly Materiality PolicyIntercompany Netting PolicyMTM Support PolicySOX Controller Escalation Policy
Evidence Discovery Timeline
17:05:01 · Close period posture loaded
Entity-level close deadlines and unresolved journal queues retrieved.
17:05:03 · Historical GL baselines assembled
Statistical anomaly patterns compared against the current journal batch.
17:05:05 · Provision, intercompany, and MTM evidence linked
Decommissioning, elimination, and trading-position support attached to the review.
17:05:07 · Recharge and operating-cost distortions evaluated
Producing-asset recharge anomalies and close sensitivity calculated.
17:05:09 · SOX and close-risk policy posture applied
Materiality and controller escalation thresholds evaluated.
17:05:10 · Recommendation generated
Escalate four anomalies before close to reduce restatement and auditor risk.
Continuous Close Runtime Chain
This use case demonstrates how close readiness is created by runtime decisions, not by a static close dashboard.
Financial Event · JRN-NS-4408
SAP S/4HANA universal journal posting for North Sea abandonment cost accrual enters the close runtime.
Signal Detection · Material movement
Provision movement exceeds close materiality guardrail and creates a controller decision rather than a passive alert.
Context Resolution · Entity + asset + policy
Context resolves BP North Sea Trading Ltd, UK Upstream, asset NS-ALPHA, GL 249900, cost center CC-4408, and close calendar day WD-2.
Evidence Resolution · 6 records
Evidence pack links SAP journal, prior-period provision, decommissioning model, approval memo, policy extract, and BlackLine workpaper.
Policy Evaluation · 2 gates
Materiality threshold and controller approval policy are evaluated before a recommendation is formed.
Readiness Recalculation · 97.2% → 96.8%
Enterprise readiness changes immediately because evidence completeness and approval status are part of the score.
Decision + Action · Approve / escalate / correct
Controller receives alternatives with impact, confidence, action payload, and replay link.
Replay + Learning · Full trace
Replay stores event, context, evidence, policy result, agent outputs, human judgment, action, outcome, and reusable learning.
Readiness Dimensions
Journal Readiness · 96.4%
Journals are monitored for missing support, duplicate postings, unexpected account usage, and segregation exceptions.
Reconciliation Readiness · 94.8%
BlackLine certification, aging breaks, owner SLA, and evidence completeness are continuously scored.
Intercompany Readiness · 92.6%
Out-of-balance pairs, elimination risk, counterparty acceptance, and settlement timing are tracked before close.
Provision Readiness · 91.8%
Environmental, decommissioning, and asset retirement provisions are checked against models, approvals, and policy thresholds.
Trading Readiness · 95.2%
Endur and Murex valuations, hedge support, market-data freshness, and MTM postings are reconciled to finance.
Control Readiness · 98.1%
SOX controls, approval matrices, authority boundaries, and manual override requirements are first-class runtime checks.
Evidence Readiness · 93.9%
Evidence packs show whether each material close judgment has traceable source records and support documents.
Entity Readiness · 96.8%
Legal-entity readiness rolls up journals, reconciliations, controls, provisions, disclosures, and unresolved decision load.
Decision Formation Proof
DEC-CLOSE-4408 · Provision journal requires controller judgment
Signal, asset context, SAP journal, BlackLine evidence, accounting policy, materiality threshold, alternatives, action payload, and replay are visible from one mission drawer.
DEC-IC-620 · Intercompany imbalance blocks entity readiness
UK Trading and Netherlands Treasury entities are linked through settlement evidence, elimination policy, and close-critical path impact.
What-if Simulation
Reduce unresolved reconciliations · 50%
Projected readiness +1.8 pts, close duration -4.2 hours, controller effort -18%, and audit evidence coverage +6 pts.
Automate journal support checks · 80%
Projected manual journal review load -38%, evidence readiness +7 pts, and late close investigation count -24%.
Resolve intercompany breaks by WD-2 · 90%
Projected entity readiness +2.4 pts, elimination risk -31%, and group reporting confidence +3.1 pts.
Enterprise Integrations Required
This launch page is an illustrative readiness model. Production close readiness must be bound to SAP, BlackLine, Endur, Murex, UDP, or other governed source records before attestation.
SAP S/4HANA + ECC · ACDOCA / BKPF / BSEG
Journals, document types, GL accounts, entities, cost centers, posting periods, currencies, assets, accruals, and controls.
BlackLine · Recs + close tasks
Reconciliation status, certification workflow, close calendar tasks, supporting documents, open exceptions, and approval history.
Endur + Murex · Trading finance
Positions, valuations, hedge relationships, mark-to-market postings, and market-data dependent close evidence.
Ariba + Maximo · Commitments + assets
Procurement commitments, receipts, supplier contracts, asset maintenance events, AFE records, and capital project context.
Documents + Policies · Evidence fabric
Accounting memos, controller approvals, contract clauses, SOX narratives, authority matrices, and accounting policy extracts.
Future UDP · Enterprise graph
Unified events, ontology relationships, asset/counterparty/project graph, and cross-domain lineage once BP exposes curated products.
Named Agent Runtime
Journal Intelligence Agent · JRN-NS-4408
Validated account movement, period, preparer history, duplicate risk, and supporting evidence gap.
Reconciliation Break Resolution Agent · REC-117
Prioritized aged BlackLine break and linked it to intercompany settlement dependency.
Provision Intelligence Agent · EP-CLOSE-NS-4408
Compared abandonment provision against latest engineering model, prior close, and policy threshold.
Trading Finance Validation Agent · TRD-VAL-903
Validated LNG desk valuation movement against Endur, market data, and finance posting evidence.
Close Evidence Assembly Agent · 6 sources
Built audit-ready evidence pack with source lineage, timestamps, completeness, and missing-support status.
Control Assurance Agent · SOX + authority
Evaluated approval matrix, materiality, segregation of duties, and controller review requirement.
Close Readiness Forecast Agent · 6.2h close
Forecasted close duration, critical path, readiness trend, and effect of unresolved actions.
Close Replay and Audit Agent · Replay ready
Captured runtime steps so the controller can prove what happened and why.
Policy, Control, and Evidence Contract
Materiality policy R2R-MAT-002Close authority matrix AOM-7SOX journal review controlBlackLine certification evidenceEndur/Murex valuation evidenceController approval required
Every material recommendation must show source evidence, policy result, approval requirement, alternatives, action consequence, and replay package.
Demo Proof Links
Use the mission for the live story, then open evidence and lineage if BP asks how the decision is proved.
Runtime Proof Links
Evidence artifact
Open the evidence pack and lineage before treating any recommendation as source-backed.
Policy and replay artifact
Policy and replay claims must resolve to a platform surface, not just launch-page narrative text.
Value claim boundary
Protected, pending, and realized value stay separate. Realized value requires finance attestation.
Evidence Pack Viewer
Close Calendar · CLOSE-M5
98% · Close Calendar
Version: Current period
Retrieved: 17:05:01
Governing status: Anchor
Current month-end close has 14 unresolved controller tasks with M+5 pressure.
Version: Current period
Retrieved: 17:05:01
Governing status: Anchor
Current month-end close has 14 unresolved controller tasks with M+5 pressure.
Journal Anomaly Set · JRN-4408
96% · GL History
Version: Current anomaly batch
Retrieved: 17:05:03
Governing status: Authoritative
Decommissioning, recharge, and mark-to-market postings deviate from historical GL behavior.
Version: Current anomaly batch
Retrieved: 17:05:03
Governing status: Authoritative
Decommissioning, recharge, and mark-to-market postings deviate from historical GL behavior.
Subledger Transactions · SUBLEDGER-771
94% · Subledger Support
Version: Current supporting set
Retrieved: 17:05:04
Governing status: Supporting
Subledger support reconciles most source transactions, but one manual adjustment lacks standard support.
Version: Current supporting set
Retrieved: 17:05:04
Governing status: Supporting
Subledger support reconciles most source transactions, but one manual adjustment lacks standard support.
Reconciliation Packet · REC-3102
95% · Reconciliation Workspace
Version: Current close draft
Retrieved: 17:05:04
Governing status: Supporting
Aged reconciling items remain unresolved for the intercompany residual and suspense balance.
Version: Current close draft
Retrieved: 17:05:04
Governing status: Supporting
Aged reconciling items remain unresolved for the intercompany residual and suspense balance.
Intercompany Elimination · IC-6610
95% · Intercompany Workspace
Version: Current elimination pair
Retrieved: 17:05:05
Governing status: Supporting
Intercompany eliminations do not net to zero across segments and legal entities.
Version: Current elimination pair
Retrieved: 17:05:05
Governing status: Supporting
Intercompany eliminations do not net to zero across segments and legal entities.
Trading MTM Support · MTM-8832
93% · Trading Position Set
Version: Current position snapshot
Retrieved: 17:05:05
Governing status: Supporting
Mark-to-market entry exceeds held-position support in the valuation set.
Version: Current position snapshot
Retrieved: 17:05:05
Governing status: Supporting
Mark-to-market entry exceeds held-position support in the valuation set.
Provision / Actuarial Evidence · DECOM-991
92% · Actuarial Pack
Version: Current actuarial cycle
Retrieved: 17:05:05
Governing status: Supporting
Decommissioning provision moved outside the normal actuarial review cadence.
Version: Current actuarial cycle
Retrieved: 17:05:05
Governing status: Supporting
Decommissioning provision moved outside the normal actuarial review cadence.
Policy · CLOSE-RISK-009
97% · Policy Library
Version: Controlled current copy
Retrieved: 17:05:09
Governing status: Authoritative
Material journal anomalies and close-control breaches require controller escalation before close sign-off.
Version: Controlled current copy
Retrieved: 17:05:09
Governing status: Authoritative
Material journal anomalies and close-control breaches require controller escalation before close sign-off.
Evidence Lineage
→
Source System: Close Calendar
Close Calendar · M+5 close pressure and unresolved controller tasks established timing risk.
→
Source System: GL History
GL History · Current journal batch deviates from normal GL behavior.
→
Journal Anomaly Set
GL History · Decommissioning, recharge, and mark-to-market postings were grouped into one anomaly cluster.
→
Intercompany Elimination
Intercompany Workspace · Eliminations do not net to zero.
→
Trading MTM Support
Trading Position Set · MTM entries are inconsistent with held positions.
→
Close Risk Policy
Policy Library · Materiality and escalation thresholds applied.
→
Resolution Recommendation
bp Sphere · Escalate four anomalies, assign remediation owner, and clear exception before close sign-off.
Validation Script
Step 1 · Open the launch page
Click: /ui/use-case-launch?case=close_intelligence
Step 2 · Launch the mission
Click: Launch Continuous Close Intelligence
Step 3 · Start with readiness
Click: Click Enterprise Close Readiness
Continuous Close Intelligence Mission demonstrates the operating model before you enter the live workspace.