3. Appendix B - Upload File Formats B

This chapter contains the following sections:

• Section 3.1, "Fund Rules Upload Formats"
• Section 3.2, "Incremental Upload Format"
• Section 3.3, "Sub Service Upload Format"
• Section 3.4, "Entity Upload Format"
• Section 3.5, "Broker Upload Format"
• Section 3.6, "Unit Holder Upload Format"
• Section 3.7, "Transactions Upload Format"

3.1 Fund Rules Upload Formats

This section contains the following topics:

• Section 3.1.1, "Segment Identification Number"
• Section 3.1.2, "Fund Rules Upload Segment Formats"
• Section 3.1.3, "PROCESSINGFREQ (ref 11FLM, 12.10)"
• Section 3.1.4, "Fund Related Information Upload Segments Format"
• Section 3.1.5, "EPU Upload File Format"
• Section 3.1.6, "Tax Aggregation Interface Format"
• Section 3.1.7, "Agent Reference File"
• Section 3.1.8, "Global Order Placement Interface"
• Section 3.1.9, "GL Setup Upload Interface Format"
• Section 3.1.10, "Interface to Check for Transaction Unrelated to GL Extraction "
• Section 3.1.11, "File Format for OMIPAY FILE INTERFACE"
• Section 3.1.12, "File format for Header Record"
• Section 3.1.13, "File format for Detailed Record"

3.1.1 Segment Identification Number

The upload file would contain various segment identification number in the first column to indicate the type of data that is present in that entire row. Each segment identified by a unique tag, indicates the type of fund rule information such as Demographics, Shares Characteristics and so on. The possible segments that would be used in Fund upload are given below for reference:

Segment Identification Number	Description	Segment Mandatory / Optional?	Multiple records allowed for the same Fund and Rule Effective Date
00GEN	This segment is used for providing information com­mon to the other fund rules that need to be uploaded in the system.	Mandatory; and will be the driving header segment for all the other segments.	No
01FDR	This segment is used for providing Fund Demograph­ics related information	Mandatory	No
02SCR	This segment is used for providing Shares Charac­teristics related information	Mandatory	No
03GOR	This segment is used for providing General Operat­ing rules information	Mandatory	No
04TPR	This segment is used for providing Transaction pro­cessing rules information	Mandatory	Yes (For each transaction type - there is a separate record)
05TCM	This segment is used for providing Transaction Pro­cessing Communication Mode information	Mandatory	Yes (For each transaction type - there is a separate record)
06INV	This segment is used for providing Transaction Pro­cessing Investor Category related information	Mandatory	Yes (For each transaction type - there is a separate record)
07IDR	This segment is used for providing Corporate Action related information	Optional	Yes (For cash and Stock dividend information)
08FSC	This segment is used for providing Fund Sale Coun­try information	Mandatory	Yes
09FRL	This segment is used for providing Fund Residency List information	Mandatory	Yes
10FFM	This segment is used for providing Fund Formula information	Optional	Yes
11FLM	This segment is used for providing Fund Load infor­mation	Optional	Yes
12FTC	This segment is used for providing Fund Transaction Currency information	Mandatory	Yes
13FAI	This segment is used for providing Fund Additional Information	Mandatory	No
14IRA	This segment is used for providing Fund IRA Infor­mation, if applicable	Optional	No
15FDI	This segment is used for providing Fund Delivery Instructions, if applicable	Optional	No
17KYC	This segment is used for providing the Customer document details, if applica­ble	Optional	Yes
18MLD	This segment is used for providing Multi language details, if applicable	Optional	Yes
19FSI	This segment is used for providing Fund Investment Account SI, if applicable	Optional	Yes
20HFP	This segment is used to include hedge fund parame­ters	Optional	No
21HFL	This segment is used to provide hedge fund linkage details	Optional	Yes
22HFD	This segment is used to provide investor category details for hedge funds	Optional	Yes

Each of the segments have variable list of fields stored as information pertaining to that segment. The list of fields for each segment is mentioned in the following tables along with the description of the segment.

3.1.2 Fund Rules Upload Segment Formats

Serial Number: 1

Segment Identification Number: 00GEN

Description: This segment is used for providing information that is common to the other fund rules that need to be uploaded in the system

Mandatory: Mandatory and will be the driving header segment for all the other segments.

Multiple records allowed for the same fund and Rule Effective Date: No

Field Name	Type	Maximum Length	Mandatory / Optional?	Characteristics / Validations applicable	Description
PROCESSID	Alphanu­meric	50	Mandatory		This should iden­tify the upload uniquely. This should also be unique within a file and it allows to identify imported records later
BULKCLI­ENTCODE	Alphanu­meric	12	Mandatory		Valid authorized, enabled Bulk cli­ent codes main­tained in the system as a part of Entity Mainte­nance.
IMPORT­FILENAME	Alphanu­meric	255	Mandatory		This is the name of the file being uploaded into the FCIS system
AMCID	Alphanu­meric	12	Mandatory		Valid authorized, enabled AMC maintained in the system as a part of Entity Mainte­nance. The fund rule upload defaulting would be based on both AMCID and the Bulk client code.
USERID	Alphanu­meric	15	Mandatory		The fund rule MakerID would have the value of UserID as a part of data storage in all the fund rule tables.
UPLOAD­MODE	Alphanu­meric	1	Mandatory	Valid values are 'N' and 'I'	Should be 'N' for New fund rule, and ‘I’ for Incre­mental for amend­ing an existing authorized fund rule.
GENERA­TEAUTH­FUNDRULE	Alphanu­meric	1	Optional	Valid values are 'A' and 'U'	This indicates whether the fund rule uploaded should be a authorized fund rule or un-author­ized fund rule.
DEFAULTOPTION	Alphanu­meric	15	Optional	Valid values are Null which means 'No defaulting'; 'BULKCLI­ENT­CODE' means defaulting information based on Bulk Client code men­tioned as a part of this segment; existing valid tem­plate id based on which defaulting would hap­pen	This indicates if data needs to be defaulted based on any existing templates or based on bulk cli­ent code.

Serial Number: 2

Segment Identification Number: 01FDR

Description: This segment is used for providing Fund demographics related information

Segment Mandatory / Optional: Mandatory

Multiple records allowed for the same Fund and Rule Effective Date: No

Field Name	Type	Maximum Length	Mandatory / Optional?	Characteristics / Validations applicable	Description
SEG­MEN­TID	Alpha­numeric	20	Mandatory	Default value 01FDR	Standard value of 01FDR to uniquely identify Fund demographics information
PRO­CESSID	Alpha­numeric	50	Mandatory	Same value as in 00GEN - Pro­cessID	This should iden­tify the upload uniquely. This should also be unique within a file and it allows to identify imported records later
FUNDID	Alpha­numeric	6	Mandatory		The Fund ID is a unique Identifica­tion for each Fund in the system. Enter a unique value for the fund for which a Fund Demographics record is being set up
RULEEFFEC­TIVE­DATE	Date	8	Mandatory	The Rule Effec­tive Date should be later than (or same as) the Fund Start Date and it should also be later than (or same as) the current application date of the system.	Specify the date from when the Fund Demograph­ics Rule that is cur­rently being set up should become effective.
FUND­START­DATE	Date	8	Mandatory		Specify the date upon which the fund is to begin operations
FUND­NAME	Alpha­numeric	60	Mandatory		Enter the name of the fund for which the Fund Demo­graphics profile is being set up in this record
FUND­NAMESHORT	Alpha­numeric	15	Mandatory		Enter the short name of the fund for which the Fund Demographics profile is being set up in this record
FUND­CLASS	Alpha­numeric	1	Optional	Valid values are 'O' for Open-ended and 'C' for Closed-ended	Enter the fund class as either Open Ended and Closed-Ended Funds
FUND­TYPE	Number	38	Optional	Valid Fund types defined in the system	Enter the value of Fund Type. The Fund Types are set up as a part of the Fund Type Maintenance.
FUND­FAMILY	Alpha­numeric	2	Optional	Valid Fund fami­lies defined in the system	Enter the fund family under which the fund must be placed
FUND­BASE­CURRENCY	Alpha­numeric	3	Optional	Valid Currency code defined in the system	Specify the cur­rency code in which the fund will be denominated. The NAV and divi­dend declarations for the fund will be in this base cur­rency.
FUND­COUN­TRY	Alpha­numeric	3	Optional	Valid Domicile code defined in the system as a part of Params Maintenance	Enter the country of domicile of the fund. This informa­tion will be used to determine whether a unit holder that subscribes to the fund must be con­sidered a Foreign unit holder or not
FIS­CAL­STARTYEAR	DATE	8	Optional	The Fiscal Start Date must be earlier than the application date and the Rule Effective Date of the fund	Enter the date from when the Fis­cal Year should start for the fund
FISCA­LEND­YEAR	DATE	8	Optional	The Fiscal End Date should be later than (or same as) the current date of the system. It should also be later than (or same as) the Rule Effective Date of the fund that is being set up.	Enter the date on which the Fiscal Year should end for the fund
AMCID	Alpha­numeric	12	Optional	Valid authorized AMC defined in the system as a part of entity maintenance	Specify the AMC that this Fund will be operative in
BRO­KER­SALLOWED	Number	1	Optional	Valid values are 1 and 0	if brokers are to be mandatory for the given Fund, then a value of '1' should be entered else enter 0.
REGIS­TRARID	Alpha­numeric	12	Optional	Valid Registrar defined in the system as a part of Entity mainte­nance	Enter the Registrar ID for the fund being set up
TRUS­TEEID	Alpha­numeric	12	Optional	Valid Trustee defined in the system as a part of Entity mainte­nance	Enter the Trustee ID for the fund being set up
FUNDENABLED	Number	1	Optional	Valid values are 1 and 0	Every new fund is created in the sys­tem initially as an enabled fund. Hence, the value can be defaulted to 1
MIN­HOLD­INGPERIOD	Number		Optional		Enter the lock in period for the investors invest­ing in the fund so that outflow trans­action would be possible only after this period
MINAMOUNT­FOR­TAXID	Number	15	Optional	Maximum of 3 decimal places allowed	Enter the minimum subscription / IPO subscription amount beyond which it is neces­sary / preferable to capture the Tax details for any unit holder.
PRIMA­RYRE­GADDRESS	Alpha­numeric	255	Optional		Registered Address for the fund
FUND­TAXID	Alpha­numeric	25	Optional		Unique Tax ID for the fund
FUN­DIDEN­TIFICATION­NUM­BER	Alpha­numeric	25	Mandatory for DEKA Installation. For others this is optional.		Fund ISIN number that helps to uniquely identify the fund
FUND­TICK­ERSYMBOL	Alpha­numeric	25	Optional		This is another value that helps to uniquely identify the fund. How­ever, if this is not applicable, it can be entered as null also.
ALLOWIRAIN­VEST­MENTS	Number	1	Optional	Valid values are 0 and 1	Only if IRA trans­actions are allowed, the value should be speci­fied as 1. Else specify 0.
CUSTO­DIAN	Alpha­numeric	12	Optional	Valid custodian defined in the system as a part of Entity mainte­nance	Enter the Custo­dian for the fund being set up
HEDGE FUND	Alpha­numeric	1	Optional	Valid values are 0 and 1	Indicate whether the fund is a hedge fund

Serial Number: 3

Segment Identification Number: 02SCR

Description: This segment is used for providing Shares Characteristics related information

Segment Mandatory/Optional? : Mandatory

Multiple records allowed for the same Fund and Rule Effective Date: No

Field Name	Type	Maximum Length	Mandatory / Optional?	Characteristics / Validations applicable	Description
SEGMEN­TID	Alphanu­meric	20	Mandatory	Default value 02SCR	Standard value of 02SCR to uniquely identify Shares charac­teristics infor­mation
PROCES­SID	Alphanu­meric	50	Mandatory	Same value as in 00GEN - Pro­cessID	This should identify the upload uniquely. This should also be unique within a file and it allows to iden­tify imported records later
FUNDID	Alphanu­meric	6	Mandatory		The Fund ID is a unique Identi­fication for each Fund and it indi­cates the fund for which Shares charac­teristics infor­mation has to be uploaded
RULEEF­FECTIVE­DATE	Date	8	Mandatory	The Fund ID and Rule effec­tive date combi­nation should be the same as defined in 01FDR	The rule effec­tive date for which share characteristic information for the fund has to be maintained.
SCRIP­BASED	Number	1	Optional	Valid values are 0,1 and 2	This field is used to desig­nate the appli­cability of certificate issue for investment in the fund. The value '0' indi­cates 'Scrip­less'; '1' indicates 'Scrip based' and '2' indicates 'Certif­icate option'
PAR­VALUE	Number	15	Optional	Maximum of 6 decimal places allowed	Enter the Par Value for the fund. Normally, this will be the base price for Initial Public Offer (IPO) period, How­ever you can change the base price for IPO.
NOOF­DECI­MALSFORUNITS	Number	1	Optional		Indicate the maximum num­ber of decimals that would be reckoned for rounding preci­sion, for the number of allot­ted units. You cannot indicate a precision higher than 6 decimal places.
ROUND­OFFTRUNCATE	Alphanu­meric	1	Optional	Valid values are 'R' for Round off; 'T' for Round Down and 'U' for Round up	Indicate the rounding options for the value of the number of allot­ted units, desig­nated for the fund.
MINNOO­FUNITHOLDERS	Number	5	Optional		At any point of time, when the fund is ena­bled, the num­ber of unit holders cannot fall below this value. This value must not be lower than zero.
MAXNOO­FUNITHOLDERS	Number	5	Optional		At any point of time, when the fund is ena­bled, the num­ber of unit holders cannot go above this value.
MINREG­ISTEREDCAPITAL	Number	20	Optional	Maximum of 6 decimal places allowed	. At any point of time, when the fund is ena­bled, the fund corpus (regis­tered capital) cannot go below this value.
MAXREG­ISTEREDCAPITAL	Number	NUM­BER(30,12)	Optional	Maximum of 6 decimal places allowed	At any point of time, when the fund is ena­bled, the fund corpus (regis­tered capital) cannot go above this value.
CAPINDI­CATOR	Alphanu­meric	1	Optional	Valid values are 'A' and 'P'	This is to spec­ify the foreign investors’ limit to be defined either in per­centage of fund corpus or a flat Amount. Enter A if the foreign investors limit is in terms of an Amount and P for a percent­age of the Reg­istered Capital.
FOREIGN­INVES­TORSLIMIT	Number	NUM­BER(30,12)	Optional	Maximum of 6 decimal places allowed	Enter a value to specify the per­centage of fund corpus that for­eigners are allowed to hold. This could be either a per­centage of Fund Corpus or a flat Amount. If it is a percentage, then it cannot be greater than 100.
ACCOUNTSTATE­MENT­FREQ	Alphanu­meric	20	Optional	Valid values are 'F' or 'B' for Bi-weekly; 'M' for 'Monthly; 'Q' for 'Quarterly' ; 'H' for 'Half-yearly' ; 'Y' for 'Yearly'	This is to indi­cate the fre­quency with which the sys­tem should initi­ate the Account Statement pro­cessing
ACCOUNTSTATE­MENTLEADTIME	Number	3	Optional		Enter a lead-time in days..
PRINTAC­COUNT­STATEMENT	Number	1	Optional	Valid values are '1' to print and '0' for not to print account statement	This is to indi­cate that the Account State­ment to be printed for the fund that is being set up
PRINTHOLDINGS­STATE­MENT	Number	1	Optional	Valid values are '1' to print and '0' for not to print holding statement	This is to indi­cate that if the Holding State­ment to be printed for the fund that is being set up
STAND­ARDLOT	Number	1	Optional		Enter a value to specify the standard lot for fund. This is also the market­able lot
PREFIX­CERT­CODE	Alphanu­meric	1	Optional		Enter a charac­ter for this field. This will be used as prefix to the Certifi­cate Number
START­CERTIS­SUEDNO	Number	1	Optional		Enter a value for this field. This is just for information. For a new Fund, the Certificate Numbers will start from this number.
LASTCER­TIS­SUEDNO	Number	5	Optional		Enter a value for this field. This is to spec­ify that this was the last certifi­cate number that has been issued so far and system needs to start from next num­ber. For new funds, this could be zero. This is also equal to the Start Certifi­cate Issue Number in the case of new Funds
PREFIXD­NRCODE	Number	1	Optional		Enter a charac­ter for this field. This will be used as prefix to the Distinc­tive Number Record (DNR) Number. This information is only applicable if you have specified the number of deci­mals for units as zero, in the Number of Dec­imals for Units field in this screen.
STARTDN­RIS­SUEDNO	Alphanu­meric	1	Optional		Enter a value for this field. This is just for information. For new funds, this will be same as last DNR issued number. This information is only applicable if you have specified the number of deci­mals for units as zero, in the Number of Dec­imals for Units field in this screen.
LASTDN­RIS­SUEDNO	Number	5	Optional		Enter a value for this field. This is to spec­ify that this was the last DNR number that has been issued so far and system needs to start from next num­ber. For new funds, this could be zero. This is also equal to the Start Certifi­cate Issue Number in the case of new Funds. This information is only applicable if you have specified the number of deci­mals for units as zero, in the Number of Dec­imals for Units field in this screen
SIN­GLECER­TALLOWED	Number	1	Optional	Valid values are 0 and 1	This is to indi­cate whether a single certificate is needed for the transaction or multiple cer­tificates are needed. Valid values are 0 and 1 indicat­ing 'No' and 'Yes' option for Single certifi­cate allowed.
MINCERT­DENOMI­NATION	Number	5	Optional		Enter a value to specify the mini­mum certificate denomination. I.e., the next level of denomi­nation after the standard lot. The system will use this after exhausting the maximum certif­icate denomina­tions.
MAX­CERTDE­NOMINATION	Number	5	Optional		Enter a value to specify the maximum certif­icate denomina­tion. This is the first level of denomination used by the system.
USER­OVER­RIDEALLOWED	Number	1	Optional	Valid values are '0' and '1'	Enter value as '1' if the user on the unit holder’s request can override the default denomi­nations defined. If the User over­ride is allowed then, system will allow the teller to override the fund default denominations. This is true only for minimum and maximum denominations. The Standard lot cannot be changed. This is applicable only to scrip-based funds.
CER­TREQD	Number	1	Optional	Valid values are '0' and '1'	For scrip less funds, this value is to indicate that certificates must be issued to investors for block transac­tions in the fund.
MAXREG­ISTERE­DUNITS	NUM­BER	5	Optional		Capture the Maximum Units Registered Capital.
UHCA­TREG­CAPITAL	VAR­CHAR2	2000	Optional		Tilde separated string with Inv Category and Max Reg Units. Eg : PB~100;CO~200

Serial Number: 4

Segment Identification Number: 03GOR

Description: This segment is used for providing General Operating rules information

Segment Mandatory/Optional: Mandatory

Multiple records allowed for the same Fund and Rule Effective Date: No

