Batch User Guide produced by CRIF - Janata Bank
Batch User Guide produced by CRIF - Janata Bank Batch User Guide produced by CRIF - Janata Bank
5.2.4 SPECIAL NOTES FOR THE REPORTING OF LINKS Since you are providing a separate file for Subjects (see 5.1), and a separate file for Contracts, there needs to be a way to link each specific contract to one (or more) specific Subjects. In particular, each contract must be linked to one, and only one, specific Borrower. Additionally, each contract can be linked to one, or more, specific Co-Borrowers and/or one, or more, specific Guarantors. This means that the relationship between Contract and Borrower is one-to-one, while the relationship between Contract and Co-Borrower as well as between Contract and Guarantor is one-to-many. As these relationships are different, not surprisingly the way to contribute the relationship to the system is also different. 5.2.4 Contract-Borrower link In order to link a specific Contract to a Specific Borrower, you will simply have to pass the F.I. Subject Code in the same line as the contract. In other words, when passing the contract information (and remember, each specific contract will be passed as one line in the batch contribution), in section “Body for Record Type: General information for all types of Financing” you will enter the F.I. Subject Code in positions 9 to 24 (please see 5.2.5). Again, each contract MUST have one and only one Subject associated with it. The Subject must either be contributed as part of the Subject file in the same batch submission, or must have been submitted in the past by the Institution in a separate batch submission (otherwise the contract will go in error and be stored in the anomalies tables). As the contract information is sent each month, and the F.I. Subject Code of the Borrower is a mandatory field of the Contract contribution, this information is sent each month during the lifecycle of the contract. 5.2.4 Contract-Co Borrower and Contract-Guarantor link(s) Instead, if you want to contribute any number of Co Borrowers, and/or a Guarantors on the contract, this information needs to be passed as a separate line in the batch submission for each Subject being linked. Therefore, for each Co Borrower and/or Guarantor on a contract, you will enter a separate row in the contract file, following the rules set out in “Body for Record Type: contract Links” section under 5.2.5 below. This line will include the F.I. Contract Code to identify the specific contract we are talking about (and such contract must be contributed within the same contract file or must have been contributed by the Institution in the past), the F.I. code of the specific Co Borrower or Guarantor that we are trying to link (called here F.I. Secondary Code), as well as the F.I. code of the main Borrower (called here F.I. Primary Secondary Code) which must match what was contributed in the specific contract row as indicated in 5.2.3. It is enough to send the Co Borrowers and Guarantors on a specific Contract once, it is not necessary to send the same link each month. At the same time, if you provide the same link each month for the same Contract this will not cause errors. If instead you send a new Co Borrower or a New Guarantor link on an existing Contract, the System will add the link. On the other hand, if you need to remove a Co Borrower or a Guarantor you cannot do so directly, but must contact CIB (please see 6.1) 5.2.5 CONTRACT DATA FILE RULES The following table details the correct procedure to validate the Contract Data File. Some cells refer to Tables that are provided in the following sections The Column “FROM” provides the position in the row where the first character of the specific field that is being passed begins on. 36 of 92
The Column “TO” provides the position in the row where the last character of the specific field that is being passed ends on. The Column “Description” indicates what specific field is being passed. The Column “COMMENTS” provides comments on the field being passed. Most times these comments will better define what the field is, or give examples of values it could take. In the case of “Dependent” fields (please see below), it indicates the dependency. The Column “TYPE” indicates whether the field is Numeric (N) or Alphanumeric (X). Please refer to section 4.3.4 and 4.3.5 for more information. The Column “MANDATORY/NON MANDATORY/DEPENDENT” indicates whether the field must be provided every time or not necessarily. Any fields marked as Mandatory (M) for a specific row must be provided or that row will result in an error and will not be loaded to the System. Any fields marked as Non-Mandatory (NM) for a specific row can be provided or not, at the discretion of the contributing FI. While not providing NM fields will not result in an error, WE STRONGLY SUGGEST that if the information is available it should be provided. The more information provided to the System, the more effective the System becomes, and the highest the value of the System becomes for Banks. Any fields marked as Dependent (D) could be either mandatory or not depending on the value of other fields. A specific indication is provided for each of these fields to indicate when the fields are mandatory and when not. The Column “LENGTH” provides the total number of characters that make up the field. It is directly related to the “FROM” and “TO” columns. The Column “RULES” provides specific information on any rules that exist to fill the specific field, such as formatting rules (for example if a field must be entered DDMMYYYY), or indication of specific values (for example "H" for the header). 37 of 92
- Page 1 and 2: Userguide Manual - Batch Monthly Co
- Page 3 and 4: 5.4.14 TABLE REAL GUARANTEE TYPE __
- Page 5 and 6: Added section 5.2.1, 5.2.3, and 5.2
- Page 7 and 8: New Credit Line Data - New Contract
- Page 9 and 10: 3.4 WHY SHOULD I SEND REQUESTS One
- Page 11 and 12: Therefore, please make sure that ev
- Page 13 and 14: 4 INSTRUCTIONS FOR DRAFTING DATA CO
- Page 15 and 16: assumes some changes in the month o
- Page 17 and 18: 4.2.1 FTPS The monthly contribution
- Page 19 and 20: for Alphanumeric Fields: right padd
- Page 21 and 22: Table - Country Code This list stat
- Page 23 and 24: FROM TO FIELD NAME COMMENTS TYPE Ma
- Page 25 and 26: avaliable/not available available,
- Page 27 and 28: 166 166 Sector Type the field is ma
- Page 29 and 30: 801 801 National ID Number avaliabl
- Page 31 and 32: 173 184 T.I.N. Taxpayer Identificat
- Page 33 and 34: and footer rows) Data Length 27 28
- Page 35: Please note that the order in which
- Page 39 and 40: 84 91 Date of Last Payment The date
- Page 41 and 42: Body for Record Type: Cards contrac
- Page 43 and 44: data belong 9 24 F.I. Subject Code
- Page 45 and 46: 108 117 Error Code See table errors
- Page 47 and 48: Q T C S Y I quarterly instalments-9
- Page 49 and 50: 034 Merchandise Export Commodities
- Page 51 and 52: 113303 Bangla Academy 113304 Bangla
- Page 53 and 54: 121710 Ansar-VDP Development Bank 1
- Page 55 and 56: 909299 Others 909100 Insurance Comp
- Page 57 and 58: BU MC BC BB MS TR PH MP MT FI BS PC
- Page 59 and 60: 2102 Electric / Electronic Goods (F
- Page 61 and 62: 8412 Chemicals (except Medicine) 84
- Page 63 and 64: EL SALVADOR EQUATORIAL GUINEA ERITR
- Page 65 and 66: NORWAY OMAN PAKISTAN PALAU PALESTIN
- Page 67 and 68: AWG AZN BAM BBD BDT BGN BHD BIF BMD
- Page 69 and 70: NIO NOK NPR NZD OMR PAB PEN PGK PHP
- Page 71 and 72: Jhalokathi Jinaidaha Joypurhat Khag
- Page 73 and 74: 4 053 Multiple headers in Subject f
- Page 75 and 76: 10 157 Total financed amount = [0]
- Page 77 and 78: 10 345 Contract refers to subject i
- Page 79 and 80: Company 1: Individual 2: 79 of 92
- Page 81 and 82: Contracts file: Non instalment Cont
- Page 83 and 84: Subject information for Proprietors
- Page 85 and 86: Please note: this does not apply to
The Column “TO” provides the position in the row where the last character of the specific field<br />
that is being passed ends on.<br />
The Column “Description” indicates what specific field is being passed.<br />
The Column “COMMENTS” provides comments on the field being passed. Most times these<br />
comments will better define what the field is, or give examples of values it could take. In the<br />
case of “Dependent” fields (please see below), it indicates the dependency.<br />
The Column “TYPE” indicates whether the field is Numeric (N) or Alphanumeric (X). Please refer<br />
to section 4.3.4 and 4.3.5 for more information.<br />
The Column “MANDATORY/NON MANDATORY/DEPENDENT” indicates whether the field must be<br />
provided every time or not necessarily. Any fields marked as Mandatory (M) for a specific row<br />
must be provided or that row will result in an error and will not be loaded to the System. Any<br />
fields marked as Non-Mandatory (NM) for a specific row can be provided or not, at the discretion<br />
of the contributing FI. While not providing NM fields will not result in an error, WE STRONGLY<br />
SUGGEST that if the information is available it should be provided. The more information<br />
provided to the System, the more effective the System becomes, and the highest the value of<br />
the System becomes for <strong>Bank</strong>s. Any fields marked as Dependent (D) could be either mandatory<br />
or not depending on the value of other fields. A specific indication is provided for each of these<br />
fields to indicate when the fields are mandatory and when not.<br />
The Column “LENGTH” provides the total number of characters that make up the field. It is<br />
directly related to the “FROM” and “TO” columns.<br />
The Column “RULES” provides specific information on any rules that exist to fill the specific field,<br />
such as formatting rules (for example if a field must be entered DDMMYYYY), or indication of<br />
specific values (for example "H" for the header).<br />
37 of 92
Change language