Integration of the SEPA data set into MT940-MT942 How are SEPA Credit Transfers and SEPA Direct Debits reported in Swift MT940-942 messages for KBC Belgium/CBC accounts? ICM Electronic Output March 2010 Summary As of 24 May 2010, KBC BE/CBC will apply the guidelines advised by SWIFT and change how SEPA Credit Transfers and SEPA Direct Debits in Swift MT940/942 messages are reported for your KBC BE/CBC accounts. What will change? The reporting of SEPA Credit Transfers and SEPA Direct Debits will change in SWIFT MT940/942 messages. Please consult the schemes below. What will not change? The reporting for other types of transaction remains the same. The CODA format will not be affected by these changes either. What are the consequences of these changes for your reconciliation and treasury software? For the interpretation of field 86 for SEPA Credit Transfers and SEPA Direct Debits, we recommend that your reconciliation tools work with the key words across the six lines of this field from now on. Questions? Additional information? If you have any additional questions about these changes, please contact: Businesses: kbc.helpdesk.bedrijven@kbc.be Corporate Banking: EBC.Desk@kbc.be KBC Global Services International Cash Management 1/5 March 2010
How will the reporting of SEPA Credit Transfers change in MT940/942? The changes concern field 61 (subfield 7) and field 86. SWIFT recommends working with key words that clarify the type of information. Field 61, subfield 7 Field 86 From now on, the KREF label will be recorded in this field as a reference to the transaction identification (identification entered by the instructing party), while the identification itself will be recorded in field 86. Field 86 still contains 6 x 65 positions. The table below displays the presentation of the reporting of a SEPA Credit Transfer: KBC Global Services International Cash Management 2/5 March 2010
Line Text/Variable Start Length SCT Credit 1/KREF/ 1 6 /KREF/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/ORDP//ID/BBBBBBBBBBBBBB 1 PaymentInformation ID, i.e. global reference entered by the ordering party, or 7 35 End2End ID, i.e. transaction identification entered by the ordering party 1 Ordering party's identification 52 14 2 Ordering party's identification (continued) 1 21 BBBBBBBBBBBBBBBBBBBBB/NAME/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX 2 Ordering party's name 28 38 3 Ordering party's name (continued) 1 32 XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/ACC/XXXXXXXXXXXXXXXXXXXXXXXXXXXX 3 /ACC/ 33 5 3 Ordering party's account number 38 28 4 Ordering party's account number (continued) 1 6 XXXXXX/REMI/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX 6 /PURP/ 24 6 SCT Debit 1/KREF/ 1 6 /KREF/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/ORDP//ID/BBBBBBBBBBBBBB 1 PaymentInformation ID, i.e. global reference entered by the ordering party, or 7 35 End2End ID, i.e. transaction identification entered by the ordering party 1 Ordering party's identification 52 14 2 Ordering party's identification (continued) 1 21 BBBBBBBBBBBBBBBBBBBBB/NAME/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX 2 Beneficiary s name 28 38 3 Beneficiary s name (continued) 1 32 XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/ACC/XXXXXXXXXXXXXXXXXXXXXXXXXXXX 3 /ACC/ 33 5 3 Beneficiary s account number 38 28 4 Beneficiary s account number (continued) 1 6 XXXXXX/REMI/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX 6 /PURP/ 24 6 KBC Global Services International Cash Management 3/5 March 2010
How will the reporting of SEPA Direct Debits change in MT940/942? The changes concern field 61 (subfield 7) and field 86. SWIFT recommends working with key words that clarify the type of information. Field 61, subfield 7 Field 86 From now on, the MARF label will be recorded in this field as a reference to the unique mandate reference, while the mandate reference itself will be recorded in field 86. Field 86 still contains 6 x 65 positions. The table below displays the presentation of the reporting of a SEPA Direct Debit: KBC Global Services International Cash Management 4/5 March 2010
Line Text/Variable Start Length SDD Credit 1/MARF/ 1 6/MARF/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/ORDP//ID/BBBBBBBBBBBBBB 1 Mandate identification 7 35 1 End2End ID, i.e. transaction identification entered by the 52 14 ordering party 2 Transaction identification (continued) 1 21 BBBBBBBBBBBBBBBBBBBBB/NAME/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX 2 Counterparty s name 28 38 3 Counterparty s name (continued) 1 32 XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/ACC/XXXXXXXXXXXXXXXXXXXXXXXXXXXX 3/ACC/ 33 5 3 Counterparty s account number 38 28 4 Counterparty s account number (continued) 1 6 XXXXXX/REMI/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX 6/PURP/ 24 6 SDD Debit 1/MARF/ 1 6/MARF/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/ORDP//ID/BBBBBBBBBBBBBB 1 Mandate identification 7 35 1 Creditor Scheme ID, i.e. creditor number 52 14 2 Creditor Scheme ID, alias creditor number (continued) 1 21 BBBBBBBBBBBBBBBBBBBBB/NAME/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX 2 Counterparty s name 28 38 3 Counterparty s name (continued) 1 32 XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/ACC/XXXXXXXXXXXXXXXXXXXXXXXXXXXX 3/ACC/ 33 5 3 Counterparty s account number 38 28 4 Counterparty s account number (continued) 1 6 XXXXXX/REMI/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX 6/PURP/ 24 6 KBC Global Services International Cash Management 5/5 March 2010