Field Name	Type	Maximum Length	Mandatory / Optional?	Characteristics / Validations applicable	Description
SEG­MENTID	Alphanu­meric	20	Mandatory	Default value 03GOR	Standard value of 03GOR to uniquely iden­tify General Operating Rules information
PROCES­SID	Alphanu­meric	50	Mandatory	Same value as in 00GEN - Pro­cessID	This should identify the upload uniquely. This should also be unique within a file and it allows to iden­tify imported records later
FUNDID	Alphanu­meric	6	Mandatory		The Fund ID is a unique Identi­fication for each Fund and it indi­cates the fund for which Gen­eral operating rules informa­tion has to be uploaded
RULEEF­FECTIVE­DATE	Date	8	Mandatory	The Fund ID and Rule effec­tive date combi­nation should be the same as defined in 01FDR	The rule effec­tive date for which general operating rules information for the fund has to be maintained.
POST­PRICED	Number	1	Optional	Valid values are '0' and '1'	Enter '1'if the price for the fund will be announced Post Transactions. Else enter '0' if it is a pre-priced fund
NEXT­PRICE­DECLAREDATE	DATE	DATE	Optional		Specify the next date upon which the fund price is to be declared. This date must be after the Rule Effective Date of the fund, and the current sys­tem date.
PRICE­DECLAREFREQ	Alphanu­meric	1	Optional	Valid values are 'D' for 'Daily; 'W' for 'Weekly'; 'F' or 'B' for 'Bi-weekly'; 'M' for 'Monthly; 'Q' for 'Quarterly' ; 'H' for 'Half-yearly' ; 'Y' for 'Yearly'	This is used to indicate the fre­quency with which the price will be announced. If the fund is Post-priced Fund, you must spec­ify this fre­quency as Daily
NOOF­DECI­MALSFORNAV	Number	1	Optional		Indicate the maximum num­ber of decimals that would be reckoned for rounding preci­sion, for the NAV. You can­not indicate a precision higher than 6 decimal places.
ROUND­OFFTRUNCATE	Alphanu­meric	1	Optional	Valid values are 'R' for Round off; 'T' for Round Down and 'U' for Round up	Indicate the rounding options for the value of the number of allot­ted units, desig­nated for the fund.
MATURI­TYDATE	DATE	DATE	Optional		Indicate the maturity date for the fund. This is applicable only if the fund is closed-ended fund.
RETAIN­IPO­BALANCE	Number	1	Optional	Valid values are '0' and '1'	This is used to indicate if the IPO Balance of unit holders must to be stored for later use. '1' indicate maintenance of IPO balance of Unit holders and '0' indi­cates that it need not be maintained sep­arately
CONFBE­FALCRE­QUIRED	Number	1	Optional	Valid values are '0' and '1'	This is used to indicate that a rejection of a transaction as applicable, for all authorized transactions, prior to alloca­tion. If this is not specified, then all authorized transactions will be taken up for allocation directly.
AUTORE­DEMP­TIONALLOWED	Number	1	Optional	Valid values are '0' and '1'	This is used to indicate if Auto­matic Redemp­tion is to be allowed for the fund. This is applicable only for Open Ended funds. When the balance the unit holder falls below a defined minimum level, then the inves­tor will be inti­mated about it and will be pro­vided with some lead-time to either increase the balance above the mini­mum level or redeem all his units. After the elapsed lead- time, if the unit holder balance still lies below the defined min­imum level, then the auto­matic redemp­tion of those units will be done.
MINI­MUM­BALANCETYPE	Alphanu­meric	1	Optional	Valid values are 'A' and 'U'	Enter the type of Minimum bal­ance (amount / units) to be maintained for Automatic Redemption
MINI­MUM­BALANCE	Number	20	Optional		Enter the mini­mum balance (in amounts / units based on what balance type has been specified above) to be maintained for Automatic Redemption
ELAPSEDDAYSBEFOREAUTORED	Number	3	Optional		Enter the num­ber of days from the date of inti­mation after which Auto­matic Redemp­tion will be initiated. This is the lead-time provided to the investor.
CHQAL­LOTON­CLGDATE	Number	1	Optional	Valid values are '0' and '1'	This is used to indicate whether alloca­tion must be done on the transaction date or on the check clearing date, using the price prevailing on that date, for transactions in which the pay­ment mode is Check
AGEING­BASE­DON	Alphanu­meric	1	Optional	Valid values are 'F' for 'FIFO'; 'T' for 'Transaction Receipts' and 'P' for 'FIFO across products'	This is used to indicate if the unit holder has specified as to how transac­tions are to be ordered - FIFO, Tansaction receipts and FIFO across products
MAIN­TAINTRA­DINGBOX	Number	1	Optional	Valid values are '0' and '1'	This is used to indicate to the system that the trading func­tions must be enabled for the fund. This means that for the fund, all trading transac­tions and the relevant pro­cessing are allowed
NAVLOT	Number	6	Optional		Specify the number of units for which the NAV quote is deemed to be applicable, for the fund.
CDSC­FUND	Varchar2	2	Optional	Valid values : 1. LOCOM 2.Market Price 3.Not Applicable 4. CDSC Class B Default : Not Applicable ‘L’,’M’,’N’,’B’	This is used to indicate that the Contingent Deferred Sales Charge (CDSC) is applicable for the transac­tions in this fund.
CDSCAP­PLICA­BLEFORSWITCHES	Number	1	Optional	Valid values are '0' and '1'	This is used to indicate that the Contingent Deferred Sales Charge (CDSC) is applicable to switch or exchange for the transac­tions in this fund.
REIN­VEST­MENTFIRST	Number	1	Optional	Valid values are '0' and '1'	This is used to indicate that reinvestment transactions must be taken up first for aging during computa­tion of Contin­gent Deferred Sales Charge for redemption transactions in this fund.
VAT­VALUE	Number	5	Optional	Maximum of 2 decimals possi­ble	Value added tax value for the fund
CHECK­FEATU­REEXISTS	Number	1	Optional	Valid values are '0' and '1'	Indicates whether the check writing facility is allowed for the fund or not
MINCHECKA­MOUNT	Number	15	Optional	Maximum of 3 decimals possi­ble	If check writing facility is allowed then the minimum check amount possible is indi­cated here.
MAX­CHECKA­MOUNT	Number	15	Optional	Maximum of 3 decimals possi­ble	If check writing facility is allowed then the maximum check amount possible is indi­cated here.
MINCHECKHOLD­ING­PERIOD	Number	5	Optional		If check writing facility is allowed then the minimum holding period required is indi­cated here.
CHECK­ACCOUNTCLO­SURE	Number	1	Optional
CHECKREDEMP­TION­PENALTY	Number	1	Optional	Valid values are '0' and '1'	If check writing facility is allowed then various penal­ties applicable or not is indi­cated by values '0' and '1'
HOLD­INGPERI­ODPENALTY	Number	1	Optional
BALAN­CEPEN­ALTY	Number	1	Optional
STOP­PAY­MENTPENALTY	Number	1	Optional
AMTLIM­ITPEN­ALTY	Number	1	Optional
INTERE­STRATE	Number	15	Optional	Maximum of 6 decimals possi­ble
PERFOR­MANCE­FEETHRESHOLD	Number	5	Optional	Maximum of 2 decimals possi­ble
LIMI­TORDER­ALLOWED	Number	1	Optional	Valid values are '0' and '1'	This indicates whether limit order is applica­ble for the fund depending upon the price
FUTURE­LIMI­TORDERALLOWED	Number	1	Optional	Valid values are '0' and '1'	Indicates - limit order based on Date
AUTOLIMITOR­DER­PROCESS	Number	1	Optional	Valid values are '0' and '1'	If limit order is based on price, indicates whether auto­matic triggering of processing is required or not.
PRICIN­GRULE	Alphanu­meric	1	Optional	Valid values are 'A' for After and 'P' for Prior	Rule to be applied for pric­ing
MinThreshHold­Limit	Number	5	Optional	Maximum of 2 decimals possi­ble	Used for captur­ing Minimum Threshold Limit.
EUSD­SCOPE	Alphanu­meric	1	Optional	Valid values are ‘R’ for Redemp­tion & Switch Out and ‘D’ for Dividend and ‘B’ for Both. Shown only for EUSD applica­ble segments.	Used to cater EUSD require­ments.
Ageing­Date	Alphanu­meric	1	Optional	Valid values are ‘T’ for Transac­tion Date and ‘C’ for Confirma­tion date and ‘D’ for Dealing date.	Used to store Ageing basis value.
INVEST­MENT­SIMULATIONMETHOD	Alphanu­meric	1	Optional	Valid values are ‘N’ and ‘H’	This indicates whether the Investment Sim­ulation Method should be a Not Allowed or His­toric Based NAV.
MIN­LOCKIN­PERIODFORGAIN	Number	4	Optional	Valid values are Greater than or equal to 0
MAX­LOCKIN­PERIODFORGAIN	Number	4	Optional	Valid values are Greater than or equal to the Min Lock-in Period
MIN­LOCKIN­PERIODFORGAIN	Number	4	Optional	Valid values are Greater than or equal to the Min Lock-in Period and Less than or equal to the Max Lock-in Period.
AMOUNTBLOCK­ALLOWED	NUMBER	1	Optional	Valid values are 0 and 1
CALCU­LATE­FEEINTXNCCY	NUMBER	1	Optional	Valid values are 0 and 1
INCLU­DEHOLD­INGPERIOD	VAR­CHAR2	1	Optional	Valid Values are 0 and 1
BLOCK­PRIORI­TYNO	NUMBER	4	Optional	Block priority should not be a numeric value.	For amount block, the prior­ity will be derived with this number and for amount unblock the priority would be reverse of this order.
DIVI­DENDE­QUALIZATIONAP­PLICA­BLE	NUMBER	1	Optional	Valid Values are ‘0’ (No) and ‘1’ (Yes)	Dividend equali­zation applica­ble” flag should be set to ‘1’ to support divi­dend / income equalization funds.

Serial Number: 5

Segment Identification Number: 04TPR

Description: This segment is used for providing Transaction processing rules information

Segment Mandatory/Optional?: Mandatory

Multiple records allowed for the same Fund and Rule Effective Date: Yes (For each transaction type - there is a separate record)

Field Name	Type	Maximum Length	Mandatory / Optional?	Characteristics / Validations applicable	Description
SEGMEN­TID	Alphanu­meric	20	Mandatory	Default value 04TPR	Standard value of 04TPR to uniquely iden­tify Transac­tion processing information
PROCES­SID	Alphanu­meric	50	Mandatory	Same value as in 00GEN - Pro­cessID	This should identify the upload uniquely. This should also be unique within a file and it allows to iden­tify imported records later
FUNDID	Alphanu­meric	6	Mandatory		The Fund ID is a unique Identi­fication for each Fund and it indicates the fund for which Transaction processing information has to be uploaded
RULEEF­FECTIVE­DATE	Date	8	Mandatory	The Fund ID and Rule effec­tive date combi­nation should be the same as defined in 01FDR	The rule effec­tive date for which transac­tion process­ing information for the fund has to be main­tained.
TRANS­ACTION­TYPE	Alphanu­meric	2	Mandatory	Valid values are '01' for IPO; '02' for Subscrip­tion; '03' for Redemption; '04' for Switch from operation; '05' for trans­fers and so on upto '10'	Indicate the value for which the transaction type for which the rules are being set up
GROS­SORNET	Alphanu­meric	1	Optional	G' for Gross ; 'N' for Net and 'B' for Both	Opting for a gross or net mode in trans­action process­ing is mode is only available for IPO, sub­scription or redemption transactions. For transac­tions with a gross process­ing mode, the value of the transaction, whether as an amount or a number of units, will be processed as a gross value from which any applicable charges will be deducted. For transactions with a net pro­cessing mode, the amount value of the transaction will be processed as a net value apart from the charges.
TRANS­ACTION­STARTDATE	DATE	8	Optional		Enter a date to specify that the above men­tioned transac­tion type will start from this date
TRANS­ACTIONENDDATE	DATE	8	Optional		Enter a date to specify that the above men­tioned transac­tion type will end on this date
TRANS­ACTION­FREQUENCY	Alphanu­meric	1	Optional	Valid values are 'D' for 'Daily; 'W' for 'Weekly'; 'F' or 'B' for 'Bi-weekly'; 'M' for 'Monthly; 'Q' for 'Quarterly' ; 'H' for 'Half-yearly' ; 'Y' for 'Yearly'	Enter a value to specify the frequency with which the transaction type will oper­ate
TRANS­ACTION­STARTPERIOD	NUMBER	1	Optional		Enter a value to specify the Start Period within the fre­quency men­tioned above. Within a par­ticular fre­quency, you have an option to restrict it to a particular period. For example if the transaction Frequency is WEEKLY, Start Period is 2 and End Period is 5. This means that the Fund is open for this transaction from second day till the fifth day of the week.
TRANS­ACTIONENDPERIOD	NUMBER	1	Optional		The End period has to be within the Transac­tion Frequency i.e., it can take values up to 7 (weekly) and not greater than that.
DATE	DATE		Optional		Enter a time to specify the start time for a given working date. On a given day when the fund is open for this transaction, you can start entering trans­actions from this time.
MIN­TRANS­ACTIONAMOUNT	NUMBER	15	Optional	Maximum of 3 decimals allowed	The minimum transaction amount allowed for this transaction type in this fund
STEPAMOUNT	NUMBER	15	Optional	Maximum of 3 decimals allowed	Enter a value to specify the steps of amount in which a unit holder can invest or redeem. This will operate above the Mini­mum Transac­tion Amount.
MAX­TRANS­ACTIONAMOUNT	NUMBER	15	Optional	Maximum of 3 decimals allowed	The maximum transaction amount allowed for this transaction type in this fund
MIN­TRANS­ACTIONUNITS	NUMBER	15	Optional	Maximum of 6 decimals allowed	The minimum transaction units allowed for this transac­tion type in this fund
STEPU­NITS	NUMBER	15	Optional	Maximum of 6 decimals allowed	The unit steps applicable for a unit holder to invest do any operation
MAX­TRANS­ACTIONUNITS	NUMBER	15	Optional	Maximum of 6 decimals allowed	The maximum transaction units allowed for this transac­tion type in this fund
ONLINE­ALLOCA­TION	NUMBER	1	Optional	Valid values '0' and '1'	This is to indi­cate if Online Allocation is to be allowed for the given trans­action type. This can be applicable only if the fund is pre-priced. For Post Priced Fund with Allo­cation as Online, the Transaction Frequency is Allocation
ALLOCA­TION­PERVSREGCAPI­TAL	NUMBER	1	Optional	Should be below 100.	Specify the per­centage up to which alloca­tion can be allowed for a given regis­tered amount on the day
ALLOCA­TION­POLICY	Alphanu­meric	1	Optional		Enter F for First In First Out or P Proportion­ate to specify the policy for allocation in case the maxi­mum limit is reached for a given day. This policy is with respect to the allocation per­centage that is allowed against the fund cor­pus.
NOOFTX­NAL­LOWEDFORFREQ	NUMBER	1	Optional		This is to spec­ify the number of transactions allowed restric­tion within this frequency
NOOFTX­NAL­LOWEDPERUH	NUMBER	1	Optional		Enter a value to specify the number of transactions that are allowed for a unit holder. You can restrict the unit holder from operating more than the speci­fied limit for transactions.
NOOF­FREETX­NALLOWEDPE­RUH	NUMBER	1	Optional		Enter a value to specify the number of free transactions within the per­mitted transac­tions. This definition will override all loads that will be set for this transaction
ALLOW­BACK­DATING	NUMBER	1	Optional		This is used to indicate whether back­dating should be allowed for this fund. This means that on any given date, for this transac­tion type, the system will allow the user to enter trans­actions dated earlier to the current date
BACK­DATIN­GLIMIT	NUMBER	1	Optional	Valid values are '0' and '1'	This is applica­ble only if Allow Back Dating is True. This has to be later than the transaction start date. Fund Price as effective on that date will be taken into account during allocation.
FUNDTRANSAC­TION­COUNTER	NUMBER	1	Optional		Enter a value to specify the total number of transactions to be allowed in this transac­tion type.
ACKNOWLEDGE­MENTRE­QUIRED	NUMBER	1	Optional		This is to indi­cate if the Acknowledg­ment Slip is to be printed after every transac­tion. Otherwise this can be printed on receiving spe­cific request from the User.
CONFIR­MATION­REQUIRED	NUMBER	1	Optional	Valid values '0' and '1'	This is to indi­cate whether confirmation Slip is to be printed after every transac­tion entry. Oth­erwise this can be user initi­ated after allo­cation of the transaction.
NOTI­CEPERI­ODDATEBASIS	VAR­CHAR2	1	Optional
NOTI­CEPER­IOD	NUMBER	3	Optional
BASE­PRICE­DEFINITION	Alphanu­meric	1	Optional	Valid values are 'P' for Par Value and 'N' for declared NAV	This indicates the Base Price definition for the transac­tion. The Unit Price will be calculated based on this price and loads defined for this transaction.
BASE­PRICE­FACTOR	NUMBER	1	Optional		This percent­age will be applied to the price arrived from the above calculations to arrive at the Base Price for this transac­tion type for the fund.
NOOF­DECI­MALSFORBASE­PRICE	NUMBER	1	Optional		Indicate the maximum num­ber of deci­mals that would be reckoned for rounding preci­sion, for the base price. You cannot indi­cate a preci­sion higher than 6 decimal places.
ROUND­OFFTRUNCATE­BASE­PRICE	Alphanu­meric	1	Optional	Valid values are 'R' for Round off; 'T' for Round Down and 'U' for Round up	Indicate the rounding options for the value of the number of allot­ted units, des­ignated for the fund.
TRANS­ACTIONENABLED	NUMBER	1	Optional		This is used to indicate whether the transaction is enabled for the fund. It is pos­sible to set up a temporary sus­pension of transactions, even if the transactions are open for the fund.
CROSS­BRANCHALLOWED	NUMBER	1	Optional	Valid values are 0 and 1
PRICE­LAG	NUMBER	1	Optional		This cannot have negative value. This indicates the price date to be used for the transaction during alloca­tion process
ALLOCA­TIONLAG	NUMBER	1	Optional		Enter a value to specify when the transaction should be allo­cated if the transaction is ‘T’. T + X , where ‘X’ will be days of Lag. Lag can only be positive.
CONFIR­MATION­LAG	NUMBER	1	Optional		Enter a value to specify when the redemption transaction should be picked for con­firmation after allocation. T + X , where ‘X’ will be days of Lag. Lag can only be posi­tive.
CHQAL­LOCON­PARWITHCASH	NUMBER	1	Optional	Valid values are '0' and '1'	This is used to specify that all check / Demand Draft transactions are to be treated on par with cash transactions. If this is true, then during allocation, the check / demand draft transactions will be taken for allocation for the same day. The units allo­cated will be provisional, and will be con­firmed only after the check is cleared.
HOLD­INGPERI­ODAPPLICABLE	NUMBER	1	Optional	Valid values are '0' and '1'	This is used to indicate whether a lock in period is applicable for the investors investing in the fund for the transaction type
RETAIN­AGEING­TOSUBSCRIP­TION	NUMBER	1	Optional	Valid values are '0' and '1'	This is used to indicate that the aging prin­ciple must be applied to sub­scription trans­actions in the fund. Aging is the process of keeping track of a transac­tion from the transaction date right up to when it is cleared in full from the account of the unit holder. Depending upon the pol­icy specified to be followed for aging, (i.e., either FIFO or proportionate), aging is applied.
CREDIT­CARDAL­LOCONPARWITH­CASH	NUMBER	1	Optional	Valid values are '0' and '1'	This is used to indicate if all credit card transactions to be treated on par with cash transactions. If this is true then during alloca­tion the credit card transac­tions will be taken for allo­cation for the same day. The units allocated will be provi­sional, and will be confirmed only after the credit card transaction is cleared.
LIMITRE­DEMP­TIONMODE	Alphanu­meric	1	Optional	Valid values are 'P' for Percent; 'U' for Units and 'A' for Amount	The mode based on which redemption will be limited
NATURE­OFLIMIT	Alphanu­meric	1	Optional		Indicates whether it is 'A' or 'U' or 'B'
TRANS­FERAL­LOCONPARWITH­CASH	NUMBER	1	Optional		Mark this check box if you want all transfer transactions to be treated on par with cash transactions. If this is true then during alloca­tion the transfer transactions will be taken for allocation for the same day. The units allo­cated will be provisional, and will be con­firmed only after the bank transfers are cleared
MININI­TIALTX­NAMOUNT	NUMBER	15	Optional	Maximum of 3 decimals allowed	Minimum amount appli­cable for initial transaction
MININI­TIALTXN­UNITS	NUMBER	15	Optional	Maximum of 3 decimals allowed	Minimum units applicable for initial transac­tion
MINSITX­NAMOUNT	NUMBER	15	Optional	Maximum of 3 decimals allowed	Minimum amount appli­cable for Standing instructions
MAX­SITX­NAMOUNT	NUMBER	15	Optional	Maximum of 3 decimals allowed	Maximum amount appli­cable for Standing instructions
MINSITX­NUNITS	NUMBER	15	Optional	Maximum of 3 decimals allowed	Minimum units applicable for Standing instructions
MAX­SITXN­UNITS	NUMBER	15	Optional	Maximum of 3 decimals allowed	Maximum units applicable for Standing instructions
EXISTIN­GUH	Alphanu­meric	2	Optional	Valid values are '0' and '1'	This is to indi­cate that the subscription transactions for the fund must only be availa­ble to existing customers, and not to new cus­tomers.
NOOF­DECI­MALSFORUNIT­PRICE	NUMBER	1	Optional		Indicate the maximum num­ber of deci­mals that would be reckoned for rounding preci­sion, for the unit price. You cannot indi­cate a preci­sion higher than 6 decimal places.
ROUND­OFFTRUNCATEU­NITPRICE	Alphanu­meric	1	Optional	Valid values are 'R' for Round off; 'T' for Round Down and 'U' for Round up	Indicate the rounding options for the value of the number of allot­ted units, des­ignated for the fund.
ROUND­OFFTRUNCATEU­NITS	Alphanu­meric	1	Optional	Valid values are 'R' for Round off; 'T' for Round Down and 'U' for Round up	Indicate the rounding options for the value of the number of allot­ted units, des­ignated for the fund.
PAY­MENT­LAG	NUMBER	1	Optional		In the case of redemption transactions, specify a value to indicate the number of days by which the resulted redemption payouts would be lagged or deferred, after the redemption transaction has been allotted and confirmed. To arrive at the actual date of redemption payment, both the confirma­tion lag (if specified) and the payment lag (if specified here) are taken into considera­tion. For instance, if the redemption transaction was allocated on 15th Janu­ary and both the confirma­tion lag and payment lag were specified as 2, then the actual redemp­tion payout to the unit holder would be effected on 19th January (15 + 2+ 2), provided it is not a holiday in the system, and provided there are no intervening hol­idays.
TRANS­ACTION­CUTOFFTIME	DATE	DATE	Optional		Specify the time, on a given working day before which a trans­action of the selected type will be accepted with the transaction date being the current date. Beyond this time on a work­ing day, the transaction date will be set by default to be the next work­ing date.
ENFORCEHOLD­ING­PERIOD	NUMBER	1	Optional		You can indi­cate that the minimum hold­ing period specified for the fund in the Fund Demo­graphics pro­file must be enforced as mandatory for the transaction type, by select­ing this option.
APPLY­ENTRY­TIMELOAD	NUMBER	1	Optional		Applicable for Exit transac­tions
Pseu­doswitch­lag	Number		Optional		Used for cap­turing Pseudo Switch lag
AllowSys­temat­icPlans	Number	1	Optional
MaxIni­tialTx­nAmount	Number	15	Optional	Maximum of 3 decimals allowed	Used for cap­turing the maxi­mum initial transaction amount.
MaxIni­tialTxn­Units	Number	15	Optional	Maximum of 6 decimals allowed	Used for cap­turing maxi­mum initial transaction units.
Pseu­doswitch­lagcalendarbasis	Alphanu­meric Code	1	Optional		Specify whether the ps lag days should be considered based on the holiday calen­dar for the fund, the actual calendar or the System calen­dar.
FULL­OUT­FLOW	NUMBER	1	Optional	Valid values are 0 and 1
MAX­NOOFSI­TRANSACTIONS	NUMBER	4	Optional	MaxNoofSI­Transactions value should be Greater than 0
MAXVA­LIDITY	NUMBER	4	Optional	Maxvalidy value should be Greater than 0
SILEAD­TIME	NUMBER	4	Optional
APPLICA­BLEAC­COUNTTYPES	Alphanu­meric	255	Optional
INFLOW­OVER­RIDABLEMSG	NUMBER	1	Optional	Valid values are 0 and 1
MINMA­TURI­TYPERIOD	NNUM­BER	4	Optional	Min.Maturity Period value sholud be greater than 0
MAXMA­TURI­TYPERIOD	NNUM­BER	4	Optional	Max.Maturity Period value sholud be greater than 0 and greater than or equal to Min.Maturity Period
FUTURE­DATELIMIT	NUMBER	1	Optional	Valid values are positive integer	To facilitate users to input future dated transactions
UHCAL­ENDAR­BASIS	VAR­CHAR2(1)	1	Optional	Valid values are ‘T’ and ‘C’
NOOF­DECI­MALSFORUNITS	NUMBER	1	Optional	Valid values are -1 to 9
CONS­SIAUTO­COUNTER	NUMBER	3	Optional		Used to cap­ture consecu­tive payment rejections allowed for the SI
THRESH­OLDA­MOUNT	NUMBER	(30, 12)	Optional		Threshold Amount

