camt.053 reconciliation compares a bank statement with the account holder's ledger, using balances, amounts, dates and references to explain differences. BankAutomation reads the statement files a US bank or credit union receives, so its operations team can reconcile correspondent accounts without hand-mapping XML each morning. Operations starts at $1,200 a month, with the source and item limits shown below.
Which statement formats a US bank actually receives in 2026
A correspondent's move to ISO 20022 changes its delivery, not every account your institution holds. Some global banks send camt.053 while others still send MT940 or MT950. Domestic correspondent statements can remain BAI2, and the Federal Reserve master account still uses FIRD. Inventory the actual file for each account before designing the reconciliation.
| Format | Typical sender | Cadence | What to reconcile against |
|---|---|---|---|
| camt.053 | Correspondent or global bank using ISO 20022 statements | End of day | Due from or nostro GL entries and booked balances |
| MT940 or MT950 | Correspondent still using SWIFT statement reporting | End of day | The same account's GL activity and balances |
| BAI2 | Domestic correspondent bank | As agreed with the sender, including daily statements | Correspondent account GL activity and balances |
| camt.052 or MT942 | Correspondent providing account reports during the day | Intraday | Pending activity and available ledger postings |
| camt.054 | Bank providing debit or credit notifications and batch detail | On notification or batch detail delivery | Underlying postings and the related statement batch |
| FIRD | Federal Reserve | Daily | Due from Federal Reserve GL activity and balances |
The November 2025 CBPR+ end of coexistence covered cross-border payment instructions such as MT103 and MT202. MT940, MT950 and MT942 are deprecated and no longer maintained by SWIFT, but remain supported on FIN after that date. SWIFT said disincentives would follow later, and J.P. Morgan described its MX reporting rollout as planned for later in 2026. A mixed statement inventory is therefore a practical reconciliation requirement.
Fedwire Funds moved to ISO 20022 on July 14, 2025, after rescheduling from March 10, 2025. The Fed's March 2025 notice kept FIRD, the Statement of Account Spreadsheet File (SASF) and Transaction End-of-Minute detail reports on their current formats. A payment message migration does not make the master account statement camt.053.
Use bank reconciliation software for the overall statement to ledger process, correspondent bank reconciliation software for due from and due to accounts, and federal reserve account reconciliation software for the master account. iso 20022 payment automation explains the payment side of the migration. Keep the evidence requirements for each account explicit.
What changes when a correspondent switches from MT940 to camt.053
The account and the GL remain the same. The statement becomes XML with a versioned namespace, balances and entries arranged in a hierarchy, and transaction detail that may sit beneath a batch. Treat the following as a mapping guide to business meaning, then validate the correspondent's actual samples and implementation guide. It is not a promise of identical content across banks.
| MT940 tag | camt.053 element or code | Reconciliation use |
|---|---|---|
| :60F: opening balance | Bal/Tp with OPBD | Opening booked balance for the statement roll-forward |
| :61: statement line | Ntry | Entry amount, credit or debit indicator, booking and value dates |
| :86: information | NtryDtls/TxDtls/RmtInf | Remittance information beneath entry details, when supplied |
| :62F: closing balance | Bal/Tp with CLBD | Closing booked balance to compare with the GL |
| :20: transaction reference | Stmt/Id | Statement identification and tracing, subject to the sender's conventions |
Match entry amounts with their credit or debit indicators and retain both booking date and value date. Use the bank transaction code to distinguish activity types, then use the end to end id, account servicer reference and remittance information where populated. A statement identifier identifies the statement; it should not be substituted for a missing transaction reference.
Versions such as camt.053.001.02 and camt.053.001.08 circulate at the same time. Test the version each correspondent actually sends, including its batch structure and reference population. Preserving XML structure matters because flattening an entry before reading its detail can discard the fields needed to explain a difference. The same account can migrate formats without changing its reconciliation policy.
A worked correspondent account example with two explained breaks
This illustrative USD example is not customer data. A bank holds a due from account at a correspondent. Its camt.053 and its GL begin with the same booked balance. The statement includes an individual receipt, an aggregated receipt and an outgoing payment. The GL has the underlying receipts, but the batch needs supporting detail and the outgoing payment has a different value date.
| Activity | camt.053 statement | Due from GL | Initial result |
|---|---|---|---|
| Opening booked balance | $100,000 OPBD | $100,000 opening balance | Balances agree |
| Individual receipt | $15,000 credit | $15,000 increase | Amount, reference and dates match |
| Aggregated receipt | $15,000 credit in a batch entry | $9,000 and $6,000 increases | Batch detail break pending camt.054 evidence |
| Outgoing payment | $12,000 debit | $12,000 decrease | Amount and reference agree, value dates differ |
| Closing booked balance | $118,000 CLBD | $118,000 closing balance | No closing balance difference |
Input
- Statement USD 100,000 + 15,000 + 15,000 - 12,000 = 118,000.
- GL USD 100,000 + 15,000 + 9,000 + 6,000 - 12,000 = 118,000.
Output
- Matched Opening and closing balances agree, and the individual USD 15,000 receipt matches by amount, reference and dates.
- Batch detail Cash operations owns the USD 15,000 batch while the USD 9,000 and USD 6,000 postings await camt.054 detail linked by message id.
- Value date Payment operations owns the USD 12,000 payment until the date difference is confirmed under the account's approved timing policy.
The batch arithmetic agrees because $9,000 plus $6,000 equals $15,000. That supports a candidate grouping, but it does not prove those postings belong to that statement entry. Where the bank provides the link, camt.054 detail tied by message id supplies the underlying evidence. The owner checks the references before accepting the group.
The value date break also leaves the booked closing balance unchanged. Confirm the payment reference, amount, booking dates and value dates before treating it as timing. Neither exception justifies a balancing journal merely because it remains open. Record the explanation and keep each item owned until the supporting detail or timing evidence is sufficient.
Break types and the team that should own them
Agree ownership before the first production statement arrives. The table suggests operating responsibilities rather than prescribing your institution's approval structure. A controller should be able to distinguish an amount missing from the GL from an amount already posted with a different date or insufficient supporting detail.
| Cause | How it shows in camt.053 | Owner |
|---|---|---|
| Batch detail missing | An Ntry amount has no usable underlying breakdown, with detail expected in camt.054 | Cash operations requests detail and confirms the grouping |
| Value date difference | Amount and reference agree but value dates differ from the GL | Payment operations confirms timing under approved policy |
| Unposted statement activity | A booked entry has no corresponding GL posting | Accounting investigates the missing posting |
| Unaccrued charge | A charge or debit has no expected GL expense or accrual | Accounting checks the charge and posting treatment |
| Reference difference | End to end id, servicer reference or remittance differs or is absent | Cash operations checks original evidence and normalization |
| Version or mapping change | The namespace or delivered structure differs from the approved source mapping | Source integration owner validates the file with operations |
How BankAutomation handles mixed statement reconciliation
BankAutomation reads camt.053, camt.054, camt.052, MT940, MT942, MT950, BAI2, Nacha ACH files, card network settlement and FIRD alongside core GL exports. Source mappings are versioned configuration. Your team approves the account mapping and matching policy once, rather than manually translating XML into a spreadsheet for each daily run.
Step 01
Inventory statements and ledger exports
Identify each correspondent account, its delivered format and camt version, the matching GL, and who supplies batch detail. Keep the Federal Reserve FIRD source in the inventory.
Step 02
Validate the source mapping
Check booked balances, entry signs, booking dates, value dates and references against the original statement. Preserve transaction detail beneath batch entries and retain the original references.
Step 03
Approve matching rules
Start with amount, reference and the relevant date. Define account-specific timing tolerances and grouping rules. Platform includes maker-checker approvals for controlled changes.
Step 04
Match and assign the residue
Run exact matching before approved tolerances. Classify remaining differences, assign an owner and retain the source evidence and rule version with the work.
Step 05
Compare results before switching formats
Run the new statement against the existing reconciliation. Confirm the balance roll-forward, grouped entries and unresolved items, then adopt the approved mapping for daily use.
For foreign correspondent accounts, nostro reconciliation covers the account-level process. A format change should not silently widen tolerances or close an unexplained difference. Intraday camt.052 and MT942 reporting can inform pending matching, while camt.053 provides the end of day booked statement. Use camt.054 for notifications or supporting batch detail according to the sender's delivery.
Options for reconciling camt.053 compared
Choose against the work your team must finish. A parser may be sufficient when a controlled internal process already handles matching and investigation. A wider platform becomes useful when different accounts, formats and owners must share a daily exception workflow. Ask each supplier to demonstrate your own statement version and batch case.
| Option | Fit | Effort | Cost model |
|---|---|---|---|
| Build an in-house parser | An engineering team that owns ingestion and already has reconciliation controls | Build and maintain version handling, mappings, tests, matching and exception workflow | Internal development and ongoing support time |
| Core or ERP statement import | The existing import reads the delivered version and supports the required matching | Validate batch detail, references, dates and investigation workflow before extending it | Existing license terms and any import or implementation charges |
| FIS Data Integrity Manager, SmartStream or Gresham | Institutions evaluating enterprise reconciliation scope across multiple operations | Confirm product coverage, configuration, implementation and support in the proposal | Vendor quote for the proposed scope |
| BankAutomation | Daily mixed statement to GL matching with owned exceptions | Configure source mappings and approved matching rules from statement and GL files | Published plans from $1,200 a month |
Keep an existing import if it preserves the evidence and produces a controlled reconciliation. For a new purchase, test a balanced statement with unresolved item detail, a value date difference and an account still on MT940. Those cases reveal more about fit than a demonstration in which every entry already matches.
Pricing for daily statement to GL reconciliation
Size the plan around monthly matched items and source connections, including the GL side. Operations supports a focused process line; Platform adds capacity and approval controls. Count the files and connections your intended scope needs before choosing, and use the pricing page for current terms and the Enterprise offering.
$1,200
250,000
$3,900
2,000,000
| Plan | Monthly price | Scope |
|---|---|---|
| Operations | $1,200 | 250,000 matched items a month and 3 source connections |
| Platform | $3,900 | 2,000,000 matched items a month, unlimited sources, SSO and maker-checker |
| Institution | $9,500 | Multi-entity scope, with current inclusions on the pricing page |
| Enterprise | See pricing | Confirm current deployment scope and pricing |
The console on this page uses sample USD card settlement data to show matching and exception handling. It is not a camt.053 XML preview. For a statement evaluation, use the correspondent's delivered version and the matching GL export, including a batch needing detail, so the trial answers the question your operations team actually faces.
Questions about camt.053 reconciliation software
What is camt.053 reconciliation?
camt.053 reconciliation matches an ISO 20022 end of day bank statement to the account holder's ledger. It compares opening and closing booked balances, entry amounts, dates and references. At a US bank or credit union, it proves correspondent or nostro accounts and assigns unresolved differences for investigation.
Is MT940 being replaced by camt.053?
Yes, banks are moving statement reporting toward camt.053, but MT940 did not stop in November 2025. That CBPR+ deadline covered payment instructions. MT940, MT950 and MT942 are deprecated and no longer maintained, yet remain supported on FIN afterward. Reconciliation must accommodate the format each correspondent actually delivers.
Can reconciliation software read camt.053 and MT940 at the same time?
Yes. BankAutomation reads camt.053 and MT940 alongside MT950, BAI2 and the GL export. Each source has its own mapping, while approved matching rules compare amounts, dates and references. That lets a bank migrate individual correspondent statements without requiring every other account to change format at the same time.
Does the Federal Reserve send camt.053 statements?
The Federal Reserve master account still reconciles from FIRD, not camt.053. Fedwire Funds moved to ISO 20022 on July 14, 2025, but the Fed kept FIRD, SASF and Transaction End-of-Minute detail reports on their current formats. Treat payment message migration and master account statement reporting as separate requirements.
How much does camt.053 reconciliation software cost?
BankAutomation starts at $1,200 a month for Operations, including 250,000 matched items and 3 source connections. Platform costs $3,900 with 2,000,000 items, unlimited sources, SSO and maker-checker. Institution is $9,500. Choose by the sources, volume and approval controls your reconciliation needs, and check pricing for current Enterprise terms.
What is the difference between camt.052, camt.053 and camt.054?
camt.052 is the intraday account report, camt.053 is the end of day statement, and camt.054 is a debit or credit notification. Notifications can supply batch booking detail. Where the sender provides the relationship, a camt.053 batch entry can be linked to its camt.054 detail by message id for reconciliation.