Credit Suisse pain ch.02 - SIX v Swiss Recommendations for Credit Transfers Message Implementation Guidelines

Size: px
Start display at page:

Download "Credit Suisse pain ch.02 - SIX v Swiss Recommendations for Credit Transfers Message Implementation Guidelines"

Transcription

1 redit Suisse Version 2.0 Issue date: Ego vero valde afflictus sum redit Suisse pain ch.02 - SIX v Swiss Recommendations for redit Transfers Message Implementation Guidelines

2 Table of ontents 1. Notes on redit Suisse Message Implementation Guidelines onventions for presentation 3 2. Technical Specifications 4 redit Suisse pain SIX v Implementation Guidelines 2

3 1. Notes on redit Suisse Message Implementation Guidelines The redit Suisse Message Implementation Guidelines for redit Transfers serves as manual for the technical and business implementation of redit Transfers pain.001 message in accordance with the ISO Payments Standard and the Swiss Recommendations. All redit Transfer messages transmitted to redit Suisse must comply with Swiss Recommendations, ISO Payments Standard and redit Suisse specification (as adhered in this document and XSD). redit Suisse Message Implementation Guidelines Swiss Recommendations ISO Payments Standards Figure 1. above shows the degree of concordance between the ISO Payments Standards, Swiss Recommendations and redit Suisse Implementations. The document provides additional information to the redit Suisse XML schema definition (XSD) and cannot be read as a stand-alone specification onventions for presentation A basic knowledge of XML is assumed for the purposes of this document, so only certain special points are explained. The technical validation of the various XML messages is carried out using XML schema. In this document, the following conventions apply to presentation. Representation of the tree structure in the tables 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 Message Item. For example, the IAN in the Payment Information is represented as shown: {Or +++dtracct ++++Id +++++IAN Representation of choices Elements with a choice are marked in the XML Tag column as follows: {Or for start of the choice Or} for end of the choice The technical specifications contain information from ISO 20022, such as Name, Index, ardinality (Presence/ Multiplicity), Message Item, XML-Tag, ISODefinition (Definition).The following information for the Swiss ISO Payments Standard can also be found in the specifications: H Definition corresponding to Swiss Implementation Guidelines field General definition H Rules Definitions for specific payment types as per Swiss Recommendations definition redit Suisse redit Suisse remark. It includes additional explanation or/and redit Suisse specific rule description Rsnd and AddtlInf some XML elements are being provided with error example, that is code and the corresponding Additional Information, which are being sent in pain.002 Status Reason Information e.g. Rsnd: H16; Initiating Party Name may not exceed 70 characters Example redit Suisse example e.g. <Nm>Max Muster</Nm> H Status Information about usage in Switzerland. The following statuses are permitted for individual XML elements according to the Swiss Implementation Guidelines Version 1.7. M Mandatory The element is mandatory. If the element is not used, a Swiss bank will refuse to process the message. D ilaterally Determined The element may only be used by agreement with the instructed financial institution. O Optional The element is optional. D Dependent The use of the element depends on other elements. R Recommended The use of the element is recommended. Data Type The names of data types given in the tables of this document correspond to the data types defined in XML schemas e.g. ISODateTime Length in some cases min and max length is indicated e.g. Length: Errorode list of possible error codes that are being sent back in the ustomer Payment Status Report (pain.002) e.g. Errorode: H16, H17, H21 Note: If during schema validation an error is detected in any element, the whole message can be rejected (error code FF01). Since this response generally applies to all elements in the table, a comment to that effect is not entered for every element. The raws marked light grey indicate the XML elements containing at least one sub-element redit Suisse pain SIX v Implementation Guidelines 3

4 2. Technical Specifications Level Message Item A A A A A ardinality: GrpHdr ISO Index: 1.0 ardinality: 1..1 H Status: M +GrpHdr ++MsgId ISO Index: 1.1 Errorode: DU01, H21 ardinality: 1..1 H Status: M +GrpHdr ++redttm ISO Index: 1.2 Errorode: H21, FF01 ardinality: 1..1 H Status: M +GrpHdr ++NbOfTxs ISO Index: 1.6 Errorode: ardinality: 1..1 H Status: M AM18, FF01, H21 H Definition: ustomer redit Transfer Initiation V03 ustomerredittransferinitiationv03 The ustomerredittransferinitiation message is sent by the initiating party to the forwarding agent or debtor's agent. It is used to request movement of funds from debtor's account to a creditor. Group Header GrpHdr GroupHeader32 Set of characteristics shared by all individual transactions included in the message. Value must be unique within the whole message (is used as reference in the Status Report pain. 002). Only the SWIFT character set is permitted for this element. Message Identification MsgId Max35Text Point to point reference, as assigned by the instructing party, and sent to the next party in the chain to unambiguously identify the message. Usage: The instructing party has to make sure that MessageIdentification is unique per instructed party for a pre-agreed period. H Definition: hecking for duplicates usually takes place at the Swiss financial institutions at document (message) level. This is why the "Message Identification" <MsgId> element must have a unique value. The uniqueness is checked by most of the financial institutions over a period of at least 90 days. It is recommended that the "Message Identification" is generally kept unique for as long as possible. Only the SWIFT character set is permitted for this element. redit Suisse: If Message Identification is not unique the whole pain.001 would be rejected. Example: <MsgId>MSGID </MsgId> H Definition: redit Suisse: Rsnd: Example: reation Date Time redttm ISODateTime Date and time at which the message was created. Recommendation: Should be the same as the actual date/time of creation. If the date is invalid format, the whole file will be rejected with Status Reason ode FF01. H21 reation Date Time is mandatory <redttm> t00:00:00</redttm> Number Of Transactions NbOfTxs Max15NumericText Number of individual transactions contained in the message. H Definition: If there is an error, the whole message is rejected. Recommendation: at present, the customer is recommended not to send any messages (files) to the financial institution exceeding 99,999 payments (-Level, transactions). Pattern: [0-9]{1,15} redit Suisse: If the content of this element does not match the total number of -Levels the file will be rejected with Status Reason ode AM18. Rsnd: AM18 Number of transactions <x> does not match the calculated number of transactions <y> Rsnd: FF01 There is no transaction present in the message. Rsnd: H21 Number of transactions is mandatory. Example: <NbOfTxs>10</NbOfTxs> redit Suisse pain SIX v Implementation Guidelines 4

5 A A A A +GrpHdr ++trlsum ISO Index: 1.7 Errorode: AM10 H Status: R +GrpHdr ++InitgPty ISO Index: 1.8 Errorode: H21 ardinality: 1..1 H Status: M +GrpHdr ++InitgPty +++Nm ISO Index: 1.8 Errorode: H16 H Status: R ontrol Sum trlsum DecimalNumber Total of all individual amounts included in the message, irrespective of currencies. H Definition: Value is the same as the sum of all the "Amount elements" ("Instructed Amount" or "Equivalent Amount") Recommendation: the control sum should be sent in this element in Level A. If there is an error, the whole message is rejected. FractionDigits: 17 TotalDigits: 18 redit Suisse: It is recommended that the element is used at A-level. If element is delivered the content will be validated with the overall sum of all amounts of all subsequent single transactions (instructed as well as equivalent amounts). If stated control sum does not match with actual sum over all -Levels the whole pain.001 (A-Level) is rejected with Status Reason ode AM10. Rsnd: AM10 ontrol Sum <x> does not match the calculated sum of Amounts <y> Example: <trlsum> </trlsum> H Definition: Initiating Party InitgPty PartyIdentification32 Party that initiates the payment. Usage: This can either be the debtor or the party that initiates the credit transfer on behalf of the debtor. At least one of the two elements "Name" or "Identification" must be sent. Name Nm Max140Text Length: Name by which a party is known and which is usually used to identify that party. H Definition: Name of the message sender, maximum 70 characters. Rsnd: H16 Initiating Party Name must not exceed 70 characters. Example: <Nm>Max Muster</Nm> Identification +GrpHdr Id ++InitgPty Party6hoice +++Id Unique and unambiguous identification of a party. ISO Index: 1.8 H Definition: Identification of the message sender. H Status: R ardinality: 1..1 xs:choice A {Or +GrpHdr ++InitgPty +++Id ++++OrgId ISO Index: 1.8 Errorode: H16, H17 ardinality: 1..1 H Status: D A +GrpHdr ++InitgPty +++Id ++++OrgId +++++IOrEI ISO Index: 1.8 Errorode: R01 H Status: D H Definition: redit Suisse: H Definition: H PT Rules: Pattern: Rsnd: Organisation Identification OrgId OrganisationIdentification4 Unique and unambiguous way to identify an organisation. Only "I Or EI" or an element from "Other" permitted. If used, the "Private Identification" must not be present. omponent should only be used, if the initiating party has an own I or EI as other identification is ignored. IOr EI IOrEI AnyIIdentifier ode allocated to a financial institution or non financial institution by the ISO 9362 Registration Authority as described in ISO 9362 "anking - anking telecommunication messages - usiness identifier code (I)". If used, "Other" must not be present. Either I or EI or one occurrence of Other is allowed but not both together. [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}){0,1} R01 Initiating Party Id <x> doesn t contain a valid I or EI-value. redit Suisse pain SIX v Implementation Guidelines 5

6 A +GrpHdr ++InitgPty +++Id ++++OrgId +++++Othr ISO Index: 1.8 Errorode: H16 ardinality: 0..unbounded H Status: D A Or} +GrpHdr ++InitgPty +++Id ++++PrvtId ISO Index: 1.8 ardinality: 1..1 H Status: D A A A A +GrpHdr ++InitgPty +++tctdtls ISO Index: 1.8 H Status: R +GrpHdr ++InitgPty +++tctdtls ++++Nm ISO Index: 1.8 H Status: R +GrpHdr ++InitgPty +++tctdtls ++++Othr ISO Index: 1.8 H Status: R +GrpHdr ++FwdgAgt ISO Index: 1.9 H Status: D ISO Index: 2.0 Errorode: H21 ardinality: 1..unbounded H Status: M H Definition: redit Suisse: H Definition: redit Suisse: H Definition: redit Suisse: Other Othr GenericOrganisationIdentification1 Unique identification of an organisation, as assigned by an institution, using an identification scheme. If used, "I Or EI" must not be present. It will be ignored. However, when provided - it must conform with the scheme. Private Identification PrvtId PersonIdentification5 Unique and unambiguous identification of a person, eg, passport. Only "Date And Place Of irth" or an element from "Other" permitted. If used, "Organisation Identification" must not be present. It will be ignored. However, when provided - it must conform with the scheme. ontact Details tctdtls ontactdetails2 Set of elements used to indicate how to contact the party. Details of the software used and the particular version. It will be ignored. However, when provided - it must conform with the scheme. Name Nm Max140Text Length: Name by which a party is known and which is usually used to identify that party. H Definition: Recommendation: Should contain the name of the software used to create this message, maximum 70 characters. redit Suisse: It will be ignored. However, when provided - it must conform with the scheme. Other Othr Max35Text ontact details in an other form. H Definition: Recommendation: Should contain the version of the software used to create this message. redit Suisse: It will be ignored. However, when provided - it must conform with the scheme. H Definition: redit Suisse: Forwarding Agent FwdgAgt ranchandfinancialinstitutionidentification4 Financial institution that receives the instruction from the initiating party and forwards it to the next agent in the payment chain for execution. This element may only be used by agreement with the instructed financial institution. Not used for processing purposes and will be ignored. However, when provided it must conform with the schema. Payment Information PmtInf PaymentInstructionInformation3 Set of characteristics that applies to the debit side of the payment transactions included in the credit transfer initiation. redit Suisse pain SIX v Implementation Guidelines 6

