Functional requirements
| Functional requirements |
| The file is imported in Fee Distribution mode. Therefore the calculation version in the agreement must refer to this fee model to manage the fee amounts and fee base amounts imported |
| The Fee rate ( initially not part of the import) has been added to the template as it can be useful for some scenarios and at a later stage if we are enhancing the detail pages of statements (not in 2026 scope). It is preferrable to use the fee rates in FSC in relation to the AuM/AuA or fee amount and do the calculation via the software so that there is complete reporting available, |
| The import is working in a delta mode. That means that every new file which does not refer to the same external reference, fee date, subservice, portfolio, product combination etc as a previous import is deemed to be ADDED.If corrections need to be made, the user needs to refer to the same data set within a line and the amount entered for the correction will then be overwrite the existing number.
|
|
Both fee amounts and fee base amount (often relate to AuM or AuA) can be positive or negative amounts. Negative amounts are aimed to lower a fee entitlement or a correction. If for a sub service both positive and negative amounts are provided, there is a netting off. For business cases where a fee needs to be fully deducted from other fee entitlements (e.g.Viridium), the user needs to create a dedicated sub service for the fee deduction and import negative numbers. In that case the sub service with the negative fee amount will be balanced off against the other sub services. In case the balance is then negative, the user needs to apply a minimum constraint of Zero to avoid an invoice with a negative amount
|
| The possible values to be used as portfolio source system are AA for alternative assets and IC for institutional clients, This is just to avoid any data conflicts between both areas. |
|
The file naming convention is as follows: IC_AA_YYYYMMDD_<placeholder>.xlsx where IC_AA_ is a fixed element which must always be used. YYYYMMDD_ is for the data of the file upload (can be another date but that would be confusing for the user) <> is a placeholder for some personalisation of the file.. The user can put some useful reference here to be able to understand what the content is.
Examples of naming: IC_AA_20260716_InstClientsIlliquidAssetsfilefromXY.xlsx IC_AA_20260716_AA_ProjectSplitElefant.xls IC_AA_20260716_ICAnlagegitter.xls
|
|
Column B ( identification) will be combined during the import with the fee date and the subservice code. Example Column A = Fee Date :31.12.2025 Column B = Identificatiiodon: AlphaIndustries Column F = SubServiceCode: AdmFee will during the import be combined to 311225_AlphaIndustries_AdmFee so if the following quarter end the fee date is 31.03.2026, the reference will be 31032026_AlphaIndustries_AdmFee.
This is done so that the users may save a template and just replace the dates and amounts from file. |
|
Period from and to must be filled out in the template as the information is used in the invoice documents. |
|
The fee date together with the invoice frequency of the agreement will define to which period the invoice is linked to in the software. Example a fee date of 31.12.2025 will be linked to
Independent from the software linking this to the quarter as mentioned above, the user can steer via the Period from and Period to settings, what period should appear on the invoice itself. Note: What happens for SCDimport that we reconfigure as Fee Distr import |