Financial and capital market Commission, the provisions of regulations No 197 in Riga on 29 November 2016 (financial and capital market Commission Council meeting No. 42 3. p.)
Information on credit customers and their transactions and provision of financial and capital market Commission Issued regulations regulations pursuant to the Criminal money-laundering and terrorist financing Prevention Act article 37.1 i. General questions 1. "information on credit customers and their transactions and provision of financial and capital market Commission regulations" (hereinafter-the rules) shall lay down the requirements as credit institutions and of the Member States and third countries, branches of credit institutions (hereinafter referred to as the credit institution) collects information about clients and their transactions , and the order in which they provide this information in the financial and capital market Commission (hereinafter the Commission). 2. the objective is to ensure a uniform and transparent compilation of information about clients and their transactions, as well as timely and accurate provision of this information, the Commission increased the criminal money-laundering and the financing of terrorism (hereinafter NILLTF) risk identification and monitoring of the business of credit NILLTF in the field of prevention.
II. Information collection requirements 3. a credit institution shall ensure that, at the request of the Commission, it shall collect and submit information about customers, which the Commission specified in the request during the period (hereinafter referred to as the report period) have or have had a business relationship with the credit institution and their transactions, providing information on: 3.1. credit institutions customers – individuals, indicating for each customer up to date information on the last day of the reference period in accordance with the provisions of annex 1; 3.2. a credit institution's clients – legal persons in the showing of each customer up to date information on the last day of the reference period in accordance with the provisions of annex 2; 3.3. credit institutions customers true beneficiaries – natural persons, including credit institutions customers true beneficiaries who changed during the reference period, specifying for each customer the true beneficiaries of the information on the last day of the reference period in accordance with the provisions of annex 3; 3.4. the customer of a credit institution (society, political parties, cooperative society) the true beneficiaries – legal entities, including credit institutions customers true beneficiaries who changed during the reference period, giving information on the last day of the reference period in accordance with the provisions of annex 4; 3.5. the credit institution's customer representatives, including representatives of customers of the credit institution, which the representation rights expired during the reporting period, specifying for each customer's representative information on the last day of the reference period in accordance with annex 5 of these regulations; 3.6. the customer of a credit institution the cashless transactions, stating, for each client transaction conducted during the reporting period, the information in accordance with the provisions of annex 6; 3.7. credit accounts, including the accounts of the credit institution, which are closed during the reporting period, turnover, showing information about each client's account type (for example, settlement, investment, war, trust, financial instrument URu.tml.), in accordance with the provisions of annex 7 for each reporting period in the calendar month; 3.8 offset bank requests received on the client's business, giving information for each of the corresponding bank received the request and the response provided in accordance with Annex 8 of these rules; 3.9. trust and fiduciary transactions, indicating the information in accordance with the provisions of Annex 9; 3.10. credit institutions customers account turnover in cash, showing the information in accordance with the provisions of annex 10 for each reporting period in the calendar month; 3.11. Balancing (lor) accounts, including balancing (lor) accounts that are closed during the reporting period, in accordance with the provisions of the annex, for each reporting period included a calendar month basis. 4. a credit institution shall ensure that the information collected is accurate and corresponds to the information contained in the current system.
III. procedure for the submission of information 5. a credit institution shall submit at the request of the Commission of these provisions to the Commission the information referred to in paragraph 3, the Commission specified the amount corresponding to the period set by the Commission.

