Reconciliation · Payment operations · Compliance
Banking automation software for bank operations teams
Reconciliation, payment operations and compliance workflows in one system. Bank formats are parsed on day one, breaks are classified and routed, every action lands on an audit trail.
camt.053 · NOSTRO USD · value date 03 sep 2026
Match rate
75.0%
Breaks
4
At risk
$533.9k533,925.40
Oldest
4d
Break
Amount
Difference and suggested action
Classification
BRK-001
Aged 0d
$219,105.40
REF//FX/SPOT/7741 · INTERBANK FX DESK
Re-price the ledger leg on the correspondent rate source for the value date and post 164.80 USD to FX variance.
BRK-002
Aged 4d
$187,650.00
PAY/90012/R · KESTREL LOGISTICS
Confirm the original entry REF//PAY/90012 cleared, then reverse this posting under maker-checker and note the reversal on the original item.
BRK-003
Aged 0d
$123,760.00
REF//TRF/554121 · HALCYON TRADING
Split the ledger posting and match the settled leg; leave the residual 61,880.00 USD open against the same reference.
BRK-004
Aged 0d
$3,410.00
REF//CHG/Q3FEES · CORRESPONDENT CHARGES
Post 3,410.00 USD to the charges account for the period and add it to the standing accrual so it stops surfacing as a break.
·
Everything matched under these tolerances.
Correspondent statement
| Value date | Reference | Amount | Counterparty |
|---|---|---|---|
| 2026-09-02 | REF//NONREF/2026090301 | 1,284,500.00 | ACME MANUFACTURING |
| 2026-09-02 | REF//INV/88231 | 96,400.00 | NORDVEST SHIPPING |
| 2026-09-03 | REF//TRF/554120 | 452,180.25 | HALCYON TRADING |
| 2026-09-03 | REF//FX/SPOT/7741 | 218,940.60 | INTERBANK FX DESK |
| 2026-09-01 | REF//SEPA/33421 | 74,220.00 | LINDQVIST AS |
| 2026-09-03 | REF//CHG/Q3FEES | 3,410.00 | CORRESPONDENT CHARGES |
| 2026-09-03 | REF//TRF/554121 | 61,880.00 | HALCYON TRADING |
| 2026-09-02 | REF//PAY/90012 | 187,650.00 | KESTREL LOGISTICS |
| 2026-09-02 | REF//INV/88245 | 242,015.00 | BRIGHTLINE FOODS |
| 2026-09-03 | REF//TRF/554133 | 18,905.50 | MERIDIAN PARTS |
| 2026-09-01 | REF//PAY/90044 | 505,300.00 | VANTAGE ENERGY |
| 2026-09-03 | REF//INV/88260 | 132,640.75 | ORION TEXTILES |
Internal nostro ledger
| Value date | Reference | Amount | Counterparty |
|---|---|---|---|
| 2026-09-02 | NONREF/2026090301 | 1,284,500.00 | ACME MANUFACTURING |
| 2026-09-02 | INV/88231 | 96,400.00 | NORDVEST SHIPPING |
| 2026-09-03 | TRF/554120 | 452,180.25 | HALCYON TRADING |
| 2026-09-03 | FX/SPOT/7741 | 219,105.40 | INTERBANK FX DESK |
| 2026-08-31 | SEPA/33421 | 74,220.00 | LINDQVIST AS |
| 2026-09-02 | PAY/90012 | 187,650.00 | KESTREL LOGISTICS |
| 2026-09-03 | TRF/554121 | 123,760.00 | HALCYON TRADING |
| 2026-08-30 | PAY/90012/R | 187,650.00 | KESTREL LOGISTICS |
| 2026-09-02 | INV/88245 | 242,015.00 | BRIGHTLINE FOODS |
| 2026-09-03 | TRF/554133 | 18,905.50 | MERIDIAN PARTS |
| 2026-09-01 | PAY/90044 | 505,300.00 | VANTAGE ENERGY |
| 2026-09-03 | INV/88260 | 132,640.75 | ORION TEXTILES |
Run this on your own files
The 6pm problem
Bank operations still close the day in spreadsheets
Not because the team is slow. Because the statement, the ledger and the settlement file disagree in ways nobody has written down, and the difference is argued out by hand every single day.
01 · Intake
Three formats, one pair of eyes
MT940 and camt.053 land from the correspondents, the core exports something slightly different, card and ATM settlement arrives in a third shape, and a credit union adds share draft and shared branching settlement on top. Somebody normalizes all of it in a workbook before matching can even start.
02 · The break
Worked in an email thread
An unmatched item becomes a message to treasury, a reply two days later, a screenshot, a decision nobody records. Ageing is invisible until it is a finding, and the same break returns next month.
03 · Quarter end
Evidence rebuilt by hand
When audit asks how an item was resolved, the answer is assembled from inboxes and file shares. The reconciliation was done. Proving it was done correctly is a separate project.
The pattern repeats in payment operations, where repairs, returns and investigations are worked manually, and in compliance, where KYC refresh queues and alert triage are tracked in a list on the side. Read the process by process breakdown in automation in banks, or start with bank reconciliation software if the daily cash break is what hurts.
What Bankautomation does
Bank-native automation, not a blank workflow canvas
Every competitor sells either an engine without the workflow, or the workflow without the banking. This is one product: the banking data model, the matching engine and the exception queue.
01
Bank formats parsed on day one
camt.053 and camt.054, MT940, MT942 and MT950, pain.001 and pacs.008, card and ATM settlement files, core banking exports and plain CSV. Field mapping is configuration, not an integration project.
02
Matching you can explain
Exact key match first, then tolerance matching on value date, amount and normalized references. Every match records which rule fired and which tolerance absorbed the difference.
03
Breaks classified and routed
FX rate source, timing, duplicate posting, missing reference, fee not accrued, partial settlement. Each break gets a suggested action, an owner queue and an age visible from the first hour.
04
Maker-checker built in
Write-offs, reversals, tolerance changes and rule edits are proposed by one role and approved by another. Segregation of duties is enforced by the system, not by a note in a procedure document.
05
Audit trail by construction
Every rule version, override, approval and attachment is kept against the item. The quarter-end evidence pack is a filtered export, not four days of rebuilding history from email.
06
Rules your ops team edits
A tolerance, a reference normalization rule or a routing target is changed in the interface under approval. No specialist, no change request, no waiting for a release window.
The engine is one product across all three process lines: see it applied to payment reconciliation, AML compliance workflow and general ledger reconciliation.
How it works
Four steps, and the fourth is a download
The same four steps run whether the source is a nostro statement, a settlement file or a KYC refresh queue.
-
Step 01
Connect a source
Drop the statement and the ledger export in. Formats are recognized, fields are mapped, the day is opened.
-
Step 02
Match under your tolerances
Exact first, then value date, amount and reference tolerances that your team owns and can change.
-
Step 03
Work the exception queue
Each break arrives classified, aged and routed, with a suggested action and the evidence attached to the item.
-
Step 04
Export the evidence
Sign-off, the rule versions that ran and every approval come out as one pack for audit or the regulator.
See bank process automation step by step, including what happens on the first day with a new source.
Worked example
One nostro break, from raw rows to a routed item
This is resolver output for a single item in the sample above. Nothing here is a customer, an account or a result we measured. It is what the product does with those rows.
Input
- Statement · 2026-09-03 · REF//FX/SPOT/7741 · 218,940.60 USD · INTERBANK FX DESK
- Ledger · 2026-09-03 · FX/SPOT/7741 · 219,105.40 USD · INTERBANK FX DESK
Output
- BRK-001 FX rate source Aged 0d
- Difference 164.80 USD (0.075 percent) against a matched reference and value date.
- Suggested action: re-price the ledger leg on the correspondent rate source for the value date and post 164.80 USD to FX variance.
- Routed to Treasury Ops, with the audit note written and the rule version attached.
Where this sits
Against the three things banks use today
Category-level differences, not a scorecard about named vendors. Every row is something a buyer can check in a demo.
| Capability | Bankautomation | Spreadsheet close | Generic RPA | Corporate close platform |
|---|---|---|---|---|
| Bank formats native | ISO 20022, SWIFT MT, settlement files parsed as inputs | Manual export and reshaping | Screen-scraped from a screen that changes | Built for corporate sub-ledgers |
| Nostro and settlement model | Value date, correspondent, FX source, two sided | Whatever the workbook models | None | Not part of the data model |
| Exception workflow | Classified, aged, routed, approved in product | Email threads and a tab called Issues | Bot stops, a human is emailed | Task lists tuned to the close calendar |
| Audit evidence | Versioned rules, approvals and attachments, exportable | Reassembled by hand at quarter end | Bot logs, not business evidence | Strong for the corporate close |
| Time to first reconciliation | Weeks, because the formats are already parsed | Immediate and permanent | Months per process, then maintenance | Integrator-led programme |
| Who changes a rule | Your ops team, under maker-checker | Whoever owns the file | The automation team, on a backlog | A consultant on a change request |
If bots are the incumbent in your bank, the honest comparison is on robotic process automation in banking. If the finance team owns the project, start at account reconciliation software.
For the COO and the CFO
The case that gets signed
Three questions decide this purchase, and none of them is about matching algorithms.
Cost
Hours back from the daily close
Two analysts, four hours a day, on breaks and evidence. Price the recovered hours against the plan you would buy and decide. We will not quote you a saving we did not measure.
Risk
Ageing that is visible on day one
Breaks carry an age, an owner and an attached history. Nothing is worked in a mailbox, so nothing quietly sits at 40 days until an auditor finds it.
Control
Segregation of duties enforced
Maker-checker on write-offs, reversals and rule changes. Versioned rules, an immutable log and role separation your second line can inspect. See security and compliance.
Pricing
Four plans, published
Priced per institution, not per bot and not per reconciliation. There is no free plan: the resolver above is the free taste.
Operations
$1,200
One ops team automating a single process line.
- 1 line: reconciliation, payment ops or compliance
- 250,000 matched items a month
- 3 source connections
- 10 users
Platform
Recommended$3,900
The whole operations floor, all three process lines.
- All three process lines
- 2,000,000 matched items a month
- Unlimited source connections
- 50 users
Institution
$9,500
Multi-entity banks and banking groups.
- All three lines, multi-entity
- Unlimited matched items
- Unlimited source connections
- Unlimited users
Enterprise
Talk to sales
Regulated deployments that go through procurement.
- All three lines, custom scope
- Unlimited matched items
- Unlimited source connections
- Unlimited users
Questions we get asked first
Before you put an email in
The full set, including deployment, controls and procurement, is on the FAQ page.
Is my data safe if I paste rows into the demo?
The Reconciliation Break Resolver is for sample data only, and the page says so above the input. Matching runs in your browser. When you press Run, the break summaries (reference, amount, currency, value date and the computed difference) are sent to the classification model so it can write the classification and the suggested action. Bankautomation does not store the rows you paste, and there is no account behind the demo. Do not paste production or customer data. The privacy policy spells this out.
Do you connect to our core banking system?
The day-one path is file based, because that is what every bank can produce this week: camt.053 and camt.054, MT940, MT942 and MT950, pain.001 and pacs.008, card and ATM settlement files, core banking exports and CSV. Where an API exists on your side, a source can be configured to pull from it on a schedule instead. We do not publish a list of pre-built core banking connectors, because the honest answer is that it depends on what your core exposes.
Does this replace our controls or our compliance team?
No. Bankautomation is operations software: it matches, classifies, routes, records and evidences. Suggested classifications and actions are decision support. Approvals, compliance determinations, regulatory filings and the control framework itself stay with your institution and its people. Automation supports the control, it does not become the control.
How long until the first reconciliation runs?
The design intent is weeks rather than quarters, because the bank formats are already parsed and matching rules are configuration rather than development. That is a statement about how the product is built, not a measured customer average, and we will not pretend otherwise. What takes the time on your side is agreeing tolerances, routing and who approves what.
Who can change a matching rule?
Your operations team, in the interface, under maker-checker. One role proposes a tolerance, a reference normalization rule or a routing target, another approves it, and the change is versioned against every item it later touches. No vendor change request, no specialist consultant, no release window.
Do you support ISO 20022 and CBPR+?
Yes. ISO 20022 messages are first-class inputs, not a conversion step bolted on the side, and structured remittance and party data is used by matching rather than flattened into a memo field. See ISO 20022 payment automation for the detail and ISO 20022 explained for the background.
Automation by process
Where teams start
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.