Swiss Usage Guide for ISO Messages according to the Swiss Recommendations

Transcription

1 Swiss Usage Guide for ISO Messages according to the Swiss Recommendations ustomer redit Transfer Initiation (pain.001) ustomer Payment Status Report (pain.002) ank-to-ustomer Statement (camt.053) Version

2 General notes Swiss Usage Guide General notes SIX reserves the right to modify this document, as the need arises, at any time without prior notice. lthough great care has been taken in the compilation and preparation of this work to ensure accuracy, errors and omissions cannot be entirely ruled out. SIX cannot be held liable for any decision made or action taken in reliance on the information in this document or for any consequential, special or similar damages. If you detect any errors in this document or have any ideas or suggestions for improvements we would be extremely grateful if you would notify these by to hange of name from " number" ( No.) to "Institutional identification" (II) The concept of the number, short for ank learing Number, has been out-of-date since at least 2010, when the Swiss National ank provided access to the SI system also to participants without the status of a bank, such as insurance companies. Furthermore, this number is used not only for the clearing of payments, but also for information that goes beyond the various payment traffic infrastructures. One example is the function of the number as part of the IN, a form of bank account number that can be used for many purposes. This is why the Swiss Recommendations will in future use "II" (institutional identification) instead of " no.". opyright 2016 SIX Interbank learing Ltd, H-8021 Zurich Page 2 of 63 Version

3 Swiss Usage Guide bout this document bout this document ocument Target audience The "Swiss Usage Guide" is intended primarily for smaller software developers of standard and customised solutions for payment traffic based on the ISO message standard, and also for customer advisers at financial institutions. The table below shows it in the context of the other documents and aids that are available to help with the use of ISO messages in accordance with the Swiss Recommendations. Target group for the document or working aid or working aid Smaller software developers ustomer advisers at financial institutions Swiss Usage Guide Swiss usiness Rules Swiss Implementation Guidelines ustomer-bank validation portal Larger software developers and IT managers at financial institutions x x (x) (x) (x) x (x) x x x Purpose The "Swiss Usage Guide" uses field rules and examples of the most common use cases (payment types) to explain how ISO messages (customer-to-bank and bank-to-customer) should be structured according to the Swiss Recommendations, and in this way provides an end-to-end overview of the whole process. Together with the documents listed below, it will enable the target group to program the relevant software and test it on the SIX customer-bank validation portal, and also to support the customers of financial institutions with programming. ssociated documents More detailed information supplementing the "Swiss Usage Guide" can be found in the following documents: Swiss usiness Rules: This document describes the requirements of business representatives of users, financial institutions and software providers, from the point of view of processes. It discusses the following subjects: efinition and description of specific business transactions, describing the relevant parties and the messages that are used (types of payments, versions of reports) Summary of message structures with more detail about certain structural elements escription of the main validation rules and ways of handling errors Version Page 3 of 63

4 bout this document Swiss Usage Guide Swiss Implementation Guidelines for redit Transfer: This document serves as manual for the technical implementation of the standard and provides assistance in producing the ISO message "pain.001" (detailed description of its XML structure and validation rules). Swiss Implementation Guidelines for Status Report: This document serves as manual for the technical implementation of the standard and provides assistance in producing the ISO message "pain.002" (detailed description of its XML structure and validation rules). Swiss Implementation Guidelines for ash Management messages: This document serves as manual for the technical implementation of the standard and provides assistance in producing the ISO messages "camt.052", "camt.053" and "camt.054" (detailled description of their XML structures and validation rules). Scope The ISO message "pain.008" for SEP direct debit procedures and the Swiss direct debit procedure are not discussed in this "Swiss Usage Guide". mendment control ll the amendments carried out on this document are listed in an amendment record table showing the version, the date of the amendment, a brief amendment description and a statement of the sections concerned. Page 4 of 63 Version

5 Swiss Usage Guide mendment control mendment control ll the amendments carried out on this document are listed below, with the version, the date of the amendment, a brief amendment description and a statement of the sections concerned. Version ate mendment description Section(s) First edition all Information about "camt.053" XML schema removed and noted that there are no plans for an XML schema specifically for the Swiss standard for "camt" messages Title page and colour scheme for tables and illustrations amended to comply with the new rand Identity Guidelines. Explanation of the change from no. to II added to the general notes. In Level of "pain.001" for ISR payments (payment type 1) "reditor/name" inserted. In Level of "camt.053" for ISR payments (payment type 1) "Related Parties/reditor/Name" inserted. ppendix all Foreword redit advice with structured reference "camt.054" inserted ccount statement message "camt.053" inserted New examples for "camt.053" specified. ppendix Version Page 5 of 63

