Corporate Payments Service Payments from Latvia, Lithuania and Estonia example appendix

Size: px
Start display at page:

Download "Corporate Payments Service Payments from Latvia, Lithuania and Estonia example appendix"

Transcription

1 Corporate Payments Service Payments from Latvia, Lithuania and Estonia example appendix pain.001 version 3 pain.002 version 3 pain.006 version 1 May 2013

2 Content 1. Background About Corporate Payments Service Message structure County specific message structure Estonia Example of the payment initiation message Latvia Description Message content XML example Lithuania Description Message content XML example Estonia Description Message content XML example Additional instructions Service ID Defining the payment type Latvia Lithuania: Estonia: Character set and special characters Payer s identifications for the payment Creditor reference on credit transfer Clearing codes Charges Use of postal address Debit entry By order of Ultimate beneficiary Salary and pension payments Purpose code Restrictions on Remittance Information Payments to Russia Need to be clarified Cover bank / intermediary bank Instructions to payer s bank Payment Status Report Content of the feedback message Accepted technical validation Examples of feedback on reception checks Payment debited and forwarded for processing Payment of transaction pending due to lack of cover Reasons for rejections... 81

3 7. Cancellation requests Examples of cancellation requests Cancellation request for a single batch Content of the cancellation request XML example Cancellation request for several batches Cancellation request for a single payment transaction Content of the cancellation request XML example Cancellation request for several payments May

4 1. Background This description presents the content of XML payment files with examples. The payment message and the related feedback conform to the ISO20022 standard approved in The following messages are included: Schema name Message name Message content pain CustomerCreditTransferInitiationV03 Payments pain CustomerPaymentStatusReportV03 Feedback pain PaymentCancellationRequestV01 Cancellation The goal is to enable smooth introduction of the service in companies. This appendix will be amended as the service is expanded; changes are possible. 2. About Corporate Payments Service Corporate Payments Service covers the processing of ordinary SEPA credit transfers, salaries and pensions, internal and domestic payments and foreign currency payments. 3. Message structure The general payment message structure is described in the Corporate Payments Service service description. See also the Federation of Finnish Financial Services publication ISO payments guide and ISO documentation. The term message is used for one XML schema occurrence, which is a combination of blocks called Group Header, Payment Information and Credit Transfer Transaction Information. Section XML example in this document contains one XML message. One file may contain several messages. A message sent to Nordea can contain payments from several payers (different service ID). One file may contain several payment messages, but for more efficient processing of the files we recommend that one file only contains one message. The schema name for Customer Credit Transfer Initiation is <pain >. 3.1 County specific message structure Estonia See the Estonaian banking Assotiation s webpage for latest information page itself in Estonian but all documents linked there are in English: Latest payment description is 1.1 ( ): r%20to%20bank _ver1%201.pdf May

5 4. Example of the payment initiation message 4.1 Latvia Description Payment 1: Urgent domestic payment Debtor: Name IBAN account number BIC Creditor: Name Country Address IBAN account number BIC Payment: Payment type Test Company SIA LV15NDEA NDEALV2X Creditor Company LV Ūnijas 35, Rīga, LV-2010, Latvija LV63HABA HABALV22 Urgent Requested execution date Payment amount Payment currency Additional identification given by the payer, not forwarded to the beneficiary (Instruction Identification) - Payment order Nr LVL I The unique transaction identification given by the payer (End To End Identification) E Remittance information (unstructured) - payment details rēķins Nr. RF Payment 2: Domestic payment Debtor: Name Test Company SIA IBAN account number LV15NDEA BIC NDEALV2X Creditor: Name ABC SIA Country LV Address Ģertrūdes 17, Rīga, LV-1310, Latvija IBAN account number LV14UNLA BIC UNLALV2X Payment: Payment amount Requested execution date Payment currency LVL Additional identification given by the payer, not forwarded to the beneficiary (Instruction Identification) - Payment order Nr I May

6 The unique transaction identification given by the payer (End To End Identification) E Remittance information (unstructured) - payment details Rēķina PK samaksa Payment 3: Cross border payment Debtor: Name IBAN account number BIC Test Company SIA LV15NDEA NDEALV2X Creditor: Name Beneficiary county Address Hyatt Central, US New York Account number BIC BANKUS33 Payment: Payment ammount 4, Payment currency Additional identification given by the payer, not forwarded to the beneficiary (Instruction Identification) - Payment order Nr USD I The unique transaction identification given by the payer (End To End Identification) E Remittance information (unstructured) - payment details Invoices 123 and 321 Payment 4: Urgent cross border payment Debtor: Name IBAN account number BIC Test Company SIA LV15NDEA NDEALV2X Creditor: Name County Address Ben E. Ficiary US Boston Account number Clearing code of the beneficiary s bank (US ABA number) Payment: Payment type urgent Payment ammount 55, Payment currency Additional identification given by the payer, not forwarded to the beneficiary (Instruction Identification) - Payment order Nr USD I The unique transaction identification given by the payer (End To End Identification) E Payment reason code 151 Remittance information (unstructured) - payment details Invoices 123 and 321 May

7 Payment 5: RUB payment to Russia Debtor: Name IBAN account number BIC Beneficiary: Name Address Test Company SIA LV15NDEA NDEALV2X Company Moscow Account number INN code Beneficiary Bank: Name Country Address Clearing code INN Moscow Bank RU Main street, Moscow RUCBC Clearing system member ID Correspondent account number of the beneficiary s bank Payment: Payment ammount 55, Payment currency Additional identification given by the payer, not forwarded to the beneficiary (Instruction Identification) - Payment order Nr RUB I The unique transaction identification given by the payer (End To End Identification) E Remittance information (unstructured) - payment details Invoices 123 and 321 Code for subject of payment in accordance with the regulations of the Central Bank of Russia VO12345 Payment 6: Salary payments Debtor: Name IBAN account number BIC Creditor: Name Test Company SIA LV15NDEA NDEALV2X Jānis Kalniņš Legal ID IBAN account number BIC Payment: LV14UNLA UNLALV2X Payment ammount Payment currency LVL Additional identification given by the payer, not forwarded to the beneficiary (Instruction Identification) - Payment order Nr I The unique transaction identification given by the payer (End To End Identification) E Remittance information (unstructured) - payment details Alga par Creditor: May

8 Name Andris Bērziņš Legal ID IBAN account number BIC Payment: LV14NDEA NDEALV2X Payment ammount Payment currency Additional identification given by the payer, not forwarded to the beneficiary (Instruction Identification) - Payment order Nr LVL I The unique transaction identification given by the payer (End To End Identification) E Remittance information (unstructured) - payment details Alga par May

9 4.1.2 Message content The example message table does not have all the elements of the ISO standard. If the customer gives extra information which the service does not check and cannot utilise or forward in the payment chain, the information is not processed or is cut off. The extra information does not cause the rejection of the payment unless it is checked (as, for example, too long Remittance Information). The examples cover the most important payment types and the information needed for them. The examples also contain optional information but do not cover all possible payment alternatives. Message item XML tag M/O Content Comment A. GroupHeader <GrpHdr> [1..1] MessageIdentification <MsgId> [1..1] CreationDateTime <CreDtTm> [1..1] T10:30:00 Mandatory, unique for at least 3 months. May not contain special characters Mandatory, valid values: current date -30 and +1 calendar days NumberOfTransactions <NbOfTxs> [1..1] 5 Mandatory, number of transactions (C-level) ControlSum <CtrlSum> [0..1] Optional. Sum of amounts at C-level. InitiatingParty <InitgPty> [1..1] Mandatory Name <Nm> [0..1] Identification [0..1] OrganisationIdentification <OrgId> [0..1] Other <Othr> [1..1] Test Company SIA Recommended to use the name Identification [1..1] Service Id given by Nordea. Mandatory either in element GroupHeader or PaymentInformation. If given in PaymentInformation element, the Id given in GroupHeader is not taken into account in the batch in question. SchemeName <SchmeNm> [1..1] Code <Cd> [1..1] BANK BANK = BankPartyIdentification, ExternalCode value B. PaymentInformation <PmtInf> First debit batch PaymentInformationIdentification <PmtInfId> [0..1] Optional, recommended, unique for at least 3 months. May not contain special characters PaymentMethod <PmtMtd> [1..1] TRF Mandatory, Transfer BatchBooking <BtchBookg> [0..1] FALSE Not mandatory, default value false RequestedExecutionDate <ReqdExctnDt> [1..1] Debtor <Dbtr> [1..1] Name <Nm> [1..1] Test Company SIA Mandatory, valid values: max +90 and -5 calendar days Mandatory The name of the accountholder is transmitted to the beneficiary from Nordea s customer register. PostalAddress <PstlAdr> [0..1] Country <Ctry> [1..1] LV Optional AddressLine <AdrLine> [0..1] Ielas nosaukums 14 Optional AddressLine <AdrLine > [0..1] Pasta indeks, Pilsēta Optional Identification [1..1] May

10 OrganisationIdentification <OrgId> [1..1] Other <Othr> [1..1] Identification [0..1] Mandatory if not given on GroupHeader level. Service Id given by Nordea. If given in PaymentInformation element, the Id given in GroupHeader is not taken into account in this batch. SchemeName <SchmeNm> [1..1] Code <Cd> [1..1] BANK BANK = BankPartyIdentification, ExternalCode value DebtorAccount <DbtrAcct> [1..1] Identification [1..1] IBAN <IBAN> [1..1] LV15NDEA Mandatory, payer s account in IBAN format DebtorAgent <DbtrAgt> [1..1] FinancialInstitutionIdentification <FinInstnId> [1..1] BIC <BIC> [1..1] NDEALV2X Mandatory, payer bank s BIC ChargeBearer <ChrgBr> [0..1] SHAR Optional. Default value: shared charges. C. CreditTransferTransaction Information (1st payment) <CdtTrfTxInf> [1..n] Credit information - Urgent domestic payment PaymentIdentification <PmtId> [1..1] Double check using the combination of Instruction Id (optional) and EndtoEnd Id (mandatory). InstructionIdentification <InstrId> [0..1] I If present, Id to be returned only to ordering party in account statement reporting EndToEndIdentification <EndToEndId> [1..1] E Mandatory, unique for at least 3 months. May not contain special characters PaymentTypeInformation <PmtTpInf> [0..1] Payment type ServiceLevel <SvcLvl> [0..1] Code <Cd> [0..1] URGP Urgent payment Amount <Amt> [1..1] InstructedAmount <InstdAmt> [1..1] LVL Mandatory, instructed amount CreditorAgent <CdtrAgt> [0..1] FinancialInstitutionIdentification <FinInstnId> [0..1] BIC <BIC> [0..1] HABALV22 BIC of beneficiary s bank is optional for SEPA credit transfers. If not given, Nordea will derive BIC from IBAN. Creditor <Cdtr> [0..1] Name <Nm> [1..1] Creditor Company Mandatory, creditor name PostalAddress <PstlAdr> [0..1] AddressLine <AdrLine> [0..1] Ūnijas 35, Rīga, Optional, recommended AddressLine <AdrLine > [0..1] LV-2010, Latvija Optional, recommended Country <Ctry> [1..1] LV Mandatory if address is given CreditorAccount <CdtrAcct> [0..1] May

11 Identification [1..1] IBAN <IBAN> [1..1] LV63HABA Mandatory, creditor IBAN RemittanceInformation <RmtInf> [0..1] Optional, payment specifications Unstructured <Ustrd> [0..1] rēķins Nr. RF One occurrence (max 140 characters) C. CreditTransferTransaction Information (2nd payment) <CdtTrfTxInf> [1..n] Credit information - Domestic payment PaymentIdentification <PmtId> [1..1] InstructionIdentification <InstrId> [0..1] I EndToEndIdentification <EndToEndId> [1..1] E Double check using the combination of Instruction Id (optional) and EndtoEnd Id (mandatory). If present, Id to be returned only to ordering party in account statement reporting Mandatory, unique for at least 3 months. May not contain special characters including å, ä and ö Amount <Amt> [1..1] InstructedAmount <InstdAmt> [1..1] LVL Mandatory, instructed amount CreditorAgent <CdtrAgt> [0..1] FinancialInstitutionIdentification <FinInstnId> [0..1] BIC <BIC> [0..1] UNLALV2X BIC of beneficiary s bank is optional for SEPA credit transfers. If not given, Nordea will derive BIC from IBAN. Creditor <Cdtr> [0..1] Name <Nm> [1..1] ABC SIA Mandatory, creditor name PostalAddress <PstAdr> [0..1] Country <Ctry> [1..1] LV Mandatory if address is given AddressLine <AdrLine> [0..1] Ģertrūdes 17, Rīga, Optional, recommended AddressLine <AdrLine> [0..1] LV-1310, Latvija Optional, recommended CreditorAccount <CdtrAcct> [0..1] Identification [1..1] IBAN <IBAN> [1..1] LV14UNLA Mandatory, creditor IBAN in SEPA credit transfers RemittanceInformation <RmtInf> [0..1] Optional, payment specifications Unstructured <Ustrd> [0..1] Rēķina PK samaksa One occurrence (max 140 characters) of freeform text is transmitted to AOS2 banks. C. CreditTransferTransaction Information (3rd payment) <CdtTrfTxInf> [1..n] Credit information - cross-border payment PaymentIdentification <PmtId> [1..1] InstructionIdentification <InstrId> [0..1] I Double check using the combination of Instruction Id (optional) and EndtoEnd Id (mandatory). If present, Id to be returned only to ordering party in account statement reporting EndToEndIdentification <EndToEndId> [1..1] E Mandatory, unique for at least 3 months. May not contain special characters Amount <Amt> [1..1] May

12 InstructedAmount <InstdAmt> [1..1] USD Mandatory, instructed amount CreditorAgent <CdtrAgt> [0..1] FinancialInstitutionIdentification <FinInstnId> [0..1] BIC <BIC> [0..1] BANKUS33 BIC of beneficiary s bank is optional for SEPA credit transfers. If not given, Nordea will derive BIC from IBAN. Creditor <Cdtr> [0..1] Name <Nm> [1..1] Hyatt Central, Mandatory, creditor name PostalAddress <PstlAdr> [0..1] Country <Ctry> [1..1] US Mandatory if address is given AdressLine <AdrLine> [0..2] New York Information that locates and identifies a specific address, as defined by postal services, presented in free format text CreditorAccount <CdtrAcct> [0..1] Identification [1..1] Other <Othr> [1..1] Identification [1..1] Identification assigned by an institution RegulatoryReporting <RgltryRptg> [0..10] Information needed due to regulatory and statutory requirements Details <Dtls> [0..n] Code <Cd> [0..1] 151 Payment reason code RemittanceInformation <RmtInf> [0..1] Optional, payment specifications Unstructured <Ustrd> [0..1] C. CreditTransferTransaction Information (4th payment) <CdtTrfTxInf> [1..n] PaymentIdentification <PmtId> [1..1] Invoices 123 and 321 One occurrence (max 140 characters) Credit information - Urgent cross-border payment Double check using the combination of Instruction Id (optional) and EndtoEnd Id (mandatory). InstructionIdentification <InstrId> [0..1] I If present, Id to be returned only to ordering party in account statement reporting EndToEndIdentification <EndToEndId> [1..1] E Mandatory, unique for at least 3 months. May not contain special characters PaymentTypeInformation <PmtTpInf> [0..1] Payment type ServiceLevel <SvcLvl> [0..1] Code <Cd> [0..1] URGP Urgent payment Amount <Amt> [1..1] InstructedAmount <InstdAmt> [1..1] USD Mandatory, instructed amount CreditorAgent <CdtrAgt> [1..1] Beneficiary s bank mandatory. Either BIC or clearing code and/or name and address (in the example) is required FinancialInstitutionIdentification <FinInstnId> [1..1] In the example the beneficiary s bank is expressed with the clearing code. When the clearing code is used, the bank s name and address are required, if known. May

13 If the bank s information is entered without the BIC or the clearing code, the name, address information and the bank s country code must be entered. ClearingSystemMemberIdentification <ClrSysMmbId> [0..1] Clearing code ClearingSystemIdentification <ClrSysId> [0..1] Code <Cd> [0..1] USABA US ABA number (Fedwire). See additional information in section Clearing codes. MemberIdentification <MmbId> [1..1] Clearing number Name <Nm> [0..1] BANK OF STATES Bank s name PostalAddress <PstAdr> [0..1] CountrySubDivision <CtrySubDvsn> [0..1] MASSACHUSETTS Optional, recommended Country <Ctry> [0..1] US Optional, recommended Creditor <Cdtr> [1..1] Name <Nm> [1..1] Ben E. Ficiary Mandatory PostalAddress <PstAdr> [0..1] Country <Ctry> [1..1] US Mandatory if address is given AdressLine <AdrLine> [0..2] Boston Information that locates and identifies a specific address, as defined by postal services, presented in free format text CreditorAccount <CdtrAcct> [0..1] Mandatory for credit transfers Identification [1..1] Other <Othr> [1..1] Identification [1..1] Other than IBAN account number is presented with Identification information only. SchemeName / Code, eg BBAN, can be given but is not necessary. RegulatoryReporting <RgltryRptg> [0..10] Information needed due to regulatory and statutory requirements Details <Dtls> [0..n] Code <Cd> [0..1] 151 Payment reason code RemittanceInformation <RmtInf> [0..1] Optional, payment specifications Unstructured <Ustrd> [0..1] Invoices 123 and 321 One occurrence (max 70 characters) of free text is forwarded in foreign currency payments. EndToEnd Id reserves 35 characters. C. CreditTransferTransaction Information (5th payment) <CdtTrfTxInf> [1..n] Credit information - RUB payments to Russia PaymentIdentification <PmtId> [1..1] InstructionIdentification <InstrId> [0..1] I Double check using the combination of Instruction Id (optional) and EndtoEnd Id (mandatory). If present, Id to be returned only to ordering party in account statement reporting EndToEndIdentification <EndToEndId> [1..1] E Mandatory, unique for at least 3 months. May not contain special characters May

14 Amount <Amt> [1..1] InstructedAmount <InstdAmt> [1..1] RUB Mandatory, instructed amount CreditorAgent <CdtrAgt> [1..1] Beneficiary s bank mandatory. Either BIC or clearing code and/or name and address (in the example) is required In the example the beneficiary s bank is expressed with the clearing code. When the clearing code is used, the bank s name and address are required, if known. FinancialInstitutionIdentification <FinInstnId> [1..1] If the bank s information is entered without the BIC or the clearing code, the name, address information and the bank s country code must be entered. ClearingSystemMemberIdentification <ClrSysMmbId> [0..1] Clearing code ClearingSystemIdentification <ClrSysId> [0..1] Code <Cd> [0..1] RUCBC See additional information in section Clearing codes. MemberIdentification <MmbId> [1..1] Clearing number Name <Nm> [0..1] Moscow Bank Bank s name PostalAddress <PstAdr> [0..1] Country <Ctry> [0..1] RU Optional, recommended AdressLine <AdrLine> [0..2] Main street AdressLine <AdrLine> [0..2] Moscow Information that locates and identifies a specific address, as defined by postal services, presented in free format text Information that locates and identifies a specific address, as defined by postal services, presented in free format text CreditorAgentAccount <CdtrAgtAcct> [0..1] Identification [1..1] Other <Othr> [1..1] Identification [1..1] Creditor <Cdtr> [1..1] Name <Nm> [1..1] Company Mandatory PostalAddress <PstAdr> [0..1] Country <Ctry> [1..1] RU Mandatory if address is given AdressLine <AdrLine> [0..2] Moscow Information that locates and identifies a specific address, as defined by postal services, presented in free format text CreditorAccount <CdtrAcct> [0..1] Mandatory for credit transfers Identification [1..1] Other <Othr> [1..1] Identification [1..1] / INN Other than IBAN account number is presented with Identification information only. INN code is given at the end of account number separated with / May

