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 April 2017

2 Agenda Framework Page 3 Formats Page 19 Use Cases Page 35 Test Procedure Page 61 April /78

3 Agenda Framework Page 3 Formats Page 19 Use Cases Page 35 Test Procedure Page 61 April /78

4 Framework: Legal Obligations Money Laundering: Debtor/Creditor Have to Be Known Current Situation Historically, communication bandwidth and storage space were precious. To save communication bandwidth and storage space, some data is not transmitted in a payment order. Payer may be unknown Payee may be unknown Future Money laundering regulations require also payer data to be transmitted. Payer known Payee known Layout example April /78

5 Payment Harmonization: Formats Opportunity to Improve Payment Formats Instead of just making small, selective changes to various formats make general shift to one future format: XML in ISO standard April /78

6 Payment Harmonization: Formats Opportunity to Improve Payment Formats But: Softwares (SW) can still interpret the same guidelines differently SW A SW B SW C <TAG></TAG> <TAG>0</TAG> <TAG>ZERO</TAG> But: Banks can still interpret the same file structure differently Bank A Bank B Bank C But: Banks can still process the same file content differently Bank B Bank C camt with details camt without details April /78

7 Payment Harmonization: Testing Required Opportunity to Avoid Problems Areas of deviation Technical interpretation can vary potential rejects Processing can vary potential execution differences New and much bigger format potential errors Need no. 1: Testing with major financial institutes required ISO Test Platform Avoid problems Join List of Compatible Software Problems Opportunities April /78

8 Payment Harmonization: Client Enabling Make Sure Your Clients Are Ready for the First Deadline Release Deadline PostFinance End of DTA Develop Test/ Adapt Client Migration Later Releases Migration Peak First market migration until mid-2018 PostFinance migration until end of 2017 Many clients with several bank relationships expected to migrate only once resulting in Peak 2HY17 Release of XML formats as early as possible to enable migration April /78

9 Payment Harmonization: Deploy Early Opportunity to Balance Your Workload and Get Ahead of Competitors Release planning Late release short client migration time frame Late release increasing migration requests Late release support peak Need no. 2: Release new formats as early as possible Early releases Spread migration and flatten support peak Early readiness as advantage in the market Problems Opportunities April /78

10 Payment Harmonization: Benefits Simplifications for Software Vendors Use know-how from SEPA migration to improve Swiss standards SEPA Migration Swiss Payments Harmonization Align with European standard ISO ISO Adapt to one standard ISO Switch from two payment systems to one system DTA EZAG TPs/Protocols LSV+/BDD/DD ZED ES/ESR/ASR/EGA SIC A10, A11 ISO Less costs for you: Simplified software development and maintenance Use IBAN instead of bank-proprietary account numbers A 123-AB CH CREDITSUISSE Use one payment slip instead of two Mega Genius GmbH Strasse Zürich CH CHF Daniel Meli Uetlibergstrasse Zürich Layout example April /78

11 Framework: ISO Client Market Transformation Move from Proprietary to XML Formats in Europe and Switzerland Government-regulated format change to ISO for Euro payments and direct debits Old Domestic Formats EUR Countries Old Domestic Formats Non-EUR Countries pain.001/pain.002/pain.008 Opportunity Format change to ISO in Switzerland Old Domestic Formats Old Domestic Payment Slips CT pain.001/pain.002/pain.008/camt Reporting New Payment Slips April /78

12 Payment Harmonization: Value Chain Coverage Minimum Adaptation or Added Value? Your Software Like-for-Like Adaptation XML Data for Payments Adaption with minimum changes Unused potential with data, and functions Data Legacy Data for Payments Unused tags Adaptation with additional data XML Data for Payments Add previously unused data Potential to differentiate with new functions and services Additional data April /78

13 Framework: Added Value Examples End-to-end reference throughout the entire value chain from client in one country to client in another Ultimate beneficiary/debtor centralizing Creditor agent (bank) Creditor pacs.008 camt with Ultimate Debtor information Debtor agent (bank) Delivery of goods Invoice pain.001 Netting Debtor e.g. the Ultimate Debtor s shared service center Invoice Ultimate Debtor More structured data, less parsing Use status reports: harmonized pain.002 instead of bank-proprietary protocols Bank A Bank B Bank C Protocol Format A Protocol Format B Protocol Format C Debtor Bank A Bank B Bank C pain.002 pain.002 pain.002 Debtor camt not only for payment reporting, but also as meta standard for potential future card reporting, securities reporting, trade finance reporting, etc. Credit Advice Debit Advice Credit Card Report Securities Report Your ideas April /78

14 Payment Harmonization: Conclusion for Software Vendors Summary of Advantages Simplifications E.g.: One standard instead of many standards Same standard as in EU Switch from two payment systems to one Use IBAN instead of various bank account numbers One inpayment slip instead of two Lower costs for software development and maintenance Software functionalities are precondition for additional bank functionalities (value chain) New format offers additional functionalities for added value ISO data has to be more structured than in legacy formats Credit Suisse channel offering optimized for ISO Migration phases will create early and late adopters Opportunity to distinguish own software from competitors by enabling additional bank functionalities Opportunity to distinguish own software from competitors by offering added values instead of just minimum functionality Opportunity to offer data cleansing service on the occasion of a service release implementation Opportunity to offer sustainable connectivity to Credit Suisse by selecting optimum channel Opportunity to distinguish own software from competitors by offering formats early April /78

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

16 Framework: Migration Phases Step-by-Step Approach for Software Vendors Strategy Implementation Plan strategic offering and further co-operation for Formats Channels Ensure new functionality for Formats Channels Format Tests Ensure version compatibility: Upcoming software version Current software version Old software versions test properly with Credit Suisse Sales Channel Onboarding Ensure version compatibility: Upcoming software version Current software version Old software versions Advertise and roll out new software release connect properly to Credit Suisse April /78

17 Framework: Migration Timetable (1/2) Two Phases for Credit Suisse Formats and Connectivity Credit Transfer Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec 1Q 2Q 3Q 4Q 1Q 2Q 3Q 4Q 1Q 2Q 3Q 4Q pain.001 SIC pain.001 EPC/CGI pain.002 SIC/EPC/CGI * * * Direct Link/Direct Exchange Direct Net Direct Link/Direct Exchange** Direct Net** (only GUI, not DXI) Direct Link/Direct Exchange DTA & DTA Protocol Direct Link/Direct Exchange Direct Net Direct Debit pain.008 & pain.002 SDD SIC/EPC Direct Link/Direct Exchange pain.008 LS Direct Link/Direct Exchange Direct Net pain.002 LS Direct Link/Direct Exchange LSV/LSV Protocol Direct Link/Direct Exchange 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 April /78

18 Framework: Migration Timetable (2/2) Two Phases for Credit Suisse Formats and Connectivity Reports Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec 1Q 2Q 3Q 4Q 1Q 2Q 3Q 4Q 1Q 2Q 3Q 4Q camt.052 SIC (with details from Sep 2017*) camt.052 CGI MT942 Direct Link/Direct Exchange Direct Link/Direct Exchange Direct Link/Direct Exchange camt.053 SIC (with details from Sep 2017) camt.053 CGI MT940 Direct Link/Direct Exchange Direct Net Direct Link/Direct Exchange Direct Net Direct Link/Direct Exchange Debit/Credit SIC Debit/Credit CGI ISR SIC ISR CGI QR Code SIC/CGI V11 * Details for Full Report only Direct Link/Direct Exchange Direct Net Direct Link/Direct Exchange Direct Link/Direct Exchange Direct Link/Direct Exchange Direct Net Direct Link/Direct Exchange Direct Link/Direct Exchange Direct Net April /78

19 Agenda Framework Page 3 Formats Page 19 Use Cases Page 35 Test Procedure Page 61 April /78

20 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 Net 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 31/32 (some banks ignore this camt control) SALA flag in pain.001 without effect, details see page 46/47 (some banks still use the SALA flag as an AOS) Master data should be sent in a structured way, details see page 42 Timing DTA * pain.001 Possible data reduction due to data conversion * April /78

21 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) LS Switzerland Upcoming Former LSV+ and BDD Direct Link EBICS Direct Link Intersys only SIC Direct Exchange Direct Net DXI/GUI only LS SWIFT FileAct Use SIC or EPC for SEPA Direct Debit (SDD). Wait for pain.008 LS 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 LS yet to be defined in the LEON project Via Direct Net only pain.008 LS planned Timing LSV pain.008 SDD pain.008 LS April /78

22 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 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 Net DXI/GUI SWIFT FileAct Direct Net no file download but status indication in the Direct Net 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 April /78

23 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 1.4 SIX Account Statement CGI (CH) World Account Statement End of day With details Without details Direct Link EBICS Direct Link Intersys Direct Exchange Direct Net 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 MT Tests camt.053 April /78

24 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 1.4 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 Net DXI/GUI 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 MT Tests camt.052 April /78

25 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 1.4 SIX CGI (CH) World Report Types Debit/Credit Notification ISR Credit Notification LSV Credit Notification External Batch Booking Notification (for camt.053) Periodicity Details Channels Best Practice Alternative formats Caution Timing 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 Net DXI/GUI 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. 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 next two pages for details; not supported by all Swiss banks Postfinance uses additional and different report types ZED V11 ISR/LSV Tests April /78

26 pain.001 pain.008 camt.053 Formats: Reporting Offering Recommendation, Special Needs or any Combination pain.002 camt.052 camt.053 camt.052 Additional camt.053 Case 1 camt.053 without detail End of day ISR End of day or intraday Mainly end-of-day cash management 2 camt.053 with detail End of day 3 camt.053 without detail End of day BBN End of day 4 camt.053 without detail End of day BBN End of day camt.052 Intraday Explicitly with intraday cash management 5 camt.053 with detail End of day camt.052 Intraday 6 camt.053 without detail End of day camt.052 Intraday 7 camt.053 with detail End of day camt.052 Intraday camt.053 without detail End of day April /78

27 pain.001 pain.008 pain.002 Formats: Reporting Core Offering Today and Tomorrow camt.053 camt.052 Legacy XML Remark: MT94x will not be discontinued 1. Likefor-Like MT940 (without details) V11 (ISR details) Paper or E- Documents (Other details) CAMT.053 (without details) CAMT.054 ISR (ISR details) Paper or E- Documents (Other details) 2. Automated Account Report in one file MT940 V11 (without details) (ISR details) Paper or E- Documents (Details) CAMT.053 (with details) not suitable for salary payments CAMT.054 ISR (ISR details) Paper or e-documents could be discontinued 3. Automated Account Report in several files MT940 (without details) Paper or E- Documents (Other details) CAMT.053 (without details) CAMT.054 Batch Booking Notification (Details) Paper or e-documents could be discontinued April /78

28 pain.001 pain.008 pain.002 Formats: Reporting SIX Comparison camt.053 camt.052 Credit Suisse Offering (only partly for comparison) Variation Buchhaltungsrelevant (end-of-day) Cash Management relevant (Intraday, inkrementell) Abstimmung Bankkonto und Debitorenbuchhaltung Untertägige Kontobewegungen Untertägige Avisierung Offering 1 Also available Offering 5 Also available Bnk-1 Bnk-2 Bnk-3 Bnk-4 Bnk-5 Bnk-6 camt.053 mit interner Sammelbuchungsauflösung camt.052 mit interner Sammelbuchungsauflösung camt.052 mit externer Sammelbuchungsauflösung im Avis Avis Avis Offering 3 Also available Offering 4 Also available Bnk-7 Bnk-8 Bnk-9 Bnk-10 Bnk-11 Bnk-12 camt.053 mit externer Sammelbuchungsauflösung im camt.052 mit interner Sammelbuchungsauflösung camt.052 mit externer Sammelbuchungsauflösung im Avis Avis Avis Offering 1 Also available Offering 5 Also available Kdn-1 Kdn-2 Kdn-3 Kdn-4 Kdn-5 Kdn-6 Kdn-7 Kdn-8 camt.053 mit interner Sammelbuchungsauflösung ohne camt.052 mit interner Sammelbuchungsauflösung camt.052 ohne Sammelbuchungsauflösung camt.052 mit externer Sammelbuchungsauflösung Avis Avis Avis Avis Also available Also available Offering 6 Also available Kdn-9 Kdn-10 Kdn-11 Kdn-12 Kdn-13 Kdn-14 Kdn-15 Kdn-16 camt.053 ohne Sammelbuchungsauflösung ohne camt.052 mit interner Sammelbuchungsauflösung camt.052 ohne Sammelbuchungsauflösung camt.052 mit externer Sammelbuchungsauflösung Avis Avis Avis Avis Offering 3 Also available Offering 4 Also available Source: Presentation Interaktion Kunde-Bank at PaymentStandards.CH Software Vendors Event in Bern Kdn-17 Kdn-18 Kdn-19 Kdn-20 Kdn-21 Kdn-22 Kdn-23 Kdn-24 camt.053 mit externer Sammelbuchungsauflösung ohne camt.052 mit interner Sammelbuchungsauflösung camt.052 ohne Sammelbuchungsauflösung camt.052 mit externer Sammelbuchungsauflösung Avis Avis Avis Avis April /78

29 pain.001 pain.008 pain.002 Formats: Reporting PostFinance Comparison camt.053 camt.052 Credit Suisse Offering (only partly for comparison) PostFinance Offering (status September 23, 2016, subject to change) Source: Overview of the harmonization of payment transactions in Switzerland at postfinance.ch Message affected ISO (XML) Yes Yes No, PostFinance format only No, PostFinance format only Yes (planned) Yes (planned) Yes (planned) No, PostFinance format only Yes (planned) No Yes (planned) No, PostFinance format only No, PostFinance format only No, PostFinance format only Yes Yes Yes (planned) PostFinance range Future PostFinance range from 2016 Future PostFinance range from mid-2018 Credit transfers/accounts payable EPO/DTA payment order for banks, order delivery Processing message (response to pain.001) Execution confirmation Individual confirmation Notifications/Account statements Account statement so far Account statement with 1 /without 2 detailed notification Intraday account movements Credit/debit advices 3 CH-DD credit/debit advices Core Direct Debit and B2B Direct Debit SEPA-DD credit/debit advices Core Direct Debit and B2B Direct Debit IS credit/debit advices 1 or 2 ISR credit/debit advices OSR credit/debit advices Debits CH-DD debit (Swiss Direct Debit) CH-DD processing message SEPA-DD order delivery SEPA-DD processing message Inpayment slip with data code ISR/IS in CHF and EUR pain.001 pain.002 camt.053 (existing) camt.053 with detailed notification or camt.053 without detailed notification camt.052 camt.053 with detailed notification or camt.053 with detailed notification or camt.053 with detailed notification or camt.053 with detailed notification or camt.053 with detailed notification or pain.008 in accordance with SIX implementation guidelines pain.002 pain.008 pain.002 Inpayment slip with data code April /78

30 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 Net 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 Net 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! April /78

31 pain.001 pain.008 Formats: Reporting Controlling the Debit Advice with pain.001 Tags camt.053 pain.002 camt.052 Payment Information +Debtor Account ++Type +++Proprietary NOA SIA Payment Information +Batch Booking False camt.053 single booking, no details No camt.053 single booking, with details with details True/Empty camt.053 batch booking, no details No pain.001 will be rejected CND pain.001 will be rejected camt.053 batch booking, no details no details CWD pain.001 will be rejected camt.053 batch booking, with details with details Empty camt.053 single booking, details as account default with details camt.053 batch booking, details as account default with details Bold: Recommended settings Out of 15 debit advice combinations, only 5 are recommended Your software should be able to control these recommended combinations, e.g. by one dropdown menu Red: Recommended settings for salary payments to allow confidentiality Salary payments should only allow one of these 5 combinations, e.g. by ticking a checkbox Grey: Not applicable or not recommended Credit Suisse Account Defaults camt in General In order to receive camt.053 or, Credit Suisse clients have to subscribe to them for each of their accounts. It is not possible to order nonsubscribed 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. Default is always with details! This can be overridden with CND or NOA. April /78

32 pain.001 pain.008 pain.002 camt.053 camt.052 Formats: Reporting Controlling Subscribed 1 Debit Advices with 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 C-Level CHF 30 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 1 No ordering of non-subscribed camt.053 and via pain.001 tags. April /78

33 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 pain.001 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 Net 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 no Details in 1 camt.053 No advice Account Default No advice Empty Amounts Details as AD* 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 April /78

34 Credit Suisse Client Channel Format Offering Overview of Connectivity Formats pain.001 pain.008 pain.002 camt.053 camt.052 Available now Not available Available in the future ISO Test Platform GUI Direct Net DXI EBICS Direct Link Intersys Direct Exchange SFTP SWIFT FileAct pain.001 SIC Yes Yes Yes 1 Yes 1 Yes 1 Yes 1 EPC No Jun 2017 No Yes 1 No Yes 1 Yes 1 CGI Yes Jun 2017 No Yes 1 No Yes 1 Yes 1 pain.008 SIC EPC Yes Yes No No Yes Yes Yes No Yes Yes Yes Yes pain.002 SIC EPC Yes Yes No No Yes Yes Yes No Yes Yes Yes Yes CGI Yes No Yes No Yes Yes camt.052 SIC CGI Yes No No No Jun 2017 Nov 2017 No No Jun 2017 Nov 2017 Jun 2017 Nov 2017 camt.053 SIC CGI Yes No Jun 2017 No Jun 2017 Nov 2017 No No Jun 2017 Nov 2017 Jun 2017 Nov 2017 Credit/Debit SIC CGI Yes No No No Oct 2017 Nov 2017 No No Oct 2017 Nov 2017 Oct 2017 Nov 2017 ISR SIC CGI Yes No Jun 2017 No Sep 2017 Nov 2017 No No Sep 2017 Nov 2017 Sep 2017 Nov Possible data reduction due to data conversion until Jun 2017 April /78

35 Agenda Framework Page 3 Formats Page 19 Use Cases Page 35 Test Procedure Page 61 April /78

