Overview
This article explains the various actions you may need to take after a positions file is uploaded.
Assignee and Status
Results can be assigned to a particular person and given a status depending on the result type. After a position file is uploaded, all results are assigned the status of Unactioned. Each action shown below will change the status of the result and update the incident in the task list.
For example, Generate Documents changes the status and task to Disclosing. The status of any result can be found on the right-hand side of the screen or by clicking on the result itself.
Actions
The table below shows which action can be applied to the most common result types and its impact.
Note: After taking one of the actions below (Reject, Verify, etc.), the result type will remain visible for information purposes.
Action | Disclosures | Warnings | Breaches | Description |
Assign | ✔ | ✔ | ✔ | It assigns the incident to the selected user. The incident's status will remain Unactioned until the selected user clicks Investigate. |
Reject | ✔ |
| ✔ | Changes the status from Unactioned to Rejected and closes the incident. However, the status cannot be reverted back to Unactioned but can be changed to Verified, Disclosing, or Filed by taking the appropriate actions (see below). |
Verify |
|
| ✔ | This changes the status of a breach from Unactioned to Verified and closes the incident. Once Verified, the status can still be Rejected at a later date. |
Generate Document | ✔ |
|
| This button sets the status to Disclosing and generates the disclosure document. This can be changed to Rejected or Filed. |
Mark as Filed | ✔ |
|
| It sets the status to Filed and closes the incident. Once set, the status is irreversible and will be marked as such permanently. Hence, we recommend only setting the status after the disclosure has been sent out. Please note that a disclosure will still appear under the results when it has been filed. |
Close |
| ✔ |
| This sets the status of a warning to Closed and closes the incident. Once set, the status cannot be reverted and will be permanently set. |
Set Back To Unactioned | ✔ |
|
| This sets the status of a Disclosure to Unactioned after being assigned. Once set, the user can reassign the incident to someone else. |
Comments
Comments are a good way to communicate with other members of your team within FundApps about a specific result. Suppose any of the above actions are selected by mistake. In that case, we recommend making a comment to keep a strong audit trail and provide context to the situation for future reference.
Additionally, if a Filed disclosure contains a mistake that needs to be fixed critically, please re-upload the positions file with a new Quantity. The old disclosure will be replaced with a new one, which can be correctly marked as filed.
Attachments
Adding attachments to a result is good practice for audit purposes (internally for the compliance team and externally when FundApps support is investigating a query or if a regulator is reviewing your compliance procedures).
Attachments can be added when filing a disclosure using the Upload file and confirm button or at any other point using the Attach button.
We do not support XLSM files; however, we support the other types of Excel files: XML, XLSX (will remove macros), and XLS (supports macros). The other file types supported as attachments to a result are CSV, PDF, DOC, DOCX, TXT, PPT, PPTX, TIF, PNG, GIF, ZIP, EML, and MSG.