Serial Number: 6

Segment Identification Number: 05TCM

Description: This segment is used for providing Transaction processing communication mode information

Segment Mandatory/Optional? : Mandatory

Multiple records allowed for the same Fund and Rule Effective Date: Yes (For each transaction type - there is a separate record)

Field Name	Type	Maximum Length	Mandatory / Optional?	Characteristics / Validations applicable	Description
SEG­MENTID	Alpha­numeric	20	Mandatory	Default value 05TCM	Standard value of 05TCM to uniquely identify Transaction pro­cessing commu­nication mode information
PRO­CESSID	Alpha­numeric	50	Mandatory	Same value as in 00GEN - Pro­cessID	This should identify the upload uniquely. This should also be unique within a file and it allows to iden­tify imported records later
FUNDID	Alpha­numeric	6	Mandatory		The Fund ID is a unique Identifi­cation for each Fund and it indi­cates the fund for which Trans­action process­ing communication mode informa­tion has to be uploaded
RULEEFFEC­TIVE­DATE	Date	8	Mandatory	The Fund ID and Rule effec­tive date combi­nation should be the same as defined in 01FDR	The rule effec­tive date for which transac­tion processing communication mode informa­tion for the fund has to be main­tained.
TRANS­ACTION­TYPE	Alpha­numeric	2	Mandatory	Valid values are '01' for IPO; '02' for Subscrip­tion; '03' for Redemption; '04' for Switch from operation; '05' for transfers and so on up to '10'	Indicate the value for which the transaction type for which the rules are being set up
COM­MUNI­CATIONMODE	Alpha­numeric	2	Mandatory		Valid Communi­cation mode code indicated as a part of Par­ams Mainte­nance.
MIN­TRANS­ACTIONAMOUNT	Number	15	Optional	Decimal values up to maximum of 3 digits are allowed	Minimum trans­action amount allowed for the transaction type and communica­tion mode.
MAX­TRANS­ACTIONAMOUNT	Number	15	Optional	Decimal values up to maximum of 3 digits are allowed	Maximum trans­action amount allowed for the transaction type and communica­tion mode.
MIN­TRANS­ACTIONUNITS	Number	15	Optional	Decimal values up to maximum of 6 digits are allowed	Minimum trans­action units allowed for the transaction type and communica­tion mode.
MAX­TRANS­ACTIONUNITS	Number	15	Optional	Decimal values up to maximum of 6 digits are allowed	Maximum trans­action units allowed for the transaction type and communica­tion mode.
DISAL­LOW­FIRSTTRANS­ACTION	Number	1	Optional	Valid values are 0 and 1

Serial Number: 7

Segment Identification Number: 06INV

Description: This segment is used for providing Transaction processing investor category related information

Segment Mandatory/Optional? : Mandatory

Multiple records allowed for the same Fund and Rule Effective Date: Yes (For each transaction type - there is a separate record)

Field Name	Type	Maximum Length	Mandatory / Optional?	Characteristics / Validations applicable	Description
SEG­MENTID	Alphanu­meric	20	Mandatory	Default value 06INV	Standard value of 06INV to uniquely iden­tify Transaction processing communication mode informa­tion
PRO­CESSID	Alphanu­meric	50	Mandatory	Same value as in 00GEN - Pro­cessID	This should identify the upload uniquely. This should also be unique within a file and it allows to iden­tify imported records later
FUNDID	Alphanu­meric	6	Mandatory		The Fund ID is a unique Identi­fication for each Fund and it indi­cates the fund for which Trans­action process­ing investor category infor­mation has to be uploaded
RULEEF­FEC­TIVEDATE	Date	8	Mandatory	The Fund ID and Rule effec­tive date combi­nation should be the same as defined in 01FDR	The rule effec­tive date for which transac­tion processing investor cate­gory informa­tion for the fund has to be main­tained.
TRANS­ACTION­TYPE	Alphanu­meric	2	Mandatory	Valid values are '01' for IPO; '02' for Subscrip­tion; '03' for Redemption; '04' for Switch from operation; '05' for transfers and so on up to '10'	Indicate the value for which the transaction type for which the rules are being set up
INVES­TORCAT­EGORY	Alphanu­meric	2	Mandatory		Valid Corporate and Individual categories defined as a part of Params Maintenance.
MIN­TRANS­ACTIONAMOUNT	Number	15	Optional	Decimal values up to maximum of 3 digits are allowed	Minimum trans­action amount allowed for the transaction type and investor category.
STEPAMOUNT	Number	15	Optional	Decimal values up to maximum of 3 digits are allowed
MAX­TRANS­ACTIONAMOUNT	Number	15	Optional	Decimal values up to maximum of 3 digits are allowed	Maximum trans­action amount allowed for the transaction type and investor category.
MIN­TRANS­ACTIONUNITS	Number	15	Optional	Decimal values up to maximum of 6 digits are allowed	Minimum trans­action unit allowed for the transaction type and investor category.
STEPU­NITS	Number	15	Optional	Decimal values up to maximum of 6 digits are allowed
MAX­TRANS­ACTIONUNITS	Number	15	Optional	Decimal values up to maximum of 6 digits are allowed	Maximum trans­action unit allowed for the transaction type and investor category.

Serial Number: 8

Segment Identification Number: 07IDR

Description: This segment is used for providing Corporate Action related information

Segment Mandatory/Optional?: Optional

Multiple records allowed for the same Fund and Rule Effective Date: Yes (For cash and Stock dividend information)

Field Name	Type	Maximum Length	Mandatory / Optional?	Characteristics / Validations applicable	Description
SEGMEN­TID	Alpha­numeric	20	Mandatory	Default value 07IDR	Standard value of 07IDR to uniquely identify Transaction pro­cessing commu­nication mode information
PROCES­SID	Alpha­numeric	50	Mandatory	Same value as in 00GEN - Pro­cessID	This should identify the upload uniquely. This should also be unique within a file and it allows to iden­tify imported records later
FUNDID	Alpha­numeric	6	Mandatory		The Fund ID is a unique Identifi­cation for each Fund and it indi­cates the fund for which Corpo­rate action has to be uploaded
RULEEF­FECTIVE­DATE	Date	8	Mandatory	The Fund ID and Rule effec­tive date combi­nation should be the same as defined in 01FDR	The rule effec­tive date for which corporate action for the fund has to be maintained.
DIVI­DENDDE­CLAREFREQ	Alpha­numeric	1	Optional	Valid values are 'D' for 'Daily; 'W' for 'Weekly'; 'F' or 'B' for 'Bi-weekly'; 'M' for 'Monthly; 'Q' for 'Quarterly' ; 'H' for 'Half-yearly' ; 'Y' for 'Yearly'	Enter the fre­quency with which the divi­dend is to be declared
DIVI­DEND­PAYMENTFREQ	Alpha­numeric	1	Optional	Valid values are 'D' for 'Daily; 'W' for 'Weekly'; 'F' or 'B' for 'Bi-weekly'; 'M' for 'Monthly; 'Q' for 'Quarterly' ; 'H' for 'Half-yearly' ; 'Y' for 'Yearly'	Enter the fre­quency with which the declared divi­dends are to be paid. As the sys­tem supports accumulation of dividends, the payment could be for any divi­dend that has been declared earlier. The Divi­dend Payment Frequency must not be less than Dividend Decla­ration Fre­quency.
REIN­VEST­MENTALLOWED	Number	1	Optional	Valid values are '0' and '1'	This is used to indicate if rein­vestment is allowed for the fund.
TAXID	Alpha­numeric	50	Optional		Enter the tax ID for the fund that is being set up.
BOOK­CLOSIN­GLEADTIME	Number	5	Optional		Enter a lead-time in days
FREEZE­HOLD­INGLEADTIME	Number	5	Optional		This data is also in days and the Freeze Holding Date is the date on which the balances held by all unit hold­ers in the fund will be consoli­dated
BOARD­MEET­INGLEADTIME	Number	5	Optional		Enter a lead-time in days. This is captured for information purposes only.
DIVI­DEND­PAYMENTLEAD­TIME	Number	5	Optional		The lead time entered is in days. Each of the lead times must be less than the Divi­dend Declara­tion Frequency. For example, if the Dividend Declaration Fre­quency is WEEKLY, the Board Meeting Lead Time can­not be 8 days.
NOOF­DECI­MALSFORDIVI­DEND	Number	5	Optional		Indicate the maximum num­ber of decimals that would be reckoned for rounding preci­sion, for the divi­dend. You cannot indicate a precision higher than 6 decimal places.
ROUND­OFFTRUNCATE­DIVI­DEND	Alpha­numeric	1	Optional	Valid values are 'R' for Round off; 'T' for Round Down and 'U' for Round up	Indicate the rounding options for the value of the dividend, designated for the fund.
TDSBA­SIS	Alpha­numeric	1	Optional	D - Each Divi­dend ; U - Fiscal year	This is to indi­cate whether slab should be looked for every dividend pay­ment separately or whether con­solidated on a fiscal year basis.
EPUCOM­PONENTS	Number	1	Optional	Valid values are '0' and '1'	This indicates the applicability of Earnings Per Unit and that the earnings per unit must be defined in terms of com­ponents, or as a single value. Setting up EPU components is not applicable for stock divi­dends.
DEFAULTDISTRI­BUTION­MODE	Alpha­numeric	1	Optional	Valid values are 'T' - Payout-A/C Transfer; 'Q' - Payout-Cheque and 'R' - Full Reinvestment	If the Income Distribution Setup for the unit holder has not yet been specified, the fund level default Unit Holder Distribu­tion Mode to be considered for the unit holder can be specified here. For stock dividends, the only possible option is ’Rein­vestment' as others would not be applicable
EXCHANGERATE­DATEBA­SIS	Alpha­numeric	1	Optional	Valid values are 'P' - Payment Date; 'R' - Ref­erence Date	Specify the basis upon which the exchange rate will be applied for dividend pro­cessing. The system pro­vides two options: Refer­ence Date and Payment Date.
RESTRIC­TIDS	Number	1	Optional	Valid values are '0' and '1'	This is used to indicate that specific income distribution set­ups for unit hold­ers may be overridden. For stock dividends this value should always be set.
EPULOT	Number	6	Optional		Specify the num­ber of units for which the EPU quote is deemed to be applica­ble, for the fund. Setting up EPU components is not applicable for stock divi­dends.
DIV­LOOKA­HEAD	Number	1	Optional		This is to indi­cate that in the event of inter­vening holidays, the system would obtain the EPU informa­tion and pro­cess dividends for the holiday period, ahead of the prior busi­ness day, for the fund.
CORPO­RATEAC­TIONTYPE	Alpha­numeric	1	Mandatory	Valid values are 'C' for Cash and 'S' for Stock divi­dends	For cash divi­dend EPU should be men­tioned whereas for Stock divi­dend, Par­ent:Resultant ratio should be mentioned
UNITS­FOR­FREEZEHOLDINGS	Alpha­numeric	1	Optional	Valid values 'A' for all units and 'C' for Con­firmed units	Specify the units to be considered for dividend eli­gibility as on the freeze holdings date. You can specify that all units (including unconfirmed units) must be considered, or that only con­firmed units are to be considered as on the freeze holdings date.
FIRST­DIVI­DENDDECLARE­DATE	Date	8	Optional		Specify the first date for dividend declaration, for the fund
SPECIAL­DIVI­DEND	Number	1	Optional		This is to indi­cate that special dividends are applicable for the fund. This feature is only available if your installation has requested for it.
MOCK­DIVI­DEND	Number	1	Optional		Not applicable now
HOLIDAY­RULE	Alpha­numeric	1	Optional	A' for After and 'P' for prior	Select the rule to be applied if the dividend pro­cessing date falls on a holi­day. You can select either the PRIOR rule (the previous work­ing day is con­sidered) or the AFTER rule (the next working day is consid­ered), for the dividend type. The holiday rule you select here will be applica­ble to all divi­dend-processing dates that have been arrived at using a fre­quency. They are not applica­ble to dates arrived at using lead times or lag periods.
PAY­MENT­LAG	Number	3	Optional		Specify a lag period (in days) for the payment of dividend. The lag value is interpreted in calendar days, and is used to arrive at the pay­ment date for the dividend. The payment date is arrived at as follows: Divi­dend Payment Date = Dividend Declaration Date + Payment Lag
PAYDIVI­DEND­DURINGRED	Number	1	Optional		This is used to indicate that div­idends may be paid during redemption.
REIN­VEST­MENTPRICEBASIS	Alpha­numeric	1	Optional
IRACOM­PULSO­RYREINVEST	Number	1	Optional		Applicable only if IRA is applica­ble for the fund.
NPISUP­PORT	Alpha­numeric	1	Optional
NPIPAY­MENT	Alpha­numeric	3	Optional
NPIU­HOverride	Alpha­numeric	1	Optional
FlgUnset­tleUnits	Alpha­numeric	1	Optional
MIMAMT­TOBEP­AIDOUT	NUM­BER	1	Optional
ACTION	VAR­CHAR2	1	Optional	Valid values are ‘L’ and ‘R’
OVER­RATPAY­TIME	NUM­BER	1	Optional	Valid values are 0 and 1
AUTORE­INVFO­RUNCLCHQ	NUM­BER	1	Optional	Valid values are 0 and 1
AUTORE­INVFO­RUNCLCHQFZB	NUM­BER	1	Optional	Valid values are 0 and 1
TRACK­UNCLEAREDTXNS	VAR­CHAR2	1	Optional	Valid values are 0 and 1
TRACK­BLOCKEDTXNS	VAR­CHAR2	1	Optional	Valid values are 0 and 1
PAYUN­GENRE­INVESTMENT	VAR­CHAR2	1	Optional	Valid values are 0 and 1
TDS APPLICA­BLE FOR ALL UH	Number	1	Optional	Valid values are 0 (No) and 1(Yes)	TDS Applicable for all UH” flag could be set to ‘1’ only if divi­dend equaliza­tion is applicable for the fund.

Serial Number: 9

Segment Identification Number: 08FSC

Description: This segment is used for providing Fund Sale Country information

Segment Mandatory / Optional?: Mandatory

Multiple records allowed for the same Fund and Rule Effective Date: Yes

Field Name	Type	Maximum Length	Mandatory / Optional?	Characteristics / Validations applicable	Description
SEG­MENTID	Alphanu­meric	20	Mandatory	Default value 08FSC	Standard value of 08FSC to uniquely identify Fund sale coun­try information
PRO­CESSID	Alphanu­meric	50	Mandatory	Same value as in 00GEN - Pro­cessID	This should iden­tify the upload uniquely. This should also be unique within a file and it allows to identify imported records later
FUNDID	Alphanu­meric	6	Mandatory		The Fund ID is a unique Identifica­tion for each Fund and it indi­cates the fund for which Fund sale country informa­tion has to be uploaded
RULEEFFEC­TIVE­DATE	Date	8	Mandatory	The Fund ID and Rule effec­tive date combi­nation should be the same as defined in 01FDR	The rule effec­tive date for which fund sale country informa­tion for the fund has to be main­tained.
COUN­TRY­CODE	Alphanu­meric	3		Valid country code present in the system as a part of Domicile in Params main­tenance	If no country code is men­tioned and this field is left blank then it means that there is no restriction on the sale of the fund. However, if valid value is entered then the fund would be restricted for sale in those coun­tries

