Swiss ISO Harmonization for Software Vendors Credit Suisse Best Practice Guide

Transcription

1 Public Swiss ISO Harmonization for Software Vendors Credit Suisse Best Practice Guide CREDIT SUISSE (Switzerland) Ltd., Software Partner Management October 2017

2 Introduction Top 7 General Swiss Payment Standards ISO Issues There s no way around ISO but don t feel forced to use intermediate formats Migrate your clients early Master data is as important as formats, it must be up to date and structured Advice steering is more than nice to have Keep to the standard ISO is a new complex standard to all market participants, interpretation mismatches can cause problems The QR-bill will replace ISR/IS due to money laundering regulations. Only native ISO can transfer the required data easily, restraining DTA to pain.001 converters. Also, QR-bill debit notes will only be available in ISO All other payment types are also being switched to ISO V11 and LSV have intermediate ISO formats which can be avoided with many financial institutions. See page 8 for details. Client support for pain.001 will peak in 2Q Flatten that peak by switching Credit Suisse clients to pain.001 earlier. Contact softwarepartner.team@credit-suisse.com to discuss your options. Financial institutions will increase matching of creditor master data. This data will increasingly be transmitted in a structured form. Therefore your software must be able to provide this data in a structured way. See page 29 for details. ISO provides electronic and paper advice steering per payment order. Offer this option to your clients, particularly to avoid wrong reporting for salary payments. Implement all 5 combinations with Swiss Business Rules terminology. See pages for details. Don t use AOS as standard for all financial institutions. See next page for major format traps. Test with all financial institutions important to you. See pages for Credit Suisse details. October /69

3 Introduction Top 4 Format Traps Issue Reference Comment Don t allow several currencies per B-Level Swiss Business Rules Version Chapter Credit Suisse and other banks will not provide this AOS to avoid reconciliation problems in your software. See page 37 for details SALA is not sufficient for salary payments, implement advice steering Swiss Business Rules Version Chapter 4.11 and 4.7 SALA has no effect on the type of processing and advices. Advice steering has to be implemented instead. See pages for details. Don t allow Payment Type Information on several levels Swiss Business Rules Version Chapter Instruction Priority (HIGH), Service Level (SEPA), Local Instrument (e.g. CH01) and Category Purpose (SALA) have to be in the same level (B or C). See page 36 for details. CH03 is not payment type 3 Swiss Implementation Guidelines for pain.001 Version Chapter Local Instruments CH01, CH02 and CH03 mark Swiss inpayment slips. CH03 is for payment type 2.2, not 3. See pages 27 and 30 for details. October /69

4 Agenda Framework Page 5 Formats Page 11 Use Cases Page 22 Test Procedure Page 53 October /69

5 Agenda Framework Page 5 Formats Page 11 Use Cases Page 22 Test Procedure Page 53 October /69

6 Migration User System Channel Transmission Technology Characteristics Technology Framework: Credit Suisse Client Channel Functionality Overview of Connectivity Portfolio Legend: Advantage Restriction Neutral attribute Direct Business and Direct Net Direct Link Direct Exchange SWIFT FileAct GUI (browser-based) DXI (Service Interface) File transfer method HTTPS HTTPS Intersys EBICS SFTP or FTPS FileAct Installation reusability N/a CS clients Yes Yes No, individual configuration Yes Manual/automated login & file transfer Manual Login manual, upload/ download automated Automated Content offering No pain.002, reduced camt No pain.002, no CGI, no EPC, reduced camt No CGI, no camt Full range Additional security SecureSign SecureSign No Electronic Distributed No Signature (EDS/VEU) No Clients Corporate and (Direct private Business and Direct Net) Private (Direct Net) Corporate Operating systems Any Any Microsoft Windows Any Any Any Software Internet web browser Dedicated third-party software vendors Dedicated third-party software vendors Dedicated third-party software vendors Any third-party software vendor Dedicated third-party software vendor ISO impact on connectivity Platform update at Credit Suisse New platform at Credit Suisse Migration impact on client connectivity None Silent migration. Additional log-in method. Silent migration Attended migration, changing credentials Attended migration, changing credentials Migrated October /69

7 Framework: Credit Suisse Client Channel Formats Overview of Format Portfolio per Channel Legend: Available now Restriction Available in the future ISO Test Platform Direct Business and Direct Net Direct Link Direct Exchange SWIFT FileAct GUI DXI Intersys EBICS SFTP pain.001 SIC Yes Yes Yes 1 Yes 1 Yes 1 Yes 1 EPC No Yes No No Yes 1 Yes 1 Yes 1 CGI Yes Yes No No Yes 1 Yes 1 Yes 1 pain.008 SIC EPC Yes Yes No No Yes No Yes Yes Yes Yes Yes Yes pain.002 SIC EPC Yes Yes No No Yes No Yes Yes Yes Yes Yes Yes CGI Yes No No Yes Yes Yes camt.052 SIC CGI Yes No No No No 1Q 2018 No 1Q Q Q Q Q 2018 camt.053 SIC CGI Yes No 1Q 2018 No No 1Q 2018 No 1Q Q Q Q Q 2018 Credit/Debit SIC CGI Yes No No No No 2Q 2018 No 2Q Q Q Q Q 2018 ISR SIC CGI Yes No 1Q 2018 No No 1Q 2018 No 1Q Q Q Q Q Possible data reduction due to data conversion until Oct 2017 October /69

8 Framework: Credit Suisse Client Format Strategy Overview of ISO Format Portfolio Legend: Phase-out format Target format Obsolete format** Message Type Old Format Intermediate Format New Format Target DTA pain.001 Credit Transfer MT101 Direct Debit LSV pain.008 CH-TA* Unknown yet, stay currently with LSV MT940/MT942 camt.053/camt.052 Reporting ISR V11 ISR Stay with V11 until ISR is discontinued QR-IBAN Credit/Debit * not offered by Credit Suisse ** other financial institutions may require these intermediate formats October /69

9 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec 1Q 2Q 3Q 4Q 1Q 2Q 3Q 4Q 1Q 2Q 3Q 4Q Framework: Migration Timetable (1/2) Credit Suisse Formats and Connectivity Credit Transfer pain.001 SIC pain.001 EPC/CGI pain.002 SIC/EPC/CGI * * * Direct Link / Direct Exchange Direct Business / Direct Net Direct Link / Direct Exchange** Direct Business** / Direct Net (only GUI, not DXI) Direct Link / Direct Exchange DTA & DTA Protocol Direct Link / Direct Exchange Direct Business / Direct Net Direct Debit pain.008 & pain.002 SDD SIC/EPC Direct Link / Direct Exchange pain.008 LS Direct Link / Direct Exchange Direct Business / Direct Net pain.002 LS Direct Link / Direct Exchange LSV/LSV Protocol Direct Link / Direct Exchange Direct Business / Direct Net Format discontinued by Swiss financial marketplace * Format expected to be discontinued by Swiss financial marketplace ** Possible data reduction due to data conversion Contact the Electronic Banking Desk New formats Old formats October /69

10 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec 1Q 2Q 3Q 4Q 1Q 2Q 3Q 4Q 1Q 2Q 3Q 4Q Framework: Migration Timetable (2/2) Credit Suisse Formats and Connectivity Reports camt.052 SIC camt.052 CGI MT942 Direct Link / Direct Exchange Direct Link / Direct Exchange Direct Link / Direct Exchange camt.053 SIC camt.053 CGI MT940 Direct Link / Direct Exchange Direct Business / Direct Net Direct Link / Direct Exchange Direct Business / Direct Net Direct Link / Direct Exchange Debit/Credit SIC Debit/Credit CGI ISR SIC ISR CGI QR Code SIC/CGI V11 Direct Link / Direct Exchange Direct Business / Direct Net Direct Link / Direct Exchange Direct Link / Direct Exchange Direct Link / Direct Exchange Direct Business / Direct Net Direct Link / Direct Exchange Direct Link / Direct Exchange Direct Business / Direct Net October /69

11 Agenda Framework Page 5 Formats Page 11 Use Cases Page 22 Test Procedure Page 53 October /69

12 Formats: Credit Transfer pain.001 Credit Transfer Initiation pain.001 pain.008 pain.002 camt.053 camt.052 CS ISO offering CS ISO offering recommendation CS ISO offering alternative CS Non-ISO alternative Please consider this CS legacy offering Version pain (SIC: pain ch.02) Flavors Channels Best Practice Name Market Scheme Payments SIC Switzerland SIX** All (domestic e.g. ESR & x-border e.g. SEPA) EPC Euro Currency 7.0 EPC SEPA CGI (CH) World with Swiss specialties (e.g. ISR) All (domestic e.g. ESR & x-border e.g. SEPA) Direct Link EBICS Direct Link Intersys only SIC Direct Exchange Direct Business GUI DXI only SIC SWIFT FileAct Use flavor SIC as it covers all Swiss payments and all CS channels Alternative practice Alternative formats Clients can use Swiss CGI if you already use CGI in other countries MT101 for single payments (SWIFT FIN or Fides) Caution camt control can be done in pain.001, details see page (some banks ignore this camt control) SALA flag in pain.001 without effect, details see page 34/35 (some banks still use the SALA flag as an AOS) Master data should be sent in a structured way, details see page 37 Timing DTA * pain.001 Possible data reduction due to data conversion * ** Scheme 1.7.x planned October /69

13 Formats: Direct Debit pain.008 Direct Debit pain.001 pain.008 pain.002 camt.053 camt.052 CS ISO offering CS ISO offering recommendation CS ISO offering alternative CS Non-ISO alternative Please consider this CS legacy offering Version pain (SIC: pain chsdd.02) Flavors Channels Best Practice Name Market Scheme Payments SIC Euro Currency 2.3 SIX SEPA (Core & B2B) EPC Euro Currency 8.0 EPC SEPA (Core & B2B) CHLS Switzerland Upcoming Former LSV+ and BDD Direct Link EBICS Direct Link Intersys only SIC Direct Exchange Direct Business GUI/DXI only CHLS SWIFT FileAct Use SIC or EPC for SEPA Direct Debit (SDD). Wait for pain.008 CHLS for Swiss direct debit. Alternative practice Alternative formats None, pain.008 CH-TA not part of the Credit Suisse offering None, E-Invoice planned to have the same format as Direct Debit Caution No official recommendation on whether to use SIC or EPC for SDD Final future standard pain.008 CHLS yet to be defined in the LEON project Via Direct Net only pain.008 CHLS planned Timing LSV pain.008 SDD pain.008 CHLS October /69

14 Formats: Status Report pain.002 Status Report pain.001 pain.008 pain.002 camt.053 camt.052 CS ISO offering CS ISO offering recommendation CS ISO offering alternative CS Non-ISO alternative Please consider this Version pain (SIC: pain ch.02) Flavors Channels Name Market Scheme Payments SIC Switzerland 1.0 SIX All (domestic e.g. ESR & x-border e.g. SEPA) EPC Euro Currency 7.0 EPC SEPA CGI (CH) World with Swiss specialties All (domestic e.g. ESR & x-border e.g. SEPA) Direct Link EBICS Direct Link Intersys only SIC Direct Exchange Direct Business GUI/DXI SWIFT FileAct Direct Business no file download but status indication in the Direct Business GUI Best Practice Same flavor as the pain.001 or pain.008 triggering the pain.002 Benefit pain.002 for all banks instead of different proprietary protocol formats Caution Not available via Direct Net Partially accepted: only incorrect parts are reported SIC includes positive and negative status reports, EPC only includes negative status reports Positive status reports are only transmission confirmations, not execution confirmation Timing same as the pain.001 or pain.008 triggering the pain.002 October /69

15 Formats: Reporting camt.053 Account Statement (End of Day) pain.001 pain.008 pain.002 camt.053 camt.052 CS ISO offering CS ISO offering recommendation CS ISO offering alternative CS Non-ISO alternative Please consider this CS legacy offering Version Flavors Periodicity Details Channels Best Practice camt (for SIC) and camt (for CGI) Name Market Scheme Report Types SIC Switzerland SIX Account Statement CGI (CH) World Account Statement End of day With details Without details Direct Link EBICS Direct Link Intersys Direct Exchange Direct Business GUI DXI only SIC SWIFT FileAct camt.053 SIC without details is CS default Alternative practice Alternative formats Clients can use Swiss CGI if you already use CGI in other countries MT940 Caution Some banks may use V2 (camt ) for SIC Oversteering of account default booking by using pain.001 tags Timing MT940 Tests camt.053 October /69

16 Formats: Reporting camt.052 Account Report (Intraday) pain.001 pain.008 pain.002 camt.053 camt.052 CS ISO offering CS ISO offering recommendation CS ISO offering alternative CS Non-ISO alternative Please consider this CS legacy offering Version Flavors Periodicity camt (for SIC) and camt (for CGI) Name Market Scheme Report Types SIC Switzerland SIX Account Statement CGI (CH) World Account Statement Intraday fixed, hourly or 2-hourly, from 7 a.m. to 6 p.m. End of day (Balance Report) Details Channels Best Practice Alternative practice Alternative formats Caution Account Report Balance Report Balance Account Report Movement Report, no details Movements Account Report Full Report, with details Balance + Movements Direct Link EBICS Direct Link Intersys Direct Exchange Direct Business GUI/DXI SWIFT FileAct camt.052 SIC Movement Report 2-hourly is CS default Clients can use Swiss CGI if you already use CGI in other countries MT942 Some financial institutes may use V2 (camt ) for SIC Timing MT942 Tests camt.052 October /69

