Record description XML File Transfer ISO 20022 XML pain.001.001.02



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

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

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

How To Create A Credit Card From A Creditcard In A Microsoft Web Server On A Microsql Web Server

Record description XML File Transfer Balance and Transaction list camt

OUTGOING PAYMENTS ISO APPLICATION GUIDELINE

DESCRIPTION OF SEPA XML FORMAT FOR ING BUSINESSONLINE IMPORT AND EXPORT TEMPLATES

ISO PAYMENT GUIDE. Messages: Pain Pain

OUTGOING PAYMENTS ISO APPLICATION GUIDELINE

SEPA CREDIT TRANSFER SCHEME INTER-BANK IMPLEMENTATION GUIDELINES

Payments Standards - Clearing and Settlement

SEPA Direct Debit Unpaid Report File Format

XML ACCOUNT STATEMENT. Service Description

ISO Message Implementation Guide for Payment Initiation

Format description XML SEPA Credit Transfer. Format Description

OP's C2B SERVICES Pain 03. Payment Transfer Products

Payments Market Practice Document. ISITC Settlements Working Group

XML message for Payment Initiation Implementation Guideline. Version 1.02

Format Description XML SEPA CT

ISO XML pain.001 implementation guide in Handelsbanken Estonia, Latvia, Lithuania

OP's C2B SERVICES Pain 02. Payment transfer products

Format description XML SEPA Credit Transfer

SEPA CORE DIRECT DEBIT SCHEME INTER-BANK IMPLEMENTATION GUIDELINES

pg. 2 pg. 6 pg.8 pg. 20

Appendix for BSK Implementerings Guides ISO 20022

Format description XML SEPA Credit Transfer

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

Formats for Internet Bank

ISO ACCOUNT STATEMENT GUIDE. v 1.3

XML Message for SEPA Direct Debit Initiation

Format Description XML SEPA DD

Swedish Common Interpretation of ISO Payment Messages. Appendix 1: Common Payment Types in Sweden

Danske Bank Message Implementation Guide Common Global Implementation (CGI) Customer Credit Transfer pain

Payment Status Report

Format Description. SWIFT MT103 Single Customer Credit Transfer

en (pf.ch/dok.pf) PF. EPO manual Electronic payment order via file transfer

Customer Statement - MT940 with Structured Information To Account Owner

Danske Bank Guideline to payments in ISO XML format (pain )

Guide. 1 Dec Introduction of the global Structured Creditor Reference in Finnish companies. 1 December 2010

Corporate Payments Service

Format description SEPA DD ISO20022 (for Euro Direct Debits)

SEPA CREDIT TRANSFER SCHEME INTER-BANK IMPLEMENTATION GUIDELINES

SEPA Direct Debit Implementation Guide. Version 1.7

Format description SEPA Direct Debit (for Euro Direct Debits) Rabo Cash Management

MT104 Direct Debit and Request for Debit Transfer Message.

SEPA CBI XML generator Documentation

Format Description SWIFT MT940 Structured

Deutsche Bank Global Transaction Banking. Internet Bankieren. Entering Payments and Collections.

F o r e i g n p a y m e n t i n P o l a n d Page 1 of 6 B u s i n e s s O n l i n e

SEPA Direct Debit Initiation Customer-to-Bank Implementation Guidelines for the Netherlands

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

Danish Implementation Guideline for Common Global Implementation (CGI) Customer Payment Status Report

More information on completing payment details

Format Description MT940. Rabo Cash Management

Functional specification for Payments Corporate egateway

E-payment. Service description

Online Banking Record Descriptions

BEST client format supported by KB (valid from 28th November 2015)

SEPA. Changes in the Payment System Implementation of the European SEPA Regulations for Kuna and Euro Payments

Changes only affecting customers using SWIFT codewords, Intermediary Institutions, or with other special requirements

Hal E-Bank Foreign payments (Format of export/import files)

RF Creditor Reference

Nordea Bank AB Lithuania branch Price List for corporate customers Valid from 1 st of September, Contents

Date: 8 January 2009 (Message Versions: pain , pain , pain , pain and pain )

