Handelsbanken. Internetbank Data Exchange Standard (FiDAViSta)

Transcription

1 Handelsbanken Data Exchange Standard (FiDAViSta) January 2014

2 Table of contents 1. Introduction Groups and types of fields Payment file Payment status file Account statement file (15)

3 1. Introduction Data exchange standard in Svenska Handelsbanken Latvia (hereinafter referred to as the ) is based on Financial Data Exchange Unified Standard (FiDAVISta) version 1.2 created by Association of Latvian Commercial Banks ( ore information about this standard you can find in web page of Association of Commercial Banks of Latvia: FiDAViSta is based on data format- XL. FiDAViSta is compatible with majority of financial management systems used in Latvia ensuring possibility to import payment orders created in company s accounting software programm into the in order to reduce time needed for payment creation and avoiding mistakes. Payment status file can be used to mark executed payments and/or to identify erroneous payments in company s accounting software programm. Using account statement in FiDAViSta file form is possible to make automatic bookkeeping entries in programm in order to facilitate bookkeeper s daily work. Data import to is made with Payment file. Data export from is made with Payment status file and Account statement file. Description of data exchange files you can find in document chapters Payment file, Payment status file and Account statement file. Fields indicated as are mandatory, fields indicated as O are optional in data exchange files. Fields (values) indicated additionally as (A) will not be taken into consideration at payment processing (accepted but not acted upon). Types of fields used in data exchange files are described in chapter Groups and types of fields. The document are also contains information about conditions and differences applied in the. 3 (15)

4 2. Groups and types of fields FiDAViSta file can consist of several groups of fields, these groups are united under one root section - <FIDAVISTA>. Groups of fields: Header group of header contains information about file preparing institution and time. Payment - group of payment contains information about payments (SEPA, cross-border etc.). PmtStat - group of payment status contains information about statuses of payments based on before defined ID-s. Statement - group of account statement contains information about review or statement for bank's accounts. Types of fields: Type Lenght Allowed symbols Description in ax xs:string 0 XL standard type for unicode texts. xs:date XL standard type for date. Format: YYYY- -DD. Bank Code Type 0-9 A-Z a-z \s/\-\?:().,'\+\n\r Derived from SwiftString. Attribute CodeType added (type SwiftString). Attribute is mandatory. ExtensionType 0 Provided for elements that are not included in standard. AccountType A-Z a-z \s/\-\?:().,'\+\n\r Derived from SwiftString. Type has limit of length. AccountOType A-Z a-z \s/\-\?:().,'\+\n\r Derived from SwiftString. Type has limit of length. AmountType Derived from xs:decimal. Limit of length. 12 symbols (including two decimal symbols separated with dot). CurrencyType 3 3 A-Z Derived from xs:string EksStringTyp 0-9 A-Z a-z ā-ž Ā-Ž \s/\- Derived from xs:string.. \?:().,'\+\n\r Restricted symbols that are not allowed in Latvian Bank Clearing System. Small Latvian and Latin letters are allowed. LegalIDType A-Z a-z \s/\-\?:().,'\+\n\r Derived from SwiftString. Type has limit of length. SWIFTType 8 11 A-Z 0-9 Used for SWIFT codes according to the SWIFT standard. SwiftStringType 0-9 A-Z a-z \s/\-\?:().,'\+\n\r Derived from xs:string. Allowed symbols that comply with X cluster of symbols of SWIFT standard except.{. and.}..small Latin letters are allowed. 4 (15)

5 3. Payment file The payment file is XL format file which is generated and exported from the bookkeeping s system in order to import the payment orders into the. The maximum size of the file is limited in the Bank with 1000 payments and 500KB. Payment file ( mandatory; O optional; A- Accepted but not acted upon): Tag Lenght Type O/ Description in ax <Header> <Timestamp> xs:string File preparing time in format YYYYDDHHSSsss <From> 0 70 xs:string O (A) File sender <Extension> ExtensionType O (A) Field deployment of additional elements </Header> <Payment> <ExtId> 0 10 SwiftStringType O Unique ID of payment in bookkeeping system. By this ID will possible in Payment status file and Statement file to find bookings related with exported payment. <DocNo> 1 10 SwiftStringType Payment/document number issued by customer in bookkeeping system. <RegDate> xs:date Payment registration date in bookkeeping system in format YYYY--DD. <TaxPmtFlg> 1 1 xs:string Default: N O (A) Indication of payment as budget or normal payment Y- tax payment N- "normal" payment <Ccy> 3 3 CurrencyType Payment currency <PmtInfo> EksStringType Payment details <StrdRef> 0 35 SwiftStringType O Beneficiary s assigned payment identificator. Used only in SEPA payments. It can not be filled in together fields <StrdRef> and <PmtInfo>. If field <StrdRef> is filled in, then field s <PmtInfo>. content is ignored. In SEPA payments this field corresponds ISO field <RmtInf> <Strd><CdtrRefInf><Ref>. <BankInfo> xs:string O (A) Information for bank <PayLegalId> 0 20 LegalIDType O Payer s registration number or tax payer s code or ID <PayAccNo> 1 34 AccountType Payer s IBAN account number <PaySubAccNo> 0 34 AccountOType O (A) Payer s subaccount number <DebitCcy> 3 3 CurrencyType O Debiting currency (cover currency). If this field is not filled in, bank considers by default value of this field as following: Single currency account account currency. <BenSet> Information about Beneficiary <BenExtId> 0 5 SwiftStringType O (A) Unique ID of Beneficiary inside of current payment. Recommended to use in case of ass payments. This field can be used for identification of payment in other files (Payment status file and Statement file) <EndToEndId> 0 35 SwiftStringType O Payers assigned payment identificator which is represented to beneficiary. This field is used in SEPA payments ( it corresponds to ISO field <EndtoEndId>). In other payments the value of this field is ignored. <Priority> 1 1 xs:string.n./.u./.x. Default =.N. <Comm> 3 3 xs:string.our./.sha. Default =.SHA. Priority of payment: N- Normal, U- Urgent, X- Express. Default value: N Type of commission: OUR- Payer, BEN-Beneficiary, SHA-. Shared. Default value: SHA <Amt> 1 12 AmountType Sum of payment. Decimals are separated with dot... <BenAccNo> 0 34 AccountOType Beneficiary s account number <BenSubAccNo> 0 34 AccountOType O (A) Beneficiary s subaccount number <BenAccIbanFlg> 0 1 xs:string.y. /.N. Default =.N. O Indication of IBAN format for Beneficiary s account Y - bank s system must verify control sum of account number according to the international IBAN standard. 5 (15)

6 <BenName> EksStringType Beneficiary s name <BenLegalId> 0 35 LegalIDType O Beneficiary s registration number or tax payer s code or ID Contains non-mandatory attibutes: 1) PersType which may contain defined values: PRIV- if beneficiary is private person ORG- if beneficiary is legal person 2) IdType, in this field can be used only codes set by ISO 20022: ExternalPersonIdentification1Code-if beneficiary is private person (e.g. NIDN, DRLC) ExternalOrganisationIdentification1Code-if beneficiary is legal person (e.g. TXID) Those Attributes are used only in SEPA payments, in other payments bank ignores those attribute content. In SEPA payment if field <BenLegalId> is filled then is mandatory required to fill in attribute <PersType>. If in SEPA payment attribute <PersType>. is not provided then bank ignores the content of field <BenLegalId>. <BenAddress> 0 70 EksStringType O Beneficiary s address <BenCountry> 2 2 CountryType Country code where Beneficiary is registered. For example, LV, EE, US. ISO3166 <BBName> 0 35 EksStringType O Name of Beneficiary bank <BBAddress> 0 70 EksStringType O Address of Beneficiary bank <BBSwift> 8 11 SWIFTType O SWIFT code or Latvian Bank.s BIC code of Beneficiary bank <BBCode> 0 66 BankCodeType O (A) Code of Beneficiary bank <CBAcc> 0 34 AccountOType O (A) Account of Beneficiary bank in Intermediary bank <CBName> 0 35 EksStringType O (A) Name of Intermediary bank <CBSwift> 8 11 SWIFTType O SWIFT code of Intermediary bank <CBCode> 0 66 BankCodeType O (A) Code of Intermediary bank <BudgCode> 0 10 SwiftStringType O (A) Budget income code <AmkSet> O External payment code of payment <Opc> 1 3 xs:string External payment code; digits only [09] <Amt> 1 12 AmountType O (A) External payment sum; Decimals must be separated by Point. </AmkSet> <Extension> ExtensionType O (A) Field deployment of additional elements </BenSet> <Extension> ExtensionType O (A) Field deployment of additional elements </Payment> Additional conditions for values of fields: Tag Name of field Condition <Timestamp> File preparing time Field is mandatory as it s used to avoid duplicate import of file. <DocNo> Payment/document number in bookkeeping system Payment/document number issued by customer in bookkeeping system can not exceed length of 5 symbols. <RegDate> Payment registration date in bookkeeping system Payment registration date in bookkeeping s system can not to be earlier than 14 calendar days in the past or above 30 calendar days in the future than current date. If payment date is up to 14 days in past, then by payment import (signing) date is replaced with current date. If payment date is up to 30 days in future, then date is checked if its Bank s business day. If it s not, then assigned is next Bank s business date. <Ccy> Payment currency Payment currency can be different as account currency, in that case currency exchange will be done. <PmtInfo> Payment details Field is mandatory <DebitCcy> Debiting currency This field is considered only for cross-border payments. If payment is made from single currency account, then debiting currency has to match with account currency. <Comm> Type of commission Bank processes only OUR and SHA. BEN will be always replaced with SHA. In case payment order is in any EEA member country s currency and executed in any EEA member country fee type should apply as following: 6 (15)

