Skip to main content

Cash & Nostro Reconciliation

Cash and nostro reconciliation, without the manual chase.

Reconcile MT940/MT950, CAMT.053/054 and internal ledger cash across every nostro, vostro and internal account — with AI-assisted triage that groups breaks by likely cause for your team to review and approve.

MT940 · CAMT.053
Statement formats reconciled
1:1 · 1:N · N:N
Matching modes supported
Intraday
Runs on statement arrival
For Treasury OperationsFor Nostro Recon TeamsFor Cash Management

The problem

The reconciliation problems this solves

Fragmented statements

Dozens of correspondent banks, mixed MT and ISO 20022 formats, timezone-dependent value dates and non-standard narratives.

Fee & FX noise

Small fees, rate differences and rounding create high-volume, low-value breaks that swamp analysts.

Duplicate & missing entries

Bank-side reversals and internal ledger delays create pending items that age silently past MTTR SLAs.

Regulatory pressure

BCBS 239, DORA and internal audit demand traceable, replayable evidence for every match and write-off.

Capabilities

What ReconIQ does for this use case

Agentic break triage

AI clusters cash breaks by root cause (fee, FX, timing, duplicate) and drafts resolutions under policy gates.

Configurable matching rules

1:1, 1:N, N:N, tolerance, fuzzy narrative, composite keys — tuned for MT940/CAMT semantics.

Statement normalisation

Pre-built transforms map narratives, value dates and reference fields into a canonical cash model.

Ageing & MTTR SLAs

Per-account ageing buckets, reviewer SLAs, escalation policies and near-real-time dashboards.

Four-eyes write-off

Purpose-built Break Manager with maker-checker approvals for tolerance write-offs and forced matches.

Hash-chained audit

Every match, break, comment and approval is signed into an immutable evidence chain for regulators.

Data sources supported

  • SWIFT MT940 / MT942 / MT950 statements
  • ISO 20022 CAMT.053 / CAMT.054 / CAMT.052
  • Core banking GL extracts (Flexcube, T24, Finacle, Vision Plus)
  • SWIFT gpi tracker events
  • Payment gateway settlement files (CSV, XML, fixed-width)
  • Legacy fixed-width mainframe drops

What this gives you

Automated
First-pass matching with tolerance and fuzzy-narrative rules
Grouped
Breaks clustered by likely cause — fee, FX, timing, duplicate
Four-eyes
Approval required for write-offs and forced matches
Hash-chained
Audit evidence for every match, break and approval

Designed with reference to the frameworks that matter here

Controls are designed with reference to these frameworks and regimes. See Security & Compliance for the full picture.

BCBS 239DORASOX ICFRISO 20022SWIFT CSPSOC 2 Type II (target)

ReconIQ does not hold SOC 2 or ISO 27001 certification. Entries marked “(target)” or “(aligned)” describe design references and roadmap targets, not certifications we have earned.

Questions

Frequently asked

How does ReconIQ handle correspondent-bank fee breaks?+

Fees are matched using tolerance and fuzzy narrative rules; residuals are auto-clustered by counterparty and routed to a tolerance write-off queue that supports four-eyes approval and policy caps.

Can we run cash recon intraday?+

Yes. ReconIQ supports scheduled, event-driven and streaming triggers, so cash can be reconciled hourly or on statement arrival, ahead of a same-day close.

Does ReconIQ support ISO 20022 migration?+

Both MT and CAMT formats are supported natively, and the Data Prep pipeline maps legacy MT narratives to canonical ISO fields so you can migrate without breaking historical rules.

See it on your data.

Try the live demo, or book a session to walk a cash & nostro reconciliation workflow end to end.