One of the main tasks carried out by the Fund Manager is performing the End of Day (EOD) and Beginning of Day (BOD) activities. These activities perform important functions in the system, and prepare it for the next business day. The system cannot logically close operations at the end of a working day or begin operations on the next business day if the End of Day and Beginning of Day processes are not performed.
Typically, only the following users or groups that are authorized to perform the End of Day activities in the Fund Manager component:
No other user or group will have access to this function.
This chapter contains the following sections:
Maintaining the Functions to be executed by the End of Day processes
Before you run the End of Day processes at any installation, you must first set up the functions that must be performed by the End of Day processes, through the End of Day Maintenance screen.
The End of Day Processing Sequence
The End of Day processes in the system follow a certain sequence of events, as explained below:
Pre-End of Day Checks
The Pre-End of Day checks will indicate any activities that are pending, that must be executed and completed by the Fund Manager before the End of Day process can be run. These pending activities can be viewed in the Fund Manager Pre-EOD Processing screen.
The pre-EOD checks could indicate unauthorized transactions, missing fund maintenance or processing information such as fund prices, exchange rates, signing off branches, and so on. The Fund Manager must complete these activities before the End of Day processes can be run.
The End of Day Processing
After all pending activities indicated by the Pre-End of Day processes have been completed, the End of Day processes can be executed, through the Execute End of Day option in the End of Day menu category of the Fund Manager component.
The functions scheduled as part of the End of Day processes are executed according to the sequence defined for them, and the frequency defined for their execution.
If a function whose successful execution is critical for the progress of the EOD process fails to execute, the EOD is aborted.
The End of Day processes perform important processes such as allocation of transactions, updating the unit holder balances, audit trail activities, running of jobs scheduled through the Scheduler Services, execution of interfaces and so on.
Reports scheduled to be generated during the EOD execution are also printed.
The Beginning of Day Process
After successful execution of all the End of Day processes, the Beginning of Day processes can be executed through the Execute BOD screen, that you can access from the End of Day menu category in the Fund Manager main menu.
The Beginning of Day processes set the application date of the system to the next business day.
Reports scheduled to be generated during the EOD execution are also printed.
After the whole EOD cycle (Pre-EOD, EOD and BOD) has been successfully completed, the system is ready for the next business day.
The End of Day and Beginning of Day processes can be performed manually, as well as automatically, as scheduled jobs through the Scheduler Services. Depending upon this mode of operation, the sequence of activities would be as follows:
Manual execution
Automatic execution
Therefore, for automatic execution of EOD, you must set up the following event-based jobs through the Scheduler:
Also, the following pre-defined tasks will be maintained at installation time for the automatic execution of EOD:
Note
If a report is scheduled to be printed as a job based on the BOD, the job must be manually executed after logging out of the Fund Manager module, so that the data as of the required date is obtained.
During automatic execution of EOD, the progress of the run can be viewed through the Scheduler Monitor. You must refresh the scheduler monitor frequently to view the status of the job.
During EOD, if an event is raised in the system, system extracts a file with the details of the contact person, their phone numbers and the message applicable for the event.
The execution and successful completion of each task and job is logged by the system.
Mini EOD Batch Execution
You can execute the following mini EOD batch for different AMC ID or Agent ID:
Note
For Dividend Freeze holding mini EOD, AMC ID input is considered only for AMC Installation. For Distributor Installation, the Agent Code selected during mini EOD process will be ignored during Dividend Freeze holding mini EOD process. The same applies for GL extract as well.
The End of Day processes also execute and process any authorized interface that has been defined with an external system, using the Online Execution of Interfaces menu item in the Batch menu category.
For a fuller description of this menu item, refer the ‘Interfaces’ User Manual.
This section contains the following topics:
The status of the Oracle FLEXCUBE Investor Servicing system changes during the course of each business day. At any point during the day, the system may be in one of three possible states:
The normal sequence of operations during a business day would result in changes of state as explained below:
Start of a Business Day
At the start of a business day, the system is online (status ‘O’), and both the Fund Manager and the Agency Branch are open for the acceptance of unit holder transactions and other operations.
Course of a Business Day
During the course of a business day, the system is still online (status ‘O’), and both the Fund Manager and the Agency Branch are still open for the acceptance of unit holder transactions and other operations.
Agency Branch Pre-EOD
When the Pre-End of Day processes are performed at the Agency Branch, the system is still online (status ‘O’), and both the Fund Manager and the Agency Branch are still open for the acceptance of unit holder transactions and other operations. The pre-EOD checks applicable for the branch alone are performed by the system during this phase. This Pre-EOD check mainly comprises of pending activities like authorization of transactions, etc., at an Agency Branch level.
Agency Branch EOD
When the End of Day process for the Agency Branch is performed, the system is still online (status ‘O’). The Agency Branch is signed off, and only allows inquiries and report printing activities, whereas the Fund Manager is still open for the acceptance of unit holder transactions and other operations.
Fund Manager Pre-EOD
When the Pre-End of Day process is performed for the Fund Manager component, the system is online (status ‘O’) till the successful completion of the pre-EOD. During this phase, the Agency Branch is signed off, and only allows inquiries and report printing activities, whereas the Fund Manager is still open for the acceptance of unit holder transactions and other operations. The pre-EOD checks for the Fund Manager are performed at this time.
Upon successful completion of Pre-EOD, the system status changes to ‘B’ (indicating that Pre-EOD has been successfully completed).
Fund Manager EOD
When the End of Day process is performed for the Fund Manager component, the system status is ‘B’ (indicating that Pre-EOD is successfully completed) till the successful completion of the EOD. During this phase, the Agency Branch is signed off, and only allows inquiries and report printing activities. The Fund Manager also allows only report printing during this phase, and it is not open for the acceptance of unit holder transactions and other operations.
Upon successful completion of EOD, the system status changes to ‘E’ (indicating that EOD has been successfully completed).
Fund Manager BOD
When the Beginning of Day process is started at the Fund Manager component, the system status is ‘E’ (indicating that EOD is successfully completed). The system date is changed to the next business day during this time.
Upon successful completion of EOD, the system status changes to ‘O’, indicating that both the Agency Branch and Fund Manager are now online and open for unit holder transactions and other operations.
The menu options for the End of Day processes are found in the Batch menu category of the Browser menu
For a fuller description of all the activities with respect to Validation and Allocation, refer the ‘Confirmation and Allocation’ chapter in this User Manual.
This section contains the following topics:
You can use this screen to view and schedule the functions that must be executed during the End of Day process run at the Fund Manager. You can assign a frequency and a critical status to each function.
The functions to be executed by the End of Day Process are set up by the implementers at the time of installation. You cannot add any new functions in this screen or edit any of the functions displayed. You can, however, schedule each function to be executed.
You can invoke the ‘EOD Maintenance Detail’ screen by typing ‘UTDEODMT’ in the field at the top right corner of the Application tool bar and clicking on the adjoining arrow button. You can retrieve the data through F8 function only and make the required changes. Each of the schedules you set up must be authorized to be effective, and can be amended after authorization.
You can perform the following operations can be performed in the EOD Maintenance screen:
You can specify the following fields in this screen:
EOD/BOD Activity
Optional
Specify the EOD or BOD activity. Choose one of the following options from the drop-down list:
After specifying EOD/ BOD Activity option, click on ‘Enter Query’ button. The system displays the following values:
The activities mapped against System Emergency Day Process will be restricted only to System level emergency day’s End of Day/Beginning of Day execution. For other entity level emergency holiday maintenances, the system will execute all the EOD/BOD activities by considering corresponding Fund/ Currency level holidays during this execution.
The system will mark the following EOD activities as default emergency day activities in EOD.
If any of the batch is not applicable for specific installation types, the same can be un-scheduled from emergency day activities.
Batches scheduled and maintained as Emergency day batch only will be executed during emergency day EOD. The system will skip all other batches during emergency day EOD execution even though they are scheduled in EOD.
Sl.No |
Activity Description |
1 |
UH Category change activities for Four Fund Class |
2 |
Misc. Activities for Online/Parallel Allocation |
3 |
Modify Ageing |
4 |
LEP - Update Product Fiscal year |
5 |
Update Transaction Enabled status |
6 |
Reset Unit holder Counter |
7 |
Derived Load Processing |
8 |
External Derived Load Processing |
9 |
Broker Migration |
10 |
Accrual data extraction |
11 |
Cancelled Transactions Settlement Amount Update |
12 |
Trailing Commission Accrual |
13 |
LEP - Update Plan Transaction Allotted Status |
14 |
Entity Commission Tracking Process |
15 |
Trading Box position adjustment process |
16 |
Unit holder account closure |
17 |
LEP - Plan Annuity 5/20 Validation Process |
18 |
Population of Gross Annualized Amount for Annuity Tax |
19 |
Year End Capital Gain Tax Calculation |
20 |
Daily CGT Calculation for Four Fund Class |
21 |
UH Stop Account release date Information Change |
22 |
Mark Unit holders for Dormancy |
23 |
Broker Status Change |
24 |
Process Transaction Components |
25 |
SI Cancellation Re-Activation |
26 |
Post Allocation Minimum holdings check |
27 |
Swift Transaction Allocation Status Updation |
28 |
UH-Automatic Closure of Inactive Accounts |
29 |
GL Extraction |
30 |
Accounting Export Flat File Generation Batch |
31 |
120 Rule Validation |
32 |
FATCA Entity US Indicia Status Updation |
33 |
LEP - Policy PIGS status Updation |
34 |
LEP - PIGS compliance batch check |
35 |
Policy - Reg28 Auto-Switch Generation |
36 |
Broker Commission Processing |
The EOD/ BOD activities applicable for Pension Administration module are as follows:
EODSEQUENCE |
Activity |
EOD/BOD |
5100 |
Migrate Party Role |
End of Day |
5101 |
Investment Account Closure |
End of Day |
5102 |
Data Merge |
End of Day |
5103 |
Balance update for locked-in accounts |
End of Day |
6001 |
Set latest rule for instrument |
Begining of Day |
6002 |
Update Instrument Fiscal |
Begining of Day |
6015 |
System date changes |
Begining of Day |
This section contains the following topics:
You can retrieve a previously entered record in the Summary screen, as follows:
Invoke the ‘EOD Maintenance Summary’ screen by typing ‘UTSEODMT’ in the field at the top right corner of the Application tool bar and clicking on the adjoining arrow button and specify any or all of the following details in the corresponding details.
Click ‘Search’ button to view the records. All the records with the specified details are retrieved and displayed in the lower portion of the screen.
Note
You can also retrieve the individual record detail from the detail screen by querying in the following manner:
You can perform Edit, Delete, Amend, Authorize, operations by selecting the operation from the Action list. You can also search a record by using a combination of % and alphanumeric value.
Note
TA to PAS module handoff can be scheduled using EOD Batch 2200 to hand off the allocated transaction to PA system.
You can modify the details of EOD Maintenance record that you have already entered into the system, provided it has not subsequently authorized. You can perform this operation as follows:
Click Save to save your changes. The EOD Maintenance Detail screen is closed and the changes made are reflected in the EOD Maintenance Summary screen.
To view a record that you have previously input, you must retrieve the same in the EOD Maintenance Summary screen as follows:
You can delete only unauthorized records in the system. To delete a record that you have previously entered:
An unauthorized EOD Maintenance record must be authorized in the system for it to be processed. To authorize a record:
When a checker authorizes a record, details of validation, if any, that were overridden by the maker of the record during the Save operation are displayed. If any of these overrides results in an error, the checker must reject the record.
After a EOD Maintenance record is authorized, it can be modified using the Unlock operation from the Action List. To make changes to a record after authorization:
An amended EOD Maintenance record must be authorized for the amendment to be made effective in the system. The authorization of amended records can be done only from Fund Manager Module and Agency Branch module.
The subsequent process of authorization is the same as that for normal transactions.
This section contains the following topics:
You can invoke the ‘Mini EOD Execution’ screen by typing ‘UTDEODMI’ in the field at the top right corner of the Application tool bar and clicking on the adjoining arrow button.
You can specify the following details:
AMC / Agent Code
Alphanumeric; 12 Characters; Optional
Specify the AMC or the agent code. Alternatively, you can select the AMC or the agent code from the option list. The list displays all valid AMC or agent codes maintained in the system.
AMC / Agent Name
Display
The system displays the AMC or the agent name of the selected AMC or agent code.
Fund ID
Alphanumeric; 6 Characters; Optional
Specify the fund ID. Alternatively, you can select the fund ID from the option list. The list displays all valid fund ID maintained in the system.
Fund Name
Display
The system displays the name of the selected fund ID.
Click ‘Execute’ button to execute mini EOD transactions.
Click ‘View Activity Status’ button to view the following details:
Click ‘View Log’ button to view the following details:
The system displays the following details:
Click ‘View Pre Mini EOD Results’ button to view the following details:
The system displays the following values:
On Emergency day, in mini-EOD the Emergency Day Processing activity should be scheduled and executed. This activity will be do the following:
Processing Emergency Holiday
The system runs mini-EOD to identify transactions which are impacted due to emergency holiday and other pending activities.
After declaring emergency holiday and subsequent system holiday, if any, the system executes mini EOD to log the transactions which are impacted. All system generated transactions (like Standing Instruction, Reinvestments etc.) will also be considered for emergency holiday processing.
The system will re-compute and log new transaction date, settlement due date, dealing date, payment date and price date. For unsettled allotted transactions, the system will re-compute settlement due date and payment date.
Activities involved in Emergency Day Processing
The activities involved in emergency day processing are as follows:
LEP Transaction Date Changes
The LEP transaction date changes are as follows:
Example
Policy Number |
Rule Effective Date |
Policy Start Date |
HSPOLICY01 |
10-Oct-16 |
10-Oct-16 |
If emergency holiday declared on 10-Oct-2016 then policy start date will be moved to next business day as follows:
Policy Number |
Rule Effective Date |
Policy Start Date |
HSPOLICY01 |
10-Oct-16 |
11-Oct-16 |
Dividend Date Changes
If freeze holding is completed, then the system will not move freeze holding date to next business date. The system will move the unprocessed dividends declared for the date to next business day.
Payment Date and Reinvestment Date will be moved to next business day. Dividend Declare Date and Freeze Holdings Date will be moved for non MMF funds.
Example 1: Non MMF Fund
Fund ID |
Dividend No |
Dividend Declare Date |
Freeze Holding Date |
Payment Date |
Reinvestment Date |
AFUND1 |
5 |
31-Oct-16 |
31-Oct-16 |
31-Oct-16 |
31-Oct-16
|
If emergency holiday declared on 31-Oct-2016, then the system will move dividend attributes to next business day as follows:
Fund ID |
Dividend No |
Dividend Declare Date |
Freeze Holding Date |
Payment Date |
Reinvestment Date |
AFUND1 |
5 |
1-Nov-16 |
1-Nov-16 |
1-Nov-16 |
1-Nov-16 |
Example 2:
Fund ID |
Dividend No |
Dividend Declare Date |
Freeze Holding Date |
Payment Date |
Reinvestment Date |
MMFFND |
575 |
31-Oct-16 |
31-Oct-16 |
31-Oct-16 |
31-Oct-16 |
If emergency holiday declared on 31-Oct-2016 then reinvestment date will be moved to next business day as follows:
Fund ID |
Dividend No |
Dividend Declare Date |
Freeze Holding Date |
Payment Date |
Reinvestment Date |
MMFFND |
575 |
31-Oct-16 |
31-Oct-16 |
1-Nov-16 |
1-Nov-16 |
Entity Commission Payment due date changes
If entity commission payment is due today, the same will be processed in next business day.
Broker commission payment date changes
Broker commission payment date will be moved to next business day
GO Cancellation
If Global Order is already generated on emergency day and if the same is not confirmed, then the system will reverse that global order.
Display
The system will display the status of the Function. The Function can be Running, Not Started, Aborted or Completed.
If the status is displayed as Aborted, you can change the status to Skip to allow the EOD to proceed with the rest of the functions.
This section contains the following topics:
To recall, the Pre-End of Day checks will indicate any activities that are pending, that must be executed and completed by the Fund Manager before the End of Day process can be run. These pending activities can be viewed in the Fund Manager Pre-EOD Processing screen.
The pre-EOD checks could indicate unauthorized transactions, missing fund maintenance or processing information such as fund prices, exchange rates, signing off branches, and so on. The Fund Manager must complete these activities before the End of Day processes can be run.
The list of Pre-EOD checks applicable for Pension Administration are as follows:
Serial Number |
Pre-EOD checks |
4000 |
Number of Unauthorised Maintenance Record |
4001 |
Number of Unauthorised Investment orders |
4002 |
Number of unauthorised withdrawal orders |
4003 |
Number of unauthorised Switch orders |
4004 |
Number of unauthorised payment clearing |
4005 |
Number of Currency Pairs for which Exchange Rates have not been maintained |
4006 |
Number of Users Logged In. |
4007 |
Number of orders due for hand off |
4008 |
Number of Future Dated Orders falling on holiday |
4009 |
Number of unauthorized Currency Records |
4010 |
Number of Unauthorized Holiday Records |
4011 |
Number of accounts with holdings beyond preservation age |
4012 |
Number of private investment accounts without bank details |
4013 |
List of parties with all address details expired |
4014 |
List of parties with no valid ID details |
4015 |
Parties with no role attached |
4016 |
Number of investors with no active investment accounts |
4017 |
Number of employees with no pension accounts attached |
4018 |
Number of uncleared payment instructions |
4019 |
Number of Uncleared Employer Payments |
You can use the ‘Pre-End of Day Check – Execute Pre EOD’ screen to perform the pre-EOD checks. You can invoke this screen by typing ‘UTDPREOD’ in the field at the top right corner of the Application tool bar and clicking on the adjoining arrow button.
In this screen click ‘Fetch Pre-EOD Count’ button and an information message will be displayed.
Click OK to return to the following screen in which the ‘View Pre-EOD Results’ and ‘Execute Pre-EOD’ button will be enabled..
In this screen, click ‘View Pre EOD Results’ button to display the activities that are pending completion before the end of day operations can be executed.
Click Ok to view the results in the Pre-End of Day Check – Execute Pre EOD screen:.
The system displays the following activities in this screen, which must be competed prior to the End of Day Operations:
To sign-off branches, use the Branch Sign Off option.
To authorize fund rules, use the Fund Rule Summary option.
To enter fund prices, use the Fund Price Maintenance option to enter the fund price, and use the Fund Price Summary option to authorize the same.
To authorize loads, use the Load Maintenance (Summary) option.
To authorize unit holder related Information, use the UH New Account (Summary) option.
To confirm redemption transactions, use the Confirm Redemption Transactions option.
To check unit holder related information, use the UH New Account (Summary) option.
To allocate IPO / subscription transactions, use the Allocation option.
To authorize/verify SI related details, use the SI related verify/authorization (Summary) option. For authorization/allocation use the corresponding transaction allocation for which the SI has been generated.
The system can proceed with End of Day Operations even if the redemption transactions are not confirmed.
The Branch Sign-Off and Fund Prices must be completed.
To execute the Pre-End of Day processes, click ‘Execute Pre EOD’ button. The system prompts you to back up the database before the process can run.
Note
If, for a broker, you have specified that payment should be held back, by checking the box ‘Hold Back Payment’ in the Broker Maintenance screen, a count of such brokers will be displayed in the Execute Pre-EOD screen.
If the emergency holiday details are maintained, system executes the mini-EOD batch ‘Emergency Day Processing’ before running the EOD.
However, EOD run is performed only after verifying that mini-EOD is executed and after all the entity level emergency holiday maintenances are done for a particular day.
You can view the following fields in this screen:
Serial Number
This is a number that indicates the particular activity. No two Activities can have the same Serial Number.
Description
Describes the various activities scheduled for EOD.
Mandatory
Indicates whether the activity is mandatory or can be skipped.
Note
The count of the mandatory activity shall be brought to zero before executing Pre-EOD or else system will throw up an error message at the time of EOD execution.
Count
Indicates the number of records for which the activity is pending completion. For instance, if Number of Unauthorized Fund Rules has the Count ‘1’, it indicates that there is one fund rule that needs to be authorized.
You can check against one of the programs in Pre-EOD check results grid and then click on the ‘Detail’ button to view the Pre-EOD details of the selected activity in the PRE-EOD Details screen:
The system displays the following details of the chosen activity in this screen:
This section contains the following topics:
You can use the End of Day Process screen to monitor the End of Day Activities (EOD) at Fund Manager.
Note
The End of Day process can be executed only if the Pre-End of Day processes at the Fund Manager have been successfully completed.
You can configure the BOD process to be executed immediately after the EOD process is completed, without manual intervention, by selecting the Include BOD Activities Also option, in this screen.
Use the End of Day Process menu option to monitor the EOD activities at the Fund Manager Branch. You can access this option by clicking the End of Day Process option under the End of Day Process menu item in the Batch Tab in Fund Manager.
To Run / Monitor EOD, follow the steps given below:
If EOD aborts, you can use the EOD Maintenance screen to change the status to Skip or Aborted and then continue with the EOD process.
Transaction Allocations
All the transactions that have been authorized and not yet allocated will be done by these functions.
For a fuller description of all the activities with respect to validation and allocation, refer the ‘Confirmation and Allocation’ chapter in the Fund Manager User Manual.
Summary Reports
All the summary reports that have been scheduled for the day are printed.
For further details on summary reports, refer to respective summary report generation in the ‘Reports’ chapter in this User Manual.
Contract Notes
The End of Day processes on a given business day execute an EOD job that prints contract notes in respect of transactions allocated on a given business day. The job checks to see if the contract notes have already been printed from the menu. If so, duplicates will be printed only if the ‘Duplicates Required’ option in the task parameters static information for the job has been enabled and set to ‘Yes’. If the Duplicates Required option has been set to ‘No’, duplicate contract notes are not printed by the EOD job. The Duplicates Required option is configured by the implementers at your installation, according to your requirement in respect of printing of duplicate contract notes.
If the contract notes have not been printed through the Confirmation Reports menu, the EOD job prints the contract notes.
Also, if allowed, as explained above, the EOD job prints transaction contract notes for transactions involving only those unit holders for whom the ‘File’ option has not been set as the preferred mailing mode in the unit holder account details. For transactions involving any unit holders for which the ‘File’ option has been set in the account details, the EOD job suppresses the printing of contract notes.
Fiscal Year Updating
The system checks for the Fiscal year period according the Fund Rules and resets the Fiscal year as the previous year is completed.
Transaction Enabled Status Updating
Check for the Transaction start and end period as per the Fund rule set up and enables or disables a given transaction for a given fund as and when required.
Unit Holder Counter Updating
Updates the unit holder Free Counter and Limit Counter for the given transaction of the fund. The unit holder is further allowed the same transaction for the fund as per the latest available Free Counter and Limit Counter details.
Audit Trail Report
Prints the Audit trail report for the day. The report is printed for the entire Audit trail Ids that are maintained through the Audit Trail Format Maintenance.
Generation of SI Reminders
Generates reminders for all the standing instructions that have been generated and not yet processed. The reminders are generated if the option is set in the SI setup. They are generated both before and after the SI. The period is as per the SI set up.
Purge Activities
The data that is to be purged is checked up with Purge Frequency and once the period is reached, the corresponding data is purged. The purge check is done for the following frequencies - Daily, Monthly and Yearly. Once the data is purged, the last purged date for the given detail is set to the Application date.
Auto Redemption Intimation
This will print intimation to all such unit holders whose unit holder balance is below the minimum balance specified for the fund. The unit holders will be given some time to increase their balance failing which their Units will be automatically redeemed.
This section contains the following topics:
You can use the Execute BOD screen to set up the system for the next day. The BOD functions can be executed along with the EOD functions, or separately, from the EOD / BOD Execute screen.
To configure the BOD process to be executed immediately after the EOD process is completed, without manual intervention, from the EOD /BOD Execution screen, by selecting the Include BOD Activities Also option in the Execute BOD screen.
This section contains the following topics:
You can use this screen for Branch Sign-On/Sign-Off. The system will display a list of Branches that have not signed-off for the day. Invoke the ‘Branch Sign Off/On Summary’ screen by typing ‘UTDBSNOF’ in the field at the top right corner of the Application tool bar and clicking on the adjoining arrow button.
The buttons indicates the sign-on / off status of a Branch.
Click on respective button to sign-on / off the branch. For an online branch, the system will display the list of unauthorized transactions as follows:
To proceed further with the End of Day activities, the following has to be done:
This section contains the following topics:
The End of Day Log Report will print a Log of the EOD functions’ status.
Refer the ‘Reports’ user manual for information about generating and printing a report.
When you initiate commissions processing in the Broker Comm Payment screen, the commission that is due to each broker is computed as on the current date. For each individual broker, any applicable tax (as defined for the broker category in the WHT Details or the overridden tax percentage specified in the Broker Maintenance) is deducted from the accrued commissions, to arrive at the actual commissions that would be paid out.
Tax is computed based on the commissions earned in the current tax year, which you have defined in the Defaults Maintenance. It is also deducted individually for each broker, independent of the broker hierarchy.
For brokers for whom payments are to be held back (as designated in the Broker Maintenance), commissions earned are paid out only if the commission amounts exceed the tax liability for that period, and the ‘hold back’ option has been revoked.
The payment of the commission accruing from a specific transaction is deferred till the payment instrument for the transaction is cleared. In the event of non-clearance of the payment instrument before the next commission payment date, the commission is processed and accrued, but the payment is deferred till the instrument is cleared. The accrued commission is paid out on the next commission payment date, provided the instrument is cleared.
This section contains the following topics:
The Entity Commission Payment process consolidates the accrued commission for each entity at a fund-level and the payment is processed based on the IDS options defined for each entity in the Entity IDS, with payment being made in the base currency of the fund. If no IDS options have been maintained, the default mode of payment for the entity is used for processing.
The Entity Commission Payment process can be executed either as a batch process as part of EOD. Invoke the ‘Entity Commission’ screen by typing ‘UTDECPYP’ in the field at the top right corner of the Application tool bar and clicking on the adjoining arrow button. Select the type of entity for which commission payment needs to be processed, and then select the ID of the entity.
Enter the details of the entity for which you wish to process the commission payments. Entity commission payments are processed only for those entities for which the Entity Payment Details have been maintained, even if entity commission has been accrued.
Entity Type
Alphanumeric; 1 Character; Mandatory
Specify the entity type.
Description
Display
The system displays the description for the selected entity type.
Entity ID
Alphanumeric; 12 Characters; Mandatory
Specify the entity ID.
Entity Name
Display
The system displays the entity name for the selected entity ID.
This section contains the following topics:
FC-IS provides a facility that enables you to extract data to FLEXCUBE Information Centre or FIC.
In order to extract data, you must set up the parameters that will govern the extraction of this data in the system. Use the FIC Setup screen in the Authorization Menu of the Fund Manager component to perform this task.
Once you have set up the parameters, you can use the Extraction Form to execute the extraction. To invoke the Extraction screen, click FIC Extraction under the FIC Extraction menu item in the Maintenance menu of the Browser.
You can specify the following fields in this screen:
Segment Name
Alphanumeric, Mandatory
Select the segment to which the source table belongs, from the options in the drop-down list. The source table is the table in which the data to be extracted must reside.
MIS Date
Date Format, Mandatory
The application date is displayed here by default, and all the tables that are pending extraction as on this date according to their frequency of extraction, are displayed in the Extraction Details section.
If you chose another date here, click the Show button to view all the tables that are pending extraction as on this date according to their frequency of extraction.
The MIS date can be changed to a value prior to the system application date. The date cannot be changed to a future date.
Extraction Details
When the MIS Date is specified, all the destination tables that are pending extraction are displayed in this section along with the following details:
This information is picked up by the system from the Destination Table Details Maintenance record for each of the destination tables, and displayed here.
If the extraction is to proceed, you must click the Extract button, and the data will be extracted to the output area. As and when a destination table is fully extracted, the table row will disappear from the list in the Extraction Details section. The system displays a confirmation message upon successful completion of the extraction.
Use the End of Day Process menu option to monitor the EOD activities at the Fund Manager Branch. You can access this option by clicking the End of Day Process option under the End of Day Process menu item in the Batch Tab in Fund Manager.
To run/ monitor EOD, follow the steps given below:
If EOD aborts, you can use the EOD Maintenance screen to change the status to Skip or Aborted and then continue with the EOD process.
In EOD Execution screen, on emergency day EOD/ BOD, the system will display the activities which are scheduled on emergency day process as ‘Yes’.
You can invoke this screen by typing ‘UTDEODEX’ in the field at the top right corner of the Application tool bar and clicking on the adjoining arrow button.
You can specify the following details:
EOD/BOD Activity
Optional
Select the EOD/ BOD activity from the drop-down list. The list displays the following values:
Click ‘View Activity Status’ button to view the following details:
Click ‘View Log’ button to view the following details:
Click ‘Execute’ button to execute EOD execution details.
Note
During the EOD execution, if emergency holiday has been declared on that day then the processes which are marked as Function Status as ‘Scheduled’ and Emergency Day Process as ‘Yes’ the system will execute only those processes on Emergency Day EOD execution.
On non-Emergency day, the system will execute all the processes which are marked as Function Status as ‘Scheduled’.
You can close the campaign code after expiry using ‘Campaign Closure’ BOD batch. During BOD, the system checks if any of the campaign whose campaign end date is greater than or equal to application date, then system will mark the campaign as closed.
Campaign Batch will archive campaign data as well for the campaign code.
This section contains the following topics:
The system provides a facility to monitor processes that are being run in the background during a current session. Such processes could typically be scheduled jobs or tasks, being run by the Scheduler Services. They are called asynchronous processes.
A typical example of an asynchronous process is the processing of dividend payment for many funds during one session.
To monitor the progress of asynchronous processes, the batch operator user can use the 'Process Status’ screen.
You can invoke this screen by typing ‘UTDPROST’ in the field at the top right corner of the Application tool bar and clicking on the adjoining arrow button.
You can specify the following details:
Module ID
Alphanumeric; 50 Characters; Optional
Specify the module ID in which the job was submitted.
User ID
Alphanumeric; 25 Characters; Optional
Specify the ID of the user that submitted the job.
From Date
Date Format; Optional
Specify the date range when the job was submitted.
To Date
Date Format; Optional
Specify the date range when the job was submitted.
Job Type
Alphanumeric; 50 Characters; Optional
Specify the ID of the job for which you want to view the progress status.
All jobs retrieved by the search operation are displayed in the lower grid portion, with their type, status, description and the name of the procedure being run.
The system displays the following details:
To view the details of the job, such as descriptions of errors, click the View button. The job details are displayed in the Asynchronous Processing Details screen.
To clear all asynchronous processing jobs, click the Clear All link in the Asynchronous Processing main screen.
This section contains the following topics:
You need to update the revised fund prices to process adjustments. The Guaranteed Funds batch process will process the adjustments due to price revisions for a period. This is done in the ‘Guaranteed Funds’ screen. You can invoke this screen by typing ‘UTDUFUND’ in the field at the top right corner of the Application tool bar and clicking on the adjoining arrow button.
You can specify the following fields in this screen:
Processing Type
Mandatory
Select whether the batch processing is Interim or Year End Processing from the drop-down list. The list displays the following values:
Processing Date
Date Format; Mandatory
Select the processing date from the adjoining calendar.
From Date and To Dates
Date Format, Mandatory
Enter the period for which the price revision is applicable.
Mock Processing
Optional
Check this box if you require the system to carry out a Simulation (Mock GF correction) run. The Simulation run is possible on an Interim as well as Year End basis.
The system uses the Mock GF Fund Price for its calculations during these runs. After the successful completion of a Simulation run, the system generates a 16- digit Batch number that you can use for reporting purposes. If you leave the box unchecked, the system treats the run as an Actual run and uses the Actual GF Fund Price.
Note
Click ‘Process’ button to execute the batch process. Consequently, the system will consider all transactions recorded during the mentioned period for Unit Holder – Policy- Fund combination. The system will store the following information from the impacted transactions:
The system then re-calculates and stores the units allotted, settlement account and unit price for all the relevant transactions.
Note
The system ignores adjustment subscriptions and adjustment redemptions done in the current fiscal year and balance transfer in transactions.
The formula used to compute difference in units for Subscriptions with transaction mode as amount is as follows:
The formula used to compute difference in units for Redemptions with transaction mode as amount is as follows:
The formula used to compute difference in units for Redemptions with transaction mode as Unit is as follows:
Depending on whether the batch processing is Interim/Year End, the system will generate the allotted subscriptions/redemptions as follows:
22nd Jan 2007 - S1 - UH1 - F1 - 1000 ZAR – 100 Units @ 10ZAR
First Interim: On 30th Mar 2007 the price is revised to 10.10 ZAR the transaction would be 1000/10.10 = 99.01 units. Now, the difference is 0.99 units.
Second Interim: On 29th Jun 2007 the price is revised to 10.15 ZAR the transaction would be 1000/10.15 = 98.52 units. Now, the difference 1.48 units but we have already subscribed for 0.99 units hence redeem only for 1.48 -.99 ➔ 0.49 units.
The EOD batch process ‘Process fund of funds investments’ is used to generate transactions from the main fund to the underlying funds. Reftype ‘FF’ identifies the Fund of Fund transactions generated by the system. The transactions are generated for the unit holder maintained in ‘fund linkage details’ section and the transaction currency will be the fund base currency of the main fund. This is applicable only for Hedge funds module.
For ‘Non-net’ transactions, during EOD, the system finds the sum of inflow amounts and sum of outflow amounts for all transactions allotted on that day, and generates a subscription and redemption transaction in the underlying funds accordingly.
For ‘net’ transactions, the system finds the (sum of inflow amount – sum of outflow amount) and generates either subscription or redemption transaction in the underlying funds.
Inflow amount considers subscriptions, switch ins, reversed redemptions and reversed switch outs that are allotted on the application date for the main fund.
Inflow amount = units allotted across all transactions * NAV as of the application date
Outflow amount considers reversed subscriptions, reversed switch ins, redemptions and switch outs that are allotted on the application date for the main fund.
Outflow amount = units allotted across all transactions * NAV as of the application date
If the transaction generation basis is ‘Non Net/Transaction Mode’, then during EOD the system find the sum of all amount based subscription and sum of amount based redemption transactions allotted on that day, and generates amount based subscription and redemption transaction in the underlying funds.
Units and percentage based transactions will be generated as amount based subscription and redemption transaction in underlying funds, in maintained ratio. The amount of the allotted transactions will be ‘Units allotted * NAV as of application date’.
Assume that JPMORG is a Fund of Hedge Fund. JFCHNF and JFHKDF are underlying hedge funds having percentages 50 and 40 respectively. Also, assume that 000000000272 and 000000000277 are the unit holder IDs for JFCHNF and JFHKDF respectively.
Transactions allotted on JPMORG as on 01/09/2009 (Assuming TBC is FBC, NAV is 10 and fund has no load)
Transaction Number |
Transaction Mode |
Transaction Value |
Transaction Amount |
SUB1 |
Amount |
1000 |
1000 |
SUB2 |
Amount |
2000 |
2000 |
SUB3 |
Unit |
100 |
1000 |
SUB4 |
Unit |
200 |
2000 |
RED1 |
Amount |
2500 |
2500 |
RED2 |
Unit |
50 |
500 |
Transaction Mode |
Value |
Total Subscription Amount |
6000 |
Total Redemption Amount |
3000 |
Total Unit Subscription |
300 |
Total Unit Redemption |
50 |
Total Amount Subscription |
3000 |
Total Amount Redemption |
2500 |
Net Transaction value |
3000 |
Transaction will be generated as given below
Transaction Generation Basis is ‘NET’
Fund ID |
Unit holder ID |
Txn Type |
Txn Mode |
Txn Value |
JFCHNF |
000000000272 |
SUB |
Amount |
1500 |
JFHKDF |
000000000277 |
SUB |
Amount |
1200 |
Transaction Generation Basis is ‘NON NET’
Fund ID |
Unit holder ID |
Txn Type |
Txn Mode |
Txn Value |
JFCHNF |
000000000272 |
SUB |
Amount |
3000 |
JFCHNF |
000000000272 |
RED |
Amount |
1500 |
JFHKDF |
000000000277 |
SUB |
Amount |
2400 |
JFHKDF |
000000000277 |
RED |
Amount |
1200 |
Transaction Generation Basis is ‘NON NET/TXN MODE’
Fund ID |
Unit holder ID |
Txn Type |
Txn Mode |
Txn Value |
JFCHNF |
000000000272 |
SUB |
Amount |
1500 |
JFCHNF |
000000000272 |
RED |
Amount |
1250 |
JFHKDF |
000000000277 |
SUB |
Amount |
1200 |
JFHKDF |
000000000277 |
RED |
Amount |
1000 |
JFCHNF |
000000000272 |
SUB |
Amount |
1500 |
JFCHNF |
000000000272 |
RED |
Amount |
250 |
JFHKDF |
000000000277 |
SUB |
Amount |
1200 |
JFHKDF |
000000000277 |
RED |
Amount |
200 |
The transactions that happen in a feeder fund are fed to the master fund based on the value of ‘Transaction Generation Basis’ (N-Net, O- Non Net) maintained at fund level for the percentage specified in ‘Fund linkage details’ section in ‘Hedge Fund Processing Rules’ screen.
The transactions from the feeder funds to the master fund are generated using the ‘Process master feeder investments’ batch process. Reftype ‘MF’ identifies the master feeder transactions generated in this batch.
If ‘Transaction Generation Basis’ is ‘N-Net’ basis then system posts the transactions as follows:
If ‘Transaction Generation Basis’ is ‘O-Non Net’ basis then system posts the following two transactions during EOD batch:
Total inflow amount considers subscriptions, switch ins, revered redemptions and reversed switch outs that are allotted on the application date for all the feeder funds.
Inflow amount = units allotted across all transactions * NAV as of the application date converted to master fund FBC using the default exchange rate, if the currency is different
Total outflow amount considers reversed subscriptions, reversed switch ins, redemptions and switch outs that are allotted on the application date for all the feeder funds.
Outflow amount = units allotted across all transactions * NAV as of the application date converted to master fund FBC using the default exchange rate if the currency is different.
A percentage of the inflow and outflow amounts, as maintained in the ‘fund linkage details’, is fed to the master fund.
Assume that JPMorgan Fund (JPMORG) is a master fund. JF Greater China Fund (JFCHNF) is a feeder fund, which invests 89% of its net assets in a unit of JPMorgan Fund (Master fund). JF Hong Kong Fund (JFHKGF) is another feeder fund, which invests 90% of its net assets in a unit of JPMorgan Fund (Master fund).
In the fund rules setup of JPMORG you can capture the split percentage details as follows, in ‘Fund linkage details’ section.
Feeder fund ID |
Fund Name |
Percentage |
JFCHNF |
JF China Fund |
89 |
JFHKGF |
JF Hong Kong Fund |
90 |
If an investment happens in JFCHN fund for 100 units, then an amount 890 (89% of the inflow amount) gets invested in JPMORG fund.
If an investment happen in JFHKGF fund for 100 units, then an amount 900 (90% of the inflow amount) gets invested in JPMORG fund.
Note
The above example assumes that both the master and feeder fund FBCs are same and without any loads at the master and feeder level. It also assumes an NAV of 10 for the funds.
If the feeder and master fund FBCs are different, then the feeder fund investment is converted into master fund FBC.
This section contains the following topics:
In service provider installations, if a new rule is maintained or an existing rule is modified at any of the Line of Business (LOB) schemas available, the same needs to be replicated to all available LOB schemas for that particular installation.
You can replicate the rules maintained in one LOB schema to all available schemas in ‘Refresh Rules’ batch screen.
You can invoke this screen by typing ‘UTDREFRU’ in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button.
You can specify the following details in this screen:
Refresh Option
Mandatory
Select any of the following refresh options:
Rule ID
Alphanumeric; 5 Characters; Optional
Specify the rule Id to be replicated to LOB schemas or select the rule Id from the option list provided.
Note
This is applicable only if you have selected ‘Specific’ as the refresh option.
Rule Description
Display
The description associated with the Rule Id selected gets displayed here.
Action
Optional
Select the option to indicate whether the rules should be refreshed during EOD or immediately. The following options are available in the drop-down list:
Click ‘Execute’ button to refresh the rules as per the options specified.
You can also use the EOD batch ‘Refresh PF Rules across LOB’ to refresh all available LOB schemas of a given service provider, whenever a new rule is created or existing rule is modified.
For more details on maintaining rules for performance fee calculation, refer the section titled ‘Maintaining Rules for Performance Fee Calculation’ in this user manual.
This section contains the following topics:
The US Indicia Check batch verifies the existing unit holder or entity records to check whether the UH or entity is 'US Indicia Available' or not. The batch classifies the UH and entity records based on this check. You can trigger the batch using ‘FATCA US Indicia Check’ screen. You can invoke this screen by typing ‘STDFATCL’ in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button.
Specify the following details:
Process Type
Optional
Specify the process type from the drop-down list. The list displays the following values:
Submit For
Optional
Select the submit option from the drop-down list. The list displays the following values:
This batch checks the following records:
If one of the following US Indicia is available for an entity, then the record will be marked as “US Indicia Available”.
FATCA status check batch is a mandatory BOD batch. It checks the existing unit holders, broker, customer, single entity and auth rep and marks them as 'Recalcitrant' or 'Compliant' based on the expiry status of proof documents.
If a standard document for any of the above entities has expired, the system changes the status of such entity from 'Compliant' to ‘Recalcitrant'.
If there are more than one documents maintained, the system checks the expiry status of each document. If any one document is expiring as of that day, the batch marks the entity as recalcitrant.US Indicia entity with status 'Pending Classification' may have 90 days lag maintained as part of system parameter. In case any such entity has not given the required set of document within the 90 days period, then this batch will change the status of the entity as 'Recalcitrant’.
Note
The 90 days lag is calculated based on the US Indicia status ‘Yes’.
The Due diligence process for pre existing account will be through batch process and the criteria for executing the process will be based on the Tax Compliance type, for instance, Common Reporting Standard, Source Entity ID, Tax Jurisdiction (if any country code is mentioned then the selected country code else all the country code maintained) and date. Following is the sequence batch processes to be followed for pre existing individual and entity accounts:
This section contains the following topics:
The due diligence process will scan all accounts opened on/before the effective date for the jurisdiction selected based on the tax compliance type. Once the system identifies indicia for the respective reportable jurisdiction, UH with Indicia is updated as ‘Yes’ and compliance status as Reportable.
For instance, the due diligence batch process will identify accounts opened on/before the execution date and identify indicia for the jurisdiction selected else ‘All’ jurisdiction maintained as part of Tax compliance setup will be applicable. If indicia is found for the jurisdiction/s, then the system updates the UH with indicia as Yes and compliance status as Reportable.
Due Diligence is a one-time process for a jurisdiction and this is operationally controlled process (there will be no system check if the process is executed multiple times in the system for the same input criteria).
If the batch is re- executed for a jurisdiction, then system will display an override message as ‘The batch is already executed for the jurisdiction selected, do you wish to continue’.
The system will identify the accounts with indicia status as Yes for the jurisdiction scanned and the compliance status will be set to Reportable. For instance, if indicia is found for Germany then the Tax jurisdiction will be Germany, with Indicia status as Yes and Compliance status as Reportable.
Before due diligence process if the UH is amended, then the system will trigger indicia check for such accounts while saving the amendment. Such account will be picked by due diligence batch but the batch will not make any change to such accounts as indicia are already identified for the account. If there are new indicia (single or multiple) identified for a new jurisdiction/s then a new record/s will be inserted.
If you classify such accounts through the Tax Compliance classification maintenance for a jurisdiction or set of jurisdiction before the batch execution then there will be no changes made to such accounts. If there are new indicia (single or multiple) identified for a new jurisdiction/s then a new record/s will be inserted.
If a new reportable country is added, then due diligence process will identify indicia for the new jurisdiction and insert a new row for the jurisdiction for which the indicia is identified.
The Diminimis batch process scan all accounts with Indicia status set to ‘Yes’ and Batch execution date (application date) should be greater than or equal to Diligence Date. The system will check the individual and corporate account limit will be checked maintained at Tax compliance setup.
For high value accounts, the system will mark Account value as High and Compliance status as Reportable. For low value accounts, the system will mark Account value as Low, and compliance status as Non Reportable. The Diminimis Yearly Check will be set to ‘Yes’.
Note
This is applicable only for low value accounts.
The system will scan all accounts with indicia status as ‘Yes’ for the reportable jurisdiction/s. Based on the due diligence date at Tax rule maintenance, this process checks for the account value with indicia set to Yes based on the date input. The date input parameter is operationally controlled.
The batch process will fetch output based on due diligence date, Indicia set to Yes and the individual and entity account value.
If the process date ≠ or < Due diligence date then the system will display an error message as ‘Batch process date to be = or > due diligence date’.
This process to be executed post the due diligence process which is again operationally controlled and there will be no system check on the sequence of execution.
If the batch is re-executed, then the system will display an override message as ‘The batch is already executed for the jurisdiction selected, do you wish to continue’.
The system will mark the accounts as high value if no limits are maintained. The account with indicia as yes and value greater than the defined value for the individual/corporate will continue to remain reportable until you make any changes at tax compliance classification maintenance or if there is any change in circumstance that trigger change in indicia, for instance, change in address etc before classification.
The input criteria to execute the ‘DIMINIMIS’ batch when a new reportable country is added (no change on batch sequence) and this process will not make any change to the account value which is already identified as part of the earlier ‘DIMINIMIS’ process. This will only change the compliance status.
The Diminimis Yearly batch scans for account with diminimus yearly status set to Yes. For the accounts identified with high value, the system will set Indicia to Yes, Compliancde Status to Reportable, Account value as High and diminimis yearly field will be unchecked.
The systme will re-scan the accounts marked with Di minimis yearly check for any change in account value (high /low) and accordingly will be marked reportable with value as high else the diminimis yearly check will continue with no change on account value. If the account becomes high value then the yearly check is removed.
This process should be executed post the ‘Diminimis batch’ which is operationally controlled and there will be no system check on the sequence of execution.
For the accounts where the value is less than the value for Individual and corporate, then Diminimis Yearly check will continue and next time the diminimis yearly batch is processed, the system will pick these accounts for processing.
The business logic sequence to run the process is as follows:
If you post the account marked with ‘Diminimis Yearly’ as Yes and post that the account is classified and if you re-execute the ‘Diminimis Yearly’ batch, the batch will remove the ‘Diminimis Yearly’ check and make changes to the account value. Any user classified values will be overridden by the batch.
There will be no change if a new reportable country is added for ‘DIMINIMIS Yearly’ process.
Validations
The system classifies the Unit holder as Indicia and is marked as reportable and the account value is’ High’ as identified by system. The Tax Compliance sub screen in UTDUH screen is updated with the indicia details and Tax jurisdiction details.
If you classify the account as non reportable at Tax Compliance Document Classification maintenance, then the over ridden details are updated back at UH level in the Tax Compliance sub screen in UTDUH screen.
The accounts which are identified with no indicia details through the Due Diligence batch undergoes modification then amendment of such Unit holder will trigger indicia. If indicia is found, then while saving, the details are updated for the UH, provided the UH is not classified through UTDCOMCL.
Batch process will always take precedence over user classified compliance status and not indicia status.
This section contains the following topics:
You can invoke Interest or Coupon Payment screen option by typing ‘UTDINPYM’ in the field at the top right corner of the Application tool bar and clicking on the adjoining arrow button.
You can specify the following details:
Fund ID
Alphanumeric; 6 Characters; Optional
Specify the fund ID. Alternatively, you can select fund ID from the option list. The list displays all valid fund ID maintained in the system.
Settlement Date
Date Format; Optional
Select the date of settlement from the adjoining calendar.
Reprocess
Optional
Select if the coupon or interest payment has to be reprocessed or not from the drop-down list. The list displays the following values:
This section contains the following topics:
You can process integration batch using ‘Integration Batch Process Screen’. You can invoke this screen option by typing ‘UTDINTBT’ in the field at the top right corner of the Application tool bar and clicking on the adjoining arrow button.
You can specify the following details:
BATCH
Alphanumeric; 8 Characters; Optional
Specify the batch process. Alternatively, you can select batch process from the option list. The list displays all valid batch process maintained in the system.
After specifying the batch details, click ‘Process’ button to process the integration batch.
This section contains the following topic:
You can process the swinging price for a fund using ‘Process Swinging Price’ screen. You can invoke this screen by typing ‘UTDSWGPR’ in the field at the top right corner of the Application tool bar and clicking on the adjoining arrow button.
You can specify the following details:
Fund ID
Alphanumeric; 6 Characters; Optional
Specify the fund ID. Alternatively, you can select fund ID from the option list. The list displays all valid fund ID maintained in the system.
After specifying the fund ID, click ‘Submit’ button. The system displays the following values:
This section contains the following topics:
You can use ‘Unitholder Balance Handling for US Accounts’ screen to process to report the UH balance for FATCA reporting. You can invoke this screen by typing ‘UTDUSBAL’ in the field at the top right corner of the Application tool bar and clicking on the adjoining arrow button.
You can specify the following details:
Date
Date Format; Optional
Select the processing date from the adjoining calendar.
Investor Type
Optional
Select the type of investor from the drop-down list. The list displays the following values:
FATCA Classification
Alphanumeric; 25 Characters; Optional
Specify the classification for which you want to process the batch. Alternatively, you can select FATCA classification from the option list. The list displays all valid FATCA classifications maintained in the system.
FATCA Fund Id
Optional
Select FATCA fund ID option from the drop-down list. The list displays the following values:
FATCA Status
Optional
Select one of the FATCA statuses from the drop-down list. The list displays the following values:
Submit For
Select if the batch needs to be submitted as online process or execute from the drop-down list. The list displays the following values: