Skip to content
Bankautomation

Live demo · sample data only

Reconciliation Break Resolver

Pick a source pair, set the tolerances your team would actually agree to, and run it. The matching is real and runs in your browser. Every break comes back classified, aged, routed and exportable.

  • Do not paste production or customer data
  • Nothing you paste is stored
  • No account needed

camt.053 · NOSTRO USD · value date 03 sep 2026

Nostro cash break, sample data

Match rate

75.0%

Breaks

4

At risk

$533.9k

Oldest

4d

Date ±1d
Amount

Sample data only. Do not paste production or customer data. Up to 40 rows a side.

This console matches the first rows a side. It left out statement and ledger , so anything in them is not counted below. To run a full file, .

BRK-001

Aged 0d

$219,105.40

2026-09-03 · both sides

REF//FX/SPOT/7741 · INTERBANK FX DESK

Amount differs by 164.80 USD (0.075%)

Re-price the ledger leg on the correspondent rate source for the value date and post 164.80 USD to FX variance.

FX RATE SOURCE

→ Treasury Ops

BRK-002

Aged 4d

$187,650.00

2026-08-30 · ledger

PAY/90012/R · KESTREL LOGISTICS

Second ledger entry for 187,650.00 USD against REF//PAY/90012

Confirm the original entry REF//PAY/90012 cleared, then reverse this posting under maker-checker and note the reversal on the original item.

DUPLICATE POSTING

→ Finance

BRK-003

Aged 0d

$123,760.00

2026-09-03 · both sides

REF//TRF/554121 · HALCYON TRADING

Statement 61,880.00 vs ledger 123,760.00 (50% short)

Split the ledger posting and match the settled leg; leave the residual 61,880.00 USD open against the same reference.

PARTIAL SETTLEMENT

→ Payments Ops

BRK-004

Aged 0d

$3,410.00

2026-09-03 · statement

REF//CHG/Q3FEES · CORRESPONDENT CHARGES

On the statement, nothing in the ledger

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.

FEE NOT ACCRUED

→ Finance

Everything matched under these tolerances.

Tighten the date or amount tolerance to see the breaks it was absorbing.

Correspondent statement

camt.053 · NOSTRO USD

Value date Reference Amount
2026-09-02 REF//NONREF/2026090301 1,284,500.00
2026-09-02 REF//INV/88231 96,400.00
2026-09-03 REF//TRF/554120 452,180.25
2026-09-03 REF//FX/SPOT/7741 218,940.60
2026-09-01 REF//SEPA/33421 74,220.00
2026-09-03 REF//CHG/Q3FEES 3,410.00
2026-09-03 REF//TRF/554121 61,880.00
2026-09-02 REF//PAY/90012 187,650.00
2026-09-02 REF//INV/88245 242,015.00
2026-09-03 REF//TRF/554133 18,905.50
2026-09-01 REF//PAY/90044 505,300.00
2026-09-03 REF//INV/88260 132,640.75

Internal nostro ledger

Core banking export

Value date Reference Amount
2026-09-02 NONREF/2026090301 1,284,500.00
2026-09-02 INV/88231 96,400.00
2026-09-03 TRF/554120 452,180.25
2026-09-03 FX/SPOT/7741 219,105.40
2026-08-31 SEPA/33421 74,220.00
2026-09-02 PAY/90012 187,650.00
2026-09-03 TRF/554121 123,760.00
2026-08-30 PAY/90012/R 187,650.00
2026-09-02 INV/88245 242,015.00
2026-09-03 TRF/554133 18,905.50
2026-09-01 PAY/90044 505,300.00
2026-09-03 INV/88260 132,640.75
Matched pairs are tinted on both sides. Breaks carry the brass left rule and appear in the worklist.

Sample data only. Matching runs in your browser; classification is written by the model when you press Run. Matching done in your browser. Writing classifications… Classifications written by the model on this run. Decision support, not a compliance determination. The classification model was unavailable, so the built-in rule classifier wrote these. Same matching, same numbers. This console classifies up to 12 runs a minute and this run went over, so the built-in rule classifier wrote these. Same matching, same numbers. Wait a minute for the model, or . The model wrote the first 8 classifications; the rule classifier wrote the remaining .

What is actually happening

01

Matching, in your browser

A two pass matcher runs on the rows: an exact key match on normalized reference, amount and value date, then a tolerance pass under the date and amount rules you set. The same algorithm renders this page on the server, so the numbers are identical with or without JavaScript.

02

Derived facts, not opinions

Break aging, value at risk, the exact difference on each item and the match rate split between exact and tolerance matches are all computed from the rows. No model touches a number.

03

Classification by model, with a fallback

When you press Run, the structured differences go to a language model through a server side proxy, which writes the classification, the suggested action, the route and the audit note. If it is unavailable or rate limited, a rule based classifier writes them and the console tells you which one you are reading.

04

Export what you see

Download CSV gives you the worklist exactly as displayed: break id, side, value date, reference, currency, amount, age, difference, classification, suggested action, route and audit note.

Things worth trying

  1. 01Set the date tolerance to zero on the nostro sample. A timing break appears, because a correspondent posted a day earlier than your ledger expected.
  2. 02Set the amount tolerance to 0.5 percent. The FX rate source difference is absorbed into a match. Ask yourself whether you would approve that tolerance on this account.
  3. 03Turn reference normalization off. The exact match count drops to zero, because a correspondent writes REF//NONREF/2026090301 where your ledger writes NONREF/2026090301.
  4. 04Switch to the card settlement sample. The interchange fee that was never accrued is the item that turns up every single day in a real operation.
  5. 05Paste your own rows in the same four column shape, with a line containing only two dashes between the statement block and the ledger block.

The honest limits

  • This is a demo of matching and exception handling on sample data. It is not a connection to your bank, it has no account behind it and it stores nothing.
  • Suggested classifications and actions are decision support. They are not a compliance determination and not accounting advice.
  • The full product adds scheduled sources, per account rules, maker-checker approvals, routing to real queues and the evidence pack. See how it works.

The same engine, by process

Account reconciliation software Where the differences start, account by account. Bank reconciliation software Statement against ledger, MT940 and camt.053 native. Automated reconciliation software Match rates, tolerances, and what auto-match must never mean. Payment reconciliation software Instructed, settled and posted, reconciled three ways. Financial reconciliation software The same engine, framed for the finance team. ATM reconciliation software Cash, switch and network settlement, balanced daily. Credit union reconciliation software Corporate, share draft, card, ATM and shared branching. ACH reconciliation software Origination, receipt, returns and FedACH settlement. Federal Reserve account reconciliation Master account, FIRD, Fedwire and FedNow against the GL. Correspondent bank reconciliation Due from, due to and respondent settlement against the GL. AML compliance software Program workflow, evidence and cadence. Not a detection model. KYC automation software Onboarding and periodic refresh, queued and evidenced. AML software for banks What to ask, and what to refuse to buy. Compliance workflow automation Maker-checker, SLAs and evidence as a system property. BSA AML monitoring software Alert triage as a worklist, not a second inbox. RPA for banks Why screen-scraping bots break, and what replaces them. General ledger reconciliation software Sub-ledger to GL, and the suspense account nobody owns. Balance sheet reconciliation software Certification, sign-off and the quarter-end pack. ISO 20022 payment automation Structured data, repair rates and CBPR+ deadlines. Nostro reconciliation automation The most bank-specific reconciliation there is.

After the demo

Run this on your own files

Create an account and we will email you how onboarding works, what a first source connection looks like and how to get your own files reconciled.

Run the demo

No card required to create an account. Sample data only in the demo. Bankautomation is operations software, not a regulated service.