Electronic foreign currency payments, LUM2

Format Description. SWIFT MT202: General Financial Institution Transfer

Implementing SEPA in Belgiu m

Accurate cheque writing When writing or accepting a cheque, ensure that all details are correct to avoid unpaid cheque Charges.

1.1. Overview Direct credits Direct debits Nab direct credits... 12

Format Description SWIFT FIN MT101. Rabobank

PAIN.002. Format description Functional

TERMS AND CONDITIONS OF PAYMENT ORDER IN FOREIGN EXCHANGE TRANSACTIONS AT PKO BP SA BANK

NOTIFICATION SERVICE GUIDELINES

KM client format supported by KB valid from 26 March 2007

GENERAL TERMS AND CONDITIONS FOR EURO-DENOMINATED PAYMENTS WITHIN SEPA

Payments via Unitel & Corporate Netbank Request for Transfer Customer tariff effective from 1 September 2016

SERVICE DESCRIPTION E-INVOICE SERVICE 17 June 2013

User's manual for OTPdirekt Internet Banking. v.1.0

Intra-day payment Frequently asked questions

Single Euro Payments Area (SEPA) with Oracle E-Business Suite for German Banks

Implementation of ISO 20022: starter kit for software partners

Price List Valid as of Accounts, Information Service Charging Terms Price Account Terms

SEPA payment transactions. Formats

Bankline internet banking import file layout user guide

SEPA - Frequently Asked Questions

Oracle FLEXCUBE Direct Banking Release Retail Transfer and Payments User Manual. Part No. E

White Paper on Extended Remittance Information (ERI) and Payment Notification

Fee schedule and cut-off times applying to International Payments. Sampo Bank Plc, Finland. A fully owned subsidiary of Danske Bank A/S

Collection Service Implementation Guide

Spanish legacy branch code 4 numbers. Spanish legacy bank code 4 numbers

Complete Solutions Personal Retirement Savings Account

SEPA Customer File Formats-Definition Proposals

IBAN calculation and validation. Service description

Payment statistics 2014, reporting template

SEPA Country-Specific Information Austria

Deutsche Bank Deutsche Bank MT940/942 format specifications

ICEPAY & SEPA Direct Debit

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

Nordea Account structure. Corporate egateway

SEPA formats - an introduction to XML. version September

Transcription:

Record description XML File Transfer 20022 XML pain.001.001.02 15.11.2012

2 Change date Version Changed 2.6.2010 1.0 2.15 Payer s business id. Length can be 8, 9, 13 or 14 marks (so called long business id) 2.58 Payment order s account can be BBAN = 89999999999999 or IBAN = FI7489999999999999. 28.6.2010 1.1 2.58 For Foreign recurring payment fill in: BBAN -field (number 811111xxxxxxxx) or in IBAN format in the IBAN - field. Bank code always DABAFIHH 14.7.2010 1.2 2.58 +++++Id beneficiary account number with or without hyphen or the account length is more than 30 marks. 1.3 +Authstn Customer can choose in Group Header what kind of Status report they need. Default value is Negative BANSTA, only information of rejected payments. 15.11.2010 1.3 Small corrections Fields - 1.3 Authorisation and 1.6 ControlSum 15.6.2011 1.4 Amednments in the following fields1.3 Authorisation, 2.65 Purpose Code, 2.86 RemittanceInformation Structured and 2.102, 2.104, 2.105. For. Ex. International Reference and AOS2 netting. 12.12.2011 1.5 With INTC or SDVA code the payment is processed always as a foreign payment, fields 2.6, 2.12, 2.30 and 2.36. Small corrections in the fields: 2.42, 2.45, 2,55 Ctry and 2.86 18.04.2012 1.6 Amendment filed 2.13 RequestedExecutionDate., Added length clarifications to fields 2.55 ja 2.57: StrtNm, BldgNb ja PstCd.

