09.01.2015 Views

Batch User Guide produced by CRIF - Janata Bank

Batch User Guide produced by CRIF - Janata Bank

Batch User Guide produced by CRIF - Janata Bank

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

5.2.4 SPECIAL NOTES FOR THE REPORTING OF LINKS<br />

Since you are providing a separate file for Subjects (see 5.1), and a separate file for Contracts,<br />

there needs to be a way to link each specific contract to one (or more) specific Subjects.<br />

In particular, each contract must be linked to one, and only one, specific Borrower.<br />

Additionally, each contract can be linked to one, or more, specific Co-Borrowers and/or one, or<br />

more, specific Guarantors. This means that the relationship between Contract and Borrower is<br />

one-to-one, while the relationship between Contract and Co-Borrower as well as between<br />

Contract and Guarantor is one-to-many. As these relationships are different, not surprisingly the<br />

way to contribute the relationship to the system is also different.<br />

5.2.4 Contract-Borrower link<br />

In order to link a specific Contract to a Specific Borrower, you will simply have to pass the F.I.<br />

Subject Code in the same line as the contract.<br />

In other words, when passing the contract information (and remember, each specific contract will<br />

be passed as one line in the batch contribution), in section “Body for Record Type: General<br />

information for all types of Financing” you will enter the F.I. Subject Code in positions 9 to 24<br />

(please see 5.2.5). Again, each contract MUST have one and only one Subject associated with it.<br />

The Subject must either be contributed as part of the Subject file in the same batch submission,<br />

or must have been submitted in the past <strong>by</strong> the Institution in a separate batch submission<br />

(otherwise the contract will go in error and be stored in the anomalies tables).<br />

As the contract information is sent each month, and the F.I. Subject Code of the Borrower is a<br />

mandatory field of the Contract contribution, this information is sent each month during the<br />

lifecycle of the contract.<br />

5.2.4 Contract-Co Borrower and Contract-Guarantor link(s)<br />

Instead, if you want to contribute any number of Co Borrowers, and/or a Guarantors on the<br />

contract, this information needs to be passed as a separate line in the batch submission for each<br />

Subject being linked.<br />

Therefore, for each Co Borrower and/or Guarantor on a contract, you will enter a separate row in<br />

the contract file, following the rules set out in “Body for Record Type: contract Links” section<br />

under 5.2.5 below. This line will include the F.I. Contract Code to identify the specific contract we<br />

are talking about (and such contract must be contributed within the same contract file or must<br />

have been contributed <strong>by</strong> the Institution in the past), the F.I. code of the specific Co Borrower or<br />

Guarantor that we are trying to link (called here F.I. Secondary Code), as well as the F.I. code<br />

of the main Borrower (called here F.I. Primary Secondary Code) which must match what was<br />

contributed in the specific contract row as indicated in 5.2.3.<br />

It is enough to send the Co Borrowers and Guarantors on a specific Contract once, it is not<br />

necessary to send the same link each month. At the same time, if you provide the same link<br />

each month for the same Contract this will not cause errors. If instead you send a new Co<br />

Borrower or a New Guarantor link on an existing Contract, the System will add the link. On the<br />

other hand, if you need to remove a Co Borrower or a Guarantor you cannot do so directly, but<br />

must contact CIB (please see 6.1)<br />

5.2.5 CONTRACT DATA FILE RULES<br />

The following table details the correct procedure to validate the Contract Data File. Some cells<br />

refer to Tables that are provided in the following sections<br />

The Column “FROM” provides the position in the row where the first character of the specific field<br />

that is being passed begins on.<br />

36 of 92

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!