Serial Number: 10

Segment Identification Number: 09FRL

Description: This segment is used for providing Fund residency list information

Segment Mandatory/Optional?: Mandatory

Multiple records allowed for the same Fund and Rule Effective Date: Yes

Field Name	Type	Maximum Length	Mandatory / Optional?	Characteristics / Validations applicable	Description
SEG­MENTID	Alphanu­meric	20	Mandatory	Default value 09FRL	Standard value of 09FRL to uniquely identify Fund resi­dency list informa­tion
PRO­CESSID	Alphanu­meric	50	Mandatory	Same value as in 00GEN - Pro­cessID	This should iden­tify the upload uniquely. This should also be unique within a file and it allows to identify imported records later
FUNDID	Alphanu­meric	6	Mandatory		The Fund ID is a unique Identifica­tion for each Fund and it indicates the fund for which Fund residency list information has to be uploaded
RULEEFFEC­TIVE­DATE	Date	8	Mandatory	The Fund ID and Rule effec­tive date combi­nation should be the same as defined in 01FDR	The rule effective date for which fund residency list infor­mation for the fund has to be main­tained.
COUN­TRY­CODE	Alphanu­meric	3		Valid country code present in the system as a part of Domicile in Params main­tenance	If no country code is mentioned and this field is left blank then it means that there is no restriction on the investor resid­ing in any domi­cile. However, if valid value is entered then the fund would be restricted for investors residing in that domicile.

Serial Number: 11

Segment Identification Number: 10FFM

Description: This segment is used for providing Fund formula information

Segment Mandatory/Optional?: Optional

Multiple records allowed for the same Fund and Rule Effective Date: Yes

Field Name	Type	Maximum Length	Mandatory / Optional?	Characteristics / Validations applicable	Description
SEG­MENTID	Alphanu­meric	20	Mandatory	Default value 10FFM	Standard value of 10FFM to uniquely identify Fund formula related informa­tion
PRO­CESSID	Alphanu­meric	50	Mandatory	Same value as in 00GEN - Pro­cessID	This should iden­tify the upload uniquely. This should also be unique within a file and it allows to identify imported records later
FUNDID	Alphanu­meric	6	Mandatory		The Fund ID is a unique Identifica­tion for each Fund and it indi­cates the fund for which Fund for­mula information has to be uploaded
RULEEFFEC­TIVE­DATE	Date	8	Mandatory	The Fund ID and Rule effec­tive date combi­nation should be the same as defined in 01FDR	The rule effective date for which fund formula information for the fund has to be maintained.
COM­PONEN­TID	Alphanu­meric	10	Mandatory		Valid compo­nents maintained in the system as a part of Params maintenance. This also depends on whether this is used for Fund price computa­tion or not.
FUND­PRICE­COMPUTATION	Alphanu­meric	1	Optional		Indicates whether the data has to be used for Fund price computa­tion or not. This value should remain the same for the fund and Rule effective date combina­tion. In other words, for a fund and Rule effec­tive date - we cannot have one component used for fund price computation and the other compo­nent not used for fund price com­putation.
FOR­MULA	Alphanu­meric	255	Optional
DEFAULTVALUE	Number	15	Optional	Maximum of 6 decimals allowed
EXCLU­DEFROMCAPI­TAL­GAINS	Number	1	Optional

Serial Number: 12

Segment Identification Number: 11FLM

Description: This segment is used for providing Fund load information

Segment Mandatory/Optional?: Optional

Multiple records allowed for the same Fund and Rule Effective Date: Yes

Field Name	Type	Maximum Length	Mandatory / Optional?	Characteristics / Validations applicable	Description
SEG­MENTID	Alphanu­meric	20	Mandatory	Default value 11FLM	Standard value of 11FLM to uniquely iden­tify Fund load related informa­tion
PROCES­SID	Alphanu­meric	50	Mandatory	Same value as in 00GEN - Pro­cessID	This should identify the upload uniquely. This should also be unique within a file and it allows to identify imported records later
FUNDID	Alphanu­meric	6	Mandatory		The Fund ID is a unique Identifi­cation for each Fund and it indi­cates the fund for which Fund load informa­tion has to be uploaded
RULEEF­FECTIVE­DATE	Date	8	Mandatory	The Fund ID and Rule effec­tive date combi­nation should be the same as defined in 01FDR	The rule effec­tive date for which fund load information for the fund has to be maintained.
TRANS­ACTION­TYPE	Alphanu­meric	2	Mandatory	Valid values are from '01' to '10' ranging from IPO to Re-issue	This is to indi­cate the trans­action type for which the loads are being defined
LOADID	Number	5	Mandatory	Valid load ID defined in the system	Specify the name of the Load (fee/incen­tive) that must be applied for the selected Fund.
LOADTO­PRICE	Number		Optional	Valid values are '0' and '1'	This is to indi­cate that this load is to be loaded to the base price
FRO­MENTI­TYTYPE	Alphanu­meric	1	Mandatory	Valid values are· 'M' for AMC, 'A' for Agent, 'B' for Broker, 'D' for Distributor, 'F' for Fund, 'R' for Registrar, 'T' for Trustee, 'U' for Unit Holder, 'S' for Custodian	This is to indi­cate the entity type from which the load is applied
TOENTI­TYTYPE	Alphanu­meric	1	Mandatory	Valid values are· 'M' for AMC, 'A' for Agent, 'B' for Broker, 'D' for Distributor, 'F' for Fund, 'R' for Registrar, 'T' for Trustee, 'U' for Unit Holder, 'S' for Custodian	This is to indi­cate the entity type to which the load is applied
PRO­CESS­INGFREQ	Alphanu­meric	1	Optional	Valid values are 'A', 'T' and 'P'	Specify the fre­quency at which this load is to be applied. Loads can be applied at any of three possible fre­quencies - Allo­cation time, Transaction time and Post allocation. (Refer the table marked ‘PRO­CESSING­FREQ’ at the end of this doc­ument)
GLAC­COUNT­CODE	Alphanu­meric	10	Optional		When transac­tion information is exported to an external sys­tem, if separate books of accounts are to be posted for different loads, this code will be used to identify this load infor­mation in the export data.
DEBI­TOR­CREDIT	Alphanu­meric	1	Optional	Valid values are 'D' and 'C'	This is used to indicate that the applied load would result in a debit or credit for the fund. This data is cap­tured for infor­mation purposes only and has no pro­cessing implica­tions in the system data­base.
CON­TRAAC­COUNTCODE	Alphanu­meric	10	Optional		Specify the code that will be used to identify the second leg of accounting entries for any transaction, in the event of exporting of transaction information to an external sys­tem.
NOOF­DECI­MALSFORLOAD	Number	1	Optional	Valid values are 'R' for Round off; 'T' for Round Down and 'U' for Round up	Indicate the rounding options for the value of the load, desig­nated for the fund.
ROUND­OFFTRUNCATE­FOR­LOAD	Alphanu­meric	1	Optional		Indicate the maximum num­ber of decimals that would be reckoned for rounding preci­sion, for the load. You can­not indicate a precision higher than 6 decimal places.
MANDA­TORY	Alphanu­meric	1	Optional	Valid values are 'M' and 'O'	Select Manda­tory or Optional to specify whether the load is manda­tory or optional
PRIORI­TYNO	Number		Optional	For a manda­tory load, the priority number is set to 0 and for an optional load the priority number should be unique i.e.. for a given Fund, no more than one load can have the same priority number.	Enter a value to specify the pri­ority number in case of optional loads.
LOAD­VATTO­PRICE	Number		Optional	Valid values are 1 and 0
APPLY­RETVA­LON	Alphanu­meric	1	Optional	Valid vales are 'G' - Capital Gains Gross; 'N' - Non-capital gains Net and 'C' - Capital gains and ‘P’ - Perfor­mance Based and ‘I’ – IOF and ‘D’ - Default IRRF and ‘O’ - Optional IRRF and ‘S’- CDSC	If the load is a Capital Gains Tax, and it is to be applied based on the gross amount after allocation, choose the Cap­ital Gains – Gross option in this field, for such a load.
SEND­FOR­GLINTERFACE	Number	1	Optional	Valid values are '0' and '1'	This is used to indicate that accounting entries due only to the selected load must be posted to the external asset management system, for the fund.
REFTYPE	Alphanu­meric	2	Mandatory	Valid reference type as per the pre-shipped data in RefTy­peTbl	When load needs to be mapped to a ref­erence transac­tion type like Reinvestment and if the sys­tem supports the mapping of the Ref Type to any load, then such RefTypes can be indicated here.
DIFFER­ENTIAL­FEE	Number	1	Optional	Valid values are '0' and '1'	This is to indi­cate whether differential fee in the case of switch transac­tions for any fund is to be applicable
SLABBA­SIS	Alphanu­meric	1	Optional	Valid values are 'G' for Gross and 'N' for Net ‘W’ – Weighted Average	This is to Indi­cate the basis on which the slabs will be reckoned for an amount-based load that you are designating as applicable for the fund
PRICEADDIN	Number	1	Optional		This is used to indicate the add-in factor that is to be applicable for computing the return value for the load, for the selected trans­action type. The add-in factor is used to arrive at the return value for a load, at the time of alloca­tion.
GROUPID	Alphanu­meric	6	Optional	Valid Group Id present in the system
INDEXA­TIONON­CGT	Alphanu­meric	1	Optional	Valid values are 'Y' for Yes and 'N' for 'No'
LevelID	Number		Optional		Used for captur­ing the LevelID
DependentLevel	Number		Optional		Used for captur­ing Dependent level.

Serial Number: 13

Segment Identification Number: 12FTC

Description: This segment is used for providing Fund transaction currency information

Segment Mandatory/Optional?: Mandatory

Multiple records allowed for the same Fund and Rule Effective Date: Yes

Field Name	Type	Maximum Length	Mandatory / Optional?	Characteristics / Validations applicable	Description
SEG­MENTID	Alpha­numeric	20	Mandatory	Default value 12FTC	Standard value of 12FTC to uniquely identify Fund transaction currency infor­mation
PROCES­SID	Alpha­numeric	50	Mandatory	Same value as in 00GEN - Pro­cessID	This should iden­tify the upload uniquely. This should also be unique within a file and it allows to identify imported records later
FUNDID	Alpha­numeric	6	Mandatory		The Fund ID is a unique Identifica­tion for each Fund and it indi­cates the fund for which Fund transaction cur­rency informa­tion has to be uploaded
RULEEF­FECTIVE­DATE	Date	8	Mandatory	The Fund ID and Rule effec­tive date combi­nation should be the same as defined in 01FDR	The rule effective date for which fund transaction currency infor­mation for the fund has to be maintained.
CURREN­CYCODE	Alpha­numeric	3	Optional	Valid currency maintained in the system	If no currency code is men­tioned and this field is left blank then it means that there is no restriction on the currency used for transaction for this fund. How­ever, if valid value is entered then the fund would be restricted for transaction in those currencies

Serial Number: 14

Segment Identification Number: 13FAI

Description: This segment is used for providing Fund additional information

Segment Mandatory/Optional?: Mandatory

Multiple records allowed for the same Fund and Rule Effective Date: No

Field Name	Type	Maximum Length	Mandatory / Optional?	Characteristics / Validations applicable	Description
SEG­MENTID	Alphanu­meric	20	Mandatory	Default value 13FAI	Standard value of 13FAI to uniquely identify Fund additional infor­mation
PRO­CESSID	Alphanu­meric	50	Mandatory	Same value as in 00GEN - Pro­cessID	This should iden­tify the upload uniquely. This should also be unique within a file and it allows to identify imported records later
FUNDID	Alphanu­meric	6	Mandatory		The Fund ID is a unique Identifica­tion for each Fund and it indi­cates the fund for which Fund addi­tional informa­tion has to be uploaded
RULEEF­FEC­TIVEDATE	Date	8	Mandatory	The Fund ID and Rule effec­tive date combi­nation should be the same as defined in 01FDR	The rule effec­tive date for which fund addi­tional informa­tion for the fund has to be main­tained.
OTHER­INFO1	Alphanu­meric	60	Optional		Additional infor­mation could be maintained in the system as a art of 'Add Info Main­tenance'. Once this is done, for a specific AMC, the additional infor­mation can be mapped for the entity type Fund. Hence, as a part of Fund addi­tional informa­tion maintenance, the values could be captured. Any such additional information can be captured using these fields
OTHER­INFO2	Alphanu­meric	60	Optional
OTHER­INFO3	Alphanu­meric	60	Optional
OTHER­INFO4	Alphanu­meric	60	Optional
OTHER­INFO5	Alphanu­meric	60	Optional
OTHER­INFO6	Alphanu­meric	60	Optional
OTHER­INFO7	Alphanu­meric	60	Optional
OTHER­INFO8	Alphanu­meric	60	Optional
OTHER­INFO9	Alphanu­meric	60	Optional
OTHER­INFO10	Alphanu­meric	60	Optional
OTHER­INFO11	Alphanu­meric	60	Optional
OTHER­INFO12	Alphanu­meric	60	Optional
OTHER­INFO13	Alphanu­meric	60	Optional
OTHER­INFO14	Alphanu­meric	60	Optional
OTHER­INFO15	Alphanu­meric	60	Optional
OTHER­INFO16	Alphanu­meric	60	Optional
OTHER­INFO17	Alphanu­meric	60	Optional
OTHER­INFO18	Alphanu­meric	60	Optional
OTHER­INFO19	Alphanu­meric	60	Optional
OTHER­INFO20	Alphanu­meric	60	Optional
OTHER­INFO21	Alphanu­meric	60	Optional
OTHER­INFO22	Alphanu­meric	60	Optional
OTHER­INFO23	Alphanu­meric	60	Optional
OTHER­INFO24	Alphanu­meric	60	Optional
OTHER­INFO25	Alphanu­meric	60	Optional
OTHER­INFO26	Alphanu­meric	60	Optional
OTHER­INFO27	Alphanu­meric	60	Optional
OTHER­INFO28	Alphanu­meric	60	Optional
OTHER­INFO29	Alphanu­meric	60	Optional
OTHER­INFO30	Alphanu­meric	60	Optional

Serial Number: 15

Segment Identification Number: 14IRA

Description: This segment is used for providing Fund IRA information, if applicable

Segment Mandatory/Optional? : Optional

Multiple records allowed for the same Fund and Rule Effective Date: No

Field Name	Type	Maximum Length	Mandatory / Optional?	Characteristics / Validations applicable	Description
SEG­MEN­TID	Alphanu­meric	20	Mandatory	Default value 14IRA	Standard value of 14IRA to uniquely identify Fund IRA information
PRO­CES­SID	Alphanu­meric	50	Mandatory	Same value as in 00GEN - Pro­cessID	This should iden­tify the upload uniquely. This should also be unique within a file and it allows to identify imported records later
FUN­DID	Alphanu­meric	6	Mandatory		The Fund ID is a unique Identifica­tion for each Fund and it indicates the fund for which Fund IRA informa­tion has to be uploaded
RULEEFFEC­TIVE­DATE	Date	8	Mandatory	The Fund ID and Rule effec­tive date combi­nation should be the same as defined in 01FDR	The rule effective date for which fund IRA information for the fund has to be maintained.
MININI­TIALIN­VESTMENTAMT	Number	15	Mandatory		Minimum initial investment amount
MAX­INI­TIALINVEST­MEN­TAMT	Number	15	Mandatory		Maximum initial investment amount
MININ­VEST­MENTAMT	Number	15	Mandatory		Minimum invest­ment amount
MAXIN­VEST­MENTAMT	Number	15	Mandatory		Maximum invest­ment amount
MIN­WITH­DRAWALAMT	Number	15	Mandatory		Minimum With­drawal amount
MAX­WITH­DRAWALAMT	Number	15	Mandatory		Maximum With­drawal amount

Serial Number: 16

Segment Identification Number: 15FDI

Description: This segment is used for providing Fund delivery instruction information, if applicable

Segment Mandatory/Optional?: Optional

Multiple records allowed for the same Fund and Rule Effective Date: No

Field Name	Type	Maximum Length	Mandatory / Optional?	Characteristics / Validations applicable	Description
SEG­MENTID	Alphanu­meric	20	Mandatory	Default value 15FDI	Standard value of 15FDI to uniquely identify Fund trans­action currency information
PRO­CESSID	Alphanu­meric	50	Mandatory	Same value as in 00GEN - ProcessID	This should iden­tify the upload uniquely. This should also be unique within a file and it allows to identify imported records later
FUNDID	Alphanu­meric	6	Mandatory		The Fund ID is a unique Identifica­tion for each Fund and it indicates the fund for which Fund delivery instruction has to be uploaded
RULEEFFEC­TIVE­DATE	Date	8	Mandatory	The Fund ID and Rule effec­tive date com­bination should be the same as defined in 01FDR	The rule effective date for which Fund delivery instruction informa­tion for the fund has to be main­tained.
REGIS­TERE­DACCOUNT	Number	1	Mandatory	Valid values are '0' and '1'	Indicate as '1' if the respective delivery mode is applicable for the fund
DELIV­ERYTO­CUSTODIAN	Number	1	Mandatory	Valid values are '0' and '1'
DELIV­ERYTO­CLGAGENT	Number	1	Mandatory	Valid values are '0' and '1'
PHYSI­CALCERTDE­LIVERY	Number	1	Mandatory	Valid values are '0' and '1'
DEFAULTDE­LIVERY	Alphanu­meric	2	Mandatory	Valid values are ‘RA’ for Registered account, ‘CU’ for Deliver to Custodian, ’CL’ for Deliver to Clearing Agent and ‘PD’ for Physical deliv­ery	Should be based on allowed deliv­ery modes
CER­TIFI­CATEDENOMI­NATIONS	Alphanu­meric	200	Optional	This value should be specified with necessary field and record separator as shown below:- 10|0:100|1:500|0:1000|0 where the field separator between Denomination value and Default is ‘|’ and the record separator is colon - ‘:’	This is applicable only in case of scri­pless funds having Physical delivery as one of the deliv­ery instruction.
PUEV	NUM­BER	1	Optional	Valid values are 0 and 1	This is a new deliv­ery+ option

3.1.3 PROCESSINGFREQ (ref 11FLM, 12.10)

* Allocation: This will mean that you will be charging the investor a fee or giving an incentive at the time of allocation of units. Allocation time loads cannot be designated for any transaction types other than IPO, subscription, redemption, and switch.

* Transaction: The charge (fee) or incentive will be applied at the time the transaction request is accepted from the investor.

* Post Allocation: This frequency is applicable typically to the Capital Gains Tax, which may be applied after allocation, on the gross amount.

Capital Gains Tax may also be designated as an allocation time load.

Serial Number: 17

Segment Identification Number: 17KYC

Description: This segment is used for capturing the Document information, if applicable

Segment Mandatory/Optional?: Optional

Multiple records allowed for the same Fund and Rule Effective Date: Yes

Field Name	Type	Maximum Length	Mandatory / Optional?	Characteristics / Validations applicable	Description
SEG­MENTID	Alphanu­meric	20	Mandatory	Default value 17KYC	Standard value of 17KYC is to uniquely identify Fund document description.
PRO­CESSID	Alphanu­meric	50	Mandatory	Same value as in 00GEN - Pro­cessID	This should iden­tify the upload uniquely. This should also be unique within a file and it allows to identify imported records later
FUNDID	Alphanu­meric	6	Mandatory		The Fund ID is a unique Identifica­tion for each Fund and it indicates the fund for which Fund delivery instruction has to be uploaded
RULEEFFEC­TIVE­DATE	Date	8	Mandatory	The Fund ID and Rule effec­tive date combi­nation should be the same as defined in 01FDR	The rule effective date for which Fund delivery instruction infor­mation for the fund has to be maintained.
Docu­mentDe­scription	Alphanu­meric Code	255	Optional	Captured only if the KYCAML parameter is set to True.	Used for captur­ing the document description.

