Exceptions desk
One operations queue for every payment exception: scheme returns, failed standing orders, quarantined bulk items and sanctions holds. Cases are raised automatically by the engines that produce them — the simulated settlement sweep, the standing-order sweep and bulk file execution — so nothing reaches this desk by somebody remembering to file it.
A case walks open → assigned → resolved and cannot skip a step: every resolution has a named owner and a written note. Only an authorised operations user may assign or resolve, and that is enforced in the write transaction, not by hiding a button. Age is derived from the creation date on every read, so a bucket is never stale, and the oldest work carries the emphasis.
Open work by type and age
Not polling: nothing on screen can change status any more. Showing state as of .
The exceptions desk is clear: no unresolved case is open. Cases are raised automatically by the settlement engine, the standing-order sweep and bulk file execution, and appear here the moment they are.
The exceptions desk is clear: no unresolved case is open. Cases are raised automatically by the settlement engine, the standing-order sweep and bulk file execution, and appear here the moment they are.
The queue
0 cases match this view · page 1 of 1
No exception case exists yet. Cases appear here the moment an engine raises one; nothing is filed by hand.
Sample book disclosure: the customer accounts, staff users and sanctions watchlist in this environment are seeded demonstration data created by this module — there is no connection to a real core banking system, payment scheme or sanctions feed. Batch (ACH-style) clearing and high-value wire settlement both run through this module's own SIMULATED settlement engine, never a real scheme or wire network.