6 Table of contents Swiss Usage Guide Table of contents 1 Overview Messages and message flows ore elements of a credit transfer instruction onventions for presentation Message descriptions ustomer redit Transfer Initiation (pain.001) ustomer Payment Status Report (pain.002) ank-to-ustomer Statement (camt.053) Use cases (payment types) ISR payment to a financial institution in Switzerland escription of the use case "pain.001" credit transfer message "pain.002" status message "camt.053" account statement message redit advice with structured reference "camt.054" IS payment to PostFinance escription of the use case "pain.001" credit transfer message "pain.002" status message "camt.053" account statement message IS payment to a financial institution in Switzerland escription of the use case "pain.001" credit transfer message "pain.002" status message "camt.053" account statement message ank payment to a financial institution in Switzerland escription of the use case "pain.001" credit transfer message "pain.002" status message "camt.053" account statement message Salary payment to a financial institution in Switzerland escription of the use case "pain.001" credit transfer message "pain.002" status message "camt.053" account statement message SEP credit transfer to a financial institution abroad escription of the use case "pain.001" credit transfer message "pain.002" status message "camt.053" account statement message ppendix : Message element descriptions Elements of the "pain.001" message in the version with minimal content Elements of the "pain.002" message Elements of the "camt.053" message Page 6 of 63 Version

7 Swiss Usage Guide Table of contents ppendix : Variations of the "pain.002" status message OK case OK case with warning NOK case ppendix : Payment status during processing ppendix : XML schemas and examples ppendix E: Glossary and list of abbreviations ppendix F: Table of figures Version Page 7 of 63

8 Overview Swiss Usage Guide 1 Overview 1.1 Messages and message flows The following diagram shows the parties involved and the message flows relating to credit transfer orders under ISO ebtor reditor 1. ustomer redit Transfer Initiation (pain.001) 2. Payment Status Report (pain.002) ebit/redit Notification (camt.054) ccount Report (camt.052) 4. Statement (camt.053) ebit/redit Notification (camt.054) ccount Report (camt.052) 4. Statement (camt.053) ebtor gent 3. Interbank Messages (pacs.nnn) via RTGS platform reditor gent Figure 1: Payment orders and ash Management (Reporting) under ISO Note: Messages that are not discussed in this document are shown in grey on the diagram. These include interbank messages (pacs.nnn) sent between financial institutions, advice messages about intraday account movements (camt.052) and debit/credit advice messages (camt.054), which not all financial institutions offer their customers. Parties such as the ultimate debtor and ultimate creditor, who are not involved in the ISO message flow, are not shown, nor are other information flows such as the sending of an inpayment slip from the creditor to the debtor. Procedure 1. The debtor sends a "pain.001" credit transfer message containing the information required for that use case (payment type) to his debtor agent. 2. The debtor agent validates the message that is received and sends the debtor the result of the validation in a "pain.002" status message. 3. If the validation result is positive, the debtor agent carries out the transfer to the creditor agent. 4. In accordance with the practice of their respective institutions, the debtor agent sends the debtor, and the creditor agent sends the creditor, a "camt.053" account statement, showing the debit or credit resulting from the transfer. Page 8 of 63 Version

9 Swiss Usage Guide Overview 1.2 ore elements of a credit transfer instruction The following core elements should normally be included in credit transfer instructions using ISO according to the Swiss Recommendations: etails about the debtor: ebtor s last name/first name and address ebtor s account number ebtor s financial institution (debtor agent) etails about the creditor: reditor s last name/first name and address reditor s account number reditor s financial institution (creditor agent) etails about the transfer: Payment amount Payment currency ate of execution harges information Reference number, notification to the creditor Notification to the debtor agent Notification to the creditor agent In general or depending on the payment type, some of this information may be mandatory (e.g. date of execution), optional (e.g. last name/first name, address of creditor), unnecessary (e.g. charges information) or not permitted (e.g. notification to the debtor or creditor agent). epending on the payment type, some information may have to be in a particular format, e.g. the account number as IN. In addition to these core elements, ISO credit transfer messages contain various control elements such as the message reference, time of creation, number of transactions in the message, check sum, message sender, payment method, payment type, booking instruction etc. which are not directly related to the credit transfer. In the tables of message descriptions in this document, the core elements and the control elements are listed in separate columns to distinguish clearly between them. Version Page 9 of 63

10 Overview Swiss Usage Guide 1.3 onventions for presentation In this document, the following conventions apply to presentation. esignation of XML elements In some publications, the names of XML elements are written as a single concept with no spaces, for example "redittransfertransactioninformation". In the interests of legibility, spaces are generally inserted in this document between the separate words i.e. "redit Transfer Transaction Information". Representation of the tree structure So that it is possible to tell where in the tree structure an element comes, the hierarchy level is indicated by preceding "+" signs in the element designation. For example, the IN in the "Payment Information" is shown as follows: Payment Information +ebtor ccount ++Identification +++IN In the tables, the root element (here "Payment Information") is only shown once and subsequently omitted. nother type of presentation that is used (mainly in free text) shows the subordinate sub-elements separated by "/". The IN shown above is then given as "Payment Information/ebtor ccount/identification/in". olor coding of different levels in the tables In the tables, each level is shown in a different color (-Level = marine, -Level = horizon, -Level = light horizon, -Level = light grey). The headings for the level tables are shown in a somewhat darker shade of the color for that level and the text is in bold. Name of the -Level Element of the -Level Name of the -Level Element of the -Level Name of the -Level Element of the -Level Name of the -Level Element of the -Level Page 10 of 63 Version

