Skip to main content

Functional requirements

Functional requirements
The file is imported in Fee Distribution mode. Therefore the calculation version in the agreement calculation must refer to this fee model to manage the fee amounts and fee base amounts imported 
The Fee Raterate ( 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 

 

 

. If the import is supposed to be a correction the external reference and file name need to match the initially provided. 
Both fee amounts and fee base amount (often relates to AuM or AuA) can be positive or negative amounts. Negative amounts are aimed to lower a fee entitlement or a correction. The intention is however not to start paying instead of invoicing.  (TBC how we do today for real estate )
 
Back to top