CONRED Sch 2 Notification requirements
Handbook reference |
Matters to be notified |
Contents of notification |
Trigger event |
Time allowed |
1CONRED 2.4.9R |
Information on the total number of scheme cases; opted-in scheme cases, and investments in Arch cru funds |
(1) total number of scheme cases; (2) The number of such investments resulting from the regulated activities for a customer in CONRED 2.1.3R; and the number of such investments falling outside the scheme with an explanation of the reason why, in each case; (3) the total number of opted-in scheme cases. |
None: notification required in all cases |
Until 29 July 2013 |
CONRED 2.9.2R |
Information on the number of opted-in scheme cases; completed and incomplete templates and the results of such; the total number of redress cases; the total number of redress determinations sent to consumers; the total number of consumers paid redress and the amount of such; and the total amount of redress unpaid to date. |
(1) the total number of opted-in scheme cases; (2) the total number of completed templates; (3) the total number of incomplete templates, with an explanation as to why the templates have not been completed; (4) the total number of redress cases; (5) the total number of redress determinations sent to consumers; (6) the total number of consumers paid redress to date; (7) the total amount of redress paid to date; and (8) the total amount of redress unpaid to date. |
None: notification required in all cases |
Until 9 December 2013 |
3Handbook reference |
Matters to be notified |
Contents of notification |
Time allowed |
|
CONRED 3.2.7R(1), (1A) and (4) |
Outcome of the financial resilience assessment in CONRED 3.2.2R |
Outcome of the financial resilience assessment in CONRED 3.2.2R |
Before the end of 27 May 2022 or 28 February 2023, and immediately if the outcome changes |
|
That N and CL, as calculated under CONRED 3.2.4AR and CONRED 3.2.6AR, are both zero |
That N and CL, as calculated under CONRED 3.2.4AR and CONRED 3.2.6AR, are both zero |
Promptly |
||
Where the firm wishes to obtain prior express consent from the FCA for payment of dividends or LLP members drawings |
(a) |
the value of the proposed dividend(s); |
In advance (express consent required) |
|
(b) |
the date on which the firm intends to pay the proposed dividend(s); |
|||
(c) |
the recipients of the proposed dividend(s); |
|||
(d) |
a clear statement of the quantified effect of the payment of the proposed dividend(s) on the firm’s regulatory capital position; |
|||
(e) |
a copy of the firm’s latest management accounts; |
|||
(f) |
an express confirmation that the payment of the proposed dividend(s) is lawful under applicable company or partnership law and insolvency law; |
|||
(g) |
demonstration that the dividend(s) will be paid in connection with services provided for or on behalf of the firm by a natural person; and |
|||
(h) |
demonstration that the timing of the proposed payment and the value of the dividend(s) are consistent with the historical pattern of the payment of dividends for equivalent purposes over the immediately preceding 12 months. |
|||
Transactions in the ordinary course of business which do not fall within CONRED 3.3.5R Any contract change with connected persons which could result in payments above the de minimis threshold |
(a) |
an explanation of the transaction or contract change; |
At least 15 business days in advance, unless urgent situation |
|
(b) |
an explanation of the quantifiable impact on the firm’s financial resilience assessment under CONRED 3.2.2R; |
|||
(c) |
an explanation of why the firm considers that the transaction or contract change occurs in the ordinary course of business and is therefore permitted; |
|||
(d) |
reference to any comparable historic payments or contract changes which support the firm’s view that this occurs in the ordinary course of business; and |
|||
(e) |
in the case of a notification on an urgent basis under CONRED 3.3.10R(2), an explanation of the nature of the urgency and why it has not been possible to comply with the normal 15-business day notification requirement in CONRED 3.3.10R(1). |