Use cases

ISO 20022 statements and payment files — real-world use cases

From reconciling camt.053 statements to checking pain.001 files before upload and moving off MT940, here is how treasury, payments and bank operations teams, and AI agents, use ISO 20022 Navigator.

100% in-browser processing — your file never leaves your device

Open the free camt.053 viewer

No. 01

Treasury & accounting

Treasury & accounting: reconcile camt.053 statements against the ledger

The problem

End-of-day statements now arrive as camt.053 XML. When the cash position doesn’t tie out, someone has to find the one entry that matches nothing in the ERP, inside thousands of lines of nested Ntry, NtryDtls and TxDtls tags. A single batch booking on the statement can stand for hundreds of individual payments, and the reference the ledger knows may sit three levels down.

How ISO 20022 Navigator helps

Open the statement in the camt Statement Viewer. Each account shows its opening and closing balances with the type codes (OPBD, CLBD, CLAV) explained, and the roll-forward is checked: opening booked balance plus booked entries must equal the closing booked balance. Every entry lists its amount, credit or debit, booking and value dates, bank transaction code in words and AcctSvcrRef, and each transaction inside a batch its EndToEndId, counterparty and remittance text. Export to CSV to match it against the ledger in a spreadsheet.

Key conceptsBalance types OPBD, CLBD, CLAV Bank transaction codesEndToEndId and AcctSvcrRefBatch bookings and TxDtlsBalance roll-forward

No. 02

Payments operations

Payments operations: check a pain.001 before it goes to the bank

The problem

A payment run exported from the ERP or treasury system goes up to the bank portal and is rejected hours later, or partly accepted. The usual causes are small: a control sum that no longer matches after someone edited the file, a typo in an IBAN’s check digits, three decimals on a two-decimal currency, a requested execution date already in the past, or a name with characters the SEPA scheme doesn’t allow.

How ISO 20022 Navigator helps

Drop the file into the Payment File Viewer first. It recomputes NbOfTxs and CtrlSum for the group header and every payment block and compares them with the declared values, checks every IBAN’s mod-97 check digits and every BIC’s format, currency decimals, duplicate EndToEndId and PmtInfId, and applies the SEPA rules when the service level is SEPA. Each finding names its line, its path and the value it expected. pain.008 direct debit files get the same checks and, under SEPA, the creditor identifier and mandate data too.

Key conceptsNbOfTxs and CtrlSumIBAN mod-97 check digitsSEPA character set and service levelRequested execution datepain.008 mandates and creditor id

No. 03

Payment support

Payment support: read pain.002 rejections in plain words

The problem

When the bank refuses a payment, the answer comes back as a pain.002 status report: a status such as RJCT or PART and a reason code such as AC01, AM04 or MS03, given for the whole file, a payment block or a single transaction. Working out which of 2,000 payments failed, and why, means reading the XML and looking each code up in a separate document.

How ISO 20022 Navigator helps

Open the pain.002 in the Payment File Viewer. It shows the original message the report refers to, the group, block and transaction statuses, and every reason code with its meaning, so you can see at once which payments to correct and send again. Rejections that carry no reason, and statuses that contradict each other, are flagged.

Key conceptsStatuses RJCT, PART, ACSC Reason codes AC01, AM04, MS03Original message and end-to-end ids

No. 04

Treasury systems

Treasury systems: migrate statement imports from MT940 to camt.053

The problem

SWIFT ended the coexistence of MT and ISO 20022 for cross-border payment instructions in November 2025, and more banks now offer, or ask for, camt.053 statements in place of MT940. Teams with years of MT940 parsing in their ERP or TMS need to see how each :61: line and its :86: details map to a camt.053 entry before they switch, and to test the new import against a file they trust.

How ISO 20022 Navigator helps

Open an MT940 in the MT940 Viewer to see every :61: statement line decoded, the structured :86: subfields read and the balances rolled forward. Then convert it to camt.053.001.08: one statement per MT940 statement, one entry per :61: line, balances mapped to OPBD, CLBD, CLAV and FWAV, and notes on what was mapped and what can’t be. Open the result in the camt Statement Viewer and compare it with the bank’s own camt.053 for the same day.

Key concepts:61: statement lines:86: structured detailscamt.053.001.08Proprietary transaction codes

No. 05

Implementation teams

Implementation teams: onboard a new bank’s statement format

The problem

Every bank fills camt.053 in its own way: which version it sends (.001.02 or .001.08), whether batch bookings carry their transaction details, where the counterparty and remittance text sit, and which bank transaction codes it uses. Writing the import mapping from the bank’s implementation guide alone is slow, and the test files often arrive weeks before anyone has time to read them.

How ISO 20022 Navigator helps

Open the bank’s test files in the viewer. The structure tree and the raw XML with line numbers show exactly what the bank sends, the entry view names every tag and explains every code, and the validation list shows where the file departs from the rules your import will rely on. Export JSON to hand the structure to whoever writes the mapping. The ISO 20022 reference covers the message types, versions and codes.

Key conceptsMessage versions .001.02 to .001.13 Domain, family and sub-family codesStructure tree and raw XMLJSON export