6. a credit institution that rule laid down in paragraph 3 for information about the reporting period shall be electronically: 6.1 the .CSV (Comma Separated values) file format in accordance with the provisions of 1-11. the requirements set out in the annex; 6.2. the field values, use the UTF-8 encoding; 6.3. the separate values (delimiter) uses a comma; 6.4. the value of the qualifier (qualifier) used quotation marks (double quotes) the values indicated that rule 1-11; 6.5. If one field contains multiple data values, and then use a semicolon to separate values; 6.6. use the report file name, URdata.csv. 7. for each reporting period to prepare a descriptive file (metadata) file in XML (Extensible Markup Language) format in accordance with the provisions of annex 12. For a descriptive file name, use the-URinfo.xml. 8. the Provisions of paragraphs 6 and 7 of the files included in the PGP files (one container two files – one corresponding report CSV and XML file) and encrypts using the public key of the Commission available to the data reporting system (http://dati.fktk.lv). 9. the PGP file, the credit institution shall send to the Commission according to Commission rules, regulations No 14.10.2008.146 "prepared statements electronically submit the legislative provisions" of the procedures laid down. If the amount of information does not allow you to use the data reporting system, credit institutions shall agree with the Commission on other PGP file submission procedures. 10. If the Commission finds that this provision of the information specified in paragraph 3 is submitted is incomplete or inaccurate, the information is communicated to the applicant. If the Commission has not indicated otherwise, corrected information, the credit institution shall be submitted not later than three working days after notification of the existence of the error from the Commission. In this case, the credit institution information, draw up and submit to the Commission the rules repeatedly 6.-9. in accordance with the procedure laid down in paragraph 1, including the data file the requested information in full, rather than just the corrected information. 11. a credit institution shall immediately notify the Commission of the information submitted, the perceived mistakes and failures and submit it to the Commission for this provision again 6-9 in accordance with the procedure laid down in point, data file, including the information requested in full, rather than just the corrected information.
IV. final question 12. a credit institution shall ensure that rules on the collection and provision of information to the Commission no later than the implementation 31.05.2017. Financial and capital market Commission President p. Birdie annex 1 financial and capital market Commission 29.11.2016. regulatory arrangements no 197 customer information-natural person

Nr. Field name field value field data or field must be filled in, or use the text qualifier ("") 1 the client's unique identifier internal identifier of the credit institution varchar (40) Yes Yes 2 date initiated business relations with the customer in accordance with the standard ISO 8601:2004 date (YYYY-MM-DD) 3 yes no date of termination of business relations with the customer in accordance with the standard ISO 8601:2004, blank if the business relationship not terminated date (YYYY-MM-DD) No No 4 customer name first name (s). A separator between words – a space or hyphen (-), nvarchar (200) Yes Yes 5 client surname (s). A separator between words – a space or hyphen (-), nvarchar (200) Yes Yes 6 customer's date of birth in accordance with the standard ISO 8601:2004 date (YYYY-MM-DD) Yes No 7 customer's country of residence in accordance with the standard LVS EN ISO 3166-1:2014. permanent place of residence of the customer address country code char (2) Yes No. 8 customer identification (people) code or equivalent code for the residents of the Republic of Latvia in accordance with Cabinet of Ministers Regulation No 98 on the population registration system (February 03, 2009). Blank if code is not varchar (40) No Yes 9 client identification number, identification document number of the document, which made the identification. If the credit institution has several customer identification documents, indicate each identification document number, separated by a semicolon (";") varchar (200) Yes Yes 10 customer identification document issuing country customer identification document issuing points under the standard LVS EN ISO 3166-1:2014. If the credit institution has several customer identification documents, and then specify the country codes 9. field in the order above, separated by a semicolon (";"), such as "EN RU varchar (8);" Yes No 11 Customer phone number according to the international e.123 standard. NI if the financial institution is not information varchar (40) No No 12 client email in accordance with the international e.123 standard. NI if the financial institution is not information varchar (40) No No 13 with credit related to personal status, the term "related person" is used according to the regulations of the Commission Regulation No 115 "with the authority of the persons exposure to limit the performance of the legislative provisions mentioned in paragraph" 4.2 term. If the customer is a person associated with the credit institution, then the field is "1", if not, then "0" boolean Yes No 14 customer tips at the end of the reporting period pursuant to the provisions of Commission regulations No. 234 ' ' customers advanced research institutions and legislative provisions of licensed payments and electronic money institutions ' ' requirements of paragraph 24-the point of paragraph 24:1-if the customer is a resident of the Republic of Latvia or to the European economic area resident natural person that month the planned or actual credit turnover not exceeding 15 000 euro; 2-If the client is a foreign person who is not a resident of the European economic area for the natural person whose monthly credit or actual planned turnover not exceeding 15 000 euro; 5-If the customer is a natural person whose monthly credit planned or actual turnover exceeds 15 000 euro; 6-If the customer is a natural person, which ranks as a major political party (PNP), the family member or a person closely related to the PNP char (1) Yes No 15 Related client groups (SKG) attribute to specify a unique identifier for the internal ROM. Blank if the client does not belong to any SKG varchar (40) No Yes URdata.csv sample file: "AB123456789",2010-10-24, "John", "Smith-,1970-10-14, a sapling" LV "12345", "AA12345 141070-" EN,12345678, janis.berzins@abcdef.lv .0 .1, "ABC123" "AC123456789",2010-10-26, "Vadim-Alexander", "Smirnov",1970-10-14, RU, BB123456,,12347896, "" RU "ABC456", 1, 5, 6, annex 2 financial and capital markets komisijas 29.11.2016. the normative regulation No. 197 customer information-legal person

Nr. Field name field value field data or field must be filled in, or use the text qualifier ("") 1 the client's unique identifier internal identifier of the credit institution-the code that automatically assigns a credit information system for varchar (40) Yes Yes 2 date initiated business relations with the customer in accordance with the standard ISO 8601:2004 date (YYYY-MM-DD) 3 yes no date of termination of business relations with the customer in accordance with the standard ISO 8601:2004, blank If the business relation is not a end date (YYYY-MM-DD) No No 4 customer name, the name of the legal person. A separator is a space between the words, nvarchar (200) Yes Yes 5 client registration number registration number of the legal person of the public register varchar (40) Yes Yes 6 client registration date in accordance with the standard ISO 8601:2004 date (YYYY-MM-DD) Yes No 7 client state of registration in accordance with the standard LVS EN ISO 3166-1:2014. legal addresses of the customer country code char (2) Yes No. 8 jurisdiction in which the customer in accordance with the standard LVS EN ISO 3166-1:2014 char (2) Yes No 9 jurisdiction the customer performs the basic economic activity in accordance with the standard LVS EN ISO 3166-1:2014 char (2) Yes No 10 jurisdiction with which the customer has significant economic ties in accordance with the standard LVS EN ISO 3166-1:2014 char (2) Yes No. 11 client economic activities NACE Description: European Parliament and Council Regulation (EC) No 1893/2006 specifies each activity, separated by a semicolon (";") varchar (59) Yes No 12 the customer's phone number in accordance with E. 123 international standard varchar (40) No No 13 client email in accordance with the international e.123 standard. NI if the financial institution is not information varchar (40) No No 14 with credit related to personal status, the term "related person" is used according to the regulations of the Commission Regulation No 115 "with the authority of the persons exposure to limit the performance of the legislative provisions mentioned in paragraph" 4.2 term. If the customer is a person associated with the credit institution, then the field is "1", if not, then "0" boolean Yes No 15 client type according to the regulations of the Commission Regulation No 234 ' ' customers advanced research institutions and legislative provisions of licensed payments and electronic money institutions ' ' requirements of paragraph 24-the point of paragraph 24:3-If the customer is a legal person or legal entity, who performs the operation based in the Republic of Latvia; 4-If the customer is a legal person or a legal entity whose basic activity is associated with the Republic of Latvia but who include public knowledge of the foreign group of companies of good repute; 6-If the customer is a legal person or a legal entity that is the real beneficiary is a natural person, which ranks as a major political party (PNP), the family member or a person closely related to the PNP; 7-if the customer is a legal person or a legal entity whose basic activity is associated with the Republic of Latvia and who is not part of the public knowledge of the foreign group of companies with a good reputation, as well as if the client is Laura correspondent (respondents); 8-if the customer is a company, which ranks as the shell company char (1) Yes No 16 associated client groups (SKG) attribute to specify a unique identifier for the internal ROM. Blank if the client does not belong to any SKG varchar (40) No Yes annex 3 financial and capital market Commission 29.11.2016. No. 197 regulations rules information about the customer's true beneficiary – physical person

Nr. Field name field value field data or field must be filled in, or use the text qualifier ("") 1 the client's unique identifier internal identifier of the credit institution-the code that automatically assigns a credit information system. You must specify a client whose PÅLÆG provides information about the unique identifier varchar (40) Yes Yes 2 the true beneficiaries of the client (PÅLÆG) unique identifier internal identifier of the credit institution-the code that automatically assigns a credit information system for varchar (40) Yes Yes 3 client PÅLÆG data registration date credit information system in accordance with standard ISO 8601:2004 date (YYYY-MM-DD) Yes No 4 client PÅLÆG property status end date in accordance with the standard ISO 8601:2004, blank If the customer has not changed data PÅLÆG (YYYY-MM-DD) No No 5 client PÅLÆG Word for Word (s). A separator between words – a space or hyphen (-), nvarchar (200) Yes Yes 6 client PÅLÆG surname (s). A separator between words – a space or hyphen (-), nvarchar (200) Yes Yes 7 client PÅLÆG (natural persons) date of birth in accordance with the standard ISO 8601:2004 date (YYYY-MM-DD) Yes No 8 client PÅLÆG country of residence in accordance with the standard LVS EN ISO 3166-1:2014.  The client type that at the end of the reporting period corresponds to 5, 6, 7 or 8. client type (paragraph 14 of annex 1 (physical person) or 2. paragraph 15 of the annex (legal person)), information indicates that the customer URobligāti.* type at the end of the reporting period correspond to 1, 2, 3, or 4. customer type (paragraph 14 of annex 1 (physical person) or 2. paragraph 15 of the annex (legal person)), information indicates a financial institution if it is a char (2) No No 9 client PÅLÆG identification (people) code or equivalent code for the residents of the Republic of Latvia in accordance with Cabinet of Ministers Regulation No 98 on the population registration system (February 03, 2009). Blank if code is not varchar (40) No Yes 10 customer identification document number PÅLÆG identification document number of the document, which made the identification. If the credit institution has several customer identification documents, indicate each identification document number, separated by a semicolon (";") varchar (200) Yes Yes 11 client identification document issuing country PÅLÆG identification document issuing points under the standard LVS EN ISO 3166-1:2014. If the financial institution has a number of identification documents, the country codes indicate 10. field in the order above, separated by a semicolon (";"), such as "EN RU varchar (8);" Yes No 12 with credit related to personal status, the term "related person" is used in accordance with the Commission's regulatory rule Nr. 115 "with the authority of the persons exposure limit" the enforcement regulations 4.2. the term referred to. If the customer is a person associated with the credit institution, then the field is "1", "0" if not, then yes no politically significant 13 boolean (PNP) the existence of status if the real beneficiary is the PNP, PNP or PNP family closely associated with a person, then use the "1", if not, then "0" boolean yes no * data without this information will not be accepted.
  4. the annex to the financial and capital market Commission 29.11.2016. No. 197 regulations rules information about the customer's true beneficiaries – legal person No. Field name field value field data or field must be filled in, or use the text qualifier ("") 1 the client's unique identifier internal identifier of the credit institution-the code that automatically assigns a credit information system. You must specify a client whose PÅLÆG provides information about the unique identifier varchar (40) Yes Yes 2 the true beneficiaries of the client (PÅLÆG) unique identifier internal identifier of the credit institution-the code that automatically assigns a credit information system for varchar (40) Yes Yes 3 client PÅLÆG data registration date credit information system in accordance with standard ISO 8601:2004 date (YYYY-MM-DD) Yes No 4 client PÅLÆG property status end date in accordance with the standard ISO 8601:2004, blank If the customer has not changed data PÅLÆG (YYYY-MM-DD) No No 5 client PÅLÆG name name of the legal person. A separator between words – a space or hyphen (-), nvarchar (200) Yes Yes 6 client (legal person) PÅLÆG registration date in accordance with the standard ISO 8601:2004 date (YYYY-MM-DD) Yes No 7 with credit related to personal status, the term "related person" is used in accordance with the Commission's regulatory rule Nr. 115 "with the authority of the persons exposure limit" the enforcement regulations 4.2. the term referred to. If the customer is a person associated with the credit institution, then the field is "1", if not, then "0" boolean yes no Annex 5 financial and capital market Commission 29.11.2016. No. 197 regulations rules information about the customer's representative

Nr. Field name field value field data or field must be filled in, or use the text qualifier ("") 1 the client's unique identifier internal identifier of the credit institution-the code that automatically assigns a credit information system. You must specify a client for which the trustee is given information, unique identifier varchar (40) Yes Yes 2 Customer data representative of the registration date of the credit information system in accordance with standard ISO 8601:2004 date (YYYY-MM-DD) Yes No 3 client representatives represent the end date in accordance with the standard ISO 8601:2004 date (YYYY-MM-DD) No No 4 client unique identifier of a representative of the credit institution's internal identifier-the code that automatically assigns a credit information system for varchar (40) Yes Yes 5 client on behalf of the representative (s). A separator between words – a space or hyphen (-), nvarchar (200) Yes Yes 6 client surname of the representative (s). A separator between words – a space or hyphen (-), nvarchar (200) Yes Yes 7 client date of birth of the representative in accordance with the standard ISO 8601:2004 date (YYYY-MM-DD) Yes No 8 customer's country of residence of the representative in accordance with the standard LVS EN ISO 3166-1:2014. customer representative permanent residence address country code char (2) Yes No 9 Customer Representative identification (people) code or equivalent code for the residents of the Republic of Latvia in accordance with Cabinet of Ministers Regulation No 98 on the population registration system (February 03, 2009). Blank if code is not varchar (40) No Yes 10 customer identification document of a representative number of the identification document number of the document, which made the identification. If the credit institution has several representatives of the client identification documents, indicate each identification document number, separated by a semicolon (";") varchar (200) Yes Yes 11 customer representative's identification document issuing country representative of the client identification document issuing points under the standard LVS EN ISO 3166-1:2014. If the credit institution has several representatives of the client identification documents, the country codes indicate 10. field in the order above, separated by a semicolon (";"), such as "EN RU varchar (8);" Yes No 12 with credit related to personal status, the term "related person" is used according to the regulations of the Commission Regulation No 115 "with the authority of the persons exposure to limit the performance of the legislative provisions mentioned in paragraph" 4.2 term. If the customer is a person associated with the credit institution, then the field is "1", "0" if not, then yes no politically significant 13 boolean (PNP) the presence status When the customer's authorised person is PNP, PNP or PNP family closely associated with a person, then use the "1", if not, then "0" boolean no no Annex 6 financial and capital market Commission 29.11.2016. No. 197 regulations rules information about the customer's non-cash transactions

Nr. Field name field value field data or field must be filled in, or use the text qualifier ("") 1 the client's unique identifier internal identifier of the credit institution-the code that automatically assigns a credit information system for varchar (40) Yes Yes 2 IBAN account number of the customer in accordance with the standard ISO 13616-1:2007 varchar (34) Yes No 3 unique payment ID payment identification varchar (40) Yes Yes 4 direction If the incoming payment in the customer's account then use the "K" from the customer's account if the outgoing payment, use the "D" char (1) Yes No 5 payment value date in accordance with the standard ISO 8601:2004 date (YYYY-MM-DD) Yes No 6 payment amount in accordance with the standard ISO 80000-1:2009 decimal (20.2) Yes No 7 payment currency under ISO 4217:2015 char (3) Yes No 8 payment of the equivalent of the euro in accordance with the standard ISO 80000-1:2009. The exchange rate at the date of posting for the decimal (20.2) Yes No 9 the purpose of the payment transaction by the attached comment. A separator between words-space nvarchar (512) No Yes 10 Payments partner (the beneficiary or payer's) name, or the name of the parties involved to the name. A separator is a space between the words, nvarchar (200) Yes Yes 11 payment partner (the beneficiary or the payer) or the country of residence of the registration code in accordance with the standard LVS EN ISO 3166-1:2014 char (2) No No 12 payment partner (the beneficiary or the payer) address address, giving the city, street, House, apartment No., index or other information if the address it contains nvarchar (200) No Yes 13 payment partner (receiving or paying) account number IBAN in accordance with standard ISO 13616-1:2007, or other account number varchar (40) Yes No 14 payment partner (the beneficiary or the payer) bank name NA-SEPA payments nvarchar (200) No Yes 15 payment partner (the beneficiary or the payer) or the bank's BIC bank code BIC code is used in accordance with the standard ISO 9362:2014. Bank code specifies, for example, AT 5! n Austrian Bankleitzahl; AU 6! n Australian Bank State Branch (BSB) code; BL 8! n German Bankleitzahl; CC 9! n Canadian Payments Association payment Routing Number; CH 6! n chips Universal Identifier; CP 4! n chips Participant Identifier; 8. Spanish EU 9n Domestics Interbanking code; FW 9 n Fedwire Routing Numbers!; GR 7! n HEBIC (Hellenic Bank Identification Code); HK 3! n the Bank code of Hong Kong; IE 6! n Irish National Clearing code (NSC); In 11 Indian Financial System Code! c (IFSC); IT 10! n Italian Domestic Identification Code; NZ New Zealand 6! n National Clearing code; PL 8! n Polish National Clearing code (IIP); PT 8! n Portuguese National Clearing code; RT Pay by Real time gross settlement; RU Russian Central Bank 9! n Identification Code; SC 6! n the UK Domestics sort code; SW 3rd. 5n Swiss Clearing code (BC Code); SW 6! n Swiss Clearing code (SIC code); NE 6! South African National Clearing code n varchar (40) Yes No 16 payment partner (the beneficiary or the payer) of the country of registration of the bank in accordance with the standard LVS EN ISO 3166-1:2014 char (2) Yes No 17 involved in offset Payment bank name NA-internal payments nvarchar (200) No Yes 18 involved in Payments offset the bank's BIC code or bank code BIC code is used in accordance with the standard ISO 9362:2014. Bank code indicates for example: AT 7! n Austrian Bankleitzahl; AU 6! n Australian Bank State Branch (BSB) code; BL 8! n German Bankleitzahl; CC 9! n Canadian Payments Association payment Routing Number; CH 6! n chips Universal Identifier; CP 4! n chips Participant Identifier; 8. Spanish EU 9n Domestics Interbanking code; FW 9 n Fedwire Routing Numbers!; GR 7! n HEBIC (Hellenic Bank Identification Code); HK 3! n the Bank code of Hong Kong; IE 6! n Irish National Clearing code (NSC); In 11 Indian Financial System Code! c (IFSC); IT 10! n Italian Domestic Identification Code; NZ New Zealand 6! n National Clearing code; PL 8! n Polish National Clearing code (IIP); PT 8! n Portuguese National Clearing code; RT Pay by Real time gross settlement; RU Russian Central Bank 9! n Identification Code; SC 6! n the UK Domestics sort code; SW 3rd. 5n Swiss Clearing code (BC Code); SW 6! n Swiss Clearing code (SIC code); NE 6! South African National Clearing code n. NA internal payments using varchar (40) No No 19 in the payment to offset the bank undertake country of registration in accordance with the standard LVS EN ISO 3166-1:2014 char (2) no no Annex 7 financial and capital market Commission 29.11.2016. regulatory arrangements no 197, information about the customer's account turnover

