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.
How to Reject a Result
Rejecting Breaches is straightforward; you can simply click the Reject button.
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 determined a Disclosure was not necessary and could be marked as rejected.
Below are different options users may select for a rejected Disclosure result:
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 general category can be used for any edge cases not covered above.
As a best practice, please ensure the correct category is selected at all times and comments are provided for the audit trail.
Resolving Accidental Rejection
If a result has been accidentally or otherwise falsely rejected, the status can be set back to Unactioned with the Set Back To Unactioned button. If you use Filing Manager, the associated filing will reappear as Unactioned shortly thereafter.
Historical Results
If this is not the latest result, you may need to verify any disclosure document submitted for any subsequent upload if the Last Disclosure Date is a required property for the disclosure. Given that your Last Disclosure Date has changed, you might need to rectify the data previously submitted to the regulator. Rerunning position files since this result was rejected may generate updated results.