Download Transactions User Manual

2. Select the exchange rate source to be used, in the Exchange Rate Source field.
3. Click the Calculate button. The system obtains the applicable exchange rate for the
application date and computes the equivalent of the transaction value in the fund base
currency. This value is displayed in the Amount in Fund Base Currency field. The applied
exchange rate is also displayed in the Applied Exchange Rate field.
If the transaction value is specified in units or percentage of holdings, then the prevalent price
for a consolidation transaction on the transaction date is used to compute the amount of the
transaction, and the same is converted into the fund base currency equivalent.
4. Select the mode in which the transaction request was communicated, in the
Communication Mode field.
For check redemption transactions, the communication mode selected must be ‘MMF Check’.
You can view the projected allocation details only for funds in which the ageing policy is FIFO
(first-in, first-out) or Transaction Receipts. If the prices are not available for redemption
transactions on the transaction date, the latest available price is picked up for allocation.
When you do so, the system temporarily saves the transaction into temporary stores in the
database and gives it a unique key string. The system then performs a ‘mock’ temporary
allocation, and displays the details of the same in the Allocation Projection screen. The
following allocation details are displayed:

The Fund ID and the ISIN Code

The Product ID

The number of units allocated, in the Units field.

The Unit Price for the transaction, as on the date of the temporary allocation.

The total load amount, in the Load Amount field.

The Gross and Net Amounts in fund base currency

The Settlement Amount in the transaction currency
Dilution Levy Processing
To arrive at the dilution levy breach limit the inflow breach factor is considered. (Fund Corpus
* inflow Breach Factor < Net Amount in FBC). Dilution Levy limit breach is validated against
the gross transaction amount. If the gross transaction amount exceeds the dilution levy
breach limit, then a warning message is displayed by the system. The dilution levy breach limit
amount can be overridden at the transaction level. The overridden value is considered only if
the transaction attracts dilution levy.
An EOD batch computes the aggregated net transaction amount at unit holder, fund and
transaction type level. This batch is schedules before the allocation process. If the gross
aggregated amount for Unit Holder, Fund and Transaction type combination is identified
breaching, then a dilution levy fee is applied on all transactions of that fund, Unit Holder, and
transaction type combination.
4.6.15.4 Specifying Details in Other Section
During transaction entry, the system defaults the settlement date by considering the payment
lag defined for the fund in the Transaction Processing Rules. The settlement date is
computed as (Transaction Date + Payment Lag), and displayed in the Settlement Date field.
You can override the computed settlement date and specify the required date.
If you have defined a different trade cycle for the fund in the ‘Override Trade Cycle Date’
screen and the transaction falls within the override period mentioned in this maintenance, the
system will default the settlement date from the maintenance.
4-57