Use cases
Automation in banking across 9 use cases
Nine processes that share one engine. Each row names the role that owns it, the metric it moves and the first thing to automate. Start with one, not with all of them. Each is a banking automation system use case and a workflow automation use case at once.
01
Correspondent statement against the internal nostro ledger, with value date and FX rate source tolerances set per correspondent.
Moves
Break aging, intraday liquidity accuracy
02
Scheme and network settlement files against core postings, with interchange and scheme fees modelled rather than surfacing as differences.
Moves
Unreconciled settlement balance, fee leakage
03
Three way matching of the pacs.008 batch, the settlement and the core posting, so partials and lifting fees are visible the same day.
Moves
Repair rate, investigation volume
04
Every return tied to its original instruction, with the reason code carried, rather than posted as unexplained activity.
Moves
Time to resolve, customer complaints
05
Item level ownership and aging instead of a monthly balance review, which is the only thing that makes suspense shrink.
Moves
Suspense balance, manual journals at close
06
Daily matching of sub-ledger movement to GL postings, with mapping and timing differences classified rather than explained in a comment box.
Moves
Close cycle days
07
Certification as a system state with preparer and reviewer separation, and the quarter-end pack as an export.
Moves
Audit findings, evidence assembly time
08
Refresh population built from risk rating and review dates, assigned, aged, chased and evidenced against the customer file.
Moves
Overdue review population
09
Alerts from your monitoring platform worked as cases with required evidence and maker-checker disposition. Detection stays where it is.
Moves
Backlog age, disposition consistency
Sequencing
Which one to automate first
The answer is almost always the process with the most manual hours and the least documented logic, not the one that looks easiest to configure.
If operations is sponsoring
Start at nostro or card settlement. Highest daily pain, clearest break vocabulary, and the fastest way to prove the exception workflow to the rest of the floor.
If finance is sponsoring
Start with the suspense or clearing account that generates the most manual journals at close. The evidence pack argument sells itself at the first quarter end.
If compliance is sponsoring
Start with the periodic refresh queue rather than alert triage, because the population is calculable and the overdue number is already known to be a problem.
Read the detail by process
Get started
Put your first reconciliation on rails
Create an account, and we will email you how onboarding works and what a first source connection looks like. The Reconciliation Break Resolver is open to try right now, on sample data, without an account.