Formats for internet bank

01.12.2023

This document specifies payment initiation and account statement formats in LHV internet bank.

Version history

01.12.2023	The new pain.001 format will be valid from 01.07.2024. More detailed information about the changes can be found from Connect specification. See news and description of the payment message.
05.10.2023	The new pain.001 format will be valid from 01.02.2024. More detailed information about the changes can be found from Connect specification. See news and description of the payment message.
30.03.2022	As of 30.03.2022, LHV no longer offers payment intermediation in rubles (RUB).
30.11.2020	Estonian Banking Association pain.001.001.03 XSD is replaced with custom XSD. See XSD for payment initiation message.Estonian Banking Association pain.001.001.03 XSD is replaced with custom XSD. See XSD for payment initiation message.
30.11.2020	Several smaller updates and changes will be done to Account Statement. Release is planned to December 2020. More details can be found from Connect Latest Updates and from the description of Account Statement.
05.02.2020	Two new optional indices added (2.10;2.35) to inform bank how the payments should be processed. Pre-agreed C2B conditions apply
05.02.2020	Payment routing code (index 2.98)
15.01.2020	Original payment reference is provided in case of return payment and original payment was uploaded with pain.001 (indecies 2.305; 2.307; 2.80)
15.01.2020	LHV implements Eesti Pangaliit version 1.4. Changes: Message element Control Sum (index 1.7; 2.5) and Number of Transactions (index 2.4) are changed from optional to mandatory. Index 2.79 maximum length changed from 140 to 70. Index 2.21 message element BIC is changed from mandatory to optional.

XML format (ISO 20022 Payment Initiation Message pain.001.001.09) (Valid from 01.07.2024)

The new pain.001 format will be valid from 01.07.2024. More detailed information about the changes can be found from Connect specification. See news and description of the payment message.

XML format (ISO 20022 Payment Initiation Message pain.001.001.03) (Valid until 30.06.2024)

The ISO 20022 Payment Initiation Message pain.001.001.03 is a payment initiation standard that covers SEPA and other payments made at LHV Bank. The ISO 20022 format allows to include information that is not supported by LHV Bank. That information is not processed by LHV Bank.

1. MESSAGE STRUCTURE
Group Header – mandatory, occurs once.
Payment Information – mandatory and repetitive. Contains information related to mostly the debit side of the payment.
Credit Transfer Transaction Information – mandatory and repetitive. Contains information related to the payment(s) included in the
message.

2. MESSAGE ROOT

INDEX	MULT.	MESSAGE ELEMENT	XML TAG	LHV REQUIREMENT
	[1..1]	+MessageRoot	<CstmrCdtTrfInitn>

3. GROUP HEADER

