Related provisions for SUP 10A.14.18
Table: Examples of how the other local responsibility function applies
Example |
Comments |
(1) ‘A’ is allocated local responsibility for one of a branch’s main business lines. A is also appointed to perform a PRA-designated senior management function for the same branch. |
A only needs approval to perform the PRA-designated senior management function. |
(2) ‘A’ is outside the branch’s management structure and A’s responsibilities for the branch are limited to setting overall strategy for the branch. A does not have responsibility for implementing that strategy. |
A is not performing the other local responsibility function. The reason for this is explained in SYSC 4.8.27G. SUP 10C.8.1R(2) is irrelevant to this example. |
(3) A small branch undertakes two business lines (wholesale lending and corporate investments). ‘A’ is head of wholesale lending and is also an executive director of the branch. ‘B’ is head of corporate investments and does not sit on the branch management committee but reports to it on corporate investments. The branch allocates local responsibility for these functions to A and B. Neither A nor B performs any other PRA or FCA-designated senior management functions. |
A only needs approval to perform the executive director function3. B needs approval to perform the other local responsibility function. |
(4) A branch does not have a Head of Internal Audit. ‘P’ is allocated local responsibility for internal audit in relation to that branch. |
P needs approval to perform the other local responsibility function. However, if P has already been approved to perform another PRA or FCA designated senior management function, then P will not be performing the other local responsibility function. |
(5) ‘A’ is appointed to perform the executive3director function. The same branch also allocates local responsibility for some branch functions to A. |
A only needs approval to perform the executive3director function. |
(6) ‘A’ is approved to perform the other local responsibility function. Later, A is appointed to perform the executive3director function for the same firm. |
A requires approval for the other local responsibility function when A is first appointed. When A is later approved to perform the executive3director function, A stops performing the other local responsibility function. The firm should use Form E to apply for approval for A to perform the executive3director function. |
(7) ‘A’ is appointed to perform: (a) the compliance oversight function for one firm (Firm X) in a group (which may or may not be a relevant authorised person); and (b) a function coming within the scope of the other local responsibility function for another firm (which is a third-country relevant authorised person) in the same group (Firm Y). |
A needs approval to perform the compliance oversight function for Firm X and the other local responsibility function for Firm Y. |
(8) ‘A’ is appointed to take on some functions that come within the other local responsibility function. Later, A is appointed as chief risk officer. |
On A’s first appointment, A will need to be approved to perform the other local responsibility function. On being approved as chief risk officer, A stops performing the other local responsibility function as being chief risk officer is a PRA designated senior management function. |
(9) ‘A’ is appointed as an executive director. A then resigns and takes up a job with the same firm coming within the other overall responsibility function. |
On A’s first appointment, A will need to be approved to perform the executive3director function. A will need to get approval to perform the other overall responsibility function before A gives up being a director. |
Note: Local responsibility is explained in SYSC 4.8.10R (Third-country relevant authorised persons: Allocation of responsibilities) |
Table: Examples of how the need for dual FCA and PRA approval in relation to PRA-authorised persons is reduced
1Example |
Whether FCA approval required |
Whether PRA approval required |
Comments |
(1) A is appointed as chief risk officer and an executive director. |
No. He is not treated as performing the executive director function. |
Yes |
Chief risk officer is a PRA-designated senior management function. A’s functions as a director will be included in the PRA-designated senior management function. To avoid the need for FCA approval, A’s appointment as director should not take effect before PRA approval for the chief risk officer role. |
(2) Same as example (1), except that A will take up the role as an executive director slightly later because the approval is needed from the firm's shareholders or governing body. |
No |
Yes |
The answer for (1) applies. The arrangements in this section apply if the application to the PRA says that A will start to perform the potential FCA governing function around the time of the PRA approval as well as at that time. |
(3) Same as example (1) but the application to the PRA does not mention that it is also intended that A is to be an executive director. |
Yes, to perform the executive director function. |
Yes |
SUP 10C.9.8R does not apply if the application for PRA approval does not say that A will also be performing what would otherwise be an FCA governing function. |
(4) A is to be appointed as chief executive and an executive director. |
No. A is not treated as performing the executive director function. |
Yes |
Being a chief executive is a PRA-designated senior management function. A’s functions as a director will be included in the PRA controlled function. |
(5) A is appointed as chief risk officer. Later, A is appointed as an executive director while carrying on as chief risk officer. |
Yes, when A takes up the director role. The executive director function applies. |
Yes, when A takes up the chief risk officer role. |
SUP 10C.9.8R does not apply because, when the firm applied for approval for A to perform the PRA chief risk officer designated senior management function, there was no plan for A also to perform the executive director function. |
(6) A is appointed as an executive director. Later, A takes on the chief risk officer function and remains as an executive director. |
Yes, when A is appointed as director. The executive director function applies. |
Yes, when A takes up the chief risk officer role. |
When A is appointed as chief risk officer, A is still treated as carrying on the executive director function. A retains the status of an FCA-approved person. |
(7) A is appointed as chief risk officer. A then stops performing that role and for a while does not perform any controlled function for that firm. Later, A is appointed as an executive director with the same firm. |
Yes, when A is appointed as an executive director. The executive director function applies. |
Yes, when A takes up the chief risk officer role. |
SUP 10C.9.8R does not apply because there is no current PRA approval when A is being appointed as a director. |
(8) A is appointed as an executive director and chief risk officer at the same time. Later, A gives up the role as chief risk officer but remains as an executive director. |
No, on A’s first appointment (see example (1)). But when A gives up the role as chief risk officer, FCA approval is needed to perform the executive director function. Form E should be used. The application should state that it is being made as a result of A ceasing to perform a PRA-designated senior management function. Form A should be used if there have been changes in A’s fitness (SUP 10C.10.9D(4)) |
Yes, on A’s first appointment. |
When A stops being a chief risk officer, A stops performing a PRA-designated senior management function. However, being an executive director requires FCA approval. A does not have that approval because A did not need it when A was first appointed. The combined effect of SUP 10C.9.8R and the relevant PRA rules is that the firm has three months to secure approval by the FCA. During that interim period, A keeps the status of a PRA approved person performing the director element of the PRA chief risk designated senior management function - which is included in that function under relevant PRA rules. The relevant PRA rules say that, during this transitional period, A is still treated as performing the PRA chief risk designated senior management function and SUP 10C.9.8R says that, for as long as A is performing a PRA-designated senior management function, A does not perform the executive director function. |
(9) A is appointed as the chief finance officer and an executive director at the same time. Later, A switches to being chief risk officer while remaining as an executive director. |
No |
Yes |
The arrangements in SUP 10C.9.8R continue to apply, even though A switches between PRA-designated senior management function after the PRA's first approval. |
(10) A is appointed chief risk officer and an executive director. A goes on temporary sick leave. A takes up his old job when he comes back. |
No, neither on A’s first appointment nor when A comes back from sick leave. |
Yes |
SUP 10C.9.8R still applies on A’s return because A does not stop performing either the PRA's chief risk function or what would otherwise have been the executive director function just because A goes on temporary sick leave. |
(11) A is appointed to be chairman of the governing body and chairman of the nomination committee at the same time. |
No. A does not need approval to perform the chair of the nomination committee function. |
Yes, on first appointment. |
Being chairman of the governing body is a PRA-designated senior management function. Therefore, the answer for example (1) applies. |
2(12) ‘A’ is to be appointed to perform the Head of Overseas Branch PRA-designated senior management function (SMF19) for a third-country relevant authorised person. A is also an executive director of that firm’sUKbranch. |
No. A is not treated as performing the executive3director function. |
Yes |
A’s functions as a director will be included in the PRA controlled function. |
Note: The relevant PRA rules can be found in Chapter 2 of the part of the PRA rulebook called ‘Senior Management Functions’ |
The table below sets out the format, reporting frequency and due date for submission in relation to regulatory returns that apply to authorised payment institutions and small payment institutions.
(1) |
(2) |
(3) |
(4) |
(5) |
Type of firm |
Return |
Format |
Reporting Frequency |
Due date |
Authorised Payment Institution Capital Adequacy Return |
FSA056 (Note 1) |
Annual (Note 2) |
30 business days (Note 3) |
|
Payment Services Directive Transactions |
FSA057 (Note 4) |
Annual (Note 5) |
1 month (Note 3) |
|
Note 1 |
When submitting the completed return required, the authorised payment institution must use the format of the return set out in SUP 16 Annex 27A D. Guidance notes for the completion of the return are set out in SUP 16 Annex 27B G. |
|||
Note 2 |
This reporting frequency is calculated from an authorised payment institution'saccounting reference date. |
|||
Note 3 |
The due dates are the last day of the periods given in column (5) of the table above following the relevant reporting frequency period set out in column (4) of the table above. |
|||
Note 4 |
When submitting the completed return required, the small payment institution must use the format of the return set out in SUP 16 Annex 28A D. Guidance notes for the completion of the return are set out in SUP 16 Annex 28B G. |
|||
Note 5 |
This reporting frequency is calculated from 31 December each calendar year. |
The table below sets out the format, reporting frequency and due date for submission in relation to regulatory returns that apply to electronic money issuers that are not credit institutions.
(1) Type of electronic money issuer |
(2) Return |
(3) Format |
(4) Reporting Frequency |
(5) Due date (Note 4) |
Balance sheet |
FSA059 |
Half yearly (Note 3) |
||
Income statement |
FSA060 |
Half yearly (Note 3) |
||
Capital requirements |
FSA061 |
Half yearly (Note 3) |
||
Safeguarding |
FSA062 |
Half yearly (Note 3) |
||
Supplementary information |
FSA063 |
Half yearly (Note 3) |
||
No standard format |
Annual (Note 3) |
|||
Small electronic money institutions (Note 2) |
Return |
FSA064 |
Half yearly (note 5) |
|
Total electronic money outstanding @ 31st December |
FSA065 |
Annual (Note 5) |
1 month |
|
No standard format |
Annual (Note 5) |
|||
(a) the Post Office Limited (b) the Bank of England, the ECB and the national central banks of EEA States other than the United Kingdom (c) Government departments and local authorities (d) credit unions (e) municipal banks (f) the National Savings Bank |
No standard format |
Half yearly (Note 6) |
||
Note 1 |
When submitting the completed returns required, the authorised electronic money institution must use the format of the returns set out in SUP 16 Annex 30A to SUP 16 Annex 30E. |
|||
Note 2 |
When submitting the completed returns required, the small electronic money institution must use the format of the returns set out in SUP 16 Annex 30F to SUP 16 Annex 30G. |
|||
Note 3 |
Where the authorised electronic money institution's reporting frequency is half yearly or annual, this field is calculated from the authorised electronic money institution'saccounting reference date. |
|||
Note 4 |
The due dates for returns are the last day of the periods given in column (5) of the table above following the relevant reporting frequency period set out in column (4) of the table above. |
|||
Note 5 |
The reporting frequency in relation to FSA065 is calculated from 31 December each calendar year. Otherwise, where the small electronic money institution's reporting frequency is half yearly or annual, this field is calculated from the small electronic money institution'saccounting reference date. |
|||
Note 6 |
This is calculated from 31 December each calendar year. |