Risk Guardops • Updated November 2026
📝 Compliance • 10 min read

DORA for ICT Suppliers to EU Financial Firms: Requirements, Costs and Timelines

EU banks and insurers are rewriting supplier contracts under DORA. Here's which clauses you can't negotiate away, what compliance typically costs in year one, and how long remediation tends to take.

SPONSORED CONTEXTUAL PLACEMENT
💼
Evaluating Enterprise Deployments in 2026?

Request our confidential total cost of ownership matrix and vendor RFP templates.

Launch Calculator →

Why DORA Binds You Even Though No EU Regulator Supervises You

If you sell software, cloud hosting, managed IT or data services to an EU bank, insurer, investment firm or payment institution, your customer's procurement team has probably already sent a DORA addendum. Some suppliers sign it unread. Others push back clause by clause. Before you do either, learn which terms are fixed by law and which are open to negotiation.

The Digital Operational Resilience Act (Regulation (EU) 2022/2554) has applied since January 2025. It regulates financial entities, not most of their suppliers. But Article 30 tells those entities what their ICT contracts must contain, and Article 28 makes them responsible for third-party risk. Your obligations reach you through the contract. DORA compliance for ICT providers is mainly a contracting and evidence exercise: you agree to the mandatory terms, then prove you can meet them.

Advertisement

Where you're incorporated makes no difference. A 60-person SaaS company in Pune, a managed service provider in Manchester and a data vendor in Toronto get the same addendum if the customer is a Frankfurt bank. The exception is the small group of suppliers the EU designates as critical. They're supervised directly, as covered below.

RECOMMENDED SOLUTION

Looking to streamline vendor RFP selection?

Access pre-negotiated tier discounts through our independent institutional network.

Compare Pricing →

Critical or Important Functions: The Classification That Sets Your Workload

DORA sets two levels of contract requirements. Every ICT service contract must meet the baseline in Article 30(2). Contracts supporting a critical or important function must also meet Article 30(3), and that's where most of the cost sits.

Your customer decides which category you fall into, not you. A function counts as critical or important if disrupting it would materially impair the firm's financial performance, the soundness or continuity of its services, or its regulatory compliance. Core banking, payments processing, policy administration, trading platforms, identity and access management, and the hosting underneath them usually qualify. HR software, marketing tools and expense management usually don't.

Ask every financial customer how they've classified your service, and get the answer in writing. If they say critical or important, budget for the full set of obligations. Customers sometimes over-classify to be safe. If your tool can't realistically disrupt a regulated service, ask them to explain their reasoning.

DORA Contractual Requirements, Clause by Clause

The table below summarizes the DORA contractual requirements in Article 30 and what each usually demands from a supplier. It isn't legal advice. Have counsel with EU financial-services experience review your actual addendum.

RequirementApplies toWhat it usually means for you
Clear description of all functions and services, including permitted subcontractingAll ICT contractsA precise service schedule, plus disclosure of the subcontractors that support it
Locations (regions/countries) of service delivery and data processing, with notice of changesAllName your hosting regions and support locations, and give advance notice before moving them
Data availability, authenticity, integrity and confidentiality, including personal dataAllDocumented security controls, usually backed by ISO 27001 or SOC 2 evidence
Access to, recovery and return of data on insolvency, resolution or terminationAllA data-return process in a usable format, on defined timelines
Assistance with ICT incidents related to the service, at no extra cost or at a cost set in advanceAllIncident-support rates agreed upfront. Open-ended time-and-materials billing won't be accepted
Full cooperation with competent authorities and resolution authoritiesAllAgreement to deal with regulators if they ask
Termination rights and minimum notice periodsAllThe customer can exit for regulatory reasons, such as a breach of law or a supervisor's instruction
Participation in the customer's security awareness and resilience trainingAllOccasional staff time
Full SLAs with precise quantitative and qualitative targetsCritical/importantMeasurable uptime, response and recovery targets, with reporting
Notice and reporting obligations on developments affecting serviceCritical/importantPrompt notice of anything that could affect delivery
Business contingency plans and their testingCritical/importantTested BCP/DR plans, with results you can share
Participation in threat-led penetration testing (TLPT)Critical/importantPossible involvement in the customer's red-team exercises. Pooled testing is allowed
Unrestricted rights of access, inspection and auditCritical/importantOn-site and remote audits by the customer, its auditors and its supervisor
Exit strategies with a mandatory adequate transition periodCritical/importantContinued service and support while the customer migrates away

