End of provision in SWIFT format

The future transaction formats are basically XML files, based on the ISO 20022 standard and defined in detail as follows:

• Advises (intraday transactions): camt.052.001.08
• Statements: camt.053.001.08
• Batched transaction files: camt.054.001.08

The formats of the old camt version 02 — i.e. camt.052.001.02, camt.053.001.02 and camt.054.001.02 — will also be replaced by the new formats in version 08 in November 2025.

Incidentally, the transaction data is not provided by the banks directly as a camt file, but as a ZIP file with one or more XML files contained therein.

Even though some credit institutions have already announced that they will continue to offer electronic transaction information in the older formats after November 2025, the change should already be prepared.

The prerequisites for a successful changeover lie with both the banks and the companies.

Bank-side authorizations available

The electronic transaction information is retrieved via new order types when using EBICS version 2.5 or via new BTF parameters for EBICS version 3.0.

If MT940 account statements are retrieved via order type STA, for example, this is done via order type C53 for account statements in camt.053 format.

This means that all EBICS subscribers with authorization to retrieve the old formats will initially also need the authorization to retrieve in the camt format.

Availability of transaction information

In addition to the authorizations for retrieval, the bank must ensure that the transactions for all accounts are actually provided for the new formats.

The date for the complete provision is usually clearly stated in the letter from the respective bank. If in doubt, it is advisable to contact the bank in this regard.

Processing in all software systems

Last but not least, all programs involved in the retrieval and processing must be able to handle the new formats without errors.

In this context, it is often problematic that the changeover is not seamless and some SWIFT statements are provided again in the first files of the new formats.

If these can still be corrected for a few accounts by one-time manual corrections, it can lead to massive problems, especially in companies with a high degree of automation and many accounts.

For this reason, the software used in the company should have an integrated function for detecting and merging these statements. The detection is then based on the statement numbers, so that statements that have already been received via SWIFT files are ignored in the camt files.

Users of BL Banking products from the software manufacturer Business-Logics can carry out the changeover themselves at any time as soon as the bank-side requirements have been met and any third-party software involved is also ready.

With BL Banking and BL Banking Web, it is only necessary to set the selection for the format to camt in the account statement settings of the respective bank.

The correct individual format is already preset as a value, e.g. “camt.053” for account statements or “camt.052” for advices. It is not necessary to specify the specific version of the new format — e.g. camt.053.001.08 — as the programs automatically support the latest version and recognize it automatically.

The problem of detecting duplicate statements is also automatically taken into account by the BL Banking programs in the new version.

If statements are missing from the customer side, users can easily fetch them from the bank in camt format by a manual from-to retrieval, thanks to the duplicate detection system.

The update to the new BL Banking versions is available to all customers free of charge as part of software maintenance.