Digital Operational Resilience Act

What the authority record establishes

DORA establishes requirements for ICT risk management, incident reporting, resilience testing, third-party risk, and oversight in the financial sector.

Binding for in-scope entities

The exact official title, issuing body, jurisdiction, version or application record, and linked source define the scope of this page. Readers should not transfer the authority's status to a commercial product or infer transaction-, patient-, system-, site-, or organization-specific applicability from this summary.

Why it matters to this market

Treasury and payment services supporting regulated financial entities may enter ICT inventories, continuity plans, testing, incident, vendor, and contractual evidence chains.

Affected operating stages

• Scope
• Control Design
• Execution
• Monitoring
• Evidence
• Improvement

Capabilities to examine

Payment Initiation Approval And Release Control

Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for payment initiation approval and release control.

Counterparty Credit And Market-Risk Controls

Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for counterparty credit and market-risk controls.

Policy Limits Approvals And Segregation Of Duties

Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for policy limits approvals and segregation of duties.

Audit Trail Control Evidence And Record Retention

Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for audit trail control evidence and record retention.

ERP Accounting Market-Data And API Integration

Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for ERP accounting market-data and API integration.

Treasury Master-Data Normalization And Lineage

Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for treasury master-data normalization and lineage.

Case Workflow Exception And Task Management

Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for case workflow exception and task management.

Affected buyer audiences

• treasury
• finance
• payments
• risk and controls

Implementation questions

• Which entities, products, populations, transactions, systems, sites, or jurisdictions are actually within scope?
• What is binding, what is guidance, and what is a technical or consensus standard?
• Which publication, adoption, effective, application, transition, and enforcement dates differ?
• Who owns legal, clinical, quality, regulatory, policy, or operational interpretation?
• How will a source revision affect open work and historical decisions?

Interpretation boundary

A software certification, hosting claim, or vendor control list does not determine DORA scope or establish regulatory compliance.