3.9 METHODS OF SENDING MONTHLY DATA MONTHLY CONTRIBUTION: The SUBSCRIBER must ensure that the monthly contribution reaches CIB <strong>by</strong> the 20 th of every month, sending data relating to the previous month (e.g. for 20 th July, the data refer to the month up to the 30 th June). For technical details regarding the contribution please refer to section 4.2 12 of 92
4 INSTRUCTIONS FOR DRAFTING DATA CONTRIBUTIONS 4.1 CONTRIBUTION FILES The data contribution must include the following two separate files with the specified information every month: a Contract Data file and a Subject Data file. 4.1.1 CONTRACT DATA FILE It is a single Contract Data file, which contains: o all Contracts (installment, non installment, credit card and revolving credit operations) that were Approved, Refused or Renounced in the reference month. o all existing (living) Contracts that were reported in the previous month or in previous months. PLEASE NOTE: • even if nothing has changed in the contract, once a contract is existing (living), all the relevant information must be sent each month. o all Contracts that terminated (i.e. were closed) during the reference month, whether these contracts were closed at the natural end of the contract (closed), or were terminated prior to the natural and expected end of the contract for whatever reason (closed in advance). For example, an Instalment Loan that was fully repayed on time will be closed. An Instalment Loan that was fully repayed months before it expired is closed in advance. The same goes for Non-Instalment loans. o Y score, Z score, and Grading (optional) o all links that indicate for each Contract, any new Co-Borrower or Guarantor. PLEASE NOTE: • Each contract can have one and only one Borrower, identified via the FI Subject code. • Co-Borrowers and Guarantors are provided as specific links. • Please refer to section 4.1.3 for further information. It follows from the above indications that the Contract Data file WILL NOT contain: o open requests, that is those that have not yet been Approved, Refused or Renounced yet. These are reported via the online channel, not the batch channel o requests that were Refused or Renounced in previous months, and for which a contribution indicating status as Refused or Renounced has already been provided. For the sake of clarity, let‟s say a Subject “A” provides a request to <strong>Bank</strong> 1 for credit on May 1 st . The <strong>Bank</strong> provides an online enquiry that automatically writes the Request to the System via the online channel. On June 10 th the bank Refuses the request. Therefore in the May contribution (which must be sent to CIB <strong>by</strong> June 20 th , and in our example is sent on June 5 th ) no info is provided via batch on the Request. In the June contribution (which must be sent to CIB <strong>by</strong> July 20 th , and in our example is sent on July 5 th ) <strong>Bank</strong> 1 will update the request as Refused. In the July contribution (which must be sent to CIB <strong>by</strong> August 20 th , and in our example is sent on August 5 th ) <strong>Bank</strong> 1 will no longer report any information on the Refused request. o contracts that were Closed or Closed in advance in previous months, and for which a contribution indicating status as Closed or Closed in advance has already been provided. For the sake of clarity, let‟s say a Subject “A” has an existing Contract at <strong>Bank</strong> 1 for credit set to expire on June 30 th which is repayed in full and on time. Therefore in the May contribution (which must be sent to CIB <strong>by</strong> June 20 th , and in our example is sent on June 5 th ) the Contract Data is regularly sent to CIB as the contract is ongoing. In the June contribution (which must be sent to CIB <strong>by</strong> July 20 th , and in our example is sent on July 5 th ) <strong>Bank</strong> 1 will update the Contract status as Closed. In the July contribution (which must be sent to CIB <strong>by</strong> August 20 th , and in our example is sent on August 5 th ) <strong>Bank</strong> 1 will no longer report any information on the Contract. 13 of 92