technical documentation - reporting functions - reporting v1.4... · 2011-11-04 · technical...

CENTRAL CORPORATE CREDIT REGISTER

Technical Documentation - Reporting functions

Chapter "Description of the action codes and validation rules"

Version 1.4 - 02/11/2011

CENTRAL CORPORATE CREDIT REGISTER Technical Documentation - Reporting functions - Chapter "Description of the action codes and validation rules"

Version 1.4 - 02/11/2011

Table of contents

1. INTRODUCTION ........................................................................................ 7

1.1 PURPOSE OF DOCUMENT...................................................................... 7

1.2 CONTENT OF DOCUMENT ...................................................................... 7

1.3 DEFINITIONS ........................................................................................ 7

1.4 REFERENCES ...................................................................................... 8

1.5 HISTORY OF DOCUMENT ....................................................................... 8

2. GENERAL INFORMATION ON A REPORT ................................................ 9

2.1 MONTHLY REPORTING .......................................................................... 9

2.2 REPORT CONTENT .............................................................................. 9

2.3 ADMINISTRATION PART OF A REPORT .................................................... 9

2.4 PROCESSING ..................................................................................... 10

2.5 XML ELEMENTS USED IN THE REPORTING ............................................ 10

2.6 CODES USED IN THE REPORTING......................................................... 10

3. GENERAL INFORMATION ON THE ACTION CODES ............................. 11

3.1 ACTION CODES REGARDING DEBTORS ................................................. 11

3.2 ACTION CODES REGARDING CREDITS .................................................. 11

3.3 REMARK............................................................................................ 12

4. DESCRIPTION OF A REPORT ................................................................ 13

4.1 INTRODUCTION .................................................................................. 13

4.2 ROOT ELEMENTS: DEBTORS_REPORT AND CREDITS_REPORT .... 14

4.2.1 Root element: DEBTORS_REPORT .................................................... 14

4.2.2 Root element: CREDITS_REPORT ..................................................... 14

4.2.3 ADMINISTRATION element ................................................................. 15


Version 1.4 - 02/11/2011

5. DEB ACTION CODE ................................................................................. 16

5.1 GENERAL DESCRIPTION ...................................................................... 16

5.1.1 Purposes of the action code................................................................. 16

5.1.2 Data to be reported .............................................................................. 16 5.1.2.1 Individual debtors, codebtors and associations ................................ 16

5.1.2.2 Reporting date and frequency of reporting ....................................... 17

5.1.2.3 Identification number ....................................................................... 18

5.1.2.4 Free texts ........................................................................................ 18

5.1.2.5 ID data by type of debtors ................................................................ 18

5.1.3 Specific conditions of validation ........................................................... 20 5.1.3.1 Update of non official id data ............................................................ 20

5.1.3.2 Not active debtor ............................................................................. 21

5.1.3.3 Deceased resident natural persons .................................................. 21

5.1.3.4 Debtor already reported but without credit anymore ......................... 21

5.1.3.5 Debtors out of the reporting scope but present in associations ......... 22

5.2 DESCRIPTION OF THE ELEMENTS ......................................................... 23

5.2.1 SINGLE_DEBTOR .............................................................................. 24

5.2.1.1 RESIDENT_LEGAL_ENTITY ........................................................... 24

5.2.1.2 NON_RESIDENT_LEGAL_ENTITY ................................................. 26

5.2.1.3 RESIDENT_NATURAL_PERSON ................................................... 27

5.2.1.4 NON_RESIDENT_NATURAL_PERSON .......................................... 28

5.2.2 ASSOCIATION .................................................................................... 29

6. DELDEB ACTION CODE .......................................................................... 31


6.1.1 Purpose of the action code .................................................................. 31

6.1.2 Data to be reported .............................................................................. 31

6.1.3 Associations ........................................................................................ 31

6.1.4 Debtor in association ........................................................................... 31

6.1.5 Processing of the action code .............................................................. 32

6.1.6 Deleted debtor to be reported later ...................................................... 32


7. MODIDDEB ACTION CODE ..................................................................... 34




7.1.3 Associations ........................................................................................ 34


8. CRED ACTION CODE .............................................................................. 36


Version 1.4 - 02/11/2011

8.1 GENERAL DESCRIPTION...................................................................... 36



8.1.2.1 Reporting date ................................................................................. 36

8.1.2.2 Debtor identification ......................................................................... 36

8.1.2.3 Credit data ....................................................................................... 37

8.1.2.4 Risk data ......................................................................................... 37

8.1.3 Rules of reporting ................................................................................ 38

8.1.4 Use of CRED in case of delayed reporting ........................................... 39

8.2 DESCRIPTION OF THE ELEMENTS ........................................................ 40

8.2.1 CRED_ITEM element .......................................................................... 40

8.2.2 RISK_PAST_DUE_DEFAULT element ................................................ 41

8.2.3 RISK_UNLIKELY_DEFAULT element .................................................. 41

8.2.4 CREDIT_DIMENSIONS element ......................................................... 42

9. CORCRED ACTION CODE ...................................................................... 43




9.1.3 Correction of a STOPCRED action code .............................................. 43


CORCRED_ITEM ELEMENT ...................................................................... 44

9.2.1 RISK_PAST_DUE_DEFAULT element ................................................ 45

9.2.2 RISK_UNLIKELY_DEFAULT element .................................................. 45

9.2.3 CREDIT_DIMENSIONS element ......................................................... 46

10. STOPCRED ACTION CODE ........................................................... 47




10.1.3 Association .......................................................................................... 47

10.1.4 Credit reporting after a STOPCRED action code .................................. 47

10.1.5 Specific cases ..................................................................................... 48


11. VALIDATION RULES ....................................................................... 50

12. MESSAGES..................................................................................... 54

12.1 WARNING MESSAGES ......................................................................... 54

12.2 ERROR MESSAGES ............................................................................ 54

13. GLOSSARY AND ABBREVIATIONS ............................................... 59

CENTRAL CORPORATE CREDIT REGISTER 7 / 60 Technical Documentation - Reporting functions - Chapter "Description of the action codes and validation rules"

1. Introduction

Version 1.4 - 02/11/2011

1. Introduction

1.1 Purpose of document This document aims at giving all the information needed by the participants of the CCCR, notably by Information Technology (IT) people which will use a file upload communication channel, to understand how they can functionaly report to the CKO2 application in order to update the database with the purpose of reflecting the credit activity of their institution according to the legal requirements and the rules defined for the partakers of the Central Corporate Credit Register (CCCR).

1.2 Content of document This document

contains general information on the reports and the actions to be carried out according to the debtor and credit situations the participant wants to report;

describes the fields of the administration section of a report as well as the fields of each action code which a report can contain and that is needed by the CKO2 application to register debtors in the database, to update some of their identification data and to register their monthly credit situation or some corrections;

gives information on how action codes can be used; contains by action code the validation rules implemented and their related messages.

1.3 Definitions Debtor is the generic term used through this document to name the persons to be reported by a participant. Credit is the generic term used through this document to name all the types of commitments to be reported between a participant and a debtor. These terms apply for all types of participants. The meaning and description of data to be reported is part of a specific document ref. [4] (in French and in Dutch).

CENTRALE DES CRÉDITS AUX ENTREPRISES 8 / 60 Technical Documentation - Reporting functions - Chapter "Description of the action codes and validation rules"

1 Introduction

Version 1.4 - 02/11/2011

1.4 References This document is a chapter being part of the Technical documentation of the reporting functions and will be included in one final document gathering all the information needed to report to the CCCR when all chapters will be in their final version agreed by the participants. This document refers to the XML schemas available in separate CKO2 documents. Ref. Title [1] Technical documentation - Reporting functions: Reporting file size and compression [2] Technical documentation - CKO2 XML elements - Description of the XML elements used in the CKO2 XML files [3] Tables of NBB codes: Description of the internal NBB codes used in the protocols [4] Description des données d'alimentation/Beschrijving van de reportinggegevens

1.5 History of document Date Version Description of change 23/04/2010 0.1 Draft version delivered to participants for reviewing 16/07/2010 1.0 Final version (effective changes with the previous version with a

possible impact on the development at the participant side or on the correct understanding of the reporting are highlighted)

10/09/2010 1.1 Change of some error message numbers + check on range of 3 to 5 digits for NACEBEL codes (see highlighted text)

13/05/2011 1.2 Order of processing of report – Some validations and error messages - Some other minor changes

28/06/2011 1.3 DELDEB action when the debtor is a codebtor in association (2 error messages added) – Validation rule & warning msg had to be erased P29 & P44

02/11/2011 1.4 Adding of validation rule V053 and message 3136 (pages 27, 28, 53 and 57)


