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

Transcription

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

2 Document version history Version Date Amendments Removed unused fields from Payment status report Added LITAS-ESIS field mapping for payments Merged two versions Removed irrelevant BOL comments Removed Sender column from statement Fixed notification sheet structure to match statement Added mokesis and taresis columns to payment sheet fixed LITAS-ESIS column for statement and notification - it now contains only field number Added field numbers to payment status table Updated LITAS-ESIS map (statement, notification) Updated LITAS-ESIS map (statement, notification) Small fixes to match LT LITAS-ESIS map Updated pain field [2.9 <SvcLvl> <Cd>] usage after EURO introduction in Lithuania (Jan 1, 2015) Fixed pain field [2.30 <PmtId> <EndToEndId>] description pain.001 format description was upgraded according specific SEPA rules pain.001 and camt.053 messages description was upgraded with specific SEB usage. Added new fields to pain.001 and camt.053 messages. Updated field CreditTransfertransactionInformation usage. Merged SEB Gateway and Payment file upload service descriptions Added descriptions of other messages and explained specific rules of SEB. Updated description of 4.2 Consolidated (salary) payments Updated pain field [2.3 <BtchBookg>] description. Updated description of 4.2 Consolidated (salary) payments Removed mokesis, taresis and acc columns in payment, statement and notification sheets. Updated pain message: 1. <CtrlSum> element becomes mandatory in <GrpHdr> and <PmtInf> information level <NbOfTxs> element becomes mandatory in <PmtInf> information level.

3 Turinys 1. Document purpose 4 2. General information 5 3. Letters and symbols used in the document 6 4. Credit transfer initiation (pain Customer Credit Transfer Initiation) Urgent payment orders Wage transfer Payments to the tax administrator's accounts Payment status report (pain Payment Status Report) Balance (camt Balance) Statement of account (camt Statement) Notification (camt Notification) Balance request (camt Balance request) SEB LT transaction types Pages

