Overview
When it comes to Breaches and Disclosures, there is an option to Reject the Result. Please see the Results Workflow article for more details on the types of actions available.
Rejecting Breaches are straightforward, you can simply mark it as Rejected.
Rejecting Disclosures requires additional information, such as categorization and the reason for rejection. This ensures that the audit trail correctly and accurately reflects investigations that took place to determine that a Disclosure was not necessary and could be marked as rejected.
As per the list and the screenshot, below are different options clients may select:
Incorrect data in the input file: This category should be selected if the disclosure is triggered due to incorrect data in the positions file. This can be an incorrect denominator value that brought you over the threshold or incorrect listings on the market, which triggered a jurisdiction incorrectly.
Rule does not apply: This category should be selected if the disclosure is identified as not applicable, i.e., Takeover GB, where the rule doesn't apply for certain triggers, or filing at this level does not apply.
Incorrect Regulatory Data: This category should be selected if the disclosure is triggered by incorrect regulatory data, such as Takeover data. If this happens, please include as much detail in the comments as possible so FundApps can contact the regulatory data providers to fix the issues, if applicable.
Different Rule Interpretation: This category should be selected if the disclosure is triggered by FundApps' interpretation of the regulation differing from yours. If so, please provide detailed views and references to the asophere memo if applicable.
Other: this is a general category that can be used for any edge cases not covered above.
As best practices, please ensure the correct category is selected at all times, and comments are provided for the audit trail.