15 RegulatoryReporting <RgltryRptg> [0..10] Information needed due to regulatory and statutory requirements Details <Dtls> [0..n] Code <Cd> [0..1] 151 Payment reason code RemittanceInformation <RmtInf> [0..1] Optional, payment specifications Unstructured <Ustrd> [0..1] (VO12345) Invoices 123 and 321 One occurrence (max 70 characters) of free text is forwarded in foreign currency payments. EndToEnd Id reserves 35 characters. Salary payments Message item XML tag M/O Content Comment A. GroupHeader <GrpHdr> [1..1] MessageIdentification <MsgId> [1..1] CreationDateTime <CreDtTm> [1..1] T10:30:00 Mandatory, unique for at least 3 months. May not contain special characters Mandatory, valid values: current date -30 and +1 calendar days NumberOfTransactions <NbOfTxs> [1..1] 2 Mandatory, number of transactions (C-level) ControlSum <CtrlSum> [0..1] Optional. Sum of amounts at C-level. InitiatingParty <InitgPty> [1..1] Mandatory Name <Nm> [0..1] Test Company SIA Recommended to use the name B. PaymentInformation <PmtInf> First debit batch PaymentInformationIdentification <PmtInfId> [0..1] Optional, recommended, unique for at least 3 months. May not contain special characters PaymentMethod <PmtMtd> [1..1] TRF Mandatory, Transfer BatchBooking <BtchBookg> [0..1] true Not mandatory, default value false PaymentTypeInformation <PmtTpInf> [0..1] CategoryPurpose <CtgyPurp> [0..1] Code <Cd> [1..1] SALA for pension payments PENS RequestedExecutionDate <ReqdExctnDt> [1..1] Mandatory, valid values: max +90 and -5 calendar days Debtor <Dbtr> [1..1] Name <Nm> [1..1] Test Company SIA Mandatory The name of the accountholder is transmitted to the beneficiary from Nordea s customer register. PostalAddress <PstlAdr> [0..1] Country <Ctry> [1..1] LV Optional AddressLine <AdrLine> [0..1] Ielas nosaukums 14 Optional AddressLine <AdrLine > [0..1] Pasta indeks, Pilsēta Optional Identification [1..1] OrganisationIdentification <OrgId> [1..1] Other <Othr> [1..1] May

16 Identification [0..1] Mandatory if not given on GroupHeader level. Service Id given by Nordea. If given in PaymentInformation element, the Id given in GroupHeader is not taken into account in this batch. SchemeName <SchmeNm> [1..1] Code <Cd> [1..1] BANK DebtorAccount <DbtrAcct> [1..1] BANK = BankPartyIdentification, ExternalCode value Identification [1..1] IBAN <IBAN> [1..1] LV15NDEA Mandatory, payer s account in IBAN format DebtorAgent <DbtrAgt> [1..1] FinancialInstitutionIdentification <FinInstnId> [1..1] BIC <BIC> [1..1] NDEALV2X Mandatory, payer bank s BIC ChargeBearer <ChrgBr> [0..1] SHAR Optional. Default value: shared charges. C. CreditTransferTransaction Information (1st payment) <CdtTrfTxInf> [1..n] Credit information - Salary 1st beneficiary PaymentIdentification <PmtId> [1..1] Double check using the combination of Instruction Id (optional) and EndtoEnd Id (mandatory). InstructionIdentification <InstrId> [0..1] EndToEndIdentification <EndToEndId> [1..1] Amount <Amt> [1..1] I E If present, Id to be returned only to ordering party in account statement reporting Mandatory, unique for at least 3 months. May not contain special characters InstructedAmount <InstdAmt> [1..1] LVL Mandatory, instructed amount CreditorAgent <CdtrAgt> [0..1] FinancialInstitutionIdentification <FinInstnId> [0..1] BIC <BIC> [0..1] Creditor <Cdtr> [0..1] Name <Nm> [1..1] Identification [0..1] PrivateIdentification <PrvtId> [1..1] Other <Othr> [0..n] Identification [1..1] CreditorAccount <CdtrAcct> [0..1] Identification [1..1] UNLALV2X Jānis Kalniņš BIC of beneficiary s bank is optional for SEPA credit transfers. If not given, Nordea will derive BIC from IBAN. Mandatory, creditor name Optional IBAN <IBAN> [1..1] LV14UNLA Mandatory, creditor IBAN RemittanceInformation <RmtInf> [0..1] Optional, payment specifications May

17 Unstructured <Ustrd> [0..1] C. CreditTransferTransaction Information (2nd payment) <CdtTrfTxInf> [1..n] Alga par One occurrence (max 140 characters) Credit information - Salary 2nd beneficiary PaymentIdentification <PmtId> [1..1] Double check using the combination of Instruction Id (optional) and EndtoEnd Id (mandatory). InstructionIdentification <InstrId> [0..1] I If present, Id to be returned only to ordering party in account statement reporting EndToEndIdentification <EndToEndId> [1..1] E Mandatory, unique for at least 3 months. May not contain special characters Amount <Amt> [1..1] InstructedAmount <InstdAmt> [1..1] LVL Mandatory, instructed amount CreditorAgent <CdtrAgt> [0..1] FinancialInstitutionIdentification <FinInstnId> [0..1] BIC <BIC> [0..1] NDEALV2X BIC of beneficiary s bank is optional for SEPA credit transfers. If not given, Nordea will derive BIC from IBAN. Creditor <Cdtr> [0..1] Name <Nm> [1..1] Identification [0..1] PrivateIdentification <PrvtId> [1..1] Other <Othr> [0..n] Identification [1..1] CreditorAccount <CdtrAcct> [0..1] Identification [1..1] Andris Bērziņš Mandatory, creditor name Optional IBAN <IBAN> [1..1] LV14NDEA Mandatory, creditor IBAN RemittanceInformation <RmtInf> [0..1] Optional, payment specifications Unstructured <Ustrd> [0..1] Alga par One occurrence (max 140 characters) May

18 4.1.3 XML example Note! The beginning of the message must include a defined schemalocation as in the example below. <?xml version="1.0" encoding="utf-8"?> <Document xmlns="urn:iso:std:iso:20022:tech:xsd:pain " xmlns:xsi=" xsi:schemalocation="urn:iso:std:iso:20022:tech:xsd:pain pain xsd"> <CstmrCdtTrfInitn> <GrpHdr> <MsgId> </MsgId> <CreDtTm> T10:30:00</CreDtTm> <NbOfTxs>5</NbOfTxs> <CtrlSum> </CtrlSum> <InitgPty> <Nm>Test Company SIA</Nm> <OrgId> <Othr> <SchmeNm> <Cd>BANK</Cd> </SchmeNm> </Othr> </OrgId> </InitgPty> </GrpHdr> <!-- **************************************************************** Payment Information block **************************************************************** --> <PmtInf> <PmtInfId> </PmtInfId> <PmtMtd>TRF</PmtMtd> <BtchBookg>false</BtchBookg> <ReqdExctnDt> </ReqdExctnDt> <Dbtr> <Nm>Test Company SIA </Nm> <PstlAdr> <Ctry>LV</Ctry> <AdrLine>Ielas nosaukums 14</AdrLine> <AdrLine>Pasta indeks, Pilsēta</AdrLine> </PstlAdr> <OrgId> <Othr> <SchmeNm> <Cd>BANK</Cd> </SchmeNm> </Othr> </OrgId> </Dbtr> <DbtrAcct> <IBAN>LV15NDEA </IBAN> </DbtrAcct> <DbtrAgt> <FinInstnId> <BIC>NDEALV2X</BIC> </FinInstnId> </DbtrAgt> <ChrgBr>SHAR</ChrgBr> <!-- **************************************************************** 1. Urgent domestic payment **************************************************************** --> <CdtTrfTxInf> May

19 <PmtId> <InstrId>I000001</InstrId> <EndToEndId> E000001</EndToEndId> </PmtId> <PmtTpInf> <SvcLvl> <Cd>URGP</Cd> </SvcLvl> </PmtTpInf> <Amt> <InstdAmt Ccy="LVL">100.01</InstdAmt> </Amt> <CdtrAgt> <FinInstnId> <BIC>HABALV22</BIC> </FinInstnId> </CdtrAgt> <Cdtr> <Nm>Creditor Company</Nm> <PstlAdr> <Ctry>LV</Ctry> <AdrLine>Ūnijas 35, Rīga,</AdrLine> <AdrLine>LV-2010, Latvija</AdrLine> </PstlAdr> <OrgId> <Othr> </Othr> </OrgId> </Cdtr> <CdtrAcct> <IBAN>LV63HABA </IBAN> </CdtrAcct> <RmtInf> <Ustrd>rēķins Nr. RF </Ustrd> </RmtInf> </CdtTrfTxInf> <!-- **************************************************************** 2. Domestic payment **************************************************************** --> <CdtTrfTxInf> <PmtId> <InstrId>I000002</InstrId> <EndToEndId> E000002</EndToEndId> </PmtId> <Amt> <InstdAmt Ccy="LVL">100.01</InstdAmt> </Amt> <CdtrAgt> <FinInstnId> <BIC>UNLALV2X</BIC> </FinInstnId> </CdtrAgt> <Cdtr> <Nm>ABC SIA</Nm> <PstlAdr> <Ctry>LV</Ctry> <AdrLine>Ģertrūdes 17, Rīga, LV-1310, Latvija</AdrLine> </PstlAdr> <CtryOfRes>LV</CtryOfRes> </Cdtr> <CdtrAcct> <IBAN>LV14UNLA </IBAN> </CdtrAcct> <RgltryRptg> <Dtls> May

20 <Cd>111</Cd> </Dtls> </RgltryRptg> <RmtInf> <Ustrd>Rēķina PK samaksa</ustrd> </RmtInf> </CdtTrfTxInf> <!-- **************************************************************** 3. Cross-border payment **************************************************************** --> <CdtTrfTxInf> <PmtId> <InstrId>I000003</InstrId> <EndToEndId> E000003</EndToEndId> </PmtId> <Amt> <InstdAmt Ccy="USD"> </InstdAmt> </Amt> <CdtrAgt> <FinInstnId> <BIC>BANKUS33</BIC> </FinInstnId> </CdtrAgt> <Cdtr> <Nm>Hyatt Central, </Nm> <PstlAdr> <Ctry>US</Ctry> <AdrLine>New York</AdrLine> </PstlAdr> <CtryOfRes>US</CtryOfRes> </Cdtr> <CdtrAcct> <Othr> </Othr> </CdtrAcct> <RgltryRptg> <Dtls> <Cd>151</Cd> </Dtls> </RgltryRptg> <RmtInf> <Ustrd>Invoices 123 and 321</Ustrd> </RmtInf> </CdtTrfTxInf> <!-- **************************************************************** 4. Urgent cross-border payment **************************************************************** --> <CdtTrfTxInf> <PmtId> <InstrId>I000004</InstrId> <EndToEndId> E000004</EndToEndId> </PmtId> <PmtTpInf> <SvcLvl> <Cd>URGP</Cd> </SvcLvl> </PmtTpInf> <Amt> <InstdAmt Ccy="USD"> </InstdAmt> </Amt> <CdtrAgt> <FinInstnId> <ClrSysMmbId> <ClrSysId> <Cd>USABA</Cd> </ClrSysId> <MmbId> </MmbId> May

21 </ClrSysMmbId> <Nm>BANK OF STATES</Nm> <PstlAdr> <CtrySubDvsn>MASSACHUSETTS</CtrySubDvsn> <Ctry>US</Ctry> </PstlAdr> </FinInstnId> </CdtrAgt> <Cdtr> <Nm>Ben E. Ficiary</Nm> <PstlAdr> <Ctry>US</Ctry> <AdrLine>Boston</AdrLine> </PstlAdr> </Cdtr> <CdtrAcct> <Othr> </Othr> </CdtrAcct> <RgltryRptg> <Dtls> <Cd>151</Cd> </Dtls> </RgltryRptg> <RmtInf> <Ustrd>Invoices 123 and 321</Ustrd> </RmtInf> </CdtTrfTxInf> <!-- **************************************************************** 5. RUB payment to Russia **************************************************************** --> <CdtTrfTxInf> <!--5th payment. RUB payment to Russia --> <PmtId> <InstrId>I000005</InstrId> <EndToEndId> E000005</EndToEndId> </PmtId> <Amt> <InstdAmt Ccy="RUB"> </InstdAmt> </Amt> <CdtrAgt> <FinInstnId> <ClrSysMmbId> <ClrSysId> <Cd>RUCBC</Cd> </ClrSysId> <MmbId> </MmbId> </ClrSysMmbId> <Nm>Moscow Bank</Nm> <PstlAdr> <Ctry>RU</Ctry> <AdrLine>Main street</adrline> <AdrLine>Moscow</AdrLine> </PstlAdr> </FinInstnId> </CdtrAgt> <CdtrAgtAcct> <Othr> / INN </Othr> </CdtrAgtAcct> <Cdtr> <Nm>Company</Nm> <PstlAdr> <Ctry>RU</Ctry> <AdrLine>Moscow</AdrLine> </PstlAdr> May

22 </Cdtr> <CdtrAcct> <OrgId> </OrgId> <Othr> <Othr> </Othr> INN </Othr> </CdtrAcct> <RgltryRptg> <Dtls> <Cd>151</Cd> </Dtls> </RgltryRptg> <RmtInf> <Ustrd>(VO12345) Invoices 123 and 321</Ustrd> </RmtInf> </CdtTrfTxInf> </PmtInf> </CstmrCdtTrfInitn> </Document> Salary payment <?xml version="1.0" encoding="utf-8"?> <Document xmlns="urn:iso:std:iso:20022:tech:xsd:pain " xmlns:xsi=" xsi:schemalocation="urn:iso:std:iso:20022:tech:xsd:pain pain xsd"> <CstmrCdtTrfInitn> <GrpHdr> <MsgId> </MsgId> <CreDtTm> T10:30:00</CreDtTm> <NbOfTxs>2</NbOfTxs> <CtrlSum>301.02</CtrlSum> <InitgPty> <Nm>Test Company SIA</Nm> </InitgPty> </GrpHdr> <PmtInf> <PmtInfId> </PmtInfId> <PmtMtd>TRF</PmtMtd> <BtchBookg>true</BtchBookg> <PmtTpInf> <CtgyPurp> <Cd>SALA</Cd> </CtgyPurp> </PmtTpInf> <ReqdExctnDt> </ReqdExctnDt> <Dbtr> <Nm>Test Company SIA </Nm> <PstlAdr> <Ctry>LV</Ctry> <AdrLine>Ielas nosaukums 14</AdrLine> <AdrLine>Pasta indeks, Pilsēta</AdrLine> </PstlAdr> <OrgId> <Othr> <SchmeNm> <Cd>BANK</Cd> </SchmeNm> </Othr> </OrgId> </Dbtr> <DbtrAcct> <IBAN>LV15NDEA </IBAN> May

23 </DbtrAcct> <DbtrAgt> <FinInstnId> <BIC>NDEALV2X</BIC> </FinInstnId> </DbtrAgt> <ChrgBr>SHAR</ChrgBr> <CdtTrfTxInf> <PmtId> <InstrId>I000002</InstrId> <EndToEndId> E000002</EndToEndId> </PmtId> <Amt> <InstdAmt Ccy="LVL">100.01</InstdAmt> </Amt> <CdtrAgt> <FinInstnId> <BIC>UNLALV2X</BIC> </FinInstnId> </CdtrAgt> <Cdtr> <Nm>Jānis Kalniņš</Nm> <PrvtId> <Othr> </Othr> </PrvtId> </Cdtr> <CdtrAcct> <IBAN>LV14UNLA </IBAN> </CdtrAcct> <RmtInf> <Ustrd>Alga par </Ustrd> </RmtInf> </CdtTrfTxInf> <CdtTrfTxInf> <PmtId> <InstrId>I </InstrId> <EndToEndId> E000003</EndToEndId> </PmtId> <Amt> <InstdAmt Ccy="LVL">200.01</InstdAmt> </Amt> <CdtrAgt> <FinInstnId> <BIC>NDEALV2X</BIC> </FinInstnId> </CdtrAgt> <Cdtr> <PrvtId> <Othr> </Othr> </PrvtId> </Cdtr> <CdtrAcct> <IBAN>LV14NDEA </IBAN> </CdtrAcct> <RmtInf> <Ustrd>Alga par </Ustrd> </RmtInf> </CdtTrfTxInf> </PmtInf> </CstmrCdtTrfInitn> </Document> May

24 4.2 Lithuania Description Note: Account numbers and legal codes are not valid as they are only for information purposes. If the same examples will be used, payments will be rejected due to validation rules. Payment 1: Urgent domestic payment Debtor: Name IBAN account number BIC Creditor: Name Country Address IBAN account number BIC Payment: Payment type Test Company UAB LT NDEALT2X Receiver UAB LT Didžioji str. 18, Vilnius LT HABALT22 Urgent Requested execution date Payment amount Payment currency Additional identification given by the payer, not forwarded to the beneficiary (Instruction Identification) - Payment order Nr The unique transaction identification given by the payer (End To End Identification) LTL DU DU0001 Remittance information (unstructured) - payment details Payment for services No Payment 2: Internal payment Debtor: Name IBAN account number BIC Creditor: Name Country Address IBAN account number BIC Payment: Test Company UAB LT NDEALT2X Receiver same bank UAB LT Didžioji str. 18, Vilnius LT NDEALT2X Payment amount Requested execution date Payment currency Additional identification given by the payer, not forwarded to the beneficiary (Instruction Identification) - Payment order No. LTL I The unique transaction identification given by the payer (End To End Identification) E May

25 Tax code 1111 Remittance information (unstructured) - payment details Transfer to partners for services Payment 3: SEPA payment Debtor: Name IBAN account number BIC Test Company UAB LT NDEALT2X Legal ID Creditor: Name Country Receiver SIA Address K. Valdemara St. 62 IBAN account number BIC Payment: LV LV25NDEA NDEALV2X Requested execution date Payment amount Payment currency Additional identification given by the payer, not forwarded to the beneficiary (Instruction Identification) - Payment order Nr EUR SEP0001 Creditor legal ID The unique transaction identification given by the payer (End To End Identification) Remittance information (unstructured) - payment details SEP0001 Payment for services No in Latvia Payment 4: Salary payments Debtor: Name IBAN account number BIC Creditor: Name Test Company UAB LT NDEALT2X Jonas Jonaitis Legal ID IBAN account number BIC Payment: LT NDEALT2X Payment ammount Payment currency LTL Additional identification given by the payer, not forwarded to the beneficiary (Instruction Identification) - Payment order Nr SAL0001 The unique transaction identification given by the payer (End To End Identification) SAL0001 Remittance information (unstructured) - payment details Alga už Creditor: Name Petras Petreaitis Legal ID May

26 IBAN account number LT BIC HABALT22 Payment: Payment ammount Payment currency LTL Additional identification given by the payer, not forwarded to the beneficiary (Instruction Identification) - Payment order Nr SAL0002 The unique transaction identification given by the payer (End To End Identification) SAL0002 Remittance information (unstructured) - payment details Alga už Payment 5: Payment in RUB to Russia Debtor: Name IBAN account number BIC Test Company UAB LT NDEALT2X Legal ID Creditor: Name GAZPROM Account number INN INN BIK code Payment: Requested execution date Payment amount Payment currency Additional identification given by the payer, not forwarded to the beneficiary (Instruction Identification) - Payment order Nr The unique transaction identification given by the payer (End To End Identification) Remittance information (unstructured) - payment details Intermediatory bank details: Name RUB Instr-H POHJA-V3-T1-1 E2E-H POHJA-V3-T1-1 VO PREPAYMENT TRANSPORT COST INV 123 CONTR 321 RUB 20,00 SBERBANK PERMSKOE. Account number Country Postal address RU Middle or Russia Message content The example message table does not have all the elements of the ISO standard. If the customer gives extra information which the service does not check and cannot utilise or forward in the payment chain, the information is not processed or is cut off. The extra information does not cause the rejection of the payment unless it is checked (as, for example, too long Remittance Information). The examples cover the most important payment types and the information needed for them. The examples also contain optional information but do not cover all possible payment alternatives. Message item XML tag M/O Content Comment LITAS-ESIS equivalent May