4 1. Purpose The document is drafted seeking to explain the rules of filling out ISO XML and use thereof by SEB bankas. Document is prepared in accordance with the rules of the ISO XML standard notification approved by the Bank of Lithuania and the guidelines for the LITAS-EISIS data format conversion to ISO standard notification ( and supplemented with the SEB format specific rules of use. If the payment initiator in its payment orders submits the fields unspecified in the present document or the fields unused in the notification types indicated in this document, the values thereof may be ignored and the payment order may be deemed incorrect. Usage rules of the SEB data exchange format based on ISO XML standard messages, v / 59

5 2. General information Elements used in the SEB bankas' notification formats: Index Notification fields Mandatoriness Type.mokesis.taresis.acc Description SEPA International Specified the index to be used in with the relevant structure element in the ISO XML standard. The field name and the notification structure level in which this field is used. Mandatoriness of the field, the allowed number of repetitions in the notifications and the rule of alternative use. The first digit indicates that the field is mandatory: 0 - field is not mandatory, 1- field is mandatory. The second digit indicates the allowed number of field repetitions in the notification: 1 - only one field of such type is allowed in the notification, 2 - two fields are allowed, n - an unlimited number of repetitions is allowed. Or" specifies that only one of alternative options is allowed. e.g. [0..1] - not mandatory field, to be used in notification only once; [1..1] - mandatory field [0..n] - not mandatory field, to be used an unlimited number of times. Note SEPA" and International" mean that different limitations are applied to the same field, depending whether the notification is related to SEPA, or the international payment. If any note is not included - the same rule applied in all cases. Specifies the allowed data values and formats. The field specifies which ISO20022 XML field matches the local payment order field of the LITAS-ESIS format. The field specified which ISO20022 XML field matches the international payment order field of the LITAS-ESIS format.. The field specified which ISO20022 XML field meets the LITAS-ESIS format extract field. Brief description of use of the relevant ISO20022 XML format field, allowed values and specific rules of filling out rules. Explains the requirements of field filing out and allowed values in SEPA payment orders. Explains the requirements of field filing out and allowed values in the international payment orders. Amendments - made amendments are specified, if compared with the previous format version. - notification format fields unused by SEB are specified. Type of unused ISO notificationss Internet Bank SEB Gateway Payments (pain Custom credit Transfer Initiation) + + Account Statement (camt Statement2) + + Payment status report (pain Paymet Status Report) + Notification (camt Notification) + Balance request (camt Balance request) + Balance report (camt Balance) + Usage rules of the SEB data exchange format based on ISO XML standard messages, v / 59

6 3. Letters and symbols Letters and symbols used in SEPA payment orders to other countries and in international payment orders: a b c d e f g h i j k l m n o p q r s t u v w x y z A B C D E F G H I J K L M N O P Q R S T U V W X Y Z / -? : ( )., ' + Space Letters and symbols used in SEPA payment orders in Lithuania to other banks: a b c d e f g h i j k l m n o p q r s t u v w x y z ą ę ė į š ų ū ž A B C D E F G H I J K L M N O P Q R S T U V W X Y Z Ą Ę Ė Į Š Ų Ū Ž / -? : ( )., ' + Space Letters and symbols used in payment orders to SEB bankas' accounts: a b c d e f g h i j k l m n o p q r s t u v w x y z ą č ę ė į š ų ū ž A B C D E F G H I J K L M N O P Q R S T U V W X Y Z Ą Č Ę Ė Į Š Ų Ū Ž / -? : ( )., ' +! " # $ % * [ ] _ ` = Space Letters and symbols allowed in all SEB payment orders, which depend on the payment order type may be replaced following the below specified rules: a b c d e f g h i j k l m n o p q r s t u v w x y z ą č ę ė į š ų ū ž A B C D E F G H I J K L M N O P Q R S T U V W X Y Z Ą Č Ę Ė Į Š Ų Ū Ž õ ä ü ā ē ģ ī ķ ļ ņ Õ Ä Ö Ü Ā Ē Ģ Ī Ķ Ļ Ņ / -? : ( )., ' +! " # $ % * [ ] _ ` = Space Usage rules of the SEB data exchange format based on ISO XML standard messages, v / 59

7 Symbol convertion, when the symbols not allowed in the relevant payment order are specified: Symbol Replaced by Symbol Replaced by Ą A ` ' ą a / Č C =. č c Õ O Ę E õ o ę e Ä A Ė E ä a ė e Ö O Į I ö o į i Ü U Š S ü u š s Ā A Ų U ā a ų u Ē E Ū U ē e ū u Ģ G Ž Z ģ g ž z Ī I!. ī i " skip Ķ K $. ķ k %. Ļ L *. ļ l #. Ņ N ;. ņ skip [ ( skip ] ) _ - Usage rules of the SEB data exchange format based on ISO XML standard messages, v / 59

8 4. Credit Transfer Initiation (pain Customer Credit Transfer Initiation) Message type to be used for payment order formation. Mesaage sending by the customer to the bank. This type messages are used in the SEB Gateway service and in the SEB Internet Bank payment file upload function. Format description Index Message item <XML Tag> Mandatoriness Message root <CstmrCdtTrfInitn> [1..1] GroupHeader <GrpHdr> [1..1] Component (GroupHeader32) MessageIdentification <MsgId> [1..1] Max35Text CreationDateTime <CreDtTm> [1..1] ISODateTime NumberOfTransactions <NbOfTxs> [1..1] Max15NumericText ControlSum <CtrlSum> [1..1] DecimalNumber InitiatingParty <InitgPty> [1..1] Component - (PartyIdentification32) Type SEPA Description INTERNATIONAL Entirety of characteristics, unique for each file, specified in the message. Automatically generated, unique identification of the file. If the file is sent for the second time (or more times), the value must be different. Link "Point to point attributed by the party initiating the message and sent to another party in the payment chain for MessageIdentification. The instructing party has to make sure that MessageIdentification is unique per instructed party for a pre-agreed period. Date and time at which the message was created. Number of "CreditTransferTransactionInformation fields. Total transaction value (does not depend on currency). Total value of "CreditTransferTransactionInformation\Amount\InstructedAmount. Only numbers with two decimal points are allowed. Identification of a private person, financial institution or a legal entity initiating payment. +++Name <Nm> [0..1] Max70Text Identification of a private person, financial institution or a legal entity initiating money transfer from the payer's account. Length of name is limited to 70 symbols Length of name is limited to 140 symbols +++Identification <Id> [0..1] Choice Component (Party6Choice) Unique identifier of the party initiating payment ++++OrganisationIdentification <OrgId> {Or [1..1] Component (OrganisationIdentification4) A section describing the identifier of the legal entity initiating payment. It will not be sent to the beneficiary. Only "BICOrBEI, or "Other field may be used BICOrBEI <BICOrBEI> {{Or [0..1] AnyBICIdentifier BIC (Business Identifier Codes) will be used for identification of financial institutions according to ISO 9362 standard. BEI (Business Entity Identifier) may be used for identification of nonfinancial institutions Other <Othr> [0..1] Or}} Component Unique Payment number Identification <Id> [1..1] Max35Text Identifier value SchemeName <SchmeNm> [0..1] Component Mandatory field, if "Identification field includes value Code <Cd> {{Or [1..1] Code Identifier name from the list of ISO external codes: TXID VAT payer's code, COID company registration number, CUST client's code in the beneficiary's IT system Proprietary <Prtry> [1..1] Or}} Max35Text Usage rules of the SEB data exchange format based on ISO XML standard messages, v / 59

9 Index Message item <XML Tag> Mandatoriness Type Description SEPA INTERNATIONAL ++++PrivateIdentification <PrvtId> [1..1] Or} Component (PersonIdentification5) A section describing the identifier of the private person initiating payment. It will be sent unchanged to the beneficiary. DateAndPlaceOfBirth are allowed or one of "Other" DateAndPlaceOfBirth <DtAndPlcOfBirth> {{Or [0..1] Component (DateAndPlaceOfBirth) Date and place of birth BirthDate <BirthDt> [1..1] ISODate Birth date CityOfBirth <CityOfBirth> [1..1] Max35Text City of birth CountryOfBirth <CtryOfBirth> [1..1] CountryCode Code of country of birth according to ISO 3166, two letter code +++++Other <Othr> [0..1] Or}} Component Identification <Id> [1..1] Max35Text SchemeName <SchmeNm> [0..1] Component Mandatory field, if "Identification field indicates value Code <Cd> Code Identifier name from the list of ISO {{Or [1..1] external codes: NIDN personal code, CUST client's code in the beneficiary's IT system, DRLC driver's licence number, SOSE social insurance number, CCPT passport number, EMPL employee's certification number, TXID code assigned by the State Tax Inspectorate, ARNU social insurance number of a person not issued a permanent residence permit Proprietary <Prtry> [1..1] Or}} Max35Text ForwardingAgent <FwdgAgt> [0..1] Component Financial institution receiving the payment order (BranchAndFinancialInstitutionIdentifi from a private individual, financial institution or a cation4) legal entity initiating payment, sends it to the next participant of the payment chain. ++++FinancialInstitutionIdentification <FinInstnId> [1..1] Component (BranchAndFinancialInstitutionIdentifi cation4) +++++BIC <BIC> [0..1] BICIdentifier 2.0 +PaymentInformation <PmtInf> [1..n] Component (PaymentInstructionInformation3) PaymentInformationIdentification <PmtInfId> [1..1] Max35Text PaymentMethod <PmtMtd> [1..1] Code Informacija apie mokėjimo nurodymą. Reference created by sending party, which identifies payment order data. Generated automatically by retaining uniform The value of this element should be a 128 bit characteristics by sending all packages. If UUID number, represented as Base16 payment order is sent for the second time (or encoded string. more times), the value must be different. Unique in each payment order. Code identifying the payment order. Only TRF is allowed Usage rules of the SEB data exchange format based on ISO XML standard messages, v / 59

10 Index Message item <XML Tag> Mandatoriness Type Description SEPA INTERNATIONAL BatchBooking <BtchBookg> [0..1] BatchBookingIndicator Indicated whether the party initiating payment requests a separate debit or credit entry for each separate transaction, or for the total bach amount of credit or debit transaction. Allowed value is true" or false". A value "true" Identifies that a credit transfer is proceed as a single (group) entry and a value "false" identifies that a single entry for each of the transactions in the message is requested NumberOfTransactions <NbOfTxs> [0..1] International [1..1] SEPA ControlSum <CtrlSum> [0..1] International [1..1] SEPA Max15NumericText DecimalNumber PaymentTypeInformation <PmtTpInf> [0..1] Component (PaymentTypeInformation19) Number of individual transactions contained in the "PaymentInformation" group. Control figure of the payment amount in the "PaymentInformation" structure. Total amoun of values CreditTransferTransactionInformation/Amount/InstructedAmount". When indicating the transaction type, PaymentTypeInformation" element we recommend using "PaymentInformation", instead of the "CreditTransferTransactionInformation" structure. If both fields are filled out, the "CreditTransferTransactionInformation" field value will be used ServiceLevel <SvcLvl> [0..1] Choice Component Payment priority (ServiceLevel8Choice) Code <Cd> {Or [1..1] ExternalServiceLevel1Code Value is "SEPA" only. Very urgent transfers in euro from will be executed as very urgent international transfers by indicating SDVA value in "ServiceLevel/Code" field. Allowed values: "NURG" = standard; "URGP" = urgent; "SDVA" = very urgent. Very urgent transfers in euro from will be executed as very urgent international transfers by indicating SDVA value in "ServiceLevel/Code" field. If value of PaymentInformation/PaymentTypeInformatio n/servicelevel/code" field does not match with the value PaymentInformation/CreditTransferTransact ioninformation/paymenttypeinformation/ser vicelevel/code" field, the latter shall be followed CategoryPurpose <CtgyPurp> [0..1] Choice Component (CategoryPurpose1Choice) Code <Cd> [1..1] Code RequestedExecutionDate <ReqdExctnDt> [1..1] ISODate Information is mostly used by the payer aiming to indicate special processing of the payment data based on a separate agreement between the payer and the payment service provider of the payer. The payment service provider of the payer is not required to send this information to the beneficiary's payment service provider. Possible code values from the list of ISO external codes, e.g. SALA (Salary payments), TAXS (Tax payment), TREA (Treasury payment). Customers using the wage transfer service are recomended to use the wage transfer functionality. All payment orders indicating SALA value and submitted in the Payment File Upload Window will be executed as the standard payment order. This is the date on which the debtor's account is to be debited Debtor <Dbtr> [1..1] Component (PartyIdentification32) Payer Maximum of 140 symbols is applied for the total symbols entered in Debtor/Name", Debtor/PostalAddress" structures. Usage rules of the SEB data exchange format based on ISO XML standard messages, v / 59

11 Index Message fields <XML Tag> Mandatoriness Type Description +++Name <Nm> [0..1] International [1..1] SEPA Max140Text (International) Max70Text (SEPA) SEPA INTERNATIONAL Name of the payment party usually used to identify such party. If any name and surname/title that does not match the name and surname/title kept by the bank is specified, the name and surname/title kept by the bank will be used in the payment order. We would like to draw your attention that maximum field length used in the LITAS-ESIS local payment order format is 200, and in SEPA 70 symbols. We would like to draw your attention that maximum field length used in the LITAS- ESIS local payment order format is 200, and in SEPA 140 symbols. +++PostalAddress <PstlAdr> [0..1] Component (PostalAddress6) ++++Country <Ctry> [0..1] Country Code Payer's address If address is specified, the country code Mandatory field. necessary. Only Latin characters are allowed. Payer's country according to ISO 3166, max length - two letter code ++++AddressLine <AdrLine> [0..7] International [0..2] SEPA +++Identification <Id> [0..1] Choice Component (Party6Choice) Max70Text Address may consist of two entries with 70 characters each. The identifier to be used must be specified in "SchemeName field. If the payer is a legal entity, OrganisationIdentification field will be used, if private person "PrivateIdentification. In such case if necessary to specify other person's identifier, the name of the initial payer must be filled out in "UltimateDebtor" field. Only Latin symbols allowed. Mandatory in case of payment to UAH - street, city, country have to present. A section describing the identifier of the payer. It will be sent unchanged to the beneficiary. ++++OrganisationIdentification <OrgId> {Or [1..1] Component (OrganisationIdentification4) A section describing the identifier of the legal entity. It will be sent unchanged to the beneficiary. Only "BICOrBEI or ""Other field may be used BICOrBEI <BICOrBEI> {{Or [0..1] AnyBICIdentifier Aiming to identify any financial institution, BIC (Business Identifier Codes) according to ISO 9362 standard may be used. BEI (Business Entity Identifier) may be used of identification of non-financial institutions Other <Othr> [0..n] International Or}} [0..1] SEPA Or}} Component Field recurrence is not allowed Identification <Id> [1..1] Max35Text Only one code I allowed. If the company code differing from the company code kept by the bank is specified, the company code kept by the bank will be used in the payment order SchemeName <SchmeNm> [0..1] Component Mandatory field if "Identification field specifies the value. Usage rules of the SEB data exchange format based on ISO XML standard messages, v / 59

12 Index Message item <XML Tag> Mandatoriness Type Description SEPA INTERNATIONAL Code <Cd> {{Or [0..1] International {{Or [1..1] SEPA Code Identifier name from the list of ISO external codes: TXID VAT payer's code, COID company registration number, CUST client's code in the beneficiary's IT system. Currently, using the payment file upload service, only COID and CUST values are allowed Proprietary <Prtry> [1..1] Or}} Max35Text ++++PrivateIdentification <PrvtId> [1..1] Or} Component (PersonIdentification5) A section describing the identifier of the private person, who is a payer. It will be sent unchanged to the beneficiary. Only "DateAndPlaceOfBirth or "Other field may be used DateAndPlaceOfBirth <DtAndPlcOfBirth> {{Or [0..1] Component (DateAndPlaceOfBirth) Date and place of birth BirthDate <BirthDt> [1..1] ISODate Birth date ProvinceOfBirth <PrvcOfBirth> [0..1] Max35Text Province of birth CityOfBirth <CityOfBirth> [1..1] Max35Text City of birth CountryOfBirth <CtryOfBirth> [1..1] CountryCode Country of birth code according to ISO 3166, - two letter code Other <Othr> [0..n] International Or}} Component Field recurrence is not allowed. [0..1] SEPA Or}} Identification <Id> [1..1] Max35Text Only one code I allowed. If the company code differing from the company code kept by the bank is specified, the company code kept by the bank will be used in the payment order SchemeName <SchmeNm> [0..1] Component Mandatory field if "Identification field specifies the value Code <Cd> {{Or [0..1] International Code Identifier name from the list of ISO {{Or [1..1] SEPA external codes: NIDN personal code, CUST client's code in the beneficiary's IT system, DRLC driver's licence number, SOSE social insurance number, CCPT passport number, EMPL employee's certification number, TXID code assigned by the State Tax Inspectorate, ARNU social insurance number of a person not issued a permanent residence permit Proprietary <Prtry> [0..1] Or}} Max35Text DebtorAccount <DbtrAcct> [1..1] Component (CashAccount16) Payer's account identification. +++Identification <Id> [1..1] Choice component (AccountIdentification4Choice) ++++IBAN <IBAN> [1..1] IBAN2007Identifier Only IBAN may be specified. Usage rules of the SEB data exchange format based on ISO XML standard messages, v / 59

13 Index Message item <XML Tag> Mandatoriness Type Description SEPA INTERNATIONAL +++Currency <Ccy> [0..1] ActiveOrHistoricCurrencyCode Other currency than EUR may be used between Payer's account currency accounts in SEB. To be used only when the payer has multi-currency account. The amount and currency must be specified in "InstructedAmount field DebtorAgent <DbtrAgt> [1..1] Component (BranchAndFinancialInstitutionIdentifi cation4) Financial institution handling payer's account (SEB). +++FinancialInstitutionIdentification <FinInstnId> [1..1] Component Only BIC allowed FinancialInstitutionIdentification7) ++++BIC <BIC> [0..1] BICIdentifier It is unnecessary to specify it. If specified, it must be in the BIC format, SWIFT code consisting of 11 characters UltimateDebtor <UltmtDbtr> [0..1] Component (PartyIdentification32) Initial payer. A party (legal entity), owing funds to (the ultimate) beneficiary of funds. +++Name <Nm> [0..1] Max70Text +++Identification <Id> [1..1] Choice Component (Party6Choice) A section describing the identifier of the initial payer. It will be sent unchanged to the beneficiary. ++++OrganisationIdentification <OrgId> {Or [1..1] Component (OrganisationIdentification4) The identifier to be used will be specified in "SchemeName field. If the payer is a legal entity, OrganisationIdentification field will be used, if a private person PrivateIdentification field. A section describing the identifier of the initial payer - the legal entity. It will be sent unchanged to the beneficiary. Only "BICOrBEI or "Other field may be used BICOrBEI <BICOrBEI> {{Or [0..1] Identifier BIC (Business Identifier Codes) will be used for identification of financial institutions according to ISO 9362 standard. BEI (Business Entity Identifier) may be used for identification of nonfinancial institutions Other <Othr> [0..n] International Or}} Component Field recurrence is not allowed. [0..1] SEPA Or}} Identification <Id> [0..1] International Max35Text [1..1] SEPA SchemeName <SchmeNm> [0..1] Component Mandatory field if "Identification field specifies the value Code <Cd> {{Or [1..1] Code Identifier name from the list of ISO external codes: TXID VAT payer's code, COID company's registration number, CUST client's code in the beneficiary's IT system Proprietary <Prtry> [1..1] Or}} Max35Text Usage rules of the SEB data exchange format based on ISO XML standard messages, v / 59

14 Index Message item <XML Tag> Mandatoriness Type Description SEPA INTERNATIONAL ++++PrivateIdentification <PrvtId> [1..1] Or} Component (PersonIdentification5) A section describing the identifier of the initial payer - a private person. It will be sent unchanged to the beneficiary. Only one field or "DateAndPlaceOfBirth or "Other field may be used +++++DateAndPlaceOfBirth <DtAndPlcOfBirth> {{Or [0..1] Date and place of birth BirthDate <BirthDt> [1..1] ISODate Birth date ProvinceOfBirth <PrvcOfBirth> [0..1] Max35Text Province of birth CityOfBirth <CityOfBirth> [1..1] Max35Text City of birth CountryOfBirth <CtryOfBirth> [1..1] CountryCode Country of birth code according to ISO 3166, two letter code Other <Othr> [0..n] International Or}} Component Field recurrence is not allowed. [0..1] SEPA Or}} Identification <Id> [0..1] International Max35Text [1..1] SEPA SchemeName <SchmeNm> [0..1] Component Mandatory field if "Identification field specifies the value Code <Cd> {{Or [1..1] Code Identifier name from the list of ISO external codes: NIDN personal code, CUST client's code in the beneficiary's IT system, DRLC driver's licence number, SOSE social insurance number, CCPT passport number, EMPL employee's certification number, TXID code assigned by the State Tax Inspectorate, ARNU social insurance number of a person not issued a permanent residence permit Proprietary <Prtry> [1..1] Or}} Max35Text ChargeBearer <ChrgBr> [0..1] ChargeBearerType1Code (CRED; DEBT; SHAR; SLEV) Only "SLEV" is allowed. If value is indicated in this field, CreditTransferTransactionInformation/Charg ebearer" field will not be filled out. If PaymentInformation/ChargeBearer" and CreditTransferTransactionInformation/Charg ebearer" fields are filled out, the value of CreditTransferTransactionInformation/Charg ebearer" field will be used for payment order processing ChargesAccount <ChrgsAcct> [0..1] Component (CashAccount16) +++Identification <Id> [1..1] Component ++++IBAN <IBAN> [1..1] IBAN2007Identifier +++Currency <Ccy> [1..1] Code CreditTransferTransactionInformation <CdtTrfTxInf> [1..n] Component (CreditTransferTransactionInformatio n10) Account for debiting charges Currency code of account for commission fees Usage rules of the SEB data exchange format based on ISO XML standard messages, v / 59

15 Index Message item <XML Tag> Mandatoriness Type Description SEPA PaymentIdentification <PmtId> [1..1] Component (PaymentIdentification1) INTERNATIONAL InstructionIdentification <InstrId> [0..1] Max35Text EndToEndIdentification <EndToEndId> [1..1] Max35Text Payment order number issued by the payer for the payment order identification, not transferred to the beneficiary. Unique payment order identification number. Transferred unchanged to the beneficiary. To be used for identification of the payment purpose, e.g. if the invoice is paid up by transferring funds three times, the "EndToEndIdentification" value of all three transactions must be identical, but "InstructionIdentification" different. When using the file upload service, any value is allowed or "NOTPROVIDED PaymentTypeInformation <PmtTpInf> [0..1] PaymentTypeInformation19 Set of elements used to further specify the type of transaction To be used with "PaymentInformation field ServiceLevel <SvcLvl> [0..1] Choice Component (ServiceLevel8Choice) Payment priority Code <Cd> [1..1] ExternalServiceLevel1Code Allowed value only "SEPA" Very urgent transfers in euro from will be executed as very urgent international transfers by indicating SDVA value in "ServiceLevel/Code" field. Allowed values: "NURG" = standard; "URGP" = urgent; "SDVA" = very urgent. Very urgent transfers in euro from will be executed as very urgent international transfers by indicating SDVA value in "ServiceLevel/Code" field.. If value of PaymentInformation/PaymentTypeInformatio n/servicelevel/code" field does not match with the value PaymentInformation/CreditTransferTransact ioninformation/paymenttypeinformation/ser vicelevel/code" field, the latter shall be followed CategoryPurpose <CtgyPurp> [0..1] Choice Component (CategoryPurpose1Choice) Information mostly used by the payer to indicate the specific payment processing based on a separate arrangement between the payer and the payer's payment service provider. The payer's payment service provider is not obligated to forward this information to the beneficiary's payment service provider Code <Cd> [1..1] Code Possible code values only according to the list of ISO external codes, e.g., SALA (Salary payments), TAXS (Tax payment), TREA (Treasury payment) Amount <Amt> [1..1] Choice component (AmountType3Choice) Usage rules of the SEB data exchange format based on ISO XML standard messages, v / 59

16 Index Message item <XML Tag> Mandatoriness Type Description SEPA INTERNATIONAL InstructedAmount <InstdAmt> {Or [1..1] ActiveOrHistoricCurrencyAndAmount Amount of funds to be transferred to the beneficiary prior to debiting the fees and the currency Payment currency must be always only in EUR. Amount must be 0.01 or more and or less. Decimal amounts will be separated by a dot. Amount must be 0.01 or more and or less. Currency code must comply with the ISO 4217 standard requirements. Decimal amounts will be separated by a dot. Field filling out sample: <Amt Ccy="SEK"> </Amt> EquivalentAmount <EqvtAmt> [1..1] Or} ActiveOrHistoricCurrencyAndAmount Amount to be transferred from the payer to the beneficiary, denominated in the payer's account currency Amount <Amt> [1..1] ActiveOrHistoricCurrencyAndAmount CurrencyOfTransfer <CcyOfTrf> [1..1] ActiveOrHistoricCurrencyCode ExchangeRateInformation <XchgRateInf> [0..1] Component (ExchangeRateInformation1) ContractIdentification <CtrctId> [0..1] Max35Text ChargeBearer <ChrgBr> [0..1] ChargeBearerType1Code (CRED; DEBT; SHAR; SLEV) SEPA allows only "SLEV". If field CreditTransferTransactionInformation/Charg ebearer" is filled out, it is not allowed to fill out PaymentInformation/ChargeBearer" field. If all fields PaymentInformation/ChargeBearer", and CreditTransferTransactionInformation/Charg ebearer" are filled out, value of field CreditTransferTransactionInformation/Charg ebearer" will be used for the payment order processing UltimateDebtor <UltmtDbtr> [0..1] Component (PartyIdentification32) Initial payer. A party (legal entity), owing funds to (the ultimate) beneficiary of funds. If the payer fills out both "UltimateDebtor" fields When specifying the initial payer in SEPA (in the "PaymentInformation" and payment orders, the value will be ignored. In "CreditTransferTransactionInformation" structures), SEB will use information available in the "CreditTransferTransactionInformation" structure. ++++Name <Nm> [0..1] Max70Text ++++Identification <Id> [1..1] Choice Component (Party6Choice) A section describing the identifier of the initial payer. It will be sent unchanged to the beneficiary. The identifier to be used will be specified in "SchemeName field. If the payer is a legal entity, the OrganisationIdentification field will be used, if a private individual the PrivateIdentification field. Usage rules of the SEB data exchange format based on ISO XML standard messages, v / 59

17 Index Message item <XML Tag> Mandatoriness Type Description SEPA INTERNATIONAL +++++OrganisationIdentification <OrgId> {Or [1..1] Component (OrganisationIdentification4) A section describing the identifier of the initial payer - a legal entity. It will be sent unchanged to the beneficiary. Only "BICOrBEI, or "Other field may be used BICOrBEI <BICOrBEI> {{Or [0..1] AnyBICIdentifier BIC (Business Identifier Codes) will be used for identification of financial institutions according to ISO 9362 standard. BEI (Business Entity Identifier) may be used for identification of nonfinancial institutions Other <Othr> [0..n] International Or}} [0..1] SEPA Or}} Component Field recurrence is not allowed Identification <Id> [0..1] International [1..1] SEPA Text SchemeName <SchmeNm> [0..1] Component Mandatory field if "Identification field specifies the value Code <Cd> [1..1] Code Identifier name from the list of ISO external codes: TXID VAT payer's code, COID company's registration number, CUST client's code in the beneficiary's IT system Proprietary <Prtry> [1..1] Max35Text +++++PrivateIdentification <PrvtId> [1..1] Or} Component (PersonIdentification5) A section describing the identifier of the initial payer - private individual. It will be sent unchanged to the beneficiary. Only the"dateandplaceofbirth field or the "Other field may be used DateAndPlaceOfBirth <DtAndPlcOfBirth> {{Or [0..1] Component (DateAndPlaceOfBirth) Date and place of birth information BirthDate <BirthDt> [1..1] ISODate Birth date CityOfBirth <CityOfBirth> [1..1] Max35Text City of birth CountryOfBirth <CtryOfBirth> [1..1] CountryCode Country of birth code according to ISO 3166, two letter code Other <Othr> [0..n] International Or}} [0..1] SEPA Or}} Component Field recurrence is not allowed Identification <Id> [0..1] International [1..1] SEPA Text SchemeName <SchmeNm> [0..1] Component Mandatory field if "Identification field specifies the value. Usage rules of the SEB data exchange format based on ISO XML standard messages, v / 59

18 Index Message item <XML Tag> Mandatoriness Type Description SEPA INTERNATIONAL Code <Cd> [1..1] Code Identifier name from the list of ISO external codes: NIDN personal code, CUST client's code in the beneficiary's IT system, DRLC driver's licence number, SOSE social insurance number, CCPT passport number, EMPL employee's certification number, TXID code assigned by the State Tax Inspectorate, ARNU social insurance number of a person not issued a permanent residence permit Proprietary <Prtry> [1..1] Max35Text IntermediaryAgent1 <IntrmyAgt1> [0..1] Component Beneficiary's credit institution (BranchAndFinancialInstitutionIdentifi cation4) ++++FinancialInstitutionIdentification <FinInstnId> [1..1] Component +++++BIC <BIC> [0..1] BICIdentifier +++++ClearingSystemMemberIdentification <ClrSysMmbId> [0..1] Component (ClearingSystemMemberIdentificatio n2) ClearingSystemIdentification <ClrSysId> [0..1] Choice Component (ClearingSystemIdentification2Choic e) Code <Cd> [1..1] ExternalClearingSystemIdentification 1Code MemberIdentification <MmbId> [1..1] Max35Text +++++Name <Nm> [0..1] Max140Text +++++Postal Address <PstlAdr> [0..1] Component AddressLine <AdrLine> [0..7] Max70Text Used In case if the beneficiary's bank does not have BIC IntermediaryAgent1Account <IntrmyAgt1Acct> [0..1] Component (CashAccount16) ++++Identification <Id> [1..1] Choice component (AccountIdentification4Choice) +++++IBAN <IBAN> {Or [1..1] IBAN2007Identifier Mandatory in case of RUR payments (a decision is based taking into consideration the beneficiary's bank address) Other <Othr> [1..1] Or} Component (GenericAccountIdentification1) Identification <Id> [1..1] Max34Text Scheme Name <SchmeNm> [0..1] Code <Cd> {{Or [1..1] ExternalAccountIdentification1Code BBAN in case BBAN is entered in <Othr>/<Id> Proprietary <Prtry> [1..1] Or}} Max35Text CreditorAgent <CdtrAgt> [0..1] Component - See (BranchAndFinancialInstitutionIdentifi cation4 Component) Beneficiary's credit institution ++++FinancialInstitutionIdentification <FinInstnId> [1..1] Component Usage rules of the SEB data exchange format based on ISO XML standard messages, v / 59

19 Index Message item <XML Tag> Mandatoriness Type Description SEPA INTERNATIONAL +++++BIC <BIC> [0..1] BICIdentifier Not mandatory to specify starting from If specified, it must be in BIC format, 11 character SWIFT code. If BIC is not specified, Only BIC is allowed. The SWIFT code (BIC) in field +++++ClearingSystemMemberIdentification <ClrSysMmbId> [0..1] Component (ClearingSystemMemberIdentificatio n2) ClearingSystemIdentification <ClrSysId> [0..1] Component (ClearingSystemIdentification2Choic e) Code <Cd> [1..1] ExternalClearingSystemIdentification 1Code MemberIdentification <MmbId> [1..1] Max35Text The SWIFT code (BIC) in field PaymentInformation/CreditTransferTransact ioninformation/creditoragent/financialinstitu tionidentification/bic", or the bank code in field PaymentInformation/CreditTransferTransact ioninformation/creditoragent/financialinstitu tionidentification/clearingsystemmemberide ntification/memberidentification" are mandatory for the international payment orders Name +++++Other <Nm> <Othr> [0..1] [0..1] Max140Text Component Mandatory field. The field will be filled out automatically, if the beneficiary's account in IBAN format is (GenericFinancialIdentification1) Identification <Id> [1..1] Max35Text Used in case of RUR payments. Part of Beneficiary bank's BIC code structure SchemeName <SchmeNm> [0..1] Component (FinancialIdentificationSchemeName 1Choice) Code <Cd> [1..1] ExternalFinancialInstitutionIdentificati on1code +++++Postal Address <PstlAdr> [0..1] Component Used in case of RUR payments. Part of Beneficiary bank's BIC code structure. Value "TXID" Country <Ctry> [0..1] CountryCode AddressLine <AdrLine> [0..7] Max70Text Mandatory in case of payments to BYR, UAH and KZT payment CreditorAgentAccount <CdtrAgtAcct> [0..1] Component (CashAccount16) ++++Identification <Id> [1..1] Choice component (AccountIdentification4Choice) Usage rules of the SEB data exchange format based on ISO XML standard messages, v / 59

20 Index Message item <XML Tag> Mandatoriness Type Description SEPA INTERNATIONAL +++++Other <Othr> [1..1] Or} Identification <Id> [1..1] Max34Text In case of RUB payment it is mandatory Creditor <Cdtr> [0..1] International [1..1] SEPA Component - See (PartyIdentification832 Component) Beneficiary. Payment party (legal entity) in whose favour funds are credited. ++++Name <Nm> [0..1] International [1..1] SEPA Max140Text (International) Max70Text (SEPA) ++++PostalAddress <PstlAdr> [0..1] Component (PostalAddress6) Name has limited length of 70 symbol +++++Country <Ctry> [0..1] Code Country of birth code according to ISO 3166, two letter code Address Line <AdrLine> [0..7] International [0..2] SEPA ++++Identification <Id> [0..1] Max70Text Two repeats of this attribute are allowed, each consisting of 70 characters Mandatory field. Mandatory field. A section describing the identifier of the beneficiary - a legal entity. It will be sent unchanged to The identifier to be used will be specified in "SchemeName field. If the payer is a legal entity, the OrganisationIdentification field will be used, if a private individual the PrivateIdentification field OrganisationIdentification <OrgId> {Or [1..1] Component (OrganisationIdentification4) A section describing the identifier of the beneficiary - a legal entity. It will be sent unchanged to the beneficiary BICOrBEI <BICOrBEI> {{Or [0..1] Identifier BIC (Business Identifier Codes) will be used for identification of financial institutions according to ISO 9362 standard. BEI (Business Entity Identifier) will be used for identification of nonfinancial institutions Other <Othr> [0..n] International Or}} [0..1] SEPA Or}} Choice Component (Party6Choice) Component (GenericOrganisationIdentification1) Field recurrence is not allowed Identification <Id> [1..1] Max35Text If beneficiary is legal entity and resident of Russian federation, INN code (10 digits) should also be entered. Also KPP, RNN (in case of KZT) code should be entered here SchemeName <SchmeNm> [0..1] Choice Component Mandatory field if "Identification field specifies (OrganisationIdentificationSchemeN the value. ame1choice) Code <Cd> {{Or [0..1] International {{Or [1..1] SEPA Proprietary <Prtry> [0..1] International Or}} [1..1] SEPA Or}} ExternalOrganisationIdentification1C ode Max35Text Identifier name allowed from the list of ISO external codes: TXID TaxIdentificationNumber, COID company's registration number, CUST client's code in the beneficiary's IT system. Used in case of RUR payments. For KPP code value "KPP". For INN - "INN" Issuer <Issr> [0..1] Max35Text Used in case of RUR payments. For KPP code value "Russian Federal Tax Agency" +++++PrivateIdentification <PrvtId> [1..1] Or} Component (PersonIdentification5) A section describing the identifier of the initial payer - private individual. It will be sent unchanged to the beneficiary. Only "DateAndPlaceOfBirth or "Other field may be used DateAndPlaceOfBirth <DtAndPlcOfBirth> {{Or [0..1] Date and place of birth information Usage rules of the SEB data exchange format based on ISO XML standard messages, v / 59

21 Index Message item <XML Tag> Mandatoriness Type Description SEPA INTERNATIONAL BirthDate <BirthDt> [1..1] ISODate Birth date ProvinceOfBirth <PrvcOfBirth> [0..1] Max35Text Province of birth CityOfBirth <CityOfBirth> [1..1] Max35Text City of birth CountryOfBirth <CtryOfBirth> [1..1] CountryCode Country of birth code according to ISO 3166, two letter code Other <Othr> [0..n] International Or}} Component Field recurrence is not allowed. [0..1] SEPA Or}} (GenericPersonIdentification1) Identification <Id> [1..1] Max35Text SchemeName <SchmeNm> [0..1] Choice Component (PersonIdentificationSchemeName1 Mandatory field if "Identification field specifies the value. Choice) Code <Cd> {{Or [1..1] ExternalPersonIdentification1Code Identifier name from the list of ISO external codes: NIDN personal code, CUST client's code in the beneficiary's IT system, DRLC driver's licence number, SOSE social insurance number, CCPT passport number, EMPL employee's certification number, TXID code assigned by the State Tax Inspectorate, ARNU social insurance number of a person not issued a permanent residence permit Proprietary <Prtry> [1..1] Or}} Max35Text +++Contact Details <CtctDtls> [0..1] Component ++++PhoneNumber <PhneNb> [0..1] PhoneNumber ++++Other <Othr> [0..1] Max35Text CreditorAccount <CdtrAcct> [0..1] International Component (CashAccount16) Beneficiary s account [1..1] SEPA ++++Identification <Id> [1..1] Choice component (AccountIdentification4Choice) +++++IBAN <IBAN> {Or [1..1] IBAN2007Identifier Only IBAN format may be specified. BYR account is 13 digits long In case of UAH - 14 digits long In case of GBP payments if beneficiary's bank SWIFT was entered, IBAN is mandatory Other <Othr> [1..1] Or} Component (GenericAccountIdentification1) Identification <Id> [1..1] Max34Text Scheme Name <SchmeNm> [0..1] Code <Cd> {{Or [1..1] ExternalAccountIdentification1Code Only BBAN code will be specified, if BBAN was entered in "Other/Identification" structure Proprietary <Prtry> [1..1] Or}} Max35Text ++++Currency <Ccy> [0..1] Code UltimateCreditor <UltmtCdtr> [0..1] Component - See Ultimate beneficiary (PartyIdentification32 Component) ++++Name <Nm> [0..1] Max70Text Max 70 characters Usage rules of the SEB data exchange format based on ISO XML standard messages, v / 59

22 Index Message item <XML Tag> Mandatoriness Type Description SEPA INTERNATIONAL ++++Identification <Id> [1..1] International [0..1] SEPA Choice Component (Party6Choice) A section describing the identifier of the ultimate beneficiary. It will be sent unchanged to the beneficiary OrganisationIdentification <OrgId> {Or [1..1] Component (OrganisationIdentification4) If the payer is a legal entity, the OrganisationIdentification field will be used, if a private individual the PrivateIdentification field. A section describing the identifier of the initial payer - a legal entity. It will be sent unchanged to the beneficiary. Only "BICOrBEI or "Other field may be used BICOrBEI <BICOrBEI> {{Or [0..1] Identifier BIC (Business Identifier Codes) may be used for identification of financial institutions according to ISO 9362 standard. BEI (Business Entity Identifier) may be used for identification of nonfinancial institutions Other <Othr> [0..n] International Or}} [0..1] SEPA Or}} Component (GenericOrganisationIdentification1) Field recurrence is not allowed Identification <Id> [1..1] Max35Text SchemeName <SchmeNm> [0..1] Choice Component (OrganisationIdentificationSchemeN ame1choice) Mandatory field if "Identification field specifies the value Code <Cd> {{Or [1..1] Code Identifier name from the list of ISO external codes: TXID VAT payer's code, COID company's registration number, CUST client's code in the beneficiary's IT system Proprietary <Prtry> [1..1] Or}} Max35Text +++++PrivateIdentification <PrvtId> [1..1] Or} Component (PersonIdentification5) A section describing the identifier of the ultimate beneficiary - a private individual. It will be sent unchanged to the beneficiary. Only one value of "DateAndPlaceOfBirth or "Other may be entered DateAndPlaceOfBirth <DtAndPlcOfBirth> {{Or [0..1] Data and place of birth information BirthDate <BirthDt> [1..1] ISODate Birth date ProvinceOfBirth <PrvcOfBirth> [0..1] Max35Text Province of birth CityOfBirth <CityOfBirth> [1..1] Max35Text City of birth CountryOfBirth <CtryOfBirth> [1..1] CountryCode Country of birth code according to ISO 3166, two letter code Other <OthrID> [0..n] International Or}} Component Field recurrence is not allowed. [0..1] SEPA Or}} (GenericPersonIdentification1) Identification <Id> [1..1] Max35Text SchemeName <SchmeNm> [0..1] Choice Component (PersonIdentificationSchemeName1 Choice) Mandatory field if "Identification field specifies the value. Usage rules of the SEB data exchange format based on ISO XML standard messages, v / 59

23 Index Message item <XML Tag> Mandatoriness Type Description SEPA INTERNATIONAL Code <Cd> {{Or [1..1] Code Identifier name from the list of ISO external codes: NIDN personal code, CUST client's code in the beneficiary's IT system, DRLC driver's licence number, SOSE social insurance number, CCPT passport number, EMPL employee's certification number, TXID code assigned by the State Tax Inspectorate, ARNU social insurance number of a person not issued a permanent residence permit Proprietary <Prtry> [1..1] Or}} Max35Text ++++CountryOfResidence <CtryOfRes> [0..1] Country Code InstructionForCreditorAgent <InstrForCdtrAgt> [0..n] Component (InstructionForCreditorAgent1) Code <Cd> [0..1] Code PHOB - Payer to be informed by telex TELB - Payer to be informed by phone Purpose <Purp> [0..1] Choice component (Purpose2Choice) Payment order type. Enables to identify the main reason of money transfer or purpose for the beneficiary Code <Cd> {Or [1..1] Code According to the list of ISO external codes, e.g. INPC car insurance premium, PPTI property insurance premium, ADVA advance invoice payment, EDUC education payment, TAXR tax refund, PHON phone services, PRWY payment related to railway transport, GASB gas bill payment, etc Proprietary <Prtry> [1..1] Or} Max35Text RegulatoryReporting <RgltryRptg> [0..10] Component (RegulatoryReporting3) ++++Details <Dtls> [0..n] Component (StructuredRegulatoryReporting3) +++++Type <Tp> [0..1] Max35Text Information +++RemittanceInformation <Inf> <RmtInf> [0..n] [0..1] Max35Text Component Transfer information. (RemittanceInformation5) "Structured" or "Unstructured" may be used. The Unstructured may be used to specify the payment purpose. Information submitted in the Structured will be ingonred Unstructured <Ustrd> [0..n] International [0..1] SEPA Structured <Strd> [0..n] International [0..1] SEPA Max140Text Component (StructuredRemittanceInformation7) Max 140 characters. Free text may be submitted in structured form. Field recurrence is not allowed. Structured payment purpose reference (e.g., payment code). Usage rules of the SEB data exchange format based on ISO XML standard messages, v / 59

24 Index Message item <XML Tag> Mandatoriness Type Description SEPA INTERNATIONAL CreditorReferenceInformation <CdtrRefInf> [0..1] Component (CreditorReferenceInformation2) Type <Tp> [0..1] Component (CreditorReferenceType2) CodeOrProprietary <CdOrPrtry> [0..1] International [1..1] SEPA Choice component (CreditorReferenceType1Choice) Code <Cd> {Or [1..1] DocumentType3Code (DISP; FXDR; PUOR; RADM; RPIN; SCOR) Only "SCOR" is allowed Issuer <Issr> [0..1] Max35Text Reference <Ref> [0..1] Max35Text If necessary to specify the payment code together with the payment purpose, such If the value is specified in the non-structured purpose field, the beneficiary's bank is not information is submitted in the Unstructured field required to check it. according to the rules for filling out submitted by If beneficiary's bank is checking control the beneficiary. number and it fails, bank can still proceed with executing the payment and send it to the next party of the chain. Usage rules of the SEB data exchange format based on ISO XML standard messages, v / 59