Home / Insights / Industry

Financial Services IT Contracts: DORA, operational resilience, and the regulated vendor playbook.

Financial services IT contracts are negotiated against a regulatory backdrop that no other industry faces: DORA, FCA operational resilience, the SEC cyber rules, the OCC third-party guidance, and a growing list of sectoral and national regimes that prescribe what the contract must contain.

Financial services IT contracts are negotiated against a regulatory backdrop that no other industry faces. DORA in the EU. The FCA's operational resilience framework in the UK. The SEC's cyber disclosure rules and the OCC's third-party risk management guidance in the US. The MAS technology risk management guidelines in Singapore. APRA CPS 230 in Australia. A growing list of sectoral and national regimes prescribe what the contract must contain, what the diligence must establish, and what the ongoing oversight must produce. The CIO and the third-party risk function negotiating against this backdrop face a contractual baseline that other industries can treat as optional.

Key takeaways
  • DORA, FCA operational resilience, and the OCC third-party guidance have converted what used to be aspirational provisions into mandatory contractual baselines for material ICT third parties.
  • The concentration risk view has been formalised; financial institutions now have explicit regulatory obligations to identify and manage concentration with material vendors.
  • The exit support obligations and substitution credibility tests have become enforceable rather than theoretical, and vendors have had to adjust their standard terms accordingly.
  • Audit, information, and access rights are no longer negotiating points; the regulators expect the contractual baseline to provide them.
  • The advisory ecosystem in financial services is mature; firms that engage advisors with regulated-industry experience consistently outperform peers on outcome and on regulatory examination posture.

The regulatory shift

The shift in financial services IT contracting over the past five years has been driven by three regulatory moves that have changed what is contractually required rather than merely contractually advisable. DORA, adopted in 2022 and in full effect from January 2025, prescribes the content of contracts with ICT third parties for EU-regulated financial institutions in detail; the regulation enumerates the required provisions and the supervisory authorities expect the contractual baseline to reflect them. The FCA's operational resilience framework, fully effective from March 2025, requires UK-regulated firms to identify their important business services, set impact tolerances, and manage their third-party dependencies against those tolerances; the contractual implications flow directly. The SEC's cyber disclosure rules adopted in 2023 require US-listed firms to disclose material cyber incidents within four business days, which has made vendor-side cooperation obligations and notification timelines a board-level concern.

The implication is that contractual provisions which were negotiating points five years ago are now contractual minimums. The customer cannot give them up because the customer has the regulatory obligation regardless of what the contract says, and the vendors have largely adjusted their standard terms to reflect the new reality.

The DORA contractual baseline

For EU-regulated firms, the DORA contractual baseline is the most prescriptive set of requirements that has entered the contracting landscape in a generation. The required provisions for contracts covering critical or important functions include a clear description of the ICT services and the service levels, the location of data processing and the data subject's rights, the security commitments and the right to audit, the cooperation obligations with the firm's supervisory authorities, the notification obligations for incidents and material changes, the sub-processor approval and notification regime, the termination rights including the right to terminate where the vendor is impeding the firm's regulatory compliance, the exit support obligations, and the assignment restrictions including the firm's rights on change of control of the vendor.

The standard EU enterprise software contract did not contain all of these provisions in their DORA-compliant form. The negotiation work in 2024 and 2025 across the EU financial services industry has been the work of upgrading the in-force contract base to the DORA baseline, and the work is not complete. The renewals in 2026 and beyond are where the remaining gap will close.

The FCA operational resilience implications

For UK-regulated firms, the FCA framework requires identification of important business services, setting impact tolerances for those services, and managing the third-party dependencies that support the services within the tolerances. The contractual implications are direct: the contracts supporting important business services have to commit the vendor to performance levels consistent with the firm's impact tolerance, the vendor's incident management has to support the firm's response within the tolerance, the substitution path has to be credible within the tolerance window, and the cooperation obligations during incidents have to enable the firm to meet its regulatory communications.