No. 06

AI agents & developers

AI agents & developers: validate payment files through MCP and the API

The problem

An agent or script that prepares payment runs, reconciles statements or answers “why was this payment rejected?” needs exact answers, not a language model’s guess at a control sum or an IBAN check digit. Writing and maintaining an ISO 20022 parser for one workflow is more work than the workflow itself.

How ISO 20022 Navigator helps

The parsers and checks behind the viewers are also a keyless REST API and an MCP server. Detect a message type, parse camt, pain and MT940 files into JSON, validate a file and get every finding with a stable rule id and line number, convert MT940 to camt.053, and explain any code. No account or key is needed; the file is processed in memory and never stored or logged. The API and MCP documentation lists the endpoints, the tools and the limits.

Key conceptsMCP tools REST endpoints and OpenAPIStable rule idsExact decimal amounts

Privacy by design: your file never leaves your device

The camt, pain and MT940 viewers parse your file entirely in your browser with client-side JavaScript. Nothing is uploaded, stored or transmitted. That makes it safe to open production statements and payment files with real IBANs, names and amounts, even under strict bank and corporate data-handling policies.

You can check it: the viewers’ security policy only lets them talk to this site, and your browser’s developer tools (Network tab) show that opening a file sends nothing. The REST API and MCP server are different by design: there the file travels in the request, is processed in memory and is never stored or logged. Read the privacy page.

Try it with your own file

Open a camt.053 statement or a pain.001 payment file, or start from a built-in sample, and see every balance, entry and payment with its checks in seconds. Still on MT940? The MT940 Viewer converts it to camt.053.

Open a camt.053 statement Check a pain.001 file

The tools

Three free viewers, one API.

Each viewer runs privately in your browser. The same checks are open to scripts and AI agents through the REST API and MCP server.

camt.053 · camt.052 · camt.054
camt Statement Viewer
Bank statements and intraday reports per account: balances with their codes explained, every entry and its references, and the roll-forward checked.
.xml · .camt · .053
Read the ISO 20022 reference
Open the Statement Viewer
pain.001 · pain.008 · pain.002
Payment File Viewer
Credit transfer and direct debit files checked before they go to the bank: control totals, IBANs, BICs, decimals and SEPA rules. Status reports with every reason code explained.
.xml
Open the Payment File Viewer
Converter
SWIFT MT940 · MT942
MT940 Viewer
Every :61: statement line decoded, structured :86: details read, balances rolled forward — and the whole file converted to camt.053.001.08.
.sta · .940 · .mt940 · .txt
Or call it from the API and MCP server
Open the MT940 Viewer

FAQ

Frequently Asked Questions

Something else? Email us, read the ISO 20022 reference or the API and MCP docs.

What is ISO 20022?

ISO 20022 is the international standard for financial messages. It defines XML messages by business area: camt for cash management, such as bank statements and reports (camt.052, camt.053, camt.054); pain for payment initiation between a company and its bank (pain.001 credit transfers, pain.008 direct debits, pain.002 status reports); and pacs for payments between banks. Fedwire moved to ISO 20022 in July 2025, and SWIFT ended the coexistence of MT and ISO 20022 for cross-border payment instructions in November 2025.

What is the difference between camt.053, camt.052 and camt.054?

camt.053 is the end-of-day bank statement: the opening and closing balances and every booked entry for an account and period. camt.052 is the intraday account report, sent during the day with booked and pending entries. camt.054 is a debit or credit notification for single entries or batches, often used to give the detail behind a batch booking. The camt Statement Viewer opens all three.

How do I check a pain.001 file before sending it to the bank?

Open it in the Payment File Viewer. It recomputes the number of transactions (NbOfTxs) and the control sum (CtrlSum) for the group header and each payment block, checks IBAN check digits, BIC formats, currency decimals, duplicate references and requested execution dates, and applies the SEPA rules when the file uses the SEPA service level. Each finding gives the line, the path and the expected value. Banks can apply rules of their own, so a clean result is a strong check, not a promise of acceptance.

Can I convert MT940 to camt.053?

Yes. The MT940 Viewer converts MT940 statements to camt.053.001.08 in your browser: one statement per MT940 statement, one entry per :61: line, balances mapped to OPBD, CLBD, CLAV and FWAV, and structured :86: details mapped to counterparty, references and remittance. Transaction type codes are kept as proprietary codes rather than guessed, and notes describe the mapping for your file. MT942 interim reports are not converted, because they correspond to camt.052. The same conversion is available through the API and the MCP server.

Are my files uploaded anywhere?

Not by the viewers. They parse your file entirely in your browser with JavaScript: it is never uploaded, stored or sent over the network, and the pages’ security policy only allows connections back to this site. The REST API and the MCP server work differently by design: the file text travels in the request, is processed in memory and is never stored or logged. Use the viewers for files that must not leave your device.

Does ISO 20022 Navigator cost anything?

No. The camt, pain and MT940 viewers, the MT940 to camt.053 converter, the REST API and the MCP server for AI agents are free, with no account and no API key. If they save you time, donations are welcome but never required.