Deposit-Flight & Fraud Guardian · Wisdom notebook
Ask the follow-up.
Agentic conversational BI · branch, then role, then destination — three cuts, one thread
Are any branches breaking fixed deposits earlier than they should be?
RKScored all ten branches on four KPIs at once — Contact-Change Count, Micro-Test Intensity, FD Premature Broken and First-Payee Outflow — counting how many of the four were outside their own band in the same week, rather than reading any one of them alone.
One confirmed, two worth a look. Branch 07 is the only branch with all four KPIs out of band. Two more have two of the four out while their amounts stay unremarkable — which is why the count is what gets scored, not the size:
All ten branches — how many of the four KPIs are out of band
Branch 03 and Branch 09 would not appear on any single-KPI alert — their amounts are ordinary, and each has a different two of the four out of band. They surface only because the four are read together. Neither is an accusation; both are a call to the branch manager this afternoon rather than a finding in next month's review.
Hold Branch 07 and split those breaks by staff role — who processed them?
RKHeld Branch 07 and its affluent slice, then cut the $306.8K of premature breaks by STAFF_ROLE, and set the ticketless ones — the breaks with no authorisation ticket behind them — against the same dimension.
One role. Back office processed $217.9K of the $306.8K — 71.0% — and all five ticketless breaks. The counter roles are inside their normal range on both:
The $306.8K of premature breaks, by STAFF_ROLE
Every ticketless break in the branch went through one role. That is not an accusation of anybody — a compromised session, a shared credential and a genuine control gap all look identical here. What it does say is that the break path and not the customer is where this needs looking, and it narrows the review from a branch to a queue.
Take that back-office slice — where did that money actually go?
RKKept only the $217.9K processed by back office and cut it by PAYEE_STATUS and PAYMENT_RAIL — who received it and how fast it moved — rather than looking at the branch total again.
Almost all of it to people we have never paid before, most of it on rails that settle the same day. $201.3K of the $217.9K — 92.4% — went to first-time payees, and $149.2K of that moved on instant rails:
The back-office $217.9K, by payee status and rail
This is the chain end to end: the breaks concentrate in one processing role, and that role's money concentrates on beneficiaries with no history and rails with no recall window. $149.2K is already unrecoverable by rail design. The $52.1K on wire is the part where speed still buys something, which is why this belongs on a desk today and not in a monthly pack.