Guide to Submitting DORA Registers of Information on the Central Bank of Ireland Portal

March 2025 Guide to Submitting DORA Registers of Information on the Central Bank of Ireland Portal

Guide to Submitting DORA Registers of Information on the Portal Central Bank of Ireland Page 2 Back to “Checklist”Back to “Checklist” Table of Contents Glossary of Terms.............................................................................................................. 4 Checklist ............................................................................................................................... 5

1. Overview.......................................................................................................................... 7 1.1 Purpose of this Guide........................................................................................... 7
2. System Information...................................................................................................... 8 2.1 Inactivity................................................................................................................... 8 2.2 Internet Browser ................................................................................................... 8 2.3 Logging On ............................................................................................................... 8 2.4 Uploading Attachments....................................................................................... 8 2.5 User Permissions ................................................................................................... 8 2.6 Messaging...............................................................................................................10
3. How to submit a Register of Information ...........................................................12 3.1 Navigating the DORA Registers Load File Screen ...................................12 3.2 Naming Convention for the Register of Information Return...............13 3.3 Correct Format.....................................................................................................14 3.4 Common Issues with the Register of Information Format....................16 3.5 Submission of a Register of Information on the Portal...........................18 3.5.1 Upload Register of Information..............................................................18 3.5.2 Addressing files which are ‘accepted with warnings’......................21 3.5.3 Finalise Register of Information.............................................................23 3.5.4 Sign off Register of Information .............................................................24
4. Viewing a previously submitted Register of Information on the Portal...28
5. Making Changes to a submitted Register of Information (auto-unlock) .28
6. Addressing Validation Errors when uploading to the Central Bank portal ................................................................................................................................................31 6.1 Guide to addressing Filing Rule Errors on the Central Bank Portal ...31 6.2 Guide to addressing Warnings on the Central Bank Portal ..................37

Guide to Submitting DORA Registers of Information on the Portal Central Bank of Ireland Page 3 Back to “Checklist”Back to “Checklist” 6.3 Guide to addressing Validation Errors on the Central Bank Portal ...41 6.3.1 Guide to addressing non-blocking errors on the Central Bank Portal ..........................................................................................................................42 6.3.2 Guide to addressing blocking errors on the Central Bank Portal46 7. EBA Feedback Files ....................................................................................................65 7.1 What to do with feedback files?......................................................................65 7.2 Addressing Validation Errors in EBA Feedback Files..............................66 7.3 EBA Feedback – Guide to addressing EBA Validation Errors in Feedback Files..............................................................................................................66 Rule Code 103..........................................................................................................67 Rule Code 305..........................................................................................................69 Rule Code 306..........................................................................................................70 Rule Code 330..........................................................................................................70 Rule Code 331..........................................................................................................71 Rule Code 503..........................................................................................................71 Rule Code 702..........................................................................................................72 Rule Code 703..........................................................................................................73 Rule Code 704..........................................................................................................74 Rule Code 714..........................................................................................................76 Rule Code 720..........................................................................................................77 Rule Code 723..........................................................................................................77 Rule Code 801..........................................................................................................78 Rule Code 805..........................................................................................................80 Rule Code 806..........................................................................................................81 Rule Code 807 in b_05.01....................................................................................82 Rule Code 807 General.........................................................................................83 Rule Code 808..........................................................................................................86 Rule Code 809..........................................................................................................86 Rule Code v88xx_m / v8888x_m .......................................................................87

Guide to Submitting DORA Registers of Information on the Portal Central Bank of Ireland Page 4 Back to “Checklist”Back to “Checklist” Rule Code VR_2 / VR_12 / VR_23 / VR_71 / VR_77 ....................................88 Rule Code VR_72 / VR_78....................................................................................88 8. Useful EBA reference guidance links ...................................................................91 Glossary of Terms Term Description C Code The financial entity’s identification number that is used for the Portal Central Bank The Central Bank of Ireland DORA Digital Operational Resilience Act (DORA) (Regulation (EU) 2022/2554) EBA European Banking Authority ESAs European Supervisory Authorities EU-ID European Union Identification Number ICT Information and Communication Technology LEI Legal Entity Identifier Portal The Central Bank of Ireland Portal used to submit Register of Information returns

Guide to Submitting DORA Registers of Information on the Portal Central Bank of Ireland Page 5 Back to “Checklist”Back to “Checklist” Checklist Financial entities subject to the Digital Operational Resilience Act (DORA) (Regulation (EU) 2022/2554) are required to submit Registers of Information in relation to all contractual arrangements on the use of ICT services provided by ICT third-party service providers, which they maintain in accordance with Article 28(3) of DORA. When submitting a DORA Register of Information return on the Central Bank of Ireland (Central Bank) Portal, the following checklist may be of assistance. • Registers of Information should be submitted via the Portal during the window specified on the DORA Reporting Registers of Information page for 2026. (If this changes in future years, updates will be issued prior to same). • The financial entity has followed the Implementing Technical Standard on the Register of Information1 , including subsequent clarifications via the ESAs Registers FAQ (available via the EBA register preparation site linked below) and the ESA DORA QAs. • The financial entity has reviewed and understands the information on the EBA website regarding preparations for reporting of DORA Registers of Information. In particular the slides on preparing the reporting package might help you. • The file type to be used by financial entities is a ‘plain-csv’ (xBRL OIM CSV) file in accordance with EBA taxonomy 4.0. In this regard, financial entities are strongly encouraged to review the above link to the EBA website on how to prepare the Registers of Information. • The name of the ZIP file (.zip) file adheres to the naming convention outlined in section 3.3 of this document. • The financial entity submitting a Register of Information return has a valid LEI code. 1 Commission Implementing Regulation (EU) 2024/2956

Guide to Submitting DORA Registers of Information on the Portal Central Bank of Ireland Page 6 Back to “Checklist”Back to “Checklist” • The financial entity has reviewed sections 3.3 (Correct Format), 3.4 (Common Issues) and section 6 (addressing validation errors) of this document before submitting a query to the Central Bank. • The ICT third-party service providers listed in the Registers of Information have valid LEI codes or EU-IDs in order for the returns to pass validation, along with meeting the other requirements mentioned above unless otherwise advised in ESA FAQs or ESA DORA QAs. • The users responsible for submitting, finalising and signing off the Registers of Information have the necessary access permissions to submit the DORA Register of Information on the Portal. Please see here for more details on Portal user permissions. • In the event that the financial entity’s or Central Bank’s systems are unavailable, or if experiencing technical issues with the Portal, please email onlinereturns@centralbank.ie or call 01 224 4545. If unable to submit Register of Information return, please contact the relevant supervisory team in the Central Bank using existing communication channels. Once any technical/operational issues have been resolved, the expectation is that the Register of Information return will be submitted on the Portal as soon as practicable.

Guide to Submitting DORA Registers of Information on the Central Bank of Ireland Portal Page 7 Back to “Checklist” Back to Checklist

1. Overview 1.1 Purpose of this Guide Financial entities subject to DORA are required to submit Registers of Information in relation to all contractual arrangements on the use of ICT services provided by ICT third-party service providers, which they maintain in accordance with DORA Article 28(3). Registers of Information should be submitted via the Portal on an annual basis. This document provides systems guidance for financial entities subject to DORA in relation to submitting Registers of Information on the Portal. The information contained in this guidance applies to financial entities in scope of DORA, where the Central Bank is the designated competent authority, and should be read in combination with other relevant documentation and legislative texts concerning DORA Registers of Information. In this guidance, examples of successful and unsuccessful submission of Registers of Information on the Portal are provided. It is the responsibility of the financial entity’s administrator to manage user access on the Portal. For users not familiar with the Portal, information and related guidance documents are available on the Central Bank’s website.

Guide to Submitting DORA Registers of Information on the Central Bank of Ireland Portal Page 8 Back to “Checklist” Back to Checklist 2. System Information 2.1 Inactivity A Portal login session times out after eight hours of inactivity, at which point the user is required to login again. When the user is finished using the Portal, it is recommended that the user exits the system using the logout link under “Account Settings” in the top right corner of the screen. 2.2 Internet Browser As explained in the Browser Support Section of the Portal webpage, the Portal should work with any modern, standards-based browser. The Central Bank does not require, or recommend, any particular browser as the Central Bank’s websites and public-facing applications support the current versions of all major browsers. Testing is concentrated on the most commonly used browsers. At this time, this specifically includes Chrome and Edge. 2.3 Logging On The Getting Started Help section of the Portal’s webpage provides information on how to register for and login to the Portal. 2.4 Uploading Attachments The type of document that may be uploaded is described in the “Messaging” section of the Portal. Please note the system supports up to a maximum size of 30MB per file uploaded. 2.5 User Permissions Please note users must have sufficient permissions to submit/finalise and sign off a Register of Information. If you are currently a portal user and do not have the relevant permissions, please contact your institution’s Portal administrator. You can reach out to your institution’s Portal administrator off-system or via the functionality in the Portal, which allows you to request a change of permissions on the system, as follows: How do I request a change to my permissions?