7 <BenAccNo> <BenName> - Shared (SHA)- payment does not involve currency conversion. If the Client in Payment order has stated fee type Payer (OUR), then by Payment execution Bank changes it to Shared (SHA); - Payer (OUR)- payment involves currency conversion and furthermore entire payment amount is converted. Beneficiary s account number Fields are mandatory. In case of intrabank payment beneficiary s name Beneficiary s name should match with correspondent name of account registered in Banks system. <BenAccIbanFlg> Indication of IBAN format for Beneficiary s account <BBSwift>* SWIFT code or Latvian Bank.s BIC code of Beneficiary bank If Y, then IBAN of the beneficiary and the BIC/SWIFT code of the beneficiary bank should be valid and refer to the same bank. If N, then payment is accepted with beneficiary account number instead of IBAN and beneficiary bank s name and address instead of BIC/SWIFT. In case of domestic payment beneficiary bank s BIC/SWIFT code will be taken from IBAN account (even if client has provided others bank s BIC/SWIFT code). <BBName> * Name of Beneficiary bank Data of beneficiary bank are taken from BIC directory according to BIC code provided in file (<BBSwift>). If <BBSwift> is not provided, Bank will <BBAddress> * Address of Beneficiary bank process given data- beneficiary s bank name and address. <CBName> Name of Intermediary bank If in file <CBSwift>, is provided, then <CBName> will be automatically taken from BIC directory. <CBSwift> SWIFT code of Intermediary bank *Possible options in file: <BBSwift> <BBSwift>+<BBAddress> <BBSwift>+<BBName> <BBName>+<BBAddress> <BBName>+<BBSwift>+<BBAddress> Allowed letters and characters in SEPA payments: Aa, Āā, Bb, Cc, Čč, Dd, Ee, Ēē, Ff, Gg, Ģģ, Hh, Ii, Īī, Jj, Kk, Ķķ, Ll, Ļļ, m, Nn, Ņņ, Oo, Pp, Rr, Ss, Šš, Tt, Uu, Ūū, Vv, Zz, Žž / -? : ( )., ' + space Allowed letters and characters in other payments: Aa, Bb, Cc, Dd, Ee, Ff, Gg, Hh, Ii, Jj, Kk, Ll, m, Nn, Oo, Pp, Rr, Ss, Tt, Uu, Vv, Zz / -? : ( )., ' + space 7 (15)

