Contractual arrangements document the formal agreements between your financial entity and ICT third-party service providers. Under DORA, these arrangements must be recorded in the Register of Information and meet specific contractual requirements outlined in Article 30.

Contracts List Page

Search and Filters

The contracts list provides a search bar for filtering by contract reference or provider name, and a status filter dropdown with the following options:

  • All — show all contracts
  • Active — currently in force
  • Draft — not yet finalised
  • Expiring — end date within 90 days
  • Expired — past end date
  • Terminated — manually terminated

Table Columns

ColumnDescription
ReferenceThe contract reference code (e.g., AWS-2025-001)
ProviderThe linked ICT provider's display name
TypeContract type from ESA code list
PeriodStart date to end date range
Annual CostAnnual cost with currency symbol
StatusStatus badge (see colours below)
FunctionsCount of linked business functions
ActionsView, Edit, Delete buttons

Status Badge Colours

  • Active — green badge
  • Draft — gray badge
  • Expiring — amber badge
  • Expired — red badge
  • Terminated — red badge

Creating a Contract

Click "Add Contract" to open the creation form. Complete the following fields:

FieldTypeRequiredDetails
ICT ProviderDropdownRequiredSelect from your registered ICT providers. The provider must be created first.
Contract ReferenceText inputRequiredA unique reference for this arrangement. Placeholder: "AWS-2025-001"
Contract TypeDropdownRequiredOptions from ESA code list including: Outsourcing, Licensing, Subscription, Maintenance/Support, Consultancy, Development, Hosting, Cloud Services, Data Services, Network Services, Security Services, Other
Start DateDate pickerRequiredThe date the contractual arrangement takes effect.
End DateDate pickerOptionalThe date the arrangement expires. Leave blank for open-ended contracts.
Annual CostNumber inputOptionalThe annual cost of the arrangement.
CurrencyDropdownOptionalOptions: EUR, USD, GBP, CHF, BGN
ICT Service TypeDropdownOptionalThe type of ICT service provided. The system can auto-detect the service type based on the provider type and contract type.
Parent ArrangementDropdownOptionalSelect "None" or another existing contract if this is a sub-arrangement.
Service DescriptionText inputOptionalA brief description of the ICT services covered by this arrangement.
Data Storage Locations (at rest)Multi-select countriesOptionalSelect all countries where data is stored at rest under this arrangement.
Data Processing LocationsMulti-select countriesOptionalSelect all countries where data is actively processed.
Notice Period — EntityNumber inputOptionalNumber of days notice required from your entity to terminate. Measured in days.
Notice Period — ProviderNumber inputOptionalNumber of days notice required from the provider to terminate. Measured in days.
Governing Law CountryDropdownOptionalThe country whose law governs this contract.
Country of ProvisionDropdownOptionalThe country from which the ICT service is primarily provided.
Data SensitivityDropdownOptionalOptions: Low, Medium, High. Indicates the sensitivity level of data handled under this arrangement.
Reliance LevelDropdownOptionalOptions: Low, Medium, High. Indicates how dependent your entity is on this ICT service.
Termination ReasonTextareaOptionalIf the contract has been terminated, record the reason here.
NotesTextareaOptionalFree-text notes about this contractual arrangement.

Article 30 Clause Checker

DORA Article 30 mandates specific contractual provisions. The clause checker provides 8 checkboxes to track whether each required clause is present in the contract:

#ClauseDORA Reference
1SLA definedService level agreements with clear performance targets
2Security standardsICT security requirements and standards specified
3Incident reportingObligations for ICT incident notification and response
4Audit rightsRight to audit or inspect the provider
5Termination clausesClear termination and exit provisions
6Data locationSpecification of data storage and processing locations
7Subcontracting notificationProvider must notify of sub-outsourcing arrangements
8Exit strategyTransition and exit strategy defined
⚠️
Contracts supporting critical or important functions must include all eight clauses under DORA Art 30. Missing clauses will be flagged in the pre-export validation as errors.

Editing a Contract

The edit page includes all the fields from the creation form, plus the following additional features:

Status Dropdown

When editing, you can change the contract status via a dropdown selector. Options: Active, Draft, Expiring, Expired, Terminated.

Document Upload

You can attach supporting documents to a contract. The document upload section supports the following file types:

  • PDF, DOCX, XLSX, CSV, TXT, PNG, JPG, JPEG

Each uploaded document displays:

  • Filename — the original file name
  • Size — file size in KB or MB
  • Upload date — when the document was attached
  • Download button — to retrieve the document
  • Delete button — to remove the attachment
💡
Link your contracts to business functions to build the full dependency chain required for ESA templates B_04.01 and B_06.01. This also feeds into the concentration risk analysis.