Guide to Submitting DORA Registers of Information on the Central Bank of Ireland Portal Page 9 Back to “Checklist” Back to Checklist Go to “Portal Administration” > “Manage Users” > Select the relevant user

Select “Actions” > “Manage Permissions”. Scroll to the bottom of the page and locate “ONR Returns”. From this section, “None”, “Viewer”, “Editor”, “Verifier” or “Editor & Verifier” access can be chosen. • None – Cannot see the return. • Viewer –Can see the return but cannot upload, finalise or sign off. • Editor – Can upload and finalise but cannot sign off. • Verifier – Cannot upload or finalise, can sign off. • Editor & Verifier –Can upload, finalise and sign off but cannot sign off a return they finalised. If you cannot see the Returns tab, please note the below: Portal administrators should activate their permissions via the Portal administrator tab. The Portal administrator receives automatic access to all return/report types, however in the scenario where the “View/Edit” option is not displayed, the following action should be taken: Go to “Portal Administration” > “Manage Users” > Select the relevant user > Select “Actions” > “Manage Permissions” > Scroll to the bottom of the permission page and select “Save”. Once saved, best practice is to clear the browser history and to log in again. The “Returns” menu item should then appear.

Guide to Submitting DORA Registers of Information on the Central Bank of Ireland Portal Page 10 Back to “Checklist” Back to Checklist 2.6 Messaging On the Portal, the user/delegate from your financial entity should receive a reminder message to submit the Register of Information. Please note if the message is not received there is still an obligation for the financial entity to submit the Register of Information annually. Registers of Information should be submitted via the Portal during the window specified on the Central Bank’s DORA Reporting Registers of Information page. The above is a sample of an automatically generated reminder email from the Portal, which can be found in the “messages” drop down menu highlighted below. “Dear Sir, Madam, Please note that the {ReturnTypeName}, for the institution {InstitutionIdentifier}, for the reporting period {ReportingDate} must be submitted via the Central Bank of Ireland Portal by {DueDate}. Regards, The Central Bank of Ireland”

Guide to Submitting DORA Registers of Information on the Central Bank of Ireland Portal Page 11 Back to “Checklist” Back to Checklist When you open the message from the Central Bank, an acknowledgement request will pop up. By clicking “Ok”, an acknowledgement will be sent to the Central Bank. Do not reply to this message as this will not be monitored. Any further queries should be sent through the usual support channels.

Guide to Submitting DORA Registers of Information on the Central Bank of Ireland Portal Page 12 Back to “Checklist” Back to “Contents” Once you have received a request from the Central Bank through the Portal for a submission, you can navigate to the “Returns” View/Edit Returns tab to submit your Register of Information. 3. How to submit a Register of Information 3.1 Navigating the DORA Registers Load File Screen To submit a Register of Information, the user logs in to the Portal with their user details, navigates to the “Returns” tab and clicks “View / Edit Returns”. The return is located under the “DORA Registers” heading. You will only see the DORA Register applicable to your financial entity. Click on the hyperlink for the relevant DORA Register. This opens the return landing page where the user can load a file or View/Edit previously uploaded returns. To load a file click on “Load a File”.

Guide to Submitting DORA Registers of Information on the Central Bank of Ireland Portal Page 13 Back to “Checklist” Back to “Contents” The “Load a File screen” allows the user to submit a Register of Information return to the Central Bank. The elements of the Load a File screen above are as follows:

1. Choose File Pressing the “Choose File” button opens the user’s file explorer. From here, the relevant Register of Information file can be selected.
2. Load File Where the selected file adheres to the naming conventions and appears beside “Choose File,” click on the “Load File” button to load the file.
3. Cancel Clicking on the “Cancel” button returns the user to the Register of Information Portal screen. 3.2 Naming Convention for the Register of Information Return The register filename must adhere to the following naming convention: CCCCCCC_YYYYMMDD_CBIREGISTERNAME Where: CCCCCCC – is the financial entity’s C code. (Note – this is the numerical section of the financial entity’s number preceded by “C” and NOT the institution number. Where the institution number is CBI0012345, the C Code will be C12345). YYYYMMDD – is the reporting date in the format year, month, day. 1 2 3

Guide to Submitting DORA Registers of Information on the Central Bank of Ireland Portal Page 14 Back to “Checklist” Back to “Contents” CBIREGISTERNAME - is the name of the register as outlined in this guide and as displayed on screen when you are loading a return. 3.3 Correct Format This section does not touch on correcting the data within the templates in your RoI. Further guidance on addressing more complex issues with your RoI is provided in section 6. Rather, this section contains high level guidance on how to structure the format of your RoI file to have it in the best condition for a successful submission. Particularly useful is the EBA site in the section on “Preparations for Official Reporting of Registers” which includes slides on how the file should look. The below screenshot from the site illustrates the correct file structure. The top level zipped file should be saved as follows:

Guide to Submitting DORA Registers of Information on the Central Bank of Ireland Portal Page 15 Back to “Checklist” Back to “Contents” Which should contain a folder, of the same name:

Which should, in turn, contain the following folders:

This is what the compiled file should look like (example with a test MiFID firm C999001): The META-INF folder should then contain the reportPackage json file: And the report folder should contain the reporting templates and appear as shown below:

Guide to Submitting DORA Registers of Information on the Central Bank of Ireland Portal Page 16 Back to “Checklist” Back to “Contents” 3.4 Common Issues with the Register of Information Format Ensure you are referencing the correct EBA taxonomy 4.0 schema (“http://www.eba.europa.eu/eu/fr/xbrl/crr/fws/dora/4.0/mod/dora.json”) in the report.json file, per the screenshot below. • NEW for 2026: Also in the report.json file, you should have adhered to EBA filing rules 5.7, whereby the report.json file in the reports folder should contain information on the software used to generate the file. This is new for 2026. It is not a mandatory inclusion, but if you include it and do not include all relevant elements, it will cause a warning error. There is more information on this warning error in section 6.2. • Information on the software component used for production of the XBRL report SHOULD be included as a json element in the report.json file. It is not mandatory, but if you include it, it SHOULD use the EBA element with the name generatingSoftwareInformation and provide an id, a version and creation date. If you include it, you will get an error if these three elements are not included. Additional information can be added through the element softwareAdditionalInfo. Example of valid report.json contents:

Guide to Submitting DORA Registers of Information on the Central Bank of Ireland Portal Page 17 Back to “Checklist” Back to “Contents” • If you generated your register manually, and include the ‘generating software information’ element, an example of valid report.json contents is as follows: • Ensure there are no spaces in the filename. • Ensure the date formatwithin the files are correct – i.e. YYYY-MM-DD. *Do not edit your templates in Excel as this will automatically save the dates in an incorrect format. Use Notepad or your security-approved text editor for any manual edits. • Ensure you have LEI and not CNUM in the parameters.CSV file. • Ensure you have rs: in front of the LEI number in the parameters.CSV file. This stands for ‘report subject’. • Ensure you have ‘.CON’ or ‘.IND’ after your LEI code in the parameters file.

Guide to Submitting DORA Registers of Information on the Central Bank of Ireland Portal Page 18 Back to “Checklist” Back to “Contents”

• Ensure there are no €£$ symbols in the csv files. • Further issues which can prevent submission of your Register are described in section 6 of this document. 3.5 Submission of a Register of Information on the Portal There is a three-step process for submitting the Register of Information via the Portal as outlined below. Please note the same user cannot finalise and sign off the upload. 3.5.1 Upload Register of Information The uploading user must be assigned “Editor Access” by their Portal Administrator. When the register file is chosen from the file explorer (as outlined in section 3.1), it appears on screen as below.

Guide to Submitting DORA Registers of Information on the Central Bank of Ireland Portal Page 19 Back to “Checklist” Back to “Contents” Select “Load File”. The File Upload Status screen appears as below. The initial “File Status” appears as “Processing”. The status progresses through the following stages: Progressing through these stages is automatic and can be quick, to the extent that they may only appear briefly on screen. Processing Validating Accepted Rejected

Guide to Submitting DORA Registers of Information on the Central Bank of Ireland Portal Page 20 Back to “Checklist” Back to “Contents” Depending on website traffic volumes, the majority of files should be processed within five minutes. Clicking on “Refresh Page” updates the user on the current file status. Upon the successful completion of the uploading process, the file status appears as “Accepted” and the processed date displayed. The user also receives a confirmation email detailing the outcome of the submission. This email is sent to the address that the user has registered with the Portal, and is only sent to the user that has submitted the return. An example of the content of such a confirmation email is set out below.

Guide to Submitting DORA Registers of Information on the Central Bank of Ireland Portal Page 21 Back to “Checklist” Back to “Contents” On the Portal upload screen, clicking on “Back”, redirects the user to the “View Uploaded Files” screen, where the user can view all previously uploaded files, the submission type, who uploaded the file, date of upload and the status. A sample of this information is set out below. The user can also access this screen from the main DORA Register Returns page by click on the “View Uploaded Files” button. 3.5.2 Addressing files which are ‘accepted with warnings’ “The file 'C999001_20250331_DORAREG_MiFID.zip' has been processed. This is an automatically generated message. Please do not reply to this email.”

Guide to Submitting DORA Registers of Information on the Central Bank of Ireland Portal Page 22 Back to “Checklist” Back to “Contents” In some instances, the user will receive a confirmation email detailing the outcome of the submission noting that the file has been accepted with warnings. An example of such a confirmation email is set out below. The file 'C999001_20250331_DORAREG_MiFID.zip' has been processed. This file has been accepted with warnings. This is an automatically generated message. Please do not reply to this email. If the file is processed with warnings, the user can view the warning by completing the following steps: Go to “Returns” > “View/Edit Returns” > select the DORA Register Return > Select “View Uploaded Files” > Select the file. This will bring you to the below screen, please ensure that you download the warnings file and address these warnings, as they could result in a rejected submission at EBA: When you download and open the 'Warnings' file you will see the <warning message> section of this. This is the part which will tell you which template and row the error is in e.g. template B_03.02 row 1 - where the first column is c0030. The message also tells you the value where the issue is. You should correct these errors before re-submitting the return. See also section 6.2 for more detailed information on this.

Guide to Submitting DORA Registers of Information on the Central Bank of Ireland Portal Page 23 Back to “Checklist” Back to “Contents” 3.5.3 Finalise Register of Information The submitting user, with editor access, must finalise the uploaded Register of Information by clicking on the “View/Edit Returns” button. To finalise, the user must click on the “reporting date” link for the register and then, on the next screen, click “Finalise”. The following screen appears with a message “This Return is 'Finalised' - it must now be 'Signed-Off' to be submitted to the Central Bank. Use the back button to navigate to the previous page.” Please note the same user cannot finalise and sign off a Register of Return.

Guide to Submitting DORA Registers of Information on the Central Bank of Ireland Portal Page 24 Back to “Checklist” Back to “Contents” 3.5.4 Sign off Register of Information A different user must be assigned “Verifier” access by the financial entity’s portal administrator. Navigate to Returns > View/Edit Returns > DORA Registers > Select the register for your financial entity.

Guide to Submitting DORA Registers of Information on the Central Bank of Ireland Portal Page 25 Back to “Checklist” Back to “Contents” To sign off, the user clicks on the reporting date link for the register that displays a status of “Finalised”. Click on the “View/Edit Returns” button.

Guide to Submitting DORA Registers of Information on the Central Bank of Ireland Portal Page 26 Back to “Checklist” Back to “Contents” The user clicks “Sign-Off”. Once the Declaration Screen opens, the user clicks the checkbox to signify acceptance of the statement and then select “sign-off return”. The user will receive a confirmation email detailing the outcome of the sign off. This email is sent to the address that the user has registered with the Portal and is only sent to the user that has submitted the return. An example of the content of such a confirmation email is set out below.

Guide to Submitting DORA Registers of Information on the Central Bank of Ireland Portal Page 27 Back to “Checklist” Back to “Contents” “You have successfully 'signed-off' DORA Register MiFID for Institution : CRDIV Test Firm 1 (C999001) Return Type : DORA Register MiFID Reporting date : 31-Dec -2025 Revision Number : 1 This return has now been submitted to the Central Bank, is 'locked' and cannot be changed until it is unlocked for revision by the Central Bank. Regards Central Bank Of Ireland”

Guide to Submitting DORA Registers of Information on the Central Bank of Ireland Portal Page 28 Back to “Checklist” Back to “Contents” 4. Viewing a previously submitted Register of Information on the Portal Go to “Returns” > “View/Edit Returns” > select the DORA Register Return > Select “View/Edit Return” > Select the file Click on “Download Excel” to download the Register of Information. 5. Making Changes to a submitted Register of Information (auto-unlock) Before requesting for an auto-unlock the user must have the required permissions. Go to “Portal Administration” > “Manage Users” > Select the relevant user > Select “Actions” > “Manage Permissions” > Scroll to “Request Changes” > “Unlock Request” and tick the box to assign the permission to the user. Select Click on the file.

Guide to Submitting DORA Registers of Information on the Central Bank of Ireland Portal Page 29 Back to “Checklist” Back to “Contents” “Save”. Once saved, best practice is to clear the browser history and to log in again. If there are changes required after signing off the Register of Information, a user with verifier access can request for an auto unlock of the return. The user logs in to the Portal with their user details, navigates to the “Returns” tab and clicks “View / Edit Returns”. The return is located under the “DORA Registers” heading. You will only see the DORA Register applicable to your financial entity. Click on the hyperlink for the DORA Register. Click on “View/Edit Returns”.

Guide to Submitting DORA Registers of Information on the Central Bank of Ireland Portal Page 30 Back to “Checklist” Back to “Contents” Click on the “reporting date” for the Register of Information that has been already signed off. Select "Create Request". A list of the available requests for your financial entity that you have permission to view/create will be displayed. If you cannot see the “Create Request” change menu item or a specific request change option you should contact your Portal Administrator. Select "Unlock Return".

Guide to Submitting DORA Registers of Information on the Central Bank of Ireland Portal Page 31 Back to “Checklist” Back to “Contents” Complete the form. Instructions are displayed on the top of the screen and mandatory fields are denoted by a red asterisk. The mandatory fields vary depending on the specific request. Click “Submit”. The system will automatically unlock the Register of Information, and you will be able to submit a new one. Please see section 3.5 above for more information on the submission process. 6. Addressing Validation Errors when uploading to the Central Bank portal In addition to the Common Issues noted in Section 3.4, there may be other instances where the submission of a Register of Information is rejected, or the user encounters errors when trying to upload a return on the Portal. This section contains a non-exhaustive guide for such instances. 6.1 Guide to addressing Filing Rule Errors on the Central Bank Portal Certain errors will be related to filing rules. These are related to the basic structure, naming and content of your return, at a file level. When the Central Bank system processes your file, if even one of these filing rules is broken, it will cause an error that will prevent your file from being successfully submitted. These errors, by their nature, will only show one at

Guide to Submitting DORA Registers of Information on the Central Bank of Ireland Portal Page 32 Back to “Checklist” Back to “Contents” a time. Therefore it is essential, to avoid these ‘one-at-a-time’ errors, to ensure your files meet these filing requirements. In this respect, it is important to follow the guidance in sections 3.2, 3.3 and 3.4 in this document and to note the following:

1. Ensure the file type used is a xBRL OIM-CSV file in accordance with EBA taxonomy 4.0. Also ensure that the name of the ZIP file (.zip) file adheres to the naming convention specified on the Central Bank Portal upload page. E.g. for MiFID entities CCCCCCC_YYYYMMDD_DORAREG_MiFID where CCCCCCC is the institution C-Code and YYYYMMDD is the reporting date/reference date for the data – i.e. for the Q1 2026 submission, this will be 20251231.
2. Ensure the file name is correct.

Guide to Submitting DORA Registers of Information on the Central Bank of Ireland Portal Page 33 Back to “Checklist” Back to “Contents” 3. Ensure that the Financial Entity’s LEI is in upper case. 4. Ensure the LEI is correct. The Portal processor will try to match the C￾Code with the LEI in the parameters file. This should also match your firm’s entry in the GLEIF If these are not aligned this will cause this error: 5. Ensure that the same return for the same reporting date is not already signed off. It will need to be unlocked per section 5 if this is the case.

Guide to Submitting DORA Registers of Information on the Central Bank of Ireland Portal Page 34 Back to “Checklist” Back to “Contents” 6. Ensure the file is not double zipped.

Guide to Submitting DORA Registers of Information on the Central Bank of Ireland Portal Page 35 Back to “Checklist” Back to “Contents” 9. Ensure the LEI is correctly populated in the parameters file. 7. Ensure the C Code is correct in the file name. 8. Ensure the reporting date in the filename is correct.

Guide to Submitting DORA Registers of Information on the Central Bank of Ireland Portal Page 36 Back to “Checklist” Back to “Contents” 10. Ensure the file has a parameters file. 11. Ensure the files are not empty.

Guide to Submitting DORA Registers of Information on the Central Bank of Ireland Portal Page 37 Back to “Checklist” Back to “Contents” 12. Ensure the file has a FilingIndicators.csv file. 13. Ensure the file has a reportPackage.JSON file. 6.2 Guide to addressing Warnings on the Central Bank Portal Certain errors will be related to warning rules. These are related to the content with your register. Per section 3.5.2 of this document, these warnings should be addressed before your return can be finalised and signed off. This section provides some more information on how to do this.

Guide to Submitting DORA Registers of Information on the Central Bank of Ireland Portal Page 38 Back to “Checklist” Back to “Contents” Although the file status says 'accepted', when you click on 1 - 'Returns', and 2 - 'View / Edit Returns' (or use the dropdown menu in the centre screen per the second screenshot below), you will see the returns you have submitted and you will see the status of the most recent file says 'Invalid'. The other point you will see this is when you go to sign off the file You will see it says the file has been ‘accepted with warnings’. You will also receive an email which will contain the same message.

Guide to Submitting DORA Registers of Information on the Central Bank of Ireland Portal Page 39 Back to “Checklist” Back to “Contents” Next click on the 'Reporting Date' link (3) for the 'Invalid' file. This is also accessible through the top menus per the screenshot below: This will bring you to the below screen, please ensure that you download the warnings file and address these warnings, as they will result in a rejected submission at EBA: You should check the warnings at this point and address them. If you have signed off the file before you realise, you will need to get the return unlocked via the auto-unlock function, as described in section 5

Guide to Submitting DORA Registers of Information on the Central Bank of Ireland Portal Page 40 Back to “Checklist” Back to “Contents” and re-submit the file once the warnings are addressed. When you download and open the 'Warnings' html file (within a zip file), you will see a file similar to the below screenshot. You will see the <warning message> section. This is the part which will tell you which template and row the error is in. In the example below, the error is in template B_03.02 row 1 - where the first column is c0030. This is highlighted in yellow below. The message also tells you the value where the issue is, e.g. "Value: …TEST1". You will see the ‘leading space’ in front of this value in this example. Or it could have a space after the value (‘trailing space’). These unnecessary spaces will cause errors in these primary/foreign key values. You should correct these errors before re-submitting the return. Examples of these are highlighted in blue below. These are examples of where there is a leading or trailing space in a field which should have text or alphanumeric characters in it. Leading and trailing spaces in these fields should be removed: The example below relates to String facts - Leading white space, located in B_01.01, row 1, column 020, B_01.03.0030 and B_05.01.0050.

Guide to Submitting DORA Registers of Information on the Central Bank of Ireland Portal Page 41 Back to “Checklist” Back to “Contents” In this instance, the warning message gives the row and column where the error is and not the value, but it does give the column and row so you will know where to look for the error: Another such example, is where you have included ‘generating software information’ in the report.json file, but have not included all required elements of this (see section 3.4 of this document). This results in the following warning, which tells you the EBA rule which has not been followed and what should be in the file, i.e. software ID, version and creation date: 6.3 Guide to addressing Validation Errors on the Central Bank Portal For the current submission the Central Bank has made improvements and enhancements to the validations performed on its Portal. This includes improved error messages and additional upfront validations which were not performed, until the reports were submitted to the EBA, in 2025. There are two types of validations: – Non-blocking errors – you can fix these and resubmit or just comment on these and submit without fixing if appropriate; and – Blocking errors – these will have to be remediated before you can signoff and submit your return. These are explained further in the sections below.

Guide to Submitting DORA Registers of Information on the Central Bank of Ireland Portal Page 42 Back to “Checklist” Back to “Contents” 6.3.1 Guide to addressing non-blocking errors on the Central Bank Portal Certain errors are designed to be non-blocking, as designated in the EBA Validation rules. These are related to the content within your register. With these errors, you will need to perform an action on the Central Bank Portal for the return to be processed. The errors alert you to the potential data quality issues within your register. This will allow you to fix them as appropriate, before you sign them off. Alternatively, you may also just add a comment within the Portal to explain the discrepancy and continue with processing the submission, as described below. Similar to the ‘warnings’, when you click on 1 -'Returns', and 2 - 'View / Edit Returns' (or use the dropdown menu in the centre screen per the screenshot below), you will see the returns you have submitted and you will see the status of the most recent file (3) says 'Invalid'. Next click on the 'Reporting Date' link for the 'Invalid' file. The screen below will appear. You will see in this screen there are two 'Sections' linked. The second 'Section' is the 'Xbrl Non Blocking Rules Report'. Click on the link for this report.

Guide to Submitting DORA Registers of Information on the Central Bank of Ireland Portal Page 43 Back to “Checklist” Back to “Contents” This will bring you to the table shown in the screenshot below. The table will note the applicable EBA rule code for the validation rule which has been broken. You will see a description of the error in the second column, the relevant template in the third column, the offending value in column four and column code in column 5 and a more detailed technical description of the error in column 6. If the error is, for example, related to an incorrect LEI code and you do have valid LEI codes, then this table provides an opportunity to review the codes you have entered, check where the errors are, correct them in your return and resubmit. If you do not have data to fix the error, Column 7 - 'Explanation', is where action is required. Some text needs to be entered here in order to be able to move to the next step and finalise your return. This can be any text explaining the discrepancy. You will need to click on 'Edit Data'. This will allow entering text to this column. These errors are 'non-blocking' errors, as defined by the EBA, so they will not prevent your file from being submitted on to the EBA; however, they should be corrected where possible.

Guide to Submitting DORA Registers of Information on the Central Bank of Ireland Portal Page 44 Back to “Checklist” Back to “Contents” Once you have clicked on 'Edit Data', the below, editable screen will appear. Enter your text in the 'Explanation' column, ensuring you have entered text in every row. Then click on 'Save Form. You may notice in the 'Row Identifier' column that there is more than one value. This column displays the key value(s) that uniquely identify that row in the templates. This may be one column or a combination of columns, based on the designation in the EBA Data Model. So you may see one value in this column, or a combination of values, as in the example below.

Guide to Submitting DORA Registers of Information on the Central Bank of Ireland Portal Page 45 Back to “Checklist” Back to “Contents” If you then click on the reporting date in the following screen, it will bring you back to the relevant returns. You will see the report submitted now has a status of 'Valid' and can be Finalised, and then Signed Off by your firm's reviewer.

Guide to Submitting DORA Registers of Information on the Central Bank of Ireland Portal Page 46 Back to “Checklist” Back to “Contents” Some examples of such errors are: • Leading or trailing spaces in fields; • In template B_01.02, if the country code in column c0030 does not match the registered country in the GLEIF for the LEI code in that template; • In template B_05.01, if the value in column c0020 identifies that an LEI code is being used as the identifier in column c0010, but the value in c0010 is not a valid LEI code per the GLEIF, you will get a non-blocking error. The same applies to columns c0030 and c0040 in this template. 6.3.2 Guide to addressing blocking errors on the Central Bank Portal Certain errors are designated as blocking, per the EBA Validation rules. These are related to the content within your register which must match certain logic to be accepted. These errors will cause your file to be ‘rejected’ and must be addressed and your file resubmitted before it can be signed off and submitted. The initial submitter can address these errors prior to finalising, so it can be done before the point where the file would have to be unlocked. A number of examples of such errors are given in this section. This is a non￾exhaustive list of such errors, while still being comprehensive enough to provide enough guidance for you to be able to address similar errors you may come across. You may get a number of these errors showing up in one submission attempt, so please search for the error wording in this section if you are unclear as to how to remediate them. The wording for these errors has been enhanced to make the problem clearer. Therefore, it should be clear from the error what needs to be done to address it.

Guide to Submitting DORA Registers of Information on the Central Bank of Ireland Portal Page 47 Back to “Checklist” Back to “Contents” There is only one such error where this may not be the case and this is the first one documented below – missing key values. Missing Key Values If one of your reporting templates is missing one of more key values, the processor will not be able to further process the file and will throw out a lot of errors. You will see many errors caused by this one omission, so if you check the errors specifically to see if they start with "[Ins Err, 2] xbrldie:PrimaryItemDimensionallyInvalidError : The primary item contains invalid hypercubes in all base sets...". This is an indication that you have left a Key Value field blank. Check the ITS and Annotated tables in EBA links if you are not sure which are key value fields. For example, in the below, there is no data in column c0010: This leads to the file being rejected and generates the following 1.7.1 filing rule errors:

Guide to Submitting DORA Registers of Information on the Central Bank of Ireland Portal Page 48 Back to “Checklist” Back to “Contents” Report templates with only column headers and no data If you submit a file that has everything correct, but the reporting templates within the files only have column headers and no data in them, the file will be rejected as the templates need to be populated. In this instance when you upload your file it will be rejected and the error you will get will be as follows: "Error: OIM-CSV Validation failed. The OIM CSV package does not contain the required populated template files"

Guide to Submitting DORA Registers of Information on the Central Bank of Ireland Portal Page 49 Back to “Checklist” Back to “Contents” Root folder name different than zip file name The root folder within the zip file should have the same name as the zip file (minus the '.zip'), the format of which is given on the portal site where you load the file. If you have incorrectly named the zip file you will get the error: "Error: Validation STOPPED: The inner directory of the OIM-CSV file should be the same as the Filename (minus the .zip)" FIX - ensure the zip file and root folder within have the same name, per section 3.3 of this guide. Report.json file is missing or named incorrectly Files with this issue will be rejected upon loading with the error saying "Error: Cannot determine Taxonomy Schema Reference, cannot locate report.json file"

Guide to Submitting DORA Registers of Information on the Central Bank of Ireland Portal Page 50 Back to “Checklist” Back to “Contents” Ensure your report.json file is included and named correctly. Taxonomy reference errors in report.json file Error: Cannot determine Taxonomy Schema Reference, it is not available in report.json The schema used for the return should be referenced in the report.json file

• in this case it is data model 4.0 (DPM 4.0) - same as used for the 2025 return. This should be referenced in the report.json file as highlighted below. The correct reference to be used in this can be found at the site for the relevant reporting framework, for Q1 2026 this is: https://www.eba.europa.eu/risk-and-data-analysis/reporting/reporting￾frameworks/reporting-framework-40, then download b. Taxonomy package under taxonomy architecture v2.0, open EBA_XBRL_4.0_Reporting_Frameworks_4.0.0.0.zip, then open META-INF and open taxonomyPackage and it is in there:

Guide to Submitting DORA Registers of Information on the Central Bank of Ireland Portal Page 51 Back to “Checklist” Back to “Contents” If it is missing, like the below: You will see the error: Or if there are multiple taxonomies referenced, for example in the below, the DORA DPM 4.0 and COREP 4.0 are both referenced in the report.json file You will see the error:

Guide to Submitting DORA Registers of Information on the Central Bank of Ireland Portal Page 52 Back to “Checklist” Back to “Contents” Or if the taxonomy is incorrect e.g.: COREP taxonomy schema referenced instead of DORA: You will get the error: "Taxonomy schema reference is not consistent with the type of return…" Or the schema is referenced incorrectly:

Guide to Submitting DORA Registers of Information on the Central Bank of Ireland Portal Page 53 Back to “Checklist” Back to “Contents” The correct reference to be used in this can be found at the site for the relevant reporting framework, e.g. for this cycle: https://www.eba.europa.eu/risk-and-data-analysis/reporting/reporting￾frameworks/reporting-framework-40, then download b. Taxonomy package under taxonomy architecture v2.0, open EBA_XBRL_4.0_Reporting_Frameworks_4.0.0.0.zip, then open META-INF and open taxonomyPackage and it is in there The error will be "… unresolvable URL: <incorrect URL link>": Or there can even be just a small typo in the schema reference URL, e.g.:

Guide to Submitting DORA Registers of Information on the Central Bank of Ireland Portal Page 54 Back to “Checklist” Back to “Contents” This will also result in the error "Taxonomy schema reference is not consistent with the type of return": Filing Indicator issues in FilingIndicators.csv file All templates must be reported as true in the FilingIndicators file. So if, for example, the FilingIndicators file was reported but blank apart from headers: You will get the following errors indicating that there are missing filing indicators and the filing indicators that are missing: "Error: [FR-MUST: EBA_CSV_1.7.1: reportedFactAssociatedWithNoPositive

Guide to Submitting DORA Registers of Information on the Central Bank of Ireland Portal Page 55 Back to “Checklist” Back to “Contents” FilingIndicator] A fact not referenced by a filing indicator exists {No positive filing indicator declared in the instance - all of reported facts are not referenced by any filing indicator}" and "Error: [FR-MUST: EBA_CSV_9.4: 808-filingIndicatorError] Missing filing indicators (B_99.01, B_07.01, B_06.01, B_05.02, B_04.01, B_03.03, B_03.02, B_02.02, B_02.01, B_05.01, B_03.01, B_02.03, B_01.03, B_01.02, B_01.01). An XBRL report MUST provide a filing indicator for each reporting unit ('template') defined in the DORA module" If a filing indicator is reported twice in the FilingIndicator file, e.g:

Guide to Submitting DORA Registers of Information on the Central Bank of Ireland Portal Page 56 Back to “Checklist” Back to “Contents” You will get the error "Error: [FR-MUST: EBA_CSV_9.4: 808- filingIndicatorError] Duplicated filing indicators (B_XX.XX)": Or if there was more than one duplicated "Error: [FR-MUST: EBA_CSV_9.4: 808-filingIndicatorError] Duplicated filing indicators (B_XX.XX, B_XX.XX)": Invalid Filing Indicators If you include filing indicators in the file which are invalid in some way, e.g. see 2 invalid indicators included in file below:

Guide to Submitting DORA Registers of Information on the Central Bank of Ireland Portal Page 57 Back to “Checklist” Back to “Contents” You will get the errors "[FR-MUST: EBA_CSV_1.6.3: invalidFilingIndicatorValue] A filing indicator value does not belong to the list of filing indicator values declared in the referenced module {X_XX.XX}"; and “File is rejected for Error: [FR-MUST: EBA_CSV_9.4: 808-filingIndicatorError] Invalid filing indicators (X_XX.XX). The values of filing indicators MUST only be those given by the label resources with the role http://www.eurofiling.info/xbrl/role/filing-indicator-code applied to the relevant tables in the XBRL taxonomy for DORA module. Filing indicator values must be formatted correctly (for example including any underscore characters and must be in capital letters)":