Negotiable: incident notification hours, audit frequency and logistics, transition period length, and liability caps. Not negotiable: the existence of audit rights, regulator access and exit support. Try to strip those and the deal will stall.

Audit Rights, Exit Plans and Incident Cooperation in Practice

Audit rights

"Unrestricted" covers who can audit and what they can examine. It doesn't mean unlimited visits at any time. Financial entities may rely on alternative assurance, such as pooled audits run by several customers together, or certifications and third-party reports, provided the assurance fits the risk. Offer a standard assurance pack: an ISO 27001 certificate, a SOC 2 Type II report, penetration test summaries and BCP test results. Define a pooled-audit process with reasonable notice periods. Most customers will accept this as first-line evidence while keeping the right to audit you directly.

Exit plans

Your customer must maintain an exit strategy for each critical service. Expect to commit to a transition period, often somewhere between 6 and 18 months, at contracted rates, plus data export in documented formats and reasonable help to whoever replaces you. Prepare a written exit runbook covering data formats, export tooling, named roles and timelines. It helps the sale, too, because procurement teams often score it.

Incident cooperation

Financial entities face tight deadlines for reporting major ICT incidents: an initial report within hours of classification, and a hard outer limit measured in a day or so after awareness. Check the current technical standards for exact figures. Those clocks flow down to you, and customers commonly ask suppliers to notify within hours of detecting an incident that affects them. Agree to a window your on-call team can reliably meet. Missing a contracted window is a breach. A slightly longer window you always hit isn't.

RECOMMENDED SOLUTION

Looking to streamline vendor RFP selection?

Access pre-negotiated tier discounts through our independent institutional network.

Compare Pricing →

Feeding Your Customers' DORA Register of Information

Every in-scope financial entity keeps a register of information covering all its ICT contracts. Its format is set by implementing technical standards, and entities submit it to national supervisors on a regular cycle. For you, this means data requests, and the same ones arrive from every customer.

  • Legal entity identifier. Supervisors expect suppliers to be identified by an LEI, or by an EUID for EU entities. If you don't have an LEI, get one. Annual fees through accredited issuers are typically modest, often under USD 200.
  • Subcontracting chain. Customers must map the subcontractors that effectively support critical services, sometimes several levels down. Keep a maintained list covering your hosting provider, support centers and key software dependencies.
  • Service and data locations by country.
  • Substitutability and exit details, meaning how hard it would be to replace you.

Keep one version-controlled "DORA supplier data sheet" and send it to every customer. Filling in each bank's spreadsheet from scratch burns days of account-management time every year.

When You Become a Critical ICT Third-Party Provider

A small group of suppliers is regulated directly. The European Supervisory Authorities (EBA, EIOPA and ESMA) designate a critical ICT third-party provider (CTPP) based on systemic impact, how many financial entities rely on it, how substitutable it is, and how many important functions it supports. The first designations have been published and centre on the large hyperscale cloud providers and other large global IT, data and telecom firms.

A designated CTPP gets a Lead Overseer with powers to request information, inspect and issue recommendations. It pays oversight fees, and periodic penalty payments are possible for non-compliance. A CTPP based outside the EU must establish an EU subsidiary.

Most mid-size suppliers won't come close. But if you serve a meaningful share of EU banks or insurers in one niche, such as core insurance platforms, follow the criteria. A provider can also opt in to oversight voluntarily.

Regional Differences for Suppliers in the UK, India, North America and Elsewhere