27 A. GroupHeader <GrpHdr> [1..1] MessageIdentification <MsgId> [1..1] Mandatory, unique for at least 3 months. May not contain special characters CreationDateTime <CreDtTm> [1..1] T10:30:00 NumberOfTransaction s Mandatory, valid values: current date -30 and +1 calendar days <NbOfTxs> [1..1] 2 Mandatory, number of transactions (C-level) Date (2) ControlSum <CtrlSum> [0..1] Optional. Sum of amounts at C-level. InitiatingParty <InitgPty> [1..1] Mandatory Name <Nm> [0..1] Identification [0..1] OrganisationIdentificat ion <OrgId> [0..1] Other <Othr> [1..1] Test Company UAB Recommended to use the name Payer name (6) Identification [1..1] Service Id given by Nordea. Mandatory either in element GroupHeader or PaymentInformation. If given in PaymentInformation element, the Id given in GroupHeader is not taken into account in the batch in question. SchemeName <SchmeNm> [1..1] Code <Cd> [1..1] BANK B. PaymentInformation <PmtInf> BANK = BankPartyIdentification, ExternalCode value First debit batch PaymentInformationId entification <PmtInfId> [0..1] Optional, recommended, unique for at least 3 months. May not contain special characters PaymentMethod <PmtMtd> [1..1] TRF Mandatory, Transfer BatchBooking <BtchBookg> [0..1] FALSE Not mandatory, default value false RequestedExecutionD ate <ReqdExctnD t> Debtor <Dbtr> [1..1] [1..1] Name <Nm> [1..1] Test Company UAB Mandatory, valid values: max +90 and -5 calendar days Mandatory The name of the accountholder is transmitted to the beneficiary from Nordea s customer register. Payment execution date (3) Payer name (6) PostalAddress <PstlAdr> [0..1] Country <Ctry> [1..1] LT Optional AddressLine <AdrLine> [0..1] Didžioji str. 18 Optional AddressLine <AdrLine > [0..1] Vilnius Optional Identification [1..1] OrganisationIdentificat ion <OrgId> [1..1] Other <Othr> [1..1] Identification [0..1] Mandatory if not given on GroupHeader level. Service Id given by Nordea. If given in PaymentInformation element, the Id given in GroupHeader is not taken into account in this batch. Legal ID (7) May

28 SchemeName <SchmeNm> [1..1] Code <Cd> [1..1] BANK DebtorAccount <DbtrAcct> [1..1] Identification [1..1] IBAN <IBAN> [1..1] DebtorAgent <DbtrAgt> [1..1] FinancialInstitutionIde ntification <FinInstnId> [1..1] LT BANK = BankPartyIdentification, ExternalCode value Mandatory, payer s account in IBAN format BIC <BIC> [1..1] NDEALT2X Mandatory, payer bank s BIC Receiver client code Payer account (5) ChargeBearer <ChrgBr> [0..1] SHAR Optional. Default value: shared charges. C. CreditTransferTrans action Information (1st payment) <CdtTrfTxIn f> [1..n] Credit information - Urgent domestic payment PaymentIdentification <PmtId> [1..1] Double check using the combination of Instruction Id (optional) and EndtoEnd Id (mandatory). InstructionIdentificatio n <InstrId> [0..1] DU0001 If present, Id to be returned only to ordering party in account statement reporting EndToEndIdentificatio n <EndToEndId > [1..1] DU0001 Mandatory, unique for at least 3 months. May not contain special characters PaymentTypeInformati on ServiceLevel <SvcLvl> [0..1] <PmtTpInf> [0..1] Payment type Code <Cd> [0..1] URGP Urgent payment Amount <Amt> [1..1] InstructedAmount <InstdAmt> [1..1] LTL Mandatory, instructed amount CreditorAgent <CdtrAgt> [0..1] FinancialInstitutionIde ntification <FinInstnId> [0..1] BIC <BIC> [0..1] HABALT22 Creditor <Cdtr> [0..1] Name <Nm> [1..1] Creditor Company UAB Mandatory, creditor name PostalAddress <PstlAdr> [0..1] BIC of beneficiary s bank is optional for SEPA credit transfers. If not given, Nordea will derive BIC from IBAN. Payment urgency (3) Instructed amount (21) and currency (22) Beneficiaty name (14) AddressLine <AdrLine> [0..1] Stirnų str. 125 Optional, recommended AddressLine <AdrLine > [0..1] LT-3000, Kaunas Optional, recommended Country <Ctry> [1..1] LT Mandatory if address is given CreditorAccount <CdtrAcct> [0..1] Identification [1..1] IBAN <IBAN> [1..1] LT Mandatory, creditor IBAN Beneficiaty legal ID (15) Beneficiaty account (13) RemittanceInformation <RmtInf> [0..1] Optional, payment specifications May

29 Unstructured <Ustrd> [0..1] C. CreditTransferTrans action Information (2nd payment) <CdtTrfTxIn f> [1..n] Payment services No One occurrence (max 140 characters) Credit information - Domestic payment Payment details (24) PaymentIdentification <PmtId> [1..1] Double check using the combination of Instruction Id (optional) and EndtoEnd Id (mandatory). InstructionIdentificatio n <InstrId> [0..1] I If present, Id to be returned only to ordering party in account statement reporting EndToEndIdentificatio n <EndToEndId > [1..1] E Mandatory, unique for at least 3 months. May not contain special characters including å, ä and ö Amount <Amt> [1..1] InstructedAmount <InstdAmt> [1..1] LTL Mandatory, instructed amount CreditorAgent <CdtrAgt> [0..1] FinancialInstitutionIde ntification <FinInstnId> [0..1] BIC <BIC> [0..1] NDEALT2X BIC of beneficiary s bank is optional for SEPA credit transfers. If not given, Nordea will derive BIC from IBAN. Instructed amount (21) and currency (22) Creditor <Cdtr> [0..1] Name <Nm> [1..1] Receiver same bank UAB Mandatory, creditor name Beneficiaty name (14) PostalAddress <PstAdr> [0..1] Country <Ctry> [1..1] LT Mandatory if address is given AddressLine <AdrLine> [0..1] Didžioji str. 18, Vilnius Optional, recommended CountryOfResidance <CtryOfRes> [0..1] LT Optional CreditorAccount <CdtrAcct> [0..1] Identification [1..1] IBAN <IBAN> [1..1] LT Mandatory, creditor IBAN Beneficiaty account (13) Purpose <Purp> [0..1] Proprietary <Prtry> [1..1] 1111 Tax code filed. Max 35 characters. Tax code (23) RemittanceInformation <RmtInf> [0..1] Optional, payment specifications Unstructured <Ustrd> [0..1] Transfer to partners for services One occurrence (max 140 characters) of free-form text is transmitted to AOS2 banks. Payment details (24) Sepa payment. 3rd message C. CreditTransferTrans action Information (3rd payment) <CdtTrfTxIn f> [1..n] Credit information - SEPA payment PaymentIdentification <PmtId> [1..1] Double check using the combination of Instruction Id (optional) and EndtoEnd Id (mandatory). May

30 InstructionIdentificatio n <InstrId> [0..1] SEP0001 If present, Id to be returned only to ordering party in account statement reporting EndToEndIdentificatio n <EndToEndId > [1..1] SEP0001 Mandatory, unique for at least 3 months. May not contain special characters Amount <Amt> [1..1] InstructedAmount <InstdAmt> [1..1] EUR Mandatory, instructed amount CreditorAgent <CdtrAgt> [0..1] FinancialInstitutionIde ntification <FinInstnId> [0..1] BIC <BIC> [0..1] NDEALV2X Creditor <Cdtr> [0..1] Name <Nm> [1..1] Receiver in LV SIA Mandatory, creditor name PostalAddress <PstlAdr> [0..1] BIC of beneficiary s bank is optional for SEPA credit transfers. If not given, Nordea will derive BIC from IBAN. Instructed amount (21) and currency (22) Beneficiaty name (14) Country <Ctry> [1..1] LV Mandatory if address is given AdressLine <AdrLine> [0..2] K.Valdemara iela 62 Information that locates and identifies a specific address, as defined by postal services, presented in free format text CreditorAccount <CdtrAcct> [0..1] Identification [1..1] Other <Othr> [1..1] Identification [1..1] CreditorAccount <CdtrAcct> [0..1] Identification assigned by an institution Beneficiaty legal ID (15) Identification [1..1] IBAN <IBAN> [1..1] LV25NDEA Mandatory, creditor IBAN RemittanceInformation <RmtInf> [0..1] Optional, payment specifications Unstructured <Ustrd> [0..1] Transfer to partners for services One occurrence (max 140 characters) Beneficiaty account (13) Payment details (24) Salary payments Message item XML tag M/O Content Comment A. GroupHeader <GrpHdr> [1..1] MessageIdentification <MsgId> [1..1] Mandatory, unique for at least 3 months. May not contain special characters CreationDateTime <CreDtTm> [1..1] T10:31:00 NumberOfTransaction s Mandatory, valid values: current date -30 and +1 calendar days <NbOfTxs> [1..1] 2 Mandatory, number of transactions (C-level) ControlSum <CtrlSum> [0..1] Optional. Sum of amounts at C-level. InitiatingParty <InitgPty> [1..1] Mandatory Name <Nm> [0..1] Test Company UAB Recommended to use the name May

31 B. PaymentInformation PaymentInformationId entification <PmtInf> <PmtInfId> [0..1] First debit batch Optional, recommended, unique for at least 3 months. May not contain special characters PaymentMethod <PmtMtd> [1..1] TRF Mandatory, Transfer BatchBooking <BtchBookg> [0..1] true Not mandatory, default value false PaymentTypeInformati on <PmtTpInf> [0..1] CategoryPurpose <CtgyPurp> [0..1] Code <Cd> [1..1] SALA for pension payments PENS RequestedExecutionD ate <ReqdExctnD t> [1..1] Mandatory, valid values: max +90 and -5 calendar days Debtor <Dbtr> [1..1] Name <Nm> [1..1] Test Company UAB Mandatory The name of the accountholder is transmitted to the beneficiary from Nordea s customer register. PostalAddress <PstlAdr> [0..1] Country <Ctry> [1..1] LT Optional AddressLine <AdrLine> [0..1] Savanoriu str Optional AddressLine <AdrLine > [0..1] KLT-3000, Kaunas Optional Identification [1..1] OrganisationIdentificat ion <OrgId> [1..1] Other <Othr> [1..1] Identification [0..1] Mandatory if not given on GroupHeader level. Service Id given by Nordea. If given in PaymentInformation element, the Id given in GroupHeader is not taken into account in this batch. SchemeName <SchmeNm> [1..1] Code <Cd> [1..1] BANK BANK = BankPartyIdentification, ExternalCode value DebtorAccount <DbtrAcct> [1..1] Identification [1..1] IBAN <IBAN> [1..1] LT Mandatory, payer s account in IBAN format DebtorAgent <DbtrAgt> [1..1] FinancialInstitutionIde ntification <FinInstnId> [1..1] BIC <BIC> [1..1] NDEALT2X Mandatory, payer bank s BIC ChargeBearer <ChrgBr> [0..1] SHAR Optional. Default value: shared charges. C. CreditTransferTrans action Information (1st payment) <CdtTrfTxIn f> [1..n] Credit information - Salary 1st beneficiary May

32 PaymentIdentification <PmtId> [1..1] Double check using the combination of Instruction Id (optional) and EndtoEnd Id (mandatory). InstructionIdentificatio n <InstrId> [0..1] SAL0001 If present, Id to be returned only to ordering party in account statement reporting EndToEndIdentificatio n <EndToEndId > [1..1] Amount <Amt> [1..1] SAL0001 Mandatory, unique for at least 3 months. May not contain special characters InstructedAmount <InstdAmt> [1..1] LTL Mandatory, instructed amount CreditorAgent <CdtrAgt> [0..1] FinancialInstitutionIde ntification <FinInstnId> [0..1] Instructed amount (21) and currency (22) BIC <BIC> [0..1] NDEALT2X BIC of beneficiary s bank is optional for SEPA credit transfers. If not given, Nordea will derive BIC from IBAN. Creditor <Cdtr> [0..1] Name <Nm> [1..1] Jonas Jonaitis Mandatory, creditor name Beneficiaty name (14) Identification [0..1] PrivateIdentification <PrvtId> [1..1] Other <Othr> [0..n] Identification [1..1] Optional Beneficiaty legal ID (15) CreditorAccount <CdtrAcct> [0..1] Identification [1..1] IBAN <IBAN> [1..1] LT Mandatory, creditor IBAN RemittanceInformation <RmtInf> [0..1] Optional, payment specifications Unstructured <Ustrd> [0..1] C. CreditTransferTrans action Information (2nd payment) <CdtTrfTxIn f> [1..n] Alga už One occurrence (max 140 characters) Credit information - Salary 2nd beneficiary Beneficiaty account (13) Payment details (24) PaymentIdentification <PmtId> [1..1] Double check using the combination of Instruction Id (optional) and EndtoEnd Id (mandatory). InstructionIdentificatio n <InstrId> [0..1] SAL0002 If present, Id to be returned only to ordering party in account statement reporting EndToEndIdentificatio n <EndToEndId > [1..1] SAL0002 Mandatory, unique for at least 3 months. May not contain special characters Amount <Amt> [1..1] InstructedAmount <InstdAmt> [1..1] LTL Mandatory, instructed amount CreditorAgent <CdtrAgt> [0..1] FinancialInstitutionIde ntification <FinInstnId> [0..1] Instructed amount (21) and currency (22) May

33 BIC <BIC> [0..1] NDEALT2X BIC of beneficiary s bank is optional for SEPA credit transfers. If not given, Nordea will derive BIC from IBAN. Creditor <Cdtr> [0..1] Name <Nm> [1..1] Petras Petraitis Mandatory, creditor name Beneficiaty name (14) Identification [0..1] PrivateIdentification <PrvtId> [1..1] Other <Othr> [0..n] Identification [1..1] Optional Beneficiaty legal ID (15) CreditorAccount <CdtrAcct> [0..1] Identification [1..1] IBAN <IBAN> [1..1] LT Mandatory, creditor IBAN RemittanceInformation <RmtInf> [0..1] Optional, payment specifications Unstructured <Ustrd> [0..1] Alga už One occurrence (max 140 characters) Beneficiaty account (13) Payment details (24) Payments to Russia in RUB Message item XML tag M/O Content Comment A. GroupHeader <GrpHdr> [1..1] MessageIdentification <MsgId> [1..1] R01 Mandatory, unique for at least 3 months. May not contain special characters CreationDateTime <CreDtTm> [1..1] T10:30:00 NumberOfTransaction s Mandatory, valid values: current date -30 and +1 calendar days <NbOfTxs> [1..1] 1 Mandatory, number of transactions (C-level) ControlSum <CtrlSum> [0..1] Optional. Sum of amounts at C-level. InitiatingParty <InitgPty> [1..1] Mandatory Name <Nm> [0..1] B. PaymentInformation PaymentInformationId entification <PmtInf> Test Company UAB <PmtInfId> [0..1] R01 Recommended to use the name First debit batch Optional, recommended, unique for at least 3 months. May not contain special characters PaymentMethod <PmtMtd> [1..1] TRF Mandatory, Transfer BatchBooking <BtchBookg> [0..1] false Not mandatory, default value false PaymentTypeInformati on <PmtTpInf> [0..1] CategoryPurpose <CtgyPurp> [0..1] RequestedExecutionD ate <ReqdExctnD t> Debtor <Dbtr> [1..1] [1..1] Name <Nm> [1..1] Test Company UAB Mandatory, valid values: max +90 and -5 calendar days Mandatory The name of the accountholder is transmitted to the beneficiary from Nordea s customer register. May

34 PostalAddress <PstlAdr> [0..1] Country <Ctry> [1..1] LT Optional AddressLine <AdrLine> [0..1] Savanoriu str Optional AddressLine <AdrLine > [0..1] KLT-3000, Kaunas Optional Identification [1..1] OrganisationIdentificat ion <OrgId> [1..1] Other <Othr> [1..1] Identification [0..1] Mandatory if not given on GroupHeader level. Service Id given by Nordea. If given in PaymentInformation element, the Id given in GroupHeader is not taken into account in this batch. SchemeName <SchmeNm> [1..1] Code <Cd> [1..1] BANK DebtorAccount <DbtrAcct> [1..1] BANK = BankPartyIdentification, ExternalCode value Identification [1..1] IBAN <IBAN> [1..1] LT Mandatory, payer s account in IBAN format DebtorAgent <DbtrAgt> [1..1] FinancialInstitutionIde ntification <FinInstnId> [1..1] BIC <BIC> [1..1] NDEALT2X Mandatory, payer bank s BIC ChargeBearer <ChrgBr> [0..1] DEBT Optional. C. CreditTransferTrans action Information (5th payment) <CdtTrfTxIn f> [1..n] Credit information - RUB payments to Russia PaymentIdentification <PmtId> [1..1] Double check using the combination of Instruction Id (optional) and EndtoEnd Id (mandatory). InstructionIdentificatio n <InstrId> [0..1] Instr-H POHJA- V3-T1-1 If present, Id to be returned only to ordering party in account statement reporting EndToEndIdentificatio n <EndToEndId > [1..1] E2E-H POHJA- V3-T1-1 Mandatory, unique for at least 3 months. May not contain special characters Amount <Amt> [1..1] InstructedAmount <InstdAmt> [1..1] RUB20.00s Mandatory, instructed amount CreditorAgent <CdtrAgt> [1..1] Beneficiary s bank mandatory. Either BIC or clearing code and/or name and address (in the example) is required FinancialInstitutionIde ntification <FinInstnId> [1..1] In the example the beneficiary s bank is expressed with the clearing code. When the clearing code is used, the bank s name and address are required, if known. May

35 If the bank s information is entered without the BIC or the clearing code, the name, address information and the bank s country code must be entered. ClearingSystemMemb eridentification ClearingSystemIdentifi cation <ClrSysMmb Id> <ClrSysId> [0..1] Code <Cd> [0..1] RUCBC [0..1] Clearing code See additional information in section Clearing codes. MemberIdentification <MmbId> [1..1] Clearing number BIK code Name <Nm> [0..1] SBERBANK PERMSKOE Bank s name PostalAddress <PstAdr> [0..1] Country <Ctry> [0..1] RU Optional, recommended AdressLine <AdrLine> [0..2] Middle or Russia CreditorAgentAccount <CdtrAgtAcct > [0..1] Identification [1..1] Information that locates and identifies a specific address, as defined by postal services, presented in free format text Other <Othr> [1..1] Identification [1..1] Creditor <Cdtr> [1..1] Name <Nm> [1..1] Company Mandatory PostalAddress <PstAdr> [0..1] Country <Ctry> [1..1] RU Mandatory if address is given AdressLine <AdrLine> [0..2] Moscow Information that locates and identifies a specific address, as defined by postal services, presented in free format text CreditorAccount <CdtrAcct> [0..1] Mandatory for credit transfers Identification [1..1] Other <Othr> [1..1] Identification [1..1] /I NN Other than IBAN account number is presented with Identification information only. SchemeName / Code, eg BBAN, can be given but is not necessary. RemittanceInformation <RmtInf> [0..1] Optional, payment specifications Unstructured <Ustrd> [0..1] VO PREPAYMENT TRANSPORT COST INV 123 CONTR 321 RUB One occurrence (max 70 characters) of free text is forwarded in foreign currency payments. EndToEnd Id reserves 35 characters. May