17 Formats: Reporting Debit/Credit Notification pain.001 pain.008 pain.002 camt.053 camt.052 CS ISO offering CS ISO offering recommendation CS ISO offering alternative CS Non-ISO alternative Please consider this CS legacy offering Version Flavors (for SIC) and (for CGI) Name Market Scheme SIC Switzerland SIX CGI (CH) World Report Types Debit/Credit Notification ISR/LSV Credit Notification External Batch Booking Notification (for camt.053) Periodicity Details Channels Best Practice Intraday fixed, hourly or 2-hourly, from 7 a.m. to 6 p.m. Intraday event-based, if booking took place, from 7 a.m. to 6 p.m. End of day (ISR/LSV) According to account default Oversteer account default with pain.001 tags Direct Link EBICS Direct Link Intersys Direct Exchange Direct Business GUI/DXI only ISR SWIFT FileAct Select the report types and details you need for your desired notification/matching functionality. SIC Debit/Credit Notification event-based & SIC ISR/LSV are CS default. Alternative formats Caution Timing E-Documents/MT900 Confirmation of Debit and MT910 Confirmation of Credit in SWIFT for planned new payment slip based on Debit/Credit Notification Debit Notification is controlled by pain.001 tags, see page for details; not supported by all Swiss banks Postfinance uses additional and different report types ZED V11 ISR/LSV Tests October /69

18 Formats: Reporting Manual Upload of ZIPped ISR Files pain.001 pain.008 camt.053 Analogously for camt.053 pain.002 camt.052 Situation 1: One ISR ready for download Direct Business ISR Oct 15, 201x Download 1 file Oct 16, 201x CS client = user Import 1 file Oct 16, 201x Payment Software you! Situation 2: Several ISR ready for download in a ZIP file Problem: if the CS client unzips the file and uploads the camts manually, he might miss a file or upload a file twice. Therefore please make sure to support at least one of the following options: Direct Business ISR Oct 16, 201x Option 1 Download 1 ZIP file Oct 19, 201x Import Oct 19, 201x then the user imports 1 ZIP file Payment Software ISR Oct 17, 201x ISR Oct 18, 201x Option 2 Download 1 ZIP file Option 3 then the user unzips and can mark all files for import Payment Software ZIP File Download 1 ZIP file then the user unzips and has to upload one file after another Payment Software but then the software needs a duplicate and maybe missing file check! October /69

19 Formats: Reporting Advice Steering 1 with pain.001 Tags: All Cases pain.001 pain.008 camt.053 pain.002 camt No ordering of non-subscribed camt.053 and via pain.001 tags. Payment Information +Debtor Account ++Type +++Proprietary NOA SIA CND CWD Empty Payment Information +Batch Booking False Single booking camt.053 with details No Single booking camt.053 with details with details Single booking camt.053 with details with details (SIA) Single booking camt.053 with details with details (SIA) Single booking camt.053 with details with details True/Empty Bold: Recommended settings Out of 15 debit advice combinations, only 5 are recommended Your software should be able to control these, e.g. by one dropdown menu Red: Recommended settings for salary payments to allow confidentiality Salary payments should only allow these settings, e.g. by ticking a checkbox Grey: Not recommended (may be rejected by other banks) Batch booking camt.053 no details No Batch booking camt.053 details as account default with details (CWD) Batch booking camt.053 no details no details Batch booking camt.053 with details with details Batch booking camt.053 details as account default with details Credit Suisse Account Defaults camt in General In order to receive camt.053/ 052/054, Credit Suisse clients have to subscribe to them for each of their accounts. It is not possible to order non-subscribed camts via pain.001. camt.053 Default booking type is always batch booking, and for the subscription, the clients have to choose between with details or no details. Both can be overridden with pain.001 tags for particular instructions. camt.052 Details are the same as for camt.053, unless camt.053 follows account default, then camt.052 is with details. Default is always with details! This can be overridden with CND or NOA. October /69

20 Formats: Reporting Advice Steering 1 with pain.001 Tags: Useful Cases pain.001 pain.008 camt.053 pain.002 camt No ordering of non-subscribed camt.053 and via pain.001 tags. Document pain.001 Document pain.001 Document pain.001 Document pain.001 Document pain.001 B-Level CHF 50 FALSE NOA B-Level CHF 50 FALSE SIA B-Level CHF 50 TRUE NOA B-Level CHF 50 TRUE CND B-Level CHF 50 TRUE CWD C-Level CHF 20 C-Level CHF 20 C-Level CHF 20 C-Level CHF 20 C-Level CHF 20 C-Level CHF 30 C-Level CHF 30 C-Level CHF 30 C-Level CHF 30 C-Level CHF 30 Document camt.053 Document camt.053 Document camt.053 Document camt.053 Document camt.053 B-Level C-Level CHF 20 D-Level Trx Details C-Level CHF 30 D-Level Trx Details B-Level C-Level CHF 20 D-Level Trx Details C-Level CHF 30 D-Level Trx Details B-Level C-Level CHF 50 D-Level B-Level C-Level CHF 50 D-Level B-Level C-Level CHF 50 D-Level Trx Details CHF 20 D-Level Trx Details CHF 30 Document B-Level C-Level CHF 20 D-Level Trx Details Document B-Level C-Level CHF 30 D-Level Trx Details Document B-Level C-Level CHF 50 D-Level Document B-Level C-Level CHF 50 D-Level Trx Details CHF 20 D-Level Trx Details CHF 30 October /69