2. General information on a report

Version 1.4 - 02/11/2011

2. General information on a report

2.1 Monthly reporting Each month (M), within the 8 calendar days after the end of a month (M-1), each participant has to close and report the situation of all its debtors and their credits at the last day of that month (M-1). The purpose is that after all the participants have fed the database of CKO2 (in the beginning of month M), it is possible, when consulting the database, to have a global view of all the credits received by any debtor at the end of the last month (M-1) accross the whole financial system. The participant has to feed the database properly by complying with the XML schemas and by implementing the present protocol. Report and file are two synonyms in the rest of the document.

2.2 Report content A report is divided into action units which comprise one single action code and the data as to one debtor or his credits to be processed. Since each unit contains all the necessary information for its processing, monthly data to be reported can be split into several sets of units (i.e. reports) which can be sent separately1. No continuity rule (order of the action codes in the files, specific field to number the files, ...) between the several reports is imposed on the participant. Nevertheless, debtor data and credit data must be included in different files. It must be noticed that a report cannot exceed some size limits (see ref. [1]).

2.3 Administration part of a report A participant may delegate the communication of his data to another participant, then called third party participant. The third party participant acts on behalf of the other participant to send a report. Therefore, the code of the particint under the name of whom the data must be registered has to be communicated in the beginning of the report. The third party sender self is identified by its digital certificate.

1 Remark: one single unit (i.e. one action as to one debtor or as to the credits of one debtor) cannot be split into 2 reports.


2 General information on a report

Version 1.4 - 02/11/2011

The participant has also to identify his report by means of a timestamp corresponding to the creation time of the file. Finally, using the free comment field to mention their own report reference is highly recommanded to participants for two reasons:

when, for any reason, a same report is twice (or more) uploaded by the participant, the report sent a second time can be rejected by the application on the basis of the report reference;

when direct contacts between a participant and the back office of the CCCR are needed in case of problems, it could ease retrieving the reports and feedbacks produced by the National Bank of Belgium (NBB) applications (OneGate and CKO2).

2.4 Processing Reports are processed on a FIFO basis (First In, First Out) of their closing time in OneGate1. All reports on debtors are processed before those on credits (credits can only be validated and registered if they can be related to correctly identified debtors). If associations and codebtors being part of associations are not reported in the same file, the file with the codebtors must be sent before the file with the associations seeing that the files are dealt with in a FIFO order. Debtors can be accepted for registration in the database or rejected automatically and immediately by the CKO2 application or manually and later by the CCCR back office. Credit reports of a same participant are only processed in CKO2 if no debtor report of the participant remains unprocessed. Reports on debtors could possibly be processed during the day but those on credits are processed during the night only to guarantee the stability of the consultations of the database during a same day.

2.5 XML elements used in the reporting XML elements used in the reporting are described in a specific document which comprises all XML elements used through all protocols (see ref. [2]).

2.6 Codes used in the reporting Internal NBB codes used in the reporting are part of tables which are detailed in a specific document which comprises all tables of codes used through all protocols (see ref. [3]).

1 All the reports and feedbacks, whatever the channel used (A2A or U2A), go through the OneGate portal.


3. General information on the action codes

Version 1.4 - 02/11/2011

3. General information on the action codes Six action codes to be used by the participants have been developed: three regarding debtors and three their credit situation. They are all named with letters offering a mnemonic means to remember them and their function.

3.1 Action codes regarding debtors DEB: is used

o to report a new DEBtor and his identification data at the participant side, or o to bring some corrections in the non-official identification data of a DEBtor

already reported by the participant1. DELDEB: is used to DELete all the data of a DEBbtor (all credit data and, if the case, all id

data). MODIDDEB: is used to MODify the ID number of a DEBtor if this is not an official number

(Enterprise number of the Crossroads Bank of Enterprises [CBE] or number of the National Register of Natural Persons) [NRNP]).

Each action code regarding debtors contains two optional fields which the participant can freely complete for every debtor and which can prove to be useful for the CCCR or the participant self:

one for a comment about the debtor; one to let the participant the occasion to add his own debtor reference and find it back in the

feedbacks in order to automatize their processing.

3.2 Action codes regarding credits CRED: is used to report monthly the CREDit situation of a debtor at the end of a month. CORCRED: is used to bring some CORrections in a CREDit situation already reported of a

debtor for a specific month. STOPCRED: is used to mention that the participant STOPs his CREDit relation with a debtor and

that no more credit reporting must be awaited from the reporting date onwards unless, if the case, the participant extends credits to him again later on.

1 Only non official data are concerned because official data from databases run by Authorities (Crossroads Bank of Enterprises or

National Register of Natural Persons) cannot be modified in the CKO2 database.


3 General information on the action codes

Version 1.4 - 02/11/2011

Each action code regarding credits contains two optional fields which the participant can freely complete for the credit data of every debtor and which can prove to be useful for the CCCR or the participant self:

one for a comment about the debtor's credits; one to let the participant the occasion to add his own reference and find it back in the

feedbacks in order to automatize their processing.

3.3 Remark All participants have to be in state by means of the action codes to report all the information which has to be registered in the CKO2 database according to the Belgian CCCR legislation and rules. They must also be in state to process the error messages contained in the several types of feedbacks in such a way that they can re-submit their reports quickly and properly.


4. Description of a report

Version 1.4 - 02/11/2011


4.1 Introduction A report contains either action codes regarding debtors, either action codes regarding credits. The tags of their root elements are named DEBTORS_REPORT and CREDITS_REPORT. Both types of report must contain a mandatory information part (ADMINISTRATION element) and at least one child element corresponding to one action code. There can be as many occurrences as possible of the different action codes, insofar the report volume doesn't exceed the recommended limits made in the document ref. [1]. Both types of report differ about their child elements:

DEBTORS_REPORT: o DEB o DELDEB o MODIDDEB

CREDITS_REPORT: o CRED o CORCRED o STOPCRED

Child elements contain the data needed to insert, update and delete debtors and credits according to the requirements made to keep the CKO2 database coherent and reflecting the correct credit situation of the debtors as aimed at by the CCCR legislation and regulations. Each individual action code is described separately further in the present document.



Version 1.4 - 02/11/2011

4.2 Root elements: DEBTORS_REPORT and CREDITS_REPORT

Tag Description Validation rule Message

DEBTORS_REPORT Contains elements relating to actions on debtors Mandatory

XML

CREDITS_REPORT Contains elements relating to actions on credits

4.2.1 Root element: DEBTORS_REPORT

Child elements


ADMINISTRATION Contains data identifying a report Mandatory - Single XML

DEB Contains data related to a DEB action At least one of these elements is

mandatory

XML

DELDEB Contains data related to a DELDEB action

MODIDDEB Contains data related to a MODIDDEB action

4.2.2 Root element: CREDITS_REPORT

Child elements


ADMINISTRATION Contains data identifying a report Mandatory - Single XML

CRED Contains data related to a CRED action At least one of these elements is

mandatory

XML

STOPCRED Contains data related to a STOPCRED action

CORCRED Contains data related to a CORCRED action



Version 1.4 - 02/11/2011

4.2.3 ADMINISTRATION element

The values of the attributes and child elements of the element ADMINISTRATION identify a report in a sole way with:

attributes. The participant o identifies his report with a detailed timestamp corresponding to its creation time; o can include a specific comment to give its own reference to the report;

child elements. The report must contain o the code of the declarer1, which is the participant under the name of whom data is

registered in the CKO2 database. This declarer can indeed be different from the participant sending the report in case of a third party declarer;

o the code of the activity (INSTITUTE), which is a fixed value “CCCR”: o the code of the application (DOMAIN), which is a fixed value “CC1”.

Attributes


REPORT_CREATION_TIMESTAMP Timestamp of the report's creation Mandatory - Single XML

REPORT_REFERENCE_TEXT Free comment given by the participant Single XML

Child elements


PARTICIPANT_CODE Unique code of the declarer of the data Mandatory-Single

V001

V003

V019

XML

3029

3003

3016

INSTITUTE_CODE "CCCR" - Fixed value for the activity Mandatory-Single

= CCCR

XML

XML

DOMAIN_CODE "CC1" - Fixed value for the application of the Institute Mandatory-Single

= CC1

XML

XML

1 This code is assigned by the CCCR. The list of all participants with their codes is published on the CCCR website.


5. DEB action code

Version 1.4 - 02/11/2011

5. DEB action code

5.1 General description

5.1.1 Purposes of the action code

The DEB action code is intended to register new debtors. The debtor creation is the preliminary

step undertaken by a participant before credit actions can be registered for the concerned debtor. If a new debtor cannot be identified, he cannot be recorded in the database, no credit report for this debtor can be accepted and no other specific action can be applied on that debtor.