8 Example of payment file: <?xml version="1.0" encoding="utf-8"?> - <FIDAVISTA xmlns=" - <Header> <Timestamp> </Timestamp> <From>Customer AABBCCDD</From> </Header> - <Payment> <ExtId> </ExtId> <DocNo>1</DocNo> <RegDate> </RegDate> <TaxPmtFlg>N</TaxPmtFlg> <Ccy>EUR</Ccy> <PmtInfo>Rek.nr </PmtInfo> <PayLegalId> </PayLegalId> <PayAccNo>LV02HAND </PayAccNo> <DebitCcy> EUR</DebitCcy> - <BenSet> <BenExtId>321</BenExtId> <Priority>N</Priority> <Comm>SHA</Comm> <Amt> </Amt> <BenAccNo>LV38LPNS </BenAccNo> <BenName>Ben name 1</BenName> <BenLegalId IdType="TXID"PersType="ORG"> </BenLegalId> <BenAddress>Riga</BenAddress> <BenCountry>LV</BenCountry> <BBName>JSC LATVIAN POST</BBName> <BBSwift>LPNSLV21</BBSwift> - <AmkSet> <Opc>010</Opc> </AmkSet> </BenSet> </Payment> - <Payment> <ExtId> </ExtId> <DocNo>7</DocNo> <RegDate> </RegDate> <TaxPmtFlg>N</TaxPmtFlg> <Ccy>SEK</Ccy> <PmtInfo>Inv. NO dd </PmtInfo> <PayLegalId> </PayLegalId> <PayAccNo>LV11HAND </PayAccNo> <DebitCcy> SEK </DebitCcy> - <BenSet> <BenExtId>327</BenExtId> <Priority>U</Priority> <Comm>SHA</Comm> <Amt> </Amt> <BenAccNo>SE </BenAccNo> <BenName>Ribe ynthandel JSC</BenName> <BenLegalId> </BenLegalId> <BenAddress>Dronningens gt. 46, N-7012 Stockholm</BenAddress> <BenCountry>SE</BenCountry> <BBName>SVENSKA HANDELSBANKEN</BBName> <BBAddress>11, BLASIEHOLSTORG, STOCKHOL</BBAddress> <BBSwift>HANDSESS</BBSwift> - <AmkSet> <Opc>100</Opc> </AmkSet> </BenSet> </Payment> </FIDAVISTA> 8 (15)