Nr. Field name field value field data or field must be filled in, or use the text qualifier ("") 1 the client's unique identifier internal identifier of the credit institution-the code that automatically assigns a credit information system for varchar (40) Yes Yes 2 account number of the customer in accordance with the standard ISO 13616-1:2007 varchar (34) Yes No 3 year and month in accordance with the standard ISO 8601:2004 date (YYYY-MM) Yes No 4 account opening balance-the equivalent of the EURO currency in accordance with the standard ISO 80000-1:2009. Exchange rate at the date of posting for the decimal (20.2) Yes No. 5 account debit turnover-the equivalent of the EURO currency in accordance with the standard ISO 80000-1:2009. Exchange rate at the date of posting for the decimal (20.2) Yes No 6 account credit turnover-the equivalent of the EURO currency in accordance with the standard ISO 80000-1:2009. Exchange rate at the date of posting for the decimal (20.2) Yes No 7 Account ending balance-the equivalent of the EURO currency in accordance with the standard ISO 80000-1:2009. Exchange rate at the date of posting for the decimal (20.2) Yes No 8 account currency in accordance with the standard ISO 4217:2015. Specify a name for the currency of each separate line chart (3) Yes No 9 account beginning balance in the currency of the account concerned in accordance with the standard ISO 80000-1:2009. Specify the balance in any currency on a separate line in decimal (20.2) Yes No 10 Account ending balance in the currency of the account in accordance with the standard ISO 80000-1:2009. Specify the balance in any currency on a separate line in decimal (20.2) Yes No 11 account debit turnover in the currency of the account in accordance with the standard ISO 80000-1:2009. Specify the balance in any currency on a separate line in decimal (20.2) Yes No 12 account credit turnover on the relevant account currency in accordance with the standard ISO 80000-1:2009. Specify the balance in any currency on a separate line in decimal (20.2) Yes No Annex 8 financial and capital market Commission 29.11.2016. regulatory arrangements no 197 requests information about a correspondent

