Batch User Guide produced by CRIF - Janata Bank
Batch User Guide produced by CRIF - Janata Bank Batch User Guide produced by CRIF - Janata Bank
4.4 PHASE FLOWS RQ RN RF Monthly contribution begins. Possible following phases are: The contract will be “LV” until its closure. LV RN RF TM TA Legend: This phase refers to online updates (new contract enquiry). This phase refers to batch updates (monthly contribution). Notes: Contracts in RQ phase theoretically can be contributed also in monthly batches. However, since all the compulsory fields have to be filled in this case as well, it is not recommended to use the RQ phase in batch files unless the FI has complete and accurate information from a customer. 20 of 92
Table – Country Code This list states the country names (official short names in ENGLISH) in alphabetical order as given in ISO 3166-1 with the addition of some historical country names, and the corresponding ISO 3166-1-Alpha-2 code elements. For the complete listing of available values please refer to table 5.4.23. Table – Currency Code This list states the country currencies (official short names in ENGLISH) in alphabetical order as given in ISO 4217. For the complete listing of available values please refer to table 5.4.24. 5 RECORD LAYOUTS As we have seen in the following sections the monthly contribution contains both a Subject Data file and a Contract Data file. We will examine each in turn. Please refer to section 3.6 for the technical rules of completing the fields. 5.1 SUBJECT DATA FILE The Subject Data File is a continuous, space delimited .txt file that has between 2 and 9.999.999 rows of information. The first row (and only the first row) will ALWAYS be the Header. Please refer to table 5.1.1 for the rules to fill the header row. The last row (and only the last row) will ALWAYS be the Footer. Please refer to Annex 5.1.1 for the rules to fill the footer row. In between the header and the footer, there will be a varying number of lines, each carrying different sets of information. ALL rows (including the Header and the Footer) will ALWAYS be 1100 characters long, but the composition of each row depends on the type of information that is being provided in that particular line. Specifically, the type of information that the Subject Data file provides are the following: • 0 to “n” rows of 1100 chars each of identification information of Individuals as well as • 0 to “n” rows of 1100 chars each of identification information of Sole Proprietorships as well as • 0 to “n” rows of 1100 chars each of identification information of Companies as well as • 0 to “n” rows of 1100 chars each of information that links specific individuals to specific companies as owners Depending on which of the above information a particular row contains, different rules must be used to fill out such row. Therefore if a particular row contains Individual information, for example, the instruction provided in “Body for Record Type: Personal Data” of 5.1.1 need to be followed. Conversely if the information in the row is a link between owners and companies, the row must be filled out according to the rules in “Body for Record Type: Company-Shareholders”. While all rows will be 1100 characters long, each section will have a specific number of characters (for example 23 in header, 691 in Body for Record Type: Personal Data) that are data, and the difference from that number and 1100 that are simply spaces that make up a “Filler”. In any row, the first character will always be the “Record Type”. This allows the System to know what format to expect in the specific row. In our examples above, the row that contained data on 21 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: for Alphanumeric Fields: right padd
- 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 and 36: Please note that the order in which
- Page 37 and 38: The Column “TO” provides the po
- 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
Table – Country Code<br />
This list states the country names (official short names in ENGLISH) in alphabetical order as<br />
given in ISO 3166-1 with the addition of some historical country names, and the corresponding<br />
ISO 3166-1-Alpha-2 code elements. For the complete listing of available values please refer to<br />
table 5.4.23.<br />
Table – Currency Code<br />
This list states the country currencies (official short names in ENGLISH) in alphabetical order as<br />
given in ISO 4217.<br />
For the complete listing of available values please refer to table 5.4.24.<br />
5 RECORD LAYOUTS<br />
As we have seen in the following sections the monthly contribution contains both a Subject Data<br />
file and a Contract Data file. We will examine each in turn.<br />
Please refer to section 3.6 for the technical rules of completing the fields.<br />
5.1 SUBJECT DATA FILE<br />
The Subject Data File is a continuous, space delimited .txt file that has between 2 and 9.999.999<br />
rows of information.<br />
The first row (and only the first row) will ALWAYS be the Header. Please refer to table 5.1.1 for<br />
the rules to fill the header row.<br />
The last row (and only the last row) will ALWAYS be the Footer. Please refer to Annex 5.1.1 for<br />
the rules to fill the footer row.<br />
In between the header and the footer, there will be a varying number of lines, each carrying<br />
different sets of information.<br />
ALL rows (including the Header and the Footer) will ALWAYS be 1100<br />
characters long, but the composition of each row depends on the type<br />
of information that is being provided in that particular line.<br />
Specifically, the type of information that the Subject Data file provides<br />
are the following:<br />
• 0 to “n” rows of 1100 chars each of identification information of<br />
Individuals as well as<br />
• 0 to “n” rows of 1100 chars each of identification information of<br />
Sole Proprietorships as well as<br />
• 0 to “n” rows of 1100 chars each of identification information of<br />
Companies as well as<br />
• 0 to “n” rows of 1100 chars each of information that links<br />
specific individuals to specific companies as owners<br />
Depending on which of the above information a particular row contains,<br />
different rules must be used to fill out such row. Therefore if a<br />
particular row contains Individual information, for example, the<br />
instruction provided in “Body for Record Type: Personal Data” of 5.1.1<br />
need to be followed. Conversely if the information in the row is a link<br />
between owners and companies, the row must be filled out according to the rules in “Body for<br />
Record Type: Company-Shareholders”.<br />
While all rows will be 1100 characters long, each section will have a specific number of<br />
characters (for example 23 in header, 691 in Body for Record Type: Personal Data) that are<br />
data, and the difference from that number and 1100 that are simply spaces that make up a<br />
“Filler”.<br />
In any row, the first character will always be the “Record Type”. This allows the System to know<br />
what format to expect in the specific row. In our examples above, the row that contained data on<br />
21 of 92