To reflect internal changes at the participant side, this action code allows also the participant to update the non-official identification data of a debtor. Official identification data can not be updated in the CKO2 database since they originate from official data bases (Crossroads Bank of Enterprises or National Register of Natural Persons).

5.1.2 Data to be reported

5.1.2.1 Individual debtors, codebtors and associations

A debtor can be an individual debtor (legal entity or natural person), or a set of debtors (legal entities, natural persons or a mix of them) named an association. An

association is composed only of individual debtors named codebtors. Identification of a debtor The individual debtors are characterized and reported with an id number and a set of identification items. An association is reported with an id number and with the identification numbers of the codebtors only. These numbers must be those of individual debtors. Associations self are not allowed as codebtors inside an association (no association id number in the list of codebtors). Registration of a debtor in the CKO2 database A debtor can be registered in the CKO2 database only if his identification has been successfully processed immediately by the automatic matching application1 or later by the back office (manual matching).

1 The matching application compares the data reported in the DEB action unit and those stored in the CKO2 database and the

reference databases (CBE or NRNP). When the matching application identifies perfectly the debtor, he becomes registered in the CKO2 database. In case of doubts, the debtor is diverted to an id problem resolution module for decision by the back office.


5. DEB action code

Version 1.4 - 02/11/2011

An association can be registered only if all codebtors were themselves registered beforehand. The CKO2 application has been designed to give priority to the processing of individual debtors over that of associations if debtors are included in the same file. If not, the file with the codebtors must be sent before the file with the associations seeing that the files are dealt with in a FIFO order. Therefore, individual debtors are always processed before the associations when they are sent the same day1. So doing, codebtors can always be identified before the processing of the associations In case of an association of which some debtors are still pending because some id problems occurred in the matching application, the association stays also in a pending status until the complete processing of the codebtors is ended. If at least one codebtor is not registered in the CKO2 database or is rejected by the matching application or the back office, the association is rejected. The reported information on debtors is checked by the application and compared to different data sources, i.e.

the CKO2 database containing already registered debtors (for non-residents, this is generally the only reference database),

the Crossroads Bank of Enterprises (for legal entities domiciled in Belgium and sole traders domiciled or not2 in Belgium),

the National Register of Natural Persons (for natural persons domiciled in Belgium). When the debtor is identified in an official database, only the official data are used in the CKO2 application3.

5.1.2.2 Reporting date and frequency of reporting

Debtors are not bound to a specific reporting date. They can be reported at any time in the month without having to wait its end. They can also be spread into several files sent over the month. A debtor reported by mistake or who finally does not receive any credit can be deleted at any time (cf DELDEB action code), even during the same month of his first reporting. It is desirable that new debtors be reported several times in a month (twice monthly or weekly), particularly by the biggest participants. So it allows the CCCR back office to spread the workload more evenly over the month in the case of identification problems, and enables participants to speed up the correction and resubmission of data on debtors rejected with a view to the reporting of their credits within the legally prescribed time.

Otherwise, he is immediately rejected by the matching application. The back office can accept the individual debtor or reject him.

1 Precisions on the time limit for the processing (around 10:00 pm) will be communicated later. 2 If they have their activity of sole trader in Belgium. 3 Therefore, if official data exists for a debtor, it is given back in the feedbacks produced by the application instead of the data

reported by the paricipant.


5. DEB action code

Version 1.4 - 02/11/2011

5.1.2.3 Identification number

A debtor must always be reported by the participant with one single identification number: if it is a legal person:

o resident: only its enterprise number is allowed; o non-resident: only an internal number assigned by the participant is allowed;

if it is a natural person: o resident:

his enterprise number (for sole traders), when there is no enterprise number, his number of NRNP, in the other cases, a participant internal number (exceptional cases where the debtor

does not have one of the official numbers); o non-resident:

his enterprise number (for natural persons having a professional activity in Belgium but domiciled abroad),

a participant internal number (general cases). if it is an association: only an internal number is possible.

In the cases where the debtor has been deleted (see DELDEB action code) or his internal number modified (see MODIDDEB action code), a participant internal number assigned in the past to a debtor may be re-used later in a DEB action for the same or an other debtor.

5.1.2.4 Free texts

5.1.2.4.1 COMMENT TEXT (PARTICIPANT_DEBTOR_COMMENT_TEXT)

A comment can be added for each debtor by the participant who deems it useful for himself or for the back office. This optional data is given back in the feedbacks returned by the CKO2 application. It is also registered in the CKO2 database. As this comment text can be reported several times for the same debtor via all three debtor action codes, only the last comment will be stored in the database.

5.1.2.4.2 REFERENCE TEXT (PARTICIPANT_FREE_REFERENCE_TEXT)

A reference can be added for each debtor by the participant who wants to automatize the processing of the feedbacks in which this reference is delivered back by the CKO2 application.

5.1.2.5 ID data by type of debtors

An individual debtor can be a legal entity or a natural person and can be resident or non-resident. Therefore, besides the identification number of the debtor, the reporting data differs according to four types of individual debtors.


5. DEB action code

Version 1.4 - 02/11/2011

5.1.2.5.1 RESIDENT LEGAL ENTITIES

The participant must report: legal name, legal form code used by the CBE, address: street, house number, postbox number, postcode, country ISO-code (which must

always be equal to BE). Case of foreign legal entities with a branch in Belgium

A foreign legal entity can be established in Belgium to perform its activities under the law of its country of origin. In that case, it is registered in Belgium with an enterprise number, a legal form and a Belgian address. It is then regarded as a resident legal entity but the country ISO-code of the registered office abroad (Headquarters) must also be reported. These entities are characterized currently with one of the following legal form codes in the CBE: 023, 027, 030, 230, 235, 260 or 2651. Some of them are no more assigned by the CBE to new legal entities but can be still used for legal entities previously registered in the CBE. Though, only in the framework of the exchange of credit information among European central credit registers run by central banks, these debtors are considered as non-resident. For purposes of identification of such debtors, the identification data (including the official identification number of the debtor in his country) prove to be an important means for a correct identification. Therefore, it is recommended for reporting institutions to report also for these branches all the identification items of the Headquarters. These are the same as those used to characterize a non-resident legal entity (see below). If this extra data is reported, the name of the legal entity must at least be mentioned.

5.1.2.5.2 NON-RESIDENT LEGAL ENTITIES

The participant must report: legal name including the legal form (abbreviated or not), address: street, house number, postbox number, town (including postcode), country ISO-code

(different from BE), economic activity code (NACE-BEL 2008): at least 3 digits.

For purposes of identification of such debtors in the framework of the exchange of credit information among European central credit registers run by central banks, the official identification number (enterprise number, tax payer number, ...) in the country of the debtor proves to be an important means for a correct identification. Therefore, the possibility exists to report this data.

1 023: Private foreign association established in Belgium; 027: Societas Europaea; 030: Foreign company; 230: Foreign company

with real estate in Belgium; 235: Foreign company not established in Belgium with a VAT representative; 260: Economic interest group established in Belgium without registered office; 265: European economic interest group established in Belgium without registered office.


5. DEB action code

Version 1.4 - 02/11/2011

5.1.2.5.3 RESIDENT NATURAL PERSONS

The participant must report: family name, first name, date of birth (if the complete date is unknown, only the year of birth can be reported), address: street, house number, postbox number, postcode, country ISO-code (which must

always be equal to BE).

5.1.2.5.4 NON-RESIDENT NATURAL PERSONS

The participant must report: family name, first name, date of birth (if the complete date is unknown, only the year of birth can be reported), address: street, house number, postbox number, town (including postcode), country ISO-code

(different from BE), economic activity code (NACE-BEL 2008): at least 3 digits.

5.1.3 Specific conditions of validation

5.1.3.1 Update of non official id data

A DEB action can be used to report modifications to non official id data of debtors. In that case, the identification process is applied normally as if it was the first reporting of the debtor and the link with the same previously reported debtor will be made by the application1. The participant will receive an “information” in the feedbacks to remind him of the previous reporting. The possible non official id data stored in the database is the following:

for all types of persons: free comment text2; for resident legal entities, only some data regarding the Headquarters can be updated: internal

participant debtor code of a Headquarters, official id number of the Headquarters in the country of origin, NACEBEL code of the Headquarters and comment text regarding the Headquarters. All other data comes from the CBE (including the other id data of the Headquarters);

for non resident legal entities: all data is non official; for resident natural persons: all data is official, except when no official id number exists. In this

last case, all data is non official; for non resident natural persons: all data is official if an enterprise number was reported (except

a possible official foreign id number and the comment regarding the debtor) and non official if no enterprise number was reported.

1 If the case, even if the participant uses an official identification number (enterprise or NRNP number) instead of the internal

number used the first time of the reporting. 2 Remark: the free reference text is not stored in the database.


5. DEB action code

Version 1.4 - 02/11/2011

5.1.3.2 Not active debtor

When he is reported for the first time by a participant, a debtor for which an enterprise number exists in the CBE is only accepted by the application if he is considered as "active" or alike by the CBE1. If not, he will be rejected2. T

5.1.3.3 Deceased resident natural persons

A deceased resident natural person reported via a DEB action code will be rejected when

o an enterprise number exists (in that case, the id data of the debtor are checked with the CBE which should have been updated to take the death into account);

o no enterprise number exists but well a NRNP number in the CKO2 database if his situation has been

updated recently with data from the NRNP3; when he is not registered in the CKO2 database (in that case, the id data of the

debtor are checked with the NRNP data); not be rejected if he is registered in the CKO2 database with a NRNP number and his death

occurred since the last update of the CKO2 database with the NRNP data.

5.1.3.4 Debtor already reported but without credit anymore

When a debtor was reported once by a participant, and later this participant reported that there was no more credit to report by using the action code "stop debtor credits" (see hereafter STOPCRED), the participant can resume his credit reporting simply by using the CRED action code if the client relation starts again (credits again extended). But, if he prefers, he may use this DEB action to report again the debtor and afterwards the credits. In that case, the identification process is applied normally as if it was the first reporting of the debtor and the link with the same previously reported debtor will be made by the application4. The participant will receive a "warning" in the feedbacks to remind him of the previous reporting.

1 I.e. not deleted, stopped or closed. 2 his validation doesn't apply to a DEB action for a debtor of which the participant wants to update the non official data (foreign id

number of non-resident debtors and Headquarters id data).Rare cases. 3 Probably every three months. 4 If the case, even if the participant uses an official identification number (enterprise or NRNP number) instead of the internal

number used the first time of the reporting.


5. DEB action code

Version 1.4 - 02/11/2011

5.1.3.5 Debtors out of the reporting scope but present in associations

Codebtors present in associations but which should normally be excluded from the reporting scope of the CCCR for legal reasons1 can nevertheless be reported. No check will reject the debtor or the association for that reason.