21 pain.001 pain.008 pain.002 Formats: Reporting pain.001 All Formats Input B-Level: Sum Batch Booking Proprietary C-Level: Amount C-Level: Amount C-Level: Amount pain.001 B-Level: Sum Batch Booking Proprietary C-Level: Amount C-Level: Amount C-Level: Amount pain.001 B-Level: Sum Batch Booking Proprietary C-Level: Amount C-Level: Amount C-Level: Amount pain.001 B-Level: Sum Batch Booking Proprietary C-Level: Amount C-Level: Amount C-Level: Amount pain.001 B-Level: Sum Batch Booking Proprietary C-Level: Amount C-Level: Amount C-Level: Amount camt.053 pain.001 camt.052 B-Level: Sum Batch Booking Proprietary C-Level: Amount C-Level: Amount C-Level: Amount C-Level: Amount C-Level: Amount C-Level: Amount C-Level: Amount C-Level: Amount C-Level: Amount Output Web-based Files Paper/E-Documents (PDF) Direct Business GUI Page «Bookings» MT940 Account Statement camt.053 Account Statement Debit Advice Paper /E-Document Account Statement Paper/E-Document Debit Advice True or Empty CWD Sum Sum Amounts + Details in 1 camt.053 Amounts + Details in 1 Amounts + Details in 1 document Amounts + Details in 1 document CND Sum Sum Sum Sum NOA Sum No advice Account Default No advice Empty As AD*: Sum or A+D** in 1 camt.053 Amounts + Details in 1 Account Default Account Default False SIA Amounts + Details Amounts + Details in 1 MT940 Amounts + Details in 1 camt.053 Amounts + Details in 4 Amounts + Details in 1 document Amounts + Details in 4 documents NOA Amounts + Details in 1 camt.053 No advice Account Default No advice Empty Amounts + Details in 1 camt.053 Amounts + Details in 4 Amounts, Details as AD* in 1 camt.053 Amounts, Details as AD* in 4 documents * Account Default ** Amounts + Details October /69

22 Agenda Framework Page 5 Formats Page 11 Use Cases Page 22 Test Procedure Page 53 October /69

23 Use Cases Remarks Payment slips and their replacement Bank payments Special payments Status reports Advices Statements Direct debit pain.001 pain.001 pain.001 pain.002 camt.053/052 pain.008 ISR (10) IS (11) QR (15) Domestic (12) Salary (20) ACCP (35) SEPA (13) ROW 1 (14) ACWC (37) PART (38) NOA (46) SIA (47) CND (48) Internal (64) External (65) Type 1 Chapter 2.2 ISR (40/41) RJCT (39) CWD (49) DD Core (44) DD B2B (45) SDD Core (42) SDD B2B (43) Payment Type Swiss Usage Guide Type 1 Chapter 2.2 camt.053/mt940 descriptions always include camt.052/mt942 Only bank formats are depicted, not PostFinance formats 1 Rest of the World. October /69

24 ISR (10) IS (11) QR (15) Domestic (12) SEPA (13) ROW (14) Use Cases: Credit Transfer Salary (20) Type Chapter ACCP (35) ACWC (37) PART (38) All Format Changes for Credit Transfer NOA (46) SIA (47) CND (48) RJCT (39) CWD (49) Internal (64) External (65) ISR (40/41) DD Core (44) DD B2B (45) SDD Core (42) SDD B2B (43) Old formats and lasting formats New formats Orange/Red Payment Slip New Payment Slip Debtor or Invoice Creditor or Invoice camt.053 camt.053 pain.002 pain.001 MT940 V11 MT940 Protocol DTA A10 A11 Debtor Bank Clearing Creditor Bank pacs.008 pacs.008 October /69

25 ISR (10) IS (11) QR (15) Domestic (12) SEPA (13) ROW (14) Create pain.001 Salary (20) Type Chapter ACCP (35) ACWC (37) PART (38) Use Cases 10/11/15: Inpayment Slips NOA (46) SIA (47) CND (48) RJCT (39) CWD (49) Internal (64) External (65) ISR (40/41) DD Core (44) DD B2B (45) SDD Core (42) SDD B2B (43) Payment Slip Variants pain.002 pain.001 Payment Slip / QR-Bill Create pain.001 from Payment Slip or QR-Bill camt.053 camt.053 ISR (German ESR, French BVR, Italian PVR). Orange inpayment slip with reference number. Currently in use, see page 26 for details. IS (German ES, French BV, Italian PV). Red inpayment slip. Currently in use, see page 27 for details. QR-bill Will replace ISR and IS, see page 28 for details. pacs.008 pacs.008 Layout example To be considered New file format pain.001 instead of DTA Booking control needs to be implemented Notification control needs to be implemented October /69

26 ISR (10) IS (11) QR (15) Domestic (12) SEPA (13) ROW (14) Create pain.001 Salary (20) ACCP (35) ACWC (37) PART (38) Use Case 10: Orange Inpayment Slip Type 1 Chapter 3.1 NOA (46) SIA (47) CND (48) RJCT (39) CWD (49) Mandatory Dependent Recommended Optional Internal (64) External (65) ISR (40/41) DD Core (44) DD B2B (45) SDD Core (42) SDD B2B (43) Real name, no code TRF or TRA Notes: Only one currency per B-Level For Instruction Priority HIGH and/or Category Purpose SALA, CH01 has to be in B-Level ISR participant number must have 9 characters, e.g or , but not (missing dashes) or (additional zeros in front of first number block instead of in front of the second one) 1 4 See Impl. Guidelines for alternatives CH01 (= Type 1) CHF or EUR Please for all pain.001: Also use +Initiating Party ++Name +++Contact Details 2 3 ISR participant number ISR reference Source: Swiss Usage Guide for ISO Messages, Version 1.2 by SIX Interbank Clearing Ltd October /69

27 ISR (10) IS (11) QR (15) Domestic (12) SEPA (13) ROW (14) Create pain.001 Salary (20) ACCP (35) ACWC (37) PART (38) Use Case 11: Red Inpayment Slip Manual Type 2.2 Chapter 3.3 NOA (46) SIA (47) CND (48) RJCT (39) CWD (49) Internal (64) External (65) ISR (40/41) DD Core (44) DD B2B (45) SDD Core (42) SDD B2B (43) Manual entry into your software by using these fields Mandatory Dependent Recommended Optional Notes: Only one currency per B-Level For Instruction Priority HIGH and/or Category Purpose SALA, CH03 has to be in B-Level CH03 requires Creditor Agent CH02 (=Type 2.1) or CH03 (=Type 2.2) CHF or EUR See Impl. Guidelines for alternatives Bank s Postal Account Number TRA or TRF CHBCC 3 Source: Swiss Usage Guide for ISO Messages, Version 1.2 by SIX Interbank Clearing Ltd IID October /69