Nr. Field name field value field data or field must be filled in, or use the text qualifier ("") 1 offset bank BIC/bank code (the sender), the BIC code is used in accordance with the standard ISO 9362:2014.  Bank code points, for example: AT 7! n Austrian Bankleitzahl; AU 6! n Australian Bank State Branch (BSB) code; BL 8! n German Bankleitzahl; CC 9! n Canadian Payments Association payment Routing Number; CH 6! n chips Universal Identifier; CP 4! n chips Participant Identifier; 8. Spanish EU 9n Domestics Interbanking code; FW 9 n Fedwire Routing Numbers!; GR 7! n HEBIC (Hellenic Bank Identification Code); HK 3! n the Bank code of Hong Kong; IE 6! n Irish National Clearing code (NSC); In 11 Indian Financial System Code! c (IFSC); IT 10! n Italian Domestic Identification Code; NZ New Zealand 6! n National Clearing code; PL 8! n Polish National Clearing code (IIP); PT 8! n Portuguese National Clearing code; RT Pay by Real time gross settlement; RU Russian Central Bank 9! n Identification Code; SC 6! n the UK Domestics sort code; SW 3rd. 5n Swiss Clearing code (BC Code); SW 6! n Swiss Clearing code (SIC code); NE 6! South African National Clearing code n varchar (40) Yes No 2 offset bank name nvarchar (200) Yes Yes 3 date of the request, in accordance with the standard ISO 8601:2004 date (YYYY-MM-DD) Yes No 4 client unique identifier internal identifier of the credit institution-the code that automatically assigns a credit information system for varchar (40) Yes Yes 5 payment ID payment identification of the Entity. NA if the request does not apply to client transactions varchar (20) Yes Yes 6 payment value date in accordance with the standard ISO 8601:2004 NA if the request does not apply to the customer's business date (YYYY-MM-DD) Yes No 7 payment amount in accordance with the standard ISO 80000-1:2009. NA if the request does not apply to client transactions decimal (20.2) Yes No 8 payment currency under ISO 4217:2015. NA if the request does not apply to the transactions of the client char (3) Yes No 9 payment purpose the purpose of the payment. NA if the request does not apply to client transactions nvarchar (512) Yes Yes 10 Payments partner (the beneficiary or payer's) name, or the name of the parties involved to the name. A separator between the word-spacing. NA if the request does not apply to client transactions nvarchar (200) Yes Yes 11 payment partner (the beneficiary or the payer) or the country of residence of the registration code in accordance with the standard LVS EN ISO 3166-1:2014 NA if the request does not apply to the transactions of the client char (2) Yes No 12 payment partner (receiving or paying) account number IBAN in accordance with standard ISO 13616-1:2007. NA if the request does not apply to client transactions varchar (40) Yes No 13 payment partner (the beneficiary or the payer) name of the bank NA, if the request does not apply to client transactions nvarchar (200) Yes Yes 14 payment partner (the beneficiary or the payer) or the bank's BIC bank code BIC code is used in accordance with the standard ISO 9362:2014.  Bank code points, for example: AT 7! n Austrian Bankleitzahl; AU 6! n Australian Bank State Branch (BSB) code; BL 8! n German Bankleitzahl; CC 9! n Canadian Payments Association payment Routing Number; CH 6! n chips Universal Identifier; CP 4! n chips Participant Identifier; 8. Spanish EU 9n Domestics Interbanking code; FW 9 n Fedwire Routing Numbers!; GR 7! n HEBIC (Hellenic Bank Identification Code); HK 3! n the Bank code of Hong Kong; IE 6! n Irish National Clearing code (NSC); In 11 Indian Financial System Code! c (IFSC); IT 10! n Italian Domestic Identification Code; NZ New Zealand 6! n National Clearing code; PL 8! n Polish National Clearing code (IIP); PT 8! n Portuguese National Clearing code; RT Pay by Real time gross settlement; RU Russian Central Bank 9! n Identification Code; SC 6! n the UK Domestics sort code; SW 3rd. 5n Swiss Clearing code (BC Code); SW 6! n Swiss Clearing code (SIC code); NE 6! South African National Clearing code n.   NA if the request does not apply to client transactions varchar (40) Yes No 15 payment partner (the beneficiary or the payer) of the country of registration of the bank in accordance with the standard LVS EN ISO 3166-1:2014 NA if the request does not apply to the transactions of the client char (2) Yes No Annex 9 financial and capital market Commission 29.11.2016. regulatory arrangements no 197, information about the trust and fiduciary transactions