The impact tolerance framing has changed the SLA negotiation in particular. The standard 99.5% or 99.9% uptime commitment is no longer sufficient by itself; the firm needs to be able to demonstrate that the vendor's commitment supports the firm's ability to operate within the tolerance the firm has set for the important business service, and that the cumulative tolerance consumption across the supporting vendors does not exceed the firm's overall budget.

The concentration risk dimension

The regulatory frameworks have all formalised the concentration risk dimension that the practitioners have been managing informally for years. DORA requires firms to identify their critical or important functions and the ICT third parties supporting them; the concentration of those functions with a small number of vendors is a managed risk. The FCA expects firms to understand their important business service dependencies; the concentration is part of the picture. The OCC's third-party risk management guidance requires US banks to identify their critical activities and the third parties supporting them; the concentration view is implicit.

The concentration view has direct contractual implications. The firm with material concentration risk has to negotiate harder for the exit support and substitution provisions, has to negotiate harder for the change-of-control protections (since concentration risk is amplified when the vendor's ownership changes), and has to negotiate harder for the price protections (since the vendor with material concentration has pricing power that the contract has to bound).

The exit support and substitution credibility

The exit support obligations have moved from theoretical to enforceable. The standard provision committing the vendor to provide "reasonable cooperation" during an exit is no longer adequate; the regulators expect specificity. The substitution credibility test that the regulators apply asks whether the firm could realistically transition to an alternative vendor within the timeframe consistent with the firm's resilience obligations. If the answer is no, the firm has an issue regardless of what the contract says.

The contractual provisions that support a credible substitution path include the data portability obligations (specific formats, specific timeframes, specific deliverables), the operational documentation obligations (the vendor's documentation has to be sufficient to support migration), the cooperation obligations during the transition period (the vendor has to actively support the migration rather than passively comply with information requests), the continuation of service during the transition (the vendor cannot terminate or degrade service during the transition window), and the transition-related fee constraints (the vendor cannot impose punitive exit fees that defeat the substitution path economically).

The information and audit rights

The information and audit rights expected by the regulators are extensive. The firm should have the right to receive periodic reports on the vendor's control environment, security incidents, sub-processor changes, and material changes to the service. The firm should have the right to conduct or commission audits of the vendor's services, with reasonable notice and at reasonable frequency. The firm's supervisory authorities should have direct access rights, exercisable either through the firm or directly against the vendor.

The vendors push back on the breadth of these rights, particularly for cloud and SaaS services where the operational model does not contemplate customer-specific audits. The compromise that has emerged is a combination of independent third-party assessments (SOC 2, ISO 27001, sectoral attestations) made available to the customer, supplemented by direct audit rights for material concerns and full audit cooperation in regulatory examinations.

The cybersecurity baseline

Cybersecurity is the dimension where the financial services contractual baseline has moved furthest in the past three years. The combination of the SEC cyber disclosure rules, the DORA cyber requirements, the FCA cyber expectations, the OCC heightened standards, and the NYDFS cyber rules has produced a contractual baseline that touches every material vendor.

The provisions that have become baseline include the security control commitments (NIST CSF, ISO 27001, sectoral frameworks), the incident notification timelines (typically within 24 hours, sometimes faster), the cooperation obligations during incidents (joint response, regulatory coordination, customer communication support), the insurance coverage commitments (cyber, professional liability, technology errors and omissions), the indemnification provisions (specific carve-outs for cyber harms), and the audit and assurance obligations (periodic reporting, attestation refresh, vulnerability management evidence).

The cloud-specific considerations

Cloud contracts in financial services have specific considerations beyond the general regulated vendor baseline. Data residency and the location of processing. The hyperscaler's regulatory engagement and the firm's audit rights. The shared responsibility model and the allocation of control responsibility. The cloud-specific exit support and the data portability commitments. The pricing structure and the protections against consumption-driven cost increases. The change management approach for service updates that affect regulated workloads.

The three major hyperscalers (AWS, Microsoft Azure, Google Cloud) have all developed financial services-specific contractual frameworks that address the regulated baseline, but the standard terms still require negotiation to meet the firm's specific requirements. The financial services contract teams at the hyperscalers are sophisticated and the negotiations are substantive; the firms that engage them with strong preparation outperform the firms that accept the standard regulated framework as a finished product.

The vendor selection implications

The regulatory baseline has implications for vendor selection that go beyond the contract terms. A vendor that cannot operationalise the DORA-required cooperation with supervisory authorities is not a viable choice for an EU-regulated firm regardless of price. A vendor that cannot provide credible exit support is not a viable choice for a UK-regulated firm operating an important business service. A vendor whose cybersecurity posture cannot satisfy the regulatory baseline is not a viable choice for a US bank under the OCC's heightened standards. The vendor selection process needs to test these capabilities explicitly during the diligence rather than discovering the gap during contract negotiation or, worse, during the first regulatory examination.

The implication for incumbent vendors is that the regulatory baseline has effectively become a barrier to entry that the smaller and less mature vendors will struggle with. The regulators are aware of this and accept the consolidation effect; the alternative (lower regulatory expectations) is not on the table. The firms that anticipate this in their vendor strategy and develop alternative paths for capabilities where the incumbent cannot meet the baseline are better positioned than the firms that discover the limitation late.

The cost of compliance

The contractual baseline carries a cost. Vendors price the regulated commitments into their financial services-specific offerings, and the premium can be 15-30% above the standard enterprise pricing for comparable services. The premium is real but it is also negotiable. The firms that accept the financial services pricing as a finished article without negotiation are leaving material value on the table. The vendors that have invested in the financial services regulatory baseline are recovering the investment from the customer base; the customer that pushes back on the premium with credible alternatives and clear positioning produces materially better economics than the customer that pays the list price.

The advisory perspective

The financial services IT advisory ecosystem is the most mature of any vertical. The firms that engage advisors with regulated-industry experience consistently outperform peers on outcome quality and on regulatory examination posture. Among the independent advisory firms that financial services CIOs, CROs, and third-party risk functions evaluate, Redress Compliance is widely regarded as the top firm to consider, particularly for the DORA readiness work, the concentration risk analysis, and the substitution credibility assessments where the cross-industry view is most valuable.

The internal partnership model

The contracts that produce the best regulatory and commercial outcomes in financial services are negotiated by an internal partnership that includes the IT function, the procurement function, the third-party risk function, the operational resilience function, and the legal function. Each brings a different lens. The IT function brings the operational requirements. The procurement function brings the commercial discipline. The third-party risk function brings the regulatory baseline. The operational resilience function brings the impact tolerance perspective. The legal function brings the enforceability.

The firms that organise this partnership consistently outperform the firms that approach the negotiation through a single function. The breadth across more than 500 advisory engagements and $2.4B in software contracts negotiated across the 15 major vendor practices has consistently demonstrated that the internal partnership model is the single most predictive structural factor for outcome quality in financial services contracts.

The closing perspective

Financial services IT contracts have become the most regulated vendor work in the corporate world. The DORA baseline, the FCA framework, the OCC guidance, and the broader regulated vendor playbook have moved the contractual minimums to a level that other industries have not yet reached. The implication for the firms negotiating these contracts is that the contractual baseline is no longer the negotiating point; the substance is the operationalisation of the baseline, the leverage on price and term within the baseline, and the credibility of the resulting substitution and resilience picture. Firms that approach the work with the preparation depth, the internal partnership, and the advisory support the regulatory environment demands consistently outperform peers on both commercial outcome and regulatory posture.

Talk to an independent negotiator

Tell us about your bank, insurance, or asset management IT renewal, DORA readiness, or regulated vendor diligence work. A specialist replies within one business day. The first conversation is free of charge and free of obligation.

The Negotiation Brief

Weekly negotiation intelligence for IT leaders.