28 ISR (10) IS (11) QR (15) Domestic (12) SEPA (13) ROW (14) Create pain.001 Salary (20) Type 3 Chapter pain.001 tag RmtInf > Ustrd ACCP (35) ACWC (37) PART (38) Use Case 15: QR-Bill Mandatory Dependent Recommended Optional QR Elements Notes: Very new spec, subject to change! Only one currency per B-Level QR Elements Ustrd without Ref: Please for all pain.001: Also use +Initiating Party ++Name +++Contact Details NOA (46) SIA (47) CND (48) Internal (64) External (65) ISR (40/41) RJCT (39) CWD (49) DD Core (44) DD B2B (45) SDD Core (42) SDD B2B (43) QR Elements CHF or EUR Amt Ccy Name StrtNm BldgNb PstCd TwnNm Ctry Name StrtNm BldgNb PstCd TwnNm Source: Swiss Implementation Guidelines, V by SIX Interbank Clearing Ltd C C C +Remittance Information ++Structured +++Creditor Reference Information ++++Type +++++Code Or Proprietary Proprietary +Remittance Information ++Structured +++Creditor Reference Information ++++Reference +Remittance Information ++Structured +++Additional Remittance Information QRR Additional information for reconciliation. Recommendation: Use Syntax Definition by SWICO. QR-IBAN QR Reference Use once IBAN Name Tp Ref Ustrd October /69

29 ISR (10) IS (11) QR (15) Domestic (12) SEPA (13) ROW (14) Create pain.001 Salary (20) Type 3 Chapter ACCP (35) ACWC (37) PART (38) Use Case 15: QR-Bill vs. ISR NOA (46) SIA (47) CND (48) RJCT (39) CWD (49) Internal (64) External (65) ISR (40/41) DD Core (44) DD B2B (45) SDD Core (42) SDD B2B (43) Caution 1: Creditor Data Must Match the Bank s Master Data The procedure for the QR-bill is the first to have been aligned with current Swiss money laundering provisions from the outset. As a result, financial institutions will increasingly check whether the names and addresses of the accounts payable that appear on the QR-bill match the corresponding bank master data. For payees, this is easy to see when creating a QR-bill. However, for payers, this process becomes problematic if an accounts payable module does not draw on the information given on the bill but rather on out-of-date master data when the payer comes to settle the QR-bill. For payments via ISR, this issue has so far been of no significance due to this data not being transmitted. Caution 2: Changes for Debtor Grouping To date, V11 files have been created for each internal ISR subscriber number at Credit Suisse. Multiple subscriber numbers could relate to one bank account. In the future, the for the QR-bill will be created for each QR-IBAN. Since each bank account can have only one QR-IBAN, it is not possible to continue the previous setup involving bank accounts with multiple subscriber numbers. Clients who still wish to group their accounts receivable when payment is received must do this with multiple QR-IBANs, and therefore with multiple bank accounts. Alternatively, the accounts receivable software can choose to distinguish between accounts receivable groups using the reference numbers and can map these groups accordingly. For the latter, as was already the case at PostFinance, the first six positions are now at your disposal, thereby making a total of 26 positions in the 27-digit reference number; old subscriber numbers can therefore continue to be used. October /69

30 ISR (10) IS (11) QR (15) Domestic (12) SEPA (13) ROW (14) Create pain.001 Salary (20) Type 3/4/5/6 Chapter ACCP (35) ACWC (37) PART (38) Use Cases 12/13/14: Bank Payments NOA (46) SIA (47) CND (48) RJCT (39) CWD (49) Internal (64) External (65) ISR (40/41) DD Core (44) DD B2B (45) SDD Core (42) SDD B2B (43) Invoice or accounting voucher Create pain.001 from invoice or accounting voucher Common Mistake: CH03 Is Not Payment Type 3 Please note that Payment Pype 3 transactions must not contain a Local Instrument. Local Instrument CH03 is not Payment Type 3 (domestic credit transfer in CHF or EUR) but Payment Type 2.2 (IS, red two-stage inpayment slip in CHF or EUR): camt.053 camt.053 pain.002 pain.001 pacs.008 pacs.008 Source: Swiss Implementation Guidelines, Version by SIX Interbank Clearing Ltd To be considered New file format pain.001 instead of DTA Booking control needs to be implemented Notification control needs to be implemented October /69

31 ISR (10) IS (11) QR (15) Domestic (12) SEPA (13) ROW (14) Create pain.001 Salary (20) ACCP (35) ACWC (37) PART (38) Use Case 12: Domestic Bank Payment Type 3/4 Chapter 3.4 NOA (46) SIA (47) CND (48) RJCT (39) CWD (49) Mandatory Dependent Recommended Optional Internal (64) External (65) ISR (40/41) DD Core (44) DD B2B (45) SDD Core (42) SDD B2B (43) Type 3: CHF or EUR Type 4: not CHF or EUR Source: Swiss Usage Guide for ISO Messages, Version 1.2 by SIX Interbank Clearing Ltd Notes: Only one currency per B-Level Please for all pain.001: Also use +Initiating Party ++Name +++Contact Details October /69

32 ISR (10) IS (11) QR (15) Domestic (12) SEPA (13) ROW (14) Create pain.001 Salary (20) ACCP (35) ACWC (37) PART (38) Use Case 13: SEPA X-Border Payment Type 5 Chapter 3.6 NOA (46) SIA (47) CND (48) RJCT (39) CWD (49) Mandatory Dependent Recommended Optional Internal (64) External (65) ISR (40/41) DD Core (44) DD B2B (45) SDD Core (42) SDD B2B (43) EUR TRA or TRF SEPA Swiss Implementation Guidelines recommend <AdrLine> and <Ctry>. CS strongly encourages to include Postal Address, if possible in the structured way as some SEPA countries seem to consider it mandatory. Notes: Only one currency per B-Level For Category Purpose SALA, SEPA has to be in B-Level Please for all pain.001: Also use +Initiating Party ++Name +++Contact Details Source: Swiss Usage Guide for ISO Messages, Version 1.2 by SIX Interbank Clearing Ltd October /69

33 ISR (10) IS (11) QR (15) Domestic (12) SEPA (13) ROW (14) Create pain.001 Salary (20) Type 6 Chapter ACCP (35) ACWC (37) PART (38) Use Case 14: Other X-Border Payment NOA (46) SIA (47) CND (48) RJCT (39) CWD (49) Mandatory Dependent Recommended Optional Internal (64) External (65) ISR (40/41) DD Core (44) DD B2B (45) SDD Core (42) SDD B2B (43) Notes: Only one currency per B-Level TRA or TRF SELDDENN001 1 Bahnhofplatz See Impl. Guidelines for alternatives Swiss Implementation Guidelines recommend <AdrLine> and <Ctry>. CS strongly encourages to include Postal Address, if possible in the structured way as some SEPA countries seem to consider it mandatory. Please for all pain.001: Also use +Initiating Party ++Name +++Contact Details Neustadt DE Source: Swiss Usage Guide for ISO Messages, Version 1.2 by SIX Interbank Clearing Ltd October /69

