Financial data in the DORA register: what to report and how to collect it

if you're grappling with the digital operational resilience act (dora) register, you've probably wondered about the financial data requirements what exactly do you need to report? and how can you make this data collection work smoothly? this article breaks down the specific reporting requirements, explains why they matter, and offers practical advice to help you navigate this compliance step importance of financial data in dora the financial data required in the dora register is critical for understanding your organization’s dependencies on ict service providers and ensuring regulatory compliance accurately reporting this data not only meets obligations but also helps your organization gain insights into its ict dependencies, manage outsourcing risks, and make informed strategic decisions the dora register requires detailed financial information related to ict service providers here’s a step by step guide to gathering and organizing this data effectively step 1 the contract perspective – rt 02 01 the first step is to take the contract perspective this is based on template rt 02 01, which focuses on individual contractual arrangements according to the implementing technical standards (annex i, part 2), you need to report annual expense or estimated cost of the contract for the past year (rt 02 01 0050) currency of the amount reported (rt 02 01 0040) when preparing the register, this means you need a breakdown of annual spend on ict providers at the contract level you can search the contract or sales order for pricing or ask a finance colleague for an overview of annual ict service provider spend, broken down per contract be mindful of the broad definition of an ict service provider to avoid missing any, conduct an inventory of in scope ict service providers first if you have multiple contracts with the same provider, refer to these its instructions total cost alignment all related arrangements must sum to the total cost of the overarching contract zero cost overarching arrangements if the top level contract has no cost, report cost at the level of each associated document unspecified sub arrangement costs if you can’t break it down, report total cost under the main contract costs at multiple levels avoid duplication by reporting cost only once per contract structure in practice, most contracts are standalone arrangements associated documents like dpas or addenda are usually not treated as separate contracts step 2 the ict provider perspective – rt 05 01 the second step is to take the ict provider perspective, based on template rt 05 01 it gives a consolidated view of annual spend per ict third party service provider you must report total annual expense or estimated cost per provider (rt 05 01 0070) currency of the amount reported (rt 05 01 0060) this is essentially the sum of contract level expenses from rt 02 01 per provider it applies only to external third party providers — not intra group ones ensure that totals reconcile between rt 05 01 and rt 02 01 identify all relevant contracts per provider common pitfalls and how to avoid them inconsistency between views reconcile contract level and provider level expenses to avoid discrepancies wrong reporting period use the actual or estimated annual cost for the past year failing to update this is not a one time task annual updates are required to keep financial data current conclusion and benefits financial data in your dora register isn’t just about compliance — it’s a tool for understanding ict risk and strategic decision making accurate financial reporting gives clarity into your digital supply chain although gathering and maintaining this data can be challenging, especially across templates, tools designed for dora compliance can automate data collection, ensure consistency, and simplify your reporting process if you want to take the pain out of building and maintaining the dora register and accelerate your progress reach out for a demo of our prebuilt dora register mailto\ info\@dora solutions com