3 1. Payment Message Structure 1.1 Payment Parties Party 20022 Debtor Ultimate Debtor Initiating Party Creditor Ultimate Creditor Debtor Agent Creditor Agent 1.2 Payment Message Group Header A- part Payment Information B-part Credit Transfer Transaction Information C-part Party, debit account. Party who has purchased the service or goods, and received the invoice. Ultimate debtor is used when the payer is other that the receiver of the original invoice. Party who sends payment message. This can be payer, service center or other party who sends the payments on behalf of the payer. Party, beneficiary s account. Party, ultimate beneficiary. For. Ex. The payment has credit in the Sampo Finance Account but the ultimate beneficiary is the customer of the Sampo Finance. Debtor s Bank Beneficiary s Bank Unique in Payment message, all common details of the message. For ex. Customer User ID registered for the sending customer Return PSR = Payment Status Report (MessageIdentification), Material creation timestamp(creationdateandtime) and Grouping type (GroupingIndicator) Can be more than one in Payment Message. All debit information for. Ex The Payer (Debtor), Debit Account (DebtorAccount), payment type (PaymentInformation) and due date (Requested Execution Date). Payment information will be replied if the due date or debit account will be different. Is in Payment Information recurring part. All credit information.for ex. beneficiary (Creditor), Beneficiary s bank (CreditorAgent), beneficiary account (Creditor Account) and invoice details (RemittanceInformation). 2.3 Abbreviations (1..1) Mandatory and only once in a message. (1..n) Mandatory, can be several times (0..1) Optional and only once in a message (0..n) Optional and can be several times >> The element is under the previous level, {Or..Or} Alternative elements (Choice)

4 M C N Mandatory Optional Not in use Tag-nimi Message 1.0 GrpHdr Group Header [1..1] M Once in a message. General indentification. 1.1 +MsgId MessageIdentification TEXT [1..1] M Customer User ID registered for the sending customer Return PSR = Payment Status Report 1.2 +CreDtTm CreationDateTime DateTime [1..1] M Material creation timestamp, given by the debtor Return PSR = Payment Status Report 1.3 +Authstn Authorisation TEXT [0..2] C Can be used to mark the payment file for test: If this tag contains the string TEST then the file will be processed but the payments will not be executed. 1.4 +BtchBookg BatchBooking True/false [0..1] C Sender selects debit forma. The feedback message will be created as default value. Other kind of feedback message is produced according the given values in this field. Feedback process and codes are in Service Transfer of Material XML, chapter 2.2 Note: If the file is TEST marked in the same batch ja if a separate feedback id needed, the request should be in the field <Authstn>. The order of the fields is not significant. True=booking per payment information False=booking per transaction Default value TRUE 1.5 +NbOfTxs NumberOfTransactions TEXT [1..1] M Number of individual transactions contained in the message, given by the debtor. Mandatory field in Material Transmission Service (Linkki) but not in File Transmission

5 Tag-nimi Message via Business Online.. 1.6 +CtrlSum ControlSum Quantity [0..1] N Not in use. The field is not checked. 1.7 +Grpg Grouping Code [1..1] M Mandatory field, If control sum is added, the it will be in the feedback file Recommendation = MIXD Note! Payments can be debited as bulk debit if the payment type is same. 1.8+ +InitgPty InitiatingParty [1..1] M Party initiating the payment. In the payment context, this can either be the debtor or the party that initiates the payment on behalf of the debtor. Mandatory ++Nm Name TEXT [0..1] C Payer s name, Recommendation is to fill in. If filled, return PSR = Payment Status Report 2.0 PmtInf PaymentInformation [1..n] M Payment psc Return PSR = Payment Status Report 2.1 +PmtlnfId PaymentInformationIden TEXT [0..1] C Free text. Senders information, max 35 marks. tification Same as present LM03 identification field, added in KTON statement: T11/06. 2.2 +PmtMtd PaymentMethod Code [1..1] M Cheque = CHK 2.3 +PmtTpInf PaymentInformatio n 2.5 ++SvcLvl ServiceLevel [0..1] [0..1] C [0..1] C Payment type Other payments = TRF transfers and money orders

