2026-06-16
Added · Updated
Latvijas Banka issued Regulation No 209 to define the technical specifications for submitting statistical data on credit institutions' exposures and involved persons. The regulation mandates specific XML file structures, naming conventions, and encryption standards for transmitting credit exposure and person involvement records. It further details the use of file exchange services and online messaging protocols to ensure secure and standardized electronic information exchange.
FCMC published 1 document in the last 30 days — get each new one by email the day it lands.
Regulation No 209 | Version of 9 February 2026 (in effect as of 1 July 2026) Structure and Format to Be Used for Providing Statistical Data on the Credit Institutions' Credit Exposures and the Persons Involved The document has been drafted based on Chapter 2.9 of Latvijas Banka's Regulation No 226 "Regulation on Electronic Information Exchange with Latvijas Banka" of 24 October 2022 and it stipulates the technical aspects for submitting the information required under Latvijas Banka's Regulation No 209 "Regulation on Compiling and Submitting the Statistical Data on the Credit Institutions' Credit Exposures and the Persons Involved" of 13 June 2023. The present version of the document has been drafted in compliance with Latvijas Banka's Regulation No 416 "Amendments to Latvijas Banka's Regulation No 209 " Regulation on Compiling and Submitting the Statistical Data on the Credit Institutions' Credit Exposures and the Persons Involved" of 13 June 2022" of 9 February 2026.
Table of contents
I. Notations used .................................................................................................................. 2
II. File exchange using the file exchange service or the online messages........................... 2
III. File of information on credit exposures......................................................................... 4
IV. File of the persons involved in credit exposures ........................................................... 9
V. Identification data correction file on the persons involved in credit exposures............ 10
VI. Reply file ..................................................................................................................... 11
I. Notations used
4.2 the names of exchanges (for outgoing files) are constructed according to the following
rules: E.<the uniform registration number (NMK code) of the Register participant>_OUT. For example, E.40000000000_OUT;
4.3 the names of the queues (for incoming files) are constructed according to the following
rules: Q.<the uniform registration number (NMK code) of the Register participant>_KREG_IN. For example, Q.40000000000_KREG_IN;
4.4 the Register participant shall indicate the following parameters for each online message:
4.4.1. MessageID – a unique message identifier (36 characters; where it is not indicated,
the uniqueness of the message shall be verified on the basis of the file name);
4.4.2. FileName – the file name;
4.4.3. SegmentCount – the total number of file segments ("1" if not indicated);
4.4.4. SegmentNumber – the current sequence number of the file segment ("1" if not
indicated);
4.4.5. FileHash – the file checksum (base64-encoded);
4.4.6. SignatureValue – the file signature (base64-encoded);
4.4.7. X509Certificate – the public part of the signing certificate (base64‑encoded);
4.5 Latvijas Banka shall indicate the following parameters for each online message:
4.5.1. MessageID – a unique message identifier;
4.5.2. CorrelationID – the identifier of the submitted message (see Paragraph 4.4.1), where
the message of Latvijas Banka is based on the submitted message and the respective identifier was indicated;
4.5.3. FileName – the file name;
4.5.4. SegmentCount – the total number of file segments ("1" if not indicated);
4.5.5. SegmentNumber – the current sequence number of the file segment ("1" if not
indicated);
4.5.6. FileHash – the file checksum (base64-encoded);
4.5.7. SignatureValue – the file signature (base64-encoded);
4.5.8. X509Certificate – the public part of the signing certificate (base64-encoded);
4.6 the following additional technical information shall be used:
Name Value Comment
RabbitMQ server
Test: at-mqfiles.bank.lv
Production: prod-mqfiles.bank.lv
Port: 15701
Authentication method
EXTERNAL Shall be indicated when using the client authentication certificate Virtual resource (VirtualHost) kreg Shall be indicated when connecting to the server File transmission Exchange: E.<NMK code>_OUT Routing key: KREG Files shall be published to the exchange, indicating the corresponding routing key File reception Queue: Q.<NMK>_KREG_IN Files are received by reading the corresponding queue
III. File of information on credit exposures
3.5. The prefix of the file name shall be "krd".
4.6. Unless otherwise stipulated in the present description, information to be provided shall
comply with the description and format stated in Formats and Structure of Credit Register Files and Web Services (hereinafter, Register Formats and Structure).
5.7. File structure
6.8. Header element of the file
6.18.1 Structure of the header element of the file
<ValidFrom>Date of the customer's obligations taking effect</ValidFrom> <TakeOverDate>Date of taking over the customer's obligations</TakeOverDate> <ValidTo>End date of the customer's obligations as per customer contract</ValidTo> <SettlementDate>Settlement date</SettlementDate> <ActualEndDate>Actual end date of the customer's obligations</ActualEndDate> <Amount>Amount of the customer's obligations as per customer contract</Amount> <Currency>Currency code of the customer's obligations as per customer contract</Currency> <Syndicate>Reference to a syndicated loan</Syndicate> <SyndContractID>Syndicated loan contract identifier</SyndContractID> <RegrRights>Reference to the right of recourse</RegrRights> <FiduciaryInst>Reference to fiduciary instrument</FiduciaryInst> <ProjectLoan>Reference to a project finance loan</ProjectLoan> <SubDebts>Reference to subordinated debt</SubDebts> <RpmntRights>Reference to repayment rights</RpmntRights> <RemainingAmount>Actual oOutstanding principal amount of the customer's obligations</RemainingAmount> <RemainderCurrency>Currency code of the actual outstanding principal amount of the customer's obligations</RemainderCurrency> <OffBlncAmount>Off-balance sheet amount of the customer's obligations</OffBlncAmount> <OffBlncCurrency>Currency code of the off-balance sheet amount of the customer's obligations</OffBlncCurrency> <CreditAccounting>Reference to the accounting</CreditAccounting> <IntRate>Interest rate</IntRate> <IntRateCap>Interest rate cap</IntRateCap> <IntRateFloor>Interest rate floor</IntRateFloor> <RefRate>Reference rate values</RefRate> <RefRateDur>Reference rate maturity</RefRateDur> <IntRateSpread>Interest rate spread</IntRateSpread> <IntRateType>Interest rate type</IntRateType> <IntRateFrq>Interest rate reset frequency</IntRateFrq> <InterestRateRevisionDate>Next interest rate reset date</InterestRateRevisionDate> <IntRateEndDate>End date of interest-only period</IntRateEndDate> <AccInterest>Accrued interest</AccInterest> <AccInterestCurrency>Currency code of the accrued interest</AccInterestCurrency> <Accruals>Accumulated impairment amount</Accruals> <AccrualsCurrency>Currency account of the accumulated impairment amount</AccrualsCurrency> <QualityRate>Impairment assessment method</QualityRate> <ImpairmentType>Type of impairment </ImpairmentType>
<PrvsnOffBlnc>Provisions associated with off-balance-sheet exposures</PrvsnOffBlnc> <PrvsnOffBlncCurrency>Currency account of the provisions associated with off-balance-sheet exposures</PrvsnOffBlncCurrency> <DelayPeriod>Number of days past due</DelayPeriod> <DelayAmount>Principal past due</DelayAmount> <DelayCurrency>Currency code of the principal past due</DelayCurrency> <DelayInterest>Interest past due</DelayInterest> <DelayInterestCurrency>Currency code of the interest past due</DelayInterestCurrency> <OtherDelayedFees>Other payments past due</OtherDelayedFees> <OtherDelayedFeesCurrency>Currency code of the other payments past due</OtherDelayedFeesCurrency> <ProbabilityOfDefault>Probability of the customer's default on its obligations</ProbabilityOfDefault> <LossGivenDefault>Potential losses in the event of the customer's default on its obligations</LossGivenDefault> <PoDMethod>Reference to the assessment method</PoDMethod> <CreditDefaultStatus>Default status of the instrument</CreditDefaultStatus> <CreditDefaultStatus>Date of the default status of the instrument</CreditDefaultDate> <PerformingStatus>Performing status of the instrument</PerformingStatus> <PerformingDate>Date of the performing status of the instrument</PerformingDate> <RecognBalStatus>Reference to balance sheet and off-balance sheet recognition</RecognBalStatus> <AccountClsf>Accounting classification of customer's obligations</AccountClsf> <AmrtType>Amortisation type</AmrtType> <PmntFrq>Payment frequency</PmntFrq> <FairValueRisk>Fair value changes due to changes in credit risk before purchase</FairValueRisk> <TransfAmount>Transferred amount</TransfAmount> <TransfAmountCurrency>Currency account of the transferred amount</TransfAmountCurrency> <CountryRiskTransfBasis>Reason for the country risk transfer</CountryRiskTransfBasis> <RiskEmanatingCountry>Country where the risk is transferred from</RiskEmanatingCountry> <RiskAcceptCountry>Country where the risk is transferred to</RiskAcceptCountry> <SecuritType>Type of securitisation</SecuritType> <Losses>Amount of losses</Losses> <LossesCurrency>Currency account of the amount of losses</LossesCurrency> <SrcEncumbrance>Source of encumbrance </SrcEncumbrance> <CreditStatus>Status of the customer's obligations</CreditStatus>
<ForbearanceStatus>Status feature of the customer's obligations</ForbearanceStatus> <ForbearanceStatusDate>Date of the status feature of the customer's obligations</ForbearanceStatusDate> <FairValAccu>Accumulated changes in fair value due to credit risk</FairValAccu> <FairValAccuCurrency>Currency code of the accumulated changes in fair value due to credit risk</FairValAccuCurrency> <CumulatRecov>Cumulative recoveries since the date of default</CumulatRecov> <CumulatRecovCurrency>Currency code of the cumulative recoveries since the date of default</CumulatRecovCurrency> <ClsExposure>Reference to the classification of customer's obligations in the trading book</ClsExposure> <CarryAmount>Carrying amount</CarryAmount> <CarryAmountCurrency>Currency code of the carrying amount</CarryAmountCurrency> <CollateralList> <Collateral> <CollateralId>Collateral identifier</CollateralId> <CollateralType>Type of collateral</CollateralType> <CollateralCountry>Real estate collateral location</CollateralCountry> <CollateralOrigValue>Original collateral value</CollateralOrigValue> <CollateralOrigValueCurrency>Currency code of the original collateral value</CollateralOrigValueCurrency> <CollateralOrigDate>Date of original collateral value</CollateralOrigDate> <CollateralValue>Collateral value</CollateralValue> <CollateralValueCurrency>Currency code of the collateral value</CollateralValueCurrency> <CollateralValueType>Type of collateral value</CollateralValueType> <CollateralValueDate>Date of collateral value</CollateralValueDate> <CollateralValutApproach>Collateral valuation approach</CollateralValutApproach> <Collateral3rdPartyClaims>Value of third party priority claims against the collateral</Collateral3rdPartyClaims> <Collateral3rdPartyClaimsCurrency>Currency code of the value of third party priority claims against the collateral</Collateral3rdPartyClaimsCurrency> <CollateralAllocValue>Collateral allocated value</CollateralAllocValue> <CollateralAllocValueCurrency>Currency code of the collateral allocated value</CollateralAllocValueCurrency> <CollateralMaturityDate>Collateral end date</CollateralMaturityDate>
</Collateral> … <Collateral>…</Collateral> </CollateralList> </Credit> </Message> 7.29.2 Description of data used in the element Name Description Format Customer's obligations identifier; Customer's obligations identifier; C35 Type of the customer's obligations From the code list. Shall be omitted if the type of operation is D N2 or N3 7.39.3 Person description element 7.3.1.9.3.1. The structure of the person description element depends on the person type and the resident type. 7.3.2.9.3.2. The structure of the description element of a resident legal person <Borrower> <ResidentType>Resident type</ResidentType> <RegNumber>Uniform registration number</RegNumber> <InvestmentFundID>Fund identifier</InvestmentFundID> <CustomerDefaultStatus>Default status of the customer</CustomerDefaultStatus> <CustomerDefaultStatus>Date of the default status of the customer</CollateralValueDate> </Borrower> 7.3.3.9.3.3. The structure of the description element of a non-resident legal person <Borrower> <ResidentType>Resident type</ResidentType> <Country>Code of the country of registration</Country> <RegNumberN>Registration number</RegNumberN> <RegNumType>Type of registration number</RegNumType> <InvestmentFundID>Fund identifier</InvestmentFundID> <RegDate>Registration date</RegDate> <NameJP>Name</NameJP> <LegalForm>Legal form</LegalForm> <AddressStreet>Registered address – street</AddressStreet> <AddressCity>Registered address – administrative territory</AddressCity> <AddressPostalCode>Registered address – postal code</AddressPostalCode> <AddressPostBox> Registered address – post box</AddressPostBox> <Category>Category</Category> <EconomicSector>Sector of the economy (according to NACE 2.0)</EconomicSector> <EconomicSector2_1>Sector of the economy (according to NACE 2.1)</EconomicSector2_1> <LegalStatus>Status of legal proceedings</LegalStatus><LegalStatusDate>Date of the legal proceedings status</LegalStatusDate> <CustomerDefaultStatus>Default status of the customer</CustomerDefaultStatus> <CustomerDefaultStatus>Date of the default status of the customer</CustomerDefaultStatusDate></Borrower> </Borrower>
7.3.4.9.3.4. Description of data used in the element
Name Description Format
Category From the code list N2
IV. File of the persons involved in credit exposures
8.10. The prefix of the file name shall be "krf".
9.11. Unless otherwise stipulated in the present description, information to be provided
shall comply with the description and format stated in Register Formats and Structure.
10.12. File structure
11.13. Header element of the file
11.113.1 Structure of the header element of the file
<FileType>T</FileType>
</Header> 15.217.2 Description of data used in the element Name Description Format Identifier of the Register participant Uniform registration number N11 Data subject BIC of the Register participant's branch C8 Date The date when the identification data correction file on the persons involved in credit exposures is prepared YYYY-MM-DD 15.317.3 Message element 15.3.1.17.3.1. Structure of the message element <Message> <Header> <MessageType>T</MessageType> <MessageID>Message identifier</MessageID> </Header> <Substitution> <PersonFrom>Current person description element</PersonFrom> <PersonTo>New person description element</PersonTo> </Substitution> </Message> 15.3.2.17.3.2. The person description element referred to in Paragraph 17.3.1 shall be prepared in line with Paragraph 9.3, replacing the name of the element "Borrower" with "PersonFrom" and "PersonTo" respectively without indicating the data Default status of the customer, Date of the default status of the customer, Category, Sector of the economy (according to NACE 2.0, Sector of the economy (according to NACE 2.1, Status of legal proceedings and Date of the legal proceedings status. Description of the data used in the element Name Description Format Message identifier Unique identifier assigned by a Register participant within the file C16 VI. Reply file 16.18. The prefix of the file name shall be "kra". 17.19. The format and structure of the reply file are described in Register Formats and Structure.Note from RegAlert. AI assistants can read this document in full, and search 70,000+ more, through the RegAlert MCP connector (https://mcp.regalert.today/mcp). Free with an account. How to connect ChatGPT, Claude or Cursor.
Source: Financial and Capital Market Commission Latvia — original document · Summary generated with machine assistance and reviewed before publication; the authoritative text is the regulator's original document. How RegAlert works
More like this from FCMC
FCMC published 1 document in the last 30 days. We email you each new one the day it's published.