11 Swiss Usage Guide Overview Presentation conventions for amount fields In the XML context, different types of presentation are permitted in amount fields. To ensure smooth processing of credit transfers, the following presentation is recommended: o not use leading or closing filler characters (space, white space, zero, plus sign). lways use a decimal separator (point). Include decimal places even for whole-digit amounts (the number of decimal places depends on the currency). Some financial institutions may define additional restrictions as required. Regardless of the presentation format used, financial institutions are allowed to convert all amount fields into a unique presentation format for further processing. Version Page 11 of 63

12 Message descriptions Swiss Usage Guide 2 Message descriptions 2.1 ustomer redit Transfer Initiation (pain.001) The "ustomer redit Transfer Initiation" credit transfer message (pain.001) is used for the electronic commissioning of credit transfer orders by customers to the instructing financial institution. "pain.001" message structure ocument (Message) -Level Group Header (1..1) -Level Payment Information (1..n) -Level redit Transfer Transaction Information (1..n) The "pain.001" message is essentially structured as follows: -Level: message level, "Group Header". This block must occur exactly once. -Level: payment group level, "Payment Information". This block must occur at least once and generally comprises several -levels. -Level: transaction level, "redit Transfer Transaction Information". This block must occur at least once for each -level. It comprises all the -levels (transactions) belonging to the -level. Figure 2: "pain.001" message structure Note: In the examples of the "pain.001" message shown in this document, only one - Level with a single -Level is used, in the interests of clarity. escription of the elements in the "pain.001" message In this document, a version of the "pain.001" message with minimal content is used that is designed to help with implementing "best practices" and is therefore confined to the main elements (primarily those which are mandatory). The elements of this version of the "pain.001" message are described in ppendix 1. detailed description of the "pain.001" message can be found in the document "Swiss Implementation Guidelines for redit Transfer and Status Report". Of course, users are free to make full use of the other options for ISO messages that are documented there in their own software solutions. Page 12 of 63 Version

13 Swiss Usage Guide Message descriptions 2.2 ustomer Payment Status Report (pain.002) The "ustomer Payment Status Report" status message (pain.002) is used by the financial institution to inform customers about the status of "pain.001" credit transfer orders that have been sent. "pain.002" message structure ocument (Message) -Level Group Header (1..1) -Level Original Group Information nd Status (1..1) -Level Original Payment Information nd Status (0..n) -Level Transaction Information nd Status (0..n) The "pain.002" message is essentially structured as follows: -Level: message level, "Group Header". This block must occur exactly once. -Level: information about the original message level, "Original Group Information nd Status". This block is present exactly once. -Level: Information about the original payment group information, "Original Payment Information nd Status". This block can be present up to n times. -Level: Information about the original transaction, "Transaction Information nd Status". Figure 3: "pain.002" message structure escription of the elements in the "pain.002" message ppendix 2 provides a description of the elements in the "pain.002" message that is sent back by the debtor agent where the credit transfer message "pain.001" with minimal content shown in ppendix 1 was used. Version Page 13 of 63

14 Message descriptions Swiss Usage Guide 2.3 ank-to-ustomer Statement (camt.053) The "ank-to-ustomer Statement" message (camt.053) is used by financial institutions for providing electronic account information to their customers. "camt.053" message structure ocument (Message) -Level Group Header (1..1) -Level ccount Statement (1..n) -Level Statement Entry (0..n) The "camt.053" message is structured as follows: -Level: message level, "Group Header" -Level: account level, "ccount Statement" -Level: amount level, "Statement Entry" -Level: amount details, "Transaction etails" -Level Transaction etails (0..n) Figure 4: "camt.053" message structure escription of the elements in the "camt.053" message ppendix 3 provides a description of the elements in the "camt.053" message that is sent by the debtor agent to the debtor and by the creditor agent to the creditor in accordance with the practice at those institutions where the credit transfer message "pain.001" with minimal content shown in ppendix 1 was used. Page 14 of 63 Version

15 Swiss Usage Guide Use cases (payment types) 3 Use cases (payment types) This version of the "Swiss Usage Guide" confines itself to discussing the following frequently occurring use cases (payment types) which are described in detail in the "Swiss usiness Rules" and the "Swiss Implementation Guidelines for redit Transfer and Status Report": ISR payment to a financial institution in Switzerland (payment type 1) IS payment to PostFinance (payment type 2.1) IS payment to a financial institution in Switzerland (payment type 2.2) ank payment to a financial institution in Switzerland (payment type 3) Salary payment to a financial institution in Switzerland (variation of payment type 3) SEP credit transfer to a financial institution abroad (payment type 5) Each of these use cases is described below in a separate sub-section. In the tables of message descriptions for these use cases, the specific data relating to the underlying example is shown, but variable information such as references, date/time of production, required date of execution etc. are shown generically. The various use cases are based on a version of the "pain.001" credit transfer message with minimal content, as defined in ppendix 1. Version Page 15 of 63

