MT940-CAMT-MAPPING

MT940 + camt mapping legacy SWIFT MT to ISO 20022 camt.053 migration.

Définition

MT940 to camt.053 mapping key elements : (1) MT940 structure : Tag 20 (Transaction Reference), Tag 21 (Related Reference), Tag 25 (Account Identification), Tag 28C (Statement Number/Sequence), Tag 60 (Opening Balance F/M), Tag 61 (Statement Line, repeatable for each transaction), Tag 86 (Information to Account Owner, narrative supplementary), Tag 62 (Closing Balance F/M), Tag 64 (Closing Available Balance), Tag 65 (Forward Available Balance). (2) camt.053 structure : XML-based, root BankToCustomerStatement, GroupHeader, Statement (account info), Balance (multiple types : OPBD Opening Booked + CLBD Closing Booked + CLAV Closing Available + FWAV Forward Available etc.), Entry (per transaction, equivalent MT940 Tag 61), EntryDetails (richer transaction details vs MT940 Tag 86 narrative). (3) Mapping challenges : (a) Free-form Tag 86 narrative to structured camt.053 EntryDetails RemittanceInformation StructuredCdtrPmtInf + UnstructuredCdtrPmtInf, (b) Tag 61 :CustomerBicCode vs Tag 86 :AdditionalEntryInformation richer in camt.053, (c) MT940 + MT942 (Interim Statement) -> camt.053 + camt.052 (Bank-to-Customer Account Report), (d) Balance Types : MT940 F (Final) vs M (Intermediate) vs camt.053 OPBD + OPAV + CLBD + CLAV + FWAV + ITBD etc richer (~15+ types). (4) ERP integration : SAP S/4HANA Cash Management camt.053 support 2020+ (native + via Bank Communication Management BCM module), Oracle Cash Management, Kyriba, FIS Treasury, multiple TMS modernization 2023-2025. (5) Coexistence period : MT940 + camt.053 coexist 2023-2025 typically (banks generate both formats during transition), ultimate cutover MT940 to camt.053 individual bank scheduled per migration plan but ECB CBPR+ deadline novembre 2025 forces correspondent banking MT migration.

Origine

SWIFT MT940 published 1980s by SWIFT ; ISO 20022 camt.053 published 2004+ ; CBPR+ migration deadline novembre 2025 SWIFT MT-MX coexistence.

Exemple en contexte

Multinational treasurer receives daily MT940 + camt.053 from primary bank during transition : SAP Treasury Management imports camt.053 (preferred richer data, structured remittance), fallback MT940 if camt.053 not available ; SAP BCM module bidirectional mapping rules transform Tag 61 + Tag 86 to camt.053 EntryDetails structures during phased ERP modernization.

Termes liés

• BAI2 format — US alternative.