Is CAMT.053 the only file Aeglio can import?

No. Aeglio supports compatible CAMT.052, CAMT.053 and CAMT.054 reports.

Does the final number identify the message type?

No. In camt.053.001.08, 053 is the message family and 08 is the version.

Should I manually select the bank account?

Not when the file identifies exactly one account and its IBAN can be detected. Selection is only needed when the source is genuinely ambiguous.

All guides

Bank reporting

CAMT.052 vs CAMT.053 vs CAMT.054

All three are ISO 20022 bank-to-customer cash-management messages, but they answer different questions. The number identifies the message purpose, while the later digits identify its version.

6 minute readPractical Aeglio guide

The short answer

Use CAMT.052 for account reporting at a point in time, CAMT.053 for booked statement entries and balances, and CAMT.054 for debit or credit notifications. For routine historical reconciliation, CAMT.053 is usually the most statement-like source, but the file your bank provides and the data it contains matter more than the filename alone.

What each CAMT message represents

The ISO 20022 catalogue names camt.052 BankToCustomerAccountReport, camt.053 BankToCustomerStatement and camt.054 BankToCustomerDebitCreditNotification. Banks can support different versions and usage profiles, so a complete identifier may look like camt.053.001.08 or camt.053.001.14.

CAMT.052: entries and/or balances reported for an account at a given point in time.
CAMT.053: entries booked to an account together with statement balance information.
CAMT.054: single or multiple debit and/or credit entries reported as notifications.

Choose the message by workflow, not by the newest version

A newer schema version does not turn one message type into another. CAMT.052 remains an account report and CAMT.053 remains a statement. Your bank or integration determines which schema versions are available.

For month-end or daily reconciliation of booked activity, a CAMT.053 statement is the clearest fit. CAMT.052 can support more current reporting. CAMT.054 is useful when the workflow is driven by transaction notifications.

Check the account and statement period before import

A safe import should identify the account IBAN from the XML, show the detected message type, date range, transaction count and balances, and warn about duplicates before committing anything.

If one file contains reports for more than one account, the system needs an explicit way to separate them. A file picker should not ask for an account when the XML already identifies one unambiguously.

How Aeglio imports CAMT reports

Aeglio accepts supported CAMT.052, CAMT.053 and CAMT.054 files as a manual entry point alongside LHV Connect. Import preflight detects the account, summarizes the file and lets the user confirm before transactions become part of the generic banking workspace.

The imported transactions use the same matching and review process regardless of their source. Re-import protection prevents the same statement or transaction from being silently duplicated.

Official reference: ISO 20022 Bank-to-Customer Cash Management message definitions at iso20022.org.

Sources

ISO 20022 Bank-to-Customer Cash Management message definitions

Aeglio bank reconciliation workspace with imported transactions and fictional company data — CAMT file imports and connected-bank transactions enter the same reconciliation workspace. The company and figures shown are fictional.

Frequently asked questions

Is CAMT.053 the only file Aeglio can import?: No. Aeglio supports compatible CAMT.052, CAMT.053 and CAMT.054 reports.
Does the final number identify the message type?: No. In camt.053.001.08, 053 is the message family and 08 is the version.
Should I manually select the bank account?: Not when the file identifies exactly one account and its IBAN can be detected. Selection is only needed when the source is genuinely ambiguous.