Structure of LITAS – ESIS text format export files of local payment orders

Format explanation

* – mandatory field
C – symbolic field
YYYY – four figures specifying the year
MM – two figures specifying the month (mandatory requirement)
DD – two figures specifying the day (mandatory requirement)
N – digital field

Note General requirements
  • the maximum length of the field is specified;
  • each field is separated by the symbol TAB (#9);
  • file extension depends on the document type. Name does not matter.
  • one payment information is specified in one row;
  • literal code of foreign exchange according to the ISO standards (pvz., EUR);
  • Windows 1257 code table is used in the text.

Import structure of local payment order

File extension must be mokesis. Name does not matter, e.g. pavedimai.mokesis.

Row no. Title Size Comments
1 Number C10* Number of the payment order
2 Date C8 Format: YYYYMMDD
3 Bank transaction date C8* Format: YYYYMMDD
4 Payment type (priority) N1* Possible entry:
1 – standard
2 – urgent
5 Payer’s account number C35* Payer’s account number (IBAN)
6 Payer’s name and surname / Company name C200 Payer’s name
7 Payer’s personal name / Registration No. C11 Payer’s personal (legal entity’s) code
8 Payer’s credit institution C11 BIC format
9 Customer’s code in the beneficiary’s information system C16 Code agreed by the payer and the beneficiary that enables the payer to identify the beneficiary
10 Originator’s account No. C35 Originator’s account number
11 Originator’s name and surname / Company name C140 Originator’s name and surname / Company name
12 Originator’s personal code / Company registration No. C11 Originator’s personal (legal entity) code
13 Beneficiary’s account No. C35* Beneficiary’s account number (IBAN)
14 Beneficiary’s name and surname / Company name C200* Beneficiary’s name
15 Beneficiary’s personal code / Registration No. C11 Beneficiary’s personal (legal entity) code
16 Beneficiary’s credit institution C11 BIC format
17 Customer’s code in the payer’s information system C16 Code agreed by payer and beneficiary that enables the payer to identify the beneficiary
18 Beneficiary party account No. C35 Beneficiary party account number
19 Beneficiary party name and surname / Company name C140 Beneficiary party name and surname or Company name
20 Beneficiary party personal code / Registration No. C11 Beneficiary party personal (legal entity) code
21 Amount N14* Cents are not separated by dot or comma. 5025 must be indicated instead of 50.25
22 Currency code C3* Currency code according to ISO standards
23 Fee code C28 Fee code indicated by the customer
24 Payment details C300* Payment details indicated by the customer
25 Archive code C50 Code for each transaction, which is given by the credit institution. Only for export

Import structure of international payment orders

File extension must be taresis. Name does not matter, e.g. international.taresis.

Row no. Title Size Comments
1 Number C10* Number of the payment order
2 Date C8 Format: YYYYMMDD
3 Bank transaction date N6 Format: YYYYMMDD
4 Payment type (priority) N1* Possible entry:
1 – standard
2 – urgent
3 – extra urgent
5 Currency code C3* Currency code according to ISO standards
6 Debit currency C3 Invalid for the Internet banking
7 Amount N14* Cents are not separated by dot or comma. 5025 must be indicated instead of 50.25
8 Payer’s account C35* Payer’s account
9 BIC of the credit institution - issuer of the payment order C11 -
10 Correspondent bank S.W.I.F.T. C11 Correspondent bank S.W.I.F.T. code. To be specified in capital letters. It consists of 8 or 11 symbols
11 Beneficiary’s account with correspondent bank C34 Account of correspondent bank
12 Name of correspondent bank 1 C35 Name of correspondent bank
13 Name of correspondent bank 2 C35 Name of correspondent bank
14 Address of bank 1 C35 Address of correspondent bank
15 Address of bank 2 C35 Address of correspondent bank
16 Beneficiary’s bank S.W.I.F.T. C11 Bank S.W.I.F.T. code. To be specified in capital letters. It consists of 8 or 11 symbols
17 Beneficiary’s Bank code C34 -
18 Name of the Beneficiary’s bank 1 C35* Name of Beneficiary’s bank to be entered into 2x35 symbol fields
19 Name of the Beneficiary’s bank 2 C35 -
20 Address of the Beneficiary’s bank 1 C35 Bank address to be entered into 2x35 symbol fields
21 Address of the Beneficiary’s bank 2 C35 -
22 Beneficiary’s account C35* Beneficiary’s account
23 Beneficiary’s name C35* Beneficiary’s name to be entered into 2x35 symbol fields
24 Beneficiary’s name 2 C35 -
25 Beneficiary’s address 1 C35* Beneficiary’s address to be entered into 2x35 symbol fields
26 Beneficiary’s address 2 C35 -
27 Payment details 1 C35 Payment details to be entered into 4x35 symbol fields
28 Payment details 2 C35 -
29 Payment details 3 C35 -
30 Payment details 4 C35 -
31 Foreign bank fees C1* Possible entry:
1 – only payer
2 – payer and beneficiary
3 – only beneficiary
32 Inform the payer by telex C1 Possible entry:
0 – do not inform
1 – inform
33 Inform the payer by phone C1 Possible entry:
0 – do not inform
1 – inform
34 Phone number for information purposes C20 -
35 Account for commission fees C20* -
36 Literal code of the currency of account for commission fees C3* -
37 Intermediary bank’s SWIFT C11 Invalid for the Internet banking
38 Name of the intermediary bank C70 Invalid for the Internet banking
39 Name of the intermediary bank C35 Invalid for the Internet banking
40 Archive code C50 Invalid for the Internet banking

Description of FiDAViSta format

A file prepared in FiDAViSta format can consist of several parts that are combined under the element of one set (Root) under a field name. In this Root element the reference on the location of XML scheme also is given, where the specified file ends in 4-digit version number. The possible groups of the field set are as follows:

  • Header – a group of header fields, which contains information on the preparer of the file and the file preparation time.
  • Statement – a field group of the account statement that is used for storing bank account statements or account report information data. (will be available soon).
  • PmtStat – payment status set that maintains information on payment statuses on the base of previously specified identifiers. (will be available soon).
  • Payment – group of payment fields, which contains information on payments (domestic, budget, international, salary payments, etc.).

Header

Tag Length Type O/M Description
Min Max
Header
Timestamp
17 17 xs:string O File preparation time, format YYYYMMDDHHMMSSsss
From 0 70 xs:string O Preparer’s identifier
Extension
Header
- - ExtensionType O Field for the location of additional elements

Payment status

Tag Length Type O/M Description
Min Max
PmtStat
ExtId
0 10 SwiftStringType O Reference to the payment identifier (payment identifier is specified in the payment)
BenExtId 0 5 SwiftStringType O Reference to the payment identifier (payment identifier is specified in the payment)
BankRef 0 25 xs:string O Bank reference
DocNo 1 10 xs:string M Payment/document number
StatCode 1 1 xs:string M Payment status code:
E – executed or booked
R – revoked
P – processing
O – other status
InfoToCustomer 0 70 xs:string O Explanation of payment status/error message
BookDate 10 10 xs:date O Payment date (only for executed payments). Format YYYY-MM-DD
RegDate 10 10 xs:date O Payment order registration date – the same as specified in the file “Payment”.
Format YYYY-MM-DD
Extension
PmtStat
- - ExtensionType O Field for the location of additional elements

Payments

Tag Length Type O/M Description
Min Max
Payment ExtId 0 10 SwiftStringType O Unique payment identifier in the "external" (accounting) system. By this identifier the "PmtStat “ requests are made. And by this identifier the link of the booking with the exported payment order can be found in the "Statement" file
DocNo 1 10 SwiftStringType M Payment/document number. It is assigned by the user in the accounting system
RegDate 10 10 xs:date O Payment order registration date in the accounting system. Format YYYY-MM-DD. When exporting “PmtStat” for a certain period from the bank system, the selection is made by this field
TaxPmtFlg 1 1 xs:string
Default: “N”
M Indication that the payment is or is not a tax payment. Possible values:
“Y” – tax payment
“N”- normal payment
Ccy 3 3 CurrencyType M Payment currency
PmtInfo 0 140 EksStringType O Payment details. (Information for the beneficiary)
BankInfo 0 140 xs:string O Information for the bank
PayLegalId 0 20 LegalIDType O Payer’s registration number, personal ID or tax payer’s code
In the case of the tax payment, the content of this field, if filled out, will be sent as the tax payer’s code
PayAccNo 1 34 AccountMType M Payer’s account number
PaySubAccNo 0 34 AccountOType O Payer’s sub account number
DebitCcy 3 3 CurrencyType O Debited currency
If this field is not filled out, the bank assumes that the content of this field is by default:
- in case of a single-currency account – the account currency;
- in case of a multi-currency account – the payment currency.
If, in the case of a multi-currency account, the position in the payment currency is not open, it will be interpreted at the bank’s discretion.
To avoid confusion, it is recommended to fill in this field
BenSet - - - M Beneficiary data
BenExtId 0 5 SwiftStringType O Unique beneficiary’s identifier within the payment order. Recommended to be filled in case of the “Mass payment”.
By this field the accounting system will be able to identify the payment in other files (“Payment status”, “Statement”)
Priority 1 1 xs:string
“N” / “U” / “X”
Default = “N”
M Payment priority:
N – Normal
U – Urgent
X – Express
Default value: N
For the domestic payments in Latvian lats, the options “N” and “U” are used
Comm 3 3 xs:string
“OUR” / “BEN” /
“SHA”
Default = “OUR”
M Commission type:
OUR – payer
BEN - beneficiary
SHA - shared
Default value: OUR
Amt 1 12 AmountType M Payment amount. Dot is used as a decimal separator ’.’
BenAccNo 0 34 AccountOType O Beneficiary’s account number
BenSubAccNo 0 34 AccountOType O Beneficiary’s sub account number
BenAccIbanFlg 0 1 xs:string
“Y” / “N”
Default = “N”
O Beneficiary’s account IBAN feature
“Y” – the bank software shall perform account number checksum verification in accordance with the international IBAN standard.
If the value of this field is “Y”, the content of the field "BenSubAccNo" shall be disregarded
BenName 1 105 EksStringType M Beneficiary’s name
BenLegalId 0 20 LegalIDType O Beneficiary’s registration number , tax payer’s code, or personal ID
BenAddress 0 70 EksStringType O Beneficiary’s address
BenCountry 2 2 CountryType M Code of the beneficiary’s registration country E.g.: LV, EE, US, etc. ISO-3166
BBName 0 35 EksStringType O Beneficiary’s bank name
BBAddress 0 70 EksStringType O Beneficiary’s bank address
BBSwift 8 11 SWIFTType O Beneficiary’s bank SWIFT code or BIC code of the Bank of Latvia
BBCode 0 66 BankCodeType O Beneficiary’s bank code. This field contains mandatory atttribute CodeType.
CBAcc 0 34 AccountOType O Recipient bank’s correspondent account in the intermediary bank
CBName 0 35 EksStringType O Intermediary bank name
CBSwift 8 11 SWIFTType O Intermediary bank SWIFT code
CBCode 0 66 BankCodeType O Intermediary bank code. This field contains mandatory attribute CodeType
BudgCode 0 10 SwiftStringType O Budget revenue code
AmkSet - - - O External payment code
Opc 1 3 xs:string M AMK (balance) code; only digits [0-9]
Amt

AmkSet
1 12 AmountType O AMK (balance) code sum. Dot is used as a decimal separator ’.’
Extension
BenSet
- - ExtensionType O Field for the location of additional elements
Extension
Payment
- - ExtensionType O Field for the location of additional elements

Field types

Type Length Permitted symbols
Description
Min Max
xs:string 0 - XML standard type for unicode text
xs:date 10 10 0-9|- XML standard type for the date
Format: YYYY-MM-DD
BankCodeType - - 0-9|A-Z|a-z|s/-?:().,'+nr Derived from SwiftString.
Added attribute CodeType, the type of which is SwiftString. The attribute is mandatory
ExtensionType 0 - Intended for the location of any elements not included in the standard
AccountMType 1 34 0-9|A-Z|a-z|s/-?:().,'+nr Derived from SwiftString. Restricted in length
AccountOType 0 34 0-9|A-Z|a-z|s/-?:().,'+nr Derived from SwiftString. Restricted in length
AmountType 1 12 0-9|. Derived from xs:decimal.
Restricted in length – 12 symbols no in the set, 2 of which behind the decimal separator dot
CurrencyType 3 3 A-Z Derived from xs:string
EksStringType - - 0-9|A-Z|a-z|a-ž|A-Ž|s/-?:().,'+nr Derived from xs:string. Restricted permitted symbols in accordance with the restrictions of the electronic clearing system of the Bank of Latvia (or xl set of symbols) and lowercase letters of Latvian and Latin alphabets
LegalIDType 0 20 0-9|A-Z|a-z|s/-?:().,'+nr Derived from SwiftString. Restricted in length
SWIFTType 8 11 A-Z|0-9 Intended for SWIFT code in accordance with the SWIFT standard
SwiftStringType - - 0-9|A-Z|a-z|s/-?:().,'+nr Derived from xs:string. Restricted permitted symbols – the symbols that correspond to the SWIFT X set of symbols are permitted, except for {“ and “}” and Latin alphabet lowercase letters

XML (pain.001.001.03 ) format

Credit transfer message initiated by the client is sent to the bank of the payer with the request to debit funds from the account of the payer and transfer them to the account of the recipient. The message may also be sent when the party initiating the credit transfer has obligations to send a payment order on behalf of the payer. The account statement message provided by the bank is sent to the account owner with all operations executed on the account during the selected time period in the past.

Each element of the credit transfer message is based on definitions of elements of the message "pain.001.001.03" (CustomerCreditTransferInitiationV03) of ISO20022 XML standard. Detailed description of elements can be found by the address: http://www.iso20022.org/documents/general/Payments_Maintenance_2009.zip .

Description of message elements can be found here .

Example .xml format file can be found here .

Character set

Character set is a set of characters which can be used in message elements. ISO 20022 XML messages are adapted for multilingual environment. Characters are coded with UTF-8. Banks and their customers must be able to support the Latin character set commonly used in international communication, as follows:

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
0 1 2 3 4 5 6 7 8 9
/ - ? : ( ) . , ‘ + Space

All other character of the UTF-coding in sent and received payments are converted according to the conversion table recommended by the EPC which corresponds to the best practice: https://www.europeanpaymentscouncil.eu/document-library/guidance-documents/sepa-requirements-extended-character-set-unicode-subset-best .

Message structure

XML document is described with a scheme written in a specific XSD language (XML Schema Definition) Such schemes describe XML Tags, their structure and order. It also may indicate codes which are possible only for specific data, whether data is mandatory or optional, number of possible cases (or repetitions), etc.

The common XSD scheme for the credit transfer message pain.001.001.03 is given at the address: http://www.iso20022.org/documents/messages/pain/schemas/pain.001.001.03.zip .

The data file which includes message pain.001.001.03 is of the following structure:

<?xml version="1.0" encoding="UTF-8"?>
<Document xmlns="urn:iso:std:iso:20022:tech:xsd:pain.001.001.03"
          xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
          xsi:schemaLocation="urn:iso:std:iso:20022:tech:xsd:pain.001.001.03 pain.001.001.03.xsd">
   <!-- Content of the message -->
</Document>
                    

The data file has to contain only one tag with only one XML message, unless the service provider and the client agree otherwise.

The content of the message consists of:

  • A. Group Header. Mndatory and cannot be repeated. Is is a set of characteristics shared by all individual transactions included in the message (e.g. date and time of message creation, number of operations in the message, etc.).
  • B. Payment Information. Mandatory and can be repeated. It is a set of characteristics that applies to the debit side of the payment transactions included in the credit transfer initiation (e.g. name of the payer, type of the operation, etc.).
  • C. Transaction Information. Mandatory and can be repeated. It is a set of elements used to provide information on the individual transaction(s) included in the message. Includes the recipient, payment purpose/details, etc.

The number of Payment Information and Transaction Information is given in the Group Header.