From MT940 to camt: more than a different filename.
Retrieve statements through your existing bank connections and make structured transaction data usable in your business software.
Read the German originalCheck what your bank actually supports
Deutsche Kreditwirtschaft has no longer listed MT940 and MT942 as DK standards since 23 November 2025. This does not mean every bank switched off these files on the same day. Other announced retirement dates for payment formats have also been postponed. Your specific bank connection is therefore the starting point for any migration.
Request current example files and the supported order types. Then check which format version your business software actually processes. A general ISO 20022 checkbox does not answer that question.
Preserve the information
A transaction may contain references, parties and details of individual items within a batch posting. These relationships must not silently disappear during migration. Compare balances and postings as well as the information your existing payment reconciliation relies on.
Use a few representative statements, including a batch posting and a repeated import. The expected business results come from your accounting process. The import must recognise which data has already been transferred.
Validate read-only retrieval first
A manageable pilot retrieves data from one bank and imports it into one target system. It does not change payment authorisation. Retrieval times, backlogs and technical errors are made visible for ongoing operation.
Switch over only after comparison with the existing process. Retain the agreed test results and a fallback for unexpected formats. Additional banks require their own tests of data and responses.
What does this look like in your work?
We can turn the idea into a sensible next step with you.
EBICS & camt: bank data for your systems · Packages