Markdown Editor

Third-Party Risk Register Template (Non-ICT, EBA/GL/2026/09)

Scope, classification and exclusions, critical function test, para 61 and 62 fields, worked register, due diligence, contracts, exit plans, notices

Finance, Investment & AccountingFullEBA/GL/2026/09 (non-ICT third-party risk, 18 September 2026)thirdpartyriskregisternon

How to use: Use it when a bank, investment firm, payment or e-money institution keeps its register of non-ICT third-party arrangements under the EBA Guidelines that replace the 2019 outsourcing guidelines. Fill the classification and critical or important function assessment first, then the register fields, reusing DORA register identifiers. The main pitfall is leaving out arrangements that are not outsourcing but still support a function.

Preview

Third-Party Risk Register for Non-ICT Services: [Financial entity or group name]

Register of all third-party arrangements for non-ICT services, and its design record, for credit institutions, investment firms, payment and e-money institutions and the other financial entities addressed by the EBA Guidelines on the sound management of third-party risk regarding non-ICT services (EBA/GL/2026/09, final report of 18 September 2026). It covers scope and classification, the critical or important function assessment, the register fields of paragraphs 61 and 62, the worked register extract, risk assessment and due diligence, contract and subcontracting checks, monitoring and concentration, exit strategies, notifications and the transition from the 2019 outsourcing guidelines. The Guidelines apply from a date the EBA sets after translation into all official EU languages; until then the EBA Guidelines on outsourcing arrangements (EBA/GL/2019/02) remain in place. ICT services stay under DORA. Replace every [bracketed] value and every row marked Example. This is a documentation format, not legal or regulatory advice; check the current official text and your competent authority's instructions.

Document control

FieldValue
Document ID[TPR-NICT-001]
Entity maintaining the register[Legal name], LEI [20-character LEI]
Register level[Individual / Sub-consolidated / Consolidated / Central for an institutional protection scheme]
Entities covered[List with LEI] Example: Fernhollow Bank, Fernhollow Payments
Type of entity[Credit institution / Investment firm (Class 1 minus or Class 2) / Payment or e-money institution / ART issuer / MCD creditor / Financial holding company]
Competent authority[Name]
Register system of record[GRC tool, database]
Combined with the DORA register?[Yes, one register / No, separate with reconciliation]
Applicable guidelines[EBA/GL/2026/09 from its date of application; EBA/GL/2019/02 until then]
Version[0.1]
Status[Draft / In review / Approved / Superseded]
Owner[@third-party-risk-lead]
Approvers/reviewers[@cro], [@coo], [@procurement-head], [@compliance], [@internal-audit]
Last updatedYYYY-MM-DD
Classification[Confidential]

Approvals

RoleNameDecisionDate
Third-party risk lead (preparer)[@name][Submitted]YYYY-MM-DD
Chief Risk Officer[@name][Approved register design and criticality method]YYYY-MM-DD
Chief Operating Officer[@name][Approved]YYYY-MM-DD
Management body or delegated committee[@chair][Noted in the yearly third-party risk report]YYYY-MM-DD

Revision history

VersionDateAuthorChange summary
0.1YYYY-MM-DD[@name]Gap analysis of the outsourcing register against paras 61 and 62
0.5YYYY-MM-DD[@name]Example: Non-outsourcing third-party arrangements added; exclusions recorded
1.0YYYY-MM-DD[@name]Example: Approved; CIF arrangements scheduled for review within the transition period

Contents

1. Scope and addressees

The Guidelines address (paras 8 to 12): institutions under the CRR, third-country branches, MiFID investment firms other than small and non-interconnected firms, payment institutions and e-money institutions (account information service providers that provide only that service are excluded), issuers of asset-referenced tokens under MiCA, creditors under the Mortgage Credit Directive that are financial institutions, and approved financial holding and mixed financial holding companies. Paras 13 to 15 set the level of application: individual, sub-consolidated and consolidated for CRD institutions; consolidated for Class 2 investment firms under the IFD; individual for payment and e-money institutions; individual and, where applicable, group-wide for ART issuers.