9 4. Payment status file The status file is XL format file which is generated and exported from the in order to import the payment orders statuses into customer s bookkeeping system. The status file is a response to the specific imported payment file. The maximum size of the file is limited with 1000 payments. Payment status file ( mandatory; O optional; A- Accepted but not acted upon): Tag Lenght Type O/ Description in ax <Header> <Timestamp> xs:string File preparing time in format YYYYDDHHSSsss <From> 0 70 xs:string Name of preparer </Header> <PmtStat> <ExtId> 0 10 SwiftStringType O Reference to unique ID of payment from Payment file <BenExtId> 0 5 SwiftStringType O(A) Reference to unique ID of beneficiary from Payment file <BankRef> 0 25 xs:string Bank s reference number <DocNo> 1 10 xs:string Payment/ document number <StatCode> 1 1 xs:string Payment status codes: E Executed; R- Rejected; P- Processed in a bank; O-Other. <InfoToCustomer> 0 70 xs:string Description of payment status or error <BookDate> xs:date Payment booking date in bank s system in format YYYY- -DD. <RegDate> xs:date O(A) Payment registration date in format YYYY--DD. </PmtStat> Additional conditions for values of fields: Tag Name of field Condition <BookDate> Payment booking date in the bank s system Provided is date when payment is executed (amount written off from account), rejected or other status in accordance with payment statuses described below. Payments which execution date is in future will be executed under condition that on account are sufficient funds. <StatCode> Payment status code and <InfoToCusto <Stat <InfoToCustomer> Description mer> Code> O Importēts, nav parakstīts. Imported not Imported but not sent to the Bank for execution (signed) signed O Nākotnes izpildes datums. Future Sent to the Bank for execution, waiting future value date execution date O Gaida līdzekļus. Waiting for cover Payment will be executed when sufficient funds P Rezervēts. Reserved Amount is reserved in the account but not yet debited E Izpildīts. Executed Amount is debited (written off) from account R Klienta atcelts. Cancelled by customer Cancelled by customer in R Atcelts pēc klienta pieprasījuma. Cancelled by the Bank based on customer s request Cancelled by customer s request R Nepietiek līdzekļu. Insufficient funds Cancelled by the Bank as insufficient funds on day of execution 9 (15)