16 Use cases (payment types) Payment type 1 Swiss Usage Guide 3.1 ISR payment to a financial institution in Switzerland escription of the use case In this use case, an invoice is being paid using an orange inpayment slip with reference number (ISR) sent by the creditor to the debtor. This use case equates to payment type 1 "ISR payment". ebtor Orange inpayment slip with reference number (ISR) reditor ustomer redit Transfer Initiation (pain.001) Payment Status Report (pain.002) Statement (camt.053) Statement (camt.053) ebtor gent Interbank Messages (pacs.nnn) via RTGS platform reditor gent Figure 5: Message flows for an ISR payment to a financial institution in Switzerland The credit transfer is to be made from the debtor s account number (IN = H ) at the Raiffeisenbank Seldwyla (I = RIFH22). Figure 6 below shows which information on the ISR should be used for the payment message. The content of the "pain.001", "pain.002" and "camt.053" messages for this use case are described in sub-sections 3.1.2, and Page 16 of 63 Version

17 Swiss Usage Guide Payment type 1 Use cases (payment types) etrag Referenznummer TN-Nr. = = = Figure 6: Orange inpayment slip with reference number (ISR) ebtor s last name/first name and address (last name/first name to be given in the "pain.001", -Level: Payment Information/ebtor/Name, entering the address is not recommended) 9-digit ISR party number (to be given in the "pain.001", -Level: redit Transfer Transaction Information/ reditor ccount/identification/other/identification) Reference number (to be given in the "pain.001", -Level: redit Transfer Transaction Information/ Remittance Information/Structured/reditor Reference Information/Reference) Payment amount (to be given in the "pain.001", -Level: redit Transfer Transaction Information/ mount/instructed mount) The orange inpayment slip used in this use case is a 1-stage voucher in favour of the direct beneficiary s postal account in HF. Version Page 17 of 63

18 Use cases (payment types) Payment type 1 Swiss Usage Guide "pain.001" credit transfer message For ISR payments (payment type 1), the debtor s software must be able to produce a "pain.001" credit transfer message containing the following elements: Level Element Information contained in the element 1 Group Header ore element ontrol element +Message Identification Message reference +reation ate Time reation date/time +Number Of Transactions 1 +ontrol Sum Initiating Party ++Name Payment Information RUTSHMNN PI +Payment Information Identification Payment group reference +Payment Method TRF +atch ooking true +Requested Execution ate Requested execution date +ebtor ++Name +ebtor ccount ++Identification +++IN +ebtor gent ++Financial Institution Identification +++I redit Transfer Transaction Information +Payment Identification ++Instruction Identification +Payment Identification ++End To End Identification +Payment Type Information ++Local Instrument +++Proprietary +mount ++Instructed mount +reditor ++Name +reditor ccount ++Identification +++Other ++++Identification +Remittance Information ++Structured +++reditor Reference Information ++++Reference RUTSHMNN PI H RIFH22 HF Robert Schneider S Transaction reference End to end reference H01 1 Specific data in accordance with the underlying example and generic data for variable information such as references, creation date/time, requested execution date etc. General information about the content of elements in the "pain.001" message can be found in ppendix 1. Page 18 of 63 Version

19 Swiss Usage Guide Payment type 1 Use cases (payment types) "pain.002" status message Once technical and business validation of the "pain.001" credit transfer message that has been received has been carried out, the debtor s software receives a "pain.002" status message sent back by the debtor agent. If the validation was successful in all respects (OK case) then the "pain.002" status message has the following content: Level Element Information contained in the element 2 ore element ontrol element Group Header +Message Identification Message reference +reation ate Time reation date/time +Initiating Party ++Identification +++Organisation Identification ++++I Or EI Original Group Information nd Status RIFH22 +Original Message Identification Message reference of the original "pain.001" message +Original Message Name Ident. pain Group Status P The variations for the "pain.002" status message in cases where validation was not successful in all respects are described in ppendix ppendix. 2 Specific data in accordance with the underlying example and generic data for variable information such as references, creation date/time etc. General information about the content of elements in the "pain.001" message can be found in ppendix 2. Version Page 19 of 63

20 Use cases (payment types) Payment type 1 Swiss Usage Guide "camt.053" account statement message The debtor s software receives from the debtor agent, in accordance with the practice of that financial institution, a "camt.053" account statement message with the following content: Level Element Information contained in the element 3 ore element ontrol element Group Header +Message Identification Message reference +reation ate Time reation date/time of the message +Message Pagination ++Page Number +Message Pagination ++Last Page Indicator Statement 1 true +Identification Unique statement reference +Electronic Sequence Number Sequential number for the year +reation ate Time ate/time of statement creation +ccount ++Identification +++IN alance ++Type +++ode or Proprietary ++++ode +alance ++mount +alance ++ebit redit Indicator +alance ++ate +++ate alance ++Type +++ode or Proprietary ++++ode +alance ++mount +alance ++ebit redit Indicator +alance ++ate +++ate H OP mount and currency of the initial balance ebit or credit balance indicator ate of the initial balance LV mount and currency of the balance on the settlement date ebit or credit balance indicator ate of the balance on the settlement date 3 Specific data in accordance with the underlying example and generic data for variable information such as references, creation date/time, balance data etc. General information about the content of elements in the "camt.053" message can be found in ppendix 3. Page 20 of 63 Version