DORA's requirements don't change by supplier location. The regulatory overlap and practical friction do.

  • UK suppliers that also serve UK firms face a separate regime: PRA and FCA outsourcing rules and the UK critical third parties regime. These overlap with DORA without matching it. Build one control set that maps to both, and expect to maintain two contract addenda.
  • India-based IT services and SaaS firms usually get the closest scrutiny on support locations, subcontracting and data access from offshore delivery centers. If your teams already meet RBI or SEBI outsourcing expectations for Indian clients, much of that evidence can be reused. GDPR data-transfer terms still apply on their own track.
  • North American suppliers often hold SOC 2 already, which covers much of the evidence base. The usual gaps are exit runbooks, regulator-access clauses and fixed-rate incident assistance.
  • Suppliers in the Middle East, Southeast Asia, Latin America and Africa face the same terms. Expect extra questions about local laws that could conflict with regulator access or data return, and map those conflicts before a customer finds them.

Rules on data localization, government access and export controls vary by country. Get local counsel to confirm you can legally commit to every Article 30 term from your jurisdiction.

DORA Compliance Cost: Indicative First-Year Budgets

The figures below are typical 2026 market ranges in USD. They vary widely by contract, region and starting maturity, and local legal and audit rates differ. Confirm with advisers and vendors. The biggest driver is whether you already hold ISO 27001 or SOC 2 Type II. If you don't, add that certification to the bill.

Cost itemSmall supplier (under 100 staff)Mid-size (100–1,000)Large (1,000+)
Gap assessment against Article 30 and customer addenda$10k–35k$30k–90k$80k–250k
Legal: standard DORA addendum plus negotiation support$15k–50k$40k–150k$150k–500k+
ISO 27001 or SOC 2 Type II (if not already held)$30k–90k$60k–180kUsually held
BCP/DR design and annual testing$10k–40k$40k–150k$150k–600k
Exit runbooks, data export tooling, subcontractor mapping$10k–30k$30k–120k$100k–400k
Ongoing audit, questionnaire and register support (staff time)0.25–0.5 FTE1–3 FTEDedicated team
Indicative first-year total$50k–200k$200k–700k$1M+

Hypothetical example: say a 45-person SaaS company already holds SOC 2 Type II and sells reconciliation software to three EU banks, all of which classify it as critical. It skips certification costs. It spends about $25k on a gap assessment and addendum template, $20k on a tested DR plan and an exit runbook, and gives a senior engineer roughly 30% of their time to audit and register requests. A realistic first-year figure is $70k–110k. Whether that's acceptable depends on contract value, so compare it with the annual revenue from those three customers.

Realistic Timelines, Red Flags and Where to Start

From a standing start, plan on 6 to 12 months. A gap assessment takes roughly 4 to 8 weeks. A standard addendum takes 1 to 2 months. Exit runbooks and DR testing take 2 to 4 months. Renegotiation usually happens at each customer's renewal, so it can stretch over 12 to 24 months across your portfolio. A new certification adds 6 to 12 months.

Watch for these red flags in customer addenda:

  • Incident notification windows shorter than your on-call coverage can meet
  • Unlimited liability attached to DORA clauses, which the regulation doesn't require
  • Free, open-ended exit support, when the law requires an adequate transition period, not an indefinite one
  • Audit clauses that rule out pooled audits or reliance on certifications
  • Flow-down terms your own hyperscaler or subcontractors won't accept

Decision rule: if a meaningful share of your revenue comes from EU financial firms, or you're bidding on a critical-function contract this year, build your own standard DORA addendum and assurance pack now rather than reacting customer by customer. Start by asking each financial customer, in writing, how it classifies your service. That answer tells you what to build first.

Quick Answers

Do ICT suppliers outside the EU have to comply with DORA? +
Can we refuse the unrestricted audit rights clause? +
Is DORA compliance a one-off cost? +
RG
Risk Guardops Editorial Team
Independent research desk
Guides on Risk Guardops are produced by our editorial team. Pricing, features and regulations change often - confirm details with the vendor or a licensed professional before making decisions.
SPONSORED 2026 Vendor Pricing Benchmarks: Model exact seat pricing, setup fees, and ROI across our verified database.
Launch Calculator →