34 ISR (10) IS (11) QR (15) Domestic (12) SEPA (13) ROW (14) Create pain.001 Salary (20) ACCP (35) ACWC (37) PART (38) Use Case 20: Salary Payment Type 3 Chapter 3.5 NOA (46) SIA (47) CND (48) RJCT (39) CWD (49) Internal (64) External (65) ISR (40/41) DD Core (44) DD B2B (45) SDD Core (42) SDD B2B (43) Create pain.001 for salary payment Caution: SALA flag has no effect on booking and advices in Swiss pain.001 Salary payments must have: Batch Booking TRUE or empty and Debtor Account >Type>Proprietary CND or NOA pain.002 pain.001 camt.053 pacs.008 pacs.008 camt.053 What happens without TRUE or CND/NOA? camt.053 default account setting is always batch booking, so the client will receive batch booking (unless the pain.001 is set to batch booking FALSE) default account setting is always with details, so for salary payments details have to be stopped with CND or NOA! To be considered New file format pain.001 instead of DTA Booking steering needs to be implemented Advice steering needs to be implemented October /69

35 ISR (10) IS (11) QR (15) Domestic (12) SEPA (13) ROW (14) Create pain.001 Salary (20) ACCP (35) ACWC (37) PART (38) Use Case 20: Salary Payment Type 3 Chapter 3.5 NOA (46) SIA (47) CND (48) RJCT (39) CWD (49) Mandatory Dependent Recommended Optional Internal (64) External (65) ISR (40/41) DD Core (44) DD B2B (45) SDD Core (42) SDD B2B (43) Batch Booking has to be TRUE or empty SALA has no impact on the salary payment processing Advice control has to be CND or NOA Source: Swiss Usage Guide for ISO Messages, Version 1.2 by SIX Interbank Clearing Ltd Notes: Only one currency per B-Level Please for all pain.001: Also use +Initiating Party ++Name +++Contact Details October /69

36 ISR (10) IS (11) QR (15) Domestic (12) SEPA (13) ROW (14) pain.001 in General Salary (20) ACCP (35) ACWC (37) PART (38) Payment Type Information Type 3 Chapter 3.5 NOA (46) SIA (47) CND (48) RJCT (39) CWD (49) Internal (64) External (65) ISR (40/41) DD Core (44) DD B2B (45) SDD Core (42) SDD B2B (43) Payment Type Information B-Level C-Level Instruction Priority HIGH (Express payment between noon and cut-off time) HIGH ( ) Service Level SEPA (Payment Type PT 5) SEPA (Payment Type 5) Local Instrument CH01 (PT 1), CH02 (PT 2.1), CH03 (PT 2.2) CH01 (PT 1), CH02 (PT 2.1), CH03 (PT 2.2) Category Purpose SALA (Salary payment, has no effect on advice steering) SALA ( ) SALA + CH01 currently rejected, being fixed. Combinations should be on B-Level. If on both Levels, B-Level is rejected. October /69

37 ISR (10) IS (11) QR (15) Domestic (12) SEPA (13) ROW (14) pain.001 in General Salary (20) ACCP (35) ACWC (37) PART (38) Important Issues to Consider Type 3 Chapter 3.5 NOA (46) SIA (47) CND (48) RJCT (39) CWD (49) Internal (64) External (65) ISR (40/41) DD Core (44) DD B2B (45) SDD Core (42) SDD B2B (43) pain.002 pain.001 camt.053 pacs.008 To be considered New file format pain.001 instead of DTA Booking steering needs to be implemented Advice steering needs to be implemented pacs.008 camt.053 Structured Master Data and Addresses Master data as source for all pain.001 payment instructions have to be very structured to avoid rejected files (pain.002 status RJCT). Credit Suisse encourages to use structured pain.001 tags instead of unstructured ones whenever possible, also for addresses. For foreign payments, the Swiss Implementation Guidelines recommend the use of unstructured address information, but particularly for payment type 5, recommendation of structured address information is under investigation. Structuring the customer s data before the customer creates pain.001 files is crucial. Therefore Credit Suisse suggests offering your clients data cleansing before they go live with pain.001. This should include consistent use of the IBAN. Do Not Allow Multiple Currencies in One B-Level Index of the Swiss Business Rules include an Additional Optional Service (AOS) to create more than one B-Level for each currency. Credit Suisse and other banks will not include this AOS, i.e. one B- Level for each currency will be mandatory to avoid reconciliation problems caused by making the same reference appear several times in the resulting camt.05x. Structuring data is one major principle of ISO 20022, therefore this should not be compromised by mixing instructions which have to be processed differently in the financial markets. October /69

38 ISR (10) IS (11) QR (15) Domestic (12) SEPA (13) ROW (14) pain.001 in General Salary (20) ACCP (35) ACWC (37) PART (38) Other Issues to Consider Type 3 Chapter 3.5 NOA (46) SIA (47) CND (48) RJCT (39) CWD (49) Internal (64) External (65) ISR (40/41) DD Core (44) DD B2B (45) SDD Core (42) SDD B2B (43) Recommendations Recommendations are not mandatory, but there is always a reason why they are not only classified as optional Therefore Credit Suisse strongly encourages to implement not only mandatory elements, but also recommended ones pain.002 pain.001 camt.053 pacs.008 To be considered New file format pain.001 instead of DTA Booking steering needs to be implemented Advice steering needs to be implemented pacs.008 camt.053 Unique IDs Create unique IDs like MsgId, PmtInfId and InstrId to facilitate file processing and support InstrId is only recommended, but as mentioned above strongly encouraged by Credit Suisse IDs are used in telephone support, so please avoid complicated and long combinations of upper and lower case IDs Initiating Party Name The Name of the Initiating Party should be the actual name of the party sending the payment order to the bank, not a code Contact Details Please use the Initiating Party Contact Detail tags Name and Other to list the name and the version of your software, this will help to support our mutual customers considerably October /69

39 ISR (10) IS (11) QR (15) Domestic (12) SEPA (13) ROW (14) Match pain.002 with pain.001 Salary (20) ACCP (35) ACWC (37) PART (38) Use Cases 35 39: Status Report Type Chapter 3.5 NOA (46) SIA (47) CND (48) RJCT (39) CWD (49) Internal (64) External (65) ISR (40/41) DD Core (44) DD B2B (45) SDD Core (42) SDD B2B (43) Match pain.002 with pain.001 Available Status Categories ACCP Accepted (Use Case 35) Syntax/semantics ok across all levels pain.002 pain.001 camt.053 camt.053 ACWC C Accepted with Change (Use Case 37) Not used at Credit Suisse ACCP with status code used instead pacs.008 pacs.008 PART Partially Accepted (Use Case 38) At least 1 B-level was incorrect (at least 1 correct) or at least 1 C-level in 1 B-level was incorrect (at least 1 correct) To be considered New file format pain.002 instead of bank-proprietary transaction protocol pain.002 only negative details No execution information Status should be indicated in your software (with Direct Link, Direct Exchange, or SWIFT connectivity only) RJCT Rejected (Use Case 39) Group Status: whole message rejected. A-level not correct or all B- or C-levels are incorrect. PmtInf: all transactions in the corresponding B-level rejected October /69