1 Some types of debtors are indeed excluded from the reporting scope of the CCCR for all participants (e.g. credit to banks are

out of the scope according to the law) or a part of them (e.g. leasing companies don't have to report credits to non-residents).


5. DEB action code

Version 1.4 - 02/11/2011

5.2 Description of the elements DEB element


DEB_ITEM Contains data on an individual debtor or association Mandatory XML

DEB_ITEM element


SINGLE_DEBTOR Contains data on a debtor Mandatory-Single XML

ASSOCIATION Contains data on an association

PARTICIPANT_DEBTOR_COMMENT_TEXT Free comment of the participant Single XML

PARTICIPANT_FREE_REFERENCE_TEXT Free reference assigned by the participant for

automatizing purposes

Single XML


5. DEB action code

Version 1.4 - 02/11/2011

5.2.1 SINGLE_DEBTOR SINGLE_DEBTOR element


RESIDENT_LEGAL_ENTITY Contains data on a resident legal entity One element at least is mandatory

Single

V046

V100

XML

3008

4001 and 4002

Info in the

feedback

NON_RESIDENT_LEGAL_ENTITY Contains data on a non-resident legal entity

RESIDENT_NATURAL_PERSON Contains data on a resident natural person

NON_RESIDENT_NATURAL_PERSON Contains data on a non-resident natural person

5.2.1.1 RESIDENT_LEGAL_ENTITY RESIDENT_LEGAL_ENTITY element


DEBTOR_KBO_NUMBER Enterprise number in the CBE Mandatory-Single

V041

V042

V017

V034

V045

XML

2010

3051

3004

3005

3007

KBO_LEGAL_NAME Enterprise legal name Mandatory-Single XML

KBO_LEGAL_FORM_CODE Enterprise legal form code (CBE table) Mandatory-Single

V004

XML

1110

KBO_ADDRESS Contains address data Mandatory-Single XML

FOREIGN_HEADQUARTERS Contains data on the registered office generally abroad

(Headquarters) when the resident legal entity is the

Belgian establishment of a foreign or European

company, i.e. when the KBO_LEGAL_FORM_CODE

has one of the following values: 023, 027, 030, 230,

235, 260 or 265

Single

V043

XML

2017

KBO_ADDRESS element


KBO_STREET_NAME Street name Mandatory-Single XML

KBO_HOUSE_NUMBER_TEXT House number Single XML

KBO_POSTBOX_TEXT Postbox number Single XML

KBO_POSTAL_CODE Postcode Mandatory-Single

V005

XML

1110

KBO_COUNTRY_ISO_CODE Country ISO-code Mandatory-Single

V054 (= BE)

XML

2054


5. DEB action code

Version 1.4 - 02/11/2011

FOREIGN_HEADQUARTERS element


HEADQUARTERS_COUNTRY_ISO_CODE Country ISO-code of the registered office of the foreign legal

entity

Mandatory-Single

V056 ( BE)

V006

XML

2056

1110

HEADQUARTERS_DATA Contains data regarding the registered office of the foreign

legal entity

Single XML

HEADQUARTERS_DATA element


HEADQUARTERS_PARTICIPANT_DEBTOR_CODE Internal number assigned by the participant to the

registered office of the foreign legal entity

Single

V009

XML

3101 HEADQUARTERS_ID_NUMBER Official identification number assigned by the foreign

authorities to the registered office of the foreign legal

entity

Single XML

HEADQUARTERS_LEGAL_NAME Legal name of the foreign legal entity Mandatory if the HQ_DATA

element is present

Single

XML

XML HEADQUARTERS_ADDRESS Contains address data of the registered office of the

foreign legal entity

Single XML

HEADQUARTERS_NACEBEL_CODE NACE-BEL 2008 code of the registered office of the


Single

3 to 5 digits

V007

XML

XML

1110 HEADQUARTERS_COMMENT_TEXT Free comment given by the participant Single XML HEADQUARTERS_ADDRESS element


ADDRESS_STREET_NAME Street name Single XML ADDRESS_HOUSE_NUMBER_TEXT House number Single XML ADDRESS_POSTBOX_TEXT Postbox number Single XML ADDRESS_CITY_NAME Postcode and name of the town Single XML ADDRESS_COUNTRY_ISO_CODE Country ISO-code (same as in FOREIGN_HQ element) Single

V006

V015

V055

XML

1110

2120

2055


5. DEB action code

Version 1.4 - 02/11/2011

5.2.1.2 NON_RESIDENT_LEGAL_ENTITY

NON_RESIDENT_LEGAL_ENTITY element


PARTICIPANT_DEBTOR_CODE Internal number assigned by the participant to the


Mandatory-Single

XML

PERSON_LEGAL_NAME Enterprise legal name (+ legal form) Mandatory-Single XML

ADDRESS Contains address data Mandatory-Single XML

PERSON_NACEBEL_CODE NACE-BEL 2008 code of the foreign legal entity Mandatory-Single

3 to 5 digits

V007

XML

XML

1110

PERSON_FOREIGN_ID_NUMBER Official identification number assigned by the foreign

authorities to the registered office of the foreign legal

entity

Single XML

ADDRESS element


ADDRESS_STREET_NAME Street name Mandatory - Single XML ADDRESS_HOUSE_NUMBER_TEXT House number Single XML ADDRESS_POSTBOX_TEXT Postbox number Single XML ADDRESS_CITY_NAME Postcode and name of the town Mandatory - Single XML ADDRESS_COUNTRY_ISO_CODE Country ISO-code Mandatory - Single

V006

V055 ( BE)

XML

1110

2055


5. DEB action code

Version 1.4 - 02/11/2011

5.2.1.3 RESIDENT_NATURAL_PERSON

RESIDENT_NATURAL_PERSON element


DEBTOR_RRN_NUMBER Number of National Register of Natural Persons One

number is

mandatory

Single

V041

V008

V050

V048

XML

2010

3052

3012

3009

DEBTOR_KBO_NUMBER Enterprise number in the CBE V041

V042

V034

V049

2010

3051

3005

3011

PARTICIPANT_DEBTOR_CODE Participant internal number V016 3133

V053 3136

PERSON_NAME Family name Mandatory-Single XML

PERSON_FIRST_NAME First name Mandatory-Single XML

PERSON_BIRTH_DATE Complete date of birth One value is mandatory-Single

V010

V047

V059

XML

3053

3006

2059

PERSON_BIRTH_YEAR Year of birth

ADDRESS Contains address data Mandatory-Single XML

ADDRESS element


ADDRESS_STREET_NAME Street name Mandatory - Single XML ADDRESS_HOUSE_NUMBER_TEXT House number Single XML ADDRESS_POSTBOX_TEXT Postbox number Single XML ADDRESS_POSTAL_CODE Postcode Mandatory - Single

V005 XML

1110 ADDRESS_COUNTRY_ISO_CODE Country ISO-code Mandatory - Single

V054 (= BE) XML

2054


5. DEB action code

Version 1.4 - 02/11/2011

5.2.1.4 NON_RESIDENT_NATURAL_PERSON

NON_RESIDENT_NATURAL_PERSON element


DEBTOR_KBO_NUMBER Enterprise number in the CBE One

number is

mandatory

Single

V041

V042

V017

V034

V048

XML

2010

3051

3004

3005

3009

PARTICIPANT_DEBTOR_CODE Participant internal number V016 3133

V053 3136

PERSON_NAME Family name Mandatory - Single XML

PERSON_FIRST_NAME First name Mandatory-Single XML

PERSON_BIRTH_DATE Complete date of birth One value is mandatory-Single

V010

V059

XML

3053

2059

PERSON_BIRTH_YEAR Year of birth

ADDRESS Contains address data Mandatory - Single XML

PERSON_NACEBEL_CODE NACE-BEL 2008 code of the foreign legal entity Mandatory-Single

3 to 5 digits

V007

XML

XML

1110

PERSON_FOREIGN_ID_NUMBER Official identification number assigned by the foreign

authorities to the foreign natural person

Single XML

ADDRESS element


ADDRESS_STREET_NAME Street name Mandatory - Single XML ADDRESS_HOUSE_NUMBER_TEXT House number Single XML ADDRESS_POSTBOX_TEXT Postbox number Single XML ADDRESS_CITY_NAME Postcode and name of the town Mandatory - Single XML ADDRESS_COUNTRY_ISO_CODE Country ISO-code Mandatory - Single

V006

V055 ( BE)

XML

1110

2055


5. DEB action code

Version 1.4 - 02/11/2011

5.2.2 ASSOCIATION ASSOCIATION element


PARTICIPANT_DEBTOR_CODE Participant internal number Mandatory – Single

V052

V100

XML

3014

4001

a

n

d

4

0

0

2 CODEBTORS Contains data of the codebtors present in the association Mandatory - Single

V051 XML

3013 PARTICIPANT_DEBTOR_COMMENT_TEXT Free comment of the participant Single XML CODEBTORS element


CODEBTOR_IDENTIFIER Contains id numbers of all the codebtors At least 2 CODEBTOR_IDENTIFIER

elements mandatory - XML

CODEBTOR_IDENTIFIER element


PARTICIPANT_CODEBTOR_CODE Participant internal number one

number is

mandatory

Single

V011

V012

V014

V013

V016 XML

2130

3111

3131

3020

3133 DEBTOR_KBO_NUMBER Enterprise number in the CBE V041

V042

V017

2010

3051

3004

DEBTOR_RRN_NUMBER

Number of National Register of Natural Persons V041

V008

2010

3052


5. DEB action code

Version 1.4 - 02/11/2011


6. DELDEB action code

Version 1.4 - 02/11/2011



6.1.1 Purpose of the action code

When a debtor has already been reported by the participant and registered in the database, this action code allows the participant to delete all his data (historical credit data and, if the case, debtor identification data). This can be necessary when the debtor and his credits have been reported by mistake. It can also be used when the debtor has been reported but has finally not received any credit. It can be used at any moment in the month.


Only the id number of the debtor has to be reported. No reporting date has to be communicated, seeing that the deletion erases all the historical data.

6.1.3 Associations

An association can be deleted by a DELDEB action. In this case, the action doesn't delete the id data of the codebtors, nor the credits granted to them as individual debtor.

6.1.4 Debtor in association

If an individual debtor to be deleted is also a codebtor in an association: If he has no credits as individual debtor: no action is performed in the database and an error

message will be returned in the feedbacks to inform the participant that the debtor cannot be deleted as he is a codebtor in an association;

If he has credits as individual debtor, only his credits received on an individual basis will be erased, but not the id data, nor the credits granted to him as codebtor1.

1 If the participant wishes to delete a debtor as individual debtor and as codebtor in an association, he must report a DELDEB for

the debtor and for the association, and create a new association with a new composition with credits for all reporting dates which had been reported previously for the deleted association.



Version 1.4 - 02/11/2011

6.1.5 Processing of the action code

This action can't be rectified or reversed later on because all the data are definitely erased. Therefore, such an action, after having been received by the application, has to be approved by the back office which will assess the significance of the deletion before accepting it. After being dealt with by the back office, the DELDEB action code impacts the CKO2 database during the following night.

6.1.6 Deleted debtor to be reported later

If a deleted debtor has to be communicated later on because credits are being granted to him, the action code DEB must be used (exept if the debtor is also part of an association).



Version 1.4 - 02/11/2011

6.2 Description of the elements DELDEB element


DELDEB_ITEM Contains data on the debtor to be deleted Mandatory XML

DELDEB_ITEM element


DEBTOR_KBO_NUMBER Enterprise number in the CBE One number is

mandatory

Single

V020

V061

V041 XML

3106

3061

2010

DEBTOR_RRN_NUMBER Number of National Register of Natural Persons V041 2010

PARTICIPANT_DEBTOR_CODE Participant internal number

PARTICIPANT_DEBTOR_COMMENT_TEXT Free comment of the participant Single XML PARTICIPANT_FREE_REFERENCE_TEXT Free reference assigned by the participant for


Single XML


7. MODIDDEB action code

Version 1.4 - 02/11/2011




To reflect internal changes at the participant side, this action code allows the participant to convert an identification number to another on the condition that only participant internal numbers are concerned. Changes where an official id number would be implied (e.g. from an enterprise number to a participant internal number or an other enterprise number, from a participant internal number to an enterprise or NRNP number) are not allowed. It can be used at any moment in the month. Consequently this action code may only be used for

associations, non-resident legal entities, non-resident natural persons not reported with an enterprise number, resident natural persons (exceptional cases).


The participant has only to mention the old internal number and report the new one. The new internal number can not already be present in the database. No other data can be changed with this action code.

7.1.3 Associations

When a participant modifies an internal number of a debtor present in an association, his number in the association will also be updated by the CKO2 application to reflect the change of the id number of the codebtor. No action is then needed from the participant to update the association's composition.



Version 1.4 - 02/11/2011

7.2 Description of the elements MODIDDEB element


MODIDDEB_ITEM Contains data necessary to report the modification Mandatory XML

MODIDDEB_ITEM element


PARTICIPANT_OLD_DEBTOR_CODE Participant internal number to be modified Mandatory – Single

V020

XML

3106

PARTICIPANT_DEBTOR_CODE New participant internal number assigned to the debtor Mandatory – Single

V018

V057

XML

3135

2057

PARTICIPANT_DEBTOR_COMMENT_TEXT Free comment of the participant Single XML PARTICIPANT_FREE_REFERENCE_TEXT Free reference assigned by the participant for


Single XML


8. CRED action code

Version 1.4 - 02/11/2011

8. CRED action code



This action code allows the participant to report monthly the credit situation of his debtors at the end of a month, as well as additional specific data relating to their risk situation (e.g. default, ...).


The participant must report in a CRED action unit one debtor code, one reporting date, a set of credit data and a set of additional data named risk data. He can also fill in a comment and a free reference.

8.1.2.1 Reporting date

One reporting date (month and year) is required in a CRED action unit. So credits are always bound to a specific end of month. If the participant wishes to report credit data for a same debtor regarding several reporting dates, he must create as many CRED units as there are reporting dates. It is not possible to mention a reporting date more recent than the end of the last month, nor older than the oldest month still recorded in the database as only credit data regarding the last 12 calendar ends of month is stored in the CKO2 database.

8.1.2.2 Debtor identification

The debtor to whom the credits must be assigned can only be identified with an identification number: enterprise number (if it exists), NRNP number (if it exists), participant internal number (if the participant reported the debtor with an internal number).

Should an official identification number be assigned after the participant has reported an internal number (rare cases), he will be allowed to continue using his internal number for credit reporting or to use the official id number. If several id numbers exist for the same debtor, the participant may choose the id number he wants to report credits. He even may switch later from an NRNP number to an enterprise number, an internal participant number to an official id number if the need arises and conversely if the participant ever reported a participant internal number. If credits are reported for a deceased debtor, the debtor will be flagged in the feedback "Immediate acknowledgment of receipt" if the information is known by CKO2 (see specific § about deceased debtors in the DEB action code §).


8. CRED action code

Version 1.4 - 02/11/2011

8.1.2.3 Credit data

A credit situation is a set of amounts characterized by five criteria. Moreover two types of amounts can be distinguished: authorized amount and used amount. The five mandatory criteria to be reported for each amount are:

credit mode code, initial maturity code, residual maturity code, currency code, country code where the credit has been granted.

For a determined combination of the five criteria, can be reported

an authorized amount, or a used amount, or both authorized and used amounts.

An amount (authorized or used) equal to zero will be accepted.

8.1.2.4 Risk data

Although the risk data regards the situation at the debtor level rather than at credit level, it is reported in the CRED action unit as it has to be monthly updated (while data on debtors is only passed on once). The risk data includes:

the probability of default. It is an optional data because some categories of participants do not have to report it. Although some other types of participants are legally obliged to report it, it is possible that some reporting institutions do not have the information for some small enterprises. Therefore, this item remains optional for all participants;

the collateral amount. It is an optional data because some categories of participants do not have to report it, but though some other types of participants are legally obliged to report it, what will be checked by the application;

the credit default. Two types of default exist and can be reported simultaneously: "90 days past due" and "Unlikely to pay". Both types can exist at the same reporting date but have their specific rules of reporting. Therefore data to be reported exists for both types.

o "Past due default": date: a complete (day, month and year) or partial date (month, year) must be

reported as soon as an amount is reported. The date may not be more recent than the current calendar date.

amount of the default: always in EUR, it must be reported as soon as a date is also reported. A value zero is not allowed. Once reported, the amount of a default must be adjusted in line with successive reviews conducted by the participant during the life of the debtor


8. CRED action code

Version 1.4 - 02/11/2011

In short, two situations are possible:

no date and no amount reported; a date and an amount, different of zero, are reported.

o "Unlikely to pay default":

date: a complete (day, month and year) or partial date (month, year) must be reported as soon as an amount is reported. The date may not be more recent than the current calendar date.

amount: always in EUR, it must be reported as soon as a date is also reported, but a value zero is allowed. Once reported, the amount of a default must be adjusted in line with successive reviews conducted by the participant during the life of the debtor.

In short, two situations are possible: no date and no amount reported; a date and an amount, possibly zero, are reported.

When the conditions of reporting the credit default do not exist anymore, date and amount will not be reported at the following reporting date.

8.1.3 Rules of reporting

After the end of a month, participants report the last credit situation (i.e. at the end of that month) of all their debtors. All credit data must be communicated even when the situation has not changed. Though, no consistency check in the CKO2 application is performed between the newly reported credit data and the previous one. A CRED action unit contains the whole picture of the indebtedness (credit AND risk data) of a debtor at the mentioned reporting date. The CRED action must be used and can be validated

if the concerned debtor has already been reported, accepted and registered by the application AND if no credit data (via CRED or STOPCRED1) has already been reported by the participant and

registered by the application for the date reported in the action unit. In the other cases (credit data already existing in the database at the reported date), the CORCRED action code must be used by the participant to report the another whole picture of the credit situation. The CORCRED action code must also be used when a value zero has been reported via a CRED action or when a STOPCRED has been reported for the concerned reporting date.

1 A STOPCRED action is considered like a reporting of credit data.


8. CRED action code

Version 1.4 - 02/11/2011

In the case where the debtor would have been sent in the same flow of reports but not yet successfully identified, the CRED action unit will stay in a pending situation and later:

processed if finally the debtor is identified and registered; rejected if finally the debtor self is rejected.

8.1.4 Use of CRED in case of delayed reporting

Several cases are possible. A participant can be late for the credit reporting of all his debtors: for instance, in 10/2009, his

last reported date for the credits is 05/2009. A CRED action code must be used for all the reporting dates after 05/2009 for all the debtors.

A participant can be late for the credit reporting of a part of his debtors: for instance, in 10/2009, credit data has been reported with 09/2009 as reporting date for a half of his debtors and with 05/2009 for the other half. A CRED action code must be used for all the reporting dates after 05/2009 regarding the second half of the debtors.

A participant can be late for the credit reporting of some "old" reporting dates but on time for "recent" reporting dates for one debtor: for instance, only for debtor X, in 10/2009, credits have been reported up to reporting date 05/2009 and afterwards, only with reporting date 09/2009. No credit data has been reported in between. A CRED action code must be used for the reporting dates from 06/2009 to 08/2009 for debtor X.


8. CRED action code

Version 1.4 - 02/11/2011

8.2 Description of the elements CRED element


CRED_ITEM Contains credit and risk data of debtors Mandatory XML

8.2.1 CRED_ITEM element

CRED_ITEM element


DEBTOR_KBO_NUMBER Enterprise number in the CBE One element is

mandatory

Single

V020

V041 XML

3106

2010



CREDIT_PERIOD_DATE Reporting month of the credit data Mandatory – Single

V021

V022

V023

XML

2021

3116

3102

RISK_DEFAULT_PROBABILITY_

PERCENTAGE

Probability of default of the debtor assessed by the

participant

Optional

Single

V024 (Max. value = 100,00 %)

XML

2024

RISK_COLLATERAL_AMOUNT Amount of collateral pledged by the debtor and

assessed by the participant

V0601

Single

3001

XML

RISK_PAST_DUE_DEFAULT Contains data on credit default “90 days past due” Single XML RISK_UNLIKELY_DEFAULT Contains data on credit default “unlikely to pay” Single XML RISK_COMMENT_TEXT Free comment text of the participant Single XML PARTICIPANT_FREE_REFERENCE_TEXT Free reference assigned by the participant for


Single XML

CREDIT_DIMENSIONS Contains credit data At least one is mandatory XML

1 Credit institutions and leasing companies. and factoring companies


8. CRED action code

Version 1.4 - 02/11/2011

8.2.2 RISK_PAST_DUE_DEFAULT element

RISK_PAST_DUE_DEFAULT element


RISK_PAST_DUE_DEFAULT_AMOUNT Amount of credit default answering the definition “90 days

past due”

Single

V058 ( 0)

Mandatoty if

RISK_PAST_DUE_DEFAULT

element is present

XML

2058

XML

RISK_PAST_DUE_DEFAULT_DATE Complete date of credit default answering the definition “90

days past due”

Single

V027

Mandatoty if


element is present

XML

2032

XML RISK_PAST_DUE_DEFAULT_PERIOD Month and year of credit default answering the definition

“90 days past due”

8.2.3 RISK_UNLIKELY_DEFAULT element

RISK_UNLIKELY_DEFAULT element


RISK_UNLIKELY_DEFAULT_AMOUNT Amount of credit default answering the definition “Unlikely

to pay”

Single

Mandatoty if


is present

XML

XML

RISK_ UNLIKELY_DEFAULT_DATE Complete date of credit default answering the definition

“Unlikely to pay”

Single

V027

Mandatoty if


is present

XML

2032

XML

RISK_ UNLIKELY_DEFAULT_PERIOD Month and year of credit default answering the definition



8. CRED action code

Version 1.4 - 02/11/2011

8.2.4 CREDIT_DIMENSIONS element

CREDIT_DIMENSIONS element


CREDIT_AMOUNTS Contains amount(s) of credit Mandatory – Single XML

CREDIT_MODE_CODE Code of the mode of the credit amount(s) Mandatory – Single

V030

XML

1110

CREDIT_INITIAL_MATURITY_CODE Code of the initial maturity of the credit amount(s) Mandatory – Single

V031

XML

1110

CREDIT_RESIDUAL_MATURITY_CODE Code of the residual maturity of the credit amount(s) Mandatory – Single

V032

XML

1110

CREDIT_CURRENCY_ISO_CODE ISO-code of the currency of the credit amount(s) Mandatory – Single

V035

XML

1110

CREDIT_COUNTRY_ISO_CODE ISO-code of the country where the credit amount(s)

was/were extended

Mandatory – Single

V006

XML

1110

CREDIT_AMOUNTS element


CREDIT_USED_AMOUNT Credit amount actually used by the debtor for the

combination of dimensions

At least one is mandatory – Single

V039

V044

XML

2139

2140 CREDIT_AUTHORIZED_AMOUNT Maximum credit amount allowed to the debtor for the



9. CORCRED action code

Version 1.4 - 02/11/2011




This action code allows the participant to correct credit data already registered for a debtor but which proved to be erroneous or incomplete. It can be used at any moment in the month.


The participant has to report the correct complete credit and risk data as well as the reporting date. It is not possible to correct only the erroneous data, to add or delete some data or to report only additional risk data. If credit data has been reported for a debtor and reporting date, but that no credit data should have been reported, the participant must report a CORCRED action code with a credit amount equal to zero for any combination of credit. The content of this action unit is exactly the same as in the CRED action code, including the additional risk data. As only the credit data regarding the last 12 calendar ends of month are stored in the CKO2 database, it is not possible to modify credits with a previous reporting date.

9.1.3 Correction of a STOPCRED action code

In the case where a STOPCRED has been erroneously reported, a CORCRED action code must also be used to report the correct credit data at the reporting date at which the STOPCRED has been registered.



Version 1.4 - 02/11/2011

9.2 Description of the elements CORCRED element


CORCRED_ITEM Contains data on credit and risk data of the debtor Mandatory XML

CORCRED_ITEM element


DEBTOR_KBO_NUMBER Enterprise number in the CBE One element is

mandatory

Single

V020

V041 XML

XML

3106

2010



CREDIT_PERIOD_DATE Reporting month of the credit data Mandatory – Single

V021

V022

V037

XML

2021

3116

3126

From here, all other items are identical to those in the CRED_ITEM element All validation rules and messages

of the CRED_ITEM element apply

RISK_DEFAULT_PROBABILITY_

PERCENTAGE

Probability of default of the debtor assessed by the

participant

Optional

Single

V024 (Max. value = 100,00 %)

XML

2024

RISK_COLLATERAL_AMOUNT Amount of collateral pledged by the debtor and

assessed by the participant

V0601

Single

3001

XML

RISK_PAST_DUE_DEFAULT Contains data on credit default “90 days past due” Single XML RISK_UNLIKELY_DEFAULT Contains data on credit default “unlikely to pay” Single XML RISK_COMMENT_TEXT Free comment text of the participant Single XML PARTICIPANT_FREE_REFERENCE_TEXT Free reference assigned by the participant for


Single XML

CREDIT_DIMENSIONS Contains credit data At least one is mandatory XML

1 Credit institutions and leasing companies. and factoring companies



Version 1.4 - 02/11/2011

9.2.1 RISK_PAST_DUE_DEFAULT element

RISK_PAST_DUE_DEFAULT element


RISK_PAST_DUE_DEFAULT_AMOUNT Amount of credit default answering the definition “90 days

past due”

Single

V058 ( 0)

Mandatoty if


element is present

XML

2058

XML

RISK_PAST_DUE_DEFAULT_DATE Complete date of credit default answering the definition “90

days past due”

Single

V026

V027

Mandatoty if


element is present

XML

3026

2032

XML

RISK_PAST_DUE_DEFAULT_PERIOD Month and year of credit default answering the definition

“90 days past due”

9.2.2 RISK_UNLIKELY_DEFAULT element



RISK_UNLIKELY_DEFAULT_AMOUNT Amount of credit default answering the definition “Unlikely

to pay”

Single

Mandatoty if


is present

XML

XML

RISK_ UNLIKELY_DEFAULT_DATE Complete date of credit default answering the definition


Single

V027

Mandatoty if


is present

XML

2032

XML

RISK_ UNLIKELY_DEFAULT_PERIOD Month and year of credit default answering the definition




Version 1.4 - 02/11/2011

9.2.3 CREDIT_DIMENSIONS element

CREDIT_DIMENSIONS element


CREDIT_AMOUNTS Contains amount(s) of credit Mandatory – Single XML

CREDIT_MODE_CODE Code of the mode of the credit amount(s) Mandatory – Single

V030

XML

1110

CREDIT_INITIAL_MATURITY_CODE Code of the initial maturity of the credit amount(s) Mandatory – Single

V031

XML

1110

CREDIT_RESIDUAL_MATURITY_CODE Code of the residual maturity of the credit amount(s) Mandatory – Single

V032

XML

1110

CREDIT_CURRENCY_ISO_CODE ISO-code of the currency of the credit amount(s) Mandatory – Single

V035

XML

1110

CREDIT_COUNTRY_ISO_CODE ISO-code of the country where the credit amount(s)

was/were extended

Mandatory – Single

V006

XML

1110

CREDIT_AMOUNTS element


CREDIT_USED_AMOUNT Credit amount actually used by the debtor for the


At least one is mandatory – Single

V039

V044

XML

2139

2140 CREDIT_AUTHORIZED_AMOUNT Maximum credit amount allowed to the debtor for the



10. STOPCRED action code

Version 1.4 - 02/11/2011




When the participant stops granting credit to a debtor and consequently that no more credit amount has to be reported, this action code allows the participant to indicate explicitly that reporting credits for this debtor stops from the specified reporting date onwards. This action code must also be used to stop the credits of a deceased debtor. As a consequence, the credit situation is flagged to indicate that there is no more credit reported by the participant for this debtor from the mentioned reporting date on.


The participant has to report the identification number of the debtor and the reporting date from which there is no more credit granted. He can also fill in a comment and a free reference.

10.1.3 Association

This action code STOPCRED must also be used when the composition of an association has changed. The credits of the association must be "stopped" with STOPCRED, a new debtor must be created (DEB action code) with the new composition of the association and credits must be reported via a CRED action for the new association. It isn't indeed possible just to change the composition of an association. When a STOPCRED action is reported for an association, it has no consequence on the credit data of the codebtors at the individual level. Only the credit data of the association self is impacted.

10.1.4 Credit reporting after a STOPCRED action code

The use of this action code does not prevent the participant from reporting new credits in the future. In that case, the participant may simply use a CRED action code and is not obliged to use a DEB action code to re-create the debtor (but he is allowed to).



Version 1.4 - 02/11/2011

10.1.5 Specific cases

This action code can also be used by a participant instead of a DELDEB action when he prefers to keep recorded in the CKO2 database a debtor he reported but to whom he decided afterwards not to grant credits. The STOPCRED action code can't be used:

when only a part of the credits have been reimbursed and that the credit relation remains for other credits.;

when credit data has already been (erroneously) registered at the reporting date at which the credit reporting stops. It will be then rejected by the application1. The participant must first report a CORCRED action code for the reporting date aimed at with a credit amount equal to zero for any combination of credit. At the following reporting date, the participant may then report the STOPCRED action code;

when credit data has already been (erroneously) registered at a reporting date more recent than the one from which there is no more credits to be reported. It will be then rejected by the application. The participant must first report CORCRED action codes with a credit amount equal to zero for any credit combination for the reporting dates at which credit data has been erroneously registered. At the following reporting date, the participant may then report the STOPCRED action code.

1 In other words, credit data cannot exist at the same reporting date. No overwrite of credit by a STOPCRED is allowed.



Version 1.4 - 02/11/2011

10.2 Description of the elements STOPCRED element


STOPCRED_ITEM Contains data to indiicate the end of the credits of a debtor Mandatory XML

STOPCRED_ITEM element


CREDIT_PERIOD_DATE Date of reporting at wich there is no more credit data Mandatory – Single

V021

V022

V033

V036

XML

2021

3116

3112

3113

DEBTOR_KBO_NUMBER Enterprise number of the debtor One element

mandatory

Single

V020

V041 XML

XML

3106

2010

DEBTOR_RRN_NUMBER Number of the National register of Natural Persons V041 2010

PARTICIPANT_DEBTOR_CODE Participant internal number of the debtor

RISK_COMMENT_TEXT Free comment of the participant Single XML

PARTICIPANT_FREE_REFERENCE_TEXT Free reference assigned by the participant for


Single XML


11. Validation rules

Version 1.4 - 02/11/2011

11. Validation rules V001 The participant code must have been created previously in OneGate by the CCCR back

office

V003 The sender of the report identified by his digital certificate must be authorized for the declarer on the name of whom data will be registered in the CKO2 database in case of third party declarer

V004 The code of legal form must exist in the list of legal form codes of the Crossroads Bank of Enterprises

V005 The code must exist in the list of Belgian official postcodes

V006 The code must exist in the list of official ISO-codes of countries

V007 The code must exist in the list of official codes of the NACE-BEL 2008 nomenclature

V008 The id number must exist in the National Register of Natural Persons

V009 The internal participant number of the registered office of the foreign legal entity must have already been reported by the participant

V010 The debtor can not be older than 118 year

V011 The same id number may not be present more than once in the same association

V012 The same debtor may not be present more than once in the same association

V013 An association number cannot be mentioned as a codebtor inside an other association

V014 All debtors of an association must have already been registered in the CKO2 database for the participant

V015 The country ISO-code must be the same as this mentioned in the FOREIGN_HEADQUARTERS element



Version 1.4 - 02/11/2011

V017 The debtor must have a status "active" or alike (not deleted, stopped or closed) in the Crossroads Bank of Enterprises

V018 The new participant internal number may not be existing in the CKO2 database

V019 The participant code must have been created previously in the CKO2 application by the CCCR back office

V020 The debtor must have already been registered in the CKO2 database for the participant

V021 The reporting date must regard the previous months. It may not be the current month or be later in the future

V022 The reporting date must regard a date for which credit data still exists in the CKO2 database. It may not be different from the last 12 ends of month

V023 No credit data may have already been registered for the mentioned reporting date and the debtor

V024 The probability of default cannot exceed 100,00 %

V027 Date/period of default cannot be in the future

V030 Credit mode code must exist in the table of credit modes

V031 Initial maturity code must exist in the table of initial maturities

V032 Residual maturity code must exist in the table of residual maturities

V033 Credit data cannot be present for the debtor in the CKO2 database for the reporting institution at the reporting date self or at a date more recent than that mentioned in the STOPCRED



Version 1.4 - 02/11/2011

V034 The enterprise number existing in the Crossroads Bank of enterprises must be assigned to the same type of person (legal entity or natural person) as the reported one

V035 The code must exist in the list of official ISO-codes of currencies

V036 No STOPCRED can have already been reported for the debtor for the reporting institution at the reporting date self or at a date more recent than that mentioned in the STOPCRED

V037 Credit data must be present for the debtor in the CKO2 database for the reporting institution at the reporting date

V039 The same combination of dimensions may be reported only once for an authorized amount and once for a used amount

V041 The last two digits are the results of the modulo 97 operation applied on the previous digits

V042 The enterprise number must exist in the Crossroads Bank of Enterprises

V043 The element FOREIGN_HEADQUARTERS is mandatory when the legal form code has one of the following values: 023, 027, 030, 230, 235, 260 and 265

V044 A used amount may not be reported for some credit modes (mixed credits and credit insurance amount)

V045 The identification must be conclusive according to the matching application between the enterprise number and name, legal form and postcode to register the debtor in the CKO2 database

V046 The identification must be conclusive according to the matching application to register the debtor in the CKO2 database

V047 Date/year of birth must be coherent with the data in the reported number of National Register of Natural persons

V048 The identification must be conclusive according to the matching application between the enterprise number and family name, first name and postcode

V049 The identification must be conclusive according to the matching application between the number of National Register of Natural Persons and the family name, first name and postcode



Version 1.4 - 02/11/2011

V050 The debtor cannot be deceased according to the National Register of Natural Persons

V051 An other participant internal number cannot be assigned to the same composition of codebtors for the participant

V052 The same participant internal number may not exist in the CKO2 database with an other composition of codebtors

V053 For a debtor natural person identified only with a participant internal number which already exists in the database, it is not allowed to change the address so that the type (resident/non resident) of debtor is modified

V054 The ISO-country code of a resident debtor must be equal to "BE"

V055 The ISO-country code of a non-resident debtor must be different from "BE"

V056 The ISO-country code of a foreign Headquarters must be different from "BE"

V057 The new internal participant debtor code must be different from the old one

V058 The amount of a "90 days past due" default cannot be equal to zero

V059 Date/year of birth cannot be a date/year in the future

V060 The amount of collateral pledged by the debtor is mandatory for some types of participants

V061 The debtor to be deleted cannot be a codebtor in an association (even if the association has no credit)

V100 The application checks if the debtor is already registered in the CKO2 database for the same participant


12. Messages

Version 1.4 - 02/11/2011

12. Messages

12.1 Warning messages

4001 Debtor already reported by your institution. No data has been changed.

4002 Debtor already reported by your institution. Non-official data peculiar to your institution has been changed as reported

12.2 Error messages 3001 Mandatory item for your institution

1110 This value does not belong to the list of valid values

3003 The sender of the report, owner of the digital certificate, is not allowed as third-party declarer for the code of the mentioned participant

3004 Debtor existing but with status deleted, stopped or closed in the Crossroads Bank of Enterprises

3005 The identification number exists in the Crossroads Bank of enterprises or the CKO2 database but is assigned to an other type of person (legal entity/natural person)

3006 Date/year of birth not coherent with the data in the number of National Register of Natural Persons

3007 The identification matching is not conclusive between the enterprise number and name, legal form and postcode. Check your data

3008 The debtor identification matching is not conclusive. The debtor cannot be identified. Check your data

3009 The identification matching is not conclusive between the enterprise number and family name, first name and postcode. Check your data

2010 Incorrect check-digit


12. Messages

Version 1.4 - 02/11/2011

3011 The identification matching is not conclusive between the number of National Register of Natural Persons and family name, first name and postcode. Check your data

3012 The debtor is deceased according to the National Register of Natural Persons

3013 The same composition of codebtors already exists for an association but with an other participant internal number

3014 The same participant internal number already exists for an association with an other composition of codebtors

3016 Participant code not existing in the database of CKO2. Check your data and modify the code or contact the CCCR back office

2017 The element FOREIGN_HEADQUARTERS is missing

3020 Participant internal number of an other association present in the reported association. An association is not allowed as codebtor in an other association

2021 The reporting date is incorrect. It must be a previous month

2024 Probability of default not valid. It exceeds 100,00 %

3029 Participant code not existing in OneGate. Check your data and modify the code or contact the CCCR back office

2032 A date/period of default in the future is not allowed

3051 The enterprise number of the debtor does not exist in the Crossroads Bank of Enterprises

3052 The number of the debtor does not exist in the National Register of Natural Persons

3053 Date or year of birth too old (debtor more than 118 year old)

2054 ISO-country code incorrect. It must be equal to BE for resident debtors


12. Messages

Version 1.4 - 02/11/2011

2055 ISO-country code incorrect. It must be different from BE for non-resident debtors

2056 ISO-country code incorrect. It must be different from BE for foreign Headquarters

2057 New internal participant debtor not valid. It is equal to the old one.

2058 Amount zero not valid for a "90 days past due" default

2059 Date/year of birth is not valid. It cannot be a date/year in the future

3101 Internal participant number not existing in the database. The id number and data of the foreign registered office must be first reported

3102 Credit data already existing for the reporting date

3106 Debtor not registered in the database for your institution

3111 Identification numbers in the reported association, although they are different, relate to a same debtor

3112 Credit data already present for the debtor in the database for your institution at the reporting date self or at a more recent date

3113 A STOPCRED has already been reported for your institution at the reporting date self or at a more recent date

3116 The reporting date is incorrect. It may not be different from the last 12 ends of month

2120 Country ISO-code different from the country ISO-code mentioned in the FOREIGN_HEADQUARTERS element. They must be equal

3126 Credit data is not present for the debtor at that reporting date for your institution

2130 The same id number may not be present more than once in the same association


12. Messages

Version 1.4 - 02/11/2011

3131 Codebtor not existing in the database for your institution

3135 Participant internal number already existing in the database for a debtor

3136 Participant internal number already existing in the database with an address corresponding to an other type (resident/non resident) of debtor natural person

2139 Authorized or used amount with the same combination of dimensions already existing in the report

2140 Used amount reported for a credit mode for which only an authorized amount is allowed 3061 The debtor to be deleted is also a codebtor in an association and cannot be deleted in that

case


13. Glossary and abbreviations

Version 1.4 - 02/11/2011

13. Glossary and abbreviations Action code Name of a set of data to report that is necessary to achieve a specific given result in the

CKO2 database Action unit Set of data corresponding to an action code CBE Crossroads Bank of Enterprises (Banque-carrefour des entreprises - Kruispuntbank van

ondernemingen) CCCR Central Corporate Credit Register (Centrale des crédits aux entreprises - Centrale voor

kredieten aan ondernemingen) CKO2 Name of the new CCCR concept (legislation, rules and IT application) CKO2 DB DataBase of CKO2 CKO2 application IT application to run CKO2 Declarer See Participant Enterprise number Name of the identification number of a resident legal entity or of a natural person (resident or

not) in the CBE File See Report. id n° Identification number M Mandatory NBB National Bank of Belgium (Banque nationale de Belgique - Nationale bank van België) NRNP National Register of Natural Persons (Registre national des personnes physiques -

Rijksregister van natuurlijke personen) O Optional OneGate NBB portal name to access the CKO2 application for reporting (A2A and U2A channel) to the

CCCR, for fetching the outputs (A2A and U2A channels) produced by the application (except the consultation function) and for exchanging messages with the CCCR back office (U2A channel)


13. Glossary and abbreviations

Version 1.4 - 02/11/2011

Participant Institution reporting data to the CCCR and under the name of which the data must be registered in the CKO2 database

Report Homogeneous set of data sent by a participant to be registered in the CKO2 database

according to the specified action codes. Corresponds to a file. S Single element Third party declarer Institution sending data on behalf of a participant

technical documentation - reporting functions - reporting v1.4... · 2011-11-04 · technical...

Documents