EBA Non-ICT Guidelines: What UK Firms Need for Exit Plans...

Picture a third-party risk committee at a UK banking group with an EU subsidiary. Next on the agenda is an outsourced loan servicing arrangement.

The supplier’s staff handle borrower calls, arrears letters, and reconciliations. On paper, it is a non-ICT service. In practice, all of that work runs on the supplier’s own platform.

For the EU entity, the committee has to decide whether the arrangement falls under DORA or the EBA’s new non-ICT guidelines. For the UK entity, that question never comes up. The PRA only wants to know one thing: would the exit plan work?

Both paths end in the same place. The exit plan depends on software the firm does not control. Few firms have tested whether that software could be recovered.

This guide covers what the EBA now expects, why the UK reaches the same expectation by a different route, and how to back your most important exit plans with verified evidence.

What the EBA guidelines change

The European Banking Authority published its final Guidelines on the sound management of third-party risk regarding non-ICT services (EBA/GL/2026/09) on 18 September 2026. They replace the 2019 Guidelines on outsourcing arrangements. The scope is now all third-party arrangements, not just outsourcing.

The guidelines apply to EU banks, most investment firms, payment and e-money institutions, issuers of asset-referenced tokens and certain mortgage creditors. Firms will have two years to review existing arrangements that support critical functions.

Three points matter most for continuity planning.

  1. They align with DORA. The EBA expects one consistent approach to third-party risk across ICT and non-ICT services.
  2. Exit plans must be tested. Plans for critical functions should be realistic, feasible and, where appropriate, tested. They must cover supplier failure, not just a planned exit.
  3. Paperwork is not enough. The EBA is clear that formal assessments alone do not show a service is under control. Firms must be able to check and challenge it themselves.

Why this matters in the UK

The EBA guidelines do not apply to UK-authorised firms. They still matter here, for five reasons.

  1. The UK does not split ICT and non-ICT.
    PRA SS2/21 treats all outsourcing and third-party arrangements under one framework. UK firms never have to classify a hybrid service before planning its exit. They go straight to the practical question: if this supplier disappears, can we keep the function running? That is the question supervisors will test on both sides of the Channel.
  2. Stressed exit is the UK version of supplier failure.
    SS2/21 asks firms to plan for two kinds of exit. A non-stressed exit is planned. A stressed exit follows the supplier’s failure or insolvency. The EBA now asks EU firms to plan for supplier failure in the same way. In a stressed exit, there is no handover and no transition period. What you secured in advance is your exit plan.
  3. Operational resilience now needs evidence.
    The transition period under PRA SS1/21 and FCA PS21/3 ended on 31 March 2025. Firms should now be able to stay within impact tolerances for their important business services. Supervisors want proof that plans work, not descriptions of how they would. Where a service depends on a supplier’s software, a verified rebuild is one of the clearest forms of proof. This applies to banks, insurers, payment and e-money firms and fintechs alike.
  4. The Critical Third Parties regime is not limited to ICT.
    The UK Critical Third Parties regime gives the PRA and FCA direct oversight of suppliers that are critical to the UK financial sector. Designation depends on systemic importance, not on whether the service is technology. Designation also does not shift responsibility away from the firms using those services. Each firm still owns its exit risk.
  5. FCA-only firms and UK suppliers are affected too.
    FCA solo-regulated firms apply the SYSC 8 outsourcing rules to critical functions. Payment and e-money firms have similar requirements. UK suppliers to EU banks face a different effect. Their EU clients will review contracts against the new guidelines, including audit rights, transition periods and exit support. Expect requests for software escrow and Technical Verification. Suppliers with a verified deposit already in place will find those conversations much easier.

To see how PRAXIS supports UK firms and their suppliers, visit software escrow for UK financial services.

The hybrid service problem

During the EBA consultation, firms asked how to treat hybrid services. These are services that are mainly non-ICT but depend on technology to deliver. The EBA’s answer was that each firm decides for itself.

That leaves a gap. Many services classed as non-ICT run on the supplier’s own software:

  • A loan servicer or collections agency using its own case management platform.
  • A claims or payments back office working in bespoke workflow software.
  • A KYC or document processing provider using in-house tools.
  • A fund administrator whose reports come from a proprietary calculation engine.

If the staff leave, you can hire new ones. If the platform disappears, the function stops. The data and business logic inside it are often the hardest things to replace.

An exit plan that covers people and contracts but ignores the software is not realistic under the EBA guidelines. It is not a credible stressed exit under SS2/21 either.

What “tested” really means for an exit plan

The EBA asks firms to set objectives, roles and success criteria for each exit plan. Contracts for critical functions should include a transition period, during which the supplier keeps working while you move the service.

That works in a planned exit. In a supplier failure, the transition period may never happen. Staff may be gone, systems switched off, and administrators focused on creditors. You can only rely on what you secured and checked in advance.

The EBA also sets a useful test for evidence. If you rely on a supplier’s certification or audit report, it should be current and should test whether key controls actually work.

Apply the same test to software escrow. An escrow agreement is a contractual control. It does not show whether the deposit is complete, current, or buildable. Only verification does.

For more on securing that right in the contract, read why verification rights are the escrow clause that matters most.

Five steps to a verified exit plan