36 Use Cases Remarks Payment Slips Bank Payments Special Payments Status Reports Notifications Statements Direct Debit pain.001 pain.001 pain.001 pain.002 camt.053/052 pain.008 ISR (10) IS (11) ISQ (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 pain.053/mt940 descriptions always include pain.052/mt942 Only bank formats are depicted, not PostFinance formats 1 Rest of the World. April /78

37 ISR (10) IS (11) ISQ (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 April /78

38 ISR (10) IS (11) ISQ (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 Payments Slip Create pain.001 from Payment Slip ISR (German ESR, French BVR, Italian PVR). Orange inpayment slip with reference number. Currently in use, see page 39 for details. pain.002 pain.001 camt.053 camt.053 IS (German ES, French BV, Italian PV). Red inpayment slip. Currently in use, see page 40 for details. QR Invoice Specifications April 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 April /78

39 ISR (10) IS (11) ISQ (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 See Impl. Guide for alternatives CH01 (= Type 1) 4 CHF or EUR 2 ISR participant number Source: Swiss Usage Guide for ISO Messages, Version 1.2 by SIX Interbank Clearing Ltd 3 ISR reference Notes: Service Level must not be SEPA Creditor Agent must be omitted April /78

40 ISR (10) IS (11) ISQ (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 Service Level must not be SEPA Creditor Agent must be omitted Remittance Info Structured must be omitted CH03 (=Type 2.2) TRA or TRF CHF or EUR See Impl. Guide for alternatives Bank s Postal Account Number CHBCC 3 Source: Swiss Usage Guide for ISO Messages, Version 1.2 by SIX Interbank Clearing Ltd BC April /78

41 ISR (10) IS (11) ISQ (15) Domestic (12) SEPA (13) ROW (14) Create pain.001 Salary (20) Type E1/E2 Chapter ACCP (35) ACWC (37) PART (38) Use Case 15: New Inpayment Slip 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) Expect new specifications and timeline in April Source: Media release October 19, 2016 by SIX Interbank Clearing Ltd April /78

42 ISR (10) IS (11) ISQ (15) Domestic (12) SEPA (13) ROW (14) Create pain.001 Salary (20) Type 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) pain.002 pain.001 Invoice or accounting voucher Create pain.001 from invoice or accounting voucher camt.053 pacs.008 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. Currently for payment types 5 and 6, address and country information is even mandatory at CS. 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. To be considered New file format pain.001 instead of DTA Booking control needs to be implemented Notification control needs to be implemented 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. April /78

43 Create pain.001 Use Case 12: Domestic Bank Payment ISR (10) IS (11) ISQ (15) Domestic (12) Salary (20) ACCP (35) ACWC (37) SEPA (13) ROW (14) Type 3/4 Chapter 3.4 PART (38) 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 Swiss Implementation Guidelines recommend <AdrLine> and <Ctry>. CS strongly encourages to include Postal Address, if possible in the structured way. Notes: Service Level must not be SEPA Local Instrument must be omitted Source: Swiss Usage Guide for ISO Messages, Version 1.2 by SIX Interbank Clearing Ltd April /78

44 ISR (10) IS (11) ISQ (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) Notes: Local Instrument must be omitted With IBAN no Creditor Agent required TRA or TRF SEPA EUR 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. Source: Swiss Usage Guide for ISO Messages, Version 1.2 by SIX Interbank Clearing Ltd April /78

45 ISR (10) IS (11) ISQ (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) TRA or TRF SELDDENN001 Bahnhofplatz See Impl. Guide for alternatives 1 Notes: Clearing System Identification Code must not be CHBCC Service Level must not be SEPA Local Instrument must be omitted Neustadt DE Source: Swiss Usage Guide for ISO Messages, Version 1.2 by SIX Interbank Clearing Ltd April /78

46 ISR (10) IS (11) ISQ (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 pain.002 pain.001 camt.053 pacs.008 pacs.008 camt.053 What happens without TRUE or CND? 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! To be considered New file format pain.001 instead of DTA Booking control needs to be implemented Notification control needs to be implemented April /78

47 ISR (10) IS (11) ISQ (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 Source: Swiss Usage Guide for ISO Messages, Version 1.2 by SIX Interbank Clearing Ltd April /78

48 ISR (10) IS (11) ISQ (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 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 pacs.008 To be considered New file format pain.001 instead of DTA Booking control needs to be implemented Notification control needs to be implemented pacs.008 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 April /78

49 ISR (10) IS (11) ISQ (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) Same as ACCP with correction, e.g. execution date changed 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 April /78

50 ISR (10) IS (11) ISQ (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 April /78

51 ISR (10) IS (11) ISQ (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) Example For this case it is assumed that the pain.001 credit transfer message that has been submitted cannot be executed on the desired day (e.g. if a date for execution was specified that is not a banking business day, or if the credit transfer message was submitted after the permitted submission times) The transfer is therefore re-dated and executed by the debtor agent on the next possible banking business day Source: Swiss Usage Guide for ISO Messages, Version 1.2 by SIX Interbank Clearing Ltd April /78

52 ISR (10) IS (11) ISQ (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 67 The ISO Test Platform can be accessed via credit-suisse.com/iso20022test April /78

53 ISR (10) IS (11) ISQ (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 April /78

54 ISR (10) IS (11) ISQ (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) April /78

55 ISR (10) IS (11) ISQ (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 April /78

56 Match camt.053 with pain.001 Use Case 64: Internal Batch Booking Notification ISR (10) IS (11) ISQ (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 April /78

57 Match camt.053 with pain.001 Use Case 65: External Batch Booking Notification ISR (10) IS (11) ISQ (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 April /78

58 ISR (10) IS (11) ISQ (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 <CrdtRefInf><Ref> </Ref></CrdtRefInf> Amount, address data etc. To be defined. 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 April /78

59 ISR (10) IS (11) ISQ (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 Invoice RmtInf (EndToEndId) Statement/Advice E2E: EndToEndId/RmtInf What References Are There? 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: The EndtoEndId is often unknown to the creditor, so the RmtInf is important for his reconciliation 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, 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 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: pacs.008 EndToEndId/RmtInf April /78

60 ISR (10) IS (11) ISQ (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. April /78