36 4.2.3 XML example Note! The beginning of the message must include a defined schemalocation as in the example below. <?xml version="1.0" encoding="utf-8"?> <Document xmlns="urn:iso:std:iso:20022:tech:xsd:pain " xmlns:xsi=" xsi:schemalocation="urn:iso:std:iso:20022:tech:xsd:pain pain xsd"> <CstmrCdtTrfInitn> <GrpHdr> <MsgId> </MsgId> <CreDtTm> T10:30:00</CreDtTm> <NbOfTxs>2</NbOfTxs> <CtrlSum>200.03</CtrlSum> <InitgPty> <Nm>Test Company UAB</Nm> </InitgPty> </GrpHdr> <!-- **************************************************************** Payment Information block **************************************************************** --> <PmtInf> <PmtInfId> </PmtInfId> <PmtMtd>TRF</PmtMtd> <BtchBookg>false</BtchBookg> <ReqdExctnDt> </ReqdExctnDt> <Dbtr> <Nm>Test Company UAB </Nm> <PstlAdr> <Ctry>LT</Ctry> <AdrLine>Didžioji str. 18</AdrLine> <AdrLine>Vilnius</AdrLine> </PstlAdr> <OrgId> <Othr> <SchmeNm> <Cd>BANK</Cd> </SchmeNm> </Othr> </OrgId> </Dbtr> <DbtrAcct> <IBAN>LT </IBAN> </DbtrAcct> <DbtrAgt> <FinInstnId> <BIC>NDEALT2X</BIC> </FinInstnId> </DbtrAgt> <ChrgBr>SHAR</ChrgBr> <!-- **************************************************************** 1. Urgent domestic payment **************************************************************** --> <CdtTrfTxInf> <PmtId> <InstrId>DU0001</InstrId> <EndToEndId> DU0001</EndToEndId> </PmtId> <PmtTpInf> <SvcLvl> <Cd>URGP</Cd> </SvcLvl> </PmtTpInf> May

37 <Amt> <InstdAmt Ccy="LTL">100.01</InstdAmt> </Amt> <CdtrAgt> <FinInstnId> <BIC>HABALT22</BIC> </FinInstnId> </CdtrAgt> <Cdtr> <Nm>Creditor Company UAB</Nm> <PstlAdr> <Ctry>LT</Ctry> <AdrLine>Stirnų g. 125,</AdrLine> <AdrLine>LT-3000, Vilnius</AdrLine> </PstlAdr> <OrgId> <Othr> </Othr> </OrgId> </Cdtr> <CdtrAcct> <IBAN>LT </IBAN> </CdtrAcct> <RmtInf> <Ustrd>Payment services No. 1111</Ustrd> </RmtInf> </CdtTrfTxInf> <!-- **************************************************************** 2. Internal payment **************************************************************** --> <CdtTrfTxInf> <PmtId> <InstrId>I000002</InstrId> <EndToEndId> E000002</EndToEndId> </PmtId> <Amt> <InstdAmt Ccy="LTL">100.02</InstdAmt> </Amt> <CdtrAgt> <FinInstnId> <BIC>NDEALT2X</BIC> </FinInstnId> </CdtrAgt> <Cdtr> <Nm>Receiver same bank UAB</Nm> <PstlAdr> <Ctry>LT</Ctry> <AdrLine>Didžioji str. 18, Vilnius</AdrLine> </PstlAdr> <CtryOfRes>LT</CtryOfRes> </Cdtr> <CdtrAcct> <IBAN>LT </IBAN> </CdtrAcct> <Purp> <Prtry>1111</Prtry> </Purp> </PmtInf> </CstmrCdtTrfInitn> </Document> <RmtInf> <Ustrd>Transfer to partners for services </Ustrd> </RmtInf> </CdtTrfTxInf> May

38 <?xml version="1.0" encoding="utf-8"?> <Document xmlns="urn:iso:std:iso:20022:tech:xsd:pain " xmlns:xsi=" xsi:schemalocation="urn:iso:std:iso:20022:tech:xsd:pain pain xsd"> <!-- **************************************************************** 3. SEPA payment. New message **************************************************************** --> <CstmrCdtTrfInitn> <GrpHdr> <MsgId> </MsgId> <CreDtTm> T10:30:00</CreDtTm> <NbOfTxs>1</NbOfTxs> <CtrlSum>100.01</CtrlSum> <InitgPty> <Nm>Test Company UAB</Nm> </InitgPty> </GrpHdr> <!-- **************************************************************** Payment Information block **************************************************************** --> <PmtInf> <PmtInfId> </PmtInfId> <PmtMtd>TRF</PmtMtd> <BtchBookg>false</BtchBookg> <ReqdExctnDt> </ReqdExctnDt> <Dbtr> <Nm>Test Company UAB </Nm> <PstlAdr> <Ctry>LT</Ctry> <AdrLine>Didžioji str. 18</AdrLine> <AdrLine>Vilnius</AdrLine> </PstlAdr> <OrgId> <Othr> <SchmeNm> <Cd>BANK</Cd> </SchmeNm> </Othr> </OrgId> </Dbtr> <DbtrAcct> <IBAN>LT </IBAN> </DbtrAcct> <DbtrAgt> <FinInstnId> <BIC>NDEALT2X</BIC> </FinInstnId> </DbtrAgt> <ChrgBr>SLEV</ChrgBr><!-- IMPORTANT USE THIS VALUE --> <CdtTrfTxInf> <PmtId> <InstrId>SEP0001</InstrId> <EndToEndId> SEP0001</EndToEndId> </PmtId> <Amt> <InstdAmt Ccy="EUR">100.01</InstdAmt> </Amt> <CdtrAgt> <FinInstnId> <BIC>NDEALV2X</BIC> </FinInstnId> </CdtrAgt> <Cdtr> <Nm>Receiver in LV SIA</Nm> May

39 <PstlAdr> <Ctry>LV</Ctry> <AdrLine>K.Valdemara iela 62</AdrLine> </PstlAdr> <OrgId> <Othr> </Othr> </OrgId> </Cdtr> <CdtrAcct> <IBAN>LT </IBAN> </CdtrAcct> <RmtInf> <Ustrd>Transfer to partners for services </Ustrd> </RmtInf> </CdtTrfTxInf> </PmtInf> </CstmrCdtTrfInitn> </Document> <?xml version="1.0" encoding="utf-8"?> <Document xmlns="urn:iso:std:iso:20022:tech:xsd:pain " xmlns:xsi=" xsi:schemalocation="urn:iso:std:iso:20022:tech:xsd:pain pain xsd"> <!-- **************************************************************** 4. Salary payments **************************************************************** --> <CstmrCdtTrfInitn> <GrpHdr> <MsgId> </MsgId> <CreDtTm> T10:31:00</CreDtTm> <NbOfTxs>2</NbOfTxs> <CtrlSum>300.04</CtrlSum> <InitgPty> <Nm>Test Company UAB</Nm> </InitgPty> </GrpHdr> <PmtInf> <PmtInfId> </PmtInfId> <PmtMtd>TRF</PmtMtd> <BtchBookg>true</BtchBookg> <PmtTpInf> <CtgyPurp> <Cd>SALA</Cd> </CtgyPurp> </PmtTpInf> <ReqdExctnDt> </ReqdExctnDt> <Dbtr> <Nm>Test Company UAB </Nm> <PstlAdr> <Ctry>LT</Ctry> <AdrLine>Savanorių per </AdrLine> <AdrLine>LT-3000, Kaunas</AdrLine> </PstlAdr> <OrgId> <Othr> <SchmeNm> <Cd>BANK</Cd> </SchmeNm> </Othr> </OrgId> </Dbtr> May

40 <Nm>Petras Petraitis</Nm> <DbtrAcct> <IBAN>LT </IBAN> </DbtrAcct> <DbtrAgt> <FinInstnId> <BIC>NDEALT2X</BIC> </FinInstnId> </DbtrAgt> <ChrgBr>SHAR</ChrgBr> <CdtTrfTxInf> <PmtId> <InstrId>SAL0001</InstrId> <EndToEndId> SAL0001</EndToEndId> </PmtId> <Amt> <InstdAmt Ccy="LTL">100.01</InstdAmt> </Amt> <CdtrAgt> <FinInstnId> <BIC>NDEALT2X</BIC> </FinInstnId> </CdtrAgt> <Cdtr> <Nm>Jonas Jonaitis</Nm> <PrvtId> <Othr> </Othr> </PrvtId> </Cdtr> <CdtrAcct> <IBAN>LT </IBAN> </CdtrAcct> <RmtInf> <Ustrd>Alga už </Ustrd> </RmtInf> </CdtTrfTxInf> <CdtTrfTxInf> <PmtId> <InstrId> SAL0002</InstrId> <EndToEndId> SAL0002</EndToEndId> </PmtId> <Amt> <InstdAmt Ccy="LTL">200.01</InstdAmt> </Amt> <CdtrAgt> <FinInstnId> <BIC>NDEALT2X</BIC> </FinInstnId> </CdtrAgt> <Cdtr> </Cdtr> <CdtrAcct> <PrvtId> </PrvtId> <Othr> </Othr> <IBAN>LT </IBAN> </CdtrAcct> <RmtInf> <Ustrd>Alga už </Ustrd> </RmtInf> May

41 </PmtInf> </CstmrCdtTrfInitn> </Document> </CdtTrfTxInf> <!-- **************************************************************** 5. RUB payment **************************************************************** --> <?xml version="1.0" encoding="utf-8"?> <Document xmlns="urn:iso:std:iso:20022:tech:xsd:pain " xmlns:xsi=" xsi:schemalocation="urn:iso:std:iso:20022:tech:xsd:pain pain xsd"> <CstmrCdtTrfInitn> <GrpHdr> <MsgId> R01</MsgId> <CreDtTm> T10:30:00</CreDtTm> <NbOfTxs>1</NbOfTxs> <CtrlSum>20</CtrlSum> <InitgPty> <Nm>Test Company UAB</Nm> </InitgPty> </GrpHdr> <PmtInf> <PmtInfId> R01</PmtInfId> <PmtMtd>TRF</PmtMtd> <BtchBookg>false</BtchBookg> <ReqdExctnDt> </ReqdExctnDt> <Dbtr> <Nm> Test Company UAB </Nm> <PstlAdr> <Ctry>LT</Ctry> <AdrLine>Didzioji 18</AdrLine> <AdrLine>LT-3000 Lietuva</AdrLine> </PstlAdr> <OrgId> <Othr> <SchmeNm> <Cd>BANK</Cd> </SchmeNm> </Othr> </OrgId> </Dbtr> <DbtrAcct> <IBAN>LT </IBAN> </DbtrAcct> <DbtrAgt> <FinInstnId> <BIC>NDEALT2X</BIC> </FinInstnId> </DbtrAgt> <ChrgBr>DEBT</ChrgBr> <CdtTrfTxInf> <PmtId> <InstrId>Instr-H POHJA-V3-T1-1</InstrId> <EndToEndId>E2E-H POHJA-V3-T1-1</EndToEndId> </PmtId> <Amt> <InstdAmt Ccy="RUB">20.00</InstdAmt> </Amt> <ChrgBr>DEBT</ChrgBr> <CdtrAgt> <FinInstnId> <ClrSysMmbId> <ClrSysId> <Cd>RUCBC</Cd> </ClrSysId> <MmbId> </MmbId> May

42 <!--BIK code --> </ClrSysMmbId> <Nm>SBERBANK PERMSKOE.</Nm> <!-- Russian bank name --> <PstlAdr> <Ctry>RU</Ctry> <AdrLine>Middle or Russia</AdrLine> </PstlAdr> </FinInstnId> </CdtrAgt> <CdtrAgtAcct> <Othr> <!-- Correspondent bank account --> </Othr> </CdtrAgtAcct> <Cdtr> <Nm>GAZPROM</Nm> </Cdtr> <CdtrAcct> <Othr> /INN </Othr> </CdtrAcct> <RmtInf> <Ustrd> PREPAYMENT TRANSPORT COST INV 123 CONTR 321 RUB 20.00</Ustrd> </RmtInf> </CdtTrfTxInf> </PmtInf> </CstmrCdtTrfInitn> </Document> 4.3 Estonia Description Payment 1: Urgent domestic payment Debtor: Name IBAN account number BIC Creditor: Name Country Address IBAN account number BIC Payment: Payment type Test Grupp AS EE NDEAEE2X Testklient1 AS EE Palmi 2, Tallinn, Eesti EE HABAEE2X Urgent Requested execution date Payment amount 3.83 Payment currency Additional identification given by the payer, not forwarded to the beneficiary (Instruction Identification) - Payment order Nr EUR PMT The unique transaction identification given by the payer (End To End Identification) NOTPROVIDED May

43 Remittance information (unstructured) - payment details Testarve A tasumine Payment 2: Domestic payment Debtor: Name IBAN account number BIC Creditor: Name Country Address IBAN account number BIC Payment: Payment amount 2.72 Test Grupp AS EE NDEAEE2X Testklient2 AS EE Ketta 8, Tallinn, Eesti EE EEUHEE2X Requested execution date Payment currency Additional identification given by the payer, not forwarded to the beneficiary (Instruction Identification) - Payment order Nr The unique transaction identification given by the payer (End To End Identification) Remittance information (unstructured) - payment details EUR PMT NOTPROVIDED Testarve A tasumine Creditor reference Payment 3: Cross border payment Debtor: Name Test Grupp AS IBAN account number EE BIC NDEAEE2X Creditor: Name Hyatt Central, Beneficiary county US Address New York Account number BIC BANKUS33 Payment: Payment ammount 4, Payment currency USD Additional identification given by the payer, not forwarded to the beneficiary (Instruction Identification) - Payment order Nr I The unique transaction identification given by the payer (End To End Identification) E Remittance information (unstructured) - payment details Invoices 123 and 321 Payment 4: Urgent cross border payment Debtor: May

44 Name IBAN account number BIC Creditor: Name County Address Test Grupp AS EE NDEAEE2X Ben E. Ficiary US Boston Account number Clearing code of the beneficiary s bank (US ABA number) Payment: Payment type urgent Payment ammount 55, Payment currency Additional identification given by the payer, not forwarded to the beneficiary (Instruction Identification) - Payment order Nr USD I The unique transaction identification given by the payer (End To End Identification) E Payment reason code 151 Remittance information (unstructured) - payment details Invoices 123 and 321 Payment 5: RUB payment to Russia Debtor: Name IBAN account number BIC Beneficiary: Name Address Test Grupp AS EE NDEAEE2X Company Moscow Account number INN code Beneficiary Bank: Name Country Address Clearing code INN Moscow Bank RU Main street, Moscow RUCBC Clearing system member ID Correspondent account number of the beneficiary s bank Payment: Payment ammount 55, Payment currency Additional identification given by the payer, not forwarded to the beneficiary (Instruction Identification) - Payment order Nr RUB I The unique transaction identification given by the payer (End To End Identification) E Remittance information (unstructured) - payment details Invoices 123 and 321 Code for subject of payment in accordance with the regulations of the Central Bank of Russia VO12345 May

45 Payment 6: Salary payments Debtor: Name IBAN account number BIC Creditor: Name Test Grupp AS EE NDEAEE2X Test Saaja1 Legal ID IBAN account number BIC Payment: EE NDEAEE2X Payment ammount Payment currency Additional identification given by the payer, not forwarded to the beneficiary (Instruction Identification) - Payment order Nr EUR I The unique transaction identification given by the payer (End To End Identification) E Remittance information (unstructured) - payment details Palk Creditor: Name Test Saaja2 Legal ID IBAN account number BIC Payment: EE HABAEE2X Payment ammount Payment currency Additional identification given by the payer, not forwarded to the beneficiary (Instruction Identification) - Payment order Nr EUR I The unique transaction identification given by the payer (End To End Identification) E Remittance information (unstructured) - payment details Puhkus Message content The example message table does not have all the elements of the ISO standard. If the customer gives extra information which the service does not check and cannot utilise or forward in the payment chain, the information is not processed or is cut off. The extra information does not cause the rejection of the payment unless it is checked (as, for example, too long Remittance Information). The examples cover the most important payment types and the information needed for them. The examples also contain optional information but do not cover all possible payment alternatives. Message item XML tag M/O Content Comment A. GroupHeader <GrpHdr> [1..1] MessageIdentification <MsgId> [1..1] MSG CreationDateTime <CreDtTm> [1..1] T15:44:35Z Mandatory, unique for at least 3 months. May not contain special characters Mandatory, valid values: current date -30 and +1 calendar days May

46 NumberOfTransactions <NbOfTxs> [1..1] 5 Mandatory, number of transactions (C-level) ControlSum <CtrlSum> [0..1] Needs calc Optional. Sum of amounts at C-level. InitiatingParty <InitgPty> [1..1] Mandatory Name <Nm> [0..1] Test Grupp AS Recommended to use the name B. PaymentInformation <PmtInf> First debit batch PaymentInformationIdentif ication <PmtInfId> [0..1] TR PaymentMethod <PmtMtd> [1..1] TRF Mandatory, Transfer Optional, recommended, unique for at least 3 months. May not contain special characters BatchBooking <BtchBookg> [0..1] false Not mandatory, default value false RequestedExecutionDate <ReqdExctnDt> [1..1] Mandatory, valid values: max +90 and -5 calendar days Debtor <Dbtr> [1..1] Name <Nm> [1..1] Test Grupp AS PostalAddress <PstlAdr> [0..1] Mandatory The name of the accountholder is transmitted to the beneficiary from Nordea s customer register. Country <Ctry> [1..1] EE Optional AddressLine <AdrLine> [0..1] Kuuse 6, Tallinn, Eesti Optional Identification [1..1] OrganisationIdentification <OrgId> [1..1] Other <Othr> [1..1] Identification [0..1] SchemeName <SchmeNm> [1..1] Mandatory if not given on GroupHeader level. Service Id given by Nordea. If given in PaymentInformation element, the Id given in GroupHeader is not taken into account in this batch. Code <Cd> [1..1] BANK BANK = BankPartyIdentification, ExternalCode value DebtorAccount <DbtrAcct> [1..1] Identification [1..1] IBAN <IBAN> [1..1] EE Mandatory, payer s account in IBAN format DebtorAgent <DbtrAgt> [1..1] FinancialInstitutionIdentifi cation <FinInstnId> [1..1] BIC <BIC> [1..1] NDEAEE2X Mandatory, payer bank s BIC ChargeBearer <ChrgBr> [0..1] SHAR Optional. Default value: shared charges. C. CreditTransferTransacti on Information (1st payment) <CdtTrfTxInf> [1..n] PaymentIdentification <PmtId> [1..1] InstructionIdentification <InstrId> [0..1] PMT Credit information - Urgent domestic payment Double check using the combination of Instruction Id (optional) and EndtoEnd Id (mandatory). If present, Id to be returned only to ordering party in account statement reporting EndToEndIdentification <EndToEndId> [1..1] NOTPROVIDED Mandatory, unique for at least 3 months. May not contain May