Nr. Field name field value field data or field must be filled in, or use the text qualifier ("") 1 the client (our employer) unique identifier internal identifier of the credit institution-the code that automatically assigns a credit information system for varchar (40) Yes Yes 2 transaction (trust insertion) date in accordance with the standard ISO 8601:2004 date (YYYY-MM-DD) Yes No 3 trust transaction identifier unique payment ID varchar (40) Yes No 4 trust transaction amount in accordance with the standard ISO 80000-1:2009 decimal (20.2) Yes No 5 trust transaction currency in accordance with the ISO 4217:2015 char (3) Yes No 6 our interest rate in accordance with standard ISO 80000-1:2009 decimal (4) Yes No 7 date of repayment of the Trust in accordance with the terms of the transaction in accordance with the standard ISO 8601:2004 date (YYYY-MM-DD) Yes No 8, the actual date of repayment of the trust in accordance with standard ISO 8601:2004, empty if not repaid the trust date (YYYY-MM-DD) No No 9 Clients (borrowers) unique identifier internal identifier-a credit institution code , which automatically assigns a credit information system for varchar (40) Yes Yes 10 transaction (credit issue) date in accordance with the standard ISO 8601:2004, NA-in cases where the trust is not used for credit liabilities date (YYYY-MM-DD) Yes No 11 credit transaction identifier Unique identifier of payment. NA-in cases where the trust is not used for credit liabilities varchar (40) Yes Yes 12 credit the amount of the transaction in accordance with the standard ISO 80000-1:2009. NA-in cases where the trust is not used for credit liabilities decimal (20.2) Yes No 13 credit transaction currency in accordance with the standard ISO 4217:2015. NA-in cases where the trust is not used for credit liabilities char (3) Yes No 14 credit interest rate in accordance with standard ISO 80000-1:2009. NA-cases When a trust is used for credit liabilities decimal (4) Yes No 15 maturity date of credit under the terms of the transaction in accordance with the standard ISO 8601:2004 date (YYYY-MM-DD) Yes No 16 the actual loan repayment date in accordance with the standard ISO 8601:2004, blank if credit is not deleted date (YYYY-MM-DD) No No 10. Annex financial and capital market Commission 29.11.2016. regulatory arrangements no 197, information about the customer's cash turnover No. Field name field value field data or field must be filled in, or use the text qualifier ("") 1 the client's unique identifier internal identifier of the credit institution-the code that automatically assigns a credit information system for varchar (40) Yes Yes 2 IBAN account number of the customer in accordance with the standard ISO 13616-1:2007 IBAN Yes No 3 year and month in accordance with the standard ISO 8601:2004 date (YYYY-MM) Yes No 4 cash transaction debit turnover in the currency equivalent of EUR according to the standard ISO 80000-1:2009. The exchange rate at the date of posting for the decimal (20.2) Yes No 5 cash in the currency of the transaction the credit equivalent of EUR turnover in accordance with standard ISO 80000-1:2009. The exchange rate at the date of posting for the decimal (20.2) Yes No 6 cash transaction currency in accordance with the standard ISO 4217:2015 char (3) Yes No 7 cash debit turnover in the currency in question in accordance with the standard ISO 80000-1:2009. Specify the turnover in each separate line in decimal currency (20.2) Yes No 8 cash credit activity in the relevant currency in accordance with the standard ISO 80000-1:2009. Specify the turnover in each separate line in decimal currency (20.2) Yes No annex 11 of the financial and capital market Commission 29.11.2016. regulatory arrangements no 197 information about offset (lor) account