Guide to Submitting DORA Registers of Information on the Central Bank of Ireland Portal Page 58 Back to “Checklist” Back to “Contents” Decimals value issues in parameters.csv file This checks the decimal values against what is set in the 'parameters' file. E.g. E.g. if you have the decimal value in the parameters file set to '-5' as in the example above, per the EBA filing rules version 5.6 (https://www.eba.europa.eu/sites/default/files/2025-05/681d27b9- 6744-4b7c-bea7- 848cb910844e/EBA%20Filing%20Rules%20v5.6_2025_05_27.pdf) this means that the monetary values will be accurate to the nearest 100,000 (i.e. =/- 0.5 x 10 -decimal setting, in this case, 0.5 x 10--5 (i.e. 0.5 x 105 )= within (+/-) 50,000 of the actual value. The EBA filing rules require the accuracy to be at least to the nearest 10,000 (i.e. a setting of -4 i.e. accurate +/- 5,000). So the 'Decimal' setting should be >= -4 (e.g. -3, -2 are also valid depending on how accurate your numbers are). If the value for decimals doesn't meet the requirements per the EBA filing rules you will get the below error "Decimals value is too low" and it will also give the corresponding monetary values within the templates which are related to this:

Guide to Submitting DORA Registers of Information on the Central Bank of Ireland Portal Page 59 Back to “Checklist” Back to “Contents” Also in the parameters file, the DecimalsInteger setting should meet the requirements per the EBA filing rules and should not have any decimal places, i.e. the integer setting should be '0': So if for example your integer setting is at -3: You will get the following error, which you can see says the Decimal value is not equal to zero and then refers to the IntegerItemType.Decimals values which are incorrect: Incorrect prefix before LEI code in parameters file You need to have 'rs:' before your LEI code in the parameters file. This stands for 'reporting subject', anything else will cause the file to be rejected, e.g.:

Guide to Submitting DORA Registers of Information on the Central Bank of Ireland Portal Page 60 Back to “Checklist” Back to “Contents” Or Will cause an error like "…2.8: InappropriateScheme… ": Or: "… Unbound prefix: sr" where sr was entered instead of 'rs'

Guide to Submitting DORA Registers of Information on the Central Bank of Ireland Portal Page 61 Back to “Checklist” Back to “Contents” LEI instead of RS before LEI code: Filing Indicators must be reported as 'true' or '1' in FilingIndicators.csv file If you have incorrect values for filing indicators such as the '0' or 'false' below: You will get an error like "reportedFactAssociatedWithNoPositiveFilingIndicator - A fact not referenced by a filing indicator exists"; and "Error: [FR-MUST: EBA_CSV_9.4: 808-filingIndicatorError] Invalid filing indicators (B_05.01=0, B_07.01=false). Reported Filing Indicators must have values of either 'true' or '1'":

Guide to Submitting DORA Registers of Information on the Central Bank of Ireland Portal Page 62 Back to “Checklist” Back to “Contents” Invalid Fact Value errors If an incorrect/ invalid value is entered for one of the values which should come from a defined drop-down list per the EBA preparation site, the file will be rejected and you will see an error similar to the below. Where you get an error like this, your best option is to do a ctrl-F to find the offending value in your register, from the examples below you can see these offending values are 'eba_GA: CAUS', 'eba_GA: XW' and 'eba_GA: VIX'. If you search for each of the values pointed out in the error and replace them with the correct value from the drop down lists available per the EBA preparation site. See section 8 with links to these useful EBA links. There are snips of these errors below as the actual errors contain all the potential valid values and are therefore too long to include here.

Guide to Submitting DORA Registers of Information on the Central Bank of Ireland Portal Page 63 Back to “Checklist” Back to “Contents” Valid Dimension in incorrect column Similarly, if you put a valid dimension code (from drop down lists – e.g. country code, currency code etc) in the incorrect column, you will get a similar error "Error: Message: [enumie: InvalidFactValue] The value 'eba_GA: XX' of the item 'eba_met_3.5: ei1552' is invalid": E.g. in the below C0020 and c0040 in b_02.01 contain valid dimensions, but from the wrong list of drop down values. e.g. c0020 contains the code for a currency which should be in c0040 and vice versa:

Guide to Submitting DORA Registers of Information on the Central Bank of Ireland Portal Page 64 Back to “Checklist” Back to “Contents” Rule 807 – Referential Integrity Checks - key-foreign key constraints If you have data in your registers which does not follow the referential integrity (key/ foreign-key) rules described in the EBA Data Model, you will get the following error: “Formula Error: eba_807_1 : B_XX.XX, c00XX is not in list {b_XX.XX, c00XX}. Rule check: The reported data must follow the key-foreign key constraints defined in the DPM. Reported value: XXXXXXXX. Template: B_XX.XX Row: XXXXXXXXX Column 00XX.” An example of this error can be seen in the screenshot below.

Guide to Submitting DORA Registers of Information on the Central Bank of Ireland Portal Page 65 Back to “Checklist” Back to “Contents” You can see these key/foreign-key relationships illustrated at the top of the EBA data model document (see section 8 for links to key EBA reference documents). Also in this document, it is specified whether a given data field is a foreign key field or not. This means the values in these fields must be defined either in the same table or in another table. For more information on resolving this error, please refer to the sections ‘Rule Code 807 in b_05.01’ and ‘Rule Code 807 General’. 7. EBA Feedback Files Upon successful submission of the Register of Information via the Central Bank Portal, it is transmitted to the EBA by the Central Bank. Once EBA validation checks have been completed, a feedback file will be sent to the Central Bank supervisor. Please note that if there are further validation errors to be addressed, the Central Bank supervisor will send the feedback results to the financial entity via the Portal Secure Messaging service for the financial entity to make any necessary changes. 7.1 What to do with feedback files? Firms should save the feedback file, received from their supervisor via the Central Bank of Ireland Portal, locally, with a shortened filename in order to avoid any issues around long filepath. The first Feedback File is likely to be a Feedback Failed (NOK) file and the second file-type will be a results (RES) file with details on the LEI and EU-ID checks. Within the feedback file zip package, there is a detailed feedback file, e.g.: This feedback file contains the validation errors which you will need to work through, row-by-row/ template by template, and update your register accordingly. Please refer to Section 7.3 for assistance on addressing these feedback errors. Once you have corrected the errors identified in the EBA feedback file, you will need to unlock your register return (as per section 5 of this guidance) and submit your updated Register package through the Central Bank portal.

Guide to Submitting DORA Registers of Information on the Central Bank of Ireland Portal Page 66 Back to “Checklist” Back to “Contents” When you receive the EBA results (RES) feedback file, if the only issues identified in this file relate to third party providers for whom you don’t have an LEI or EU-ID and for whom you have entered another identifier (as described in EBA FAQ 39), the EBA have advised in their FAQ that this is permitted for 2025 data, even though it is still identified as a Data Quality (DQ) issue. Therefore you can let your supervisor know that your only remaining DQ issues are related to those providers for whom you do not have an LEI or EU￾ID and that all other DQ issues have been remediated and your submission is as complete as possible for the current reporting period. You should continue to push your providers to ensure they have provided a valid LEI or EU-ID in time for your next register submission. 7.2 Addressing Validation Errors in EBA Feedback Files This section and the next section contain guidance to help address DORA register EBA feedback file errors. It identifies common errors noted within the feedback files received from the EBA, following the technical and data quality validations they are performing, and provides guidance to FEs in addressing these errors. The format of the validation errors is per below, giving the template code, the row code, the column code, the error code, the error message and the value that prompted the error: 7.3 EBA Feedback – Guide to addressing EBA Validation Errors in Feedback Files This section contains guidance to help address DORA register EBA feedback file errors. It identifies common errors noted within the feedback files received from the EBA, following the technical and data quality validations they are performing, and provides guidance to FEs in addressing these errors. The errors in these feedback files are to be remediated by Financial Entities (FEs), before re-submitting to the Central Bank of Ireland and this guide should assist FEs in doing so.

Guide to Submitting DORA Registers of Information on the Central Bank of Ireland Portal Page 67 Back to “Checklist” Back to “Contents” This guide contained the most common errors the Central Bank have noted and thus is not exhaustive. It should be read in conjunction with the EBA guidance referenced in the next section, all available on their Register preparation site. Rule Code 103 Rule description: Invalid ZIP file. Displayed Error: • Failed reception check 103: Invalid ZIP file, instance filename [filename] not matching zip filename [name of zip file]; or • Failed reception check 103: Invalid ZIP file root folder [name of root folder] is not found in ZIP file [name of zip file]; or • Failed reception check 103: Invalid ZIP file, instance file extension is missing in zip file [name of zip file] Error Description: Various problems can cause different error messages, such as: • The root folder name differs from the zip file name; • The root folder or some subfolders are missing; • The zip file lacks the correct file extension; or • The zip file does not follow the required structure. Instructions

Guide to Submitting DORA Registers of Information on the Central Bank of Ireland Portal Page 68 Back to “Checklist” Back to “Contents” Financial entities should ensure that the files are in line with the EBA site in the section on “Preparations for Official Reporting of Registers” which includes slides on how the file should look; along with section 3.3 of the CBI external guidance. Common issues are as follows: Financial entities must ensure that: • The root folder is present inside the zip file • The root folder’s name matches the zip file name, excluding the .zip extension • The main folder contains exactly two subfolders: ‘reports’ and ‘META-INF’

Guide to Submitting DORA Registers of Information on the Central Bank of Ireland Portal Page 69 Back to “Checklist” Back to “Contents” Rule Code 305 Rule description: Numeric fact must not be reported with a string value. Displayed Error: • [table],[row],[column],305, Numeric fact must not be reported with a string value. Error Description: A numeric value shall be provided in data field [table],[row],[column]. The financial entity has either provided a non-numeric value or has left the data field empty. Instructions

Guide to Submitting DORA Registers of Information on the Central Bank of Ireland Portal Page 70 Back to “Checklist” Back to “Contents” Financial entities shall provide the mandatory value in data field [table],[row],[column]. Rule Code 306 Rule description: XBRL instance documents must use UTF-8 encoding. Displayed Error: [table filename]…306, XBRL instance documents must use UTF-8 encoding. Error Description: • File [table file name] has not been encoded in the requested ‘UTF-8’ format. Instructions Financial entities shall ensure that all files contained in the .zip file are encoded in ‘UTF-8’ format. Example The table file b_01.03.csv has been encoded in UTF-8-BOM format and this will cause errors in the validation of the file. Rule Code 330 Rule description: Date type metric must be reported with format 'yyyy-mm-dd'. Displayed Error:

Guide to Submitting DORA Registers of Information on the Central Bank of Ireland Portal Page 71 Back to “Checklist” Back to “Contents” [[table],[row],[column],330, Date type metric must be reported with format 'yyyy-mm-dd'. Error Description: The data field [table],[row],[column] shall contain a date and the value shall respect the format 'yyyy-mm-dd'. Instructions Financial entities shall ensure that dates are encoded in the requested format. Rule Code 331 Rule description: Integer type metric must be reported with an integer. Displayed Error: [table],[row],[column],331, Integer type metric must be reported with an integer. Error Description: An integer value shall be provided in data field [table],[row],[column]. The financial entity has either not provided such an integer value or has left the data field empty. To note that for example the value ‘200.5’ is in floating point format and not an integer value as an integer shall not contain a decimal place. Instructions Financial entities shall ensure that an integer value is provided for data field [table],[row],[column]. Rule Code 503 Rule description: Extensible main property and explicit key dimension must only be reported with one of the restricted value of a hierarchy. Displayed Error: [table],[row],[column],503, Extensible main property and explicit key dimension must only be reported with one of the restricted value of a hierarchy. Error Description:

Guide to Submitting DORA Registers of Information on the Central Bank of Ireland Portal Page 72 Back to “Checklist” Back to “Contents” The value contained in data field [table],[row],[column] shall be a value from the EBA permitted values for drop down fields. Instructions Please refer to the EBA permitted values for drop down fields. Common example – B_02.02 - The data fields b_02.02.0130, b_02.02.0150 and b_02.02.0160 are key fields and thus cannot be left empty. The ESAs have defined for those 3 data fields a drop-down list from which financial entities shall choose a value. Example In case the mandatory key value is not known by the financial entity for one of those three above mentioned data fields, it shall specify the code ‘eba_GA:qx2007’ representing the value ‘Not applicable’. Rule Code 702 Rule description: Invalid declarations in FilingIndicators.csv - wrong number of columns reported. Displayed Error: [filename]…702,Column names do not match the expected format. Error Description: The column names of file [filename] do not respect the requirements of the Data Point Model (“DPM”). Instructions The header of the file FilingIndicators.csv shall be : templateID,reported Example The filingindicators.csv file below contains spaces between the header names, leading to the rejection of the submitted register.

Guide to Submitting DORA Registers of Information on the Central Bank of Ireland Portal Page 73 Back to “Checklist” Back to “Contents” Rule Code 703 Rule description: Each template can be declared only once in FilingIndicators.csv. Displayed Error: FilingIndicators.csv,,,703, Each templateID must be unique. Error Description: The different names of the table files in the FilingIndicators.csv must be unique. Instructions Financial entities shall ensure that filenames are not duplicated within the csv file. Example The filingindicators.csv file below contains duplicate file names, leading to the rejection of the submitted register.

Guide to Submitting DORA Registers of Information on the Central Bank of Ireland Portal Page 74 Back to “Checklist” Back to “Contents” Rule Code 704 Rule description: Only boolean values are allowed for any template code in FilingIndicators.csv. Displayed Error: FilingIndicators.csv,,,704,"Each reported value must be ‘true’ Error Description: The FilingIndicators.csv file does not match the requirements defined in the DPM Instructions Content of a correct ‘FilingIndicators.csv’ file is shown below. • The name of the .csv file is case sensitive. The value “true” must be in lowercase. • All lines except the header contain the Boolean value ‘true’ even if the financial entity will not report a given template (for instance in case the financial entity has no branches, file b_01.03.csv is not required). • Please also refer to the EBA slides on common errors

Guide to Submitting DORA Registers of Information on the Central Bank of Ireland Portal Page 75 Back to “Checklist” Back to “Contents”

Guide to Submitting DORA Registers of Information on the Central Bank of Ireland Portal Page 76 Back to “Checklist” Back to “Contents” Rule Code 714 Rule description: The 'entityID' parameter must exist and its value must match filename. Displayed Error: parameters.csv,,,714, The 'entityID' parameter must exist and its value must match filename. Error Description: The parameters.csv file does not respect the requirements defined by the ESAs. • Content of the ‘parameters.csv’ file:

• The order of the header in the parameters.csv file is crucial — it must start with “name” followed by “value.” • The second row should begin with ‘entityID,rs:’ followed by the LEI of the submitting entity and either ‘.CON’ or ‘.IND’. • The reference period indicated in line 3 must match the one specified in the zip file’s name. For the 2025 submission, the reference date is set as ‘2025-03-31.’ • The header line must not end with a comma (‘,’). Instructions Financial entities shall review the content of the parameters.csv file.

Guide to Submitting DORA Registers of Information on the Central Bank of Ireland Portal Page 77 Back to “Checklist” Back to “Contents” Rule Code 720 Rule description: Valid table names must be used as .csv filenames. Displayed Error: [LEI].[IND/CON],,,720, Extra files found in the submission: [filename]. Error Description: Financial entity has added additional files in the sub-folder ‘reports’, or the name of a .csv table file has been misspelled. Instructions Financial entity shall ensure that only the requested files are included in the .zip file. Rule Code 723 Rule description: The header row in parameters.csv must consist only of the values name and value, in the first and second columns, respectively. Displayed Error: [parameters.csv,,,723, The header row in parameters.csv must consist only of the values name and value, in the first and second columns, respectively Error Description: The first line in the parameters.csv shall be ‘name,value’ . Instructions Financial entities must ensure that the first line of the file reads ‘name,value.’ They must not replace ‘value’ with the name of their financial entity. Sample accepted file (with a made-up LEI code):

Guide to Submitting DORA Registers of Information on the Central Bank of Ireland Portal Page 78 Back to “Checklist” Back to “Contents” Rule Code 801 Rule description: All header column codes must be defined in the taxonomy .json files (as described in the EBA data model. Displayed Error: [table filename],,,801, All header column codes must be defined in the schema Error Description: The financial entity has specified a header in table file [table filename] that is not compliant with the DPM. Instructions; • The header of a .csv file lists various columns such as c0010, c0020, and so on. • Each column in the header is separated by a comma (‘,’) when opened in notepad/ your security-approved text editor. • All column names are lowercase, starting with the letter “c” followed by four digits. • No extra columns should be added. • The header must not contain any empty values.

Guide to Submitting DORA Registers of Information on the Central Bank of Ireland Portal Page 79 Back to “Checklist” Back to “Contents” • Columns are numbered in increments of 10 (e.g., c0010, c0020, c0030, etc.) (except for B_03.03, which has columns c0010, c0020 and c0031). See the EBA annotated template as an illustration of the columns. • The header line must not end with a comma (‘,’), as this will be interpreted as an additional, undefined column. • Please also refer to the EBA FAQ for unusual instances, for example the numbering error in the column codes in template B_06.01 in the ITS, whereby data field B_06.01.0050 is missing in the column codes, resulting in the data fields being assigned erroneous column codes. The ESAs further noted that for reporting purposes, the data points included in the reporting technical package v4.0 for the ITS on the Registers of information should be considered. The data point model contains consecutive numbers of the data fields. Following the renumbering of the columns, the header of the table file b_06.01.csv shall be: c0010,c0020,c0030,c0040,c0050,c0060,c0070,c0080,c0090,c0100 Example: Template B.01.01 is composed of 6 different data fields: The header of the file b_01.01.csv must be: c0010,c0020,c0030,c0040,c0050,c0060 Column Order: Financial entities must ensure that the number of columns in the .csv header matches ESA’s specifications. However, the order of the columns can vary and appear in any sequence. In such cases, financial entities must ensure that the values correspond to the same order as the columns in the header. Below are two examples of different b_01.01.csv files that will be accepted:

Guide to Submitting DORA Registers of Information on the Central Bank of Ireland Portal Page 80 Back to “Checklist” Back to “Contents” Example1 (accepted): Example2 (accepted): In both examples column c0010, for instance, contains the LEI of the financial entity and column c0020 its name. Example of a b.01.01.csv file that will be rejected: In this example column c0010 incorrectly contains the reporting date and there is an extra ‘,’ after column c0060, which is interpreted as an extra column. Rule Code 805 Rule description: For open tables, the key columns values cannot be empty. Displayed Error: [table],[row],[column],805, For open tables, the key columns values cannot be empty, None Error Description: A data field defined as a key field is empty i.e. contains no value. Instructions; Please populate the offending cell as per the ITS on the RoI, sample files, EBA Data Model, EBA FAQ, EBA annotated template and EBA permitted values for drop down fields.

Guide to Submitting DORA Registers of Information on the Central Bank of Ireland Portal Page 81 Back to “Checklist” Back to “Contents” In the above example, data fields b.01.01.0010, b.01.02.0010 and b.01.02.0060 are defined as keys and cannot be empty. Rule Code 806 Rule description: For open tables, you cannot have multiple rows with identical key values. Displayed Error: [table],[line],[column],806, For open tables, you cannot have multiple rows with identical key values,[value] and [table],[line],[column],806, For open tables, you cannot have multiple rows with identical key values,[value] Error Description: Each table in the DORA data model has a primary key composed of a single column or a combination of several columns. All columns of a table which are part of the table’s key are represented in bold in the EBA data model; Examples: The primary key for table B.05.01 is a single column: c0010

Guide to Submitting DORA Registers of Information on the Central Bank of Ireland Portal Page 82 Back to “Checklist” Back to “Contents” The primary key for table B.01.03 is a combination of the two columns: [c0010, c0020] For a given table, the value of a key cannot be duplicated. Instructions; Financial entities shall ensure that a given .csv file has no duplicated keys. Rule Code 807 in b_05.01 Rule description: The reported data must follow the key-foreign key constraints defined in the DPM. Displayed Error: [table],[row],[column],807,The reported data must follow the key-foreign key constraints defined in the DPM,[value] Error Description:

Guide to Submitting DORA Registers of Information on the Central Bank of Ireland Portal Page 83 Back to “Checklist” Back to “Contents” In B_05.01, this error occurs because the Implementing Regulation (EU) 2024/2956 (the ITS)) requires such ultimate parent undertakings reported in c0110 to be reported in B_05.01 as separate rows, identified in c0010. Instructions; The ultimate parent undertakings reported in B_05.01.0110 are to be reported in B_05.01 as separate rows, identified by c0010. If the value is present for the ultimate parent in B_05.01.0110, it is checked against B_05.01.0010 for the parent, which should be reported as a separate entry. If there are no parents, or for ultimate parent entries, they should repeat the same ID as in B_05.01.0010. Rule Code 807 General Rule description: The reported data must follow the key-foreign key constraints defined in the DPM. Displayed Error: [table],[row],[column],807,The reported data must follow the key-foreign key constraints defined in the DPM,[value] Error Description: The EBA data model specifies in column ‘ForeignKey’ whether a given data field is a foreign key field or not. Example:

Guide to Submitting DORA Registers of Information on the Central Bank of Ireland Portal Page 84 Back to “Checklist” Back to “Contents” In the example above, the data fields B_02.02.0010, B_02.02.0020, B_02.02.0030, and B_02.02.0050 are Foreign Keys. This means the values in these fields must be defined either in the same table or in another table. If not, an error message of type 807 will be triggered, causing the rejection of the submitted register. The ESAs distinguish two types of Foreign Key violations:

1. Foreign Key Violation – across tables This occurs when a data field contains a value that is not defined as a primary key in another table. For example: Table B_02.01 lists all contractual arrangements signed with Intra-Group entities or external TPPs, with each contract identified by a unique Contractual Arrangement Reference Number as the primary key. Table B_02.03 includes all Intra-Group contractual arrangements. Each contract in Table B_02.03 must also be defined in Table B_02.01. If this is not the case, an error message of type ‘Foreign Key Violation – across tables’ will be displayed. The relationship between tables B_02.01 and B_02.03—specifically between data fields B_02.01.0010 and B_02.02.0010—is illustrated in the Data Model for the DORA RoI document as follows:

Guide to Submitting DORA Registers of Information on the Central Bank of Ireland Portal Page 85 Back to “Checklist” Back to “Contents” 2. Foreign Key Violation -self reference This type of violation occurs when a data field contains a value that is not defined within the same table Example: Example: Table B_02.01 lists all contractual arrangements of the financial entity. If a reference in one of its fields points to a value not present within that same table, it results in a self-reference Foreign Key Violation. • Column c0020 in table B_02.01 indicates the type of contract: either a standalone arrangement, an overarching/master contractual arrangement, or a subsequent/associated arrangement. • If column c0020 contains the value “subsequent or associated arrangement,” then column c0030 (a foreign key) must include the contractual reference number (the primary key) of the related overarching/master contractual arrangement. If column c0030 references a contractual reference number, the corresponding overarching/ master contract must be present in table B_02.01. If it is not, an error message of type 807 will be generated, and the submitted register will be rejected. Instructions; The error message will specify the source data field — including the table, row, column, and the value — where the foreign key violation occurred.

Guide to Submitting DORA Registers of Information on the Central Bank of Ireland Portal Page 86 Back to “Checklist” Back to “Contents” According to the DORA RoI Data Model, financial entities must identify the table and data field linked to the source field in order to ensure the referenced value exists. The EBA slides on common errors also contain examples of this error. Note: A large number of 807 errors may occur if the .csv files are not properly encoded in UTF-8 format. Rule Code 808 Rule description: All filing indicators have to be set as true - and the templates reported empty if no data is present. Displayed Error: FilingIndicators.csv,,,808, All filing indicators have to be sent as true. Error Description: The FilingIndicators.csv file does not match the requirements defined in the EBA data model. Instructions; All templates have to be reported as ‘true’ in FilingIndicators.csv per slide 16 in the EBA slides on common errors and as shown below, even if the financial entity is not reporting a given template (for instance in case the financial entity has no branches, file b_01.03.csv is not required); Rule Code 809 Rule description: CSV formatting problem detected.

Guide to Submitting DORA Registers of Information on the Central Bank of Ireland Portal Page 87 Back to “Checklist” Back to “Contents” Displayed Error: • [filename],,,809, CSV formatting problem detected.,'utf-8' codec can't decode byte [value] in position [value] invalid start byte; or • Unexpected number of columns in row [value] Error Description: An issue has been detected inside a .csv table file: • The file [filename] is not encoded in ‘UTF-8’. To note that the error ‘306 XBRL instance documents must use UTF-8 encoding’ may also be raised in this case. The header does not match the columns in row [value]. Instructions; Financial entities shall review the encoding of the file. Rule Code v88xx_m / v8888x_m Rule description: Value should not be missing. Displayed Error: [v88xx_m [row] Value should not be missing [table] [column] None. Error Description: A given data field is empty but shall contain a value. Instructions; The ESAs have defined for all tables (except for B_02.03,B_02.03,B_03.02) Data Point Model (DPM) Business Validation Rules. DPM Business Validation rules v88xx_m / v8888x_m check that a given data field is not empty under a predefined condition. The structure of each of those validation rules is [in case a certain condition is met] then [a given data field cannot be empty e.g. must contain a value]. Please populate the offending templates as per the ITS on the RoI, sample files, EBA Data Model, EBA FAQ and drop down fields and refer to the EBA slides on common errors.

Guide to Submitting DORA Registers of Information on the Central Bank of Ireland Portal Page 88 Back to “Checklist” Back to “Contents” Rule Code VR_2 / VR_12 / VR_23 / VR_71 / VR_77 Rule description: LEI code needs to be a valid one according to the GLEIF database. Displayed Error: • [table],[row],[column],VR_2,LEI code needs to be a valid one according to the GLEIF database,[value] • [table],[row],[column],VR_12,LEI code needs to be a valid one according to the GLEIF database,[value] • [table],[row],[column],VR_23,LEI code needs to be a valid one according to the GLEIF database,[value] • [table],[row],[column],VR_71,LEI code needs to be a valid one according to the GLEIF database,[value] [table],[row],[column],VR_77,LEI code needs to be a valid one according to the GLEIF database,[value] Error Description: The LEI does not appear to be a valid LEI code in the GLEIF. (Also check that UTF-8 encoding was used and not UTF-8-BOM). Instructions; Financial entities shall provide a valid LEI code in data field [table],[row],[column]. According to EBA FAQ #40, if an ICT third-party provider (or its ultimate parent) in a third country does not have an LEI, the financial entity should populate the data field with any relevant value to avoid the file being rejected as failing the referential integrity check. In practice this could mean that the financial entity could use other identifiers available. The use of such identifiers will be highlighted as a data quality issue, but the files will not be rejected. Rule Code VR_72 / VR_78 Rule description: EUID code needs to be a valid one according to the BRIS. Displayed Error: EUID code needs to be a valid one according to the BRIS Error Description: Warning message, not leading to the rejection of the submitted register. Financial entities are however requested to fix the raised issues and re-submit their register.

Guide to Submitting DORA Registers of Information on the Central Bank of Ireland Portal Page 89 Back to “Checklist” Back to “Contents” Instructions; Financial entities shall check the composition of the EUID code and ensure that the EUID code is recorded in the BRIS database where possible 7.4 Addressing Data Quality Feedback from EBA 18 February 2026 update - the EBA announced that there will be an additional review step to be performed on the content of the data submitted in the Registers of Information for the upcoming 2026 submission. This step is to address issues that are uncovered in terms of the quality of the data content within the files. The initial collection will take place as happened in 2025, whereby financial entities submit their Registers between 1 and 31 March, ensuring all EBA feedback on technical validations is addressed and that Registers are resubmitted before the 31 March deadline. Subsequently, in April 2026, the EBA will run Data Quality checks on all Registers. This is a new step. This will result in additional feedback on data within Registers. We do not yet have sight of exactly what these data quality feedback files will look like. We have been given examples of some of the checks which will be performed, for example: • An Invalid value reported for the Identification code of a TPP’s ultimate parent: 9999999DUMMY99999999; or • A generic value reported for the name of the ICT third-party service provider: not applicable. To the extent that we have information, we will update this guidance with new information, as we receive it.

Guide to Submitting DORA Registers of Information on the Central Bank of Ireland Portal Page 90 Back to “Checklist” Back to “Contents” Some examples, which have been provided by the EBA, of the types of Data Quality checks to be performed are as follows:

Guide to Submitting DORA Registers of Information on the Portal Central Bank of Ireland Page 91 Back to “Checklist” 8. Useful EBA reference guidance links RoIs will fail to be uploaded successfully to the Central Bank of Ireland Portal if basic steps have not been followed by those responsible for submitting the RoI. We therefore recap, below, the key links to be followed for guidance. Please note that the Central Bank of Ireland will not troubleshoot issues within reporting packages. Our support teams will only be on hand to support issues with the Central Bank of Ireland systems as part of the submission process. We encourage firms to frontload their initial submission early in the collection window, such that there is time for the firm to remediate any issues. Furthermore, we want to emphasize the importance of following the relevant EU level guidance for compiling your register packages to meet your compliance requirements. • The guidance provided on the EBA preparation site in the section on ‘PREPARATIONS FOR OFFICIAL REPORTING OF REGISTERS’, in particular the slides on preparing the reporting package provide useful information. • Financial entities must compile their RoI reporting package following the details in the Implementing Technical Standards (ITS on the RoI), noting any clarifications in the EBA’s RoI FAQ on their preparation site (linked above) and also any corrections to the ITS in the ESAs DORA QAs. • On the register preparation site, the ESAs also provide many other useful materials for financial entities preparing their RoI including but not limited to: o Examples of what your compiled registers should look like - EBA sample files – useful for guidance on, e.g. what the reporting package should look like and how the date format should look (YYYYMM-DD throughout all files). o It should also be noted that you should view/edit these and your own files in Notepad/ Your security-approved text editor in order for the format to be correct - e.g. date format shows incorrectly if you open files with Excel;

Guide to Submitting DORA Registers of Information on the Portal Central Bank of Ireland Page 92 Back to “Checklist” o What the correct columns are as well as what should be included in columns with drop down fields – see EBA annotated template. o Also in terms of how each csv should be structured, the DPM dictionary and DPM table layout and data point categorization, on the same EBA preparation website, guides entities and their vendors as to what should be in each of the files; o Answers/ clarity on many questions as to what to include in the register – the Implementing Technical Standards (ITS) and the EBA FAQ . You can use CTRL+F to search the FAQ for specific templates or fields (E.g.B_01.03) in these FAQ to find out if there are certain peculiarities around a specific template or field. Also see EBA slides on common errors. o What fields are mandatory/ format of those fields - see EBA data model and the Implementing Technical Standards (ITS) - please note that there are conflicts in some EBA guidance, in that the data model says some fields are nullable (i.e. can be left blank) – but where these fields are noted as mandatory in the ITS, or key fields in the data model/ annotated template, they need to be filled in. o The EBA data model also denotes which fields in tables are linked (referential integrity), so please take note of this, as ignoring this caused many errors in the first submission. o Further documentation on the overall EBA reporting framework 4.0 is also available: https://www.eba.europa.eu/risk-and-data￾analysis/reporting-frameworks/reporting-framework-40; and o EBA Filing rules version 5.7.