6 Tag-nimi Message 2.6 +++Cd Code [0..1] C SEPA transfer = SEPA Capital transfer = SDVA SDVA code process the payment always as foreign payment. 2.7 +++Prtry Proprietary [0..1] C Use either URGP in this field or HIGH in 2.4 to signify an express payment. If both fields are used then 2.7 takes precedence. 2.9 ++LclInstrm LocalInstrument] [0..1 C 2.12 ++CtgyPurp CategoryPurpose Code [0..1] C Group Payment = INTC INTC code process the payment always as foreign payment. 2.13 +ReqdExctnDt RequestedExecutionDat e Recurring Payment = SALA Tax Payment = TAXS DATE [1..1] M Debit day which the customer gives: If the field CdtTrfTxInf/PmtId/CtgyPurp (index 2.36) is filled then this field is ignored. Max 365 calendar day prior the due date In file transfers via Web Services and Business Online web bank the debit day is allowed to be 60 calendar days and file transfer via Linkki material transmission service 2 banking days old. If payment type SALA, then the debit day must be always banking day. 2.15+ +Dbtr Debtor [1..1] M A Payer, debit account ++Id Identification [0..1] M Payer s identification +++OrgId OrganisationIdentificatio n [1..1] M Business identification

7 Tag-nimi Message ++++BkPtyId BankPartyIdentification TEXT [0..1] M Used for Customer ID on Finnish Payments: Contains the Linkki Customer ID which can be either 8, 9,13 or 14 chars. 2.16+ +DbtrAcct DebtorAccount [1..1] M Debtor s account number. ++Id Identification [1..1] M The first 8 chars is the Linkki Customer ID and the next 5 chars is extension id. The extension id is optional. If missing we will use "00000" instead +++IBAN IBAN Identifier [1..1] C IBAN code used to identify the country of Debtors Bank. Mandatory when the account is in +++BBAN BBAN Identifier [1..1] C Used only in MT101 messages ++Ccy Currency Code [0..1 C Account s currency code. Used if the payment includes exhange. 2.17+ +DbtrAgt DebtorAgent [1..1] M Payer s bank ++FinInstnId FinancialInstitutionIdenti fication [1..1] M Recommendation to fill in currency BIC is mandatory +++BIC BIC Identifier [1..1] M Samoo Bank BIC = DABAFIHH 2.19+ +UltmtDbtr UltimateDebtor [0..1] C Ultimate debtor s. The receiver of the invoice is diffrent than payer. The field is used with SEPA -payments

8 Tag-nimi Message ++Nm Name TEXT [0..1] C Ultimate debtor s name Will be in payer s and beneficiary s KTO account statement s additional information T11/11. Max 70 mark 2.20 +ChrgBr ChargeBearer Code [0..1] C If the payment is CHK, then all other charges than 2.23 +CdtTrfTxInf CreditTransferTransacti oninformation 2.24 ++PmtId PaymentIdentification [1..1] M Mandatory CRED is changed to SHAR CRED = beneficiary pays all fees DEBT = payer pays all fees SHAR = pays own fees SLEV = pays own fees (mandatory in SEPA payments) [1..n] M In Payment Information part,. Includes beneficiary details. 2.25 +++InstrId InstructionIdentification] TEXT [0..1 C Payment identification information for the debtor, used between the payer and payer s bank. (Like in LM03 fields 18 and 19), response in the KTOn Account statement T11/06 (5.1 and 5.2) fields. Max 35 chars to Debtor/Creditor Identifier. Max 35 chars to Advice Text. The first 20 chars to Senders Reference. 2.26 +++EndToEndId EndToEndIdentification TEXT [1..1] M Payment identification information given by debtor. Used only on SEPA-payments. 2.27 ++PmtTpInf PaymentInformatio n [0..1] C 2.29 +++SvcLvl ServiceLevel [0..1] [0..1] C End-to-End Id is not in showed in bulk-payments, only in single payments and specifications.

9 Tag-nimi Message 2.30 ++++Cd Code [0..1] C SEPA payment = SEPA Capital Transfer = SDVA SDVA code process the payment always as foreign payment. 2.31 ++++Prtry Proprietary [0..1] C Urgent Paym,ent = URGP. Domestic Urgent Payment in the field 2.7. 2.33 +++LclInstrm LocalInstrument] [0..1 C 2.36 +++CtgyPurp CategoryPurpose Code [0..1] C Internal payment = INTC INTC code process the payment always as foreign payment. Recurring payment = SALA TAX Payment = TAXS Recommendation for SALA- and TAXS-codes, use field 2.12. 2.37 ++Amt Amount [ Amount 1..1] M Currency and amount of the payment 2.38 +++InstdAmt InstructedAmount Use either 2.38 or 2.39 2.39 +++EqvtAmt EquivalentAmount Use either 2.38 or 2.39 [1..1] C Currency and amount of the payment Use the field 2.38 or 2.39. [1..1] C Currency and amount of the payment, when the debited amount is in same currency as the debit account. Use the field 2.38 or 2.39.

10 Tag-nimi Message 2.40 ++++Amt Amount Amount [1..1] C the debited amount is in same currency as the debit account. 2.41 ++++CcyOfTrf CurrencyOfTransfer Code [1..1] C Payment s Currency 2.42 ++XchgRateInf ExchangeRateInformatio n [0..1] C Exhange Rate Agreement is allowed also if code is Grouped or Mixed 2.45 +++CtrctId ContractIdentification Text [0..1] C Exhange rate agreement number 14 mark 2.46 ++ChrgBr ChargeBearer Text [0..1] C If in use, then the field ChrgBr (index 2.20) is ignored If the payment is CHK, then all other charges than CRED is changed to SHAR CRED = beneficiary pays all fees DEBT = payer pays all fees SHAR = pays own fees SLEV = pays own fees (mandatory in SEPA payments) 2.47+ ++ChqInstr ChequeInstruction Text [0..1] C Default for foreign cheques is NOT CROSSED and domestic are ALWAYS CROSSED. +++DlvryMtd DeliveryMethod [0..1] C ++++Cd Code Code [1..1] C Codes: Foreign Finnish cheques are always crossed too. MLCD = the bank mails the cheque to beneficiary

11 Tag-nimi Message MLDB = the bank mails the cheque to payer 2.48+ ++UltmtDbtr UltimateDebtor [0..1] C Ultimate debtor when receiver of the invoice differs from the payer. The field is used with SEPA payments. If Present overrules 2.19 +++Nm Name TEXT [0..1] C Name of the invoice receiver if it differs from the payer Will be in KTO Statements Additional information T11/11 If Present overrules UltmDbtr/Nm kentässä (index 2.19. Truncated to 70 chars. 2.55+ ++CdtrAgt CreditorAgent [0..1] C Creditor bank s information +++FinInstnId ++++BIC FinancialInstitutionIdenti fication BIC Use either BIC or CmbndId [1..1] C Creditor bank s identification. Identifier [1..1] C Creditor bank s BIC-code. Mandatory on SEPA-payments If BIC code is filled in, then no other address field is needed. ++++CmbndId CombinedIdentification [1..1] C Creditors s bank information if the BIC code is not known. +++++ ClrSysMmbId ClearingSystemMember Identification [0..1] C ++++++Id Identification Code [1..1] C Creaditor s bank clearing-code.for ex. FW123456789. You can give the Clearingcode as -standard for ex. USABA123456789. +++++Nm Name TEXT [0..1] C Creditor bank s name Max. 35 marks +++++PstlAdr PostalAddress [0..1] C Creditor bank s address ++++++AdrLine AddressLine TEXT [0..5] C Creditor bank s address max. 2

12 Tag-nimi Message ++++++StrtNm StreetName TEXT [0..1] C Creditor bank s street address Max. 35 marks ++++++BldgNb BuildingNumber TEXT [0..1] C Creditor bank s street address number. BldgNb + StrtNm max 35 marks ++++++PstCd PostCode TEXT [0..1] C Creditor bank s ZIP code. Max 5 marks ++++++TwnNm TownName TEXT [0..1] C Creditor bank s town ++++++Ctry Country Code [1..1] C Creditor bank s country code. Must be standard format. 2.57+ ++Cdtr Creditor Maksun saaja Creditor bank s country code is mandatory, if the BIC code does not exist but the payment details are included. [0..1] M Creditor, beneficiary to whom the payment is transfered +++Nm Name TEXT [0..1] M Creditor name Max. 35 mark. In SEPA payments the field can be 70 marks. +++PstlAdr PostalAddress [0..1] C Creditor address information. ++++AdrLine AddressLine TEXT [0..5] C Creditor address, max. 2 rows allowed for SEPA-payments. Foreign cheques address is mandatory in this field. Max 3 total 105 marks includes country name (for. Ex. FRANCE. If cheque is mailed to beneficiary (code MLCD in the filed 2.47) and one AdrLine atleast 36 marks is mandatory. If 2-3 AdrLine no demands. Money orders the street address is given here or StreetName-field. ++++StrtNm StreetName TEXT [0..1] C Creditor street address. Max 35 marks ++++BldgNb BuildingNumber TEXT [0..1] C Creditor street address number. BldgNb + StrtNm max 35 marks ++++PstCd PostCode TEXT [0..1] C Creditor ZIP code. Mandatory for Money orders. Max 5 marks ++++TwnNm TownName TEXT [0..1] C Creditor town address. Mandatory for Money orders ++++Ctry Country Code [1..1] C Creditor Country code. Must be standard format Mandatory if the address information is filled in.

13 Tag-nimi Message +++Id Identification [0..1] C Creditor identification ++++OrgId Use either OrgId or PrvtId OrganisationIdentificatio n [1..1] C ++++PrvtId PrivateIdentification [1..4] C For Recurring Payments (Category Purpose = SALA) +++++SclSctyN b If more than one, only the first one is counted. SocialSecurityNumber TEXT [1..1] C In Recurring payments, beneficiary personal social security number. In Finland the form is nnnnnn- nnn. 2.58+ ++CdtrAcct CreditorAccount [0..1] C Beneficiary account number +++Id Identification [1..1] C ++++IBAN ++++BBAN IBAN Either IBAN or BBAN BBAN Either IBAN or BBAN ++++PrtyAcct ProprietaryAccount C Identifier [1..1] C Beneficiary IBAN account number Mandatory in SEPA payments.. Identifier [1..1] C Beneficiary BBAN account number. Note: BBAN field is allowed only letter or numeric. Punctuation marks are not allowed (schema-validiation). See also the field below CdtrAcct/Id/PrtryAcct/Id. For ex. Money order, BBAN = 89999999999999 tai IBAN = FI7489999999999999 -format Foreign Recurring Payments vie register you give in the BBAN field (811111xxxxxxxx) or IBAN format in IBAN field. Beneficiary bank is always DABAFIHH and <PmtMtd> TRF. And in <CtgyPurp> tag value SALA and <Purp><Cd> tag the payment type for ex. PENS. Payments are always in EUR,.

14 Tag-nimi Message [1..1] Either IBAN, BBAN, UPIC or PtryAcc +++++Id Identification [1..1] TEXT [0..1] C Is used if the beneficiary account number includes for.ex. hash or the length is over 30 marks, max. 34 marks. 2.59 ++UltmtCdtr UltimateCreditor [0..1] [0..1] C Ultimate creaditor. For ex. The payment is transfered to Finance company from where it is transfered to a customer. Only in SEPA payments, +++Nm Name TEXT [0..1] C Ultimate Creditor name, max. 70 marks +++Id Identification [0..1] C Identification number ++++OrgId OrganisationIdentificatio n [1..1] C Identification number for corporate ++++PrvtId PrivateIdentification [1..1] C Private identification number +++++SclSctyN b 2.63 ++InstrForDbtrA gt SocialSecurityNumber TEXT [1..1] C Personal social security number in SALA category purpose payments. In Finland the form is nnnnnn- nnn. InstructionForDebtorAg ent [0..1] TEXT C Instruction for payer s bank 2.64 ++Purp Purpose [0..1] C Payment type in recurring payments. 2.65 +++Cd Code Code [1..1] C Payment type In Domestic payments can be for. Ex. KATESIIRTO in the first line, Not possible in the bulk payment.. For foreign payments max, 105 marks. The field prevents to use automatic transfer and does add extra fee for the payer. SALA = Wages and salaries STDY = Educational grants

15 Tag-nimi Message BENE = Benefits PENS = Pension SSBE = Reimbursement AGRT= Agricultural Income BECH = Child Benefits TAXS = Tax return If the field is not fllled byt he customer, then add payment type Payment for the beneficiary. 2.84 ++RmtInf RemittanceInformation [0..1] C Additional information of the payment. Can be structured or unstructured or both. (AOS2), normally only one type at time. One exception, AOS2 structure, where both message types are allowed 2.85 +++Ustrd Unstructured TEXT [0..1] C Free text field Max. One total 140 marks, exept domestic urgent payments this is max. 70 mark. Present recurring payments payment type code additional text can be given here. Invoices and credits, netting please look AOS2 and s message modell. In Domestic transfers can be text KATESIIRTO at the begin of the first line,. Cannot be used in the bulk-payment, 2.86 +++Strd Structured [0..9] C Structured message, for. Ex domestic reference number or international reference. Used only in SEPA payments and domestic urgent payments. Only one line max. 140 marks message, exept if it is AOS2 Max. 999 lines á 280 marks, if the beneficiary account is account or Helsinki Account max, 9 lines á 280 marks, if the beneficiary accounts is another bank s account including marks between <Strd> ja </Strd> tags.

16 Tag-nimi Message 2.87 ++++RfrdDocInf ReferredDocumentInfor mation 2.88 +++++RfrdDocT p Optional structured messages reference and tax-message.. Invoices and credits, netting please look AOS2 and s message modell. [0..1] C Only in use for AOS2 netting ReferredDocument [0..1] C Only in use for AOS2 netting 2.89 ++++++Cd Code Code [1..1] C CINV or CREN. Invoices and credits, netting please look AOS2 2.92 +++++RfRdDoc Nb 2.93 ++++ RfrdDocRltdDt ReferredDocumentNum ber TEXT [0..1] C Only in use for AOS2 netting, max. 15 marks ReferredDocumentRelat DateTime [0..1] C Only in use for AOS2 netting eddate 2.94 ++++RfrdDocAmReferredDocumentAmo t unt [0..n] C Only in use for AOS2 netting 2.95 +++++DuePyblA DuePayableAmount mt Amount [1..1] C Payable amount. 2.96 +++++DscntApl damt Use either 2.95, 2.96, 2.97, 2.98 or 2.99 DiscountAppliedAmount Amount [1..1] C Cash Discount Use either 2.95, 2.96, 2.97, 2.98 or 2.99 2.97 +++++RmtdAmt RemittedAmount Amount [1..1] C Payment total. Only in use for AOS2 netting

17 Tag-nimi Message Use either 2.95, 2.96, 2.97, 2.98 or 2.99 2.98 +++++CdtNoteA CreditNoteAmount mt Use either 2.95, 2.96, 2.97, 2.98 or 2.99 2.99 +++++TaxAmt TaxAmount Amount [1..1] C Credit payment amount. Only in use for AOS2 netting Amount [1..1] C Tax payment Use either 2.95, 2.96, 2.97, 2.98 or 2.99 2.100 ++++CdtrRefInf CreditorReferenceInfor mation [0..1] C Beneficiary reference. Used in reference payments 2.101 +++++CdtrRefTp CreditorReference [0..1] C Beneficiary s reference type Used in reference payments 2.102 ++++++Cd Code Code [1..1] C SCOR = Finnish or International reference. Mandatory if 2.105 is a Finnish reference number. Reference is possible id CategoryPurpose code is SALA. 2.104 ++++++Issr Issuer TEXT [0..1] C If CdtrRef field is an international reference (RF reference), then this field has value. The field is not in use for Finnish domestic reference 2.105 +++++CdtrRef CreditorReference TEXT [0..1] C Beneficiary s Finnish reference number, Finnish reference is filled with nulls and max. 20 marks. International RF reference, max 25 marks 2.108 ++++AddtlRmtIn AdditionalRemittanceInf TEXT C Free message. For. Ex. Tax payment or other free text. Max. 70 marks.

18 Tag-nimi Message f ormation [0..1]