40 ISR (10) IS (11) QR (15) Domestic (12) SEPA (13) ROW (14) Match pain.002 with pain.001 Salary (20) ACCP (35) ACWC (37) PART (38) Use Case 35: Status Report ACCP Type Chapter NOA (46) SIA (47) CND (48) RJCT (39) CWD (49) Internal (64) External (65) ISR (40/41) DD Core (44) DD B2B (45) SDD Core (42) SDD B2B (43) Source: Swiss Usage Guide for ISO Messages, Version 1.2 by SIX Interbank Clearing Ltd October /69

41 ISR (10) IS (11) QR (15) Domestic (12) SEPA (13) ROW (14) Match pain.002 with pain.001 Salary (20) Type ACCP (35) ACWC (37) PART (38) Use Case 37: Status Report ACWC Appendix B2 NOA (46) SIA (47) CND (48) RJCT (39) CWD (49) Internal (64) External (65) ISR (40/41) DD Core (44) DD B2B (45) SDD Core (42) SDD B2B (43) Practice Not used at Credit Suisse, ACCP is used instead Execution date modification by the bank is indicated by Status Reason Code DT06 Source: Swiss Usage Guide for ISO Messages, Version 1.2 by SIX Interbank Clearing Ltd October /69

42 ISR (10) IS (11) QR (15) Domestic (12) SEPA (13) ROW (14) Match pain.002 with pain.001 Salary (20) Type Appendix ACCP (35) ACWC (37) PART (38) Use Case 38: Status Report PART NOA (46) SIA (47) CND (48) RJCT (39) CWD (49) Internal (64) External (65) ISR (40/41) DD Core (44) DD B2B (45) SDD Core (42) SDD B2B (43) Examples The Credit Suisse ISO Test Platform features several PART examples Please find an overview of the best practice examples in this guide from page 58 The ISO Test Platform can be accessed via credit-suisse.com/iso20022test October /69

43 ISR (10) IS (11) QR (15) Domestic (12) SEPA (13) ROW (14) Match pain.002 with pain.001 Salary (20) Type ACCP (35) ACWC (37) PART (38) Use Case 39: Status Report RJCT Appendix B3 NOA (46) SIA (47) CND (48) RJCT (39) CWD (49) Internal (64) External (65) ISR (40/41) Example: Error at A-Level Message submitted twice by the debtor Example: Error at B-Level Debtor s account is blocked DD Core (44) DD B2B (45) SDD Core (42) SDD B2B (43) Example: Error at C-Level ISR reference number check digit incorrect Source: Swiss Usage Guide for ISO Messages, Version 1.2 by SIX Interbank Clearing Ltd October /69

44 ISR (10) IS (11) QR (15) Domestic (12) SEPA (13) ROW (14) Match with pain.001 Salary (20) ACCP (35) ACWC (37) PART (38) Use Cases for Account Payables Type Chapter 3.5 NOA (46) SIA (47) CND (48) RJCT (39) CWD (49) Internal (64) External (65) ISR (40/41) DD Core (44) DD B2B (45) SDD Core (42) SDD B2B (43) Available Booking and Statement Categories in pain.001 Match with pain.001 Payment Information +Batch Booking Payment Information +Debtor Account ++Type +++Proprietary pain.002 pain.001 camt.053 camt.053 No Advice (Use Case 46) Individual Advice (Use Case 47) TRUE/FALSE/ empty FALSE NOA SIA pacs.008 pacs.008 Collective Advice without Details (Use Case 48) TRUE/empty CND Individual Advice (Use Case 49) TRUE/empty CWD To be considered New file format ch Preparsing to reveal message type: debit/credit notification, ISR credit notification, LSV credit notification, external batch booking notification Could be end of day, depending on the report type (e.g. ISR end of day) Could be intraday, depending on the report type (e.g. ISR every 2 hours) October /69

45 ISR (10) IS (11) QR (15) Domestic (12) SEPA (13) ROW (14) Match with pain.001 Salary (20) ACCP (35) ACWC (37) PART (38) Use Cases 48 for Salary Payments Type Chapter 3.5 NOA (46) SIA (47) CND (48) RJCT (39) CWD (49) Internal (64) External (65) ISR (40/41) DD Core (44) DD B2B (45) SDD Core (42) SDD B2B (43) Available Booking and Statement Categories in pain.001 Match with pain.001 Payment Information +Batch Booking Payment Information +Debtor Account ++Type +++Proprietary pain.002 pain.001 camt.053 camt.053 No Advice (Use Case 46) Individual Advice (Use Case 47) TRUE/FALSE/ empty FALSE NOA SIA pacs.008 pacs.008 Collective Advice without Details (Use Case 48) TRUE/empty CND Individual Advice (Use Case 49) TRUE/empty CWD To be considered SALA flag has no effect on booking and advices in Swiss pain.001 Salary payments must have Batch Booking TRUE (or empty) and Debtor Account > Type > Proprietary CND October /69

46 Match camt.053 with pain.001 Use Case 64: Internal Batch Booking Notification ISR (10) IS (11) QR (15) Domestic (12) Salary (20) ACCP (35) ACWC (37) SEPA (13) ROW (14) PART (38) NOA (46) SIA (47) CND (48) Internal (64) External (65) Type Chapter 3.5 ISR (40/41) RJCT (39) CWD (49) DD Core (44) DD B2B (45) SDD Core (42) SDD B2B (43) Available Booking and Statement Categories in pain.001 Match camt.053 (with details) with pain.001 Payment Information +Batch Booking Payment Information +Debtor Account ++Type +++Proprietary pain.002 pain.001 camt.053 camt.053 Single Booking without Details Single Booking with Details FALSE FALSE NOA SIA pacs.008 pacs.008 Batch Booking without Details TRUE/empty NOA OR CND Batch Booking with Details TRUE/empty CWD To be considered New file format camt instead of MT940 October /69