Serial Number: 18

Segment Identification Number: 18MLD

Description: This segment is used for capturing the information in multiple languages against the language codes.

Segment Mandatory/Optional?: Optional

Multiple records allowed for the same Fund and Rule Effective Date: Yes

Field Name	Type	Maximum Length	Mandatory / Optional?	Characteristics / Validations applicable	Description
SEG­MENTID	Alpha­numeric	20	Mandatory	Default value 18MLD	Standard value of 18MLD is to uniquely identify multiple lan­guages.
PRO­CESSID	Alpha­numeric	50	Mandatory	Same value as in 00GEN - ProcessID	This should iden­tify the upload uniquely. This should also be unique within a file and it allows to identify imported records later
FUNDID	Alpha­numeric	6	Mandatory		The Fund ID is a unique Identifica­tion for each Fund and it indicates the fund for which Fund delivery instruction has to be uploaded
RULEEFFEC­TIVE­DATE	Date	8	Mandatory	The Fund ID and Rule effec­tive date combi­nation should be the same as defined in 01FDR	The rule effective date for which Fund delivery instruction informa­tion for the fund has to be main­tained.
Lan­guage­Code	Alpha­numeric Code	12	Optional		Used for capturing the information in multiple lan­guages against the language code.
Fund­Name	Alpha­numeric Code	60	Optional		Enter the name of the fund for which the Fund Demo­graphics profile is being set up in this record

Serial Number: 19

Segment Identification Number: 19FSI

Description: This segment is used for providing Fund Investment Account SI, if applicable

Segment Mandatory/Optional?: Optional

Multiple records allowed for the same Fund and Rule Effective Date: Yes

Field Name	Type	Maximum Length	Mandatory / Optional?
MAXNOOFSITRANSACTIONS	NUMBER	4	Optional
MAXVALIDITY	NUMBER	4	Optional

Serial Number: 20

Segment Identification Number: 20HFP

Description: This segment is used for providing hedge fund parameters

Segment Mandatory/Optional?: Optional

Field Name	Type	Maximum Length	Mandatory / Optional?
SegmentID	VARCHAR2	20	Mandatory
ProcessID	VARCHAR2	50	Mandatory
FundID	VARCHAR2	6	Mandatory
RuleEffectiveDate	DATE	7	Mandatory
HedgeFundType	VARCHAR2	1	Mandatory
HedgeFundManager	VARCHAR2	12	Mandatory
TxnGenerationBasis	VARCHAR2	1	Optional
MasterFundUHID	VARCHAR2	12	Optional
NoticePeriodforRed	NUMBER	5	Optional
ComputationMethod	VARCHAR2	4	Optional
RuleGroupID	VARCHAR2	10	Optional
PerformancefeePer	NUMBER	3	Optional
AccrualFrequency	VARCHAR2	1	Optional
NextAccrualDate	DATE	7	Optional
PaymentFrequency	VARCHAR2	1	Optional
NextPaymentDate	DATE	7	Optional
HurdleRateApplicable	VARCHAR2	1	Optional
HurdleType	VARCHAR2	1	Optional
ResetHurdle	VARCHAR2	1	Optional
HurdleRateType	VARCHAR2	1	Optional
CalculationMethod	VARCHAR2	1	Optional
DayBasis	VARCHAR2	1	Optional
RateCode	VARCHAR2	15	Optional
RateBasis	VARCHAR2	1	Optional
Rate	NUMBER	20	Optional

Serial Number: 21

Segment Identification Number: 21HFL

Description: This segment is used for providing hedge fund linkage details

Segment Mandatory/Optional?: Optional

Field Name	Type	Maximum Length	Mandatory / Optional?
SegmentID	VARCHAR2	20	Mandatory
ProcessID	VARCHAR2	50	Mandatory
FundID	VARCHAR2	6	Mandatory
RuleEffectiveDate	DATE	7	Mandatory
LinkFundID	VARCHAR2	6	Mandatory
Percentage	NUMBER	3	Optional
Unit holder ID	VARCHAR2	12	Optional

Serial Number: 22

Segment Identification Number: 21HFD

Description: This segment is used for providing investor category details for hedge funds

Segment Mandatory/Optional?: Optional

Field Name	Type	Maximum Length	Mandatory / Optional?
SegmentID	VARCHAR2	20	Mandatory
ProcessID	VARCHAR2	50	Mandatory
FundID	VARCHAR2	6	Mandatory
RuleEffectiveDate	DATE	7	Mandatory
InvestorCategory	VARCHAR2	25	Mandatory
PerformanceFeeR­ate	NUMBER	20	Mandatory

3.1.4 Fund Related Information Upload Segments Format

The upload file would contain various segment identification numbers in the first column to indicate the type of data that is present in that entire row. Each segment identified by a unique tag, indicates the type of Fund rule related information like Fund entity, Fund calendar and Fund Agency Branch Back-dating limit.

Segment Identification Number	Description	Segment Mandatory / Optional?	Multiple records allowed for the same Fund and Rule Effective Date
00GEN	This segment is used for providing information that is common to the other fund related rules that need to be uploaded in the system.	Mandatory and will be the driving header segment for all the other segments.	No
01FEM	This segment is used for providing Fund entity related information that needs to be uploaded in the system for the Fund.	Optional	Yes [For various entity types and entity ids]
02FAB	This segment is used for providing Fund agency branch back-dating informa­tion that needs to be uploaded in the system for the Fund.	Optional	Yes [For various transaction types]
03FBC	This segment is used for providing Fund based cal­endar related information that needs to be uploaded in the system for the Fund.	Optional	Yes [For various years]

3.1.4.1 Fund Related Information Segments Formats

Serial Number: 1

Segment Identification Number: 00GEN

Description: This segment is used for providing information that is common to the other fund related rules that need to be uploaded in the system.

Segment Mandatory / Optional?: Mandatory and will be the driving header segment for all the other segments.

Multiple records allowed for the same Fund and Rule Effective Date: No

Field Name	Type	Maximum Length	Mandatory / Optional?	Characteristics / Validations applicable	Description
PROCES­SID	Alphanu­meric	50	Mandatory		This should iden­tify the upload uniquely. This should also be unique within a file and it allows to identify imported records later
BULKCLI­ENT­CODE	Alphanu­meric	12	Mandatory		Valid authorized, enabled Bulk cli­ent codes main­tained in the system as a part of Entity mainte­nance.
IMPORT­FILE­NAME	Alphanu­meric	255	Mandatory		This is the name of the file being uploaded into the FCIS system
AMCID	Alphanu­meric	12	Mandatory		Valid authorized, enabled AMC maintained in the system as a part of Entity mainte­nance. The fund rule upload defaulting would be based on both AMCID and the Bulk client code.
USERID	Alphanu­meric	15	Mandatory		The fund rule MakerID would have the value of UserID as a part of data storage in all the fund rule tables.
UPLOAD­MODE	Alphanu­meric	1	Mandatory	Valid values are 'N' and 'I'	Should be 'N' for New fund rule. And ‘I’ for Amending an existing author­ized fund rule.
GENERA­TEAUTH­FUNDRULE	Alphanu­meric	1	Optional	Valid values are 'A' and 'U'	This indicates whether the fund rule uploaded should be a authorized fund rule or un-author­ized fund rule.

Serial Number: 2

Segment Identification Number: 01FEM

Description: This segment is used for providing Fund entity related information

Segment Mandatory / Optional: Optional

Multiple records allowed for the same Fund and Rule Effective Date: Yes (For various entity types and entity IDs)

Field Name	Type	Maximum Length	Mandatory/Optional?	Characteristics / Validations applicable	Description
SEG­MENTID	Alpha­numeric	20	Mandatory	Default value 01FEM	Standard value of 01FEM to uniquely identify Fund entity information
PRO­CESSID	Alpha­numeric	50	Mandatory	Same value as in 00GEN - ProcessID	This should identify the upload uniquely. This should also be unique within a file and it allows to identify imported records later
FUNDID	Alpha­numeric	6	Mandatory	Depending upon the scheme cross reference maintained at the Bulk client defaults - this field value could either be FundID, Fund Identification number or Fund ticker symbol.	The Fund ID is a unique Identification for each Fund in the system. Enter the fund for which a Fund entity map­ping needs to be maintained.
ENTITY­TYPE	Alpha­numeric	2	Optional	Valid values are - 'A' for Agent; 'Q' for Check Ven­dor;'U' for Investor, 'L' for Clearing Agent; 'IC' for Individual cus­tomer cate­gory and 'CC' for Corporate customer cate­gory	The entity type for which the fund is mapped. This helps us to understand whether it is a Fund-Agent map­ping, Fund-Check Vendor mapping, Fund-Clearing Agent mapping, Fund-Investor map­ping, Fund-Individ­ual category mapping or Fund - Corporate category mapping
ENTIT­YID	Alpha­numeric	12	Optional	Valid entity ID maintained in the system as a part of Single entity mainte­nance for the respective entity type.	The Entity ID which belongs to the entity type specified
DISA­BLE	Number	1	Optional	Valid values are '0' and '1'	This is to indicate whether the defini­tion should be disa­bled or enabled.
RESTRICTIVEL­IST	Number	1	Optional	Valid values are '0' and '1'	Indicates whether the mapping is a positive list or nega­tive list. The value of '1' indicates that it is a negative list and vice versa.
DEFAULTOP­TION	Alpha­numeric	15	Optional	Valid values are null, 'BULKCLIENT­CODE' or any valid Fund Id available in the system.	* If the default option is null, then all values provided by the user for entity type, entity id and Restrictive list should be used. * If the value 'BULK­CLIENTCODE' is mentioned, then default the informa­tion based on the bulk client code mentioned as a part of header segment. * If any other Fund ID value is men­tioned, then default values based on the latest available record for the Fund mentioned.
UPLOADMODE	Alpha­numeric	1	Optional	Valid values are null, 'N' and 'I'. This is to override the value men­tioned as a part of header segment.	Should be 'N' for New fund rule. And ‘I’ for Incremental for Amending an existing authorized fund rule.
GENER­ATEAU­THFUNDRULE	Alpha­numeric	1	Optional	Valid values are null, 'A' and 'U'. This is to override the value men­tioned as a part of header segment.	This indicates whether the fund rule uploaded should be a author­ized fund rule or un-authorized fund rule.

Serial Number: 3

Segment Identification Number: 02FAB

Description: This segment is used for providing Fund agency branch back-dated related information

Segment Mandatory/Optional: Optional

Multiple records allowed for the same Fund and Rule Effective Date: Yes (For various transaction types)

Field Name	Type	Maximum Length	Mandatory/Optional?	Characteristics / Validations applicable	Description
SEG­MEN­TID	Alpha­numeric	20	Mandatory	Default value 02FAB	Standard value of 02FAB to uniquely identify Fund agency branch back-dating limit information
PRO­CES­SID	Alpha­numeric	50	Mandatory	Same value as in 00GEN - ProcessID	This should iden­tify the upload uniquely. This should also be unique within a file and it allows to identify imported records later
FUN­DID	Alpha­numeric	6	Mandatory	Depending upon the scheme cross reference main­tained at the Bulk client defaults - this field value could either be FundID, Fund Identification number or Fund ticker symbol.	The Fund ID is a unique Identifica­tion for each Fund in the system. Enter the fund for which a Fund agency branch back-dated limit needs to be main­tained.
AGENTCODE	Alpha­numeric	12	Optional	Valid agent as a part of entity maintenance	Valid entity id in the system for which entity type is 'A'
AGEN­CYBRANCH­CODE	Alpha­numeric	12	Optional	Valid agency branch as a part of entity maintenance	Valid entity id in the system for which the parent code is Agent code men­tioned in the previ­ous column
TRANSACTIONTYPE	Alpha­numeric	2	Optional	Valid values are '01' for IPO; '02' for Subscrip­tion; '03' for Redemption and so on.	Transaction type for which back-dat­ing limit is main­tained. Valid values are '01' to '10' rang­ing from IPO to Re-issue
BACK­DAT­INGPERIOD	Number		Optional	Back dating limit in days
DISA­BLE	Number	1	Optional	Valid values are '0' and '1'	This is to indicate whether the defini­tion should be disa­bled or enabled.
DEFAULTOP­TION	Alpha­numeric	15	Optional	Valid values are null, 'BULKCLI­ENTCODE' or any valid Fund Id available in the system.	* If the default option is null, then all values provided by the user for entity type, entity id and Restrictive list should be used. * If the value 'BULK­CLIENTCODE' is mentioned, then default the informa­tion based on the bulk client code mentioned as a part of header seg­ment. * If any other Fund ID value is mentioned, then default values based on the latest available record for the Fund men­tioned.
UPLOADMODE	Alpha­numeric	1	Optional	Valid values are null, 'N' and 'I'. This is to over­ride the value mentioned as a part of header segment.	Should be 'N' for New fund rule. And ‘I’ for Incremental for Amending an existing authorized fund rule.
GEN­ERA­TEAUTHFUN­DRULE	Alpha­numeric	1	Optional	Valid values are null, 'A' and 'U'. This is to over­ride the value mentioned as a part of header segment.	This indicates whether the fund rule uploaded should be an authorized fund rule or un-author­ized fund rule.

Serial Number: 4

Segment Identification Number: 03FBC

Description: This segment is used for providing Fund based calendar information

Segment Mandatory/Optional?: Optional

Multiple records allowed for the same Fund and Rule Effective Date: Yes (for various years)

Field Name	Type	Maximum Length	Mandatory/Optional?	Characteristics / Validations applicable	Description
SEG­MEN­TID	Alpha­numeric	20	Mandatory	Default value 03FBC	Standard value of 03FBC to uniquely identify Fund agency branch back-dating limit information
PRO­CES­SID	Alpha­numeric	50	Mandatory	Same value as in 00GEN - ProcessID	This should identify the upload uniquely. This should also be unique within a file and it allows to iden­tify imported records later
FUN­DID	Alpha­numeric	6	Mandatory	Depending upon the scheme cross reference maintained at the Bulk client defaults - this field value could either be FundID, Fund Identification number or Fund ticker symbol.	The Fund ID is a unique Identification for each Fund in the system. Enter the fund for which a Fund agency branch back-dated limit needs to be maintained.
YEAR	Number	4	Optional		The year for which the calendar need to be maintained for the fund.
DEFAULTOPTION	Alpha­numeric	15	Optional	Valid values are null, 'BULKCLIENT­CODE' or any valid Fund Id available in the system.	* If the default option is null, then all values provided by the user for entity type, entity id and Restrictive list should be used. * If the value 'BULKCLI­ENTCODE' is men­tioned, then default the information based on the bulk client code mentioned as a part of header segment. * If any other Fund ID value is mentioned, then default values based on the latest available record for the Fund mentioned.
UPLOADMODE	Alpha­numeric	1	Optional	Valid values are null, 'N' and 'I'. This is to override the value men­tioned as a part of header segment.	Should be 'N' for New fund rule. And ‘I’ for Incremental for Amending an existing authorized fund rule.
GEN­ERA­TEAUTHFUNDRULE	Alpha­numeric	1	Optional	Valid values are null, 'A' and 'U'. This is to override the value men­tioned as a part of header segment.	This indicates whether the fund rule uploaded should be a authorized fund rule or un-authorized fund rule.

3.1.5 EPU Upload File Format

EPU upload is specific to OMSTA, as the assumption is that OMSTA maintains the following components and those component names are hard-coded in DIVIDENDEPUIMPTBL:

Field Name	Data Type	Remarks
Fund Id	Char (3)	The fund id in FCIS.
Distribution Type	Char (1)	This field will be ignored and the dividend type in FCIS will be treated as cash dividend.
Gross Or Net Distribu­tion	Char (1)	This field will be ignored.
Declaration Date	Date	The interface will verify if there is any generated cash dividend record for this date, and will update that record with the required EPU.
Payment Date / Re-investment Date	Date	This field will be ignored by the interface.
Gross Amount	Float	This will be a dividend component. Component code ‘GA’.
Dividend Amount	Float	This will be a dividend component. Component code ‘DA’.
Dividend Amount For­eign	Float	This will be a dividend component. Component code ‘AF’.
Dividend Amount For­eign Withholding Tax	Float	This will be a dividend component. Component code ‘WF’.
Dividend Amount For­eign Exempt	Float	This will be a dividend component. Component code ‘EF’.
Interest Amount	Float	This will be a dividend component. Component code ‘IA’.
Interest Amount Local	Float	This will be a dividend component. Component code ‘IL’.
Interest Amount For­eign	Float	This will be a dividend component. Component code ‘IF’.
Interest Amount For­eign Withholding Tax	Float	This will be a dividend component. Component code ‘TF’.
NPI Amount	Float	This will be a dividend component. Component code ‘NP’.
Interest Withheld Tax Amount	Float	This will be a dividend component. Component code ‘IT’.
Property Dividend Amount	Float	This will be a dividend component. Component code ‘PD’.

3.1.6 Tax Aggregation Interface Format

The formats for export and import of files for transfer of tax information are given below. This is applicable to annuity taxes only.

The Record Specifications for the export file containing tax is as follows:

Field Name	Description	Data Type	Remarks
Tax Year	The tax year applicable –format – ddmmccyy	Number (8)	This will be set to the last day of the fiscal year in he required format.
LOB	Line of Business code – ‘GAL’	String (3)	Will be set as ‘GAL’.
Agree­ment_Code	Contract number	Char (12)	Policy number
Pro­duct_Code	Product Code	Char (10)	Product code.
Sequence	Numeric Count	Number (4)	Record number, incremented sequentially.
Owner_­Client_Id	Client Number or owner of the contract	Char (9)	The unitholder id.
Title	Null	Char (12)	This will be set to null.
Initials	Null	Char (15)	This will be set to null.
Surname	Null	Char (64)	This will be set to null.
IDNumber	Null	Char (15)	This will be set to null.
IDType	Null	Char (2)	This will be set to null.
DOB	Nulls	Char (10)	This will be set to null.
ClientType	‘N’ for naturals	Char (1)	This will be set to null.
Tax_Num­ber	Nulls	Char (12)	This will be set to null.
TRUST­NUMBER	Nulls	Char (12)	This will be set to null.
AnnuType	‘C’ for compulsory, ‘V’ for voluntary	Char (1)	This will be set to ‘C’.
GN18	‘Y’ or ‘N’	Char (1)	This will be set to ‘N’.
Fund­Name	The pension Fund Name	Char (70)	Fund Name
Frequency	Frequency of the annu­ity income	Char (1)	The frequency of the annuity.
Pay­ments_left	No of payments left within the tax year	Number (2)	The remaining number of annuities to be executed.
TaxEarn­ings_YTD	The taxable earning to date for the tax year.	Number (8,2)	The total annuity till date, including the tax already applied.
TaxDe­duct­ed_YTD	Tax deducted for the tax year	Number (8,2)	The tax deducted for the current fis­cal year.
TaxEarn­ings	Taxable earnings for this annuity income	Number (8,2)	Taxable earnings for this annuity income
TaxDe­ducted	Tax to be deducted for that annuity income	Number (8,2)	Tax to be deducted for that annuity income
SystemId	The system ID as defined by the tax aggregation module.	Char (10)	This will be set to ‘FCIS’.
Scheme	Nulls	Char (30)	This will be set to null.

The control record for the export of information relating to tax has the following format:

Field Name	Description	Data Type	Remarks
Record	‘CONTROL’	Char (7)	This field will be set as ‘CONTROL’
SystemId	The system ID as defined by the tax aggregation module.	Char (10)	Will be set as ‘FCIS’.
Entries	Number of entries on the file	Num­ber (8)	The number of entries in the file.
TaxEarn­ings_YTD	The taxable earning to date for the tax year.	Num­ber (13,2)	The sum of all the TaxEarn­ings_YTD in the file.
TaxDeduct­ed_YTD	The tax deducted for that tax year.	Num­ber (13,2)	The sum of all the TaxDe­ducted_YTD in the file.
TaxEarnings	The taxable earnings for this annuity income	Num­ber (13,2)	The sum of all the TaxEarn­ings in the file.
TaxDeducted	The tax to be deducted for that annuity income.	Num­ber (13,2)	The sum of all the TaxDe­ducted in the file.
Tax_Recalc	The tax amount that should be deducted	Num­ber (13,2)	This will be set to null.
Tax_Differ	The difference between what should be deducted and what was calculated by the product admin system.	Num­ber (13,2)	This will be set to null.
Monthly_Ad­just	Not applicable		This will be set to null.

The Record Specifications for the import of tax aggregation information into FCIS is as indicated below. The import will only log the data in the designated tables of FCIS. There is no processing carried out on the data imported.

Field Name	Description	Data Type	Remarks
GCS_CLNO	The group client id	Char (20)	This field will be ignored.
TaxYear	The tax year applicable in dd/mm/ccyy format	Char (8)
TaxMonth	Month of the year	Char (2)
PARM	ProductCode	Char (8)
Agreement_Code	Contract Number	Char (12)	The policy number.
Sequence	Numeric Count	Char (4)	This fiekld will be ignored.
LOB	Line of Business – ‘GAL’	Char (3)	This field will be ignored.
Owner_Client_Id	Client Number or Owner of the contract	Char (9)	The unitholder id in FCIS.
Tax_Number	Nulls	Char (12)
TrustNumber	Nulls	Char (16)
AnnuType	‘C’ for compulsory, ‘V’ for volun­tary	Char (1)
GN18	‘Y’ or ‘N’	Char (1)
FundName	Nulls	Char (30)
Frequency	Frequency of the annuity income	Char (1)
Payments_Left	No of payments left within the tax year	Char (2)
TaxEarnings_YTD	The taxable earning to date for the tax year.	Char (16)
TAXDEDUCT­ED_YTD	The tax deducted for that tax year.	Char (16)
TaxEarnings	Taxable earnings for this annuity income	Char (16)
TaxDeducted	Tax to be deducted for that annu­ity income	Char (16)
Scheme	Nulls	Char (10)
Tax_Recalc	Tax amount that should be deducted	Char (16)
Tax_Deffer	The difference between what should be deducted and what was calculated by the product admin system.	Char (16)
Monthly_Adjust	Not applicable	Char (16)
SystemId	The system ID as defined by the tax aggregation module.	Char (10)
Tax_Remunera­tion	The total taxable income across the Old Mutual group.	Char (16)

The Control Record for the import of information pertaining to tax aggregation should be in the following format:

Field Name	Description	Data Type	Remarks
Record	‘CONTROL’	Char (7)	This field will be ignored.
SystemId	The system ID as defined by the tax aggre­gation module.	Char (10)	This field will be ignored.
Entries	Number of entries on the file	Number (8)	This field will be ignored.
TaxEarn­ings_YTD	The taxable earning to date for the tax year.	Number (13,2)	This field will be ignored.
TaxDeduct­ed_YTD	The tax deducted for that tax year.	Number (13,2)	This field will be ignored.
TaxEarnings	The taxable earnings for this annuity income	Number (13,2)	This field will be ignored.
TaxDeducted	The tax to be deducted for that annuity income.	Number (13,2)	This field will be ignored.
Tax_Recalc	The tax amount that should be deducted	Number (13,2)	This field will be ignored.
Tax_Differ	The difference between what should be deducted and what was calculated by the product admin system.	Number (13,2)	This field will be ignored.
Monthly_Ad­just	Not applicable

3.1.7 Agent Reference File

The files uploaded using the Agent Reference File have to be imported and the broker details updated. They should have the following format:

Field Name	Format	Comments	Remarks/ Mapping
Intermediary or Broker Code	Char 10	Intermediary Code and No	Broker Code
Broker Category	Char 1	Corporate/ Individual	Broker Category
Broker Name	Char 50	Individual name or corporate name	Broker Name
Broker Type	Char	For example, Platinum, Gold, Silver	Broker Type
Parent Broker	Char	Channel – For example, PFA, BD	Parent Broker Code
Active Flag	Char	Y/N	Broker Enabled
Date Effective	Date		Rule effective date

Control Record

The sum of the transaction amount for each day is recorded in the Control Record. The file upload should have the following format:

Field Name	Description	Data Type	OMUT Value	Galaxy Value
RECORD_ID	Indicates it’s the trailer record	Char (50)	All 9s	All 9s
GROUP_ID	Unique Group Number to distin­guish import data within a source	Char (15)	Source file id & run number	Source file id & run number
TOTAL_AMT_DR	Total monetary amount of debits on the file	Char (15)	Format: 999999999999.99'	Format: 999999999999.99'
TOTAL_CNT_DR	Total count of debits on the file	Char (8)	Format: 99999999	Format: 99999999
TOTAL_AMT_CR	Total monetary amount of credits on the file	Char (15)	Format: 999999999999.99'	Format: 999999999999.99'
TOTAL_CNT_CR	Total count of cred­its on the file	Char (8)	Format: 99999999	Format: 99999999

3.1.8 Global Order Placement Interface

Files uploaded using the Global Order Placement should have the following format:

Field Name	Calculation	Disinvestments	Investments
Transaction Date	N/A	Transaction Date	Transaction Date
Asset Code	For each Product – Fund combination, an asset code would be maintained	Yes	Yes
Fund Name	N/A	Yes	Yes
Product Name	N/A	Yes	Yes
Net Investment Amount (Amount with +ve sign)/ Disinvestment Amount(Amount with -ve sign)	Derived	0	Yes
Disinvestment Units	N/A	Yes	0
Manco Initial Unit Trust Fee	N/A	0	Yes
Transaction Type Name	Transaction Descrip­tions as available in the system	Yes	Yes
Internal Reference Number	Running serial per batch	Yes	Yes

3.1.9 GL Setup Upload Interface Format

Files uploaded using the GL Setup Upload should have the following format:

Field Name	Data Type	Details
Fund Id	Character(6)
GL Template Id	Character(10)	The template Id of the GL set up. A dummy value to be provided for this.
Account type	Character(2)	The account type of the GL set up.
Business Event	Character(2)	One of the valid codes for business events.
Trigger Event	Character(15)	The triggering event. One of the valid enu­merations for the triggering event.
Theoretical Flag	Character (1)	Y: Theoretical N: Actual
Setup Enabled	Character (1)	Y: Enabled N: Disabled
Component Id	Character(20)	One of the valid codes for business events.
Component Description	Character (255)	Description of the component code.
Debit credit Flag	Character(2)	Dr: Debit Cr: Credit
GL set up for primary	Character(1)	C: CASA G:GL S:SAP P:Payment
Primary Entity Type	Character(1)	The primary entity type of the GL set up. U: Uniholder D:Distributor M:AMC F:Fund
Account Number	Character(16)
AccountCurrency	Character(3)
Transaction Currency	Character(3)
Bank branch	Character(12)
Direct DebitApplicable	Character(1)	1: Applicable 0: Not applicable
GL setup for Contra	Character(1)	C: CASA G:GL S:SAP P:Payment
Contra Primary Entity Type	Character(1)	U: Uniholder D:Distributor M:AMC F:Fund
Contra Account Number	Character(16)
Contra Account Currency	Character(3)
Contra Transaction Cur­rency	Character(3)
Contra Bank branch	Character(12)
Contra Direct DebitAppli­cable	Character(1)	1: Applicable 0: Not applicable
Restricted reference types	Character(255)	A semicolon separated list of the restricted reference types.
GL Currency	Character(3)
GL reference number	Character(10)
Product Id	Character(10)
Product or Fund Level	Character(1)	F: Fund Level P: Product level
Mode of upload	Character(1)	N: new mode A: Amend mode

3.1.10 Interface to Check for Transaction Unrelated to GL Extraction

Files uploaded for checking the transaction unrelated to GL Extraction Interface should have the format mentioned below:

Field Name	Data Type	Details
IFaceRefNo	Charac­ter(25)	The reference number of the entry in the AMInter­facemasterTbl.
TransactionType	Character(2)	The transaction type of the entry.
Component	Charac­ter(20)	The component code of the entry.
TransactionNum­ber	Charac­ter(16)	The transaction number of the missing entry.
Valuedate	Date	The date on which the entry was expected to be passed.

3.1.11 File Format for OMIPAY FILE INTERFACE

The interface is capable of exporting the details in two separate formats. These are:

• The detailed format includes all the records of the day, for every individual broker.
• The Header record for OMIPAY contains the sum of all the brokers’ Commission accounts which have been listed in the Detailed Record.

The system extracts commission details for upfront and trailer (periodic load) commission.

3.1.12 File format for Header Record

The File format for the Header Record is as follows:

Field Name	Data Type	Details
Record Category	Number	It is displayed as 00
Trigger System	Character	Ensures the entries which require to be entered for calculation of Commission
Product Provider	Character	The code for which the file is processed to cal­culate commission. For example Unit Trust ‘UT’
Cycle Number	Number	The number of the cycle for which the export action is being processed
Interface Date	Number	The date of generation of the interface file
Number Of Transaction Records (01 Category)	Number	Total Number of transaction records on input file
Commission Total	Number	The total value of Premium amount on the Input File
Commission Allowance Total	Number	Value of Commission Allowance amounts on the Input File
Fund Value Total	Number	The total value of Fund Value amounts on the Input File
Current Potential Com­mission	Number	Applicable to recurring business only
Future Potential Commis­sion	Number	Applicable to recurring business only
Numeric Field 11	Number	Provide preceding zeros as 0000000

3.1.13 File format for Detailed Record

The Detail Record File format is the record of all the Broker details, involved in all the transactions for that day, taken individually. The file containing the Detailed records for all the individual Brokers. The file format used for Detailed records is:

Field Name	Data Type	Details
Record Category	Number	It is displayed as 00
Transaction Sequence Number	Number	Unique identifier of transaction in the source external interface
Product Provider	Character	The code for which the file is processed to calcu­late commission. For example Unit Trust ‘UT’
Cycle Number	Number	Preceded by zeros
Intermediary Code (Sales Code)	Number	The intermediary’s sales code as supplied on the policy proposal / application form. It consists of six digits preceded by zeros
Intermediary Type (Sales Type)	Number	Code for the intermediary who has initiated the sale of that policy; 0 is for the Sales Staff 1 is for the Office staff
Intermediary Commis­sion Percentage (Direct Share)	Number	The percentage of commission as indicated in the policy/ application form
Intermediary Figure Percentage (Indirect Share)	Numeric	The percentage of indirect commission as indi­cated in the policy/ application form
Sales Centre (branch / team structure code)	Character	An optional field
Sale Type	Character	Not applicable can be left blank
Policy Number (Con­tract Number)	Character	It is the Policy or Contract number
Policy Type (Contract Type)	Character	Only applicable for recurring business types, can be left blank
Policy Term	Number	It is applicable for recurring business only, default set at 01
Product Code	Character	The selection is available from a drop down list
Premium Amount	Number	The amount of the premium for a transaction
Premium Frequency	Character	You can select from a list, for the type of premium applicable
Premium Term	Number	The term for which the premium is applicable
Movement Code	Number	It is the number code for the type of transaction
Transaction Date	Number	The date on which the transaction takes place
Entry Date	Number	The date from which the new business/policy is started
Effective Date	Number	The date from which the policy becomes effective
Client or Entity Number	Character	It is an optional field
Client Name	Character	The name as mentioned in description
Fees	Character	Optional field
Commission Amount 01	Number	The commission amount for 1 year
Commission Amount 02	Number	The commission amount for the 2nd year
Life Credit	Character	Not mandatory can be left blank
Commission Year Indi­cator	Number	It indicates the year for which the commission is applicable
Commission Content	Number	It contains the commission amount for the two years
Commission Scaling Factor	Number	The amount agreed between the client and the broker
Commission Frequency	Character	It is optional, left blank
Commission Type	Character	This field is left blank
Current Potential Com­mission (Primary)	Number	It is applicable for only recurring business, input display shows 000000000000000
Future Potential Com­mission (Secondary)	Number	It is applicable for only recurring business, input display shows 000000000000000
VAT	Number	It is the value added tax, not required as input
Broker Reference	Character	It is the reference as specified on the application form
Currency Indicator	Character	It indicates the currency type selected
Agents Commission	Number	It is not applicable in this case, displayed as 000000000000000
Commission Allowance	Number	It is the waiver amount on the broker’s commis­sion
New Business Date	Number	It is the transaction date
Total Investment	Number	It is the total amount of investments
Investment Type	Character	An optional field can be left blank
Fund Value	Number	It is the sum of the average of the absolute values of the fund of the client
Layer type	Character	This field is left blank
Layer Number	Number	This field displays 00
Reject ID	Number	This field is not required for entry, it displays 00000000
Adjustment Indicator	Character	This field is not required for entry and is left blank
Territory	Character	This field is not required for entry
Annual Fund Total	Number	This field is not required for entry, it displays 000000000000000
Distribution Fee (Chan­nel)	Number	This field is not required for entry, it displays 000000000000000
Maximum Commission	Number	This field is not required for entry, it displays 000000000000000
Instance Number	Character	This field is not required for entry
BEN Type	Character	This field is not required for entry
EMM Client Number	Character	This field is not required for entry
Sales Instance	Number	This field is not required for entry, it displays 000
Transaction Instance	Number	This field is not required for entry, it displays 000

3.2 Incremental Upload Format

For Incremental mode, the system will modify data present in upload file. If data provided in the file is already present, then the system will override existing data with new value provided in the file. If data is not present in system, then the data provided in the file will be added.

The system will not change/replace data which is not available in file for incremental mode. for instance, in unit holder upload, if only telephone number is given in Incremental mode, the system will just update old phone number with new phone number without changing other fields.

The upload file would contain various segment identification number in the first column to indicate the type of data that is present in that entire row. The possible segments that would be used in Incremental upload are given below for reference:

Upload Type	Use Case	Description	Upload mode	Segments to be used in Incremental upload
Entity	Contact details update	Cell phone number to be made available in upload file	I	00EIM,02ECI
Entity	Contact details update	E-mail to be made available in upload file	I	00EIM,02ECI
Entity	Bank details Update	BANKCODE,BRANCH­CODE,ACCOUNT­TYPE,ACCOUNTNUMBER,ACCOUNTNAME,ACCOUNT­CURRENCY,DEFAULTDE­TAILS,DIRECTDEBITAPPLICABLE to be made available in upload file.If default flag is set as Yes, default flag for existing bank detail for same bank/branch/account type/account currency combination will be set as No	I	00EIM,01EBD
Broker	Contact details update	Cell phone number to be made available in upload file	I	00BRO,01CON
Broker	Contact details update	email number to be made avail­able in upload file	I	00BRO,01CON
Broker	Bank details Update	BANKCODE,BRANCH­CODE,ACCOUNT­TYPE,ACCOUNTNUMBER,ACCOUNTNAME,ACCOUNT­CURRENCY,DEFAULTDE­TAILS,DIRECTDEBITAPPLICABLE to be made available in upload file.If default flag is set as Yes, default flag for existing bank detail for same bank/branch/account type/account currency combination will be set as No	I	00BRO,02BAN
Unitholder	Address update	Address1,2,3,4,zip code, coun­try code to be made available in upload file	I	00UH,15CON
Unitholder	Address update	Address line to be made availa­ble in upload file	I	00UH,15CON
Unitholder	Address update	Address type along with Address1,2, city, country & BIC code to be made available in upload file	I	00UH,15CON
Unitholder	Contact details update	Cell phone number to be made available in upload file	I	00UH,15CON
Unitholder	Contact details update	email to be made available in upload file	I	00UH,15CON
Unitholder	Bank details Update	Beneficiary details to be made available in upload file	I	00UH,03BNK
Unitholder	Bank details Update	BANKCODE,BRANCH­CODE,ACCOUNT­TYPE,ACCOUNTNUMBER,ACCOUNTNAME,ACCOUNT­CURRENCY,DEFAULTDE­TAILS,DIRECTDEBITAPPLICABLE to be made available in upload file.If default flag is set as Yes, default flag for existing bank detail for same bank/branch/account type/account currency combination will be set as No	I	00UH,03BNK
Unitholder	Address & bank details update	Alternate Address line 2 & ben­eficiary info details to be made available in upload file in respective segments	I	00UH,15CON,03BNK
Trans­action	Settlement details Update	Cheque number & cheque date to be made available in file	I	00CON,01SET
Trans­action	Settlement details Update	Paid Date and settled to be made available in file	I	00CON,01SET
Trans­action	Settlement details Update	TRANSFERACCOUNTCUR­RENCY,TRANSFERAC­COUNTNUMBER,TRANSFERACCOUNTTYPE,TRANSFER­BRANCHCODE,PAYMENT DATE,PAYMENT AMOUNT to be made available in file	I	00CON,01SET
Trans­action	Settlement details Update	SWIFTFORMAT,BANK­CHARGED,BENEFI­CIARY,BENEFICIARYADDRESS,BENEFICIARYBIC­CODE,BENEFICIAR­YACCTNO,BENEFICIARYCODE,BENEFICIARYINFO to be made available in file	I	00CON,01SET

3.3 Sub Service Upload Format

You can create subservice to support specific amendment requests. Using Amendment maintenance, you can create a subservice to modify only specific fields as per the modifiable fields given in maintenance.

The upload file would contain various segment identification number in the first column to indicate the type of data that is present in that entire row. The possible segments that would be used in sub service upload are given below for reference:

Upload Type	Use Case	Description	Sub service operation
Entity	Bank details Update	BANKCODE,BRANCH­CODE,ACCOUNT­TYPE,ACCOUNTNUMBER,ACCOUNTNAME,ACCOUNTCUR­RENCY,DEFAULTDE­TAILS,DIRECTDEBITAPPLICABLE to be made available in upload file.If default flag is set as Yes, default flag for existing bank detail for same bank/branch/account type/account currency combination will be set as No	ENTITY_­BANKDTLS
Broker	Bank details Update	BANKCODE,BRANCH­CODE,ACCOUNT­TYPE,ACCOUNTNUMBER,ACCOUNTNAME,ACCOUNTCUR­RENCY,DEFAULTDE­TAILS,DIRECTDEBITAPPLICABLE to be made available in upload file.If default flag is set as Yes, default flag for existing bank detail for same bank/branch/account type/account currency combination will be set as No	BROKER_­BANKDTLS
Unitholder	Address update	Address1,2,3,4,zip code, country code to be made available in upload file	UH_CONDTLS
Unitholder	Bank details Update	BANKCODE,BRANCH­CODE,ACCOUNT­TYPE,ACCOUNTNUMBER,ACCOUNTNAME,ACCOUNTCUR­RENCY,DEFAULTDE­TAILS,DIRECTDEBITAPPLICABLE to be made available in upload file.If default flag is set as Yes, default flag for existing bank detail for same bank/branch/account type/account currency combination will be set as No	UH_BNK­DTLS
Unitholder	Beneficiary details	Email to be made available in upload file	UH_BENDTLS
Unitholder	Intermediary details	complete intermediary segment details to be made available in upload file	UH_IN­MDTLS
Transaction	Settlement details Update	First segment is mandatory.Com­plete details to be provided for settlement segment	TXN_SET­DTLS
Transaction	Intermediary update	complete intermediary segment details to be made available in upload file	TXN_INT­DTLS
Transaction	Intermediary update	complete intermediary segment details to be made available in upload file	TXN_INT­DTLS
Unitholder	Intermediary details	complete intermediary segment details to be made available in upload file	UH_IN­MDTLS

3.4 Entity Upload Format

The upload file would contain various segment identification number in the first column to indicate the type of data that is present in that entire row. The possible segments that would be used in entity upload are given below for reference:

Segment ID - 00EIM: This segment will be mandatory for incremental upload