EntityTypeAddressee?Level of applicationNotes
Fernhollow Bank (Example)Credit institutionYesIndividual and consolidatedParent; keeps the central register (para 60)
Fernhollow Payments (Example)Payment institutionYesIndividualUses group-procured providers; its usage is shown per arrangement
Fernhollow Insurance Agency (Example)Insurance intermediaryNoNot applicableCovered by the group policy on a voluntary basis

For EU branches of third-country credit institutions, para 10 accepts a service level arrangement or policy with the head undertaking in place of a contract, because the branch is not a separate legal entity.

2. Classification of arrangements

Para 17 defines a third-party arrangement as an arrangement of any form between a financial entity and a third-party service provider (TPSP), including intragroup providers, that supports one or more functions on a recurrent or ongoing basis; outsourcing arrangements are a subset. Para 31 asks three questions, and para 32 deals with mixed ICT and non-ICT services: the financial entity decides whether the ICT element is material and therefore brings the arrangement under DORA.

Para 33 lists services excluded as a general principle, with the reminder that their risks still need managing. In summary:

ExclusionExamples given in the Guidelines (paraphrased)
Services legally required to be performed by a TPSPStatutory audit
Regulated financial services that must by law be performed by another EU-regulated financial entityCustody and safekeeping, trading venues
Market information servicesMarket data feeds
Financial transactions between financial institutions or with central banksInterbank lending, central bank deposit and lending facilities
Payment network infrastructuresCard schemes and European payment initiatives
Clearing and settlement between clearing houses, central counterparties, settlement institutions and their members
Global financial messaging infrastructures under oversight
Correspondent banking services
Services with no material impact on risk exposures or operational resilience, and purchases of goods and utilitiesLegal opinions and court representation, cleaning, catering, travel, post room, office supplies, electricity
Relationship (Example)Excluded?ICT material?Recurrent support of a function?Result
Cash-in-transit and ATM cash replenishmentNoNoYesThird-party arrangement
Residential property valuations for mortgage lendingNoNoYesThird-party arrangement
Collection of retail loan arrearsNoNo (uses the bank's own systems through a portal)YesThird-party arrangement
Compliance monitoring fieldwork by a group service companyNoNoYesThird-party arrangement (intragroup)
Overflow customer contact centre staffed by a providerNoAssessed under para 32: telephony platform provided by the bank, so ICT not materialYesThird-party arrangement
Statement printing and mailingYes, goods and services with no material impactExcluded, recorded as EXC-001
Hosted core banking platformNoYesYesDORA register

3. Critical or important function assessment

Para 34 sets three tests, any one of which makes a function critical or important (CIF): disruption, discontinuity, defect or failure would materially impair (a) continuing compliance with authorisation conditions or other obligations under financial services law, (b) financial performance, or (c) the soundness or continuity of services and activities. The Guidelines state that this definition is consistent with DORA. Three further rules apply:

  • Para 35: operational tasks of internal control functions are treated as critical or important unless the assessment shows that their failure would not harm the effectiveness of the internal control function.
  • Para 36: using a provider for functions of banking activities, payment services or ART issuance to an extent that would require authorisation makes the function critical or important automatically.
  • Para 37: for entities under the BRRD, functions needed for critical functions or core business lines are critical or important unless the assessment shows no material impact on their operational continuity.
Function IDFunctionTest (a)Test (b)Test (c)Para 35, 36 or 37 ruleCIF?Same answer as DORA function list?
FUN-011 (Example)Cash supply to branches and ATMsNoNoYes: cash withdrawals stop within two daysPara 37: supports the core business line retail depositsYesYes (FUN-011 in the DORA list)
FUN-024 (Example)Collateral valuation for mortgage originationYes: CRR valuation requirementsNoYesNoYesYes
FUN-031 (Example)Arrears collectionNoYes: recoveriesNoNoYesYes
FUN-042 (Example)Second-line compliance monitoringYesNoNoPara 35: internal control taskYesYes
FUN-055 (Example)Overflow telephone customer serviceNoNoNo: core contact centre continuesNoNoYes

4. Register fields

4.1 Fields for every arrangement (para 61)

Field IDField (para 61 point)Format and validationDORA register equivalent (check)Owner
NR-F01Reference number and contract type: standalone, overarching, or subsequent or associated, with the reference of the overarching arrangement for the last (a)Unique ID; list of three values; parent reference mandatory for subsequentB_02.01Procurement
NR-F02Start date, next renewal date, end date and reason for ending (b)ISO dates; reason from a listB_02.02Procurement
NR-F03Entities in the group or IPS that use the provider (c)LEI listB_04.01Third-party risk
NR-F04Whether the provider or subcontractor is part of the group or IPS, or owned by group or IPS entities (d)Yes or no, with ownerB_05.01Third-party risk
NR-F05Brief description of the functions provided (e)Text up to 300 charactersB_06.01Business owner
NR-F06Supports a critical or important function: yes or no, with a summary of reasons (f)Yes or no; reason mandatory if yesB_06.01Business owner, checked by risk
NR-F07Internal category of each function covered; one per function (g)Code from the internal taxonomyB_06.01Third-party risk
NR-F08Provider name, identifier (LEI, EUID or alternative), registration number, registered address, contact details, ultimate parent and its identifier (h)LEI validated against the GLEIF formatB_05.01Procurement
NR-F09Country or countries where the function is performed (i)ISO 3166 country codesB_02.02Business owner

4.2 Additional fields for arrangements supporting critical or important functions (para 62)

Field IDField (para 62 point)Format and validationOwner
NR-F10Governing law of the arrangement (a)Country codeLegal
NR-F11Dates of the most recent audits (b)ISO datesThird-party risk
NR-F12Subcontractors of material parts: name, country of registration, identifier, type of function or part, rank in the chain, location of performance (c)One row per subcontractor; rank an integer from 1Third-party risk
NR-F13Outcome and date of the last substitutability assessment: easy, medium, highly complex or impossible to substitute (d)List of four values; dateThird-party risk
NR-F14Summary and date of the last assessment of reintegration or of the impact of discontinuing the function, with recovery time objective (RTO) and recovery point objective (RPO) (e)Text, date, RTO and RPO in hoursBusiness owner with business continuity
NR-F15Existence of an exit plan: yes or no (f)Yes or no; link to the planBusiness owner
NR-F16Alternative providers identified, where possible (g)Names or "none identified"Procurement
NR-F17Estimated annual budget cost for the past year, with currency (h)Amount and ISO 4217 codeFinance

Paras 58 and 59 add two design rules: distinguish arrangements supporting critical or important functions from the rest, and keep ended arrangements and their documentation in the register for an appropriate period. Para 58 also asks that ICT subcontractors effectively underpinning a non-ICT service that supports a CIF be documented in this register.

5. Register extract

5.1 All arrangements (para 61 fields)

NR-F01 Reference and typeNR-F02 DatesNR-F03 UsersNR-F04 Group?NR-F05 FunctionNR-F06 CIFNR-F07 CategoryNR-F08 ProviderNR-F09 Country
TPA-001, standalone (Example)2024-04-01, renewal 2027-03-31Fernhollow BankNoCash-in-transit and ATM cash replenishmentYes, para 37 core business lineCAT-OPS-CASHHarrowdene Cash Logistics, LEI [LEI][Member State A]
TPA-002, overarching (Example)2025-01-01, renewal 2028-01-01Fernhollow BankNoResidential property valuation panelYes, test (a)CAT-CRD-VALTamsford Property Valuers, LEI [LEI][Member State A], [Member State B]
TPA-002-01, subsequent to TPA-002 (Example)2025-06-01, renewal 2028-01-01Fernhollow BankNoDesktop valuations for remortgagesYes, test (a)CAT-CRD-VALTamsford Property Valuers[Member State A]
TPA-003, standalone (Example)2023-09-01, renewal 2026-12-31Fernhollow Bank, Fernhollow PaymentsNoCollection of retail arrearsYes, test (b)CAT-CRD-COLVelloway Collections, LEI [LEI][Member State B]
TPA-004, standalone (Example)2022-01-01, open-endedFernhollow Bank, Fernhollow PaymentsYes, group service companyCompliance monitoring fieldworkYes, para 35CAT-CTL-CMPFernhollow Shared Services, LEI [LEI][Member State A]
TPA-005, standalone (Example)2025-03-01, renewal 2027-02-28Fernhollow BankNoOverflow telephone customer serviceNoCAT-CUS-SRVSallowmere Contact Services, EUID [EUID][Member State C]
TPA-099, standalone, ended (Example)2019-05-01 to 2025-12-31, ended: exit to in-house teamFernhollow BankNoDocument archivingNoCAT-OPS-ARC[Former provider][Member State A]

5.2 Arrangements supporting critical or important functions (para 62 fields)

ReferenceNR-F10 LawNR-F11 Last auditNR-F12 Material subcontractors (rank)NR-F13 SubstitutabilityNR-F14 Reintegration and RTO/RPONR-F15 Exit planNR-F16 AlternativesNR-F17 Annual cost
TPA-001 (Example)[Member State A]2026-05-14Armoured vehicle maintenance firm (rank 1), [Member State A]MediumReintegration not feasible within a year; RTO 48 h for ATM cash, RPO not applicableYes, EXP-001Two national cash logistics firmsEUR 2.4m
TPA-002 (Example)[Member State A]2026-02-20NoneEasyPanel of other valuers can take over; RTO 120 hYes, EXP-002Three valuation firms on the reserve panelEUR 1.1m
TPA-003 (Example)[Member State B]2025-11-03Field agent network (rank 1), [Member State B]Highly complexIn-house recoveries team could take 30% of volume within three months; RTO 240 h, RPO 24 h for case dataYes, EXP-003One identified, not yet assessedEUR 0.9m
TPA-004 (Example)[Member State A]2026-06-30NoneMediumReintegration into the bank's compliance function within six months; RTO 720 hYes, EXP-004External audit firms for interim coverEUR 0.6m

Totals check: annual cost of CIF arrangements 2.4 + 1.1 + 0.9 + 0.6 = EUR 5.0 million. Excluded services are kept in a separate list (EXC-001 statement printing and mailing) with the reason, so a reviewer can see that they were considered.

6. Risk assessment and due diligence

StepParaQuestions to answerEvidence
Criticality68(a), section 3Is the function critical or important?Function assessment
Supervisory conditions68(b), 69 onwardsDoes the activity require authorisation and does the provider hold it? Is a third-country provider subject to cooperation arrangements where required?Licence check, legal memo
Risk assessment68(c), 71 to 76Impact on risk management and clients, size of the business affected, ability to scale, transfer or reintegrate, data protection, concentration at entity level, aggregated risks across functions, step-in risk for significant institutions, subcontracting chain risks, location and political stabilityRisk assessment with scenarios (para 73)
Due diligence68(d), 77 to 82Business model, financial soundness, ownership, operational track record, supervision status; for CIFs also reputation, capacity, internal controls, geographic dependencies, continuity plans, authorisations and auditabilityDue diligence file
Conflicts of interest68(e), section 7Do group links or other relationships create conflicts? Are intragroup terms at arm's length?Conflicts assessment

Example: For the renewal of TPA-003, the scenario analysis tested the provider's insolvency and a regulatory ban on its field agents. Both scenarios lead to a recovery backlog of about EUR 4 million in arrears cases within three months, within the operational risk appetite, provided the exit plan EXP-003 is triggered in the first month.

7. Contract, subcontracting, access and termination checks

Section 12 of the Guidelines (paras 83 to 109) sets the minimum content of every contract (para 84), extra content for arrangements supporting CIFs (para 85), conditions for subcontracting CIFs (paras 87 to 95), access, information and audit rights including pooled audits and certifications (paras 96 to 107) and termination rights with a transfer of the service (paras 108 and 109). Para 97 asks credit institutions to refer to the powers of competent and resolution authorities in every contract, regardless of criticality; for non-CIF arrangements, access and audit rights are risk-based (para 99).

Check IDClause areaApplies toTPA-001TPA-002TPA-003TPA-004TPA-005
CON-01Description of the function, service levels, start and end dates, notice periodsAllYesYesYesYes (SLA with group company)Yes
CON-02Governing law, location of performance and data, financial obligationsAllYesYesYesYesYes
CON-03Reference to competent and resolution authority powersAll for CRD institutionsYesYesGap, to fix at renewal 2026-12-31YesYes
CON-04Subcontracting permitted or not, conditions, notice and right to objectCIFYesNot applicable, no subcontracting allowedYesNot applicableNot required
CON-05Access, information and audit rights for the entity and the authorities, unrestrictedCIFYesYesYesYesRisk-based, yes
CON-06Business continuity obligations and testingCIFYesYesPartialYesNot required
CON-07Termination rights and support for transferCIFYesYesYesYesYes

Record each gap as a remediation item with an owner and due date in the risk register, and link it to the transition plan in section 12.

8. Monitoring and concentration risk

Para 110 asks for risk-based monitoring and periodic reporting to the management body on CIF arrangements; para 111 asks for internal concentration risk to be monitored, including through subcontractors; para 112 lists the tools (provider reports, KPIs, key control indicators, service delivery reports, self-certifications, independent reviews, business continuity test reports); para 113 requires corrective action or termination when shortcomings appear.

Indicator IDArrangementIndicatorThreshold (Example)Last value (Example)Status
TPI-001TPA-001ATM cash-out incidents per monthAmber at 5, red at 103Green
TPI-002TPA-002Valuations delivered within 5 business daysAmber below 95%, red below 90%96.5%Green
TPI-003TPA-003Cure rate of arrears cases after 90 daysAmber below 40%, red below 30%37%Amber
TPI-004All CIFProvider credit rating or financial health scoreDowngrade by two notches triggers reviewNo changeGreen

Concentration view: list providers that support more than one CIF, functions supported by a single provider with "highly complex" or "impossible" substitutability, and dependencies on one country.

Concentration IDDescription (Example)AssessmentAction
CNC-001TPA-003 is highly complex to substitute and its field agent subcontractor is in one countryMediumAssess the alternative provider by YYYY-MM-DD
CNC-002Group service company TPA-004 also supports the internal audit function under another arrangementLow, conflicts managedAnnual review of the conflicts assessment

Feed the indicators into the KRI Framework Specification (finance/kri-framework-spec) so that third-party KRIs reach the risk committee with the rest of the operational risk profile.

9. Exit strategies

Para 114 requires a documented exit strategy for CIF arrangements covering at least termination, provider failure, concentration and difficult exit, deterioration of quality, material risks to continuous performance and significant breaches by the provider. Para 115 asks for realistic, documented and, where appropriate, tested exit plans and for alternative solutions and transition plans. Para 116 lists what to define: objectives, roles and resources, success criteria for the transfer of services and data, and indicators that trigger exit.

Exit plan IDArrangementExit triggersTarget end stateTransition timeLast testSuccess criteria
EXP-001 (Example)TPA-001Provider insolvency, licence loss, two red months on TPI-001Second national provider under a standby agreement8 weeksTabletop, 2026-03-12ATM availability at least 95% during transition
EXP-002 (Example)TPA-002Quality failures in sample reviews, conflicts of interestReserve panel valuers2 weeksDesk review, 2026-01-20No backlog above 5 business days
EXP-003 (Example)TPA-003Provider failure, conduct breach, red on TPI-003 for three monthsAlternative provider plus in-house team for 30% of volume6 monthsNot yet tested: test planned YYYY-MM-DDRecovery rate within 5 points of plan, all case data transferred and reconciled
EXP-004 (Example)TPA-004Group restructuring, sale of the service companyReintegration into the bank's compliance function6 monthsDesk review, 2026-07-01Monitoring plan delivered on schedule

10. Notifications and supervisory requests

EventParaWhat to provideTimingLog ID
Planned CIF arrangement, or a function becoming critical or important65At least the information in paras 61 and 62, and supervisory dialogue where appropriate (payment institutions also under PSD2 Article 19(6))In a timely manner, before the arrangement startsNOT-YYYY-NNN
Material change or severe event affecting a CIF arrangement66Description and impact on business continuityIn a timely mannerNOT-YYYY-NNN
Request for the register63Full register or specified sections in processable electronic form (the DORA ITS format may be used)On requestREQ-YYYY-NNN
Request for supervisory information64Any information needed, including a copy of a contractOn requestREQ-YYYY-NNN
CIF review not finished within two years of the date of application20Fact of the delay, measures to complete the review or possible exit strategyAt the two-year pointNOT-YYYY-NNN

Check national requirements as well: some competent authorities set advance notice periods for outsourcing in national rules that implement the guidelines.

11. Governance and data quality

Under paras 38 to 50, the management body defines, approves and regularly reviews a strategy on third-party risk and a policy on arrangements for non-ICT services supporting CIFs; both may be integrated with the DORA ICT third-party strategy and policy (para 49 allows the policy to be merged with the DORA Article 28(10) policy). Sections 7 to 9 add conflicts of interest, business continuity plans and internal audit coverage.

Data quality controlRuleFrequencyOwnerLast result (Example)
DQ-01 CompletenessEvery arrangement has all para 61 fields; every CIF arrangement also has all para 62 fieldsMonthly[@third-party-risk-lead]2 CIF records missing RTO, fixed
DQ-02 Consistency with DORASame provider identifiers and function IDs as the DORA register; no function marked CIF in one and not in the otherQuarterly[@third-party-risk-lead]Passed
DQ-03 Identifier validityLEI or EUID format valid and activeMonthly[@procurement]Passed
DQ-04 Ended arrangementsEnded records kept with end date and reasonQuarterly[@procurement]Passed
DQ-05 Reconciliation to accounts payableEvery provider paid above [EUR 50,000] a year is classified in the register or the exclusion listHalf-yearly[@finance]3 suppliers added after review

12. Transition plan

Paras 18 to 22: the Guidelines apply from a date to be set to arrangements entered into, reviewed or amended on or after it; existing arrangements are to be reviewed and amended; for CIF arrangements, if the review and documentation are not finished within two years of the date of application, the entity informs its competent authority with the planned measures or a possible exit strategy; non-CIF arrangements may be reviewed at renewal; the 2019 Guidelines on outsourcing are repealed from the date of application.

WorkstreamScopeTarget dateOwnerStatus (Example)
TR-01 Register gap closureAdd non-outsourcing arrangements and the new fields (contract type, RTO and RPO, exit plan, annual cost)Before the date of application[@third-party-risk-lead]In progress
TR-02 CIF contract reviewTPA-001 to TPA-004 against section 7Within two years of the date of application[@legal]TPA-003 scheduled at renewal 2026-12-31
TR-03 Non-CIF arrangementsTPA-005 and othersAt next renewal[@procurement]Planned
TR-04 Policy and strategy updateCombined ICT and non-ICT policyBefore the date of application[@cro]Draft
TR-05 Exit plan testingEXP-003 not yet testedYYYY-MM-DD[@coo]Planned

13. Jurisdiction notes

JurisdictionBasisStatus as of 2026-10 (check the official source)
EU, non-ICTEBA/GL/2026/09, Guidelines on the sound management of third-party risk regarding non-ICT servicesFinal report 2026-09-18; date of application to be set after translation; replaces EBA/GL/2019/02
EU, ICTRegulation (EU) 2022/2554 (DORA), Article 28 register of informationApplies since 2025-01-17
UKPRA Supervisory Statement SS2/21, Outsourcing and third party risk managementCurrent version effective 2024-12-31; an updated version published 2026-03-18 (with PS7/26) is effective from 2027-03-18
USInteragency Guidance on Third-Party Relationships: Risk Management (Federal Reserve, FDIC, OCC), 88 FR 37920Final guidance of 2023-06-06, published 2023-06-09

14. Glossary and references

TermMeaning
Third-party arrangementArrangement of any form with a provider, including intragroup, that supports one or more functions on a recurrent or ongoing basis (para 17)
Outsourcing arrangementA third-party arrangement in which the provider performs a function the entity would otherwise perform itself
TPSPThird-party service provider
CIFCritical or important function
IPSInstitutional protection scheme
ARTAsset-referenced token under MiCA
RTO, RPORecovery time objective; recovery point objective
EUIDEuropean Unique Identifier for companies registered in EU business registers
SubstitutabilityHow easily a provider can be replaced: easy, medium, highly complex or impossible (para 62(d))

References (cited by number and title; obtain the official text):

15. Standard and licence note

Based on the EBA Guidelines on the sound management of third-party risk regarding non-ICT services (EBA/GL/2026/09, final report of 18 September 2026), with Regulation (EU) 2022/2554 (DORA) for the boundary with ICT services. EBA material is reused with acknowledgement; paragraph numbers are cited and the register fields are paraphrased in original words, with no normative text reproduced. The structure, field IDs, checks, indicators and the Fernhollow Bank example are original; Fernhollow Bank, its providers and every figure are fictional. Check the current official text, the date of application set by the EBA and your competent authority's national requirements before use. This is a documentation format, not legal or regulatory advice.

Template licence: MIT.

Related templates