21 Swiss Usage Guide Payment type 1 Use cases (payment types) Level Element Information contained in the element 3 ore element ontrol element Entry +NtryRef ISR participant number +mount HF ebit redit Indicator IT +Status OOK +ooking ate ++ate +Value ate ++ate +ank Transaction ode ++omain +++ode ank Transaction ode ++omain +++Family ++++ode +ank Transaction ode ++omain +++Family ++++Sub Family ode Transaction etails ooking date Value date PMNT IT VOM +References ++End To End Identification End to end reference of the original "pain.001" message +mount etails ++Instructed mount +++mount +Related Parties ++reditor +++Name +Remittance Information ++Structured +++reditor Reference Information ++++Reference HF Robert Schneider S Version Page 21 of 63

22 Use cases (payment types) Payment type 1 Swiss Usage Guide redit advice with structured reference "camt.054" The debtor s software receives from the debtor agent, in accordance with the practice of that financial institution, a "camt.054" credit advice (Version.04, ISO Release 2013) with the following content: Level Element Information contained in the element 4 ore element ontrol element Group Header +Message Identification Message reference +reation ate Time reation date/time of the message +Message Pagination ++Page Number +Message Pagination ++Last Page Indicator Notification 1 true +Identification Unique statement reference +reation ate Time ate/time of statement creation +ccount ++Identification +++IN H redit account Entry +NtryRef ISR participant number +mount HF ebit redit Indicator RT +Status OOK +ooking ate ++ate +Value ate ++ate +ank Transaction ode ++omain +++ode ank Transaction ode ++omain +++Family ++++ode +ank Transaction ode ++omain +++Family ++++Sub Family ode +Entry etails ++atch +++Number of Transactions ooking date Value date PMNT RT VOM 1 Number of transactions (-Level) of the corresponding booking (-Level) 4 Specific data in accordance with the underlying example and generic data for variable information such as references, creation date/time, balance data etc. General information about the content of elements in the "camt.053" message can be found in ppendix 3. Page 22 of 63 Version

23 Swiss Usage Guide Payment type 1 Use cases (payment types) Level Element Information contained in the element 4 ore element ontrol element Transaction etails +References ++End To End Identification End to end reference of the original "pain.001" message +mount HF mount and currency of the individual transaction. +redit ebit Indication RT redit +mount etails ++Transaction mount +++mount HF mount and currency of the transaction. +Related Parties ++ ebtor +++Name Pia Rutschmann +Related Parties ++ebtor +++Postalddress ++++StreetName Marktgasse optional +Related Parties ++ebtor +++Postalddress ++++uildingnumber +Related Parties ++ebtor +++Postalddress ++++Postode 28 optional 9400 optional +Related Parties ++ebtor +++Postalddress ++++TownName Rorschach optional +Remittance Information ++Structured +++reditor Reference Information ++++Reference Version Page 23 of 63

24 Use cases (payment types) Payment type 2.1 Swiss Usage Guide 3.2 IS payment to PostFinance escription of the use case In this use case, an invoice that has been sent by the creditor to the debtor is being settled using a red inpayment slip (IS) in favor of a postal account. This use case equates to payment type 2.1 "IS payment, 1-stage". ebtor red 1-stage inpayment slip (ES) in favor of PostFinance reditor ustomer redit Transfer Initiation (pain.001) Payment Status Report (pain.002) Statement (camt.053) Statement (camt.053) ebtor gent Interbank Messages (pacs.nnn) via RTGS platform PostFinance = reditor gent Figure 7: Message flows for an IS payment to PostFinance The transfer is to be made from the debtor s account number (IN = H ) at Sparkasse Seldwyla (II = 8307). Figure 8 below shows which information on the IS should be used for the payment message. The content of the "pain.001", "pain.002" and "camt.053" messages for this use case are described in sub-sections 3.2.2, and Page 24 of 63 Version

25 Swiss Usage Guide Payment type 2.1 Use cases (payment types) Figure 8: Red 1-stage inpayment slip (IS) in favor of PostFinance Notification to the creditor (to be given in the "pain.001", -Level: redit Transfer Transaction Information/ Remittance Information/Unstructured) reditor s last name/first name and address (to be given in the "pain.001", -Level: redit Transfer Transaction Information/ reditor/name and redit Transfer Transaction Information/reditor/Postal ddress) reditor s account number (to be given in the "pain.001", -Level: redit Transfer Transaction Information/ reditor ccount/identification/other/identification) Payment amount (to be given in the "pain.001", -Level: redit Transfer Transaction Information/ mount/instructed mount) ebtor s last name/first name and address (last name/first name to be given in the "pain.001", -Level: Payment Information/ebtor/Name, entering the address is not recommended) Version Page 25 of 63

