Unofficial translation 20 Appendix 8€¦ · Formats and Structure of Credit Register Files and Web...

Unofficial translation 20

Appendix 8

to the Bank of Latvia Regulation No. 64

of 18 October 2010

Formats and Structure of Credit Register Files and Web Services

I. Notation used

1. Notations

Notation Explanation

N Value is a positive number.

C Value is a combination of characters. Characters to be used are '0'–'9', 'A'–'Z',

'a'–'z', capital and small letters of the Latin alphabet (including Latvian letters

with diacritical marks), Space symbols, '–', '+', '.', ',', '&', '*', '_', '(', ')', ''', ':', '%',

';' and '/'.

Cn Value as in C format; maximum length of the value is n characters.

Nm Value is a positive number with a maximum length of m characters.

YYYY-MM-

DD

Value is expressed as the date in the format YYYY-MM-DD where:

YYYY – four digit number of the year;

MM – double digit number of the month (from 01 to 12);

DD – double digit number of the day (from 01 to 31).

HH.MM:SS Value is expressed as time in the format HH.MM:SS, where:

HH – hours (from 00 to 23);

MM – minutes (from 00 to 59);

SS – seconds (from 00 to 59).

Cn or Nn Value as in C or N, and the length of the value is exactly n characters.

II. File exchange using the file exchange service

2. After encrypting and digital signing of the prepared files, the participant shall insert them in

the KREG/OUT catalogue of the file exchange service. After encrypting and digital signing of

the reply files, the Bank of Latvia shall insert them in the KREG/IN catalogue of the file

exchange service.

III. Data submission file

3. The format of data submission file name is krkyymmddnnnnnn.ext or

krkyymmddnnnnnn.xml.ext, where:

yymmdd – the date when the file is prepared;

nnnnnn – file sequence number on the day when the file was prepared, starting the numbering

with 000001;

ext – encrypted and digitally signed file extension ("ent" or "p7m").

4. Data submission file structure

<?xml version="1.0" encoding="Windows-1257"?>

<KRFile>

<Header>Header element of a file (see Paragraph 6 herein)</Header>

<KRMessages>

<Message>Message element</Message>

…


<Message>Message element</Message>

</KRMessages>

</KRFile>

5. In the message element, a message identifying obligations (see Paragraph 7 herein), a

delayed payment message (see Paragraph 8 herein), a delayed payment settlement message

(see Paragraph 9 herein) or violation message (see Paragraph 10 herein) shall be indicated.

6. Header element of a file

6.1 The structure of the file header element

<Header>

<BIC>Identifier of a participant</BIC>

<Messages>Number of messages</Messages>

<Prepared>Date</Prepared>

<FileType>File type</FileType>

</Header>

6.2 Description of the data included in the file header element

Data name Description Format Value

Identifier of a

participant

First four characters of the Credit

Register participant's bank BIC or the

registration number of a company

having close links with the bank, an

insurer or a credit union

C4 or N11

Number of messages Number of messages in a file. The

number of messages may not exceed 10

000 in a file.

N5

Date The date when the file is prepared. YYYY-MM-

DD

File type Data submission file C1 "K"

7. Message identifying obligations

7.1 When submitting and modifying the data, the structure of the message identifying

obligations is as follows (upon cancelling the message, the element BorrowerList is not

indicated).

<Message>

<Header>Header element (see Sub-paragraph 7.2 herein)</Header>

<BorrowerList>

<Borrower>Person description element (see Sub-paragraph 7.3

herein)</Borrower>

…

<Borrower>Person description element</Borrower>

</BorrowerList>

<Credit>Obligations description element (see Sub-paragraph 7.4 herein)</Credit>

</Message>

7.2 Header element

7.2.1 The structure of the header element

<Header>


<MessageType>Message type</MessageType>

<Operation>Type of operation</Operation>

</Header>

7.2.2 Description of data used in the header element


Message type Message identifying

obligations

C1 "S"

Type of operation C1 "N" – message input;

"E" – message

modification;

"D" – message

cancellation

7.3 Person description element

7.3.1 The structure of the person description element depends on the person type and the

resident type.

7.3.2 The structure of the description element of a resident natural person

<Borrower>

<PersonType>Person type</PersonType>

<ResidentType>Resident type</ResidentType>

<PersonCode>Person's identity number</PersonCode>

<Name>Name</Name>

<Surname>Surname</Surname>

<Income>Amount of income</Income>

<PeriodList>

<Period>

<Status>Status</Status>

<IndividualDateFrom>Date of the individual borrower/borrower guarantor's

obligations taking effect</IndividualDateFrom>

<IndividualDateTo>End date of the borrower/borrower guarantor's

obligations</IndividualDateTo>

<GuaranteeAmount>Amount of the borrower guarantor's

obligations</GuaranteeAmount>

<GuaranteeCurrency>Currency code of the borrower guarantor's

obligations</GuaranteeCurrency>

</Period>

…

<Period>..</Period>

</PeriodList>

</Borrower>

7.3.3 The structure of the description element of a non-resident natural person

<Borrower>



<DocNumber>Number of the travel document valid for entering the Republic of

Latvia</DocNumber>

<Country>Code of the country issuing the document valid for entering the Republic of

Latvia</Country>


<BirthDate>Birth date</BirthDate>

<PersonCodeN>Person's identity number</PersonCodeN>

<Name>Name</Name>

<Surname>Surname</Surname>

<Income>Amount of income</Income>

<PeriodList>

<Period>




<IndividualDateTo>End date of the individual borrower/borrower guarantor's




<GuaranteeCurrency>Currencies of the borrower guarantor's


</Period>

…

<Period>..</Period>

</PeriodList>

</Borrower>

7.3.4 The structure of the description element of a resident legal person

<Borrower>



<RegNumber>Uniform registration number</RegNumber>

<NameJP>Name</NameJP>

<PeriodList>

<Period>










</GuaranteeCurrency>

</Period>

…

<Period>..</Period></PeriodList>

<Category>Category</Category>

</Borrower>

7.3.5 The structure of the description element of a non-resident legal person

<Borrower>



<Country>Code of the country of registration</Country>


<RegNumberN>Registration number</RegNumberN>

<RegDate>Registration date</RegDate>

<NameJP>Name</NameJP>

<Address>Registered address</Address>

<PeriodList>

<Period>









obligations</GuaranteeCurrency></GuaranteeCurrency>

</Period>

…

<Period>..</Period>

</PeriodList>

<Category>Category</Category>

</Borrower>

7.3.6 Description of the data used in the person description element


Person type C1 "F" – natural

person;

"J" – legal person

Resident type C1 "R" – resident;

"N" – non-

resident

Person's identity number Resident's identity

number

Non-resident's

identity number

N6-N5

C40

Name C40

Surname C40

Number of the travel

document valid for entering

the Republic of Latvia

C40

Date of birth YYYY-MM-DD

Uniform registration number N11 or N9

Name C254

Code of the country of

registration

C2 From the standard


Code of the country issuing

the travel document valid for

entering the Republic of

Latvia


Registration number C100

Registration date YYYY-MM-DD

Registered address C254

Amount of income N15.N2

Status C1 "B" – borrower;

"G" – guarantor

Date of the individual

borrower/borrower

guarantor's obligations taking

effect

YYYY-MM-DD

End date of the individual

borrower/borrower

guarantor's obligations

YYYY-MM-DD

Amount of the borrower

guarantor's obligations

N15.N2

Currency code of the

borrower guarantor's

obligations


Category N2 From the

classificator

7.4 Obligations description element

7.4.1 Element structure

<Credit>

<CreditID>Identifier of the borrower's obligations</CreditID>

<CreditType>Type of the borrower's obligations</CreditType>

<EconomicSector>Sector of the economy</EconomicSector>

<ValidFrom>Date of the borrower's obligations taking effect</ValidFrom>

<Term>End date of the borrower's obligations</Term>

<Amount>Amount of borrower's obligations</Amount>

<Currency>Currency code of borrower's obligations</Currency>

<InterestRate>Type of interest rate</InterestRate>

<Syndicate>Indication of a syndicated loan</Syndicate>

<TrustLoan>Indication of a trust loan</TrustLoan>

<Losses>Amount of losses</Losses>

<CollateralList>

<Collateral>

<CollateralType>Type of collateral</CollateralType>

<CollateralAmount>Value of collateral</CollateralAmount>

<CollateralCurrency>Currency code of

collateral</CollateralCurrency>

</Collateral>

…


<Collateral> …</Collateral>

</CollateralList>

</Credit>

7.4.2 Description of data used in the element


Identifier of the

borrower's obligations

C35

Type of the borrower's

obligations

N2 or N3 From the

classificator

Sector of the economy Not indicated if the

type of operation is

D

C5 From the

classificator

Date of the borrower's

obligations taking effect

Not indicated if the


D

YYYY-MM-DD

End date of the




D

YYYY-MM-DD

Amount of the


N15.N2




Type of interest rate Not indicated if the


D

C1 "F" – fixed interest

rate;

"M" – floating

interest rate

Indication of a

syndicated loan



D

C1 "S" – a syndicated

loan has been

granted

Indication of a trust loan Not indicated if the


D

C1 "T" – a trust loan has

been granted

Amount of losses Not indicated if the


D

N15.N2

Type of collateral Not indicated if the


D

N2 or N3 From the

classificator

Value of collateral Not indicated if the


D

N15.N2

Currency code of

collateral



D



8. Delayed payment message

8.1 When submitting and modifying the data, the structure of the delayed payment

message is as follows (upon cancelling the message, the element Borrower is not

indicated).

<Message>



<Borrower>Person description element (see Sub-paragraph 8.4 herein)</Borrower>

</Message>

8.2 Header element


<Header>


<MessageID>Debtor information identifier</MessageID>


</Header>



Message type Delayed payment message C1 "N"

Debtor information

identifier

If the type of operation is E or

D, the debtor information

identifier of the respective

message subject to

modification or cancellation is

indicated.

C16


"E" – message

modification;

"D" – message

cancellation


8.3.1 The structure of the obligations description element

<Credit>


<MKDate>Date of delayed payment</MKDate>

</Credit>



Identifier of the borrower's

obligations

C35

Date of delayed payment YYYY-MM-DD


8.4 Person description element

8.4.1 For the description of data used in the element see Sub-paragraph 7.3 herein.

8.4.2 The structure of the person description element depends on the person type and the

resident type.

8.4.3 The structure of the description element of a resident natural person

<Borrower>



<PersonCode>Person's identity number</PersonCode>

</Borrower>

8.4.4 The structure of the description element of a non-resident natural person

<Borrower>



<DocNumber>Number of the travel document valid for entering the Republic of

Latvia</DocNumber>

<Country>Code of the country issuing the document valid for entering the Republic of

Latvia</Country>

<BirthDate>Birth date</BirthDate>

<PersonCodeN>Person's identity number</PersonCodeN>

</Borrower>

8.4.5 The structure of the description element of a resident legal person

<Borrower>



<RegNumber>Uniform registration number</RegNumber>

</Borrower>

8.4.6 The structure of description element of a legal person non-resident

<Borrower>



<Country>Code of the country of registration</Country>

<RegNumberN>Registration number</RegNumberN>

<RegDate>Registration date</RegDate>

</Borrower>

9. Delayed payment settlement message

9.1 The structure of the delayed payment settlement message:

<Message>



</Message>

9.2 Header element


<Header>




<MessageIDCO>Related identifier of debtor information </MessageIDCO>


</Header>



Message type Delayed payment

settlement message

C1 "P"

Debtor information

identifier

If the type of operation is E

or D, the debtor information

identifier of the respective

message subject to

modification or cancellation

is indicated.

C16

Related identifier of

debtor information

Debtor information

identifier from the

respective delayed payment

message

C16


"E" – message

modification;

"D" – message

cancellation



<Credit>


<MKIDate>Delayed payment settlement date</MKIDate>

</Credit>



Identifier of the


C35

Delayed payment

settlement date

YYYY-MM-DD

10. Violation message

10.1 When submitting and modifying the data, the structure of the violations message is

as follows (upon cancelling the message, the element Borrower is not indicated).

<Message>




<Borrower>Person description element (see Sub-paragraph 8.4 herein)</Borrower>

</Message>

10.2 Header element


<Header>




</Header>



Message type Violation message C1 "V"

Debtor information

identifier

If the type of operation is

E or D, the debtor

information identifier of

the respective message

subject to modification or

cancellation is indicated.

C16

Type of operation C1 "N" – message

input;

"E" – message

modification;

"D" – message

cancellation



<Credit>


<ViolationMark>Violation type</ViolationMark>

<Violation73>Type of violation of provisions of Article 73 of the Law "On Credit

Institutions"</Violation73>

<ViolationInfo>Description of any other significant violation of the

agreement</ViolationInfo>

<ViolationDate>Date of violation of provisions of Article 73 of the Law "On Credit

Institutions" /Date of other significant violation of the agreement</ViolationDate>

</Credit>



Identifier of the borrower's

obligations

C35


Violation type C1 "K" – violation of

provisions of Article 73

of the Law "On Credit

Institutions";

"C" – other material

violation of the

agreement

Type of violation of provisions

of Article 73 of the Law "On

Credit Institutions"

C2 From the classificator

Description of other significant

violation of the agreement

C254

Date of violation of provisions

of Article 73 of the Law "On

Credit Institutions" /Date of

other significant violation of the

agreement

YYYY-MM-DD

IV. Outstanding obligations file

11. The format of outstanding obligations file name is krryymmddnnnnnn.ext or

krryymmddnnnnnn.xml.ext, where:


nnnnnn – file sequence number on the day when the file is prepared, starting the numbering

with 000001;


12. The structure of the outstanding obligations file


<KRFile>


<KRMessages>

<Message>Outstanding obligations message element (see Paragraph 14

herein)</Message>

…

<Message>Outstanding obligations message element </Message>

</KRMessages>

</KRFile>



<Header>



<Year>Year</Year>

<Quarter>Quarter</Quarter>



</Header>


13.2 Description of data used in the element


Identifier of a

participant


Register participant's bank BIC or

the registration number of a company



C4 or N11

Number of messages Number of messages in a file. The

number of messages may not exceed

10 000 in a file.

N5

Year N4

Quarter N1

Date The date when the outstanding

obligations file is prepared

YYYY-MM-

DD

File type Outstanding obligations file C1 "R"

14. Outstanding obligations message element

14.1 The structure of the outstanding obligations message element

<Message>

<Header>



</Header>

<Credit>


<RemainingAmount>Amount of borrower's outstanding

obligations</RemainingAmount>

<RemainderCurrency>Currency code of the borrower's outstanding obligations

</RemainderCurrency>

<CreditClass>Classification group of the borrower's

obligations</CreditClass>

<Accruals>Special provisions for the principal of the loan</Accruals>

<AccrualsCurrency>Currency code of the special provisions for the principal of the

loan</AccrualsCurrency>

<QualityRate>Type of quality assessment of the borrower's

obligations</QualityRate>

<Delay>Delay period</Delay>

<DelayedAmount>Delayed principal of the borrower's

obligations</DelayedAmount>

<DelayCurrency>Currency code of the delayed principal of the borrower's

obligations</DelayCurrency>

<PercentageAmount>Delayed interest</PercentageAmount>

<PercentageCurrency>Currency code of the delayed

interest</PercentageCurrency>

</Credit>

</Message>




Message type Outstanding obligations

message

C1 "R"

Type of operation C1 "N" – message input

Identifier of the


C35

Amount of the

borrower's outstanding

obligations

N15.N2



obligations


Classification group of

the borrower's

obligations

N1 From the classificator

Special provisions for

the principal of the loan

N15.N2


specific provisions for

the principal of the loan


Type of quality

assessment of the


C1 "I" – individually;

"G" – grouped

Delay period N5

Delayed principal of the


N15.N2


delayed principal of the



Delayed interest N15.N2


delayed interest


V. Request file

15. The format of request file name is krpyymmddnnnnnn.ext or krpyymmddnnnnnn.xml.ext,

where:



with 000001;

ext – encrypted and digitally signed file extension ("ent"or "p7m").

16. The structure of the request file


<KRFile>


<KRQueries>

<Message>Request element (see Paragraph 18 herein)</Message>


…

<Message>Request element</Message>

</KRQueries>

</KRFile>



<Header>


<Queries>Number of request elements</Queries>



</Header>



Identifier of a

participant



the registration number of a

company having close links with

the bank, an insurer or a credit

union

C4 or N11

Number of request

elements

Number of request elements in a

request file. The number of request

elements may not exceed 10 000 in

a file.

N5

Date The date when the file is prepared YYYY-MM-DD

File type Request file C1 "P"

18. Request element

18.1 The structure of the request element

<Message>

<Header>

<MessageType>Type of the element </MessageType>

<QueryID>Request identifier</QueryID>

<ReportType>Report type</ReportType>

</Header>

<Query>Request parameter element</Query>

<Message>

18.2 If the type of the element is B, the person's description is indicated in the request

parameter element in accordance with Sub-paragraph 8.4 herein, thereby replacing the

element's name "Borrower" with the name "Query".

18.3 If the type of the element is C, the identifier of obligations is indicated in the request

parameter element.





Type of the element C1 "B" – report on

person;

"C" – on

obligations

Request identifier An identifier, unique within one

request file, and assigned by the

Credit Register's participant

C16

Report type Indication on preparing an

aggregated or a detailed report about

the person's obligations. Only

indicated, if the type of the element

is "B".

C1 "G" – aggregated

report

"D" – detailed

report

Identifier of the

borrower's

obligations

C35

VI. Reply file

19. The format of reply file is krayymmddnnnnnn.ext, where:



with 000001;


20. The structure of the reply file


<KRFile>


<KRErrors>

<Message>Message rejection element (see Paragraph 23 herein)</Message>

…

<Message>Message rejection element </Message>

</KRErrors>

</KRFile>

21. The element KRErrors is only indicated, if the data submission or outstanding obligations

file contains erroneous messages.



<Header>


<FileName>File name</FileName>

<Errors>Number of erroneous messages</Errors>

<ErrorCode>Error code</ErrorCode>

<ErrorText>Error description</ErrorText>

<Line>Number of erroneous line</Line>

<LinePos>Error position in a line</LinePos>


<Reason>Reason for error</Reason>



</Header>



Identifier of a

participant






C4 or N11

File name The data submission or outstanding

obligations file name without

extension, submitted by the Credit

Register's participant

C15

Number of

erroneous messages

Number of erroneous messages in the

data submission file or outstanding

obligations file. If the data

submission file or outstanding

obligations file contains no erroneous

messages or a file format error is

identified, the value is 0.

N5

Error code C4

Error description Explanatory text about the error C

Number of

erroneous line

Indicated if the file format error is

identified

N

Error position in a

line


identified

N

Reason for error Indicated if the file format error is

identified

C

Date The date when the reply file is

prepared

YYYY-MM-DD

File type Reply file C1 "A"

23. Message rejection element

23.1 The structure of the message rejection element

<Message>

<Header>

<MessageType>Type</MessageType>

<MessageID>Identifier</MessageID>

</Header>

<Error>


<Type>Type of the submitted erroneous message</Type>

<MessageIDCO>Identifier of the submitted erroneous message

</MessageIDCO>




</Error>

</Message>



Type Type of notification generated by the

system

C1 "A"

Identifier Identifier of notification generated by

the system

C16

Identifier of the

borrower's

obligations

Identifier of borrower obligations from

the participant's erroneous message

C35

Type of the

submitted erroneous

message

C1 "S" – message

identifying

obligations;

"R" –

outstanding

obligations

message;

"N" – Delayed

payment

message;

"P" – Delayed

payment

settlement

message;

"V" – Violation

message.

Identifier of the

submitted erroneous

message

Only indicated for N, P and V types of

messages

C16

Error code Error code indicated by the system C4


VII. Data retrieval file

24. The format of data retrieval file name is krzyymmddnnnnnn.ext, where:



with 000001;


25. Structure of the data retrieval file


<KRFile>


<KRReports>

<Report>Data element (see Paragraph 27 herein)</Report>


…

<Report>Data element </Report>

<QueryError>Error description element (see Paragraph 28

herein)</QueryError>

…

<QueryError>Error description element</QueryError>

</KRReports>

</KRFile>



<Header>



<Reports>Number of reports prepared</Reports>

<Errors>Number of erroneous requests</Errors>








</Header>



Identifier of a

participant



the registration number of a

company having close links with the

bank, an insurer or a credit union

C4 or N11

File name The request file name without

extension, submitted by the

participant

C15

Number of reports

prepared

Number of reports prepared by the

system

N5

Number of

erroneous requests

Number of erroneous requests in a

request file

N5

Error code C4


Number of

erroneous line


identified

N

Error position in a

line


identified

N


identified

C

Date Date when the data retrieval file is

prepared

YYYY-MM-DD


File type Data retrieval file C1 "Z"

27. Data element

27.1 The structure of the data element

<Report>


<Query>Request parameter element</Query>

<KRMessages>Report message element (see Sub-paragraph 27.4

herein)</KRMessages>

</Report>

27.2 Request parameter element contains information on request parameters from the

request file (see Paragraph 18 herein).

27.3 Header element


<Header>

<ReportType>Report type</ReportType>

<ReportID>Report registration number</ReportID>


<PreparedDate>Date of preparing a report</PreparedDate>

<PreparedTime>Date of preparing a report</PreparedTime>

<QueryUserName>Name of the authorised representative of a person requesting the

data</QueryUserName>

<QueryUserSurname>Surname of the authorised representative of a person

requesting the data</QueryUserSurname>


<TotalRemainder>Outstanding obligations</TotalRemainder>

</Header>



Report type The feature of the report type C1 "G" – aggregated

report on a

person

"D" – detailed

report on person;

"C" – report on

obligations

Report registration

number

Report registration number assigned

by the system

C16

Request identifier Identifier of the related request from

the participant's request file

C16

The date of

preparing a report

YYYY-

MM-DD

Time of preparing

a report

HH.MM:SS


Name of the

authorised

representative of a

person requesting

the data

C

Surname of the

authorised

representative of a

person requesting

the data

C

Number of

messages

Number of messages prepared by the

system in the element KRMessages

N5

Outstanding

obligations

Valid total outstanding obligations of

the borrower in lats. Indicated if the

report type is G.

N15.N2

27.4 Report message element

27.4.1 The structure of the report message element

<KRMessages>

<Message>Message</Message>

…

<Message>Message</Message>

</KRMessages>

27.4.2 Depending on the indication of the report type (G, D or C) specified in the request, the

aggregated report on person messages (see Sub-paragraph 27.4.3 herein), the detailed report

messages on person (see Sub-paragraph 27.4.4 herein) or the obligations report messages (see

Sub-paragraph 27.4.5 herein) are included in the report messages element.

27.4.3 Aggregated report message

27.4.3.1 The structure of the aggregated report message

<Message>

<Header>


</Header>

<Credit>


<CreditType>Type of the borrower's obligations</CreditType>

<ValidFrom>Date of the borrower's obligations taking effect</ValidFrom>

<Term>End date of the borrower's obligations</Term>

<Amount>Amount of borrower's obligations</Amount>

<Currency>Currency code of borrower's obligations</Currency>

<RemainingAmount>Amount of borrower's outstanding

obligations</RemainingAmount>

<RemainderCurrency>Currency code of the borrower's outstanding

obligations</RemainderCurrency>

<RemainderLVL>Amount of the borrower's outstanding obligations in

lats</RemainderLVL>

<BorrowerCount>Number of borrowers</BorrowerCount>

<GuarantorCount>Number of borrower guarantors</GuarantorCount>

<MKCount>Number of delayed payment messages</MKCount>


<MKStatus>Indication of delayed payment validity status</MKStatus>

<ViolationCount>Number of violation messages</ViolationCount>

<Historical>Type of the settled obligations</Historical>

</Credit>

</Message>

27.4.3.2 Description of data used in the element


Message type Type of the message

prepared by the system

C1 "G"

Status Indication of the person's

status

C1 "B" –

borrower;

"G" –

guarantor

Type of the borrower's

obligations

N2 or N3 From the

classificator

Date of the borrower's

obligations taking effect

YYYY-MM-DD

End date of the


YYYY-MM-DD

Amount of the


N15.N2



C3 From the

standard

Amount of the


obligations

N15.N2



obligations

C3 From the

standard

Amount of the


obligations in lats

N15.N2

Number of borrowers N

Number of borrower

guarantors

N

Number of delayed

payment messages

N5

Indication of delayed

payment validity status

Data contain value K, if a

delayed payment message

has been last registered for a

person. Data are not

indicated, if a delayed

payment settlement message

has been last registered for a

person.

C1 "K"

Number of violation

messages

N5


Type of the settled

obligations

Data contain value H, if the

obligations are settled.

C1 "H"

27.4.4 Detailed report message

27.4.4.1 The structure of the detailed report message

<Message>

<Header>



<MessageIDCO>Related identifier of debtor information</MessageIDCO>



<Historical>Type of the settled obligations</Historical>

<Year>Year<Year>

<Quarter>Quarter<Quarter>

<Registered>Message registration date</Registered>

<RegisteredBy>Identifier of a participant</RegisteredBy>

</Header>

<Borrower>Person description element</Borrower>

<Credit>Obligations description element</Credit>

</Message>

27.4.4.2 The person description element is only indicated for the S type messages. For the

description of element see Sub-paragraph 7.3 herein.

27.4.4.3 Obligations description element

Message type Obligations

description format

Notes

S See Sub-paragraph

7.4 herein

The data Identifier of the borrower obligations,

the Amount of losses and Indication of a trust loan

of the Obligations description element and the

data Value of collateral and Currency code of

collateral of the element CollateralList are only

indicated, if the data request submitter has also

been the data submitter.

N See Sub-paragraph

8.3 herein

P See Sub-paragraph

9.3 herein

V See Sub-paragraph

10.3 herein

R See Paragraph 14

herein

If the data request submitter has not also been the

data submitter, the data Amount of the borrower's

outstanding obligations and Currency code of the

borrower's outstanding obligations, are only

indicated in the element of outstanding obligations

messages.


27.4.4.4 Description of the data used in the obligations description element


Message type Type of the message of the

obligations description element

C1 "S" – message

identifying

obligations;

"R" – outstanding

obligations

message;

"N" – Delayed

payment

message;

"P" – Delayed

payment

settlement

message;

"V" – Violation

message.

Debtor

information

identifier

Indicated for N, P and V types of

messages only if the data request

submitter is also the data

submitter.

C16

Related identifier

of debtor

information

Debtor information identifier from

the respective delayed payment

message. Indicated for P type

messages only if the data request

submitter is also the data

submitter.

C16

Number of

borrowers

Indicated for S type of messages

only.

N

Number of

borrower

guarantors

Indicated for S type of messages

only.

N

Type of the

settled

obligations

Data contain value H, if the

obligations are settled.

C1 "H"

Year The year of outstanding

obligations quarter. Indicated for R

type of messages only.

YYYY

Quarter The quarter of outstanding

obligations. Indicated for R type of

messages only.

N1

Message

registration date

YYYY-MM-

DD

Identifier of a

participant

If the data request submitter is the

data submitter, the data contain the

first four characters of the bank's

BIC or the registration number of

a company having close links with

the bank, an insurer or a credit

C4, N11 or C


union. Otherwise, the data contain

the respective indication about the

request submitter: "Bank",

"Associated company", "Insurer"

or "Credit Union".

27.4.5 Message on the obligations report

27.4.5.1 The structure of the message on the obligations report

<Message>

<Header>



<MessageIDCO>Related identifier of debtor information </MessageIDCO>



<Year>Year<Year>

<Quarter>Quarter<Quarter>

<Registered>Message registration date</Registered>

</Header>

<BorrowerList>Person description element</BorrowerList>

<Credit>Obligations description element</Credit>

</Message>

27.4.5.2 For the S type messages, all borrowers and guarantors are indicated in the person

description element. The person, to whom this message applies, has to be indicated in

the messages of other types. For the person description see Sub-paragraph 7.3 herein.

27.4.5.3 Description of data used in the element


Message type C1 "S" – message

identifying

obligations;

"R" –

outstanding

obligations

message;

"N" – Delayed

payment

message;

"P" – Delayed

payment

settlement

message;

"V" –

Violation

message.

Debtor information

identifier

Indicated for N, P and V

types of messages only.

C16


Related identifier of

debtor information

Debtor information

identifier from the

respective delayed

payment message.

Indicated for P type of

messages only.

C16

Number of borrowers N

Number of borrower

guarantors

N

Year The year of outstanding

obligations quarter.

Indicated for R type of

messages only.

YYYY

Quarter The quarter of outstanding

obligations. Indicated for

R type of messages only.

N1

Message registration

date

YYYY-MM-DD

28. Error description element

28.1 The structure of the error description element

<QueryError>

<Header>

<MessageType>Type of the element </MessageType>

<MessageID>Identifier of a notice</MessageID>

</Header>

<Query>Request element</Query>

<Error>




</Error>

</QueryError>

28.2 Request element contains information from the person description element of the

participant's request file (see Paragraph 18 herein).



Type of the

element

Element comprising a notice of erroneous

request rejection

C1 "A"

Message identifier Identifier generated by the system C16

Request identifier Identifier of the respective erroneous

request from the request file

C16

Error code C4

Error description C


VIII. Loan portfolio request file

29. The format of loan portfolio request file name is krqyymmddnnnnnn.ext or

krqyymmddnnnnnn.xml.ext, where:


nnnnnn – file sequence number on the day when the file is prepared, starting the

numbering with 000001;

ext – encrypted and digitally signed file extension ("ent"or "p7m").

30. The structure of the loan portfolio request file


<KRFile>


<Query>Request element (see Paragraph 32 herein)</Query>

</KRFile>


31.1 Element structure

<Header>



</Header>



Identifier of a

participant





insurer or a credit union.

C4 or N11

File type C1 "Q"

32. Request element

32.1 Element structure

<Query>

<CreditStartFrom>The first date of a period of time from which the obligations take

effect</CreditStartFrom>

<CreditStartTo>The last date of a period of time from which the obligations take

effect</CreditStartTo>

<RegisteredFrom>Registration period commencement date</RegisteredFrom>

<RegisteredTo>Registration period end date</RegisteredTo>

<ModifiedFrom>Commencement date of the last modification</ModifiedFrom>

<ModifiedTo>End date of the last modification</ModifiedTo>

</Query>


32.2 Any of the following periods shall be indicated in the request file: period of time

within which the obligations take effect (The first date of period of time from which the

obligations take effect and The last date of a period of time on which the obligations take

effect) or the period of time for registering obligations (Registration period

commencement date and Registration period end date), or the period of time for

modifying obligations (Commencement date of the last modification and End date of the

last modification).



The first date of a

period of time from

which the

obligations take

effect

The first date of a period of time

where the date of the obligations

taking effect falls within.

YYYY-MM-DD

The last date of a

period of time from

which the

obligations take

effect

The last date of a period of time where

the date of the obligations taking

effect falls within. Should be

indicated, if the data The first date of a

period of time from which the

obligations take effect have been

indicated.

YYYY-MM-DD

Registration period

commencement date


where the date of the registration of

obligations falls within.

YYYY-MM-DD

Registration period

end date


the date of the registration of

obligations falls within. Should be

indicated, if the data Registration

period commencement date have been

indicated.

YYYY-MM-DD

Commencement date

of the last

modification


where the date of the last modification

of obligations falls within.

YYYY-MM-DD

End date of the last

modification


the date of the last modification of

obligations falls within. Should be

indicated, if the data Commencement

date of the last modification have been

indicated.

YYYY-MM-DD

IX. Loan portfolio report file

33. The format of loan portfolio file name is krsyymmddnnnnnn.ext, where:



with 000001;



34. The structure of the loan portfolio request file


<KRFile>


<Query>Request element</Query>

<Credits>Obligations element (see Paragraph 37 herein)</Credits>

</KRFile>

35. Request element includes information from the loan portfolio request file of the request

element (see Paragraph 32 herein).



<Header>



<Credits>The number of the selected obligations</Credits>








</Header>



Identifier of a

participant






C4 or N11

File name The request file name without

extension, submitted by the participant

C15

The number of the

selected

obligations

The number of obligations selected

according to the periods stated in the

loan portfolio request file. Not

indicated, if an error has occurred in the

request file.

N

Error code C4


Number of the

erroneous line


identified.

N

Error position in a

line


identified.

N


identified.

C


Date Date of preparing a loan portfolio

report file

YYYY-MM-DD

File type Loan portfolio report file C1 "S"

37. Obligations element

37.1 Data on the selected obligations are indicated in the obligations element. Each line

comprises one unit of obligations' data.

37.2 The structure of the obligations description

<Credit ID=Identifier of_obligations StartDate=Date of the obligations taking effect

EndDate=End date of obligations Registered=Obligations registration date

LastModified=Date of the last modification of obligations Remainder=Outstanding_

obligations Currency=Currency code of the outstanding obligations Period=Quarter of

outstanding obligations />



Identifier of obligations C35

Date of obligations taking

effect

YYYY-MM-DD

End date of obligations YYYY-MM-DD

Obligations registration

date

YYYY-MM-DD

Date of the last

modification of

obligations

YYYY-MM-DD

Outstanding obligations The latest submitted amount of

the outstanding obligations. If the

outstanding amount has not been

submitted, the value of the field is

empty.

N15.N2

Currency code of

outstanding obligations

Currency code of outstanding

obligations. If the outstanding

amount has not been submitted,

the value of the field is empty.

C3

Quarter of outstanding

obligations

Quarter of the latest submitted

amount of the outstanding

obligations. If the outstanding

amount has not been submitted,

the value of the field is empty.

YYYY/N1


X. Obligations assumption file

38. The format of obligations assumption file name is krcyymmddnnnnnn.ext. where:


nnnnnn – a unique number;


39. The structure of obligations assumption file

<?xml version="1.0" encoding="windows-1257"?>

<CessionList OrgFrom="Identifier of a participant–transferor of obligations"

OrgTo="Identifier of a participant assuming obligations">

<Cession CreditIdFrom="Current identifier of the borrower's obligations"

CreditIdTo="New identifier of the borrower's obligations">

<Message MsgIdFrom="Current identifier of debtor information"

MsgIdTo="New identifier of debtor information"/>

…

</Cession>

…

</CessionList>

39.1 Description of data used


Identifier of a

participant






C4 vai N11

Identifier of the

borrower's

obligations

C35

Identifier of

debtor information

C16

XI. Information request using the web service function

40. Data exchange takes place via SOAP messages using HTTP protocol. Encrypting of data

is ensured at the level of individual messages in accordance with the Web Services Security

specification.

41. Information requests are provided by the function QueryData (queryType: <string>,

query:<string>):<string>.

41.1 The parameter queryType of the function QueryData indicates the type of the

request and may have the following value: "G" – aggregated report on a person, "D" –

detailed report on a person, "C" – report on obligations.

41.2 The value of the parameter query is indicated in accordance to the type of the

request. The parameter value is identifier of a person or of obligations complying with the

XML format specified in Sub-paragraphs 18.2 and 18.3 herein.


41.3 A string of XML format symbols is generated as a result of request satisfaction.

<Report>

<KRMessages>Message element (see Sub-paragraph 27.4 herein)</KRMessages>

<Error>Description of request error<Error>

</Report>

41.4 If the format of the parameter queryType and query has been correct, the section

<KRMessages> is prepared and the section <Error> is omitted; otherwise, only the

section <Error> is prepared.

Governor of the Bank of Latvia I. Rimšēvičs

Date post:	17-Jul-2020
Category:	Documents
Upload:	others
View:	0 times
Download:	0 times

Unofficial translation 20 Appendix 8€¦ · Formats and Structure of Credit Register Files and Web...

Documents