Skip to content
BankAutomation

Questions: [email protected]

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.

Run the demo
  • Sample data only in the demo
  • Your data stays yours
  • No card required to create an account

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 . Nothing in the rows left out is 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

Posted in the ledger, not on the statement

Trace the posting to its instruction, repair the reference and re-present it, or reverse it if the payment was returned.

MISSING REFERENCE

→ Payments Ops

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 rest ().

Run this on your own files

Pick a queue, move the tolerances, press Run. Matching happens in your browser, then the classification and the audit note are written for each break. Create an account and we will email you how onboarding and a first source connection work.

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 correspondent accounts, 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. Aging 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 banking, 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.

  1. Step 01

    Connect a source

    Drop the statement and the ledger export in. Formats are recognized, fields are mapped, the day is opened.

    camt.053 · MT940 · CSV · core export

  2. Step 02

    Match under your tolerances

    Exact first, then value date, amount and reference tolerances that your team owns and can change.

    ±1d · one cent · ref normalization

  3. Step 03

    Work the exception queue

    Each break arrives classified, aged and routed, with a suggested action and the evidence attached to the item.

    Treasury Ops · Payments Ops · Finance

  4. 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.

    CSV · PDF pack · API

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

Two rows that will not match on the key

  • 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

Same value date, same reference once normalized, amounts 164.80 apart. Under an exact amount tolerance this is a break, not a match.

Output

One worklist item, ready to work

  • 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

Swipe the table sideways to read every column.

Comparison of approaches, not of specific products. Deployment timelines describe design intent and typical market experience, not a measured customer average.

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.

If a reconciliation vendor is already in place, the replacement guides for Frontier Reconciliation software, Trintech ReconNET, Accurate Reconciliation software, Modern Treasury alternatives and OneStream account reconciliation map each product to the daily work of a US bank, with pricing side by side.

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

Aging 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.

Save 50% with annual billing. Half the monthly rate, charged once a year.

Operations

$1,200$600

per month, billed monthlyper month, billed $7,200 a year, save 50%

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 user seats
Get started

Platform

Recommended

$3,900$1,950

per month, billed monthlyper month, billed $23,400 a year, save 50%

The whole operations floor, all three process lines.

  • All three process lines
  • 2,000,000 matched items a month
  • Unlimited source connections
  • 50 user seats
Get started

Institution

$9,500$4,750

per month, billed monthlyper month, billed $57,000 a year, save 50%

Multi-entity banks and banking groups.

  • All three lines, multi-entity
  • Unlimited matched items
  • Unlimited source connections
  • Unlimited users
Get started

Enterprise

$14,900$7,450

per month, billed monthlyper month, billed $89,400 a year, save 50%

Regulated deployments that go through procurement.

  • All three lines, multi-entity
  • Unlimited matched items
  • Unlimited source connections
  • Unlimited users
Get started

Paid plans are paid by card on a secure checkout; creating an account from the demo needs no card. See the full pricing table, including annual billing, limits, SLA and procurement terms.

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 resolver is for sample data only: matching runs in your browser and BankAutomation does not store the rows you paste. Only the break summaries go to the classification model when you press Run. The detail is in the FAQ.

Do you connect to our core banking system?

Through files first, because every bank can export camt.053, MT940, settlement files and core banking CSV this week. Where your side exposes an API, a source can pull from it on a schedule. More in the FAQ.

Does this replace our controls or our compliance team?

No. BankAutomation matches, classifies, routes and evidences, and its suggestions are decision support. Approvals, determinations and filings stay with your people.

How long until the first reconciliation runs?

Weeks rather than quarters is the design intent, because bank formats are already parsed and rules are configuration. What takes the time is agreeing tolerances, routing and approvers.

Who can change a matching rule?

Your operations team, in the interface, under maker-checker. Every change is versioned against the items it touches.

Do you support ISO 20022 and CBPR+?

Yes, as first-class inputs, with structured remittance and party data used by matching. See ISO 20022 payment automation.

What about SSO, roles, residency and the audit log?

SSO, segregation of duties, maker-checker, an immutable audit log and a residency choice come with Platform and above. The full list is on the security page.

What does it cost, and can we try it before paying?

Operations is $1,200 a month, Platform $3,900, Institution $9,500 and Enterprise $14,900, with annual billing at half the monthly rate. The resolver above is open without an account, and there is no free plan.

How do we buy, and will you survive our InfoSec review?

Invoicing from Platform, purchase orders from Institution, and MSA, DPA and a named review contact on Enterprise. Procurement and deployment questions are answered in full on the FAQ page.

Automation by process

Where teams start

Each page covers one process end to end: the inputs, the breaks it produces and how they get worked.

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. Suspense account reconciliation Suspense and clearing accounts worked item by item, with an owner and an age. Frontier Reconciliation alternative What replaces each Frontier module when the upgrade quote arrives. ReconNET alternative What replaces each ReconNET workload at a bank or credit union, with pricing. Trintech Adra alternative What replaces Adra Matcher and Balancer at a bank or credit union, with pricing. Trintech Cadency alternative What replaces Cadency matching and reconciliation at a bank or credit union, with pricing. Accurate Reconciliation alternative What replaces Trintech Accurate matching and certification at a US bank, with pricing. SolveXia alternative What replaces SolveXia reconciliation at a US bank or credit union after the GTreasury deal, with pricing. OneStream reconciliation alternative When a US bank on OneStream should keep its Account Reconciliations solution, and when daily settlement matching belongs elsewhere. Modern Treasury alternatives When a US bank or fintech program needs reconciliation without adopting a new payment provider. Debit card reconciliation software Network settlement, interchange and disputes matched to the core every morning. Cash reconciliation software Vault, ATM, Fed cash and due from accounts tied to the GL every day. Loan reconciliation software Loan subledger, payment clearing, escrow and investor remittances tied to the GL. Transaction matching software Every settlement line paired with its postings, every break owned. Check reconciliation software Cash letters, inclearings, returns and official checks tied to the Fed and the GL. Fiserv reconciliation software Daily ACH, switch, card, Fed and GL reconciliation for banks and credit unions on Fiserv cores. Jack Henry reconciliation software Daily ACH, card, instant payment, Fed and GL reconciliation for banks and credit unions on Jack Henry cores. FIS reconciliation software Daily ACH, Fedwire, card, Fed and correspondent reconciliation for banks on FIS IBS and Horizon cores. camt.053 reconciliation software camt.053, MT940 and BAI2 statements matched to the GL daily, with every break owned. Instant payments reconciliation software FedNow and RTP settlement matched to the core by cycle, seven days a week, with unposted payments owned and aged. Wire transfer reconciliation software Fedwire, CHIPS and SWIFT wires matched to the core, the Fed account and the correspondent statement, with unmatched wires owned and aged. Zelle reconciliation software Zelle activity matched to core postings and ACH or RTP settlement, with weekend balances explained and unposted payments owned. Credit card settlement reconciliation software Visa and Mastercard settlement, interchange income, rewards and disputes matched to the card ledger every morning. 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. Payment exception management Returns, rejects and unmatched payments owned, aged and closed.

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.

Run the demo

Creating an account with the button above needs no card; paid plans are paid on our payment processor's secure page. Sample data only in the demo. BankAutomation is operations software, not a regulated service.