47 Match camt.053 with pain.001 Use Case 65: External Batch Booking Notification ISR (10) IS (11) QR (15) Domestic (12) Salary (20) ACCP (35) ACWC (37) SEPA (13) ROW (14) PART (38) NOA (46) SIA (47) CND (48) Internal (64) External (65) Type Chapter 3.5 ISR (40/41) RJCT (39) CWD (49) DD Core (44) DD B2B (45) SDD Core (42) SDD B2B (43) camt.053 One reference per <Ntry> to one in <AddtInfInd><MsgId> pain.002 pain.001 camt.053 Match camt.053 with reference to with pain.001 camt.053 pacs.008 pacs.008 One reference per file to one camt.053 in <GrpHdr><MsgId> To be considered New file format camt instead of MT940 Details can be outsourced to Source: Credit Suisse ISO Test Platform October /69

48 ISR (10) IS (11) QR (15) Domestic (12) SEPA (13) ROW (14) Match ISR with pain.001 Salary (20) Type Chapter ACCP (35) ACWC (37) PART (38) Use Cases 40/41 for Creditors NOA (46) SIA (47) CND (48) RJCT (39) CWD (49) Internal (64) External (65) ISR (40/41) DD Core (44) DD B2B (45) SDD Core (42) SDD B2B (43) Reconciliation Data pain.002 pain.001 camt.053 Payments Slip Match ISR with Payment Slip camt ISR IS QR-bill <CrdtRefInf><Ref> </Ref></CrdtRefInf> Amount, address data etc. <CrdtRefInf><Ref> </Ref></CrdtRefInf> pacs.008 pacs.008 Layout example To be considered New file format instead of V11 Switch from V11 to at latest with the new payment slip Same information in camt.053 with details or camt.053 without details and external batch booking notification in October /69

49 ISR (10) IS (11) QR (15) Domestic (12) SEPA (13) ROW (14) Matching in General Salary (20) Type Chapter ACCP (35) ACWC (37) PART (38) Debtor Side and Creditor Side NOA (46) SIA (47) CND (48) RJCT (39) CWD (49) Internal (64) External (65) ISR (40/41) DD Core (44) DD B2B (45) SDD Core (42) SDD B2B (43) Payment Order P2P: MsgId/PmtInfId/InstrId E2E: EndToEndId/RmtInf Statement/Advice P2P: MsgId/PmtInfId/InstrId E2E: EndToEndId/RmtInf Invoice RmtInf (EndToEndId) pacs.008 EndToEndId/RmtInf Statement/Advice E2E: EndToEndId/RmtInf Point-to-Point and End-to-End References Point-to-point references are transmitted between the sender and receiver of a payment phase (bank to client, bank to bank, or bank to client). End-to-end-references are transmitted between the debtor and the creditor, e.g. the ISR reference. However, the following issues have to be considered: Creditor Reconciliation The EndtoEndId is often unknown to the creditor, so the RmtInf is important for his reconciliation. Debtor Reconciliation (also see the following two pages) The EndtoEndId is compulsory and is defined as major reconciliation ID for the debtor side. But there are at least three exceptions: When your software allows to enter an EndToEndId created by the creditor, this ID might not be unique, so you might also use the InstrId for the reconciliation on the debtor side The EndtoEndId is not included in the camt.05x for collective booking without details, so for collective bookings the PmtInfId should be used by the debtor as it is also transmitted in the case of CND or NOA. For individual booking and NOA, all references are missing in the camt.05x, so use name/amounts/etc. for reconciliation October /69

50 ISR (10) IS (11) QR (15) Domestic (12) SEPA (13) ROW (14) Matching in General Salary (20) Type Chapter ACCP (35) ACWC (37) PART (38) Debtor Side camt.05x References NOA (46) SIA (47) CND (48) RJCT (39) CWD (49) Recommended for reconciliation Recommended for reconciliation if used Also included in camt.053 Internal (64) External (65) ISR (40/41) DD Core (44) DD B2B (45) SDD Core (42) SDD B2B (43) pain.001 camt.052/camt.053/ Point to point IDs End to end ID Identify the pain.001 s A-Level Identify the pain.001 s B-Level Identify the pain.001 s C-Level Batch booking = true CND/ NOA MsgId PmtInfId 3 CWD MsgId PmtInfId InstrId EndToEndId 3 Batch booking = false NOA Amount, name 4 SIA MsgId PmtInfId InstrId (optional) 2 EndToEndId (mandatory) 1 October /69

51 ISR (10) IS (11) QR (15) Domestic (12) SEPA (13) ROW (14) Matching in General Salary (20) Type Chapter ACCP (35) ACWC (37) PART (38) Debtor Side X-Format References NOA (46) SIA (47) CND (48) RJCT (39) CWD (49) Internal (64) External (65) ISR (40/41) DD Core (44) DD B2B (45) SDD Core (42) SDD B2B (43) What Relationship Do References from Different Formats Have to Each Other? During a transitional period, companies will use both ISO and old formats. The assignment of references between the formats takes place as follows: Type of Reference Point-to-Point (P2P) End-to-End (E2E) For (Level) Payment Order Statement/Advice pain.001 MT101 DTA camt.05x MT940 Paper/PDF File (A) MsgId :20: File name MsgId - - Instruction (B) PmtInfId :21R: - PmtInfId :61: subtag 7 or 9* - Transaction (C) InstrId - Output sequence # InstrId :86: trigger tag?21 - End-to-End-Info EndToEndId :21: - EndToEndId :86: trigger tag?22** EndToEndId Remittance-Info RmtInf :70: 70: RmtInf :86: trigger tag?60 RmtInf * If 16 characters, then Subtag 7, otherwise Subtag 9 ** If no InstrId available in payment order, then also in field :61: Subtag 7 or 9 Remarks about MT101 :20: Sender Reference :21R: Customer Specified Reference :21: Transaction Reference :70: Remittance Information Remarks about MT940 :61: Details of the Transaction :86: Info to Account Holder?21 Your Reference?22 Client Reference?60 Reason for payment Remarks about Paper/PDF RmtInf/EndToEndId with single booking. October /69

52 ISR (10) IS (11) QR (15) Domestic (12) SEPA (13) ROW (14) Use Cases: Direct Debit Salary (20) Type Chapter ACCP (35) ACWC (37) PART (38) All Format Changes for Direct Debit NOA (46) SIA (47) CND (48) RJCT (39) CWD (49) Internal (64) External (65) ISR (40/41) DD Core (44) DD B2B (45) SDD Core (42) SDD B2B (43) Old formats and lasting formats New formats Debtor Invoice Creditor Invoice camt.053 pain.002 pain.008 camt.053 MT940 V11 Protocol LSV MT940 A10 A11 pacs.003 pacs.003 A10 A11 Debtor Bank Clearing Creditor Bank pacs.008 pacs.008 Cases will be published by the time the pain.008 LS specifications are published. October /69

53 Agenda Framework Page 5 Formats Page 11 Use Cases Page 22 Test Procedure Page 53 October /69