Step 1: Map the software behind each critical service
Start with your register of third-party arrangements. For each critical function, or important business service in UK terms, note the software it relies on. Record who owns it, where it runs, and how it is delivered. This often uncovers platforms that were missed in due diligence, including those run by subcontractors.

Step 2: Choose the right protection
If the software is installed or licensed, source code escrow keeps the code and build materials available to you. If it is hosted, SaaS Continuity protects the application, environment, and data so the service can be restored. Automated Escrow pulls deposits directly from the supplier’s repositories on a set schedule, so escrow keeps pace with the live service.

Step 3: Match verification to criticality
PRAXIS Technical Verification works to a full rebuild standard. The aim is proof that the deposit can become working software again. Each level builds on the last:

      • Level 1, Deposit Index and Accessibility: confirms what was deposited and that it can be opened.
      • Level 2, Inventory and Analysis: reviews the contents and identifies dependencies and gaps.
      • Level 3, Remote Compile Evaluation: confirms the source code compiles into a working build and documents the tools needed.
      • Level 4, Simulated Release: rebuilds and deploys the application in a test environment, as in a real release.

Levels 1 and 2 are the foundation. For most hybrid services, Level 3 Remote Compile Evaluation is the right evidence point. It proves the code builds and shows what a new provider or in-house team would need. For the most critical services, or where a supervisor is likely to test a stressed exit closely, Level 4 Simulated Release gives the fullest proof.

Step 4: Set success criteria that verification can prove
Make some exit criteria technical and measurable. UK firms can tie them to the impact tolerance of the service. For example:

      • The code compiles from the escrowed materials alone.
      • All third-party libraries and licences needed for the build are identified.
      • A competent team new to the code could follow the build documentation.
      • The time, skills and environment needed for a rebuild are known and fit within impact tolerance.

A verification report that answers each point becomes evidence for internal audit, the board or a supervisor.

Step 5: Re-test when things change
Both regimes expect firms to reassess arrangements after material change. Software changes constantly, so a two-year-old verification says little about today’s release. Plan an annual audit as standard. Add a fresh Level 3 or Level 4 after major releases, supplier restructuring or a new subcontractor. Infinite Retention keeps every past deposit, so you can track changes and roll back if a new deposit has problems.

For a wider testing routine, see our practical checklist for testing vendor protections before you need them.

One verification pack for SS2/21 and the EBA guidelines

UK groups with EU entities do not need two sets of evidence. One deposit, verified to a full rebuild standard, can support:

  • A stressed exit plan under PRA SS2/21.
  • Your ability to stay within impact tolerance under UK operational resilience rules.
  • A tested exit strategy under the EBA guidelines.

One pack, read against each regime, saves duplicated work across risk, procurement and compliance. It also gives every supervisor the same clear answer.

Escrow and SaaS Continuity secure the materials. Technical Verification proves they can be rebuilt. PRAXIS does not make firms compliant with any regulation, but it supports the evidence firms need for credible, tested exit plans. Our SOC 2 certification gives audit teams confidence in how deposits are handled. All-inclusive pricing means you can extend verification across your register without unexpected costs.

If your register includes services where the people can be replaced but the platform cannot, talk to PRAXIS about Technical Verification for UK and EU exit plans.

FAQs

They are the EBA’s final guidelines (EBA/GL/2026/09), published on 18 September 2026, setting out how EU financial firms should manage and exit non-ICT supplier arrangements, replacing the 2019 Outsourcing Guidelines.

Not directly, but they apply to EU entities within UK groups and will shape what EU clients ask of their UK suppliers.

It is an exit that follows the failure or insolvency of a supplier, which the PRA expects firms to plan for alongside a planned exit.

DORA covers ICT suppliers, the EBA guidelines cover non-ICT suppliers, and firms are expected to manage both consistently.

It is a service that is mainly non-ICT but depends on technology, such as the supplier’s own software, to deliver it.

If the service runs on the supplier’s own platform, an exit plan that cannot recover that software will not hold up in a supplier failure.

It confirms the deposited source code compiles into a working build and documents what a new team would need.

At least once a year, and again after major releases, supplier restructuring or other material changes.

Glossary of Terms

A business that provides a service to a financial firm under a contractual arrangement.

A function whose disruption would seriously affect a firm’s finances, services or ability to meet its authorisation, defined in line with DORA.

A service that is mainly non-ICT but depends on technology, such as the supplier’s own software, to deliver it.

A documented plan for leaving a supplier, through termination or supplier failure, without serious disruption.

The PRA’s supervisory statement on outsourcing and third-party risk management, which covers all supplier arrangements without separating ICT and non-ICT.

An exit that follows a supplier’s failure or insolvency, where the supplier’s cooperation cannot be assumed.

The maximum disruption, including maximum duration, that an important business service can tolerate under UK operational resilience rules.

A supplier designated by HM Treasury whose services to the UK financial sector are directly overseen by the PRA and FCA.

A PRAXIS Technical Verification level that confirms deposited source code compiles into a working build and documents the build process.

A PRAXIS service that protects a hosted application, its environment and its data so the service can be restored if the provider fails.

Praxis Editorial Team

Praxis Editorial Team Author

Chris Smith is the Founder and CEO of PRAXIS Technology Escrow and a recognized leader in software and SaaS escrow with more than 20 years of industry experience. He pioneered the first automated escrow solution in 2016, transforming how escrow supports Agile development, SaaS platforms, and emerging technologies.

Leave a Comment