7 +Id ISO Index: 2.1 Errorode: ardinality: 1..1 H Status: M ++PmtMtd ISO Index: 2.2 Errorode: ardinality: 1..1 H Status: M DU02, H21, FF01 FF01, NARR, H21 Payment Information Identification PmtInfId Max35Text Unique identification, as assigned by a sending party, to unambiguously identify the payment information group within the message. H Definition: Value must be unique within the whole message (is used as reference in the Status Report "pain. 002"). Only the SWIFT character set is permitted for this element. redit Suisse: If value is not unique within the message, the whole pain.001 will get rejected. The uniqueness of Payment Information Identification over time is not validated. Rsnd: H21 Instruction Reference is mandatory Rsnd: DU02 Value <PmtInfId> must be unique within the whole message. Example: <PmtInfId>PmtInfId-P01-POS-01</PmtInfId> Payment Method PmtMtd PaymentMethod3ode Specifies the means of payment that will be used to move the amount of money. H Definition: "TRA" and "TRF": same meaning, no effect on the way the debit advices are controlled. In Switzerland the "TRA" value is processed in the same way as the "TRF" value, it has no special function. Furthermore, for check payments and payment instructions (postal mandates), the "HK" value is permitted. H PT Rules: Type 1, 2.1, 2.2, 3, 4, 5, 6: May only contain "TRA" or "TRF". Type 7, 8: May only contain "HK". redit Suisse: Domestic HF postal orders (Payment Type 7) are not supported (Status Reason ode: NARR). Rsnd: FF01 Allowed values of Payment Method are "TRF","TRA","HK" Rsnd: NARR OUTPMT payment type is not supported post SIX release 4.3 Rsnd: H21 Payment Method is mandatory Example: <PmtMtd>TRF</PmtMtd> redit Suisse pain SIX v Implementation Guidelines 7

8 ++tchookg ISO Index: 2.3 Errorode: FF01 H Status: O H Definition: redit Suisse: atch ooking tchookg atchookingindicator Identifies whether a single entry per individual transaction or a batch entry for the sum of the amounts of all transactions within the group of a message is requested. Usage: atch booking is used to request and not order a possible batch booking. The option "true" is recommended. "true": Wherever possible, one batch booking is made per "Payment Information" (). A separate -level must be created for each currency being transferred. Mixed -levels may only be used as AOS by agreement with the financial institution, grouped according to currency and sometimes other criteria (e.g. charging options), The booking is identified using the Payment Information Identification (). "false": One booking should be made for each "redit Transfer Transaction Information" (). ookings are usually identified by the "Payment Identification" (). Alternatively, the financial institution can also identify the booking using, for example, the "Payment Information Identification" () element. If this element is not sent, then the booking proceeds as for "true". Effect on setting values for <tchookg> and <Prtry> (/PmtInf/DbtrAcct/Tp/ Prtry): tchookg Prtry ooking camt.054 camt.053 camt.053 camt.052 with details without details true / empty NOA atch No Advice No Details No Details No Details true / empty 1 SIA atch With Details With Details No Details With Details true / empty 2 ND atch No Details No Details No Details No Details true / empty WD atch With Details With Details With Details With Details true / empty Empty atch With Details With Details No Details With Details false NOA Single No Advice With Details With Details With Details false SIA Single With Details With Details With Details With Details false 1 ND Single With Details With Details With Details With Details false 1 WD Single With Details With Details With Details With Details false Empty Single With Details With Details With Details With Details 1 The combination should not be used and is not recommended by redit Suisse 2 The combination is recommended for salary payments ++NbOfTxs ISO Index: 2.4 Errorode: AM18, FF01 H Status: O ++trlsum ISO Index: 2.5 Errorode: AM10 H Status: O Rsnd: Example: Only 4 values are allowed for atch ooking element: '0'', '1", 'true', 'false', as per XSD definition (boolean data type). When any other value is provided (e.g. <tchookg>true</tchookg> or <tchookg></tchookg>) - the whole -Level will be rejected with the Status Reason ode FF01. FF01 Invalid value of atch ooking, it should be "true" or "false" <tchookg>true</tchookg>; <tchookg>false</tchookg>; <tchookg>1</tchookg>; <tchookg>0</tchookg> Number Of Transactions NbOfTxs Max15NumericText Number of individual transactions contained in the paymnet information group. H Definition: Not generally checked by Swiss institutions. hecking uses the corresponding element at A-Level. Pattern: [0-9]{1,15} redit Suisse: It is recommended that the element is provided on A-Level. However, when provided the content will be validated. The value must be the same as total number of -Levels within -Level. Rsnd: FF01 There is no transaction present in the message. Rsnd: AM18 Number of transactions <x> does not match the calculated number of transactions <y> ontrol Sum trlsum DecimalNumber Total of all individual amounts included in the group, irrespective of currencies. H Definition: Not generally checked by Swiss institutions. hecking uses the corresponding element at A-Level. FractionDigits: 17 TotalDigits: 18 redit Suisse: It is recommended that the element is provided on A-Level. However, when provided the value will be validated. The value must match the overall sum of all amounts of all single transactions within -Level (instructed as well as equivalent amounts). Rsnd: AM10 ontrol Sum <x> does not match the calculated sum of Amounts <y> redit Suisse pain SIX v Implementation Guidelines 8

9 ++PmtTpInf ISO Index: 2.6 Errorode: H07 H Status: O ++PmtTpInf +++InstrPrty ISO Index: 2.7 H Status: D H Definition: H PT Rules: redit Suisse: Rsnd: Example: H Definition: redit Suisse: Payment Type Information PmtTpInf PaymentTypeInformation19 Set of elements used to further specify the type of transaction. an be used at -Level or -Level, but generally not in both at the same time. Some institutions permit it to be sent at both levels but not the same sub-element at both levels. Type 5, 7: Use at -Level is recommended. Type 1, 2.1, 2.2: Use at -Level is recommended. If element is present on both, - and -Levels, the whole -Level will be rejected with the Status Reason ode 'H07' and with the error text on pain.002 -Level. H07 PmtTpInf, UltmtDbtr or hrgr should not be duplicated across and level <PmtTpInf> <LclInstrm> <Prtry>H01</Prtry> </LclInstrm> </PmtTpInf> ; <PmtTpInf> <SvcLvl> <d>sepa</d> </SvcLvl> </PmtTpInf> Instruction Priority InstrPrty Priority2ode Indicator of the urgency or order of importance that the instructing party would like the instructed party to apply to the processing of the instruction. The service that is initiated must first be agreed with the financial institution in question. For normal handling, the element can be omitted. The value "NORM" equates to execution with the value date as the next banking business day (depending on the currency). The value "HIGH" equates to the current Express processing, i.e. execution on the same value date, provided delivery is within the time for acceptance specified by the financial institution in question (depending on the currency). This kind of execution may result in additional charges. Any details about the Express processing should be sent at -Level, because values at -Level are ignored. The payment will be processed according to redit Suisse cut-off times, independent from the delivered code. Service Level SvcLvl ++PmtTpInf ServiceLevel8hoice +++SvcLvl Agreement under which or rules under which the transaction should be processed. ISO Index: 2.8 H Definition: Service Level affects the way payment is made at the financial institution. The focus is on achieving the fastest possible credit for the creditor. H Status: O H PT Rules: Type 5: use is recommended. ardinality: 1..1 xs:choice {Or ++PmtTpInf +++SvcLvl ++++d ISO Index: 2.9 Errorode: H16 ardinality: 1..1 H Status: D ode d ExternalServiceLevel1ode Length: 1 4 Specifies a pre-agreed service or level of service between the parties, as published in an external service level code list. H Definition: odes according Payments External ode Lists. If used, then Proprietary must not be present. H PT Rules: Type 5: Must be used if "Service Level" is used, only "SEPA" permitted. Swiss Remark: odes according "Payments External ode Lists". The following values will be accepted by the financial institutions: SEPA (Single Euro Payments Area) PRPT (EA Priority Service) SDVA (Same Day Value) URGP (Urgent Payment) These values SEPA, PRPT, SDVA, URGP are taken into account if the financial institution offers the service in question, otherwise they are ignored. If used, then "Proprietary" must not be present. redit Suisse: Only value 'SEPA' is used for processing purposes. Other values do not trigger a special behavior. It is recommended to be used at -Level. It must not be used simultaneously at -Level and - Level. Rsnd: H16 Proprietary must not be present at same time. Example: <d>sepa</d> redit Suisse pain SIX v Implementation Guidelines 9

10 Or} ++PmtTpInf +++SvcLvl ++++Prtry ISO Index: 2.10 Errorode: H17 ardinality: 1..1 H Status: D ++PmtTpInf +++LclInstrm ISO Index: 2.11 Errorode: H21 H Status: D Proprietary Prtry Max35Text Specifies a pre-agreed service or level of service between the parties, as a proprietary code. H Definition: Is currently ignored by financial institutions. If used, then "ode" must not be present. H PT Rules: Type 5: must not be used. redit Suisse: urrently not used for processing purposes. However, when provided it must conform with the scheme. Rsnd: H17 Service Level Proprietary ode is not allowed for this payment type. Local Instrument LclInstrm LocalInstrument2hoice User community specific instrument. Usage: This element is used to specify a local instrument, local clearing option and/or further qualify the service or service level. H PT Rules: Type 1, 2.1, 2.2, 7: must be used. Example: <PmtTpInf> <LclInstrm> <Prtry>H01</Prtry> </LclInstrm> </PmtTpInf> ardinality: 1..1 xs:choice {Or ++PmtTpInf +++LclInstrm ++++d ISO Index: 2.12 Errorode: ardinality: 1..1 H Status: D H16, NARR, H17 Or} ++PmtTpInf +++LclInstrm ++++Prtry ISO Index: 2.13 Errorode: H17 ardinality: 1..1 H Status: D ode d ExternalLocalInstrument1ode Specifies the local instrument, as published in an external local instrument code list. H Definition: If used, then "Proprietary" must not be present. H PT Rules: Type 7: "PP" must be used in combination with "PmtMtd" = "HK". redit Suisse: Domestic HF postal orders (Payment Type 7) are not supported. Value "PP" (Payment Method 'HK' ) will be rejected with Status Reason ode NARR. Rsnd: NARR OUTPMT payment type is not supported post SIX release 4.3 Rsnd: H16 Proprietary must not be present at same time. Proprietary Prtry Max35Text Specifies the local instrument, as a proprietary code. H Definition: If used, then "ode" must not be present. H PT Rules: Type 1: "H01" must be used. Type 2.1: "H02" must be used. Type 2.2: "H03" must be used. Each in combination with PmtMtd = TRF/TRA. Rsnd: H17 Local Instrument ode and Proprietary Local Instrument ode may not both be present at the same time ategory Purpose tgypurp ++PmtTpInf ategorypurpose1hoice +++tgypurp Specifies the high level purpose of the instruction based on a set of pre-defined categories. ISO Index: 2.14 Usage: This is used by the initiating party to provide information concerning the processing of the payment. It is likely to trigger special processing by any of the agents involved in the payment H Status: O chain. H Definition: Gives information about the purpose of the payment order. ardinality: 1..1 xs:choice redit Suisse pain SIX v Implementation Guidelines 10