Nr. Field name field value field data or field must be filled in, or use the text qualifier (the) (1) a credit institution (bank lor) name separator between words – a space or hyphen (-), nvarchar (200) Yes Yes 2 credit (Laura bank) of the State of registration in accordance with the standard LVS EN ISO 3166-1:2014 char (2) Yes No 3 credit institutions (bank lor) BIC/bank code BIC code is used in accordance with the standard ISO 9362:2014.  Bank code points, for example: AT 7! n Austrian Bankleitzahl; AU 6! n Australian Bank State Branch (BSB) code; BL 8! n German Bankleitzahl; CC 9! n Canadian Payments Association payment Routing Number; CH 6! n chips Universal Identifier; CP 4! n chips Participant Identifier; 8. Spanish EU 9n Domestics Interbanking code; FW 9 n Fedwire Routing Numbers!; GR 7! n HEBIC (Hellenic Bank Identification Code); HK 3! n the Bank code of Hong Kong; IE 6! n Irish National Clearing code (NSC); In 11 Indian Financial System Code! c (IFSC); IT 10! n Italian Domestic Identification Code; NZ New Zealand 6! n National Clearing code; PL 8! n Polish National Clearing code (IIP); PT 8! n Portuguese National Clearing code; RT Pay by Real time gross settlement; RU Russian Central Bank 9! n Identification Code; SC 6! n the UK Domestics sort code; SW 3rd. 5n Swiss Clearing code (BC Code); SW 6! n Swiss Clearing code (SIC code); NE 6! South African National Clearing code n varchar (40) Yes No 4 Lor the IBAN account number according to standard ISO 13616-1:2007 varchar (34) Yes No 5 year and month in accordance with the standard ISO 8601:2004 date (YYYY-MM) Yes No 6 Laura account opening balance in the currency equivalent of EUR according to the standard ISO 80000-1:2009. The exchange rate at the date of posting for the decimal (20.2) Yes No 7 Lor account debit turnover in the currency equivalent of EUR according to the standard ISO 80000-1:2009. The exchange rate at the date of posting for the decimal (20.2) Yes No 8 Laura account credit turnover in the currency equivalent of EUR according to the standard ISO 80000-1:2009. Exchange rate at the date of posting for the decimal (20.2) Yes No 9 Lor account ending balance in the currency equivalent of EUR according to the standard ISO 80000-1:2009. Exchange rate at the date of posting for the decimal (20.2) Yes No 10 Laura the account currency in accordance with the standard ISO 4217:2015. Specify a name for the currency of each separate line chart (3) Yes No 11 Laura account beginning balance in the currency of the account concerned in accordance with standard ISO 80000-1:2009. Specify the balance in any currency on a separate line in decimal (20.2) Yes No 12 Lor the account debit turnover in the currency of the account in accordance with the standard ISO 80000-1:2009. Specify the balance in any currency on a separate line in the decimal (20.2) Yes No 13 Lor account credit turnover on the relevant account currency in accordance with the standard ISO 80000-1:2009. Specify the balance in each currency separate line decimal (20.2) Yes No 14 Laura the ending balance on the account in the respective currency of the account in accordance with the standard ISO 80000-1:2009. Specify the balance in each currency decimal (separate line 20.2) Yes No 12. Annex financial and capital market Commission 29.11.2016. regulatory arrangements no 197 1. Descriptive (metadata) of the content requirements for field name field data format (*) field value the name of the Element 1. credit institutions LEI code string (20) in accordance with standard ISO 17442:2012 2. Reporting period start date date (YYYY-MM-DD) in accordance with standard ISO 8601:2004. Specify the report period the first month of the first day of the 3. The reporting period end date for a date (YYYY-MM-DD) in accordance with standard ISO 8601:2004. Specifies the most recent reporting period the last day of the month 4. identification Chart Report (2) the provisions of the annex indicates that the data file has been prepared URdata.csv, number (01-11) 5th data types char (1) if the report includes all existing financial institution during the period in question, the report data (e.g. for all customers), then "F". If the report is limited to credit institutions include on-hand during the period in question, the report data (e.g. for individual clients in accordance with the Commission's request), then "L" 6. URData.csv file creation time stamp DateTime (YYYY-MM-DDThh: mm: ssTZD) in accordance with standard ISO 8601:2004. Specifies the URdata.csv file creation time stamp 2. XML file sample 648500AJIJ8SBAUBWN19 2017 2017-01-01-04-30 04 L 2001-12-17T09:30:47