Properties Required to Set Up a Portfolio or Entity

Properties used within the FundApps system vary in importance. This is also the case when it comes to Portfolio properties. This article describes the properties displayed under the General Information tab in the edit/create portfolio screen and details which are required for setting up a portfolio/entity. 


Id (Required): This the unique key given to each portfolio or entity and is required for infrastructure purposes. It is important that the PortfolioId is unique within the corporate structure. This Id is matched against the positions file when actually sending positions through to FundApps, see: Introduction to the XML File.

Name (Required): This is the portfolio/entity name that will be displayed in the portfolio screen. Contrary to the Id, this name does not have to be unique.

Currency (Required): This is the base currency of the portfolio and can be selected from the drop down list provided when clicking the input box.

Company (Required): This property displays the company the portfolio or entity lies under. In most cases this will be the name of the FundApps environment. E.g. if your URL is, then this value would be BombayCapital. The value will only have an effect if information barriers are setup internally within certain companies. If there are such visibility restrictions within your company, please get in touch with the FundApps team.

Inception Date (portfolios only): The date a fund/account was launched.

Liquidation Date (portfolios only): If a fund/account is liquidated/closed it is not possible to simply delete it from the system as there will be results attached to the portfolio and that would create a discontinuity. To make sure that a portfolio is not just acting as noise within the Portfolio screen, the Liquidation date should be entered in this property, which will take the portfolio out of the Active Funds view and put it into the Liquidated view filter. If a portfolio is active, this property should be left blank.


Was this article helpful?
0 out of 0 found this helpful
Share article