47 PaymentTypeInformation <PmtTpInf> [0..1] Payment type special characters. Special value NOTPROVIDED for empty content. ServiceLevel Code <SvcLvl> <Cd> [0..1] [0..1] URGP Urgent payment Amount <Amt> [1..1] InstructedAmount <InstdAmt> [1..1] EUR 3.83 Mandatory, instructed amount CreditorAgent <CdtrAgt> [0..1] FinancialInstitutionIdentifi cation <FinInstnId> [0..1] BIC <BIC> [0..1] HABAEE22 Creditor <Cdtr> [0..1] BIC of beneficiary s bank is optional for SEPA credit transfers. If not given, Nordea will derive BIC from IBAN. Name <Nm> [1..1] Testklient1 AS Mandatory, creditor name PostalAddress <PstlAdr> [0..1] Country <Ctry> [1..1] EE Mandatory if address is given AddressLine <AdrLine > [0..1] Palmi 2, Tallinn, Eesti Optional, recommended CreditorAccount <CdtrAcct> [0..1] Identification [1..1] IBAN <IBAN> [1..1] EE Mandatory, creditor IBAN RemittanceInformation <RmtInf> [0..1] Optional, payment specifications Unstructured <Ustrd> [0..1] C. CreditTransferTransacti on Information (2nd payment) <CdtTrfTxInf> [1..n] PaymentIdentification <PmtId> [1..1] InstructionIdentification <InstrId> [0..1] Testarve A tasumine PMT EndToEndIdentification <EndToEndId> [1..1] NOTPROVIDED ServiceLevel Code <SvcLvl> <Cd> Amount <Amt> [1..1] [0..1] [0..1] URGP One occurrence (max 140 characters) Credit information - Domestic payment Double check using the combination of Instruction Id (optional) and EndtoEnd Id (mandatory). If present, Id to be returned only to ordering party in account statement reporting Mandatory, unique for at least 3 months. May not contain special characters including å, ä and ö Urgent payment InstructedAmount CreditorAgent <InstdAmt> <CdtrAgt> [1..1] [0..1] EUR 2.72 Mandatory, instructed amount FinancialInstitutionIdentifi cation <FinInstnId> [0..1] BIC <BIC> [0..1] EEUHEE2X BIC of beneficiary s bank is optional for SEPA credit transfers. If not given, Nordea will derive BIC from IBAN. Creditor <Cdtr> [0..1] Name <Nm> [1..1] Testklient2 AS Mandatory, creditor name May

48 PostalAddress <PstAdr> [0..1] Country <Ctry> [1..1] EE Mandatory if address is given AddressLine <AdrLine> [0..1] Ketta 8, Tallinn, Eesti Optional, recommended CreditorAccount <CdtrAcct> [0..1] Identification [1..1] IBAN <IBAN> [1..1] EE Mandatory, creditor IBAN in SEPA credit transfers RemittanceInformation <RmtInf> [0..1] Optional, payment specifications Unstructured <Ustrd> [0..1] Testarve A tasumine Structured <Strd> [0..1] - One occurrence CreditorReferenceInformat ion <CdtrRefInf> [0..1] - - Type <Tp> [0..1] - - CodeOrProprietary <CdOrPrtry> [1..1] - - One occurrence (max 140 characters) of free-form text is transmitted to AOS2 banks. Code <Cd> [1..1] SCOR Use SCOR if reference number set Reference <Ref> [0..1] C. CreditTransferTransacti on Information (3rd payment) <CdtTrfTxInf> [1..n] PaymentIdentification <PmtId> [1..1] InstructionIdentification <InstrId> [0..1] I EndToEndIdentification <EndToEndId> [1..1] E Amount <Amt> [1..1] Correctness of reference number is checked against Estonian reference number standard. Credit information - cross-border payment Double check using the combination of Instruction Id (optional) and EndtoEnd Id (mandatory). If present, Id to be returned only to ordering party in account statement reporting Mandatory, unique for at least 3 months. May not contain special characters InstructedAmount CreditorAgent <InstdAmt> <CdtrAgt> [1..1] [0..1] USD Mandatory, instructed amount FinancialInstitutionIdentifi cation <FinInstnId> [0..1] BIC <BIC> [0..1] BANKUS33 BIC of beneficiary s bank is optional for SEPA credit transfers. If not given, Nordea will derive BIC from IBAN. Creditor <Cdtr> [0..1] Name <Nm> [1..1] Hyatt Central, Mandatory, creditor name PostalAddress <PstlAdr> [0..1] Country <Ctry> [1..1] US Mandatory if address is given AdressLine <AdrLine> [0..2] New York CreditorAccount <CdtrAcct> [0..1] Information that locates and identifies a specific address, as defined by postal services, presented in free format text Identification [1..1] Other <Othr> [1..1] Identification [1..1] Identification assigned by an institution May

49 RegulatoryReporting <RgltryRptg> [0..10] Information needed due to regulatory and statutory requirements Details <Dtls> [0..n] Code <Cd> [0..1] 151 Payment reason code RemittanceInformation <RmtInf> [0..1] Optional, payment specifications Unstructured <Ustrd> [0..1] C. CreditTransferTransacti on Information (4th payment) Invoices 123 and 321 One occurrence (max 140 characters) <CdtTrfTxInf> [1..n] Credit information - RegulatoryReporting <RgltryRptg> [0..10] Urgent cross-border payment PaymentIdentification <PmtId> [1..1] InstructionIdentification <InstrId> [0..1] I EndToEndIdentification <EndToEndId> [1..1] E PaymentTypeInformation <PmtTpInf> [0..1] Payment type Double check using the combination of Instruction Id (optional) and EndtoEnd Id (mandatory). If present, Id to be returned only to ordering party in account statement reporting Mandatory, unique for at least 3 months. May not contain special characters ServiceLevel Code <SvcLvl> <Cd> [0..1] [0..1] URGP Urgent payment Amount <Amt> [1..1] InstructedAmount <InstdAmt> [1..1] USD Mandatory, instructed amount CreditorAgent <CdtrAgt> [1..1] Beneficiary s bank mandatory. Either BIC or clearing code and/or name and address (in the example) is required FinancialInstitutionIdentifi cation <FinInstnId> [1..1] ServiceLevel <SvcLvl> [0..1] Code <Cd> [0..1] URGP ClearingSystemMemberIde ntification ClearingSystemIdentificati on <ClrSysMmbId> [0..1] Clearing code <ClrSysId> [0..1] In the example the beneficiary s bank is expressed with the clearing code. When the clearing code is used, the bank s name and address are required, if known. If the bank s information is entered without the BIC or the clearing code, the name, address information and the bank s country code must be entered. Code <Cd> [0..1] USABA US ABA number (Fedwire). See additional information in section Clearing codes. Clearing number MemberIdentification Name PostalAddress <MmbId> <Nm> <PstAdr> [1..1] [0..1] [0..1] BANK OF STATES Bank s name CountrySubDivision <CtrySubDvsn> [0..1] MASSACHUSETTS Optional, recommended May

50 Country <Ctry> [0..1] US Optional, recommended Creditor <Cdtr> [1..1] Name <Nm> [1..1] Ben E. Ficiary Mandatory PostalAddress <PstAdr> [0..1] Country <Ctry> [1..1] US Mandatory if address is given AdressLine <AdrLine> [0..2] Boston Information that locates and identifies a specific address, as defined by postal services, presented in free format text CreditorAccount <CdtrAcct> [0..1] Mandatory for credit transfers Identification [1..1] Other <Othr> [1..1] Identification [1..1] RegulatoryReporting <RgltryRptg> [0..10] Other than IBAN account number is presented with Identification information only. SchemeName / Code, eg BBAN, can be given but is not necessary. Information needed due to regulatory and statutory requirements Details <Dtls> [0..n] Code <Cd> [0..1] 151 Payment reason code RemittanceInformation <RmtInf> [0..1] Optional, payment specifications Unstructured <Ustrd> [0..1] Invoices 123 and 321 C. CreditTransferTransacti on Information (5th payment) <CdtTrfTxInf> [1..n] Credit information - RegulatoryReporting <RgltryRptg> [0..10] RUB payments to Russia One occurrence (max 70 characters) of free text is forwarded in foreign currency payments. EndToEnd Id reserves 35 characters. PaymentIdentification <PmtId> [1..1] InstructionIdentification <InstrId> [0..1] I EndToEndIdentification <EndToEndId> [1..1] E Double check using the combination of Instruction Id (optional) and EndtoEnd Id (mandatory). If present, Id to be returned only to ordering party in account statement reporting Mandatory, unique for at least 3 months. May not contain special characters Amount <Amt> [1..1] InstructedAmount CreditorAgent <InstdAmt> <CdtrAgt> [1..1] [1..1] RUB Mandatory, instructed amount Beneficiary s bank mandatory. Either BIC or clearing code and/or name and address (in the example) is required FinancialInstitutionIdentifi cation <FinInstnId> [1..1] In the example the beneficiary s bank is expressed with the clearing code. When the clearing code is used, the bank s name and address are required, if known. InstructionIdentification <InstrId> [0..1] I If the bank s information is entered without the BIC or the clearing code, the name, address information and the bank s country code must be entered. EndToEndIdentification <EndToEndId> [1..1] E ClearingSystemMemberIde ntification ClearingSystemIdentificati on <ClrSysMmbId> [0..1] Clearing code <ClrSysId> [0..1] May

51 Code <Cd> [0..1] RUCBC See additional information in section Clearing codes. MemberIdentification Name PostalAddress <MmbId> <Nm> <PstAdr> [1..1] [0..1] [0..1] Moscow Bank Clearing number Bank s name Country <Ctry> [0..1] RU Optional, recommended AdressLine <AdrLine> [0..2] Main street AdressLine <AdrLine> [0..2] Moscow Information that locates and identifies a specific address, as defined by postal services, presented in free format text Information that locates and identifies a specific address, as defined by postal services, presented in free format text CreditorAgentAccount <CdtrAgtAcct> [0..1] Identification [1..1] Other <Othr> [1..1] Identification [1..1] Creditor <Cdtr> [1..1] Name <Nm> [1..1] Company Mandatory PostalAddress <PstAdr> [0..1] Country <Ctry> [1..1] RU Mandatory if address is given AdressLine <AdrLine> [0..2] Moscow Identification [0..1] OrganisationIdentification <OrgId> [1..1] Other <Othr> [0..n] Identification [1..1] INN Information that locates and identifies a specific address, as defined by postal services, presented in free format text INN code CreditorAccount <CdtrAcct> [0..1] Mandatory for credit transfers Identification [1..1] Other <Othr> [1..1] Identification [1..1] RegulatoryReporting <RgltryRptg> [0..10] Details <Dtls> [0..n] Other than IBAN account number is presented with Identification information only. SchemeName / Code, eg BBAN, can be given but is not necessary. Information needed due to regulatory and statutory requirements Code <Cd> [0..1] 151 Payment reason code RemittanceInformation <RmtInf> [0..1] Optional, payment specifications Unstructured <Ustrd> [0..1] (VO12345) Invoices 123 and 321 One occurrence (max 70 characters) of free text is forwarded in foreign currency payments. EndToEnd Id reserves 35 characters. Salary payments Message item XML tag M/O Content Comment May

52 A. GroupHeader <GrpHdr> [1..1] MessageIdentification <MsgId> [1..1] CreationDateTime <CreDtTm> [1..1] T10:30:00 Mandatory, unique for at least 3 months. May not contain special characters Mandatory, valid values: current date -30 and +1 calendar days NumberOfTransactions <NbOfTxs> [1..1] 2 Mandatory, number of transactions (C-level) ControlSum <CtrlSum> [0..1] Optional. Sum of amounts at C-level. InitiatingParty <InitgPty> [1..1] Mandatory Name <Nm> [0..1] Test Grupp AS Recommended to use the name B. PaymentInformation <PmtInf> First debit batch PaymentInformationIdentification <PmtInfId> [0..1] Optional, recommended, unique for at least 3 months. May not contain special characters PaymentMethod <PmtMtd> [1..1] TRF Mandatory, Transfer BatchBooking <BtchBookg> [0..1] true Not mandatory, default value false PaymentTypeInformation <PmtTpInf> [0..1] CategoryPurpose <CtgyPurp> [0..1] Code <Cd> [1..1] SALA for pension payments PENS RequestedExecutionDate <ReqdExctnDt> [1..1] Debtor <Dbtr> [1..1] Name <Nm> [1..1] Test Grupp AS Mandatory, valid values: max +90 and -5 calendar days Mandatory The name of the accountholder is transmitted to the beneficiary from Nordea s customer register. PostalAddress <PstlAdr> [0..1] Country <Ctry> [1..1] EE Optional AddressLine <AdrLine> [0..1] Kuuse 6, Tallinn, Eesti Optional Identification [1..1] OrganisationIdentification <OrgId> [1..1] Other <Othr> [1..1] Identification [0..1] Mandatory if not given on GroupHeader level. Service Id given by Nordea. If given in PaymentInformation element, the Id given in GroupHeader is not taken into account in this batch. SchemeName <SchmeNm> [1..1] Code <Cd> [1..1] BANK BANK = BankPartyIdentification, ExternalCode value DebtorAccount <DbtrAcct> [1..1] Identification [1..1] IBAN <IBAN> [1..1] EE Mandatory, payer s account in IBAN format DebtorAgent <DbtrAgt> [1..1] May

53 FinancialInstitutionIdentification <FinInstnId> [1..1] BIC <BIC> [1..1] NDEAEE2X Mandatory, payer bank s BIC ChargeBearer <ChrgBr> [0..1] SHAR Optional. Default value: shared charges. C. CreditTransferTransaction Information (1st payment) <CdtTrfTxInf> [1..n] Credit information - Salary 1st beneficiary PaymentIdentification <PmtId> [1..1] Double check using the combination of Instruction Id (optional) and EndtoEnd Id (mandatory). InstructionIdentification <InstrId> [0..1] EndToEndIdentification <EndToEndId> [1..1] Amount <Amt> [1..1] I E If present, Id to be returned only to ordering party in account statement reporting Mandatory, unique for at least 3 months. May not contain special characters InstructedAmount <InstdAmt> [1..1] EUR Mandatory, instructed amount CreditorAgent <CdtrAgt> [0..1] FinancialInstitutionIdentification <FinInstnId> [0..1] BIC <BIC> [0..1] Creditor <Cdtr> [0..1] Name <Nm> [1..1] Identification [0..1] PrivateIdentification <PrvtId> [1..1] Other <Othr> [0..n] Identification [1..1] CreditorAccount <CdtrAcct> [0..1] Identification [1..1] NDEAEE2X Test Saaja BIC of beneficiary s bank is optional for SEPA credit transfers. If not given, Nordea will derive BIC from IBAN. Mandatory, creditor name Optional IBAN <IBAN> [1..1] EE Mandatory, creditor IBAN RemittanceInformation <RmtInf> [0..1] Optional, payment specifications Unstructured <Ustrd> [0..1] C. CreditTransferTransaction Information (2nd payment) <CdtTrfTxInf> [1..n] Palk One occurrence (max 140 characters) Credit information - Salary 2nd beneficiary PaymentIdentification <PmtId> [1..1] Double check using the combination of Instruction Id (optional) and EndtoEnd Id (mandatory). InstructionIdentification <InstrId> [0..1] I If present, Id to be returned only to ordering party in account statement reporting EndToEndIdentification <EndToEndId> [1..1] E Mandatory, unique for at least 3 months. May not contain special characters Amount <Amt> [1..1] May

54 InstructedAmount <InstdAmt> [1..1] EUR Mandatory, instructed amount CreditorAgent <CdtrAgt> [0..1] FinancialInstitutionIdentification <FinInstnId> [0..1] BIC <BIC> [0..1] HABAEE2X BIC of beneficiary s bank is optional for SEPA credit transfers. If not given, Nordea will derive BIC from IBAN. Creditor <Cdtr> [0..1] Name <Nm> [1..1] Identification [0..1] PrivateIdentification <PrvtId> [1..1] Other <Othr> [0..n] Identification [1..1] CreditorAccount <CdtrAcct> [0..1] Identification [1..1] Test Saaja Mandatory, creditor name Optional IBAN <IBAN> [1..1] EE Mandatory, creditor IBAN RemittanceInformation <RmtInf> [0..1] Optional, payment specifications Unstructured <Ustrd> [0..1] Puhkus One occurrence (max 140 characters) XML example <?xml version="1.0" encoding="utf-8"?> <Document xmlns="urn:iso:std:iso:20022:tech:xsd:pain " xmlns:xsi=" xsi:schemalocation="urn:iso:std:iso:20022:tech:xsd:pain pain xsd"> <CstmrCdtTrfInitn> <GrpHdr> <MsgId>MSG000001</MsgId> <CreDtTm> T15:35:45Z</CreDtTm> <NbOfTxs>2</NbOfTxs> <CtrlSum>6.55</CtrlSum> <InitgPty> <Nm>Test Grupp AS</Nm> </InitgPty> </GrpHdr> <!-- **************************************************************** Payment Information block **************************************************************** --> <PmtInf> <PmtInfId>TR000001</PmtInfId> <PmtMtd>TRF</PmtMtd> <BtchBookg>false</BtchBookg> <ReqdExctnDt> </ReqdExctnDt> <Dbtr> <Nm>Test Grupp AS</Nm> <PstlAdr> <Ctry>EE</Ctry> <AdrLine>Kuuse 6, Tallinn, Eesti</AdrLine> </PstlAdr> <OrgId> <Othr> <SchmeNm> <Cd>BANK</Cd> </SchmeNm> May

55 </Dbtr> <DbtrAcct> </OrgId> </Othr> <IBAN>EE </IBAN> </DbtrAcct> <DbtrAgt> <FinInstnId> <BIC>NDEAEE2X</BIC> </FinInstnId> </DbtrAgt> <ChrgBr>SHAR</ChrgBr> <!-- **************************************************************** 1. Urgent domestic payment **************************************************************** --> <CdtTrfTxInf> <PmtId> <InstrId>PMT000001</InstrId> <EndToEndId>NOTPROVIDED</EndToEndId> </PmtId> <PmtTpInf> <SvcLvl> <Cd>URGP</Cd> </SvcLvl> </PmtTpInf> <Amt> <InstdAmt Ccy="EUR">3.83</InstdAmt> </Amt> <CdtrAgt> <FinInstnId> <BIC>HABAEE2X</BIC> </FinInstnId> </CdtrAgt> <Cdtr> <Nm>Testklient1 AS</Nm> <PstlAdr> <Ctry>EE</Ctry> <AdrLine>Palmi 2, Tallinn, Eesti</AdrLine> </PstlAdr> </Cdtr> <CdtrAcct> <IBAN>EE </IBAN> </CdtrAcct> <RmtInf> <Ustrd>Testarve A tasumine</ustrd> </RmtInf> </CdtTrfTxInf> <!-- **************************************************************** 2. Domestic payment **************************************************************** --> <CdtTrfTxInf> <PmtId> <InstrId>PMT000002</InstrId> <EndToEndId>NOTPROVIDED</EndToEndId> </PmtId> <PmtTpInf> <SvcLvl> <Cd>NURG</Cd> </SvcLvl> </PmtTpInf> <Amt> <InstdAmt Ccy="EUR">2.72</InstdAmt> </Amt> <CdtrAgt> <FinInstnId> May