10 Example of payment status file: <?xml version="1.0" encoding="utf-8"?> - <FIDAVISTA xmlns=" xmlns:xsi=" - <Header> <Timestamp> </Timestamp> <From>Svenska Handelsbanken Riga Branch</From> </Header> - <PmtStat> <ExtId> </ExtId> <BankRef>102237</BankRef> <DocNo>1</DocNo> <StatCode>E</StatCode> <InfoToCustomer> Izpildīts.Executed </InfoToCustomer> <BookDate> </BookDate> </PmtStat> - <PmtStat> <ExtId> </ExtId> <BankRef>102238</BankRef> <DocNo>7</DocNo> <StatCode>O</StatCode> <InfoToCustomer> Gaida līdzekļus.waiting for cover </InfoToCustomer> <BookDate> </BookDate> - <PmtStat> <ExtId>0006</ExtId> <BankRef>102493</BankRef> <DocNo>6</DocNo> <StatCode>R</StatCode> <InfoToCustomer>Bankas atcelts. Cancelled by bank</infotocustomer> <BookDate> </BookDate> </PmtStat> </FIDAVISTA> 10 (15)

11 5. Account statement file The statement file is XL format file which is generated and exported from the in order to import the account statement to the customer s bookkeeping system. Account statement that reflects transactions for the specified period. The maximum size of the file is limited in with 2000 transactions. Account statement file ( mandatory; O optional; A- Accepted but not acted upon): Tag Garums Tips O/ Description in ax <Header> <Timestamp> xs:string <From> 0 70 xs:string O O File preparing time in format YYYYDDHHSSsss Name of preparer </Header> <Statement> <Period> Data of statement period <StartDate> xs:date Account statement start date in format YYYY--DD <EndDate> xs:date Account statement end date in format YYYY--DD <PrepDate> xs:date Account statement preparing date in format YYYY--DD </Period> <BankSet> AccHolderType O Information about bank who prepared account statement <Name> xs:string O Bank s name <LegalId> 0 20 LegalIDType O Bank s registration number <Address> 0 70 xs:string O Bank s address </BankSet> <ClientSet> AccHolderType O Client (account holder) data <Name> xs:string O Client s name <LegalId> 0 20 LegalIDType O Client s registration number or ID <Address> 0 70 xs:string O Client s address </ClientSet> <AccountSet> <AccNo> 1 34 AccountType Account number (from account IBAN number) <SubAccNo> 0 34 AccountOType O(A) Subaccount number <AccType> 0 70 xs:string O(A) Name of account type <AccHolder> <Name> xs:string O(A) <LegalID> 0 20 LegalIDType O(A) <Address> 0 70 xs:string O(A) AccHolderType O(A) Information about account holder. Usually is the same name as <ClientSet> but are exceptions. </AccHolder> <CcyStmt> Statement data for specific currency <Ccy> 3 3 CurrencyType Statement currency <OpenBal> 1 12 AmountType Opening balance <CloseBal> 1 12 AmountType Closing balance <TrxSet> O Account transaction. Field is mandatory if there are transactions in account in selected period. If there are no transactions in selected period field is not shown. 11 (15)