26 Use cases (payment types) Payment type 2.1 Swiss Usage Guide "pain.001" credit transfer message For IS payments to PostFinance (payment type 2.1), the debtor s software must be able to produce a "pain.001" credit transfer message containing the following elements: Level Element Information contained in the element 5 ore element ontrol element Group Header +Message Identification Message reference +reation ate Time reation date/time +Number Of Transactions 1 +ontrol Sum Initiating Party ++Name Payment Information LEHMNN ORIS +Payment Information Identification Payment group reference +Payment Method TRF +atch ooking true +Requested Execution ate Requested execution date +ebtor ++Name +ebtor ccount ++Identification +++IN LEHMNN ORIS H ebtor gent ++Financial Institution Identification +++learing System Member Ident. ++++learing System Identification +++++ode +ebtor gent ++Financial Institution Identification +++learing System Member Ident. ++++Member Identification redit Transfer Transaction Information +Payment Identification ++Instruction Identification +Payment Identification ++End To End Identification +Payment Type Information ++Local Instrument +++Proprietary +mount ++Instructed mount +reditor ++Name H 8307 HF Robert Schneider S Transaction reference End to end reference H02 5 Specific data in accordance with the underlying example and generic data for variable information such as references, creation date/time, requested execution date etc. General information about the content of elements in the "pain.001" message can be found in ppendix 1. Page 26 of 63 Version

27 Swiss Usage Guide Payment type 2.1 Use cases (payment types) Level Element Information contained in the element 5 +reditor ++Postal dress +++Street Name +reditor ++Postal dress +++Post ode +reditor ++Postal dress +++Town Name +reditor ++Postal dress +++ountry +reditor ccount ++Identification +++Other ++++Identification +Remittance Information ++Unstructured ore element ase postale 2501 iel/ienne H Rechnung Nr. 408 ontrol element "pain.002" status message Once technical and business validation of the "pain.001" credit transfer message that has been received has been carried out, the debtor s software receives a "pain.002" status message sent back by the debtor agent. The information in section also applies to this use case "camt.053" account statement message The debtor s software receives from the debtor agent, in accordance with the practice of that financial institution, a "camt.053" account statement message. The information in section also applies to this use case with the following exception: the SubFamily code of the business case code (<Entry/ank Transaction ode/omain/family/sub Family ode> element) for IS payments is "MT". Version Page 27 of 63

28 Use cases (payment types) Payment type 2.2 Swiss Usage Guide 3.3 IS payment to a financial institution in Switzerland escription of the use case In this use case, an invoice that has been sent to the debtor by the creditor is being settled with a red inpayment slip in favor of a bank account. This use case equates to payment type 2.2 "IS payment, 2-stage". ebtor red 2-stage inpayment slip (IS) in favor of a bank reditor ustomer redit Transfer Initiation (pain.001) Payment Status Report (pain.002) Statement (camt.053) Statement (camt.053) ebtor gent Interbank Messages (pacs.nnn) via RTGS platform reditor gent Figure 9: Message flows for an IS payment to a financial institution in Switzerland The transfer is to be made from the debtor s account number (IN = H ) at redit Suisse hur (II = 4835). Figure 10 below shows which information on the IS should be used for the payment message. The content of the "pain.001", "pain.002" and "camt.053" messages for this use case are described in sub-sections 3.2.2, and Page 28 of 63 Version

29 Swiss Usage Guide Payment type 2.2 Use cases (payment types) Max eispieler ahnhofstrasse hur Figure 10: Red 2-stage inpayment slip (IS) in favor of a bank ebtor s last name/first name and address (last name/first name to be given in the "pain.001", -Level: Payment Information/ebtor/Name, entering the address is not recommended) reditor s account number (to be given in the "pain.001", -Level: redit Transfer Transaction Information/ reditor ccount/identification/in) reditor s last name/first name and address (to be given in the "pain.001", -Level: redit Transfer Transaction Information/ reditor/name and redit Transfer Transaction Information/reditor/Postal ddress) Notification to the creditor (to be given in the "pain.001", -Level: redit Transfer Transaction Information/ Remittance Information/Unstructured) Payment amount (to be given in the "pain.001", -Level: redit Transfer Transaction Information/ mount/instructed mount) Post account number of the creditor agent (to be given in the "pain.001", -Level: redit Transfer Transaction Information/ reditor gent/financial Institution Identification/Other/Identification) Reference number (to be given in the "pain.001", -Level: redit Transfer Transaction Information/ Remittance Information/Unstructured) onstant "07" plus II of the creditor agent (to be given in the "pain.001", -Level: redit Transfer Transaction Information/ Remittance Information/Structured/reditor Reference Information/Reference) Version Page 29 of 63

30 Use cases (payment types) Payment type 2.2 Swiss Usage Guide "pain.001" credit transfer message For IS payments to a financial institution in Switzerland (payment type 2.2), the debtor s software must be able to produce a "pain.001" credit transfer message containing the following elements: Level Element Information contained in the element 6 ore element ontrol element Group Header +Message Identification Message reference +reation ate Time reation date/time +Number Of Transactions 1 +ontrol Sum Initiating Party ++Name Payment Information MX EISPIELER +Payment Information Identification Payment group reference +Payment Method TRF +atch ooking true +Requested Execution ate Requested execution date +ebtor ++Name MX EISPIELER +ebtor ccount ++Identification +++IN +ebtor gent ++Financial Institution Identification +++learing System Member Ident. ++++learing System Identification +++++ode +ebtor gent ++Financial Institution Identification +++learing System Member Ident. ++++Member Identification redit Transfer Transaction Information +Payment Identification ++Instruction Identification +Payment Identification ++End To End Identification +Payment Type Information ++Local Instrument +++Proprietary +mount ++Instructed mount H H 4835 HF Transaction reference End to end reference H03 6 Specific data in accordance with the underlying example and generic data for variable information such as references, creation date/time, requested execution date etc. General information about the content of elements in the "pain.001" message can be found in ppendix 1. Page 30 of 63 Version

