Holdings File
Minimum Requirements
The holding file should ideally contain the following details
* Scheme Name is optional
** Sedol is preferable as it is unique per instrument. ISIN is used to populate Disclosure Reports, therefore it would be ideal to have both present in the portfolio holdings file.
Manual Setup Requirements
The holding file should ideally contain the following details for manual Security / Derivative set-up:
* Where standard tickers are used, we will not require the above derivative data.
Note:
For bonds, we suggest dirty price and values.
Forward FX should enable us to see both legs of the forward FX – either on one line or two.
Security / Market Data File
The security file should ideally contain the following details;
* Terminology for these fields can be found in the “Global Disclosures Data Requirements & Terminology” Document.
Trades File
For most Disclosures Rules, the Disclosure requirement can adequately be identified from a movement in Quantity of the Position and hence the Holdings Position file.
However, for some Rules and / or Report Production, there may be a need to monitor against Trades.
For example, for UK Takeover Rule 8, we can use Positions to identify Opening Disclosures and Dealing Disclosures, but the Form will need populated (manually or by FundWare) with details of Trades.
If clients wish to upload Trades, then the file should contain the following fields:
NAV File
The NAV file is a simple file containing the official NAV of the fund. The following columns are required: