Bank Intelligence Cockpit — see fees, anomalies, and idle cash you didn't know you had

What's in today

• Multi-format ingestion: MT940 today
• Three persona dashboards: Executive Cash live; Treasurer + Reconciliation rolling out
• Bank-fee % of throughput, fee leaderboard, fee-per-non-fee-tx, idle-cash days
• 10 anomaly rules across deterministic and statistical families
• Reconciliation queue with case state machine and bulk actions
• 5 cost-saving rules with currency-denominated impact estimates
• LLM executive narrative, validated against numeric allow-list

What's coming

Coming soon: CAMT.053, BAI2, CSV-with-profile parsers. SAP-join reconciliation against BSID, BSAD, BSIK, BSAK. Conversational Q&A. Auto-categorisation. Treasurer dashboard rollout.

The anomaly engine

10 anomaly rules across two families.

Deterministic rules: duplicates, round-number transactions, weekend transactions (with country-aware Fri/Sat allow-list for SA, BH, QA, KW, OM, YE, EG, IQ), large outliers, frequency spikes, new counterparty, FX out-of-market quote, currency mismatch.

Statistical rules: z-score and IQR on transaction amounts and frequency.

Each anomaly fires with severity. Each has a “why” panel — what triggered it, what the threshold was, what the underlying figure is.

Cost-saving rules

Five rules that translate cash signals into euro-, SAR-, or USD-denominated impact estimates:

• Idle-cash sweep — cash sitting in low-yield accounts past a threshold
• Fee leader — accounts paying disproportionate bank fees
• Wire-vs-ACH — wire transfers under a threshold that should have been ACH/SEPA
• Duplicate fee — bank fees double-charged across statements
• FX spread — FX transactions above market spread

Each rule outputs an impact estimate in the customer's reporting currency.

Persona dashboards

Three dashboards. Today: Executive Cash is live. Treasurer and Reconciliation are rolling out.

Executive Cash gives the CFO live cash position, bank-fee KPIs, and idle-cash visibility. Treasurer and Reconciliation dashboards roll out next — designed for daily operations rather than monthly reporting.

AI narratives, validated against your numbers

Every figure in the executive narrative — total fees, idle-cash days, anomaly counts — is checked against the underlying aggregate. If a narrative drifts more than 5% from the source data, it's rejected. The CFO never reads a hallucinated KPI.

Frequently asked questions

Which bank statement formats are supported today?

MT940 is live. CAMT.053, BAI2, and CSV-with-profile are on the roadmap.

Does the anomaly engine handle GCC weekends?

Yes. Weekend transactions use a country-aware allow-list for Saudi Arabia, Bahrain, Qatar, Kuwait, Oman, Yemen, Egypt, and Iraq, where the working week is Sunday–Thursday and Fri/Sat are weekend days. A Saturday transaction in Riyadh isn't flagged as a weekend anomaly.

Can I reconcile against SAP postings today?

SAP-join reconciliation against BSID, BSAD, BSIK, BSAK is on the roadmap. Today's reconciliation queue works on the bank side with a case state machine and bulk actions.

How are cost-saving impacts denominated?

In your reporting currency — €, SAR, USD. Each cost-saving rule outputs an estimated impact figure with the underlying calculation.

Is the AI narrative editable before publish?

Narratives are auto-validated against the source aggregate; figures that drift get rejected. You read what survived the check.