31 Swiss Usage Guide Payment type 2.2 Use cases (payment types) Level Element Information contained in the element 6 +reditor gent ++Financial Institution Identification +++Name +reditor gent ++Financial Institution Identification +++Other ++++Identification +reditor ++Name +reditor ++Postal dress +++Street Name +reditor ++Postal dress +++uilding Number +reditor ++Postal dress +++Post ode +reditor ++Postal dress +++Town Name +reditor ++Postal dress +++ountry +reditor ccount ++Identification +++IN +Remittance Information ++Unstructured ore element SELWYL NK MUSTER G HNHOFSTRSSE ZUERIH H H Rechnung Nr ontrol element "pain.002" status message Once technical and business validation of the "pain.001" credit transfer message that has been received has been carried out, the debtor s software receives a "pain.002" status message sent back by the debtor agent. The information in section also applies to this use case "camt.053" account statement message The debtor s software receives from the debtor agent, in accordance with the practice of that financial institution, a "camt.053" account statement message. The information in section also applies to this use case with the following exception: the SubFamily code of the business case code (<Entry/ank Transaction ode/omain/family/sub Family ode> element) for IS payments is "MT". Version Page 31 of 63

32 Use cases (payment types) Payment type 3 Swiss Usage Guide 3.4 ank payment to a financial institution in Switzerland escription of the use case In this use case, the debtor Erich Müller, Rosenweg 6, 3110 Münsingen is paying a sum of HF 200 that is owing on behalf of his under-age son Fritz (ultimate debtor), who does not have a bank account, from his own bank account to Kurt Meyerhans (ultimate creditor), who attends Sports ollege at the High lpine Institute Ftan (creditor). This use case equates to payment type 3. Ultimate ebtor Ultimate reditor HF 200 in cash HF 200 in cash ebtor reditor ustomer redit Transfer Initiation (pain.001) Payment Status Report (pain.002) Statement (camt.053) Statement (camt.053) ebtor gent Interbank Messages (pacs.nnn) via RTGS platform reditor gent Figure 11: Message flows for a bank payment to a financial institution in Switzerland The transfer is to be made from the debtor s account number X (IN = H X ) at US G Münsingen (II = 235) to account number (IN = H ) at the Graubündner Kantonalbank in Scuol (I = GRKH2270). Note: The <Ultmtdtr> (ultimate creditor) element should only be used by agreement with the debtor agent. The content of the "pain.001", "pain.002" and "camt.053" messages for this use case are described in sub-sections 3.4.2, and Page 32 of 63 Version

33 Swiss Usage Guide Payment type 3 Use cases (payment types) "pain.001" credit transfer message For bank payments to a financial institution in Switzerland (payment type 3) the debtor s software must be able to produce a "pain.001" credit transfer message containing the following elements: Level Element Information contained in the element 7 ore element ontrol element Group Header +Message Identification Message reference +reation ate Time reation date/time +Number Of Transactions 1 +ontrol Sum Initiating Party ++Name Payment Information MUELLER ERIH +Payment Information Identification Payment group reference +Payment Method TRF +atch ooking true +Requested Execution ate Requested execution date +ebtor ++Name +ebtor ccount ++Identification +++IN +ebtor gent ++Financial Institution Identification +++learing System Member Ident. ++++learing System Identification +++++ode +ebtor gent ++Financial Institution Identification +++learing System Member Ident. ++++Member Identification +Ultimate ebtor ++Name +Ultimate ebtor ++Postal ddress +++Street Name +Ultimate ebtor ++Postal ddress +++uilding Number +Ultimate ebtor ++Postal ddress +++Post ode MUELLER ERIH H X H 235 FRITZ MUELLER ROSENWEG Specific data in accordance with the underlying example and generic data for variable information such as references, creation date/time, requested execution date etc. General information about the content of elements in the "pain.001" message can be found in ppendix 1. Version Page 33 of 63

34 Use cases (payment types) Payment type 3 Swiss Usage Guide Level Element Information contained in the element 7 ore element ontrol element +Ultimate ebtor ++Postal ddress +++Town Name redit Transfer Transaction Information MUENSINGEN +Payment Identification ++Instruction Identification +Payment Identification ++End To End Identification Transaction reference End to end reference +mount ++Instructed mount +reditor gent ++Financial Institution Identification +++I +reditor ++Name +reditor ++Postal dress +++Street Name +reditor ++Postal dress +++uilding Number +reditor ++Postal dress +++Post ode +reditor ++Postal dress +++Town Name +reditor ++Postal dress +++ountry +reditor ccount ++Identification +++IN +Ultimate reditor ++Name +Remittance Information ++Unstructured HF GRKH2270 HOHLPINES INSTITUT FTN WLWEG FTN H H KURT MEYERHNS Notification to the creditor "pain.002" status message Once technical and business validation of the "pain.001" credit transfer message that has been received has been carried out, the debtor s software receives a "pain.002" status message sent back by the debtor agent. The information in section also applies to this use case. Page 34 of 63 Version

