Exception monitoring for banks. Your core system already logs everything. Cold Case reads it, every period, and tells you which entries deserve a second look.
Your core banking system archives its activity as COLD reports: fixed-format text files covering maintenance, memo posts, transfers, overdraft decisions and more. They are complete, they are already yours, and at any real volume they are unreadable by hand.
So they sit in an archive until something goes wrong, and then someone spends weeks reading them backwards. Cold Case reads them forwards, as they are produced, so the pattern shows up while it is still small.
One ZIP of the period's COLD reports, monthly or quarterly, by upload or through a connected folder.
Nothing installed, and nothing written back. It reads the reports your system already produces.
Cold Case is a recurring service, not a one-off review. The value is the repetition: the same rules, run the same way, against every period you submit.
Upload the month or quarter as a single ZIP, or let it arrive in a connected folder.
Every report is parsed and tested, and you can watch the progress rather than wait on it.
An exception report: new exceptions set apart from recurring ones, and coverage stated plainly.
A catalog of fifty rules across eleven categories, drawn from real bank review work and generalized so they apply to any institution. Six of the families:
Address changes tested for the signature of manipulation, statement holds set alongside an address change, and notices suppressed from printing.
Repeated memo credits that raise an available balance with no real posting behind them.
Transfers between customers with no apparent relationship, and each user's rate measured against their peers.
Batches approved by the person who created them, and transactions edited after they were entered.
Pay and fee-waiver rates by reviewer, and fee refunds by user, each set against the rest of the team.
Holds released, traced to what moved immediately afterward.
A rule that fires forty times every month is part of how your bank works. A rule that fired four times last month and forty this month is the story. Exceptions are ranked by severity and then by change between periods, so the screen does the triage.
| Rule | Last period | This period | Trend |
|---|---|---|---|
| Unrelated-party telephone transfers | 4 | 40 | Sharp rise |
| Address change with a statement hold | 1 | 6 | Rising |
| Fee refunds above peer rate | 38 | 41 | Steady |
| Overdraft fee waivers by reviewer | 40 | 40 | Steady |
Illustrative figures.
Every exception opens to the rows behind it and the page of the original report, so it can be verified without leaving the screen.
Each exception is open, reviewed, or dismissed with a reason recorded, so the list shrinks as you work it instead of resetting every visit.
Which reports and days a period contained, and which it did not. A month with no report is not a month with no exceptions.
The period's exception report exports as a document you can hand to your board or your examiner.
A short call to walk through the reports your system produces and what Cold Case would read from them.
Book a Call