What the FCA means by cannot delegate
The FCA says a firm that outsources critical functions stays fully responsible for its obligations. What that means for IT, and what changes in 2027.
If your firm is authorised by the Financial Conduct Authority and you use an outside IT provider, you have probably been told that you cannot delegate your regulatory responsibility. It is a phrase that gets repeated more often than it gets explained, and the explanation matters, because it decides what you need to ask for, what you need to keep, and what you need to do before 18 March 2027.
This guide sets out what the rule actually says, which parts of the FCA’s rulebook apply to a firm of your size, and what the two new regimes starting in March 2027 will and will not require of you. It is written for managing directors, finance directors and operations directors rather than compliance specialists. If you want the wider picture of how IT fits a regulated firm’s plans, our IT support for financial services page covers the service side.
One thing to be clear about before anything else. We do not give legal or regulatory advice, and nothing you buy from an IT provider makes your firm compliant with the FCA. What follows describes the technical controls, the evidence they produce and the questions worth asking a supplier. Whether a particular rule applies to your firm, and whether you are meeting it, is a judgement for you and your compliance adviser.
The sentence that does the work
The phrase comes from the FCA itself. On its outsourcing and operational resilience page, under risk management, the FCA states that your firm is responsible and accountable for all the regulatory responsibilities that apply to its outsourcing and third party service arrangements, and that firms “cannot delegate any part” of that responsibility to a third party.
Behind that plain-English statement sits a rule. SYSC 8.1.6R in the FCA Handbook says that a firm outsourcing functions the FCA calls critical or important remains fully responsible for discharging all of its obligations under the regulatory system. Outsourcing, in the FCA’s sense, means an arrangement where someone outside your firm performs a process, service or activity that your firm would otherwise carry out itself.
It then sets four conditions. The outsourcing must not result in senior personnel delegating their responsibility. Your relationship and obligations towards your clients under the regulatory system must not change. The conditions you have to meet in order to be authorised, and to stay authorised, must not be undermined. And none of the other conditions of your authorisation may be removed or modified. There is a parallel version of the rule, SYSC 8.1.6-AR, for firms the Handbook calls common platform firms, with the same four conditions framed against UK law on markets in financial instruments.
Read those four conditions together and the meaning is narrow and practical. You can hand over the work. You cannot hand over the answerability for it. If your IT provider misconfigures something and client data leaks, the FCA’s conversation is with you, not with the provider.
Which of these rules apply to your firm
This is where a lot of writing on the subject goes wrong, so it is worth being careful.
The outsourcing requirements in SYSC 8.1 bind some firms as rules and guide others. For a common platform firm they are rules, with “must”. For other firms the FCA says in SYSC 8.1.1A G, SYSC 8.1.5A G and SYSC 8.1.11A G that they should take account of the same provisions as if they were guidance, reading “should” where the rule says “must”. The practical difference is smaller than it sounds. A firm that ignores guidance of this kind still has to explain itself, and the responsibility sentence in SYSC 8.1.6R is not softened for anybody.
The operational resilience regime in SYSC 15A applies to a defined list of firm types, and it is a list rather than a size test. The FCA’s policy statement PS21/3 names them: banks, building societies, PRA-designated investment firms, insurers, Recognised Investment Exchanges, enhanced scope SM&CR firms, and entities authorised and registered under the Payment Services Regulations 2017 or the Electronic Money Regulations 2011. If your firm is not in one of those categories, the specific duties to identify important business services and set impact tolerances are not yours. An important business service is one whose disruption would cause intolerable harm to clients or risk to market integrity. An impact tolerance is the maximum disruption to it you would be willing to accept. Those duties came into force on 31 March 2022, and the deadline for being able to stay within your tolerances, and having made the investment to do so consistently, was 31 March 2025.
A smaller firm can be in scope. An authorised payment institution or e-money institution is in scope whatever its headcount, and so is an enhanced scope SM&CR firm. The point is that scope follows your permissions and your SM&CR category, not your size, and the place to check it is the FCA’s own list. Our guide to financial services IT strategy sets out the wider sequencing once you know where you stand.
One distinction is worth holding on to, because it is where most of the muddle comes from. The FCA does apply proportionality to outsourcing and third party obligations: it says it expects firms to be risk-based and proportionate, taking into account the nature, scale and complexity of their operations when meeting those obligations. That is a statement about how much work a given firm has to do. It is not a route into the operational resilience regime. Proportionality changes the depth expected of you within rules that apply to you. It does not extend SYSC 15A to a firm outside the listed categories, and it does not reduce the outsourcing responsibility to a firm inside them.
It is also worth knowing that the FCA, the Bank of England and the Prudential Regulation Authority have begun jointly overseeing the largest suppliers to the financial sector under a separate critical third parties regime, aimed at suppliers whose failure could threaten confidence in the UK financial system. If one of your major suppliers is caught by it, that is not a transfer of your own position. The FCA says plainly that the regime does not change the accountability of firms, their boards and their senior management for staying operationally resilient and for complying with the existing outsourcing and operational resilience rules, including where they rely on third parties.
Everything in the next three sections applies much more widely, which is why it deserves more attention than it usually gets.
What is critical or important, and what is not
The FCA’s test, in SYSC 8.1.4R, is whether a defect or failure in performing the function would materially impair your continuing compliance with the conditions and obligations of your authorisation, or your other obligations under the regulatory system, or your financial performance, or the soundness or continuity of your services.
For most authorised firms, the IT that carries client records, client communications and payment instructions will meet that test comfortably. The question is worth asking function by function rather than supplier by supplier, because one provider may be doing something critical and something trivial under the same contract.
The Handbook is also helpful about what does not count. SYSC 8.1.5R says that, for a common platform firm and without prejudice to the status of any other function, the following are not critical or important: advisory and other services that are not part of your regulated activity, including legal advice, staff training, billing services and the security of your premises and people; the purchase of standardised services, including market information services and price feeds; and the recording and retention of relevant telephone conversations or electronic communications covered by SYSC 10A.
That last exclusion catches people out, because call recording feels critical. It is covered by its own rules in SYSC 10A instead.
There is a prior question worth separating out, because it is where a lot of confusion starts. Not every third party arrangement is outsourcing at all. The FCA’s own examples of things that are not outsourcing include buying office supplies and furniture, cleaning, vending machines, statutory audit, legal representation in court, the purchase of standard off-the-shelf software, market information services, and global network infrastructures such as the card schemes.
That does not put those arrangements outside the rules. The FCA is explicit that an arrangement falling outside the definition of outsourcing may escape the specific outsourcing requirements while remaining within the scope of its rules and guidance on governance, risk management, and systems and controls. Principle 3 and SYSC 1.2.1 require a firm to take reasonable care to organise and control its affairs responsibly and effectively, with adequate risk management systems, and that reaches a firm whatever it has or has not outsourced. So the useful question is not “is this outsourcing” but “what could this supplier’s failure do to us”.
Two related points. The FCA treats the provision of cloud services for the delivery of important business functions as a form of outsourcing, and potentially material outsourcing at that, so a Microsoft 365 arrangement is unlikely to sit outside this conversation. And if you outsource to another company in your own group, including a parent or sibling outside the UK, the FCA expects the same requirements to be met as for an unconnected supplier, and says firms should not treat intra-group arrangements as less risky or as exempt.
What the FCA expects you to do about it
SYSC 8.1.8R sets out twelve things a firm must take the necessary steps to secure when it outsources a critical or important function. Eight of them bear directly on an IT arrangement.
The provider must have the ability, capacity, organisational structure and any legally required authorisation to do the work reliably and professionally. It must carry out the work effectively and in line with applicable law, and you must establish methods for assessing how it is performing and for reviewing the service on an ongoing basis. The provider must properly supervise the outsourced work and manage the risks that come with it. You must effectively supervise the outsourced functions yourself and keep enough in-house expertise and resource to do so. The provider must tell you about any development that could materially affect its ability to perform. You must be able to terminate the arrangement, with immediate effect where that is in your clients’ interests, without harming the continuity or quality of what you provide to clients. You, your auditors and the FCA must have effective access to data about the outsourced activities, and to the provider’s premises where that is needed for proper oversight. And you and the provider must have a contingency plan for disaster recovery, with periodic testing of backup facilities, where the nature of what has been outsourced makes that necessary.
SYSC 8.1.9R then deals with the paperwork. The respective rights and obligations go in a written agreement, and you keep your rights to instruct, to terminate, to information, and to inspect and access books and premises. The provider may only sub-outsource, meaning pass part of the work to someone else again, with your written consent.
The common thread is that these are ongoing duties, not a procurement exercise. A due diligence file from the year you signed does not evidence the words “on an ongoing basis”. This is the practical reason a written service level agreement matters more in a regulated firm than elsewhere, and ours is published rather than sent on request, at our service level agreement.
There is also a notification step that is easy to miss. SYSC 8.1.12G points at SUP 15.3.8G and says a firm should notify the FCA when it intends to rely on a third party for operational functions that are critical or important, on a continuous and satisfactory basis. In other words, the FCA expects to hear about the arrangement before it starts, not after something has gone wrong.
Detection, because you are expected to know
Nothing in the outsourcing rules tells you to buy a particular security product. What they do is make it very hard to argue that you were effectively supervising an arrangement you had no visibility of. The FCA’s own list of what can cause an operational incident is short and unglamorous: a cyber attack, a system change that does not go to plan, and disruption to a third party.
The first of those is where most firms spend their money, and it is also where the gap between having a tool and knowing what happened sits. Detection matters here for a specific reason rather than a general one. The reporting duties described in the next section are triggered by what an incident does, and you cannot judge that, or report it inside a day, if nobody was watching. Our managed detection and response service provides 24x7x365 monitoring by a security operations centre, watching for signs of compromise and acting on them, and it is included in Lanmark Total.
Incident reporting, and what changes on 18 March 2027
This is the part of the FCA’s work on third parties that reaches the widest group of firms, and it is the part least often written about.
On 18 March 2026 the FCA published PS26/2, its final rules and guidance on operational incident and third party reporting, after consulting in CP24/28 from December 2024 to March 2025. The rules come into force on 18 March 2027, and the FCA has described the 12 months in between as preparation time. The FCA, the Prudential Regulation Authority and the Bank of England have built a single regime, so an affected firm makes one submission rather than three.
Who it covers. Operational incident reporting applies to all firms with a Part 4A permission, meaning the standard permission to carry on regulated activities in the UK, as well as payment service providers, UK Recognised Investment Exchanges, registered trade repositories and registered credit rating agencies. The FCA’s own summary is that it will apply to almost all firms it regulates. If you hold an FCA permission, you should assume this one is yours.
What triggers a report. From March 2027 you must report an operational incident that meets one or more thresholds by posing a risk: of causing intolerable harm to consumers from which they cannot easily recover; to the safety and soundness of your firm or other market participants; or to market stability, market integrity or confidence in the UK financial system. Reports go in on a single form through Connect, the FCA’s online submission system, whichever regulator the report is for. Most FCA solo-regulated firms, meaning firms the FCA supervises alone rather than jointly with the PRA, will submit a short standard report. A smaller group of enhanced reporting firms must provide more, update the FCA on significant changes to an incident while it is live, and finalise the report once it is resolved. Incident reporting that used to sit under the Payment Services Regulations has been folded into the same framework.
Until then, the existing route still applies. The FCA says to keep following the current process until March 2027. Its non-exhaustive list of indicators that an incident may be material is worth pinning up: material disruption to the financial services you provide, a large number of customers affected, unauthorised access to your information systems, significant loss of data, and the unavailability or loss of control of your IT systems. If you judge an incident material, you tell your named FCA supervisor, or use the firm notification form under SUP 15 if you do not have one, and you tell the PRA as well if you are dual-regulated.
The FCA is not the only call to make. Its own guidance points firms towards the National Cyber Security Centre for cyber incidents, Report Fraud where the incident looks criminal, and the Information Commissioner’s Office for a personal data breach, noting that the ICO requires that within 72 hours of becoming aware of it where feasible. Those clocks run at the same time as each other, which is the main reason the first hour is worth rehearsing in advance. We have written a first-hour checklist at what to do in the first hour after a suspected breach.
Material third party arrangements, and the register
The second half of PS26/2 is narrower, and this is the distinction most summaries blur.
From 18 March 2027, firms in scope must tell the FCA when they enter into a material third party arrangement, or significantly change an existing one, and must report annually by submitting a register of those arrangements. The FCA will say when the submission window opens, expects that to be at the end of the 12-month run-up, and has said firms will then have 90 calendar days to file.
An arrangement is material where its disruption or failure could cause intolerable harm to your clients, pose a risk to the soundness, stability, resilience, confidence or integrity of the UK financial system, or cast serious doubt on your ability to satisfy the threshold conditions, or to meet your obligations under the Principles or under SYSC 15A. Notably, the new rules reach a wider range of arrangements than before, whether or not they would be classed as outsourcing in the older sense.
Who is in scope is a closed list: enhanced scope SMCR firms, banks, designated investment firms, building societies, Solvency II firms, CASS large firms, UK Recognised Investment Exchanges, authorised electronic money institutions and authorised payment institutions, and consolidated tape providers.
If your firm is not on that list, the FCA’s position is that you continue to meet your existing obligations, including Principle 11, and it has confirmed those obligations will still apply to firms outside the new regime after 18 March 2027. Compliance with Principle 11 includes disclosing anything relating to your firm that may have a serious regulatory impact, under SUP 15.3.8, and that in turn covers notification on critical, important or material outsourcing under SYSC 8.1.12 and SYSC 13.9.2.
So the honest summary for a smaller authorised firm is this. The register is probably not yours. The incident reporting almost certainly is. And the notification duty on critical outsourcing has been yours all along.
What this guide is not
It is not advice on whether any of the above applies to your firm, and it is not a compliance service. Lanmark does not advise on FCA obligations and no product or service we sell makes a firm compliant with the FCA. The rules in this guide bind authorised firms, not their IT suppliers, and we are not an FCA-authorised firm.
What an IT provider can do is narrower and still useful. It can put the controls in place, run them, and hand you the evidence of what they do, so that you and your adviser can make the judgement with something solid underneath it. Where this guide quotes a rule, check it against the FCA Handbook rather than against us.
What to ask a provider, and what to keep
If you are appointing or reviewing an IT provider and you hold an FCA permission, these are the questions that map onto the conditions above. They are deliberately written so that a vague answer is obvious.
- Which of the functions you perform for us would you call critical or important, and why?
- What will you give us, in writing, that lets us assess your performance on an ongoing basis rather than once at signing?
- What will you tell us, and how quickly, if something changes at your end that affects your ability to deliver? Put a timescale on it.
- What are your target recovery times for our most important systems, and when did you last test them rather than document them?
- What happens to our data, and to the service, if we terminate? Who moves it, how long does it take and what does it cost?
- Will you let us, our auditors and the FCA have access to data about what you do for us, and to your premises if that is needed for oversight?
- Do you sub-contract any of this, and will you agree not to do so without our written consent?
- Who at your end is accountable, by name and role?
And four things worth keeping, because they are what an ongoing-oversight question is answered with: your written agreement and its schedules, the record of what you checked before you appointed the provider, your periodic service reviews with dates and attendees, and the results of your last recovery test including what failed.
Recovery testing is the one firms most often skip, and it is also the one that turns a plan into evidence. Backup is the starting point. Our Microsoft 365 backup service keeps an independent copy of mailboxes, SharePoint, OneDrive and Teams data, which is what makes a restore test possible in the first place.
Where Lanmark fits
We provide fully managed IT support, priced per user per month so the bill does not move with the number of incidents. Lanmark Total is from £55 to £65 per user per month ex VAT on a 12-month term, and includes 24x7x365 managed detection and response and security operations centre cover, identity threat detection and response, Microsoft 365 backup, and an annual IT plan and budget. We are a Microsoft Direct CSP, which means we source Microsoft licensing directly rather than through an intermediary. We hold Cyber Essentials, recently renewed.
Our service desk runs Monday to Friday. 24x7 support is available on request. We say this plainly because a firm thinking about recovery times needs to know it rather than discover it, and because the 24x7x365 part of the service above is security monitoring, which is a different thing from a service desk.
On your line-of-business systems, tell us which ones you use and we will confirm what we can support. We would rather give you a straight answer on a named system than imply we support everything.
What we will not do is tell you that buying our service satisfies an FCA obligation. We will answer the questions in the list above in writing for your firm, in terms you can put in front of your compliance adviser, and you can judge the answers against your own position.
Two related reads. The Cyber Security and Resilience Bill will tighten supplier due diligence across sectors, not just financial services, and is worth horizon-scanning now. And Cyber Essentials certification is a reasonable baseline to ask a supplier about, including us.
If you want to go through your own position, call 020 7123 4910 or book a free IT review. We will tell you plainly if we think you do not need to change anything.
Common questions
Does outsourcing IT move any regulatory responsibility to the provider?
No. The FCA's outsourcing rule is explicit that a firm outsourcing critical or important operational functions remains fully responsible for discharging all of its obligations under the regulatory system, and that the outsourcing must not result in senior personnel delegating their responsibility. The provider carries contractual obligations to the firm. The regulatory obligations stay with the firm and its senior managers.
Is our IT support a critical or important function?
It depends on what it holds up. The FCA's test is whether a defect or failure in performing the function would materially impair the firm's continuing compliance with its authorisation conditions or its other obligations under the regulatory system, or its financial performance, or the soundness or continuity of its services. For most firms, the systems that carry client records, client communications and payment instructions will meet that test. A standalone service that touches none of those may not.
What happens on 18 March 2027?
Two new FCA regimes start. Operational incident reporting applies to almost all FCA-regulated firms, including every firm with a Part 4A permission, with a single reporting form submitted through Connect. Separately, a narrower set of firms must notify the FCA of new or significantly changed material third party arrangements and submit an annual register of them. Both were published in PS26/2 on 18 March 2026 with a 12-month run-up.
Do we have to keep a register of our IT suppliers?
Only some firms do. The FCA's register requirement from 18 March 2027 applies to enhanced scope SMCR firms, banks, designated investment firms, building societies, Solvency II firms, CASS large firms, UK Recognised Investment Exchanges, authorised electronic money and payment institutions, and consolidated tape providers. Firms outside that list continue under their existing obligations, including Principle 11, and the FCA has said those obligations keep applying after March 2027. Whether your firm is on the list is a question for you and your compliance adviser.
What should we be able to show about our IT provider?
In practice, four things: that you checked the provider could do the work before you appointed it, that you review how it is performing on an ongoing basis rather than once at signing, that your written agreement keeps your rights to information, inspection, instruction and termination, and that you have tested what happens when something fails. The FCA's conditions are about ongoing oversight, not a one-off due diligence file.
Where to go next
About this guide
Written by Lanmark, Lanmark Limited, 36 Basepoint, Victoria Road, Dartford, Kent DA1 5FS. Published .
Book a free IT review.
In about half a day we look at what you have, what it costs and where the risks are, and give you a red, amber and green (RAG) report. We tell you plainly if you do not need to change anything.
Book a free IT review