35 Swiss Usage Guide Payment type 3 Use cases (payment types) "camt.053" account statement message The debtor s software receives from the debtor agent, in accordance with the practice of that financial institution, a "camt.053" account statement message with the following content: Level Element Information contained in the element 8 ore element ontrol element Group Header +Message Identification Message reference +reation ate Time reation date/time of the message +Message Pagination ++Page Number +Message Pagination ++Last Page Indicator Statement 1 true +Identification Unique statement reference +Electronic Sequence Number Sequential number for the year +reation ate Time ate/time of statement creation +ccount ++Identification +++IN alance ++Type +++ode or Proprietary ++++ode +alance ++mount +alance ++ebit redit Indicator +alance ++ate +++ate alance ++Type +++ode or Proprietary ++++ode +alance ++mount +alance ++ebit redit Indicator +alance ++ate +++ate H X OP mount and currency of the initial balance ebit or credit balance indicator ate of the initial balance LV mount and currency of the balance on the settlement date ebit or credit balance indicator ate of the balance on the settlement date 8 Specific data in accordance with the underlying example and generic data for variable information such as references, creation date/time, balance data etc. General information about the content of elements in the "camt.053" message can be found in ppendix 3. Version Page 35 of 63

36 Use cases (payment types) Payment type 3 Swiss Usage Guide Level Element Information contained in the element 8 ore element ontrol element Entry +mount HF ebit redit Indicator IT +Status OOK +ooking ate ++ate +Value ate ++ate +ank Transaction ode ++omain +++ode ank Transaction ode ++omain +++Family ++++ode +ank Transaction ode ++omain +++Family ++++Sub Family ode Transaction etails ooking date Value date PMNT IT MT +References ++End To End Identification End to end reference of the original "pain.001" message +mount etails ++Instructed mount +++mount +Remittance Information ++Unstructured HF Notification to the creditor Page 36 of 63 Version

37 Swiss Usage Guide Variation of payment type 3 Use cases (payment types) 3.5 Salary payment to a financial institution in Switzerland escription of the use case In this use case, the debtor company Muster G, ahnhofstrasse 5, 8001 Zurich is paying its employee Hans Meier, Langstrasse 120, 8004 Zurich, his monthly salary of HF from the company account into his salary account. This use case equates to the "Salary Payment" variation of payment type 3. ebtor reditor ustomer redit Transfer Initiation (pain.001) Payment Status Report (pain.002) Statement (camt.053) Statement (camt.053) ebtor gent Interbank Messages (pacs.nnn) via RTGS platform reditor gent Figure 12: Message flows for a salary payment to a financial institution in Switzerland The transfer is to be made from the debtor s account number (IN = H ) at Raiffeisenbank Seldwyla (I = RIFH22) to the salary account (IN = H ) at the Zürcher Kantonalbank (II = 700). Unlike with a "normal" payment of payment type 3, for the "Salary Payment" variation, the following additional elements should be used: 1. Payment Information/ategory Purpose/ode = "SL" to identify the purpose of the transfer as "Salary Payment" on the debit side. 2. Payment Information/ebtor ccount/type/proprietary = "N" for notification control as a collective advice with no details on the debit side. 3. redit Transfer Transaction Information/Purpose/ode = "SL" to identify the purpose of the transfer as "Salary Payment" on the credit side. The content of the "pain.001", "pain.002" and "camt.053" messages for this use case are described in sub-sections 3.5.2, and Version Page 37 of 63

38 Use cases (payment types) Variation of payment type 3 Swiss Usage Guide "pain.001" credit transfer message For salary payments to a financial institution in Switzerland (variation of payment type 3), the debtor s software must be able to produce a "pain.001" credit transfer message containing the following elements: Level Element Information contained in the element 9 ore element ontrol element Group Header +Message Identification Message reference +reation ate Time reation date/time +Number Of Transactions 1 +ontrol Sum Initiating Party ++Name Payment Information MUSTER G +Payment Information Identification Payment group reference +Payment Method TRF +atch ooking true +ategory Purpose ++ode SL +Requested Execution ate Requested execution date +ebtor ++Name +ebtor ccount ++Identification +++IN +ebtor ccount ++Type +++Proprietary +ebtor gent ++Financial Institution Identification +++I redit Transfer Transaction Information +Payment Identification ++Instruction Identification +Payment Identification ++End To End Identification +mount ++Instructed mount +reditor gent ++Financial Institution Identification +++learing System Member Ident. ++++learing System Identification +++++ode MUSTER G H N RIFH22 HF H Transaction reference End to end reference 9 Specific data in accordance with the underlying example and generic data for variable information such as references, creation date/time, requested execution date etc. General information about the content of elements in the "pain.001" message can be found in ppendix 1. Page 38 of 63 Version