56 <BIC>EEUHEE2X</BIC> </FinInstnId> </CdtrAgt> <Cdtr> <Nm>Testklient2 AS</Nm> <PstlAdr> <Ctry>EE</Ctry> <AdrLine>Ketta 8, Tallinn, Eesti</AdrLine> </PstlAdr> </Cdtr> <CdtrAcct> <IBAN>EE </IBAN> </CdtrAcct> <RmtInf> <Ustrd>Testarve A tasumine</ustrd> <Strd> <CdtrRefInf> <Tp> <CdOrPrtry> <Cd>SCOR</Cd> </CdOrPrtry> </Tp> <Ref> </Ref> </CdtrRefInf> </Strd> </RmtInf> </CdtTrfTxInf> <!-- **************************************************************** 3. Cross-border payment **************************************************************** --> <CdtTrfTxInf> <PmtId> <InstrId>I000003</InstrId> <EndToEndId> E000003</EndToEndId> </PmtId> <Amt> <InstdAmt Ccy="USD"> </InstdAmt> </Amt> <CdtrAgt> <FinInstnId> <BIC>BANKUS33</BIC> </FinInstnId> </CdtrAgt> <Cdtr> <Nm>Hyatt Central, </Nm> <PstlAdr> <Ctry>US</Ctry> <AdrLine>New York</AdrLine> </PstlAdr> <CtryOfRes>US</CtryOfRes> </Cdtr> <CdtrAcct> <Othr> </Othr> </CdtrAcct> <RgltryRptg> <Dtls> <Cd>151</Cd> </Dtls> </RgltryRptg> <RmtInf> <Ustrd>Invoices 123 and 321</Ustrd> </RmtInf> </CdtTrfTxInf> <!-- **************************************************************** 4. Urgent cross-border payment May

57 **************************************************************** --> <CdtTrfTxInf> <PmtId> <InstrId>I000004</InstrId> <EndToEndId> E000004</EndToEndId> </PmtId> <PmtTpInf> <SvcLvl> <Cd>URGP</Cd> </SvcLvl> </PmtTpInf> <Amt> <InstdAmt Ccy="USD"> </InstdAmt> </Amt> <CdtrAgt> <FinInstnId> <ClrSysMmbId> <ClrSysId> <Cd>USABA</Cd> </ClrSysId> <MmbId> </MmbId> </ClrSysMmbId> <Nm>BANK OF STATES</Nm> <PstlAdr> <CtrySubDvsn>MASSACHUSETTS</CtrySubDvsn> <Ctry>US</Ctry> </PstlAdr> </FinInstnId> </CdtrAgt> <Cdtr> <Nm>Ben E. Ficiary</Nm> <PstlAdr> <Ctry>US</Ctry> <AdrLine>Boston</AdrLine> </PstlAdr> </Cdtr> <CdtrAcct> <Othr> </Othr> </CdtrAcct> <RgltryRptg> <Dtls> <Cd>151</Cd> </Dtls> </RgltryRptg> <RmtInf> <Ustrd>Invoices 123 and 321</Ustrd> </RmtInf> </CdtTrfTxInf> <!-- **************************************************************** 5. RUB payment to Russia **************************************************************** --> <CdtTrfTxInf> <PmtId> <InstrId>I000005</InstrId> <EndToEndId> E000005</EndToEndId> </PmtId> <Amt> <InstdAmt Ccy="RUB"> </InstdAmt> </Amt> <CdtrAgt> <FinInstnId> <ClrSysMmbId> <ClrSysId> <Cd>RUCBC</Cd> </ClrSysId> <MmbId> </MmbId> </ClrSysMmbId> May

58 <Nm>Moscow Bank</Nm> <PstlAdr> <Ctry>RU</Ctry> <AdrLine>Main street</adrline> <AdrLine>Moscow</AdrLine> </PstlAdr> </FinInstnId> </CdtrAgt> <CdtrAgtAcct> <Othr> </Othr> </CdtrAgtAcct> <Cdtr> <Nm>Company</Nm> <PstlAdr> <Ctry>RU</Ctry> <AdrLine>Moscow</AdrLine> </PstlAdr> <OrgId> <Othr> INN </Othr> </OrgId> </Cdtr> <CdtrAcct> <Othr> </Othr> </CdtrAcct> <RgltryRptg> <Dtls> <Cd>151</Cd> </Dtls> </RgltryRptg> <RmtInf> <Ustrd>(VO12345) Invoices 123 and 321</Ustrd> </RmtInf> </CdtTrfTxInf> </PmtInf> </CstmrCdtTrfInitn> </Document> Salary payment <?xml version="1.0" encoding="utf-8"?> <Document xmlns="urn:iso:std:iso:20022:tech:xsd:pain " xmlns:xsi=" xsi:schemalocation="urn:iso:std:iso:20022:tech:xsd:pain pain xsd"> <CstmrCdtTrfInitn> <GrpHdr> <MsgId> MSG000001</MsgId> <CreDtTm> T15:44:35Z </CreDtTm> <NbOfTxs>2</NbOfTxs> <CtrlSum>301.02</CtrlSum> <InitgPty> <Nm> Test Grupp AS </Nm> </InitgPty> </GrpHdr> <PmtInf> <PmtInfId> TR000001</PmtInfId> <PmtMtd>TRF</PmtMtd> <BtchBookg>true</BtchBookg> <PmtTpInf> <CtgyPurp> <Cd>SALA</Cd> </CtgyPurp> May

59 </PmtTpInf> <ReqdExctnDt> </ReqdExctnDt> <Dbtr> <Nm> Test Grupp AS </Nm> <PstlAdr> <Ctry>EE</Ctry> <AdrLine> Kuuse 6, Tallinn, Eesti </AdrLine> </PstlAdr> <OrgId> <Othr> <SchmeNm> <Cd>BANK</Cd> </SchmeNm> </Othr> </OrgId> </Dbtr> <DbtrAcct> <IBAN>EE </IBAN> </DbtrAcct> <DbtrAgt> <FinInstnId> <BIC>NDEAEE2X</BIC> </FinInstnId> </DbtrAgt> <ChrgBr>SHAR</ChrgBr> <CdtTrfTxInf> <PmtId> <InstrId> I000001</InstrId> <EndToEndId> E000001</EndToEndId> </PmtId> <Amt> <InstdAmt Ccy="EUR">100.01</InstdAmt> </Amt> <CdtrAgt> <FinInstnId> <BIC>NDEAEE2X</BIC> </FinInstnId> </CdtrAgt> <Cdtr> <Nm> Test Saaja1</Nm> <PrvtId> <Othr> </Othr> </PrvtId> </Cdtr> <CdtrAcct> <IBAN>EE </IBAN> </CdtrAcct> <RmtInf> <Ustrd> Palk </Ustrd> </RmtInf> </CdtTrfTxInf> <CdtTrfTxInf> <PmtId> <InstrId> I </InstrId> <EndToEndId> E000002</EndToEndId> </PmtId> <Amt> <InstdAmt Ccy="EUR">200.01</InstdAmt> </Amt> <CdtrAgt> <FinInstnId> <BIC>HABAEE2X</BIC> </FinInstnId> May

60 </CdtrAgt> <Cdtr> <Nm> Test Saaja2</Nm> <PrvtId> <Othr> </Othr> </PrvtId> </Cdtr> <CdtrAcct> <IBAN>EE </IBAN> </CdtrAcct> <RmtInf> <Ustrd> Puhkus </Ustrd> </RmtInf> </CdtTrfTxInf> </PmtInf> </CstmrCdtTrfInitn> </Document> 5. Additional instructions 5.1 Service ID Nordea s service ID is mandatory information. It can be given: 5.2 Defining the payment type Latvia In the Initiating Party / OrganisationIdentification element, in which case it will be used as the service ID for all batches in the message In the Debtor / OrganisationIdentification element, in which case it will be used as the payer s service ID. The Debtor service ID is used even if a service ID has been given in Initiating Party. In the ISO standard the payment type can be given both on the debit level and on the credit level. We recommend that the payment type is given on the debit level. In salary and pension payments the Category Purpose SALA must be given on the debit level. In foreign currency payments the payment type can also be on the credit level, if it has not been given on the debit level. Credit transfers payment method TRF Nordea determines payment type from the given data based on following information: Internal payments: Payment is between Nordea LV accounts in any, supported by Nordea, currency. Domestic payments: Instructed payment currency is LVL and the beneficiarie s bank is in LV SEPA credit transfers: Nordea determines from the given data whether the payment conforms to the SEPA rules and routes the payment to the SEPA channel. Hence the SEPA code in Payment Type Information / Service Level is not needed, but it can be given. If the Service Level SEPA is given but the payment does not fulfill the SEPA criteria, the payment is routed as a foreign currency payment. May

61 Routing of payments to SEPA processing: the instructed currency is the euro;the credit account is in IBAN format and the beneficiary s bank adheres to the SEPA credit transfer rules: Lithuania: Foreign currency payments: Routing of payments to foreign currency payment processing: the instructed currency is other than the LVL, and the beneficiary s bank BICis not NDEALV2X, or the instructed currency is LVL and the beneficiary s bank is not in LV Same day value payments: <PmtTpInf><SvcLvl><Cd>SDVA Intra company <PmtTpInf><SvcLvl><Cd>INTC Salary/Pension payments: Salary and pension payments are processed in batches and payments should satisfy following rules: only currency LVL is allowed one of CategoryPurpose codes SALA or PENS are given; Beneficiarie s bank BIC is in LV Single payments inside the batch that does not apply domestic or internal payment rules or currency is not LVL, will be rejected. if batch booking indicator is False and SALA/PENS tags are given payment is processed as single transactions. Credit transfers payment method TRF Nordea determines payment type from the given data based on following information: Internal payments: Payment is between Nordea LT accounts in any, supported by Nordea, currency. Domestic payments: Instructed payment currency is LTL and the beneficiarie s bank is in LT SEPA credit transfers: Nordea determines from the given data whether the payment conforms to the SEPA rules and routes the payment to the SEPA channel. Hence the SEPA code in Payment Type Information / Service Level is not needed, but it can be given. If the Service Level SEPA is given but the payment does not fulfill the SEPA criteria, the payment is routed as a foreign currency payment. Routing of payments to SEPA processing: the instructed currency is the euro;the credit account is in IBAN format and the beneficiary s bank adheres to the SEPA credit transfer rules:international euro payments to the countries that are SEPA compliment will be automatically converted to SEPA payments. In this case if BE19 error code is received, then <ChrgBr> values should be set to SLEV and urgency must be set to REGL or XML value deleted. Foreign currency payments: Routing of payments to foreign currency payment processing: the instructed currency is other than the LTL, and the beneficiary s bank BICis not NDEALT2X, or the instructed currency is LTL and the beneficiary s bank is not in LT Same day value payments May

62 <PmtTpInf><SvcLvl><Cd>SDVA Intra company <PmtTpInf><SvcLvl><Cd>INTC Estonia: Salary payments: Salary and pension payments are processed in batches and payments should satisfy following rules: only currency LTL is allowed one of CategoryPurpose codes SALA is given; Beneficiarie s bank BIC is in LT Single payments inside the batch that does not apply domestic or internal payment rules or currency is not LTL, will be rejected. if batch booking indicator is False and SALA tags are given payment is processed as single transactions. Credit transfers payment method TRF Nordea determines payment type from the given data based on following information: Internal payments: Payment is between Nordea EE accounts in any, supported by Nordea, currency. Domestic payments: Instructed payment currency is EUR and the beneficiarie s bank is in EE. Nordea determines from the given data whether the payment conforms to the domestic rules and routes the payment to the domestic channel if SEPA code in Payment Type Information / Service Level is not given. Routing of payments to domestic processing: the instructed currency is the euro; the beneficiarie s bank is in EE; SEPA code in Payment Type Information / Service Level is not given. SEPA credit transfers: Nordea determines from the given data whether the payment conforms to the SEPA rules and routes the payment to the SEPA channel. Hence the SEPA code in Payment Type Information / Service Level is not needed, but it can be given. If the Service Level SEPA is given but the payment does not fulfill the SEPA criteria, the payment is routed as a foreign currency payment. Routing of payments to SEPA processing: the instructed currency is the euro; the credit account is in IBAN format and the beneficiary s bank adheres to the SEPA credit transfer rules; either the beneficiarie s bank is not in EE or SEPA code in Payment Type Information / Service Level is given. Foreign currency payments: Routing of payments to foreign currency payment processing: the instructed currency is other than the EUR and the beneficiary s bank BICis not NDEAEE2X, or the instructed currency is EUR and the beneficiary s bank is not in EE and beneficiary s bank does not adhere to the SEPA credit transfer rules Same day value payments <PmtTpInf><SvcLvl><Cd>SDVA Intra company <PmtTpInf><SvcLvl><Cd>INTC Salary/Pension payments: May

63 Salary and pension payments are processed in batches and payments should satisfy following rules: only currency EUR is allowed one of CategoryPurpose codes SALA or PENS are given; Beneficiarie s bank BIC is in EE Single payments inside the batch that does not apply domestic or internal payment rules or currency is not EUR, will be rejected. if batch booking indicator is false and SALA/PENS tags are given payment is processed as single transactions 5.3 Character set and special characters The files sent to Nordea must be in UTF-8 format. Special characters, are not allowed in identification elements (MessageId, PaymentInformationId, InstructionId, and EndtoEndId). If Nordea forwards a foreign currency payment to a beneficiary s bank or an intermediary bank via the SWIFT network, the non-permitted SWIFT characters will be replaced by _. Local characters in foreign currency payments will be converted as follows: ā replaced by a, ē replaced by e. The replaced characters are in elements payer, beneficiary, remittance information and identification. Amount fields The amount fields in payment orders are cut after two decimals. The amount field printed on the feedback message has five decimals. The XML tags in the amount field may not include special characters (eg line divisions) or spaces. The amount of the payment is given in the Instructed Amount element, see examples. 5.4 Payer s identifications for the payment The ISO standard has two transaction level IDs for a payment: EndToEnd ID (mandatory) is transmitted to the beneficiary and returned to the payer on feedback messages (see Payment Status Report ) and on the account statement. Instruction ID (optional) is not transmitted through the payment chain but is returned only to the payer on feedback messages and the account statement. The IDs must be unique for 3 months. The service checks that the transaction s EndToEnd ID and Instruction ID are unique for 3 months. If not, the payment is assumed a double transaction and is rejected. In a SEPA credit transfer the EndToEnd Id is transmitted to the beneficiary in its own field. In foreign currency payments the service moves the EndToEnd Id to the remittance information field on row 1 with the prefix /ROC/ ( Ordering Customer Reference ). In this case there is one less row for free text available. 5.5 Creditor reference on credit transfer The international reference (ISO 11649, RF reference) is transmitted in SEPA payments as such. In foreign currency payments the international reference must be in the unstructured remittance information. Content International reference RF Example of the RemittanceInformation of an XML message <RmtInf> <Strd> <CdtrRefInf> <Tp> <CdOrPrtry><Cd>SCOR</Cd></CdOrPrtry> <Issr>ISO</Issr> </Tp> <Ref>RF </Ref> </CdtrRefInf> </Strd> </RmtInf> May

64 5.6 Clearing codes ISO clearing codes are maintained in External Code Lists, which can be found on the ISO web pages. Nordea checks the allowed values on the basis of the list. ClearingSystemMemberIdentification Clearing System Member Identification Country Clearing Code Long Name Payment System Prefix Bank Identifier ([charactertype] {length}) Example 1 Australia Australian Bank State Branch Code (BSB) AUBSB [0-9]{6,6} AUBSB Austria Austrian Bankleitzahl ATBLZ [0-9]{5,5} ATBLZ Canada Canadian Payments Association Payment Routing CACPA [0-9]{9,9} CACPA Number 4 China CNAPS Identifier CNAPS [0-9]{12,12} CNAPS Germany German Bankleitzahl DEBLZ [0-9]{8,8} DEBLZ Greece Helenic Bank Identification Code GRBIC [0-9]{7,7} GRHIC Hong Kong Hong Kong Bank Code HKNCC [0-9]{3,3} HKNCC123 8 India Indian Financial System Code INFSC [a-za-z0-9]{11,11} INFSC123AZ Ireland Irish National Clearing Code IENCC [0-9]{6,6} IENCC Italy Italian Domestic Identification Code ITNCC [0-9]{10,10} ITNCC Japan Japan Zengin Clearing Code JPZGN [0-9]{7,7} JPZGN New Zealand New Zealand National Clearing Code NZNCC [0-9]{6,6} NZNCC Poland Polish National Clearing Code PLKNR [0-9]{8,8} PLKNR Portugal Portuguese National Clearing Code PTNCC [0-9]{8,8} PTNCC Russia Russian Central Bank Identification Code RUCBC [0-9]{9,9} RUCBC Singapore IBG Sort Code SGIBG [0-9]{7,7} or SGIBG [0-9]{3,4} 17 South Africa South African National Clearing Code ZANCC [0-9]{6,6} ZANCC Spain Spanish Domestic Interbanking Code ESNCC [0-9]{8,9} ESNCC Switzerland Swiss Clearing Code (BC Code) CHBCC [0-9]{3,5} CHBCC Switzerland Swiss Clearing Code (SIC Code) CHSIC [0-9]{6,6} CHSIC Taiwan Financial Institution Code TWNCC [0-9]{7,7} TWNCC UK UK Domestic Sort Code GBDSC [0-9]{6,6} GBDSC US CHIPS Participant Identifier USPID [0-9]{4,4} USPID US United States Routing Number (Fedwire, NACHA) USABA [0-9]{9,9} USABA Note Value is used to identify Bank ID schemes unique to an individual payment system. SWIFT BIC does not appear on this list as it is separately addressed in the standard. The value "XXXXX" may be used by bilateral agreement to specify any of the above, where: 1 - the originator cannot produce the clearing system member identification code, but 2 - both originator and receiver understand what clearing system the payment instruction refers to. Allowed character set for Payment System Prefix = roman alphabet. 5.7 Charges In SEPA payments the charging of costs ChargeBearer is always SLEV In other payments the charging of costs ChargeBearer SHAR is mandatory when the beneficiary s bank is located in an EU or EEA country and the currency of the payment is the euro or the currency of some other member state In other cases the option in full (ChargeBearer DEBT ) can also be used. 5.8 Use of postal address There are two ways to state the postal address of the parties included in the payment (payer, beneficiary, ultimate payer, ultimate beneficiary). The structured postal address comprises street name, building number, postal code, city and country code. The unstructured option comprises two address lines (Address Line). May

65 5.9 Debit entry As a default payments are debited one by one. This means that every CreditTransferTransaction shows on the account statement as a single debit. And the feedback will be transaction-specific. A single debit is requested by giving false as the BatchBooking value in GroupHeader. XML example: <BtchBookg>false</BtchBookg> A lot debit is available only for Salary/Pension payments and is requested by giving true as BatchBooking value in GroupHeader. XML example: 5.10 By order of <BtchBookg>true</BtchBookg> Nordea transmits the name of the accountholder to the beneficiary from Nordea s customer register as the payer s name. If you want to make a payment on behalf of someone else, you can give the name of the original recipient of the invoice (Ultimate Debtor). You can either give it on debit level, which means that it applies to all payments in that batch, or for a single payment on credit level, if it is not given on debit level. In a SEPA credit transfer the data is transmitted in its own field. In foreign currency payments the service moves the name of the Ultimate Debtor to the remittance information field with the prefix B/O ( By order of ). In this case there is one line less for free text available Ultimate beneficiary The beneficiary, for example a finance company, can differ from the ultimate beneficiary. The ultimate beneficiary is given in the Ultimate Creditor field. In a SEPA credit transfer the data is transmitted in its own field. In foreign currency, internal and domestic payments this data is not transmitted Salary and pension payments 5.13 Purpose code Salary and pension payments are processed in batches and should satisfy following rules: only currency LVL for Latvia, LTL for Lithuania and EUR for Estonia is allowed; one of CategoryPurpose codes SALA or PENS is given; Creditor BIC is in LV for Latvian payments, EE for Estonian payments and LT for Lithuanian payments; Single payments inside the batch that does not apply domestic or internal payment rules or currency is not LVL for Latvia, LTL for Lithuania or EUR for Estonia, will be rejected; if batch booking indicator is False and SALA/PENS tags are given payment is processed as single transactions. The Purpose code is carried to the beneficiary in a SEPA credit transfer. The value of the Purpose code or a corresponding explanation is not carried to the payer s paper and SWIFT (MT940 and MT942) account statement. In the XML account statement the value is carried to the payer's and the beneficiary's account statements Restrictions on Remittance Information The message can contain either unstructured free-form text or structured information with the condition that neither exceeds 140 characters. One free-form message in the schema can contain a maximum of 140 characters. May

66 The number of characters in Structured Remittance Information is counted between the tags <Strd> and </Strd> (initial and final separator of the Structured Remittance Information) and the number of characters (data fields and XML tags together) must not exceed 140 characters Payments to Russia Need to be clarified Information on payments sent to Russia is available on Nordea's website at under Corporate customers (Payments and cards, Electronic foreign currency payments, Country-specific bank connection information, service description). Foreign currency payments to Russia in other currencies than the rouble use the BIC and the beneficiary's account number like other foreign currency payments. Rouble payments to Russia must include the following information: Name and address information of the beneficiary s bank o CreditorAgent, name and address required, use the Combined presentation form for bank information <Nm>Moscow Bank</Nm> <PstlAdr> <Ctry>RU</Ctry> <AdrLine>Main street</adrline> <AdrLine>Moscow</AdrLine> </PstlAdr> Clearing code of the beneficiary s bank o Creditor Agent / ClearingSytemeMember Id see Clearing codes and the creditor bank information in the example <ClrSysMmbId> <ClrSysId><Cd>RUCBC</Cd><ClrSysId> <MmbId> </MmbId> </ClrSysMmbId> Account number, ie Correspondent account number of the beneficiary s bank o The Correspondent account number is placed in the CreditorAgentAccount element <CdtrAgtAcct> <Othr> </Othr> </CdtrAgtAcct> Beneficiary s name and address information <Cdtr> <Nm>Creditor Company</Nm> <PstlAdr> <Ctry>RU</Ctry> <AdrLine>Main street</adrline> <AdrLine>Moscow</AdrLine> </PstlAdr> <CtryOfRes>RU</CtryOfRes> </Cdtr> May

67 The beneficiary s rouble account (20 digits, the 6th, 7th and 8th digit always 810 ) and INN number (INN number is information reported to the tax authorities) <CdtrAcct> </CdtrAcct> <Othr> </Othr> /INN In addition, in the message field (Unstructured) o Code for subject of payment in accordance with the regulations of the Central Bank of Russia. It is composed of VO and five digits (VO12345). A customer making rouble payments has received the relevant VO code from the beneficiary. If the customer does not have a new VO code, the payment cannot be executed until the customer has received the code from the Russian beneficiary. Nordea does not have Russian VO codes. o The subject of payment is given in English. In addition, enter the number and date of the invoice in order to enable control of the foreign exchange regulations. Example: (VO20020) PREPAYMENT TRANSPORT COST INV 123 CONTR 321 RUB 1000, Cover bank / intermediary bank In some payments the beneficiary may give the payer an instruction on how to route the payment. Such payments occur only in the US and in Russia in situations in which the payment is to be routed to the beneficiary s bank through another bank in the same country the beneficiary's bank has given instructions to send the foreign currency to a bank in a third country, for example, a Russian bank wants to have its USD payments sent to Frankfurt. The cover/intermediary bank is entered in the BIC of IntermediaryAgent1 (IntrmyAgt1/FinInstnId/BIC) Instructions to payer s bank In foreign currency payments it is possible to give instructions concerning the routing of the payment with a maximum of 60 characters in the InstructionForDebtorAgent element <InstrForDbtrAgt>. Free-form information may be used, for example, to inform Nordea about the payment routing suggested by the beneficiary. As this type of payment is always processed manually, the Instruction to payer s bank information should only be used when necessary. May

68 6. Payment Status Report After a payment message has been checked at reception and in connection with executing the payment, Nordea forms a feedback message, Payment Status Report. See also the instructions on feedback created by Nordea in section 3 Uploading and downloading messages in the Corporate Payments Service service description. The schema name of the Payment Status Report message is <pain >. The message is divided as follows: A. Group Header - ID given by Nordea for the feedback message B. Original Group Information and Status - ID and status of the original payment message C. Original Payment information and status - ID and status of the original payment batch or the transactions included in the batch. May

XML message for Credit Transfer Initiation

XML message for Credit Transfer Initiation XML message for Credit Transfer Initiation Implementation Guidelines Version 2.4 This document is greatly inspired by the Febelfin one. Table of Contents XML message for Credit Transfer Initiation... 1

More information

XML message for Credit Transfer Initiation

XML message for Credit Transfer Initiation XML message for Credit Transfer Initiation Implementation Guidelines Version 2.5 This document is greatly inspired by the Febelfin one. Table of Contents XML message for Credit Transfer Initiation... 1

More information

Danish Inpayment Form 01, 04, 15, 71, 73, 75

Danish Inpayment Form 01, 04, 15, 71, 73, 75 Danish Inpayment Form 01, 04, 15, 71, 73, 75 Change log Version no. Date Change 0.1 15.07.2014 New design 0.2 29.10.2014 Remarks in English CGI rules added in Remarks Danish Clearing rules for addresses.

More information

XML Message for SEPA Direct Debit Initiation

XML Message for SEPA Direct Debit Initiation XML Message for SEPA Direct Debit Initiation Core and Business-to-Business Implementation Guidelines Version 1.4 Table of Contents 1 Introduction... 4 1.1 SEPA Direct Debit definition... 5 1.2 Message

More information

Rules for the use of ISO standard data format in LUMINOR-TO-CUSTOMER statement

Rules for the use of ISO standard data format in LUMINOR-TO-CUSTOMER statement Rules for the use of ISO 20022 standard data format in LUMINOR-TO-CUSTOMER statement Version 1.4 September 2017 References No Description Reference 1 Guidelines on the conversion of the LITAS ESIS data

More information

Rules for the use of ISO standard data format in DNB BANK-TO-CUSTOMER statement

Rules for the use of ISO standard data format in DNB BANK-TO-CUSTOMER statement Rules for the use of ISO 20022 standard data format in DNB BANK-TO-CUSTOMER statement Version 1.3 April 2016 References No Description Reference 1 Guidelines on the conversion of the LITAS ESIS data exchange

More information

ISO XML messages for Customer Credit Transfer and Account Statement. Contents. Implementation Guideline

ISO XML messages for Customer Credit Transfer and Account Statement. Contents. Implementation Guideline ISO 20022 XML messages for Customer Credit Transfer and Account Statement Implementation Guideline Contents Introduction... 2 1. Message content of the Customer Credit Transfer... 3 2. Additional description

More information

XML message for Credit Transfer Initiation

XML message for Credit Transfer Initiation XML message for Credit Transfer Initiation Implementation Guidelines Version 3.2.a (see updates in annex 3) Table of Contents 1 Introduction... 4 1.1 Coverage... 5 1.2 Use of these Guidelines... 6 1.3

More information

XML message for Payment Initiation Implementation Guideline

XML message for Payment Initiation Implementation Guideline XML message for Payment Initiation Implementation Guideline Version 1.3 Version 1.3 Changes Updated 20160901 Customer Credit Transfer: Message element name is changed to Customer Credit Transfer Initiation

More information

XML message for Credit Transfer Initiation

XML message for Credit Transfer Initiation XML message for Credit Transfer Initiation Implementation Guidelines Version 2.0 XML message for Credit Transfer Initiation 2 Table of Contents 1 Introduction... 4 1.1 Coverage... 5 1.2 Use of these Guidelines...

More information

XML message for Payment Initiation Implementation Guideline

XML message for Payment Initiation Implementation Guideline XML message for Payment Initiation Implementation Guideline Version 1.2 Version 1.2 Changes Updated 20130916 New column XML Tag added to the Customer Credit Transfer and Payment Status Report tables Version

More information

Bank Connect. Customer Credit Transfer Pain Table of Contents

Bank Connect. Customer Credit Transfer Pain Table of Contents Bank Connect Customer Credit Transfer Pain 001.001.03 Table of Contents Introduction... 2 Scope... 2 Character set... 2 Change log... 3 Explanation on format usage... 5 1 Introduction This Danish Message

More information

XML Message for European Direct Debit Initiation

XML Message for European Direct Debit Initiation XML Message for European Direct Debit Initiation Core and Business-to-Business Implementation Guidelines Version 4.1a Belgian Financial Sector Federation rue d Arlon/Aarlenstraat, 82 B-1040 Brussels http://www.febelfin.be

More information

XML Message for European Direct Debit Initiation

XML Message for European Direct Debit Initiation XML Message for European Direct Debit Initiation Core and Business-to-Business Implementation Guidelines Version 3.0.a Belgian Financial Sector Federation rue d Arlon/Aarlenstraat, 82 B-1040 Brussels http://www.febelfin.be

More information

Format Specification

Format Specification Format Specification ISO20022-pain.001.001.03 mbank S.A. 2017.11.27 Version 1.6 1. General Info... 3 2. Short review of pain.001.001.03 file, format requirements and processing mechanism... 3 3. Type of

More information

Orders in ISO format for transfers, checks, promissory notes and direct debit payments, in euros and other currencies

Orders in ISO format for transfers, checks, promissory notes and direct debit payments, in euros and other currencies Confidence, social commitment and quality Orders in ISO 20022 format for transfers, checks, promissory notes and direct debit payments, in euros and other currencies February 2016 INDEX Page INTRODUCTION...

More information

SEPA Credit Transfer Instructions

SEPA Credit Transfer Instructions SEPA Credit Transfer Instructions STANDARD ISO 20022 pain.001.001.03 Guideline for SEPA Credit Transfer Instructions transmitted to Société Générale France Version: August 2015 ORDRE DE VIREMENT SEPA STANDARD

More information

Corporate Payments Service. Example appendix - pain.001 version 3

Corporate Payments Service. Example appendix - pain.001 version 3 Corporate Payments Service Example appendix - pain.001 version 3 January 2018 Content 1 Background... 3 2 About Corporate Payments Service... 3 3 Message structure... 3 4 Example of the payment initiation

More information

ISO Customer Direct Debit Initiation

ISO Customer Direct Debit Initiation ISO 20022 Customer Direct Debit Initiation pain.008.001.02 Version 1.0.1 Publishing date 10 January 2017 Table of contents 1 INTRODUCTION... 3 1.1 Related documents... 3 1.2 History... 3 2 GENERAL INFORMATION...

More information

Swedbank Sweden's MIG Credit Transfer and Payment Status (pain.001, pain.002) Swedbank AB (publ) (28)

Swedbank Sweden's MIG Credit Transfer and Payment Status (pain.001, pain.002) Swedbank AB (publ) (28) Swedbank Sweden's MIG Credit Transfer and Payment Status (pain.001, pain.002) Swedbank AB (publ) 2015-11-17 1 (28) ver15.02.01 Introduction This document describes the usage on a set of ISO20022 messages.

More information

pain CustomerDirectDebitInitiationV02

pain CustomerDirectDebitInitiationV02 Corporate egateway Message Implementation Guideline CustomerDirectDebitInitiationV02 MIG version: 1.2 : 01-10-2018 2 of 13 Table of Contents 1. Introduction... 3 2. Scope... 3 3. Nordea usage of 20022

More information

XML message for Payment Initiation Implementation Guideline. Pain001. Version 1.0

XML message for Payment Initiation Implementation Guideline. Pain001. Version 1.0 XML message for Payment Initiation Implementation Guideline Pain001 Version 1.0 1 Version history Version Changes Date 1.0 First version 21.09.2015 1.1 ControlSum field is mandatory in GroupHeader and

More information

Format Specification

Format Specification Format Specification ISO20022-pain.001.001.03 mbank S.A. Version 1.7 / 2018-04-13 1. General Info... 3 2. Short review of pain.001.001.03 file, format requirements and processing mechanism... 3 3. Type

More information

Format description CT-XML import

Format description CT-XML import Format description CT-XML import Rabo Cash Management Rabobank Format description CT-XML import 2 October 2017 Version 1.02 1 Contents 1 CT-XML import format... 3 1.1 CT-XML import format description...

More information

Format Specification

Format Specification Format Specification ISO20022-pain.001.001.03 mbank S.A. 2016.11.28 Version 1.5 1. General Info... 3 2. Short review of pain.001.001.03 file, format requirements and processing mechanism... 3 3. Type of

More information

Differences BTL91and Generic Payment File. RCM, RIB Pro, RDC and SWIFT FileAct

Differences BTL91and Generic Payment File. RCM, RIB Pro, RDC and SWIFT FileAct Differences BTL91and Generic Payment File RCM, RIB Pro, RDC and SWIFT FileAct Contents 1 GENERAL INFORMATION 3 2 INTRODUCTION 3 3 GENERAL DIFFERENCES 4 4 DESCRIPTION OF THE DIFFERENCES 6 APPENDIX: CHANGE

More information

Orders in ISO format for issuance of transfers and cheques in euros

Orders in ISO format for issuance of transfers and cheques in euros Orders in ISO 20022 format for issuance of transfers and cheques in euros Series of banking standards and procedures Implementation Guide Adapted to version 1.0 RB 2017 SEPA Credit Transfer November 2017

More information

Corporate Payments. Example appendix, pain.001 version 2. March 2018

Corporate Payments. Example appendix, pain.001 version 2. March 2018 Corporate Payments Example appendix, pain.001 version 2 March 2018 Content 1 Background... 3 2 About Corporate Payments Service... 3 3 The message structure... 3 4 Example of the payment initiation message...

More information

Orders in ISO format for issuance of transfer in euros and other currencies, cheques, promissory notes and direct debit payments in euros

Orders in ISO format for issuance of transfer in euros and other currencies, cheques, promissory notes and direct debit payments in euros Confianza, compromiso social y calidad Orders in ISO 20022 format for issuance of transfer in euros and other currencies, cheques, promissory notes and direct debit payments in euros February 2018 CHANGE

More information

ISO Message Implementation Guide for Payment Initiation

ISO Message Implementation Guide for Payment Initiation ISO 20022 Message Implementation Guide for Payment Initiation Pain001 Pain002 Version: 1.7 Issue date: 12 January 2017 Author: Swedbank Table of Contents 1. Introduction 2. Customer Credit Transfer Initiation

More information

ISO XML message for Payment Initiation Implementation Guideline. Version 1.0 Estonia

ISO XML message for Payment Initiation Implementation Guideline. Version 1.0 Estonia ISO 20022 XML message for Payment Initiation Implementation Guideline Version 1.0 Estonia Approved by payment standards working group of Estonian Banking Association 31.01.2013 Table of contents Table

More information

ISO Customer-to-Bank messages usage guidelines

ISO Customer-to-Bank messages usage guidelines ISO 20022 Customer-to-Bank messages usage guidelines 1 Contents 1. Foreword... 3 2. Message description... 3 3. Message structure... 4 3.1. Message structure... 4 3.2. Character set... 5 3.3. Message pain.001.001.03...

More information

pain EPC; 1.0

pain EPC; 1.0 Message Implementation Guideline pain.008.001.02 - EPC; 1.0 Model: pain.008.001.02 - EPC Version: 1.0 Issue date: June 2015 Author: Credit Suisse Message Overview... 2 Message Details... 6 Components...

More information

Danske Bank Baltic ISO XML messages for Payment Initiation and Cash Management Implementation Guideline. Pain001 Pain002 Camt052 Camt053 Camt054

Danske Bank Baltic ISO XML messages for Payment Initiation and Cash Management Implementation Guideline. Pain001 Pain002 Camt052 Camt053 Camt054 Danske Bank Baltic ISO 20022 XML messages for Payment Initiation and Cash Management Implementation Guideline Pain001 Pain002 Camt052 Camt053 Camt054 Version 1.0 1 Version history Version Changes Date

More information

pain CustomerCreditTransferInitiationV03

pain CustomerCreditTransferInitiationV03 20022 Message Implementation Guidelines for payment initiation pain.001.001.03 CustomerCreditTransferInitiationV03 Version: 0.2 : Author: Luminor Bank AB 31/08/2015 2 of 17 Table of contents 1. Introduction...

More information

Version OUTGOING PAYMENTS SERVICE DESCRIPTION. Pain Pain

Version OUTGOING PAYMENTS SERVICE DESCRIPTION. Pain Pain Version 2.6 15.1.2018 OUTGOING PAYMENTS SERVICE DESCRIPTION Pain001.001.03 Pain002.001.03 2 (54) CONTENTS VERSION INFORMATION... 4 1 OUTGOING PAYMENTS, APPLICATION GUIDELINE... 5 1.1 ISO 20022 MESSAGE

More information

Corporate Payments Service. Appendix on Request for Transfer

Corporate Payments Service. Appendix on Request for Transfer Corporate Payments Service Appendix on Request for Transfer March 2018 Content 1 Background... 2 2 Payments with Request for Transfer orders... 2 3 Messages used... 3 3.1 Payment order from a customer

More information

XML Message for Payment Status Report

XML Message for Payment Status Report XML Message for Payment Status Report Implementation Guidelines Version 1.1 Table of Contents Table of Contents... 2 1 Introduction... 5 1.1 Coverage... 6 1.2 Use of these Guidelines... 7 1.3 Character

More information

C2B - Customer to Bank Services

C2B - Customer to Bank Services SEPA Data Format (XML) Version: 02.02 Status: Final Go live date: 2016-02-01 Related Documents Reference Title Source EPC132-08 Implementation Guidelines SEPA CT C2B European Payments Council EPC130-08

More information

pain CustomerCreditTransferInitiationV03

pain CustomerCreditTransferInitiationV03 Corporate Access Payables Changes in Message Implementation Guideline pain.001.001.03 CustomerCreditTransferInitiationV03 Changes in version 1.3 since version 1.2 MIG version: 1.3 : 20-06-2016 Please refer

More information

SDD Bulk Payments XML File Format

SDD Bulk Payments XML File Format www.aib.ie/sepa SDD 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

Implementation guide. ISO CustomerPaymentStatusReport pain.002 version 3

Implementation guide. ISO CustomerPaymentStatusReport pain.002 version 3 ISO 20022 CustomerPaymentStatusReport pain.002 version 3 Version 1.0.0 Publishing date 30 August 2016 Table of contents 1 INTRODUCTION... 3 1.1 Related documents... 3 1.2 History... 3 2 GENERAL RULES...

More information

Mutual Fund Trailer Fee Payments Market Practice

Mutual Fund Trailer Fee Payments Market Practice Mutual Fund Trailer Fee Payments Market Practice ISITC Payments Working Group DISCLAIMER This market practice document has been developed by the International Securities Association for Institutional Trade

More information

Swiss Payment Standards 2018

Swiss Payment Standards 2018 Swiss Payment Standards 2018 Swiss Implementation Guidelines for Customer-Bank Messages SEPA Direct Debit (SEPA Direct Debit Scheme) Customer Direct Debit Initiation (pain.008) Version 2.6, with effect

More information

ISO Payments. Swiss Implementation Guidelines for Customer-Bank Messages SEPA Direct Debit (SEPA Direct Debit Scheme)

ISO Payments. Swiss Implementation Guidelines for Customer-Bank Messages SEPA Direct Debit (SEPA Direct Debit Scheme) ISO 20022 Payments for Customer-Bank Messages SEPA Direct Debit (SEPA Direct Debit Scheme) Version 2.5.2 21.08.2017 General note Any suggestions or questions relating to this document should be addressed

More information

SEPA BUSINESS-TO-BUSINESS DIRECT DEBIT SCHEME CUSTOMER-TO-BANK IMPLEMENTATION GUIDELINES

SEPA BUSINESS-TO-BUSINESS DIRECT DEBIT SCHEME CUSTOMER-TO-BANK IMPLEMENTATION GUIDELINES Doc: EPC131-08 26 January 2015 (Version 7.0 Approved) EPC SEPA BUSINESS-TO-BUSINESS DIRECT DEBIT SCHEME CUSTOMER-TO-BANK IMPLEMENTATION GUIDELINES Abstract Document Reference Issue This document sets out