12 <TypeCode> 0 4 xs:string O Transaction types: <TypeName> 0 70 xs:string O Name of transaction type <RegDate> xs:date O OUTP- outgoing payment; INP- incoming payment; INTR- payment between one customer accounts; ED- memorial order (bank.s debiting payment); EC- memorial order (bank.s crediting payment); CHIN- cashin; CHOU-cashout; OTHR-other transactions. Payment registration date in format YYYY--DD. <BookDate> xs:date Transaction booking date in bank s system in format YYYY--DD <ValueDate> xs:date Value date of payment in bank s system. Field should be provided if value date is different from book date. <ExtId> 0 10 xs:string O Unique ID of payment from Payment file (if payment was uploaded using Payment file) <BenExtId> 0 5 xs:string O(A) Unique ID in case of ass payment <EndtoEndId> 0 35 xs:string O Payers assigned payment identificator. Used only in SEPA payments (corresponds to ISO field <EndtoEndId>) <BankRef> 1 25 xs:string Bank s reference number <DocNo> 0 25 xs:string O Document (payment) number. Provided by user in bookkeeping system (if payment was uploaded using Payment import) or entered in account remote control system (). <CorD> 1 1 xs:string.c. /.D. <AccAmt> 1 12 AmountType C or D. credit or debit operation Transaction amount in account currency. Decimals are separated with dot... <FeeAmt> 1 12 AmountType Amount of commission in account currency <PmtInfo> xs:string Transaction (payment) details <StrdRef> 1 35 xs:string O Beneficiary s assigned payment identificator <CPartySet> O Information about contra party of transaction (payment) <AccNo> 0 34 AccountOType Account number of contra party <SubAccNo> 0 34 AccountOType Contra party subaccount number <AccHolder> AccHolderType Data of contra party <Name> xs:string O Name of contra party <LegalID> 0 20 LegalIDType O Registration number of contra party <Address> 0 70 xs:string O Address of contra party </AccHolder> <BankCode> 0 20 xs:string O Contra party bank code <BankName> xs:string O Contra party bank name <Ccy> 3 3 CurrencyType O(A) Contra party transaction currency <Amt> 1 12 AmountType O(A) Contra party transaction amount <CurRate> 1 9 xs:decimal O(A) Currency rate (if payment was converted) <Giro> 0 5 xs:string O(A) Giro number of Beneficiary or Payer </CPartySet> </TrxSet> </CcyStmt> 12 (15)

13 </AccountSet> </Statement> Additional conditions for values of fields: Tag Name of field Condition <TypeCode> Transaction types ED and EC not applied <TypeName> Name of transaction type According to SWIFT standard in account statement T940 codes are used to describe certain transaction. T940 code/ <TypeName> Description NTRF Incoming/outgoing payments NSC Cash transactions, card payments and deposits NCHG Bank fees FINT Current asccount interest NINT Other interest NFEX Currency exchange FSC Other transactions NCRO Cross-border (incoming and outgoing) payments NLOC Domestic (incoming and outgoing) payments <BookDate> Transaction booking date The date is provided when payment is executed and amount debited from or credited to account <BankCode> Contra party bank code Bank code is provided only for cross-border payments Examples of transaction codes used in account statement: Tag <TypeCode> Tag <TypeName> Transaction OUTP NLOC Outgoing domestic payment OUTP NCRO Outgoing cross-border payment INP NCRO Incoming cross-border payment INP NLOC Incoming domestic payment OTHR NFEX Currency exchange (SPOT) CHIN NSC Cash deposit OTHR NCHG Fees for domestic payment, fee for cross-border payment, card transaction fee, current account maintenance fee CHOU NSC Cash withdrawal OTHR NINT Loan agreement No XYZ interest OTHR NSC Loan agreement No XYZ principal payment etc etc etc 13 (15)