Column Name	Mandatory fields in upload file for upload mode I	Modifiable fields in Incremental mode	Remarks
SEGMENTID	Yes		00EIM
PROCESSID	Yes		Unique
SEQUENCENUM­BER	Yes		Unique
BULKCLIENTCODE	Yes		Unique
IMPORTFILENAME	Yes		Unique
ENTITYID	Yes		Existing Entity ID
PARENTENTITY­FLAG	No
ENTITYNAME	No
ENTITYTYPE	Yes		Entity type belong­ing to Entity ID
PARENTENTITY	No
EFFECTIVEDATE	No
RECORDLINK	No
NEWENTITYNAME	No
NEWENTITYID	No
ENTITYBASECUR­RENCY	No
AUTH_STAT	Yes
UNIQUERECORD­NUMBER	No
MARKEDFORREIMP	No
ACCOUNTTYPES	No
ENTITYCATEGORY­TYPE	No
ENTITYCATEGORY	No
AMCID	No
SWITCHINGLOGIC	No
UHGENERATION­LOGIC	No
NATUREOFBUSI­NESS	No
SECTION	No
ENTITYSUBTYPE	No
CROSSBRANCHING	No
FUNDSPOWERIN­STALLED	No
CUSTOMERINTER­FACEKEY	No
ONLINEINTERFACE	No
WEEKENDBITS	No
AUTHORIZEDSIG­NATORY	No
LINKENTITYID	No
LINKENTITYTYPE	No
ALTLANGENTI­TYNAME	No
ALTLANGCONTACT­PERSON	No
ALTLANGAD­DRESS1	No
ALTLANGAD­DRESS2	No
ALTLANGCITY	No
ALTLANGSTATE	No
FINWAREPOSTING	No
CHANNELENTITY	No
MICRCODE	No
CHECK­ER_DT_STAMP	No
CHECKER_ID	No
COUNTRYOFBIRTH	No
COUNTRYOFDOMI­CILE	No
EIN	No
FATCACLASSIFICA­TION	No
FATCASTATUS	No
INCORPORATION­COUNTRY	No
MAKER_DT_STAMP	No
MAKER_ID	Yes		Valid id in system
MOD_NO	No
NATIONALITY	No
TAXCATEGORY	No
TAXCERTIFICA­TEEFFEDATE	No
TAXCERTIFICATE­EXPDATE	No
TAXCIRCLE	No
TAXID	No
UPLOADMODE	Yes		I
USINDICIAAVAILA­BLE	No
GIIN	No
FATCACLASSIFICA­TION	No
ISAREFERENCENO	No
CURRENCY	No
MINISATRANSFERIN	No
MINISATRANSFER­OUT	No
FUNDSTRUCTAP­PLICABLE	No
AUTOSETTLE­SWITCH	No
SWIFTMSGLIST	No
ELECTRONICDEAL­FLAG	No
DEFAULTAGENCY­BRANCH	No
BENEFICIAR­YACCTNO	No
EMAILID	No
PHONENUMBER	No

Segment ID - 01EBD

Column Name	Mandatory fields in upload file for upload mode I	Modifiable fields in Incremental mode	Remarks
SEGMENTID	Yes		01EBD
PROCESSID	Yes		Unique
SEQUENCENUMBER	Yes		Unique
BULKCLIENTCODE	No
ENTITYID	No
ENTITYTYPE	No
BANKCODE	Yes		If bank/branch/account type/account number/account currency combination pro­vided in file exists in system- other details will be updated.If does not exist, record will be inserted in system
BRANCHCODE	Yes
ACCOUNTTYPE	Yes
ACCOUNTNUMBER	Yes
ACCOUNTNAME	Yes
ACCOUNTCUR­RENCY	Yes
DEFAULTDETAILS	Yes	Yes
DIRECTDEBITAPPLI­CABLE	No	Yes
SWIFTFORMAT	No	Yes
BANKCHARGED	No	Yes
BENEFICIARY	No	Yes
BENEFICIARYADD1	No	Yes
BENEFICIARYADD2	No	Yes
BENEFICIARYADD3	No	Yes
BENEFICIARYBIC­CODE	No	Yes
BENEFICIAR­YACCTNO	No	Yes
BENEFICIARYCODE	No	Yes
BENEFICIARYINFO	No	Yes
INTERMEDIARY	No	Yes
INTERMEDIARYADD1	No	Yes
INTERMEDIARYADD2	No	Yes
INTERMEDIARYADD3	No	Yes
INTERMEDIARYBIC­CODE	No	Yes
INTERMEDIAR­YACCTNO	No	Yes
INTERMEDIARY­CODE	No	Yes
INTERMEDIARYINFO	No	Yes
FURTHERCREDIT­NAME	No	Yes
FURTHERCRED­ITACCTNO	No	Yes
REFERENCE1	No	Yes
REFERENCE2	No	Yes
IBAN	No	Yes
BENEFICIARYIBAN	No	Yes
INTERMEDIARYIBAN	No	Yes

Segment ID - 02ECI

Column Name	Mandatory fields in upload file for upload mode I	Modifiable fields in Incremental mode	Remarks
SEGMENTID	Yes		02ECI
PROCESSID	Yes		Unique
SEQUENCENUMBER	Yes		Unique
BULKCLIENTCODE	No
ENTITYID	No
ENTITYTYPE	No
ADDRESSTYPE	Yes		If address type present in file is available in sys­tem, system will be updated with remaining details present in file.If Address type pres­ent in file is not available in sys­tem, new address type will be added with details as avail­able in file
ADDRESSLINE1	No	Yes
ADDRESSLINE2	No	Yes
ADDRESSLINE3	No	Yes
ADDRESSLINE4	No	Yes
ZIPCODE	No	Yes
COUNTRY	No	Yes
USSTATE	No	Yes
TELEPHONE1	No	Yes
TELEPHONE2	No	Yes
CELLPHONENUMBER	No	Yes
FAX	No	Yes
EMAIL	No	Yes
CONTACTPERSON	No	Yes
EFFECTIVEFROMDATE	No	Yes
EFFECTIVETODATE	No	Yes
BICCODE	No	Yes
INTDIALLINGCODEPH1	No	Yes
INTDIALLINGCODEPH2	No	Yes
INTDIALLINGCODE­CELL	No	Yes
INTDIALLINGCODEFAX	No	Yes

Segment ID - 05ADD

Column Name	Mandatory fields in upload file for upload mode I	Modifiable fields in Incremental mode	Remarks
SEGMENTID	Yes		05ADD
SEQUENCENUMBER	Yes		Unique
PROCESSID	Yes		Unique
ADDINFOLABEL	Yes
FIELDVALUE	Yes	Yes

3.5 Broker Upload Format

The upload file would contain various segment identification number in the first column to indicate the type of data that is present in that entire row. The possible segments that would be used in Broker upload are given below for reference:

Segment ID - 00BRO: This segment will be mandatory for incremental upload

Column Name	Mandatory fields in upload file for upload mode I	Modifiable fields in Incremental mode	Remarks
SEGMENTID	Y		00BRO
SEQUENCENUMBER	Y		Unique
PROCESSID	Y		Unique
BULKCLIENTCODE	Y		Unique
IMPORTFILENAME	Y		Unique
UPLOADMODE	Y		I
BROKERCODE	Y		Valid broker code
BROKERNAME	N
PARENTBROKERCODE	N
BROKERBASECCY	N
AMCID	N
AUTH_STAT	Y		U/A
DELETEDSTATUS	N
OVERRIDDENTAXPER­CENTAGE	N
MAKER_ID	Y		Valid maker id
MAKER_DT_STAMP	N
LEVELNUMBER	N
RULEEFFECTIVEDATE	Y
CHANGETYPE	N
VATREGISTERED	N
VATREGISTRATION­NUMBER	N
COMMISSIONPERCENT­AGE	N
COMMISSIONPAYMENT­FREQ	N
UNITHOLDERID	N
LASTPAYMENTDATE	N
LASTPAYMENTNUMBER	N
LASTPROCESSEDDATE	N
NEXTPAYMENTDATE	N
CHECKER_ID	N
CHECKER_DT_STAMP	N
BROKERTYPE	N
USEBROKERTYPEPAY­MENTDATES	N
BROKERCONSULTANT	N
BROKERCATEGORY	N
HOLDBACKPAYMENT	N
MOD_NO	N
HOLDPYMTFROMDATE	N
LATESTRULE	N
BROKERSTATUS	N
RECORD_STAT	N
ONCE_AUTH	N
REPLICATEPARENTDET	N
VATREGISTRATION­DATE	N
TEMPLATEID	N
USINDICIAAVAILABLE	N
FATCASTATUS	N
NATIONALITY	N
COUNTRYOFBIRTH	N
COUNTRYOFDOMICILE	N
INCORPORATIONCOUN­TRY	N
TAXID	N
EIN	N
TAXCERTIFICATEEFFE­DATE	N
TAXCERTIFICATEEXP­DATE	N
TAXCIRCLE	N
FATCACLASSIFICATION	N
GIIN	N
VATEXPIRYDATE	N

Segment ID -01CON

Column Name	Mandatory fields in upload file for upload mode I	Modifiable fields in Incremental mode	Remarks
SEGMENTID	Y		01CON
SEQUENCENUMBER	Y		Unique
PROCESSID	Y		Unique
ENTITYID	N
ENTITYTYPE	N
ADDRESSTYPE	Y		If address type present in file is available in sys­tem, system will be updated with remaining details present in file.If Address type pres­ent in file is not available in sys­tem, new address type will be added with details as available in file
ADDRESSLINE1	N	Y
ADDRESSLINE2	N	Y
ADDRESSLINE3	N	Y
ADDRESSLINE4	N	Y
ZIPCODE	N	Y
COUNTRY	N	Y
USSTATE	N	Y
TELEPHONE1	N	Y
TELEPHONE2	N	Y
CELLPHONENUMBER	N	Y
FAX	N	Y
EMAIL	N	Y
CONTACTPERSON	N	Y
EFFECTIVEFROMDATE	N	Y
EFFECTIVETODATE	N	Y
BICCODE	N	Y
RULEEFFECTIVEDATE	Y	Y
INTDIALLINGCODEFAX	N	Y
INTDIALLINGCODEPH2	N	Y
INTDIALLINGCODEPH1	N	Y
INTDIALLINGCODECELL	N	Y

Segment ID -02BAN

Column Name	Mandatory fields in upload file for upload mode I	Modifiable fields in Incremental mode	Remarks
SEGMENTID	Y		02BAN
SEQUENCENUMBER	Y		Unique
PROCESSID	Y		Unique
BROKERCODE	N
RULEEFFECTIVEDATE	Y
REFERENCENUMBER	N
BANKCODE	Y		If bank/branch/account type/account number/account ccy combi­nation provided in file exists in sys­tem- other details will be updated.If does not exist, record will be inserted in system
BRANCHCODE	Y
ACCOUNTTYPE	Y
ACCOUNTNUMBER	Y
ACCOUNTNAME	Y
ACCOUNTCURRENCY	Y
DEFAULTDETAILS	Y	Y
DIRECTDEBITAPPLICA­BLE	N	Y
SWIFTFORMAT	N	Y
BANKCHARGED	N	Y
BENEFICIARY	N	Y
BENEFICIARYADD1	N	Y
BENEFICIARYADD2	N	Y
BENEFICIARYADD3	N	Y
BENEFICIARYBICCODE	N	Y
BENEFICIARYACCTNO	N	Y
BENEFICIARYCODE	N	Y
BENEFICIARYINFO	N	Y
INTERMEDIARY	N	Y
INTERMEDIARYADD1	N	Y
INTERMEDIARYADD2	N	Y
INTERMEDIARYADD3	N	Y
INTERMEDIARYBIC­CODE	N	Y
INTERMEDIARYACCTNO	N	Y
INTERMEDIARYCODE	N	Y
INTERMEDIARYINFO	N	Y
FURTHERCREDITNAME	N	Y
FURTHERCRED­ITACCTNO	N	Y
REFERENCE1	N	Y
REFERENCE2	N	Y
IBAN	N	Y
BENEFICIARYIBAN	N	Y
INTERMEDIARYIBAN	N	Y

Segment ID - 05ADD

Column Name	Mandatory fields in upload file for upload mode I	Modifiable fields in Incremental mode	Remarks
SEGMENTID	Y		05ADD
SEQUENCENUMBER	Y		Unique
PROCESSID	Y		Unique
OTHERINFOFIELD	Y
FIELDVALUE	N	Y

3.6 Unit Holder Upload Format

The upload file would contain various segment identification number in the first column to indicate the type of data that is present in that entire row. The possible segments that would be used in Unit Holder upload are given below for reference:

Segment ID - 00UH: This segment will be mandatory for incremental upload

Column Name	Mandatory fields in upload file for upload mode I	Modifiable fields in Incremental mode	Remarks
SEGMENTID	YES		00UH
SEQUENCENUM­BER	YES		Unique
PROCESSID	YES		Unique
BULKCLIENTCODE	YES		Unique
IMPORTFILENAME	YES		Unique
AMCID	YES
UPLOADMODE	NO		I
CIFNUMBER	NO
UNITHOLDERID	Yes
REFERENCENUM­BER	NO
ACCOUNTOPEN­INGDATE	NO
TITLE	NO
FIRSTNAME	NO
MIDDLENAME	NO
LASTNAME	NO
ACCOUNTOPERA­TIONTYPE	NO
FIRSTNOMINEE	NO
SECONDNOMINEE	NO
THIRDNOMINEE	NO
FATHER_SPOUSENAME	NO
INVESTORTYPE	NO
TAXDEDUCTEDAT­SOURCE	NO
TAXID	NO
TAXCIRCLE	NO
IDENTIFICATION­TYPE	NO
IDENTIFICATION­NUMBER	NO
IDENTIFICATIONIS­SUEDATE	NO
IDENTIFICATION­EXPIRYDATE	NO
RESIDENTSTATUS	NO
UHCATEGORY	NO
ACCOUNTSTMT­FREQ	NO
YTDSTMTREQD	NO
DATEOFBIRTH	NO
GUARDIANNAME	NO
RELATIONSHIP	NO
BENEFICIARY	NO
SEX	NO
MARITALSTATUS	NO
OCCUPATION	NO
NATIONALITY	NO
COUNTRYOFDOMI­CILE	NO
CORPORATION­TYPE	NO
FIRSTAUTHOR­IZEDSIGNATORY	NO
SECONDAUTHOR­IZEDSIGNATORY	NO
THIRDAUTHOR­IZEDSIGNATORY	NO
CONTACTNAME	NO
MINNOOFCORPO­RATESIGNATORY	NO
SCHEMECROSS­REFNO	NO
UHBASECUR­RENCY	NO
LANGUAGE	NO
REDEMPTIONMOP	NO
ACCOUNTSTMT­CURRENCY	NO
EMAILID	NO
FIRSTJOIN­TUHNAME	NO
SECONDJOIN­TUHNAME	NO
THIRDJOIN­TUHNAME	NO
ALTADDRESS­FROMDATE	NO
ALTADDRESSTO­DATE	NO
TELEPHONERED	NO
TELEPHONESWI	NO
WRITECHECK­FORMMF	NO
FEDWIREACHPAY­MENT	NO
IRSNOTIFICATION	NO
ROAINVESTOR	NO
ALLOWROAATCI­FLEVEL	NO
UHACCOUNTTYPE	NO
RPOCODE	NO
REGISTRATION­TYPE	NO
REGISTRATION­NAME	NO
ACCOUNTOPEN­INGPURPOSE	NO
REMARKS	NO
PREFERRED­MAILMODE	NO
NOTEPADAVAILA­BLE	NO
FEECATEGORY	NO
FEESUBCATE­GORY	NO
AGENTCODE	NO
BRANCHCODE	NO
MAKER_ID	Yes
MAKER_DT_STAMP	NO
CHECKER_ID	NO
CHECK­ER_DT_STAMP	NO
AUTH_STAT	Yes
STOPACCOUN­TREASON	NO
RELEASEDATE	NO
ALLSIGNATORIES­REQDTOSIGN	NO
TAXEXEMPTED	NO
INDEXATIONON­CGT	NO
CERTDELIVERY­PREF	NO
TEMPLATEID	NO
EFFECTIVEDATE	NO
CELLPHONENUM­BER	NO
PRIMARYCOUN­TRYCODE	NO
ALTCELLPHONE­NUMBER	NO
ALTHOMEPHONE­NUMBER	NO
ALTOFFICEPHONE­NUMBER	NO
ALTEMAILID	NO
SECONDARY­COUNTRYCODE	NO
PLACEOFISSUE	NO
ALTCONTACTNAME	NO
ALTFAXNUMBER	NO
PREFERREDFUND­FORREDEMPTION	NO
GUARDIANPAN­GIRNO	NO
GUARDIAN­FORM6061	NO
PRIMARYUH­FORM6061	NO
UNITHOLDERNRI	NO
EUSDOPTION	NO
TAXCERTIFICATE­EXPDATE	NO
PLACEOFBIRTH	NO
COUNTRYOFBIRTH	NO
FATFORNONFATF	NO
CHASINGDATE	NO
ADDNCOMMENTS	NO
ALLKYCRECEIVED	NO
RETAINTRADEACK	NO
RETAINCONTRACT­NOTES	NO
NOTREPORTKY­CREQ	NO
UHBICCODE	NO
ALTLANGFIRST­NAME	NO
ALTLANGMIDDLE­NAME	NO
ALTLANGLAST­NAME	NO
ALTLANGFIR­STAUTHSIGN	NO
ALTLANGSEC­ONDAUTHSIGN	NO
ALTLANGTH­IRDAUTHSIGN	NO
ALTLANGCON­TACTPERSON	NO
ALTLANGCORAD­DRESSLINE1	NO
ALTLANGCORAD­DRESSLINE2	NO
ALTLANGCORAD­DRESSLINE3	NO
ALTLANGCORAD­DRESSLINE4	NO
ALTLANGALTAD­DRESSLINE1	NO
ALTLANGALTAD­DRESSLINE2	NO
ALTLANGALTAD­DRESSLINE3	NO
ALTLANGALTAD­DRESSLINE4	NO
DATEOFCONTRI­BUTION	NO
TRANSFERDATE	NO
RETIREMENTAGE	NO
RETIREMENTDATE	NO
DATEOFDEATH	NO
DEATHCAUSE	NO
AREACODE	NO
DISPATCHDATE	NO
RETURNEDDATE	NO
PRIMARYUHMFIN	NO
GUARDIANMFIN	NO
RECOVERCGT	NO
PROCESSID1	NO
INITIALS	NO
KYCPURCHASE­LIMIT	NO
KYCANNUALDEBI­TORDERLIMIT	NO
CAMPAIGNCODE	NO
REDEMPTIONPAY­OUT	NO
DIVIDENDPAYOUT	NO
DUALNATIONALITY	NO
SUBSTANTIAL­STAYINUS	NO
TAXCERTIFICA­TEEFFEDATE	NO
SECONDIDENTITY­TYPE	NO
SECONDIDENTITY­NUMBER	NO
SECONDISSUE­DATE	NO
SECONDEXPIRY­DATE	NO
SECONDPLA­CEOFISSUE	NO
TRAILCOMMPREF	NO
DUEDILI­GENCELEVEL	NO
REVIEWEDBY	NO
LASTREVIEWED­DATE	NO
CHASERID	NO
CHASINGMODE	NO
NAMESCHECKOP­TION	NO
NAMESCHECK­REMARKS	NO
ACCOUNTSTATE­MENT	NO
CONTRACTNOTES	NO
INVESTORRISK­LEVEL	NO

Segment ID - 03BNK