More information

UBS Implementation Guidelines

UBS Implementation Guidelines US Implementation Guidelines Swiss Recommendations for credit transfers pain.001.001.03.ch.02 - SR Version 1.5.1 US Version 1.0 July 2016 US Implementation Guidelines Swiss Recommendations for credit transfers

More information

pain MandateInitiationRequestV03

pain MandateInitiationRequestV03 Corporate egateway Message Implementation Guideline MandateInitiationRequestV03 MIG version: 1.2 : 11-02-2017 2 of 14 Table of Contents 1. Introduction... 3 2. Scope... 3 3. Document references... 4 4.

More information

Implementation guide. ISO CustomerPaymentStatusReport pain.002 version 2

Implementation guide. ISO CustomerPaymentStatusReport pain.002 version 2 ISO 20022 CustomerPaymentStatusReport pain.002 version 2 Version 1.0.0 Publishing date 30 August 2016 Table of contents 1 INTRODUCTION... 3 1.1 Related documents... 3 1.2 History... 3 2 GENERAL RULES...

More information

pain ch-six cs-st; 1

pain ch-six cs-st; 1 Message Implementation Guideline Model: pain.002.001.03-ch-six-1.5. Version: 1 Issue date: November 2016 Author: Credit Suisse (Switzerland) Ltd. Message Overview... 2 Message Details... 5 Components...

More information

CZECH REPUBLIC INSIDEBUSINESS PAYMENTS CZECH REPUBLIC ANNEX. File formats and validations. Contents

CZECH REPUBLIC INSIDEBUSINESS PAYMENTS CZECH REPUBLIC ANNEX. File formats and validations. Contents INSIDEBUSINESS PAYENTS CZECH REPUBLIC ANNEX File formats and validations Contents Validation of fields 2 CFD File Format 3 CFA File Format 5 Single credit transfer format T103 8 Single European Credit

More information

pain MandateCancellationRequestV03

pain MandateCancellationRequestV03 Corporate egateway Message Implementation Guideline MandateCancellationRequestV03 MIG version: 1.2 : 01-10-2018 2 of 12 Table of Contents 1. Introduction... 3 2. Scope... 3 3. Document references... 3

More information

SEPA B2B DIRECT DEBIT SCHEME ADVANCE MANDATE INFORMATION SERVICE IMPLEMENTATION GUIDELINES

SEPA B2B DIRECT DEBIT SCHEME ADVANCE MANDATE INFORMATION SERVICE IMPLEMENTATION GUIDELINES Doc: EPC315-10 26 January 2015 (Version 7.0 Approved) EPC SEPA B2B DIRECT DEBIT SCHEME ADVANCE MANDATE INFORMATION SERVICE IMPLEMENTATION GUIDELINES Abstract Document Reference Issue This document sets

More information

pain CustomerCreditTransferInitiationV03

pain CustomerCreditTransferInitiationV03 Corporate Access Payables Message Implementation Guidelines pain.001.001.03 CustomerCreditTransferInitiationV03 MIG version: 1.6 : eference to Treasury payments expected to be launched during Q1 2019 2

More information

Service description. Corporate Access Payables Appendix Norway

Service description. Corporate Access Payables Appendix Norway Service description Corporate Access Payables Appendix Norway Page 2 of 16 Table of contents 1 APPENDIX NORWAY... 3 2 GENERAL OVERVIEW OF THE NORWEGIAN PAYMENT INFRASTRUCTURE... 3 2.1 AVAILABLE PAYMENT

More information

ISO Credit Notification

ISO Credit Notification ISO 20022 Credit Notification camt.054 version 2 Version 1.0.0 Publishing date 30 November 2012 Table of contents 1 INTRODUCTION... 3 1.1 Related documents... 3 1.2 History... 3 2 GENERAL RULES... 4 2.1

More information

pain CustomerCreditTransferInitiationV03

pain CustomerCreditTransferInitiationV03 Corporate Access Payables Message Implementation Guidelines CustomerCreditTransferInitiationV03 MIG version: 1.7 : 2 of 31 Table of contents 1. Introduction... 3 2. About Corporate Access Payables... 3

More information

ISO Message Implementation Guide for Cash Management Reports

ISO Message Implementation Guide for Cash Management Reports ISO 20022 Message Implementation Guide for Cash Management Reports CAMT052 CAMT053 CAMT054 CAMT060 Version: 1.5 Issue date: 9 July 2015 Author: Swedbank Table of Contents 1. Introduction 2. Bank To Customer

More information

pain CustomerCreditTransferInitiationV03

pain CustomerCreditTransferInitiationV03 Corporate Access Payables Message Implementation Guidelines pain.001.001.03 CustomerCreditTransferInitiationV03 MIG version: 1.5 : eference to equest for Transfer expected to be launched during Q4 2018

More information

Implementation guide. ISO Credit Notification camt.054 version 2

Implementation guide. ISO Credit Notification camt.054 version 2 Implementation guide ISO 20022 Credit Notification camt.054 version 2 Version 1.1.1 Publishing date 13 April 2018 Implementation guide Table of contents 1 INTRODUCTION... 3 1.1 Related documents... 3 1.2

More information

Service description Corporate Access Payables Appendix Denmark

Service description Corporate Access Payables Appendix Denmark Service description Corporate Access Payables Appendix Denmark Page 2 of 21 Table of contents 1 APPENDIX - DENMARK... 3 2 GENERAL OVERVIEW OF THE DANISH PAYMENT INFRASTRUCTURE... 3 2.1 AVAILABLE PAYMENT

More information

Implementation guide. ISO Extended Account Statement camt.053 version 2

Implementation guide. ISO Extended Account Statement camt.053 version 2 Implementation guide ISO 20022 Extended Account Statement camt.053 version 2 Version 1.2.2 Published 13 April 2018 Implementation guide Table of contents 1 INTRODUCTION... 3 1.1 Related documents... 3

More information

Service description Corporate Access Payables Appendix Finland

Service description Corporate Access Payables Appendix Finland Service description Corporate Access Payables Appendix Finland Page 2 of 2 Page 2 of 2 Table of contents APPENDIX FINLAND... 3 2 GENERAL OVERVIEW OF THE FINNISH PAYMENT INFRASTRUCTURE... 3 2. AVAILABLE

More information

pain CustomerCreditTransferInitiationV03

pain CustomerCreditTransferInitiationV03 Corporate Access Payables Message Implementation Guidelines pain.001.001.03 CustomerCreditTransferInitiationV03 MIG version: 1.3 : Note: Please refer to Change document 1.3 under Introduction chapter for

More information

Service description. Corporate Access Payables Appendix Norway

Service description. Corporate Access Payables Appendix Norway Service description Corporate Access Payables Appendix Norway Table of contents Page 2 of 13 1 APPENDIX NORWAY... 3 2 GENERAL OVERVIEW OF THE NORWEGIAN PAYMENT INFRASTRUCTURE... 3 2.1 AVAILABLE PAYMENT

More information

Service description. Corporate Access Payables Appendix Norway

Service description. Corporate Access Payables Appendix Norway Service description Corporate Access Payables Appendix Norway Page 2 of 19 Table of contents 1 APPENDIX NORWAY 3 2 GENERAL OVERVIEW OF THE NORWEGIAN PAYMENT INFRASTRUCTURE 3 2.1 AVAILABLE PAYMENT TYPES

More information

Service description. Corporate Access Payables Appendix Finland

Service description. Corporate Access Payables Appendix Finland Service description Corporate Access Payables Appendix Finland Page 2 of 5 Table of contents APPENDIX FINLAND... 3 2 GENERAL OVERVIEW OF THE FINNISH PAYMENT INFRASTRUCTURE... 3 2. AVAILABLE PAYMENT TYPES...

More information

Service description. Corporate Access Payables Appendix Denmark

Service description. Corporate Access Payables Appendix Denmark Service description Corporate Access Payables Appendix Denmark Page 2 of 19 Table of contents 1 APPENDIX - DENMARK... 3 2 GENERAL OVERVIEW OF THE DANISH PAYMENT INFRASTRUCTURE... 3 2.1 AVAILABLE PAYMENT

More information

Multi-Currency Bulk Payments XML File Format

Multi-Currency Bulk Payments XML File Format www.aib.ie/sepa Multi-Currency 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,

More information

Multi-Currency Bulk Payments XML File Format

Multi-Currency Bulk Payments XML File Format www.aib.ie/sepa Multi-Currency 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,

More information

The Nets camt.054 service is based on the contents of the Egiro service for credit notifications and on Dirrem accounting data for the Debit part.

The Nets camt.054 service is based on the contents of the Egiro service for credit notifications and on Dirrem accounting data for the Debit part. Index Element XML Tag Occurrence Type UseInIG Definition BSK Rules Nets Usage Document Document Document Document BkToCstmrDbtCdtN1..1 BankToCustomerDebitCreditNotificationV02 The Bank-to-Customer Debit

More information

camt.052 Bank to Customer Report camt.053 Bank to Customer Statement camt.054 Bank to Customer Notification Format Description

camt.052 Bank to Customer Report camt.053 Bank to Customer Statement camt.054 Bank to Customer Notification Format Description camt.052 Bank to Customer Report camt.053 Bank to Customer Statement camt.054 Bank to Customer Notification 28.06.2016 Format Description camt.053 Format Description Introduction... 3 Character set...

More information

pain CustomerCreditTransferInitiationV03

pain CustomerCreditTransferInitiationV03 Corporate egateway Message Implementation Guideline pain.001.001.03 CustomerCreditTransferInitiationV03 MIG version: 2.1 : 02-01-2017 2 of 28 Table of Contents 1. Introduction... 3 2. Scope... 3 3. Document

More information

SEPA payment transactions

SEPA payment transactions SEPA payment transactions Format Updated Version with amendments from 19 November 2017 September 2017 2 Table of contents 1 Data formats and SEPA processes current status in Germany 5 2 Relation between

More information

pain CustomerCreditTransferInitiationV03

pain CustomerCreditTransferInitiationV03 Corporate egateway Message Implementation Guideline pain.001.001.03 CustomerCreditTransferInitiationV03 MIG version: 2.2 : 2018.02.01 2 of 24 Table of Contents 1. Introduction... 3 2. Scope... 3 3. Document

More information

pain CustomerCreditTransferInitiationV03

pain CustomerCreditTransferInitiationV03 Corporate egateway Message Implementation Guideline pain.001.001.03 CustomerCreditTransferInitiationV03 MIG version: 2.3 : 2018.11.26 2 of 28 Table of Contents 1. Introduction... 3 2. Scope... 3 3. Document

More information

The Nets camt.054 service is based on the contents of the Egiro service for credit notifications and on Dirrem accounting data for the Debit part.

The Nets camt.054 service is based on the contents of the Egiro service for credit notifications and on Dirrem accounting data for the Debit part. Index Element XML Tag Occurrence Type UseInIG Definition BSK Rules Nets Usage Document Document Document Document BkToCstmrDbtCdtN1..1 BankToCustomerDebitCreditNotificationV02 The Bank-to-Customer Debit

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) Version 6.4 July 2013 Table of content 1 Introduction 5 1.1 Character Set 6 1.2 Change history 6 2 Message item description 7 1.0

More information

OP-POHJOLA GROUP C2B SERVICES. Payment Services

OP-POHJOLA GROUP C2B SERVICES. Payment Services OP-POHJOLA GROUP C2B S Payment Services Service Description November 2010 2/63 Contents 1 General information... 3 1.1 Making of C2B payments... 4 1.2 Recurring C2B payments... 5 1.3 C2B payload checks

More information

Service description. Corporate Access Payables Appendix Sweden

Service description. Corporate Access Payables Appendix Sweden Service description Corporate Access Payables Appendix Sweden Table of contents Page 2 of 18 1 APPENDIX SWEDEN... 3 2 GENERAL OVERVIEW OF THE SWEDISH PAYMENT INFRASTRUCTURE... 3 2.1 AVAILABLE PAYMENT TYPES...

More information

ANZ TRANSACTIVE GLOBAL FILE FORMATS

ANZ TRANSACTIVE GLOBAL FILE FORMATS ANZ TRANSACTIVE GLOBAL FILE FORMATS 07 2018 Classification: Insert Classification 1 CONTENTS 1 INTRODUCTION... 4 1.1 About this guide... 4 1.2 Scope... 4 1.3 Online Help... 4 1.4 Online Resources... 4

More information

Swiss Payment Standards 2018

Swiss Payment Standards 2018 Swiss Payment Standards 2018 Swiss Business Rules for Payments and Cash Management for Customer-Bank Messages Version 2.7, with effect from November 2018 Version 2.7 18.12.2017 General note Any suggestions

More information

Swiss Payment Standards 2018

Swiss Payment Standards 2018 2018 Swiss Implementation Guidelines for Customer-Bank Messages (Reports) Bank-to-Customer Account Report (camt.052) Bank-to-Customer (camt.053) Bank-to-Customer Debit/Credit Notification (camt.054) Version

More information

SEPA Germany Comparison CGI, EPC and DK

SEPA Germany Comparison CGI, EPC and DK SEPA Germany Comparison CGI, EPC and DK Comparison of technical formats Contents 1. SEPA Germany Comparison CGI, EPC and DK 1.1. General 1.2. Significant differences Credit Transfer SEPA Germany 1.3. Significant

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 (camt.053) Bank-to-Customer Debit/Credit Notification

More information

Functional specification for Payments Corporate egateway

Functional specification for Payments Corporate egateway Functional specification for Payments Corporate egateway 2(57) Page Table of contents 1 Introduction... 5 1.1 Explanation of definitions for EDIFACT & XML ISO20022 6 1.2 Level descriptions for EDIFACT

More information

SEPA BUSINESS-TO-BUSINESS DIRECT DEBIT SCHEME CUSTOMER-TO-BANK IMPLEMENTATION GUIDELINES

SEPA BUSINESS-TO-BUSINESS DIRECT DEBIT SCHEME CUSTOMER-TO-BANK IMPLEMENTATION GUIDELINES Doc: EPC131-08 30 November 2012 (Version 5.0 Approved) EPC SEPA BUSINESS-TO-BUSINESS DIRECT DEBIT SCHEME CUSTOMER-TO-BANK IMPLEMENTATION GUIDELINES Abstract Document Reference Issue This document sets

More information

PKO Webconnect Context CZ - Export Formats.

PKO Webconnect Context CZ - Export Formats. PKO Webconnect Context CZ - Export Formats. March 2017 TABLE OF CONTENTS EXPORT FORMATS IN PKO WEBCONNECT CONTEXT CZ... 3 EXPORT TO CSV FORMAT... 3 List of Possible Export Sets to CSV Format From WebConnect

More information

SEPA CORE DIRECT DEBIT SCHEME CUSTOMER-TO-BANK IMPLEMENTATION GUIDELINES

SEPA CORE DIRECT DEBIT SCHEME CUSTOMER-TO-BANK IMPLEMENTATION GUIDELINES Doc: EPC130-08 30 November 2012 (Version 7.0 Approved) EPC SEPA CORE DIRECT DEBIT SCHEME CUSTOMER-TO-BANK IMPLEMENTATION GUIDELINES Abstract Document Reference Issue This document sets out the rules for

More information

Funds Order Processing

Funds Order Processing UK Funds Market Practice Group Funds Order Processing Status: Final version Preparation date: August 2009 Author: UK NMPG Steve Wallace, Idea Group Ltd Version 01.00.00 FINAL UK NMPG Orders 2009 Version

More information

SEPA BUSINESS-TO-BUSINESS DIRECT DEBIT SCHEME CUSTOMER-TO-BANK IMPLEMENTATION GUIDELINES

SEPA BUSINESS-TO-BUSINESS DIRECT DEBIT SCHEME CUSTOMER-TO-BANK IMPLEMENTATION GUIDELINES Doc: EPC131-08 1 November 2010 (Version 3.0 Approved) EPC SEPA BUSINESS-TO-BUSINESS DIRECT DEBIT SCHEME CUSTOMER-TO-BANK IMPLEMENTATION GUIDELINES Abstract Document Reference This document sets out the

More information

Implementation guide. Status report rejected payments in Handelsbanken CSV format

Implementation guide. Status report rejected payments in Handelsbanken CSV format Status report rejected payments in Handelsbanken CSV format Version 0.1.1 Publishing date 12 June 2008 Table of contents 1 INTRODUCTION... 3 1.1 DEFINITIONS... 3 1.2 HISTORY... 3 2 INFORMATION ABOUT THE

More information

ABN AMRO addendum on the XML Message for European Direct Debit Initiation

ABN AMRO addendum on the XML Message for European Direct Debit Initiation ABN AMRO addendum on the XML Message for European Direct Debit Initiation Table of contents 1 Introduction...4 2 Message description...5 1.0 Group Header... 5 1.1 Message Identification... 5 1.2 Creation

More information

Addendum on the XML message for SEPA Direct Debit Initiation (PAIN)

Addendum on the XML message for SEPA Direct Debit Initiation (PAIN) Addendum on the XML message for SEPA Direct Debit Initiation (PAIN) Version 6.0 - May 2012 Table of content 1 Introduction 5 1.1 Character Set 6 1.2 Change history 6 2 Message item description 7 1.0 Group

More information

SEPA CORE DIRECT DEBIT SCHEME CUSTOMER-TO-BANK IMPLEMENTATION GUIDELINES

SEPA CORE DIRECT DEBIT SCHEME CUSTOMER-TO-BANK IMPLEMENTATION GUIDELINES Doc: EPC130-08 1 November 2010 (Version 5.0 Approved) EPC SEPA CORE DIRECT DEBIT SCHEME CUSTOMER-TO-BANK IMPLEMENTATION GUIDELINES Abstract Document Reference This document sets out the rules for implementing

More information

XML Format of Account Statements Supported by KBSK, Effective as from 25 February 2016

XML Format of Account Statements Supported by KBSK, Effective as from 25 February 2016 XML Format of Account Statements Supported by KBSK, Effective as from 25 February 2016 1/20 Contents: 1 Introduction... 4 1.1 Purpose of the Document... 4 1.2 Information on the Document... 4 1.3 Rules

More information

SEPA CORE DIRECT DEBIT SCHEME CUSTOMER-TO-BANK IMPLEMENTATION GUIDELINES

SEPA CORE DIRECT DEBIT SCHEME CUSTOMER-TO-BANK IMPLEMENTATION GUIDELINES Doc: EPC130-08 30 October 2009 (Version 3.4 Approved) EPC SEPA CORE DIRECT DEBIT SCHEME CUSTOMER-TO-BANK IMPLEMENTATION GUIDELINES Abstract Document Reference Issue This document sets out the rules for

More information

SWIFT for Corporates

SWIFT for Corporates SWIFTStandards MT Implementation Guide This document describes the rules users must follow when sending or receiving SWIFTStandards MT in SCORE (Standardised Corporate Environment). Cash Management Standards

More information

Cash-Securities Split Settlement Market Practice

Cash-Securities Split Settlement Market Practice Cash-Securities Split Settlement Market Practice Disclaimer The Securities Market Practice Group is a group of experts who devote their time on a voluntary basis to define global and local market practices

More information

SEPA BUSINESS-TO-BUSINESS DIRECT DEBIT SCHEME CUSTOMER-TO-BANK IMPLEMENTATION GUIDELINES

SEPA BUSINESS-TO-BUSINESS DIRECT DEBIT SCHEME CUSTOMER-TO-BANK IMPLEMENTATION GUIDELINES Doc: EPC131-08 17 November 2011 (Version 4.0 Approved) EPC SEPA BUSINESS-TO-BUSINESS DIRECT DEBIT SCHEME CUSTOMER-TO-BANK IMPLEMENTATION GUIDELINES Abstract Document Reference Issue This document sets

More information