14 Account statement example: <?xml version="1.0" encoding="utf-8"?> - <FIDAVISTA xmlns=" xmlns:xsi=" - <Header> <Timestamp> </Timestamp> <From> SVENSKA HANDELSBANKEN RIGA BRANCH </From> </Header> - <Statement> - <Period> <StartDate> </StartDate> <EndDate> </EndDate> <PrepDate> </PrepDate> </Period> - <BankSet> <Name> SVENSKA HANDELSBANKEN RIGA BRANCH </Name> <LegalId> </LegalId> <Address> CESU IELA 31/9</Address> </BankSet> - <ClientSet> <Name>Company X 1105</Name> <LegalId>1105</LegalId> </ClientSet> - <AccountSet> <AccNo>LV69HAND </AccNo> - <CcyStmt> <Ccy>EUR</Ccy> <OpenBal> </OpenBal> <CloseBal> </CloseBal> - <TrxSet> <TypeCode>OUTP</TypeCode> <TypeName>NLOC</TypeName> <BookDate> </BookDate> <BankRef>229922</BankRef> <DocNo>1</DocNo> <CorD>D</CorD> <AccAmt>123.33</AccAmt> <PmtInfo>Invoice 123/56 by Agreement 9787 dd </PmtInfo> - <CPartySet> <AccNo>LV37TREL </AccNo> - <AccHolder> <Name>Valsts Kase</Name> <LegalId> </LegalId> <Address>Smilšu ielā 7,Rīga</Address> </AccHolder> <BankCode>TRELLV20</BankCode> <Amt>123.33</Amt> <Ccy>EUR</Ccy> </CPartySet> </TrxSet> - <TrxSet> <TypeCode>OTHR</TypeCode> <TypeName>NCHG</TypeName> <BookDate> </BookDate> <BankRef>229922</BankRef> <CorD>D</CorD> <AccAmt>0.28</AccAmt> <PmtInfo> Charge for Domestic payment. Arch.ID: </PmtInfo> - <CPartySet> - <AccHolder> <Name>Handelsbanken Latvia</Name> </AccHolder> <Amt>0.28</Amt> <Ccy>EUR</Ccy> </CPartySet> </TrxSet> </CcyStmt> - <CcyStmt> <Ccy>SEK</Ccy> 14 (15)

15 <OpenBal>0.00</OpenBal> <CloseBal> </CloseBal> - <TrxSet> <TypeCode>OTHR</TypeCode> <TypeName>NSC</TypeName> <BookDate> </BookDate> <BankRef> </BankRef> <CorD>C</CorD> <AccAmt> </AccAmt> <PmtInfo>Overnight Deposit Agreement No Deposit Amount</PmtInfo> - <CPartySet> - <AccHolder> <Name>Handelsbanken Latvia</Name> </AccHolder> <Amt> </Amt> <Ccy>SEK</Ccy> </CPartySet> </TrxSet> - <TrxSet> <TypeCode>OTHR</TypeCode> <TypeName>NINT</TypeName> <BookDate> </BookDate> <BankRef> </BankRef> <CorD>C</CorD> <AccAmt>14.68</AccAmt> <PmtInfo>Overnight Deposit Agreement No Interest 0.30%</PmtInfo> - <CPartySet> - <AccHolder> <Name>Handelsbanken Latvia</Name> </AccHolder> <Amt>14.68</Amt> <Ccy>SEK</Ccy> </CPartySet> </TrxSet> </CcyStmt> - <CcyStmt> <Ccy>USD</Ccy> <OpenBal>0.00</OpenBal> <CloseBal>0.00</CloseBal> </CcyStmt> </AccountSet> </Statement> </FIDAVISTA> 15 (15)