11 {Or ++PmtTpInf +++tgypurp ++++d ISO Index: 2.15 Errorode: H16 ardinality: 1..1 H Status: M ++ReqdExctnDt ISO Index: 2.17 Errorode: ardinality: 1..1 H Status: M H03, H04, H21, FF01 ode d ExternalategoryPurpose1ode Length: 1 4 ategory purpose, as published in an external category purpose code list. H Definition: odes according "Payments External ode Lists". If required, the code "SALA" or "PENS" must always be sent at - Level. Must be used if "ategory Purpose" is used. redit Suisse: When provided it must conform with the scheme. This code has no effect on processing within redit Suisse. odes SALA=SalaryPayment and PENS=PensionPayment do not result in a different processing. Remark: A salary payment is defined by setting <atchookg> to 'true' and <DbtrAcct><Tp><Prty> to 'ND'. H Definition: redit Suisse: Requested Execution Date ReqdExctnDt ISODate Date at which the initiating party requests the clearing agent to process the payment. Usage: This is the date on which the debtor's account is to be debited. If payment by cheque, the date when the cheque must be generated by the bank. ontains the required date of execution. Where appropriate, the value data is automatically modified to the next possible banking/post Office working day. Valid date range is: Date of execution no more than 60 calendar days in the future (from submission date) Date of execution no more than 40 calendar days in the past (from submission date) ++Dbtr ISO Index: 2.19 ardinality: 1..1 H Status: M ++Dbtr +++Nm ISO Index: 2.19 Errorode: H16 H Status: R ++Dbtr +++PstlAdr ISO Index: 2.19 H Status: O Rsnd: Rsnd: Rsnd: Example: H Definition: Where appropriate, the value data is automatically modified to the next possible banking/post Office working day. H03 The value date is too far in the future H04 The value date is too far in the past H21 Instructed Day is mandatory <ReqdExctnDt> </ReqdExctnDt> Debtor Dbtr PartyIdentification32 Party that owes an amount of money to the (ultimate) creditor. The debtor is only identified by the "Debtor Account" element. Information in the "Debtor" field will be ignored. What is required is the master data for the financial institution for this debtor. Name Nm Max140Text Length: Name by which a party is known and which is usually used to identify that party. H Definition: Recommendation: Use, maximum 70 characters. redit Suisse: The element is not used for processing purposes. However, if delivered it must be conformed with the schema. Rsnd: H16 Originating Party Name may not exceed 70 characters H Definition: redit Suisse: Postal Address PstlAdr PostalAddress6 Information that locates and identifies a specific address, as defined by postal services. Recommendation: Do not use. The content will be overwritten with account master data. However, if delivered, the element must still be conformed with th schema: Structured Address elements are recommended. Maximum 2 occurrences of Address Line are allowed. When combining Structured elements with Unstructured Address Lines, only ountry is allowed. Identification Id ++Dbtr Party6hoice +++Id Unique and unambiguous identification of a party. ISO Index: 2.19 H Definition: Is currently ignored by financial institutions. redit Suisse: redit Suisse does not control content of this element (no validation). It will be ignored. However, if H Status: O delivered the element must still conform with the scheme. ardinality: 1..1 xs:choice redit Suisse pain SIX v Implementation Guidelines 11

12 {Or ++Dbtr +++Id ++++OrgId ISO Index: 2.19 ardinality: 1..1 H Status: D Or} ++Dbtr +++Id ++++PrvtId ISO Index: 2.19 ardinality: 1..1 H Status: D ++DbtrAcct ISO Index: 2.20 Errorode: H21 ardinality: 1..1 H Status: M ++DbtrAcct +++Id ISO Index: 2.20 ardinality: 1..1 H Status: M H Definition: redit Suisse: H Definition: H Definition: Rsnd: ardinality: 1..1 xs:choice {Or ++DbtrAcct +++Id ++++IAN ISO Index: 2.20 Errorode: A01 ardinality: 1..1 H Status: R Or} ++DbtrAcct +++Id ++++Othr ISO Index: 2.20 Errorode: H17 ardinality: 1..1 H Status: D ++DbtrAcct +++Id ++++Othr +++++Id ISO Index: 2.20 Errorode: A01 ardinality: 1..1 H Status: M H Definition: Pattern: redit Suisse: Rsnd: Example: H Definition: redit Suisse: Organisation Identification OrgId OrganisationIdentification4 Unique and unambiguous way to identify an organisation. Only "I Or EI" or an element from "Other" permitted. If used, the "Private Identification" must not be present. redit Suisse does not control content of this element (no validation). It will be ignored. However, if delivered the element must still conform with the scheme. Private Identification PrvtId PersonIdentification5 Unique and unambiguous identification of a person, eg, passport. Only "Date And Place Of irth" or an element from "Other" permitted. If used, "Organisation Identification" must not be present. Debtor Account DbtrAcct ashaccount16 Unambiguous identification of the account of the debtor to which a debit entry will be made as a result of the transaction. Recommendation: IAN should be used. However, "Other" is currently also still permitted by some financial institutions for the proprietary account number. The "Type/Proprietary" element can also be used to define the way the debit advice is controlled. H21 Originating Party Account is mandatory Identification Id AccountIdentification4hoice Unique and unambiguous identification for the account between the account owner and the account servicer. IAN IAN IAN2007Identifier International ank Account Number (IAN) - identifier used internationally by financial institutions to uniquely identify the account of a customer. Further specifications of the format and content of the IAN can be found in the standard ISO "anking and related financial services - International ank Account Number (IAN)" version , or later revisions. Recommendation: Use. If used, "Other" must not be present. [A-Z]{2,2}[0-9]{2,2}[a-zA-Z0-9]{1,30} Must be defined for account identification. A01 Originating Party Account <IAN>H </IAN> Other Othr GenericAccountIdentification1 Unique identification of an account, as assigned by the account servicer, using an identification scheme. If used, then "IAN" must not be present. Will be ignored (IAN must be used for account identification) Identification Id Max34Text Length: 1 34 Identification assigned by an institution. H Definition: Proprietary bank or postal account number. Must be used if Other is used. redit Suisse pain SIX v Implementation Guidelines 12

13 Type Tp ++DbtrAcct ashaccounttype2 +++Tp Specifies the nature, or use of the account. ISO Index: 2.20 redit Suisse: Not used for processing. H Status: O ardinality: 1..1 xs:choice {Or ++DbtrAcct +++Tp ++++d ISO Index: 2.20 ardinality: 1..1 H Status: D Or} ++DbtrAcct +++Tp ++++Prtry ISO Index: 2.20 Errorode: H16 ardinality: 1..1 H Status: D ++DbtrAcct +++cy ISO Index: 2.20 H Status: O ++DbtrAgt ISO Index: 2.21 ardinality: 1..1 H Status: M ++DbtrAgt +++FinInstnId ISO Index: 2.21 ardinality: 1..1 H Status: M ++DbtrAgt +++FinInstnId ++++I ISO Index: 2.21 Errorode: R01 H Status: D H Definition: ode d ashaccounttype4ode Account type, in a coded form. Is currently ignored by financial institutions. If used, then "Proprietary" must not be present. Proprietary Prtry Max35Text Nature or use of the account in a proprietary form. H Definition: an be used to control the debit advice. The following options are available: NOA No Advice SIA Single Advice ND ollective Advice No Details WD ollective Advice With Details If used, then "ode" must not be present. redit Suisse: Please see details redit Suisse on element <PmtInf><tchookg>. Element will be used to steer advice production at redit Suisse. Only following values are used for processing purposes: NOA, SIA, ND, WD. Any other values will be ignored. H Definition: Pattern: H Definition: H Definition: Pattern: Example: urrency cy ActiveOrHistoricurrencyode Identification of the currency in which the account is held. Usage: urrency should only be used in case one and the same account number covers several currencies and the initiating party needs to identify which currency needs to be used for settlement on the account. Is currently ignored by financial institutions. [A-Z]{3,3} Debtor Agent DbtrAgt ranchandfinancialinstitutionidentification4 Financial institution servicing an account for the debtor. The Swiss financial institutions recommend entering the I or IID (institutional identification) in this element. Financial Institution Identification FinInstnId FinancialInstitutionIdentification7 Unique and unambiguous identification of a financial institution, as assigned under an internationally recognised or proprietary identification scheme. I I IIdentifier ode allocated to a financial institution by the ISO 9362 Registration Authority as described in ISO 9362 "anking - anking telecommunication messages - usiness identifier code (I)". I of the Debtor ank. If used, then "learing System Member Identification" must not be present. [A-Z]{6,6}[A-Z2-9][A-NP-Z0-9]([A-Z0-9]{3,3}){0,1} <I>RESHZZ80A</I> redit Suisse pain SIX v Implementation Guidelines 13

14 ++DbtrAgt +++FinInstnId ++++lrsysmmbid ISO Index: 2.21 H Status: D ++DbtrAgt +++FinInstnId ++++lrsysmmbid +++++lrsysid ISO Index: 2.21 H Status: O H Definition: ardinality: 1..1 xs:choice {Or ++DbtrAgt +++FinInstnId ++++lrsysmmbid +++++lrsysid d ISO Index: 2.21 Errorode: H16 ardinality: 1..1 H Status: D Or} ++DbtrAgt +++FinInstnId ++++lrsysmmbid +++++lrsysid Prtry ISO Index: 2.21 Errorode: H16 ardinality: 1..1 H Status: N ++DbtrAgt +++FinInstnId ++++lrsysmmbid +++++MmbId ISO Index: 2.21 Errorode: AGNT ardinality: 1..1 H Status: M ++DbtrAgtAcct ISO Index: 2.21 H Status: M ++UltmtDbtr ISO Index: 2.23 Errorode: H07 H Status: O learing System Member Identification lrsysmmbid learingsystemmemberidentification2 Information used to identify a member within a clearing system. If used, then "I" must not be present. learing System Identification lrsysid learingsystemidentification2hoice Specification of a pre-agreed offering between clearing agents or the channel through which the payment instruction is processed. ode d ExternallearingSystemIdentification1ode Length: 1 5 Identification of a clearing system, in a coded form as published in an external list. H Definition: odes according "Payments External ode Lists" [7]. Only "H" is permitted in Switzerland. If used, then "Proprietary" must not be present. redit Suisse: Only value H is allowed. Proprietary Prtry Max35Text Identification code for a clearing system, that has not yet been identified in the list of clearing systems. H Definition: Recommendation: Do not use. If used, then "ode" must not be present. Member Identification MmbId Max35Text Identification of a member of a clearing system. H Definition: I number of the Debtor ank / IID of the Debtor ank. Must be used if learing System Member Identification is used. H Definition: H Definition: redit Suisse: Debtor Agent Account DbtrAgtAcct ashaccount16 Unambiguous identification of the account of the debtor agent at its servicing agent in the payment chain. The Swiss financial institutions recommend entering the I or IID (institutional identification) in this element. Ultimate Debtor UltmtDbtr PartyIdentification32 Ultimate party that owes an amount of money to the (ultimate) creditor. an be used at -Level or -Level but not at both at the same time. If element is present on both, the - and the -Levels, then the whole -Level will be rejected with the Status Reason ode 'H07' and with the error text on pain.002 -Level. redit Suisse pain SIX v Implementation Guidelines 14

15 ++UltmtDbtr +++Nm ISO Index: 2.23 H Status: O ++UltmtDbtr +++PstlAdr ISO Index: 2.23 H Status: O Name Nm Max140Text Length: Name by which a party is known and which is usually used to identify that party. H Definition: Maximum 70 characters H Definition: H PT Rules: redit Suisse: Postal Address PstlAdr PostalAddress6 Information that locates and identifies a specific address, as defined by postal services. This information is structured and defined in the same way as the definitions for the reditor (Index 2.79). Type 5: is not forwarded in interbank traffic. Structured Address elements are recommended. Maximum 2 occurrences of Address Line are allowed. When combining Structured elements with Unstructured Address Lines, only structured ountry element is allowed. Identification Id ++UltmtDbtr Party6hoice +++Id Unique and unambiguous identification of a party. ISO Index: 2.23 H Definition: Recommendation: do not use. H Status: O ardinality: 1..1 xs:choice {Or ++UltmtDbtr +++Id ++++OrgId ISO Index: 2.23 ardinality: 1..1 H Status: D Or} ++UltmtDbtr +++Id ++++PrvtId ISO Index: 2.23 ardinality: 1..1 H Status: D ++hrgr ISO Index: 2.24 Errorode: H Status: D FF01, H16, H07 H Definition: H Definition: H Definition: H PT Rules: redit Suisse: Rsnd: Rsnd: Organisation Identification OrgId OrganisationIdentification4 Unique and unambiguous way to identify an organisation. Only "I Or EI" or an element from "Other" permitted. If used, the "Private Identification" must not be present. Private Identification PrvtId PersonIdentification5 Unique and unambiguous identification of a person, eg, passport. Only "Date And Place Of irth" or an element from "Other" permitted. If used, "Organisation Identification" must not be present. harge earer hrgr hargeearertype1ode Specifies which party/parties will bear the charges associated with the processing of the payment transaction. an be used at -Level or -Level but not at both at the same time. Permitted codes are: DET orne by Debtor (ex OUR) RED orne by reditor (ex EN) SHAR Shared (ex. SHA) SLEV Service Level Type 5: If used, then "SLEV" must be used. If element is present on both, the - and the -Levels, then the whole -Level will be rejected with the Status Reason ode 'H07' and with the error text on pain.002 -Level. FF01 harge earer must be from any of the following ("DET","RED","SHAR","SLEV") H16 When Service Level ode is "SEPA" then expected value of harge earer is "SLEV" redit Suisse pain SIX v Implementation Guidelines 15

16 ++hrgsacct ISO Index: 2.25 H Status: O H Definition: redit Suisse: harges Account hrgsacct ashaccount16 Account used to process charges associated with a transaction. Usage: harges account should be used when charges have to be booked to an account different from the account identified in debtor's account. Not normally used, in this case any charges are made to the "Debtor Account". It will not be used for processing purposes. When provided, it still must conform with the scheme. harges by default are made to the "Debtor Account" (if not indicated differently in "hrgr"). Identification Id ++hrgsacct AccountIdentification4hoice +++Id Unique and unambiguous identification for the account between the account owner and the ISO Index: 2.25 account servicer. ardinality: 1..1 H Definition: Must be used if "harges Account" is used. H Status: M ardinality: 1..1 xs:choice {Or ++hrgsacct +++Id ++++IAN ISO Index: 2.25 Errorode: A01 ardinality: 1..1 H Status: R Or} ++hrgsacct +++Id ++++Othr ISO Index: 2.25 Errorode: A01 ardinality: 1..1 H Status: D ++hrgsacct +++Id ++++Othr +++++Id ISO Index: 2.25 Errorode: A01 ardinality: 1..1 H Status: M ++hrgsacct +++cy ISO Index: 2.25 H Status: O ISO Index: 2.0 Errorode: H21 ardinality: 1..unbounded H Status: M H Definition: Pattern: H Definition: IAN IAN IAN2007Identifier International ank Account Number (IAN) - identifier used internationally by financial institutions to uniquely identify the account of a customer. Further specifications of the format and content of the IAN can be found in the standard ISO "anking and related financial services - International ank Account Number (IAN)" version , or later revisions. Use of "IAN" recommended. If used, "Other" must not be present. [A-Z]{2,2}[0-9]{2,2}[a-zA-Z0-9]{1,30} Other Othr GenericAccountIdentification1 Unique identification of an account, as assigned by the account servicer, using an identification scheme. If used, then "IAN" must not be present. Identification Id Max34Text Length: 1 34 Identification assigned by an institution. H Definition: Proprietary bank or postal account number. Must be used if "Other" is used. H Definition: Pattern: urrency cy ActiveOrHistoricurrencyode Identification of the currency in which the account is held. Usage: urrency should only be used in case one and the same account number covers several currencies and the initiating party needs to identify which currency needs to be used for settlement on the account. Is currently ignored by financial institutions. [A-Z]{3,3} redit Transfer Transaction Information dttrftxinf redittransfertransactioninformation10 Set of elements used to provide information on the individual transaction(s) included in the message. redit Suisse pain SIX v Implementation Guidelines 16

17 +++PmtId ISO Index: 2.28 Errorode: H21 ardinality: 1..1 H Status: M +++PmtId ++++InstrId ISO Index: 2.29 Errorode: DU05, H21 H Status: R +++PmtId ++++EndToEndId ISO Index: 2.30 ardinality: 1..1 H Status: M +++PmtTpInf ISO Index: 2.31 Errorode: H07 H Status: D +++PmtTpInf ++++InstrPrty ISO Index: 2.32 H Status: O Payment Identification PmtId PaymentIdentification1 Set of elements used to reference a payment instruction. Instruction Identification InstrId Max35Text Unique identification as assigned by an instructing party for an instructed party to unambiguously identify the instruction. H Definition: Usage: the instruction identification is a point to point reference that can be used between the instructing party and the instructed party to refer to the individual instruction. It can be included in several messages related to the instruction. Recommendation: Should be used and be unique within the -Level. Only the SWIFT character set is permitted for this element. End To End Identification EndToEndId Max35Text Unique identification assigned by the initiating party to unumbiguously identify the transaction. This identification is passed on, unchanged, throughout the entire end-to-end chain. H Definition: H PT Rules: redit Suisse: H Definition: H PT Rules: redit Suisse: Rsnd: Usage: The end-to-end identification can be used for reconciliation or to link tasks relating to the transaction. It can be included in several messages related to the transaction. ustomer reference, normally forwarded as far as the beneficiary. Only the SWIFT character set is permitted for this element. Type 1: not forwarded to the beneficiary. If instruction ID is not present, end to end ID will be used as a booking reference for messages with batch booking indicator equals false. Payment Type Information PmtTpInf PaymentTypeInformation19 Set of elements used to further specify the type of transaction. an be used at -Level or -Level, but normally not in both at the same time. Some institutions permit it to be sent at both levels but not the same sub-element at both levels. Type 5, 7: Use at -Level is recommended. Type 1, 2.1, 2.2: Use at -Level is recommended. Usage of this component is only conditional, depending on the redit Suisse payment types. If element is present on both, - and -Levels, the whole -Level will be rejected with the Status Reason ode 'H07' and with the error text on pain.002 -Level. H07 Payment Type Information can be used at -Level or -Level but not at both at the same time. Instruction Priority InstrPrty Priority2ode Indicator of the urgency or order of importance that the instructing party would like the instructed party to apply to the processing of the instruction. H Definition: Any information about the Express processing should be sent at - Level, values in this element are ignored. H PT Rules: Type 5: Must not be used. redit Suisse: Used by redit Suisse to trigger processing (HIGH = Express Payment, NORMAL or empty = Normal Payment.) The payment will be processed according to redit Suisse cut-off times, independent from the delivered code and charges may apply. If the element is not provided on -level, the value on -Level will be validated and processed accordingly. redit Suisse pain SIX v Implementation Guidelines 17

18 Service Level SvcLvl ServiceLevel8hoice +++PmtTpInf Agreement under which or rules under which the transaction should be processed. ++++SvcLvl H Definition: Service Level affects the way payment is made at the financial institution. The focus is on achieving ISO Index: 2.33 the fastest possible credit for the creditor. Errorode: H17 H PT Rules: Type 5: Use is recommended. redit Suisse: Usage of this component is only conditional, depending on the redit Suisse payment types. H Status: O ardinality: 1..1 xs:choice {Or +++PmtTpInf ++++SvcLvl +++++d ISO Index: 2.34 Errorode: H16 ardinality: 1..1 H Status: D Or} +++PmtTpInf ++++SvcLvl +++++Prtry ISO Index: 2.35 Errorode: H17 ardinality: 1..1 H Status: D ode d ExternalServiceLevel1ode Length: 1 4 Specifies a pre-agreed service or level of service between the parties, as published in an external service level code list. H Definition: odes according "Payments External ode Lists". The following values will be accepted by the financial institutions: SEPA (Single Euro Payments Area) PRPT (EA Priority Service) SDVA (Same Day Value) URGP (Urgent Payment) Other values from the external code list only to be used by agreement with the financial institution. If used, then "Proprietary" must not be present. H PT Rules: Type 5: Must be used if "Service Level" is used, only "SEPA" permitted. redit Suisse: Only value 'SEPA' is used for processing purposes. Other values do not trigger a special behavior. It is recommended to be used at -Level. It must not be used simultaneously at -Level and - Level. Rsnd: H16 If ode is send, then Proprietary must not be present. Proprietary Prtry Max35Text Specifies a pre-agreed service or level of service between the parties, as a proprietary code. H Definition: Is currently ignored by financial institutions. If used, then "ode" must not be present. H PT Rules: Type 5: Must not be used. redit Suisse: urrently not used for processing purposes. However, when provided it must conform with the scheme. Rsnd: H17 Service Level Proprietary ode is not allowed for this payment type Local Instrument LclInstrm LocalInstrument2hoice +++PmtTpInf User community specific instrument. ++++LclInstrm ISO Index: 2.36 Usage: This element is used to specify a local instrument, local clearing option and/or further Errorode: H21 qualify the service or service level. H PT Rules: Type 1, 2.1, 2.2, 7: Must be used. H Status: D ardinality: 1..1 xs:choice {Or +++PmtTpInf ++++LclInstrm +++++d ISO Index: 2.37 Errorode: ardinality: 1..1 H Status: D NARR, H16, H17 ode d ExternalLocalInstrument1ode Specifies the local instrument, as published in an external local instrument code list. H Definition: odes according "Payments External ode Lists". If used, then "Proprietary" must not be present. H PT Rules: Type 7: "PP" must be used in combination with "PmtMtd" = "HK". redit Suisse: Domestic HF postal orders (Payment Type 7) are not supported. Value "PP" (Payment Method 'HK' ) will be rejected with Status Reason ode NARR. Rsnd: NARR OUTPMT payment type is not supported post SIX release 4.3 Rsnd: H17 If "ode" is used, then "Proprietary" must not be present. redit Suisse pain SIX v Implementation Guidelines 18

19 Or} +++PmtTpInf ++++LclInstrm +++++Prtry ISO Index: 2.38 Errorode: H17, H16 ardinality: 1..1 H Status: D Proprietary Prtry Max35Text Specifies the local instrument, as a proprietary code. H Definition: If used, then "ode" must not be present. H PT Rules: Type 1: "H01" must be used. Type 2.1: "H02" must be used. Type 2.2: "H03" must be used. Each in combination with PmtMtd = "TRF/TRA". Rsnd: H16 Local Instrument ode and Proprietary Local Instrument ode may not both be present at the same time Rsnd: H17 If "Proprietary" is used, then "ode" must not be present. ategory Purpose tgypurp ategorypurpose1hoice +++PmtTpInf Specifies the high level purpose of the instruction based on a set of pre-defined categories. ++++tgypurp Usage: This is used by the initiating party to provide information concerning the processing of the ISO Index: 2.39 payment. It is likely to trigger special processing by any of the agents involved in the payment Errorode: H17 chain. H Definition: Any information about the purpose of the payment order should be sent at -Level, values in this H Status: O element are ignored. Rsnd: H17 ategory Purpose is not allowed for this payment type. ardinality: 1..1 xs:choice {Or +++PmtTpInf ++++tgypurp +++++d Errorode: H16 ardinality: 1..1 ode d ExternalategoryPurpose1ode Length: 1 4 ategory purpose, as published in an external category purpose code list. redit Suisse: When provided it must conform with schema. This code has no effect on processing within redit Suisse. odes SALA=SalaryPayment and PENS=PensionPayment does not result in a differentt processing. Remark: A salary payment is defined by setting <atchookg> to 'true' and <DbtrAcct><Tp><Prty> to 'ND'. Amount Amt AmountType3hoice +++Amt Amount of money to be moved between the debtor and creditor, before deduction of charges, ISO Index: 2.42 expressed in the currency as ordered by the initiating party. ardinality: 1..1 H Definition: Either as "Instructed Amount" or "Equivalent Amount". It is recommended to create one -Level for H Status: M each currency transferred. ardinality: 1..1 xs:choice {Or +++Amt ++++InstdAmt ISO Index: 2.43 Errorode: ardinality: 1..1 H Status: D AM01, AM02, H17 Instructed Amount InstdAmt ActiveOrHistoricurrencyAndAmount Amount of money to be moved between the debtor and creditor, before deduction of charges, expressed in the currency as ordered by the initiating party. H Definition: If used, then "Equivalent Amount" must not be present. H PT Rules: Type 1, 2.1, 2.2, 3: Must contain "HF" or "EUR", the amount must be between 0.01 and Type 4: All currencies except "HF" and "EUR" permitted. Type 5: Must contain "EUR", the amount must be between 0.01 and Type 7: Must contain "HF". FractionDigits: 5 TotalDigits: 18 redit Suisse: redit Suisse dynamically checks the number of decimals depending on the currency, according to ISO Rsnd: AM01 If "urrencyamount" is used, then "Equivalent Amount" must not be present. Rsnd: AM02 Instructed Amount is mandatory Rsnd: H17 Instructed Amount must contain a valid amount with [n] decimal places. Instructed Amount [x] should be numeric with maximum [n] decimals and a value between [y] and [z] redit Suisse pain SIX v Implementation Guidelines 19

UBS Implementation Guidelines

UBS Implementation Guidelines US Implementation Guidelines Swiss Recommendations for credit transfers pain.001.001.03.ch.02 - SR Version 1.6 US Version 1.0 January 2017 US Implementation Guidelines Swiss Recommendations for credit

More information

UBS Implementation Guidelines

UBS Implementation Guidelines US Implementation Guidelines Swiss Payment Standards for credit transfers pain.001.001.03.ch.02 - SPS Version 1.8 US Version 1.0 September 2018 Table of ontents 1. redit Transfer message 3 1.1 Scope of

More information

UBS Implementation Guidelines

UBS Implementation Guidelines US Implementation Guidelines ommon Global Implementation (GI) for credit transfers pain.001.001.03 US Version 1.1 September 2018 Table of ontents 1. redit Transfer message 3 1.1 Scope of application of

More information

UBS Implementation Guidelines

UBS Implementation Guidelines US Implementation Guidelines DFÜ greement of Deutsche Kreditwirtschaft for SEP redit Transfer Initiation pain.001.001.03 - DK Version 3.1 US Version 1.0 pril 2018 US Implementation Guidelines DFÜ greement

More information

UBS Implementation Guidelines

UBS Implementation Guidelines US Implementation Guidelines DFÜ greement of Deutsche Kreditwirtschaft for SEP redit Transfer Initiation pain.001.001.03 - DK Version 3.0 US Version 1.0 January 2017 US Implementation Guidelines DFÜ greement

More information

ISO Payments. Swiss Implementation Guidelines for Customer-Bank Messages Credit Transfer (Payment Transactions)

ISO Payments. Swiss Implementation Guidelines for Customer-Bank Messages Credit Transfer (Payment Transactions) ISO 20022 Payments for Customer-Bank Messages Credit Transfer (Payment Transactions) Version 1.7 29.05.2017 General note Any suggestions or questions relating to this document should be addressed to the

More information

Swiss Payment Standards 2018

Swiss Payment Standards 2018 Swiss Payment Standards 2018 Swiss Implementation Guidelines for Customer-Bank Messages Credit Transfer (Payment Transactions) Customer Credit Transfer Initiation (pain.001) Version 1.8, with effect from

More information

Swiss Payment Standards 2018

Swiss Payment Standards 2018 Swiss Payment Standards 2018 Swiss Implementation Guidelines for Customer-Bank Messages Credit Transfer (Payment Transactions) Customer Credit Transfer Initiation (pain.001) Version 1.8, with effect from

More information

UBS Implementation Guidelines

UBS Implementation Guidelines UBS Implementation Guidelines Swiss Payment Standards for domestic direct debit pain.008.001.02.ch.03 SPS Version 1.2 UBS Version 1.0 April 2018 UBS Implementation Guidelines Swiss Payment Standards for

More information

ISO Payments. Swiss Implementation Guidelines for Customer-Bank Messages Credit Transfer (Payment Transactions)

ISO Payments. Swiss Implementation Guidelines for Customer-Bank Messages Credit Transfer (Payment Transactions) ISO 20022 Payments Swiss Implementation Guidelines for Customer-Bank Messages Credit Transfer (Payment Transactions) Version 1.6 25.07.2016 General note Any suggestions or questions relating to this document

More information

ISO Payments. Swiss Implementation Guidelines for Customer-to-Bank Messages Credit Transfer (Payment Transactions)

ISO Payments. Swiss Implementation Guidelines for Customer-to-Bank Messages Credit Transfer (Payment Transactions) ISO 20022 Payments Swiss Implementation Guidelines for Customer-to-Bank Messages Credit Transfer (Payment Transactions) Customer Credit Transfer Initiation (pain.001) and Customer Payment Status Report

More information

SEPA Direct Debit Initiation Danske Bank's interpretation of ISO pain (Direct Debit Initiation)

SEPA Direct Debit Initiation Danske Bank's interpretation of ISO pain (Direct Debit Initiation) SEPA Direct Debit Initiation Danske Bank's interpretation of ISO 20022 pain.008.001.02 (Direct Debit Initiation) Table of Contents Introduction File layout Description Group Header Payment Information

More information

Credit Transfer. PAIN XML File Structure V 1.2

Credit Transfer. PAIN XML File Structure V 1.2 Credit Transfer PAIN.001.001.03 XML File Structure V 1.2 This document is published by Bank of Ireland, and both it, and its contents, are the property of Bank of Ireland. This document may not be reproduced

More information

UBS Implementation Guidelines

UBS Implementation Guidelines UBS Implementation Guidelines Swiss Recommendations for Payment Report pain.002.001.03.ch.02 - SR Version 1.5.1 UBS Version 1.0 July 2016 UBS Implementation Guidelines Swiss Recommendations for Payment

More information

SEPA Direct Debit Initiation Danske Bank's interpretation of ISO pain (Direct Debit Initiation)

SEPA Direct Debit Initiation Danske Bank's interpretation of ISO pain (Direct Debit Initiation) SEPA Direct Debit Initiation Danske Bank's interpretation of ISO 20022 pain.008.001.02 (Direct Debit Initiation) Table of Contents Introduction File layout Description Group Header Payment Information

More information

ISO Payments. Swiss Implementation Guidelines for Customer-Bank Messages for the Swiss Direct Debit Procedure

ISO Payments. Swiss Implementation Guidelines for Customer-Bank Messages for the Swiss Direct Debit Procedure ISO 20022 Payments Swiss Implementation Guidelines for Customer-Bank Messages for the Swiss Direct Debit Procedure Customer Direct Debit Initiation (pain.008) Version 1.1.1 07.08.2017 General note Any

More information

Credit Transfer. PAIN XML File Structure Version 1.2. Mandatory Fields Optional Fields Payment Information (Batch) / Transaction Level

Credit Transfer. PAIN XML File Structure Version 1.2. Mandatory Fields Optional Fields Payment Information (Batch) / Transaction Level Credit Transfer PAIN.001.001.03 XML File Structure V 1.3 This document is published by Bank of Ireland, and both it, and its contents, are the property of Bank of Ireland. This document may not be reproduced

More information

Swiss Payment Standards 2018

Swiss Payment Standards 2018 Swiss Payment Standards 2018 Swiss Implementation Guidelines for Customer-Bank Messages for the Swiss Direct Debit Procedure Customer Direct Debit Initiation (pain.008) Version 1.2, with effect from November

More information

SEPA Credit Transfer Unpaid Report File Format

SEPA Credit Transfer Unpaid Report File Format SEPA Credit Transfer Unpaid Report File Format PAIN.002.001.03 XML File Structure V 1.2 This document is published by Bank of Ireland, and both it, and its contents, are the property of Bank of Ireland.

More information

SCT Bulk Payments XML File Format

SCT Bulk Payments XML File Format www.aib.ie/sepa SCT Bulk Payments XML File Format This document is the property of AIB Group. No official or other user of this document, may, without the prior written permission of the Bank, disseminate

More information

Addendum on the XML message for SEPA Credit Transfer Initiation (PAIN)

Addendum on the XML message for SEPA Credit Transfer Initiation (PAIN) Addendum on the XML message for SEPA Credit Transfer Initiation (PAIN) 201 Version 1.0 - August 201 2 Table of content 1. Introduction 3 1.1 Related documents 1.2 Character Set 1.3 Change history 1.4 Summary

More information

ISO Payments. Swiss Implementation Guidelines for Customer-to-Bank Messages for the Swiss Direct Debit Procedure

ISO Payments. Swiss Implementation Guidelines for Customer-to-Bank Messages for the Swiss Direct Debit Procedure ISO 20022 Payments Swiss Implementation Guidelines for Customer-to-Bank Messages for the Swiss Direct Debit Procedure Customer Direct Debit Initiation (pain.008) and Customer Payment Status Report (pain.002)

More information

Customer Documentation Request For Payment Message (pain.013 & pain.014)

Customer Documentation Request For Payment Message (pain.013 & pain.014) Customer Documentation Request For Payment Message (pain.013 & pain.014) Version 2.2 April 2018 THIS DOCUMENT ( DOCUMENT ) IS PROVIDED UNDER THE TERMS OF THIS RTP DOCUMENTATION AGREEMENT ("AGREEMENT").

More information

Format Specification

Format Specification Format Specification ISO20022-pain.002.001.03 mbank SA 2017.01.02 Version 1.6 1. General Info...3 2. Short review of pain.002.001.03; format requirements; processing mechanism...3 3. Allowed characters

More information

UBS Implementation Guidelines

UBS Implementation Guidelines UBS Implementation Guidelines Swiss Recommendations for cash management reports camt.053.001.04 - SR Version 1.3 UBS Version 1.0 August 2016 UBS Implementation Guidelines Swiss Recommendations for cash

More information

Format Description CAMT and CAMT

Format Description CAMT and CAMT Format CAMT.052.001.02 and CAMT.053.001.02 InsideBusiness Connect SwiftNet FileAct EBICS The Netherlands Document version history Version Date Changes 1.0 First version 2.0 14-02-2014 Updated - List of

More information

pain CustomerPaymentReversalV02

pain CustomerPaymentReversalV02 Corporate egateway Message Implementation Guideline MIG version: 1.0 : 13-04-2015 2 of 7 Table of Contents 1. Introduction... 3 2. Scope... 3 3. Document references... 3 4. Services... 4 5. Use of references

More information

pain CustomerPaymentReversalV02 SEPA Direct Debit

pain CustomerPaymentReversalV02 SEPA Direct Debit Message Implementation Guideline CustomerPaymentReversalV02 SEPA Direct Debit MIG version: 1.0 : 23-04-2018 2 of 6 Table of Contents 1. Introduction... 3 2. Scope... 3 3. Document references... 3 4. Use

More information

Format description XML SEPA DD. Rabo Direct Connect (RDC)

Format description XML SEPA DD. Rabo Direct Connect (RDC) Format description XML SEPA DD Rabo Direct Connect (RDC) Content 1 SEPA DD IMPORT FORMAT... 3 1.1 DESCRIPTION... 3 1.2 GENERAL CHARACTERISTICS... 3 1.3 SEPA DD STRUCTURE... 3 1.3.1 Introduction... 3 1.3.2

More information

SEPA Direct Debit. PAIN XML File Structure

SEPA Direct Debit. PAIN XML File Structure SEPA Direct Debit PAIN.008.001.02 XML File Structure This document is published by Bank of Ireland, and both it, and its contents, are the property of Bank of Ireland. This document may not be reproduced

More information

ISO Message Implementation Guide for Payment Initiation pain

ISO Message Implementation Guide for Payment Initiation pain ISO 20022 Message Implementation Guide for Payment Initiation pain001.001.03 Credit Transfer PAIN.001.001.03 XML File Structure 1. Document Overview 1.1. Background 1.2. Document Purpose 2. The Character

More information

pain CustomerDirectDebitInitiationV02 SEPA Direct Debit

pain CustomerDirectDebitInitiationV02 SEPA Direct Debit Message Implementation Guideline CustomerDirectDebitInitiationV02 SEPA Direct Debit MIG version: 1.0 : 27-02-2017 2017-02-27 2 of 18 Table of Contents 0. Document change history... 3 1. Introduction...

More information

Document Overview. Credit Transfer PAIN XML File Structure. 1.1 Background. 1.2 Document Purpose. The Character Set.

Document Overview. Credit Transfer PAIN XML File Structure. 1.1 Background. 1.2 Document Purpose. The Character Set. ASOCIAȚIA ROMÂNĂ A BĂNCILOR Credit Transfer PAIN.001.001.03 XML File Structure Document Overview 1.1 Background 1.2 Document Purpose 2. 3. 4. 5. 6. 7. 8. 9. The Character Set Fields Types Usage Rules Unused

More information

SEPA Direct Debit. PAIN XML File Structure

SEPA Direct Debit. PAIN XML File Structure SEPA Direct Debit PAIN.008.001.02 XML File Structure This document is published by Bank of Ireland, and both it, and its contents, are the property of Bank of Ireland. This document may not be reproduced

More information

Format description Generic Payment File. Rabo Direct Connect & Rabo Internet banking (Professional)

Format description Generic Payment File. Rabo Direct Connect & Rabo Internet banking (Professional) Format description Generic Payment File Rabo Direct Connect & Rabo Internet banking (Professional) Contents 1 GENERAL... 3 1.1 GENERAL CHARACTERISTICS...3 1.2 STRUCTURE...3 1.2.1 Introduction...3 1.2.2

More information

ING Format Description Transaction Details Camt InsideBusiness Connect InsideBusiness Payments SwiftNet FileAct EBICS

ING Format Description Transaction Details Camt InsideBusiness Connect InsideBusiness Payments SwiftNet FileAct EBICS ING Format Transaction Details Camt.054.001.02 InsideBusiness Connect InsideBusiness Payments SwiftNet FileAct EBICS Document version history Version Date Changes 1.0 01-11-2016 First version 1.1 15-12-2016

More information

pain CustomerPaymentStatusReportV03

pain CustomerPaymentStatusReportV03 Message Implementation Guideline CustomerPaymentStatusReportV03 MIG version: 1.0 : SEPA Direct Debit / CustomerPaymentStatusReportV03 2 of 9 Table of Contents 1. Introduction... 3 2. Nordea usage of ISO20022

More information

camt CustomerPaymentCancellationRequestV01

camt CustomerPaymentCancellationRequestV01 Corporate Access Payables Message Implementation Guidelines camt.055.001.01 CustomerPaymentCancellationequestV01 MIG version: 1.0 : 2 of 9 Table of contents 1. Introduction... 3 2. About Corporate Access

More information

Message Usage Guideline

Message Usage Guideline Draft approved by the ISO 20022 RTPG Core Review Group Message Usage Guideline Modell: pacs.002.001.08 Version: 1.1 Issue Date: 19/07/2017 Author: ISO 20022 RTPG Core Review Group Contents History... 3

More information

Format Specification

Format Specification Format Specification ISO20022-pain.002.001.03 mbank SA 2015.12.20 Version 1.3 1. General Info... 3 2. Short review... 3 3. Allowed characters / Coding... 3 4. References to codes and colors used in the

More information

ISO CustomerPaymentStatusReport Direct Debit

ISO CustomerPaymentStatusReport Direct Debit Implementation guide ISO 20022 CustomerPaymentStatusReport Direct Debit pain.002.001.03 Version 1.0.0 Publishing date 4 November 2013 Implementation guide Table of contents 1 INTRODUCTION... 3 1.1 Related

More information

XML CONVERTING LLOYDSLINK ONLINE EURO MONEYMOVER PAYMENT XML FILES. Importing Payments in Commercial Banking Online

XML CONVERTING LLOYDSLINK ONLINE EURO MONEYMOVER PAYMENT XML FILES. Importing Payments in Commercial Banking Online XML Ò CONVERTING LLOYDSLINK ONLINE EURO MONEYMOVER PAYMENT XML FILES Importing Payments in Commercial Banking Online Import your Payments Files in Commercial Banking Online In Commercial Banking Online

More information

Bankline SEPA Direct Debit Origination XML PAIN

Bankline SEPA Direct Debit Origination XML PAIN Bankline SEPA Direct Debit Origination XML PAIN.008.001.02 This guide provides details of the formats and standards needed to generate a valid Bankline SEPA Direct Debit Origination file in PAIN.008.001.02

More information

Swiss Usage Guide for ISO Messages according to the Swiss Recommendations

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

More information

ISO CustomerPaymentStatusReport Confirmation of Receipt

ISO CustomerPaymentStatusReport Confirmation of Receipt ISO 20022 CustomerPaymentStatusReport Confirmation of Receipt pain.002 version 3 Version 1.0.1 Publishing date 21 December 2012 Table of contents 1 INTRODUCTION... 3 1.1 Related documents... 3 1.2 History...

More information

ISO Cash Management

ISO Cash Management ISO 20022 Cash Management Swiss Implementation Guidelines for Bank-to-Customer Messages (Reports) Bank-to-Customer Account Report (camt.052) Bank-to-Customer Statement (camt.053) Bank-to-Customer Debit/Credit

More information

Swiss ISO Harmonization for Software Vendors Credit Suisse Best Practice Guide

Swiss ISO Harmonization for Software Vendors Credit Suisse Best Practice Guide Public Swiss ISO 20022 Harmonization for Software Vendors Credit Suisse Best Practice Guide CREDIT SUISSE (Switzerland) Ltd., Software Partner Management October 2017 Introduction Top 7 General Swiss Payment

More information

Bankline SEPA Money Transfer XML pain

Bankline SEPA Money Transfer XML pain Bankline SEPA Money Transfer XML pain.001.001.03 This guide provides details of the formats and standards needed to generate a valid Bankline SEPA Money Transfer file Version 02.01 November 2017 Page 1

More information

ipko biznes Input File Structure International Transfers (MT103 / CSV / XML ISO20022)

ipko biznes Input File Structure International Transfers (MT103 / CSV / XML ISO20022) ipko biznes Input File Structure International Transfers (T103 / SV / XL ISO20022) Index General Information... 3 PLA / T103 File Structure... 3 Description of File Format... 3 PLA / T103 File Structure...

More information

XML CONVERTING LLOYDSLINK BACS XML FILES. Importing Payments in Commercial Banking Online

XML CONVERTING LLOYDSLINK BACS XML FILES. Importing Payments in Commercial Banking Online XML Ò CONVERTING LLOYDSLINK BACS XML FILES Importing Payments in Commercial Banking Online Import your Payments Files in Commercial Banking Online In Commercial Banking Online all Payment Files must be

More information

Format description Generic Payment File version Rabo Direct Connect, SWIFT FileAct & Rabo Internet banking (Professional)

Format description Generic Payment File version Rabo Direct Connect, SWIFT FileAct & Rabo Internet banking (Professional) Format description Generic Payment File version 1.8.2 Rabo Direct Connect, SWIFT FileAct & Rabo Internet banking (Professional) Contents 1 GENERAL... 3 1.1 GENERAL CHARACTERISTICS...3 1.2 STRUCTURE...3

More information

SEPA CREDIT TRANSFER SCHEME IMPLEMENTATION GUIDELINES

SEPA CREDIT TRANSFER SCHEME IMPLEMENTATION GUIDELINES Doc: EPC115_06 13 December 2006 (Version 2.2) OITS SG SEPA CREDIT TRANSFER SCHEME IMPLEMENTATION GUIDELINES Abstract Document Reference Issue This document sets out the SEPA rules for implementing the

More information

ING Format Description

ING Format Description ING Format CAMT.052.001.02 and CAMT.053.001.02 InsideBusiness Connect InsideBusiness Payments SwiftNet FileAct EBICS Document version history Version Date Changes 1.0 First version 2.0 14-02-2014 Updated

More information

Message Definition Report

Message Definition Report Approved by the ISO 20022 RMG Message Definition Report Model: pacs.008.001.06 Version: 1.0 Issue Date: 15/04/2016 Author: ISO 20022 RTPG Contents History... 3 Introduction... 3 History Version Date Authors

More information

XML CONVERTING LLOYDSLINK FASTER PAYMENT XML FILES. Importing Payments in Commercial Banking Online

XML CONVERTING LLOYDSLINK FASTER PAYMENT XML FILES. Importing Payments in Commercial Banking Online XML Ò CONVERTING LLOYDSLINK FASTER PAYMENT XML FILES Importing Payments in Commercial Banking Online Import your Payment Files in Commercial Banking Online In Commercial Banking Online all Payment Files

More information

camt Debit Notification BankToCustomerDebitCreditNotificationV02

camt Debit Notification BankToCustomerDebitCreditNotificationV02 orporate Access Payables Message Implementation Guidelines camt.054.001.02 Debit Notification BankToustomerDebitreditNotificationV02 These Message Implementation Guidelines only include a description of

More information

camt Account Statement BankToCustomerStatementV02

camt Account Statement BankToCustomerStatementV02 Corporate Access Account eporting Message Implementation Guidelines BankToCustomerStatementV02 MIG version: 1.00 : Corporate Access Account eporting version 1.0 2 of 10 Table of contents 1. Introduction...

More information

camt Debit Notification BankToCustomerDebitCreditNotificationV02

camt Debit Notification BankToCustomerDebitCreditNotificationV02 orporate Access Payables Message Implementation Guidelines camt.054.001.02 Debit Notification BankToustomerDebitreditNotificationV02 These Message Implementation Guidelines only include a description of

More information

Bankline XML standard import format

Bankline XML standard import format Bankline XML standard import format Bankline XML standard import format Contents Introduction to Bankline XML import... 2 What is Bankline XML import?... 2 How do I structure a Bankline XML import format?...

More information

Usage rules of the SEB data exchange format based on ISO XML standard messages. Version 2.5 (effective from )

Usage rules of the SEB data exchange format based on ISO XML standard messages. Version 2.5 (effective from ) Usage rules of the SEB data exchange format based on ISO 20022 XML standard messages Version 2.5 (effective from 2017-11-19) Document version history Version Date Amendments 1.21 2013-09-19 Removed unused

More information

ipko biznes input file structure international transfers (MT103 / CSV / XML ISO20022)

ipko biznes input file structure international transfers (MT103 / CSV / XML ISO20022) ipko biznes input file structure international transfers (T103 / SV / XL ISO20022) ONTENTS General information... 3 PLA / T103 file structure... 3 File format description... 3 PLA / T103 file structure...

More information

STET PSD2 API. Documentation. Author: Robache Hervé. Date: Version: (English)

STET PSD2 API. Documentation. Author: Robache Hervé. Date: Version: (English) STET PSD2 API Documentation Author: Robache Hervé Date: 2017-11-15 Version: 1.2.3 (English) Table of content 1. INTRODUCTION... 7 1.1. Context... 7 1.2. Mission... 7 1.3. Licence... 8 2. BUSINESS MODEL...

More information

ISO TRANSACTION REPORTING GUIDE. v 1.3

ISO TRANSACTION REPORTING GUIDE. v 1.3 ISO 20022 TRANSACTION REPORTING GUIDE v 1.3 4.10.2012 1 ISO 20022 Transaction Reporting Guide Table of contents 1 Introduction... 2 2 General... 2 3 Notification message structure... 3 3.1 Group Header

More information

camt Debit Notification BankToCustomerDebitCreditNotificationV02

camt Debit Notification BankToCustomerDebitCreditNotificationV02 orporate Access Payables Message Implementation Guidelines camt.054.001.02 Debit Notification BankToustomerDebitreditNotificationV02 These Message Implementation Guidelines only include a description of

More information

camt BankToCustomerStatementV02

camt BankToCustomerStatementV02 Corporate egateway Message Implementation Guideline camt.053.001.02 BankToCustomerStatementV02 MIG version: 1.4 : 2018.11.26 2 of 10 Table of Contents 1. Introduction... 3 2. Scope... 3 3. Document references...

More information

DRAFT for NO: camt Credit Notification BankToCustomerDebitCreditNotificationV02

DRAFT for NO: camt Credit Notification BankToCustomerDebitCreditNotificationV02 orporate Access Account eporting Message Implementation Guidelines DAFT for NO: camt.054.001.02 redit Notification BankToustomerDebitreditNotificationV02 This Message Implementation Guide only includes

More information

OP Corporate Bank plc Latvia Branch

OP Corporate Bank plc Latvia Branch OP Corporate Bank plc Latvia Branch Data exchange standard used in the Internet bank ISO 20022 September 2017 Content 1. Introduction... 3 2. Payment Initiation Message pain.001.001.03... 4 3. Account

More information

ISO Cash Management

ISO Cash Management ISO 20022 Cash Management Swiss Implementation Guidelines for Customer-Bank Messages (Reports) Bank-to-Customer Account Report (camt.052) Bank-to-Customer Statement (camt.053) Bank-to-Customer Debit/Credit

More information

Swiss ISO Harmonization for Software Vendors Credit Suisse Best Practice Guide

Swiss ISO Harmonization for Software Vendors Credit Suisse Best Practice Guide Public Swiss ISO 20022 Harmonization for Software Vendors Credit Suisse Best Practice Guide CREDIT SUISSE (Switzerland) Ltd., Software Partner Management April 2017 Agenda Framework Page 3 Formats Page

More information

Customer Documentation Request for Information Message (camt.026 & camt.028)

Customer Documentation Request for Information Message (camt.026 & camt.028) Customer Documentation Request for ormation Message (camt.026 & camt.028) Version 2.2 April 2018 THIS DOCUMENT ( DOCUMENT ) IS PROVIDED UNDER THE TERMS OF THIS RTP DOCUMENTATION AGREEMENT ("AGREEMENT").

More information

INTRODUCTION TO THE ISO AFT USAGE GUIDELINES

INTRODUCTION TO THE ISO AFT USAGE GUIDELINES INTRODUCTION TO THE ISO 20022 AFT USAGE GUIDELINES INTRODUCTION 1.0 Scope This document outlines the specifications related to the formatting of CPA ISO 20022 Automated Funds Transfer (AFT) payment messages

More information

SEPA XML PAYMENTS ISO FILE FORMAT pain.001 via ALPHA WEB BANKING. OPERATIONAL and TECHNICAL SPECIFICATIONS

SEPA XML PAYMENTS ISO FILE FORMAT pain.001 via ALPHA WEB BANKING. OPERATIONAL and TECHNICAL SPECIFICATIONS PAYMENTS SEPA XML FILE FRMAT VIA ALPHA WEB BANKING SEPA XML PAYMENTS IS 20022 FILE FRMAT pain.001 via ALPHA WEB BANKING PERATINAL and TECHNICAL SPECIFICATINS VERSIN 1.3 1 PAYMENTS SEPA XML FILE FRMAT VIA

More information

camt BankToCustomerStatementV02

camt BankToCustomerStatementV02 Corporate egateway Message Implementation Guideline camt.053.001.02 BankToCustomerStatementV02 MIG version: 1.2 : 16-12-2013 2 of 7 Table of Contents 1. Introduction... 3 2. Scope... 3 3. Document references...

More information

SWIFT FIN MT103. Format Description

SWIFT FIN MT103. Format Description SWIFT FIN MT103 Format Description June 2018 Contents 1. SWIFT FIN MT103: SINGLE CUSTOMER CREDIT TRANSFER 3 1.1 Introduction 3 1.2 General information 3 1.3 Format Specification 3 2. TECHNICAL DESCRIPTION

More information

Status Report (pain.002) input files. General... 2 List of trigger codes... 2 Special cases Example Example

Status Report (pain.002) input files. General... 2 List of trigger codes... 2 Special cases Example Example General........................................................................... 2 List of trigger codes................................................................. 2 Special cases.......................................................................

More information

ING Format Description MT940 & MT942 Structured NL (V.4)

ING Format Description MT940 & MT942 Structured NL (V.4) ING Format MT940 & MT942 Structured NL (V.4) InsideBusiness Connect SwiftNet FIN SwiftNet FileAct EBICS The Netherlands Document version history Version Date Changes 1.0 20-11-2013 First version 2.0 14-02-2014

More information

International Securities Association For Institutional Trade Communication

International Securities Association For Institutional Trade Communication International Securities Association For Institutional Trade Communication MT103 Single Customer Credit Transfer Market Practice Guideline Presented by the United States Settlements/Cash/Treasury Working

More information

Category 2 Financial Institution Transfers

Category 2 Financial Institution Transfers SWIFTStandards Category 2 Financial Institution Transfers November 2003 Standards Release 1 Legal Notices Legal Notices IMPORTANT NOTE: You may install and use this publication only if you have entered

More information

ING Format Description

ING Format Description ING Format Structured MT940 & MT942 (Version 4) Strategic InsideBusiness Connect InsideBusiness Payments CEE SwiftNet FIN SwiftNet FileAct Telelink@Isabel EBICS Document version history Version Date Changes

More information

PSD2 API INTERFACE SPECIFICATION

PSD2 API INTERFACE SPECIFICATION PSD2 API INTERFACE SPECIFICATION CONTENTS Contents... 2 List of figures... 3 List of tables... 3 Document information... 4 List of acronyms... 5 References... 6 1 Introduction... 7 1.1 Main focus... 7

More information

Customer Documentation Message Status Report

Customer Documentation Message Status Report Customer Documentation Message Status Report Version 2.2 April 2018 THIS DOCUMENT ( DOCUMENT ) IS PROVIDED UNDER THE TERMS OF THIS RTP DOCUMENTATION AGREEMENT ("AGREEMENT"). ANY USE OR REPRODUCTION OF

More information

Message Definition Report

Message Definition Report Message Definition Report 2010-06-01 Table Of Contents Overview... 1 Scope... 1 Deployment... 1 How to read... 1... 2 Message Functionality... 2 Structure... 2 Rules and Guidelines... 11 Message Items

More information

SEPA DIRECT DEBIT SCHEME IMPLEMENTATION GUIDELINES

SEPA DIRECT DEBIT SCHEME IMPLEMENTATION GUIDELINES Doc: EPC114-06 13 December 2006 (Version 2.2) OITS SG SEPA DIRECT DEBIT SCHEME IMPLEMENTATION GUIDELINES Abstract Document Reference Issue This document sets out the SEPA rules for implementing the direct

More information

Bank Millennium. Millenet for Companies Specification for importing orders in XML format

Bank Millennium. Millenet for Companies Specification for importing orders in XML format Bank Millennium Millenet for Companies Specification for importing orders in XML format Table of content 1. Introduction...3 2. General rules to the XML files...3 3. Structure of file...4 4. XML file header...4

More information

Format Description MT942 Structured version Rabo Direct Connect, SWIFT FileAct & Rabo Internetbankieren (Professional)

Format Description MT942 Structured version Rabo Direct Connect, SWIFT FileAct & Rabo Internetbankieren (Professional) Format Description MT942 Structured version 1.0.1 Rabo Direct Connect, SWIFT FileAct & Rabo Internetbankieren (Professional) Contents 1. MT942 STRUCTURED INTERIM TRANSACTION REPORT 3 1.1 General information

More information

camt Credit Notification BankToCustomerDebitCreditNotificationV02

camt Credit Notification BankToCustomerDebitCreditNotificationV02 orporate Access Account eporting Message Implementation Guidelines camt.054.001.02 redit Notification BankToustomerDebitreditNotificationV02 This Message Implementation Guideline includes description of

More information

Customer Documentation System Time-Out / Request for Return of Funds (camt.056 & camt.029)

Customer Documentation System Time-Out / Request for Return of Funds (camt.056 & camt.029) Customer Documentation System Time-Out / Request for Return of Funds (camt.056 & camt.029) Version 2.2 April 2018 1 THIS DOCUMENT ( DOCUMENT ) IS PROVIDED UNDER THE TERMS OF THIS RTP DOCUMENTATION AGREEMENT

More information

SEPA Credit Transfer Customer-to-Bank Implementation Guidelines for the Netherlands

SEPA Credit Transfer Customer-to-Bank Implementation Guidelines for the Netherlands SEPA Credit Transfer Customer-to-Bank Implementation Guidelines for the Netherlands Disclaimer These guidelines may be subject to changes. Utmost care has been taken to ensure the information in this publication

More information

Wire & Internal Transfers

Wire & Internal Transfers Wire & Internal Transfers USER GUIDE Transfer funds easily and securely. Convenience. Transfer money between accounts at Union Bank and different banks domestically and internationally. Ease. Say goodbye

More information

Format Description MT940 Structured version 1.0. Rabo Direct Connect, SWIFT FileAct and Rabo Internetbanking (Professional)

Format Description MT940 Structured version 1.0. Rabo Direct Connect, SWIFT FileAct and Rabo Internetbanking (Professional) Format Description MT940 Structured version 1.0 Rabo Direct Connect, SWIFT FileAct and Rabo Internetbanking (Professional) January 2018 Contents 1. MT940 CUSTOMER STATEMENT MESSAGE 3 1.1 General information

More information

XML message for SEPA Credit Transfer Initiation Implementation Guidelines for the Netherlands

XML message for SEPA Credit Transfer Initiation Implementation Guidelines for the Netherlands XML message for SEPA Credit Transfer Initiation Implementation Guidelines for the Netherlands Disclaimer These guidelines may be subject to changes. Utmost care has been taken to ensure the information

More information

camt Account Statement Extended BankToCustomerStatementV02

camt Account Statement Extended BankToCustomerStatementV02 orporate Access Account eporting Message Implementation Guidelines camt.053.001.02 Account Statement Extended BankToustomerStatementV02 MIG version: 1.0 (DAFT) : This version is expected to be launched

More information

camt Account Statement Standard BankToCustomerStatementV02

camt Account Statement Standard BankToCustomerStatementV02 Corporate Access Account eporting Message Implementation Guidelines camt.053.001.02 Account Statement Standard BankToCustomerStatementV02 MIG version: 1.2 : This version is expected to be launched to the

More information

Format description MT940 Structured version Rabo Direct Connect, SWIFT FileAct & Rabo Internetbankieren (Professional)

Format description MT940 Structured version Rabo Direct Connect, SWIFT FileAct & Rabo Internetbankieren (Professional) Format description MT940 Structured version 1.0.2 Rabo Direct Connect, SWIFT FileAct & Rabo Internetbankieren (Professional) Contents 1. MT940 CUSTOMER STATEMENT MESSAGE 3 1.1 General information 3 1.2

More information

Message flow and use of XML ISO20022 Messages Corporate egateway

Message flow and use of XML ISO20022 Messages Corporate egateway Message flow and use of XML ISO20022 Messages Corporate egateway Table of contents 1 PURPOSE OF THIS GUIDE... ERROR! BOOKMARK NOT DEFINED. 2 INTRODUCTION... ERROR! BOOKMARK NOT DEFINED. 2.1 THE XML ISO20022

More information

Message Reference Guide. Category 2 - Financial Institution Transfers. Standards. For Standards MT November 2017

Message Reference Guide. Category 2 - Financial Institution Transfers. Standards. For Standards MT November 2017 Standards Category 2 - Financial Institution Transfers For Standards MT November 2017 Message Reference Guide This reference guide contains the category 2 message text standards, including a detailed description

More information

BANKING CIRCLE WEB BULK UPLOAD

BANKING CIRCLE WEB BULK UPLOAD 18109 Training Manual - BULK UPLOAD_Layout 1 11/05/2016 10:06 Page 1 Freedom to BANKING CIRCLE WEB BULK UPLOAD SAXO PAYMENTS INTERNET BANKING WHAT IS A BULK PAYMENT? A bulk payment is defined as a payment

More information

XML message for SEPA Direct Debit Initiation Implementation Guidelines for the Netherlands

XML message for SEPA Direct Debit Initiation Implementation Guidelines for the Netherlands XML message for SEPA Direct Debit Initiation Implementation Guidelines for the Netherlands Core and Business-to-Business Implementation Guidelines Disclaimer These guidelines may be subject to changes.

More information

Record Descriptions - lang

Record Descriptions - lang Record s - lang Online Banking 01-02-2018 1 Indholdsfortegnelse Introduction... 4 Bankdata format... 4 of fixed-length records... 6 Data name Field name.... 6 of variable-length records... 7 Payment start...

More information

Bankline. Import file layout guide SWIFT MT101 format

Bankline. Import file layout guide SWIFT MT101 format Bankline Import file layout guide SWIFT MT101 format Contents 1. Introduction to Bankline SWIFT MT101 import...2 1.1 What is Bankline SWIFT import?...2 1.2 Payment Type Derivation...2 1.3 SWIFT Character

More information