INDEX	MULT.	MESSAGE ELEMENT	XML TAG	LHV REQUIREMENT
1.0	[1..1]	+GroupHeader	<GrpHdr>
1.1	[1..1]	++MessageIdentification	<MsgId>
1.2	[1..1]	++CreationDateTime	<CreDtTm>
1.6	[1..1]	++NumberOfTransactions	<NbOfTxs>	Number of payments in all Payment Information blocks included in this message. If this number is not correct, the file upload will be cancelled.
1.7	[1..1]	++ControlSum	<CtrlSum>	Control sum of all individual amounts for all Payment Information blocks included in this message, irrespective of currencies. If this number is not correct, the file upload will be cancelled.
1.8	[1..1]	++InitiatingParty	<InitgPty>	LHV does not support credit transfers on behalf of the remitter. Information in this block will be ignored.
1.8	[0..1]	+++Name	<Nm>
1.8	[0..1]	+++Identification	<Id>
1.8	{Or	++++OrganisationIdentification	<OrgId>
1.8	{{Or	+++++BICOrBEI	<BICOrBEI>
1.8	Or}}	+++++Other	<Othr>
1.8	[1..1]	++++++Identification	<Id>
1.8	[0..1]	++++++SchemeName	<SchmeNm>
1.8	{{{Or	+++++++Code	<Cd>
1.8	Or}}}	+++++++ Proprietary	<Prtry>
1.8	{{Or	++++PrivateIdentification	<PrvtId>
1.8	{Or	+++++DateAndPlaceOfBirth	<DtAndPlcOfBirth>
1.8	[1..1]	++++++BirthDate	<BirthDt>
1.8	[1..1]	++++++CityOfBirth	<CityOfBirth>
1.8	[1..1]	++++++CountryOfBirth	<CtryOfBirth>
1.8	Or}}	+++++Other	<Othr>
1.8	[1..1]	++++++Identification	<Id>
1.8	[0..1]	++++++SchemeName	<SchmeNm>
1.8	{{{Or	+++++++Code	<Cd>
1.8	Or}}}	+++++++ Proprietary	<Prtry>

4. PAYMENT INFORMATION

INDEX	MULT.	MESSAGE ELEMENT	XML TAG	LHV REQUIREMENT
2.0	[1..n]	+PaymentInformation	<PmtInf>
2.1	[1..1]	++PaymentInformationIdentification	<PmtInfId>	Uniquely identifies the payment information group within this message.
2.2	[1..1]	++PaymentMethod	<PmtMtd>	Only the value TRF (credit transfer) is allowed here. If any other value is entered, it will be ignored.
2.3	[0..1]	++BatchBooking	<BtchBookg>	Not used.
2.4	[1..1]	++NumberOfTransactions	<NbOfTxs>	Number of payment included in the current Payment Information block. If this number is not correct, the file upload will be cancelled.
2.5	[1..1]	++ControlSum	<CtrlSum>	Control sum of all individual amounts in the current Payment Information block, irrespective of currencies. If this number is not correct, the file upload will be cancelled.
2.6	[0..1]	++PaymentTypeInformation	<PmtTpInf>
2.7	[0..1]	+++InstructionPriority	<InstrPrty>
2.8	[0..1]	+++ServiceLevel	<SvcLvl>
2.9	{Or	++++Code	<Cd>
2.10	Or}	++++Proprietary	<Prtry>	Used to send payment routing code (INST; SEPA; FAST; ALL)
2.11	[0..1]	+++LocalInstrument	<LclInstrm>
2.12	{Or	++++Code	<Cd>
2.13	Or}	++++Proprietary	<Prtry>	Payment priority information. The value here applies to all payments included in the current Payment Information block. See the supported values in Code Set: Payment Priority.
2.14	[0..1]	+++CategoryPurpose	<CtgyPurp>
2.15	[1..1]	++++Code	<Cd>	See the supported values in Code Set: Category Purpose.
2.17	[1..1]	++Requested Execution Date	<ReqdExctnDt>	Date on which the remitter’s account is debited.
2.19	[1..1]	++Remitter	<Dbtr>	Party from whose account the amount of payment is to be debited. If a different party’s information is entered, it will be ignored.
2.19	[1..1]	+++Name	<Nm>	Remitter’s name. For Virtual IBAN - the holder name (not the master account owner)
2.19	[0..1]	+++PostalAddress	<PstlAdr>
2.19	[0..1]	++++Country	<Ctry>	Remitter’s country ISO code. For Virtual IBAN - the holder country.
2.19	[0..2]	++++AddressLine	<AdrLine>	Remitter’s address. For Virtual IBAN - the holder address.
2.19	[0..1]	+++Identification	<Id>	For Virtual IBAN - do not use
2.19	{Or	++++OrganisationIdentification	<OrgId>
2.19	{{Or	+++++BICOrBEI	<BICOrBEI>	Remitter’s BIC or BEI code.
2.19	Or}}	+++++Other	<Othr>
2.19	[1..1]	++++++Identification	<Id>	Organisation’s identification code.
2.19	[0..1]	++++++SchemeName	<SchmeNm>
2.19	{{{Or	+++++++Code	<Cd>	See the supported values in Code Set: Organisation Identification.
2.19	Or}}}	+++++++ Proprietary	<Prtry>
2.19	Or}	++++PrivateIdentification	<PrvtId>
2.19	{{Or	+++++DateAndPlaceOfBirth	<DtAndPlcOfBirth>
2.19	[1..1]	++++++BirthDate	<BirthDt>	Remitter’s birth date.
2.19	[1..1]	++++++CityOfBirth	<CityOfBirth>	Remitter’s city of birth.
2.19	[1..1]	++++++CountryOfBirth	<CtryOfBirth>	Remitter’s birth country ISO code.
2.19	Or}}	+++++Other	<Othr>
2.19	[1..1]	++++++Identification	<Id>	Remitter’s identification code.
2.19	[0..1]	++++++SchemeName	<SchmeNm>
2.19	{{{Or	+++++++Code	<Cd>	See the supported values in Code Set: Private Person Identification.
2.19	Or}}}	+++++++ Proprietary	<Prtry>
2.20	[1..1]	++RemitterAccount	<DbtrAcct>	Remitter’s account from which the amount of payment is to be debited.
2.20	[1..1]	+++Identification	<Id>
2.20	[1..1]	++++IBAN	<IBAN>	Remitter’s IBAN or Virtual IBAN.
2.20	[0..1]	+++Currency	<Ccy>	Not required to be filled in. The payment will be made in the currency of the payment amount. If there are not enough funds available on the account, a relevant error message will appear.
2.21	[1..1]	++ RemitterAgent	<DbtrAgt>	Remitter’s bank information.
2.21	[1..1]	+++FinancialInstitutionIdentification	<FinInstnId>
2.21	[0..1]	++++BIC	<BIC>	If the LHV BIC is faulty or missing, it will be replaced with the correct code.
2.21	[0..1]	++++ Other	<Othr>	Not used.
2.21	[1..1]	+++++ Identification	<Id>	Usage Rule: Only ‘NOTPROVIDED’ is allowed.
2.23	[0..1]	++UltimateRemitter	<UltmtDbtr>	SEPA specific information. Ultimate party that owes an amount of money to the (ultimate) beneficiary. If ultimate remitter information is filled in at the Payment Information level, it will apply to all payments included in this block. Usage rule: Only to be used if different from the beneficiary.
2.23	[0..1]	+++Name	<Nm>	Ultimate remitter’s name.
2.23	[0..1]	+++Identification	<Id>
2.23	{Or	++++OrganisationIdentification	<OrgId>
2.23	{{Or	+++++BICOrBEI	<BICOrBEI>	Ultimate remitter’s BIC or BEI code.
2.23	Or}}	+++++Other	<Othr>
2.23	[1..1]	++++++Identification	<Id>	Organisation’s identification code.
2.23	[0..1]	++++++SchemeName	<SchmeNm>
2.23	{{{Or	+++++++Code	<Cd>	See the supported values in Code Set: Organisation Identification.
2.23	Or}}}	+++++++ Proprietary	<Prtry>
2.23	Or}	++++PrivateIdentification	<PrvtId>
2.23	{{Or	+++++DateAndPlaceOfBirth	<DtAndPlcOfBirth>
2.23	[1..1]	++++++BirthDate	<BirthDt>	Ultimate remitter’s birth date.
2.23	[1..1]	++++++CityOfBirth	<CityOfBirth>	Ultimate remitter’s city of birth.
2.23	[1..1]	++++++CountryOfBirth	<CtryOfBirth>	Ultimate remitter’s birth country ISO code.
2.23	Or}}	+++++Other	<Othr>
2.23	[1..1]	++++++Identification	<Id>	Ultimate remitter’s identification code.
2.23	[0..1]	++++++SchemeName	<SchmeNm>
2.23	{{{Or	+++++++Code	<Cd>	See the supported values in Code Set: Private Person Identification.
2.23	Or}}}	+++++++ Proprietary	<Prtry>
2.24	[0..1]	++ChargesBearer	<ChrgBr>	See the supported values in Code Set: Charges Bearer.
2.25	[0..1]	++ChargesAccount	<ChrgsAcct>	LHV does not support charge debiting from other than remitter’s account.
2.25	[1..1]	+++Identification	<Id>
2.25	[1..1]	++++IBAN	<IBAN>
2.25	[0..1]	+++Currency	<Ccy>
2.27	[1..n]	++CreditTransferTransactionInformation	<CdtTrfTxInf>	This block contains a set of elements providing information on the payment(s) included in the message.
2.28	[1..1]	+++PaymentIdentification	<PmtId>
2.29	[0..1]	++++InstructionIdentification	<InstrId>	Unique identification, as assigned by an instructing party for an instructed party, to unambiguously identify the instruction.
2.30	[1..1]	++++EndToEndIdentification	<EndToEndId>	Unique identification assigned by the initiating party to unumbiguously identify the transaction.Always sent to beneficiary bank.
2.31	[0..1]	+++PaymentTypeInformation	<PmtTpInf>	Set of elements used to specify the type of payment.
2.33	[0..1]	++++ServiceLevel	<SvcLvl>	Not used.
2.34	{Or	++++Code	<Cd>
2.35	Or}	++++Proprietary	<Prtry>	Used to send payment routing code (INST; SEPA; FAST; ALL)
2.36	[0..1]	++++LocalInstrument	<LclInstrm>
2.37	{Or	+++++Code	<Cd>
2.38	Or}	+++++Proprietary	<Prtry>	Payment priority information. The value here applies to the payment included in the current Credit Transfer Transaction Information block. See the supported values in Code Set: Payment Priority.
2.39	[0..1]	++++CategoryPurpose	<CtgyPurp>
2.40	[1..1]	+++++Code	<Cd>	See the supported values in Code Set: Category Purpose.
2.42	[1..1]	+++Amount	<Amt>
2.43	{Or	++++InstructedAmount	<InstdAmt>	Payment amount and the currency ordered by the initiating party. All currencies accepted by the bank for payment services are allowed. If there are not enough funds available on the account in a given currency, a relevant error message will appear.
2.44	Or}	++++EquivalentAmount	<EqvtAmt>	Not used.
2.51	[0..1]	+++ChargeBearer	<ChrgBr>	See the supported values in Code Set: Charges Bearer.
2.70	[0..1]	+++UltimateRemitter	<UltmtDbtr>	SEPA specific information. Ultimate party that owes an amount of money to the (ultimate) beneficiary. If ultimate remitter information is filled in at the Credit Transfer Transaction Information level, it will apply only to the current payment. Usage rule: Only to be used if different from the beneficiary.
2.70	[0..1]	++++Name	<Nm>	Ultimate remitter’s name.
2.70	[0..1]	++++Identification	<Id>
2.70	{Or	+++++OrganisationIdentification	<OrgId>
2.70	{{Or	++++++BICOrBEI	<BICOrBEI>	Ultimate remitter’s BIC or BEI code.
2.70	Or}}	++++++Other	<Othr>
2.70	[1..1]	+++++++Identification	<Id>	Organisation’s identification code.
2.70	[0..1]	+++++++SchemeName	<SchmeNm>
2.70	{{{Or	++++++++Code	<Cd>	See the supported values in Code Set: Organisation Identification.
2.70	Or}}}	++++++++ Proprietary	<Prtry>
2.70	Or}	+++++PrivateIdentification	<PrvtId>
2.70	{{Or	++++++DateAndPlaceOfBirth	<DtAndPlcOfBirth>
2.70	[1..1]	+++++++BirthDate	<BirthDt>	Ultimate remitter’s birth date.
2.70	[1..1]	+++++++CityOfBirth	<CityOfBirth>	Ultimate remitter’s city of birth.
2.70	[1..1]	+++++++CountryOfBirth	<CtryOfBirth>	Ultimate remitter’s birth country ISO code.
2.70	Or}}	++++++Other	<Othr>
2.70	[1..1]	+++++++Identification	<Id>	Ultimate remitter’s identification code.
2.70	[0..1]	+++++++SchemeName	<SchmeNm>
2.70	{{{Or	++++++++Code	<Cd>	See the supported values in Code Set: Private Person Identification.
2.70	Or}}}	++++++++ Proprietary	<Prtry>
2.71	[0..1]	+++IntermediaryAgent1	<IntrmyAgt1>	Information about the beneficiary’s bank’s correspondent bank. Used for foreign payments.
2.71	[1..1]	++++FinancialInstitutionIdentification	<FinInstnId>
2.71	[0..1]	+++++BIC	<BIC>	Bank’s BIC code.
2.71	[0..1]	+++++ClearingSystemMemberIdentification	<ClrSysMmbId>
2.71	[0..1]	++++++ClearingSystemIdentification	<ClrSysId>
2.71	[1..1]	+++++++Code	<Cd>	For the clearing system’s identification code see the External Code Sets spreadsheet on the ISO website.
2.71	[1..1]	++++++MemberIdentification	<MmbId>	Identification of the beneficiary's bank's correspondent bank in a clearing system.
2.71	[0..1]	+++++Name	<Nm>	Name of the beneficiary’s bank’s correspondent bank. Used when the BIC or the clearing system’s member identification is not known to the initiating party.
2.71	[0..1]	+++++PostalAddress	<PstlAdr>
2.71	[0..1]	++++++Country	<Ctry>	Country ISO code of the beneficiary’s bank’s correspondent bank.
2.71	[0..2]	++++++AddressLine	<AdrLine>	Country address of the beneficiary’s bank’s correspondent bank.
2.72	[0..1]	+++IntermediaryAgent1Account	<IntrmyAgt1Acct>	Not used.
2.72	[1..1]	++++Identification	<Id>
2.72	{Or	+++++IBAN	<IBAN>
2.72	Or}	+++++Other	<Othr>
2.72	[1..1]	++++++Identification	<Id>
2.77	[0..1]	+++BeneficiaryAgent	<CdtrAgt>	Beneficiary agent’s information is required if agent is situated outside Estonia.
2.77	[1..1]	++++FinancialInstitutionIdentification	<FinInstnId>
2.77	[0..1]	+++++BIC	<BIC>	Beneficiary’s bank’s BIC.
2.77	[0..1]	+++++ClearingSystemMemberIdentification	<ClrSysMmbId>
2.77	[0..1]	++++++ClearingSystemIdentification	<ClrSysId>
2.77	[1..1]	+++++++Code	<Cd>	For the clearing system’s identification code see the External Code Sets spreadsheet on the ISO website.
2.77	[1..1]	++++++MemberIdentification	<MmbId>	Beneficiary’s bank identification in a clearing system. RUB payments to Russia, the BIK code is entered here.
2.77	[0..1]	+++++Name	<Nm>	Beneficiary's bank name. Usage rule: The name is limited to 70 characters in length. Used when the BIC or the clearing system’s member identification is not known to the initiating party.
2.77	[0..1]	+++++PostalAddress	<PstlAdr>
2.77	[0..1]	++++++Country	<Ctry>	Beneficiary’s bank’s country ISO code.
2.77	[0..2]	++++++AddressLine	<AdrLine>	Beneficiary’s bank’s address.
2.78	[0..1]	+++BeneficiaryAgentAccount	<CdtrAgt>	Beneficiary’s bank account at its correspondent bank. Usage rule: Used only for RUB payments.
2.78	[1..1]	++++Identification	<Id>
2.78	{Or	+++++IBAN	<IBAN>
2.78	Or}	+++++Other	<Othr>
2.78	[1..1]	++++++Identification	<Id>	For RUB payments to Russia, the beneficiary’s bank's correspondent account with the Russian central bank is entered here.
2.79	[1..1]	+++Beneficiary	<Cdtr>	Beneficiary’s information.
2.79	[1..1]	++++Name	<Nm>	Beneficiary’s name. Maximum lenght 70
2.79	[0..1]	++++PostalAddress	<PstlAdr>	Beneficiary’s address.
2.79	[0..1]	+++++Country	<Ctry>
2.79	[0..2]	+++++AddressLine	<AdrLine>
2.79	[0..1]	++++Identification	<Id>	Beneficiary’s identification.
2.79	{Or	+++++OrganisationIdentification	<OrgId>
2.79	{{Or	++++++BICOrBEI	<BICOrBEI>	Beneficiary’s BIC or BEI code.
2.79	Or}}	++++++Other	<Othr>
2.79	[1..1]	+++++++Identification	<Id>	Organisation’s identification code. For RUB payments to Russia, INN and KPP codes are entered here.
2.79	[0..1]	+++++++SchemeName	<SchmeNm>
2.79	{{{Or	++++++++Code	<Cd>	See the supported values in Code Set: Organisation Identification.
2.79	Or}}}	++++++++Proprietary	<Prtry>	Scheme names INN and KPP are be entered here.
2.79	Or}	+++++PrivateIdentification	<PrvtId>
2.79	{{Or	++++++DateAndPlaceOfBirth	<DtAndPlcOfBirth>
2.79	[1..1]	+++++++BirthDate	<BirthDt>	Beneficiary’s birth date.
2.79	[1..1]	+++++++CityOfBirth	<CityOfBirth>	Beneficiary’s city of birth.
2.79	[1..1]	+++++++CountryOfBirth	<CtryOfBirth>	Beneficiary’s birth country ISO code.
2.79	Or}}	++++++Other	<Othr>
2.79	[1..1]	+++++++Identification	<Id>	Beneficiary’s identification.
2.79	[0..1]	+++++++SchemeName	<SchmeNm>
2.79	{{{Or	++++++++Code	<Cd>	See the supported values in Code Set: Private Person Identification.
2.79	Or}}}	++++++++Proprietary	<Prtry>	Scheme names INN and KPP are be entered here.
2.80	[1..1]	+++BeneficiaryAccount	<CdtrAcct>	Beneficiary’s account.
2.80	[1..1]	++++Identification	<Id>
2.80	{Or	+++++IBAN	<IBAN>	Beneficiary’s IBAN.
2.80	Or}	+++++Other	<Othr>	Beneficiary’s account number.
2.80	[1..1]	++++++Identification	<Id>
2.80	[0..1]	++++++SchemeName	<SchmeNm>
2.80	[1..1]	+++++++Code	<Cd>
2.81	[0..1]	+++UltimateBeneficiary	<UltmtCdtr>	SEPA specific information. Ultimate beneficiary is the ultimate beneficiary of the payment.
2.81	[0..1]	++++Name	<Nm>	Ultimate beneficiary’s name.
2.81	[0..1]	++++Identification	<Id>
2.81	{Or	+++++OrganisationIdentification	<OrgId>
2.81	{{Or	++++++BICOOrBEI	<BICOrBEI>	Ultimate beneficiary’s BIC or BEI.
2.81	Or}}	++++++Other	<Othr>
2.81	[1..1]	+++++++Identification	<Id>	Ultimate beneficiary’s organisation identification.
2.81	[0..1]	+++++++SchemeName	<SchmeNm>
2.81	{{{Or	++++++++ Code	<Cd>	See the supported values in Code Set: Organisation Identification.
2.81	Or}}}	++++++++ Proprietary	<Prtry>
2.81	Or}	+++++PrivateIdentification	<PrvtId>
2.81	{Or	++++++DateAndPlaceOfBirth	<DtAndPlcOfBirth>
2.81	[1..1]	+++++++BirthDate	<BirthDt>	Ultimate beneficiary’s birth date.
2.81	[1..1]	+++++++CityOfBirth	<CityOfBirth>	Ultimate beneficiary’s city of birth.
2.81	[1..1]	+++++++CountryOfBirth	<CtryOfBirth>	Ultimate beneficiary’s birth country ISO code.
2.81	Or}}	++++++Other	<Othr>
2.81	[1..1]	+++++++Identification	<Id>	Ultimate beneficiary’s identification.
2.81	[0..1]	+++++++SchemeName	<SchmeNm>
2.81	{{{Or	++++++++ Code	<Cd>	See the supported values in Code Set: Private Person Identification.
2.81	Or}}}	++++++++ Proprietary	<Prtry>
2.86	[0..1]	+++Purpose	<Purp>	SEPA specific information. Reason for the payment.
2.87	[1..1]	++++Code	<Cd>	See the supported codes in Code Set: Purpose.
2.89	[0..10]	+++RegulatoryReporting	<RgltryRptg>	Information about the declaration of payments. Usage rules: 1.Information required by the Russian central bank: For RUB payments to Russia, the VO code and in some cases the KBK code are entered here.
2.89	[0..1]	++++Authority	<Authrty>
2.89	[0..1]	+++++Country	<Ctry>
2.89	[0..n]	++++Details	<Dtls>
2.89	[0..1]	+++++Type	<Tp>
2.89	[0..1]	+++++Country	<Ctry>
2.89	[0..1]	+++++Code	<Cd>
2.89	[0..1]	+++++Information	<Inf>	Specification of the balance of payment code 900. For RUB payments to Russia, the VO and KBK codes are entered here.
2.98	[0..1]	+++RemittanceInformation	<RmtInf>	Used to enter the payment description (unstructured) and the reference number (structured). It is mandatory to provide one or the other. If both structured and unstructured information is filled in, the beneficiary reference under the structured information will be lifted to the unstructured information tag in accordance with the EACT standard for unstructured remittance information formatting rules. If the remittance information will, as a result, be longer than 140 characters, the bank will deliver only the first 140 characters of the remittance information. Reference number (structured) must comply with Estonian reference standard or Creditor reference
2.99	[0..1]	++++Unstructured	<Ustrd>	Payment description is entered here.
2.100	[0..1]	++++Structured	<Strd>
2.120	[0..1]	+++++BeneficiaryReferenceInformation	<CdtrRefInf>
2.121	[0..1]	++++++Type	<Tp>
2.122	[1..1]	+++++++CodeOrProprietary	<CdOrPrtry>
2.123	[1..1]	++++++++Code	<Cd>	Only the value SCOR is allowed here. If any other value is entered, it will be ignored.
2.125	[0..1]	+++++++Issuer	<Issr>
2.126	[0..1]	++++++Reference	<Ref>	Payment reference number is entered here.

5. CODE SET: PAYMENT PRIORITY
If payment priority is not provided or faulty, default values will be used. For additional information see Payment processing time limits and settlements.

CODE [2]	DESCRIPTION [10]
NORM	Normal payment.
HIGH	Urgent payment.
EXPR	Extra urgent payment.

6. CODE SET: CATEGORY PURPOSE

CODE [2]	DESCRIPTION [10]
CASH	Cash management.
CORT	Trade settlement payment.
DIVI	Dividends payment.
GOVT	Government payment.
HEDG	Hedging.
INTC	Intra-company payment.
INTE	Interest payment.
LOAN	Transfer of a loan to a borrower.
PENS	Pension payment.
SALA	Salary payment.
SECU	Securities payment.
SSBE	Social security benefit payment.
SUPP	Supplier payment.
TAXS	Tax payment.
TRAD	Trade finance transaction payment.
TREA	Treasury payment.
VATX	VAT payment.
WHLD	Withholding tax payment.
OTHR	Other payment.
EPAY	Payment via online banking.
FCOL	Fee collection.

7. CODE SET: PURPOSE

CODE [2]	DESCRIPTION [10]
ACCT	Account management.
CASH	Cash management.
COLL	Collection payment.
INTC	Intra-company payment.
LIMA	Liquidity management.
NETT	Netting.
AGRT	Agricultural payment.
BEXP	Business expenses.
COMC	Commercial payment.
CPYR	Copyright.
LICF	Licence fee.
GDDS	Purchase and sale of goods.
SCVE	Purchase and sale of services.
SUBS	Subscription.
SUPP	Supplier payment.
CHAR	Charity payment.
HLRP	Housing loan repayment.
INSU	Insurance premium.
INTE	Interest.
LBRI	Labour insurance.
LIFI	Life insurance.
LOAN	Loan to borrower.
LOAR	Loan to lender.
PPTI	Property insurance.
ADVA	Advance payment.
CCRD	Credit card payment.
DCRD	Debit card payment.
GOVT	Government payment.
MSVC	Multiple service types.
NOWS	Not otherwise specified.
OTHR	Other.
PADD	Preauthorised debit.
RENT	Rent.
STDY	Study.
DERI	Derivatives.
DIVD	Dividend.
FREX	Foreign exchange.
SAVG	Savings.
SECU	Securities.
TREA	Treasury payment.
DNTS	Dental services.
HLTI	Health insurance.
HSPC	Hospital care.
LTCF	Long-term care facility.
MDCS	Medical services.
ALMY	Alimony payment.
BONU	Bonus payment.
BECH	Child benefit.
COMM	Commission.
PENS	Pension payment.
SALA	Salary payment.
SSBE	Social security benefit.
HSTX	Housing tax.
INTX	Income tax.
TAXS	Tax payment.
VATX	VAT payment.
AIRB	Air transport.
BUSB	Bus transport.
FERB	Ferry transport.
RLWY	Railway transport.
CBTV	Cable TV bill.
ELEC	Electricity bill.
ENRG	Energies.
GASB	Gas bill.
NWCH	Network charge.
NWCM	Network communication.
OTLC	Other telecom related bill.
PHON	Telephone bill.
WTER	Water bill.
DEBT	Deposit.
GDSV	Purchase and sale of goods and services.
CDBL	Credit card bill.
EDUC	Education.
IVPT	Invoice payment.
TBIL	Telecommunication bill.
INVS	Investment and securities.
ALLW	Allowance.
PAYR	Payroll.
UBIL	Utilities.

8. CODE SET: PRIVATE PERSON IDENTIFICATION

CODE [2]	DESCRIPTION [10]
ARNU	Number assigned by a social security agency to identify a non-resident person.
CCPT	Number assigned by an authority to identify the passport number of a person.
CUST	Number assigned by an issuer to identify a customer.
DRLC	Number assigned by an authority to identify a driver's license.
EMPL	Number assigned by a registration authority to an employee.
NIDN	Number assigned by an authority to identify the national identity number of a person.
SOSE	Number assigned by an authority to identify the social security number of a person.
TXID	Number assigned by a tax authority to identify a person.

9. CODE SET: CHARGES BEARER
If the payment priority is not provided or faulty, default values will be used. For additional information see Payment processing time limits and settlements.

CODE [2]	DESCRIPTION [10]
SLEV Allowed only for SEPA payments. Shared charges.
SHAR Shared charges.
DEBT Remitter pays charges.

10. CODE SET: ORGANISATION IDENTIFICATION

CODE [2]	DESCRIPTION [10]
BANK	Unique and unambiguous assignment made by a specific bank or similar financial institution to identify a relationship as defined between the bank and its client.
CBID	A unique identification number assigned by a central bank to identify an organisation.
CHID	A unique identification number assigned by a clearing house to identify an organisation.
COID	Country authority given organisation identification (e.g., corporate registration number).
CUST	Number assigned by an issuer to identify a customer. Number assigned by a party to identify a beneficiary or remitter relationship.
DUNS	A unique identification number provided by Dun & Bradstreet to identify an organisation.
EMPL	Number assigned by a registration authority to an employer.
GS1G	Global Location Number. A non-significant reference number used to identify legal entities, functional entities, or physical entities according to GS1 numbering scheme rules. The number is used to retrieve detailed information that is linked to it.
SREN	The SIREN number is a 9 digit code assigned by INSEE, the French National Institute for Statistics and Economic Studies, to identify an organisation in France.
SRET	The SIRET number is a 14 digit code assigned by INSEE, the French National Institute for Statistics and Economic Studies, to identify an organisation unit in France. It consists of the SIREN number, followed by a five digit classification number, to identify the local geographical unit of that entity.
TXID	Number assigned by a tax authority to identify an organisation.

XML format (ISO 20022 Account Statement Message camt.053.001.02)

The ISO 20022 Account Statement Message camt.053.001.02 standard is used to report account booked transactions and balances of a selected time period. The message includes information about the opening balance, the closing balance, and the available balance together with all booked transactions of a reporting period. The ISO 20022 format allows to include information that is not supported by LHV Bank. That information is not provided by LHV Bank.

Message structure and detailed description

TH6 format (Account Statement Message)

A – alphanumeric (character)
* Mandatory field
Ø – space
N – numeric
** Not processed in payment importing Amount aligned to the right

HEADER

NO [1]	POS [1]	DESCRIPTION [3]	TYPE [1]	LENGTH [1]	COMMENT [5]
1	1	Subject code	A*	4	VVØØ
2	5	Record code	A*	3	,000
3	8	Bank code	N*	3	689
4	11	Account number	A*	20	Bank account number in the IBAN format.
5	31	Date	N*	6	YYMMDD, query date.
6	37	Time	N*	4	HHMM, query time.

TRANSACTIONS

NO [1]	POS [1]	DESCRIPTION [3]	TYPE [1]	LENGTH [1]	COMMENT [5]
1	1	Subject code	A*	4	VVØØ
2	5	Record code	A*	1	1 – transaction, 2 – opening balance, 3 – closing balance.
3	6	Bank reference	A*	16	Displayed in the format YYYYMMDD .
4	22	Tr. type	A*	4	Transaction code (MK – domestic payment, MV – foreign payment).
5	26	Own account number	A*	20	Bank account number in the IBAN format.
6	46	Currency	A*	3
7	49	Bank	A*	35	Counterparty’s bank code and account number.
8	84	Name	A*	35	Counterparty’s name.
9	119	Doc. no	A*	8
10	127	Description	A*	140
11	267	C/D	A*	2	C – credit, D – debit.
12	269	Amount	N*	12	In cents and always positive.
13	281	Client reference	A*	35	Payment reference no.

FOOTER

NO [1]	POS [1]	DESCRIPTION [3]	TYPE [1]	LENGTH [1]	COMMENT [5]
1	1	Subject code	A*	4	VVØØ
2	5	Record code	A*	3	999
3	8		A	190	Unused.
4	198	Checksum	N*	12	Last 12 positions.
5	210		A	20	Unused.

CSV format (Account Statement Message)

Under the internet bank settings, you yourself can define the field and decimal separators.