Corporate eGateway Message Implementation Guideline

1 Corporate eGateway Message Implementation Guideline CustomerCreditTransferInitiationV03 MIG version: Date: Nordea version Date Page 2020-06-29 2 of 25 Nordea Bank Abp, Satamaradankatu 5, FI-00020 NORDEA, Finland, domicile Helsinki, Business ID 2858394-9, VAT number FI28583949 Nordea Danmark, filial af Nordea Bank Abp, Finland, Business ID 2858394-9, Patent and Registration Office, CVR no. 25992180, Copenhagen Nordea Bank Abp, filial i Norge, Essendrops gate 7, PO box 1166 Sentrum, 0107 Oslo, Norway, 920058817 MVA (Norwegian Register of Business Enterprises) Nordea Bank Abp, filial i Sverige, 516411-1683, Swedish Companies Registration Office, VAT No.

2 Table of Contents 1. Introduction .. 3 2. Scope .. 3 3. Document references .. 3 4. Guideline .. 4 Nordea version Date Page 2020-06-29 3 of 25 Nordea Bank Abp, Satamaradankatu 5, FI-00020 NORDEA, Finland, domicile Helsinki, Business ID 2858394-9, VAT number FI28583949 Nordea Danmark, filial af Nordea Bank Abp, Finland, Business ID 2858394-9, Patent and Registration Office, CVR no. 25992180, Copenhagen Nordea Bank Abp, filial i Norge, Essendrops gate 7, PO box 1166 Sentrum, 0107 Oslo, Norway, 920058817 MVA (Norwegian Register of Business Enterprises) Nordea Bank Abp, filial i Sverige, 516411-1683, Swedish Companies Registration Office, VAT No.

3 1. Introduction The purpose of this documentation is to define how information in payment Messages should be structured for the exchange between the Message sender and Nordea. The terms and definitions used in this document are defined in a separate document, Glossary for Corpo-rate eGateway , which can be found on the Nordea Group s homepage: This Message Implementation Guide complies with the international definitions for content and use of an ISO20022 Customer Credit Transfer Initiation and Common Global Implementation (CGI) Credit Transfer Initiation recommendations. The files sent to Nordea must be in UTF-8 format, using only the characters included in ISO-8859-1.

4 This MIG does not include any technical issues such as security, retransmissions, or duplicates. For more information about Payment types, please read the document Payment Types Additional information about account number structure, and usage, can be found in the document Ac-counts in Both documents can be found at Nordea eGateway web page. Further information about ISO 20022 definitions in can be found in document Payments - Maintenance_2009 - Message Definition at Link: Please note, that Nordea do not accept LineBreak (CR LF) inside text elements. If LineBreak is included the file will fail in the processing, and will not be reported.

5 2. Scope The CustomerCreditTransferInitiation 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. 3. Document references This chapter contains references to documents relevant for this MIG: 1. ISO 20022, Payments Maintenance 2009, Approved by the Payments SEG on 30 March 2009, Message Definition Report, Edition September 2009, , CustomerCreditTransferInitiationV03 Nordea version Date Page 2020-06-29 4 of 25 Nordea Bank Abp, Satamaradankatu 5, FI-00020 NORDEA, Finland, domicile Helsinki, Business ID 2858394-9, VAT number FI28583949 Nordea Danmark, filial af Nordea Bank Abp, Finland, Business ID 2858394-9, Patent and Registration Office, CVR no.

6 25992180, Copenhagen Nordea Bank Abp, filial i Norge, Essendrops gate 7, PO box 1166 Sentrum, 0107 Oslo, Norway, 920058817 MVA (Norwegian Register of Business Enterprises) Nordea Bank Abp, filial i Sverige, 516411-1683, Swedish Companies Registration Office, VAT No. 4. Guideline ISO Index Or Payment Initiation Message Item XML Tag ISO Mult. Type Nordea comment Customer Credit Transfer Initiation <CstmrCdt- TrfInitn> CustomerCreditTransfer- InitiationV03 Used to request movement of funds from debtor's account to a creditor. GroupHeader <GrpHdr> [ ] GroupHeader32 MessageIdentification <MsgId> [ ] Max35 Text This Id will be stored for 90 days and will be used for duplicate control.

7 Will be returned in status report. CreationDateTime <CreDtTm> [ ] ISODateTime NumberOfTransactions <NbOfTxs> [ ] Max15 NumericText InitiatingParty <InitgPty> [ ] PartyIdentification32 Name <Nm> [ ] Max140 Text Russia: This must include the name of the customer holding the Corporate eGateway agreement with the bank. The name must also be stated in accordance with the Instructing Party in the local agreement in Nordea Russia. The maximum length is 35 characters. Identification <Id> [ ] Party6 Choice Required by CGI. {Or OrganisationIdentification <OrgId> [ ] OrganisationIdentification4 Required by CGI.}

8 BICOrBEI <BICOrBEI> [ ] AnyBICI dentifier Presently not used. Other <Othr> [ ] GenericOrganisation- Identification1 Identification <Id> [ ] Max35 Text Required by CGI. The agreement Identification that is agreed with Nordea. SchemeName <SchmeNm> [ ] OrganisationIdentification-SchemeName1 Choice Code <Cd> [ ] ExternalOrganisation- Identification1 Code Required by Nordea. CUST is the agreement Identification that is agreed by Nordea. Allowed Codes: CUST CustomerNumber Proprietary <Prtry> [ ] Max35 Text Not used.

9 Or} PrivateIdentification <PrvtId> [ ] PersonIdentification5 Not used. Nordea version Date Page 2020-06-29 5 of 25 Nordea Bank Abp, Satamaradankatu 5, FI-00020 NORDEA, Finland, domicile Helsinki, Business ID 2858394-9, VAT number FI28583949 Nordea Danmark, filial af Nordea Bank Abp, Finland, Business ID 2858394-9, Patent and Registration Office, CVR no. 25992180, Copenhagen Nordea Bank Abp, filial i Norge, Essendrops gate 7, PO box 1166 Sentrum, 0107 Oslo, Norway, 920058817 MVA (Norwegian Register of Business Enterprises) Nordea Bank Abp, filial i Sverige, 516411-1683, Swedish Companies Registration Office, VAT No.

10 ISO Index Or Payment Initiation Message Item XML Tag ISO Mult. Type Nordea comment PaymentInformation <PmtInf> [ ] PaymentInstruction- Information3 All credit transfer transactions for the same debit account, payment date and currency must be stated under the same Payment level. For all payments from Russia and UK, and for international and high value payments from Sweden and the US, only 999 occurrences are allowed per PaymentInformation. For all other payment types a maximum of instances of <PaymentInformation> is allowed. PaymentInformationIdentification <PmtInfId> [ ] Max35 Text Will be returned in a Status Report PaymentMethod <PmtMtd> [ ] PaymentMethod3 Code CHK only valid for Canada and USA and International payment to cheque, including SWIFT to cheque.