Column Name	Mandatory fields in upload file for upload mode I	Modifiable fields in Incremental mode	Remarks
SEGMENTID	YES		03BNK
PROCESSID	YES		Unique
SEQUENCENUM­BER	YES		Unique
BANKCODE	YES		If bank/branch/account type/account num­ber/account ccy combination provided in file exists in sys­tem- other details will be updated.If does not exist, record will be inserted in sys­tem
BRANCHCODE	YES
ACCOUNTTYPE	YES
ACCOUNTNUMBER	YES
ACCOUNTNAME	YES
ACCOUNTCUR­RENCY	YES
DEFAULTDETAILS	YES	Y	If this is marked as Yes- the old bank/branch/account num­ber/account ccy combination will be marked as Default No.
DIRECTDEBITAP­PLICABLE	No	Y
ACCOUNTCATE­GORY	No	Y
INITIALS	No	Y
LASTNAME	No	Y
IDENTIFICATION­TYPE	No	Y
IDENTIFICATION­NUMBER	No	Y
STATUS	No	Y
IBAN	No	Y
REFERENCENUM­BER	No	Y
FUNDID	No	Y
TRANSACTION­TYPE	No	Y
SWIFTFORMAT	No	Y
BANKCHARGED	No	Y
BENEFICIARY	No	Y
BENEFICIARYADD1	No	Y
BENEFICIARYADD2	No	Y
BENEFICIARYADD3	No	Y
BENEFICIARYBIC­CODE	No	Y
BENEFICIAR­YACCTNO	No	Y
BENEFICIARY­CODE	No	Y
BENEFICIARYINFO	No	Y
INTERMEDIARY	No	Y
INTERMEDIARY­ADD1	No	Y
INTERMEDIARY­ADD2	No	Y
INTERMEDIARY­ADD3	No	Y
INTERMEDIARY­BICCODE	No	Y
INTERMEDIAR­YACCTNO	No	Y
INTERMEDIARY­CODE	No	Y
INTERMEDIARY­INFO	No	Y
FURTHERCREDIT­NAME	No	Y
FURTHERCRED­ITACCTNO	No	Y
REFERENCE1	No	Y
REFERENCE2	No	Y
RELATIONSHIP	No	Y
BENEFICIARYIBAN	No	Y
INTERMEDIARY­IBAN	No	Y

Segment ID - 04INM

Column Name	Mandatory fields in upload file for upload mode I	Modifiable fields in Incremental mode	Remarks
SEGMENTID	Y		04INM
PROCESSID	Y		Unique
SEQUENCENUM­BER	Y		Unique
ENTITYTYPE	Y		Existing inter­mediary in sys­tem will be replaced by one provided in file
ENTITYID	Y	Y
SPLITPERCENT	N	Y
DEFAULTINTERME­DIARY	N	Y

Segment ID - 02BEN

Column Name	Mandatory fields in upload file for upload mode I	Modifiable fields in Incremental mode	Remarks
SEGMENTID	Y		02BEN
SEQUENCENUM­BER	Y		Unique
PROCESSID	Y		Unique
EXISTINGUHORCIF	Y
ADDRESSLINE1	N	Y
ADDRESSLINE2	N	Y
ADDRESSLINE3	N	Y
ADDRESSLINE4	N	Y
ZIPCODE	N	Y
COUNTRY	N	Y
EMAIL	N	Y
CONTACTPERSON	N	Y
COUNTRYOFDOM­ICILE	N	Y
IBAN	N	Y
BENEFICIARYID	Y		If benefeciary id is existing in sys­tem,details in file wil be used to modify the record.If benefe­ciary id is not available for UH, new benefeciary record will be cre­ated
BENEFICIARY­TYPE	Y
BENEFI­CIARYNAME	N	Y	This field will not be modifiable if existing UH or CIF field is yes
BENEFICIARYDOB	N	Y	This field will not be modifiable if existing UH or CIF field is yes
BENEFICIARYRE­LATION	N	Y
BENEFICIARYGEN­DER	N	Y	This field will not be modifiable if existing UH or CIF field is yes
BENEFICIARYID­TYPE	N	Y	This field will not be modifiable if existing UH or CIF field is yes
BENEFICIARYID­NUMBER	N	Y	This field will not be modifiable if existing UH or CIF field is yes
BENEFICIAR­YAWARD	N	Y	This field will not be modifiable if existing UH or CIF field is yes
BENEFICIA­RYBANKCODE	N	Y	This field will not be modifiable if existing UH or CIF field is yes
BENEFICIARY­BRANCHCODE	N	Y	This field will not be modifiable if existing UH or CIF field is yes
BENEFICIAR­YACCTYPE	N	Y	This field will not be modifiable if existing UH or CIF field is yes
BENEFICIAR­YACCNAME	N	Y	This field will not be modifiable if existing UH or CIF field is yes
BENEFICIAR­YACCCCY	N	Y	This field will not be modifiable if existing UH or CIF field is yes
ACCOUNTNUM­BER	N	Y	This field will not be modifiable if existing UH or CIF field is yes

Segment ID - 07JNT

Column Name	Mandatory fields in upload file for upload mode I	Modifiable fields in Incremental mode	Remarks
SEGMENTID	Y		07JNT
PROCESSID	Y		Unique
SEQUENCENUM­BER	Y		Unique
EXISTINGUHORCIF	Y
BENEFICIARYID	Y		If benefeciary id is existing in sys­tem,details in file wil be used to modify the record.If benefe­ciary id is not available for UH, new Joint UH record will be cre­ated subject to existing valida­tions
BENEFI­CIARYNAME	N		This field will not be modifiable if existing UH or CIF field is yes
BENEFICIARYTYPE	Y
BENEFICIARYDOB	N	Y	This field will not be modifiable if existing UH or CIF field is yes
BENEFICIARYGEN­DER	N	Y	This field will not be modifiable if existing UH or CIF field is yes
BENEFICIARYP­ANNO	N	Y	This field will not be modifiable if existing UH or CIF field is yes
BENEFICIARY­FORM60	N	Y	This field will not be modifiable if existing UH or CIF field is yes
BENEFICIARYMFIN	N	Y	This field will not be modifiable if existing UH or CIF field is yes
COUNTRYOFDOMI­CILE	N	Y	This field will not be modifiable if existing UH or CIF field is yes
RECOVERCGT	N	Y
ADDRESSLINE1	N	Y
ADDRESSLINE2	N	Y
ADDRESSLINE3	N	Y
ADDRESSLINE4	N	Y
ZIPCODE	N	Y
COUNTRY	N	Y
EMAIL	N	Y
CONTACTPERSON	N	Y
USINDICIAAVAILA­BLE	N	N

Segment ID - 10ADD

Column Name	Mandatory fields in upload file for upload mode I	Modifiable fields in Incremental mode	Remarks
SEGMENTID	Y		10ADD
SEQUENCENUM­BER	Y		Unique
PROCESSID	Y		Unique
ADDINFOLABEL	Y
FIELDVALUE	N	Y

Segment ID - 15CON

Column Name	Mandatory fields in upload file for upload mode I	Modifiable fields in Incremental mode	Remarks
SEGMENTID	Y		15CON
PROCESSID	Y		Unique
SEQUENCENUM­BER	Y		Unique
UNITHOLDERID	N
REFERENCENUM­BER	N
ADDRESSTYPE	Y		If address type present in file is available in sys­tem, system will be updated with remaining details present in file.If Address type present in file is not available in system, new address type will be added with details as availa­ble in file
ADDRESSLINE1	N	Y
ADDRESSLINE2	N	Y
ADDRESSLINE3	N	Y
ADDRESSLINE4	N	Y
ZIPCODE	N	Y
COUNTRY	N	Y
USSTATE	N	Y
TELEPHONE1	N	Y
TELEPHONE2	N	Y
CELLPHONENUM­BER	N	Y
FAX	N	Y
EMAIL	N	Y
CONTACTPERSON	N	Y
EFFECTIVEFROM­DATE	N	Y
EFFECTIVETODATE	N	Y
BICCODE	N	Y
INTDIALLINGCO­DEPH1	N	Y
INTDIALLINGCO­DEPH2	N	Y
INTDIALLINGCODE­CELL	N	Y
INTDIALLINGCODE­FAX	N	Y

3.7 Transactions Upload Format

The upload file would contain various segment identification number in the first column to indicate the type of data that is present in that entire row. The possible segments that would be used in Transaction upload are given below for reference:

Segment ID - 00CON: This segment will be mandatory for incremental upload

Column Name	Mandatory fields in upload file for upload mode I	Modifiable fields in Incremental mode	Remarks
SEGMENTID	Y		00CON
PROCESSID	Y		Unique
SEQUENCENUM­BER	Y		Unique
TXNSERIALNUM­BER	Y		Unique
BULKCLIENT­CODE	Y		Unique
IMPORTFILENAME	Y		Unique
AMCID	Y
UPLOADMODE	Y		I
TRANSACTION­NUMBER	Y
REFERENCENUM­BER	N
TRANSACTION­DATE	Y
UNITHOLDERID	N
REFUNITHOLDE­RID	N
AGENTCODE	N
BRANCHCODE	N
FUNDID	N
AMOUNT	N
PAYMENTMODE	N
CHEQUENUMBER	N
CLEARINGDATE	N
TRANSACTION­CURRENCY	N
TRANSACTION­MODE	N
UNITSAPPLIED	N
PERCENTAPPLIED	N
TOFUNDID	N
TOUNITHOLDERID	N
REFTOUNITHOLD­ERID	N
TRANSACTION­TYPE	Y
REFTYPE	N
REMARKS	N
CERTIFICATE	N
	N
CIFNUMBER	N
TOCIFNUMBER	N
GROSSORNET	N
SUBPAYMENT­MODE	N
COMMUNICATION­MODE	N
POLICYNUMBER	N
PRODUCTID	N
LOIAPPLICABLE	N
REFFUNDID	N
REFTOFUNDID	N
ENTITYTYPE	N
ENTITYID	N
SETTLEMENT­DATE	N
DELIVERYOPTION	N
TRANSACTION­SUBTYPE	N
REVERSALCODE	N
CANCELINSTRUC­TION	N
FROMFUND­PRICEBASIS	N
TOFUNDPRICEBA­SIS	N
TXN_OR_PRICE_­DATE_FLAG	N
FROMPRICEDATE	N
TOPRICEDATE	N
SUBSCRIPTION­FUNDID	N
SUBSCRIPTION­PRICEBASIS	N
PAYMENTAL­LOWED	N
PROCESSID1	N
SUBSETTLE­MENTDATE	N
SUBPRICEDATE	N
BASECOST	N
EXCHANGERATE­DETAILS	N
DEALINGDATE	N
COMPLETION­DATE	N
EUSDOPTION	N
TODEALINGDATE	N
KYCCHASING­DATE	N
KYCRECEIVED	N
LOCKINPERIOD­FORGAIN	N
SWIINEXCHANG­ERATEAPPLIED	N
AUTOCLEARPRO­VISIONALBAL­ANCE	N
AUTOCLEARREIN­VESTMENTS	N
FEECURRENCY	N
MATURITYDATE	N
SUBSOURCEID	N
CERTSPILLOVER	N
ISSUED	N
BLOCKTXNNUM­BER	N
CPMFBONUSPER­CENT	N
CPMFCREDITLAG	N
RETAINAGEING	N
CAMPAIGNCODE	N
FXDEALDATE	N
FXVALUEDATE	N
MAKER_ID	Y
MAK­ER_DT_STAMP	N
CHECKER_ID	N
CHECK­ER_DT_STAMP	N
AUTH_STAT	Y
ORDERRE­CEIVEDDATE	N
TXNCATEGORY	N
ORDERRE­CEIVEDTIME	N
SOURCEID	N
LOADREFTYPE	N
KIIDRECEIVED	N

Segment ID - 01SET

Column Name	Mandatory fields in upload file for upload mode I	Modifiable fields in Incremental mode	Remarks
SEGMENTID	Y		01SET
TXNSERIALNUM­BER	Y		Unique
SEQUENCENUM­BER	Y		Unique
PROCESSID	Y		Unique
BULKCLIENT­CODE	Y		Unique
IMPORTFILENAME	Y		Unique
AMCID	N
TRANSACTION­NUMBER	N
PRODUCTID	N
POLICYNUMBER	N
SYSREFERENCE­NUMBER	N
UNITHOLDERID	N
PAYMENTREFER­ENCENUMBER	N
PAYMENTMODE	N
SUBPAYMENT­MODE	N
PAYMENTCUR­RENCY	N
PAYMENTDATE	N	Y
PAYMENTAMOUNT	N	Y
BANKCHARGES	N	Y
PAY­MENTCHARGES	N	Y
EXCHANGERATE­SOURCE	N	Y
EXCHANGERATE	N	Y
PAYMENTFBCTX­NAMOUNT	N
PAYMENTALTER­NATEAMOUNT	N
SETTLEMENT­DUEDATE	N	Y
PAIDDATE	N	Y
AUTOSETTLE­MENT	N	Y
PAYMENTSTATUS	N
CLEARINGSTATUS	N
PAID	N	Y
SETTLEMENT­METHOD	N
SETTLEMENTSTA­TUS	N
SETTLEMENTAT	N
CHEQUEDATE	N	Y
CHEQUENUMBER	N	Y
CHEQUECUR­RENCY	N	Y
CHEQUEAMOUNT	N	Y
DRAWEEBANK­CODE	N	Y
DRAWEE­BRANCHNAME	N	Y
PAYMEN­TREMARKS	N	Y
PAYMENTTYPE	N
THIRDPARTYAD­DRESS	N	Y
THIRDPARTYAD­DRESSLINE1	N	Y
THIRDPARTYAD­DRESSLINE2	N	Y
THIRDPARTYAD­DRESSLINE3	N	Y
THIRDPARTYAD­DRESSLINE4	N	Y
THIRDPARTYBIC­CODE	N	Y
THIRDPARTY­COUNTRYCODE	N	Y
THIRDPARTYPAY­MENTREFER­ENCE	N	Y
THIRDPARTYS­TATE	N	Y
THIRDPARTY­USSTATE	N	Y
THIRDPARTYZIP­CODE	N	Y
TRANSFERAC­COUNTCUR­RENCY	N		Complete transfer details can be updated if there are no existing transfer details & mode of payment is transfer or existing transfer details to be changed to new transfer details
TRANSFERAC­COUNTHOLDER­NAME	N
TRANSFERAC­COUNTNUMBER	N	Y
TRANSFERAC­COUNTTYPE	N	Y
TRANSFER­BRANCHCODE	N	Y
TRANSFERREF­ERENCENUMBER	N	Y
CREDITCAR­DREFNO	N	Y
INKINDPAYMENT­DETAILS	N	Y
PAYMENTAD­DRESSDETAILS	N	Y
OLDPAYMEN­TREFERENCENO	N
UHBICCODE	N	Y
SWIFTFORMAT	N	Y
BANKCHARGED	N	Y
BENEFICIARY	N	Y
BENEFICIARY­ADD1	N	Y
BENEFICIARY­ADD2	N	Y
BENEFICIARY­ADD3	N	Y
BENEFICIARYBIC­CODE	N	Y
BENEFICIAR­YACCTNO	N	Y
BENEFICIARY­CODE	N	Y
BENEFICIARY­INFO	N	Y
INTERMEDIARY	N	Y
INTERMEDIARY­ADD1	N	Y
INTERMEDIARY­ADD2	N	Y
INTERMEDIARY­ADD3	N	Y
INTERMEDIARY­BICCODE	N	Y
INTERMEDIAR­YACCTNO	N	Y
INTERMEDIARY­CODE	N	Y
INTERMEDIARY­INFO	N	Y
FURTHERCREDIT­NAME	N	Y
FURTHERCRED­ITACCTNO	N	Y
REFERENCE1	N	Y
REFERENCE2	N	Y
ENTITYID	N	Y
ENTITYTYPE	N	Y
IBAN	N	Y
BENEFICIARY­IBAN	N	Y
INTERMEDIARY­IBAN	N	Y
BENEFICIARYID	N	Y
BENEFI­CIARYPERCENT­AGE	N	Y
AMOUNTBLOC­KNO	N
SETTLED	N	Y
REVERSED	N	Y

Segment ID - 03AIF

Column Name	Mandatory fields in upload file for upload mode I	Modifiable fields in Incremental mode	Remarks
SEGMENTID	Y		03AIF
TXNSERIALNUM­BER	Y		Unique
SEQUENCENUM­BER	Y		Unique
PROCESSID	Y		Unique
BULKCLIENT­CODE	Y		Unique
IMPORTFILENAME	Y		Unique
AMCID	N
TRANSACTION­NUMBER	N
REFERENCENUM­BER	N
OTHERINFO1	N	Y
OTHERINFO2	N	Y
OTHERINFO3	N	Y
OTHERINFO4	N	Y
OTHERINFO5	N	Y
OTHERINFO6	N	Y
OTHERINFO7	N	Y
OTHERINFO8	N	Y
OTHERINFO9	N	Y
OTHERINFO10	N	Y
OTHERINFO11	N	Y
OTHERINFO12	N	Y
OTHERINFO13	N	Y
OTHERINFO14	N	Y
OTHERINFO15	N	Y
OTHERINFO16	N	Y
OTHERINFO17	N	Y
OTHERINFO18	N	Y
OTHERINFO19	N	Y
OTHERINFO20	N	Y
OTHERINFO21	N	Y
OTHERINFO22	N	Y
OTHERINFO23	N	Y
OTHERINFO24	N	Y
OTHERINFO25	N	Y
OTHERINFO26	N	Y
OTHERINFO27	N	Y
OTHERINFO28	N	Y
OTHERINFO29	N	Y
OTHERINFO30	N	Y

Segment ID - 04INT

Column Name	Mandatory fields in upload file for upload mode I	Modifiable fields in Incremental mode	Remarks
SEGMENTID	Y		Segment ID - 04INT
PROCESSID	Y		Unique
TXNSERIALNUM­BER	Y		Unique
SEQUENCENUM­BER	Y		Unique
ENTITYID	Y	Y	If this field is popu­lated along with dependant fields, this will replace entity at transaction level
ENTITYTYPE	Y	Y
SPLITPERCENT­AGE	N	Y
FROMORTOLEG	N	Y

Segment ID - 09LOD

Column Name	Mandatory fields in upload file for upload mode I	Modifiable fields in Incremental mode	Remarks
SEGMENTID	Y		09LOD
PROCESSID	Y		Unique
SEQUENCENUM­BER	Y		Unique
TXNSERIALNUM­BER	Y		Unique
LOADID	Y
FUNDID	N
CHANGETYPE	N	Y
CHANGEVALUE	N	Y
GROUPID	N		If not provided, sys­tem will consider this as DEFGRP

Segment ID - 10DLO

Column Name	Mandatory fields in upload file for upload mode I	Modifiable fields in Incremental mode	Remarks
SEGMENTID	Y		10DLO
PROCESSID	Y		Unique
SEQUENCENUM­BER	Y		Unique
TXNSERIALNUM­BER	Y		Unique
DERIVEDLOADID	Y
FUNDID	N
CHANGETYPE	N	Y
CHANGEVALUE	N	Y
PARENTLOADID	N

Segment ID - 12PSL

Column Name	Mandatory fields in upload file for upload mode I	Modifiable fields in Incremental mode	Remarks
SEGMENTID	Y		12PSL
PROCESSID	Y		Unique
SEQUENCENUM­BER	Y		Unique
TXNSERIALNUM­BER	Y		Unique
REFERENCENUM­BER	Y
LOADID	Y
FUNDID	N
CHANGETYPE	N	Y
CHANGEVALUE	N	Y
GROUPID	N		If not provided, sys­tem will consider this as DEFGRP

Segment ID - 13PSD

Column Name	Mandatory fields in upload file for upload mode I	Modifiable fields in Incremental mode	Remarks
SEGMENTID	Y		13PSD
PROCESSID	Y		Unique
SEQUENCENUM­BER	Y		Unique
TXNSERIALNUM­BER	Y		Unique
REFERENCENUM­BER	Y
DERIVEDLOADID	Y
FUNDID	N
CHANGETYPE	N	Y
DER­CHANGEVALUE	N	Y
PARENTLOADID	N