...
So, the issuers of the financial products deliver EMT files (which may be aggregated by suppliers like MFEX and then forwarded on to the intermediaries) which is imported to this application. The content in the EMT files rarely change so when conducting calculations of costs and charges for the end customers the last EMT file import data is used.
Broker Ex Posts
Within costs and charges the intermediary also has to show how much kickback that might have been received by the intermediary and to know this a file can be imported to this application in the section called Broker Ex Posts where the csv file has to have the following columns with these exact headers and being delimited by semicolon:
ISIN | The ISIN code of the financial instrument. |
DistributorKickBack | The percentage kickback received by the intermediary in decimal format. This means that 0.5 % should be inputted like 0.005. |
AdvisorKickBack | The percentage kickback received by the financial advisor from the intermediary as a total value of the fund fee. If the advisor received half of the kickback from the distributor from what the distributor received from the producer in the prior column it would mean 0.25 % and should be entered like 0.0025. |
PeriodStartDate | This is the start date from when this kickback schedule should be active and the application will use the schedule for the correct period in the calculation of cost and charges. |
PeriodEndDate | This is the end date from when this kickback schedule should be active and the application will use the schedule for the correct period in the calculation of cost and charges. |
Example file to use as a template:
| View file | ||
|---|---|---|
|
| Info |
|---|
See the section Distributors producer cost if you have a need to show this data too. |
Another prerequisite to starting the calculations is that the relevant transaction types from BFS has to be imported. Since custom transaction types may be used this step should be conducted together with Bricknode staff.
...