---
sourceDocument: Australia Governance, Risk, and Compliance
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/governance-risk-compliance

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Governance, Risk, and Compliance

ft:clusterId :

    - grc

bundleId :

    - grc

workflow :

    - Technology


---

# Create Microsoft Excel download and upload request

# Create Microsoft Excel download and upload request {#ariaid-title1}

* Release version: Australia
* 
* Updated March 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 8 minutes to read

Create a Microsoft Excel upload and download request to upload and download the records from and into the Digital resilience third-party registers for auditing purposes.

## Before you begin

Role required: sn_oper_res.admin

## About this task

Use the Excel download/upload requests module in Digital resilience third-party registers to export and import the records in Microsoft Excel format. The European Union auditors and regulators can download these records for audit and reviewing purposes and take appropriate actions.  
To become familiar with the process before handling more complex operations, you can follow these steps:

* Create records on the UI: Create records for each type on the user interface. It helps you to understand which fields are mandatory and their required formats.
* Download data: Next, download the data to get a clear understanding of the values in each Microsoft Excel column.
* Upload data with the changes: Finally, make a simple change to a column and upload the data back to verify that the process works as expected.
{#create-excel-upload-download-request__ul_lqt_bv1_5gc}

## Procedure

1. Navigate to WorkspacesOperational Resilience WorkspaceDigital resilience third-party registersExcel download/upload requests.
2. Select New.  
   The Create New Excel download/upload request form is displayed.
3. On the form, fill in the fields.  
   For descriptions of all these fields, see [Create Excel download/upload request form](https://servicenow-prod.fluidtopics.net/gfL59ulTc_cf5gfRNP9Ruw "On the Create Excel download/upload request form, fill in the fields.").
4. For the Upload request, select the Attach file option in the Select file field.
5. To download the template for uploading the selected type of record such as Assessments, select Download template, select the file in the Save as field in the modal, and select Save.
6. To upload the selected file, select Upload.  
   During upload, the system performs a two-pass batch LEI verification:
   1. Collection pass: The system parses the entire Excel file and collects all unique LEI codes from the following fields: - Legal Entity uploads: LEI of the entity (b_01_02_0010) - Branch uploads: Identification code of the branch - Third Party uploads: Identification code field (b_05_01_0010) where Type of code = LEI - Third-Party Engagement uploads: Identification code field (b_05_01_0010) where Type of code = LEI Duplicate LEI codes across multiple rows are deduplicated and verified only once.
   2. Verification pass: The collected LEI codes are sent to the GLEIF API in a single batch request (up to 200 LEIs per request). The results are cached and reused for all rows.
   {#create-excel-upload-download-request__ol_w1g_hv2_mjc}

   LEI format validation is always performed locally before the API call. LEIs that do not match the format are reported as errors without calling the GLEIF API.

   The upload result report includes LEI verification messages for each row: - Success: 'Row {N}: LEI verification successful -- LEI {code} -- Entity: {name}' - Warning (property = Yes): 'Row {N}: WARNING -- LEI verification failed -- LEI {code} not found in GLEIF registry. Record saved with unverified LEI.' - Error (property = No): 'Row {N}: LEI verification failed -- LEI {code} not found in GLEIF registry. Row skipped'.

   The behavior for each failure scenario during upload is controlled by the system property sn_dora_accel.lei_save_on_gleif_error. For the properties reference and the complete behavior matrix, see [Properties installed with Digital Operational Resilience Management](https://servicenow-prod.fluidtopics.net/fftxbs2F15HRvFL8vwr1iw "When you install the Digital Operational Resilience Management application, several system properties are added to your instance. You can access the properties by navigating to All > Digital Operational Resilience Management > Properties > .").

   During upload of contractual arrangement records, the system checks each row against existing records using the same 8-field duplicate detection logic used on the UI form. Rows that match an existing record are
   skipped (not inserted or updated), and a duplicate error is added to the upload error report.
7. Select Save.  
   After saving a download request, you can choose which records you want to download by navigating to its corresponding tab. For example, you would navigate to the Contracts tab for a Third-party information register download request or the Assessments tab for an Assessments download request.
8. Select the records that you want from the list and perform one of the following steps.

   | Step | Description |
   | Export to excel | When making a download request for records related to Assessments, Branches, Contracts, Functions, Legal Entities, Supply Chains, Third Parties, or Third-Party Engagements, select Export to Info Excel. Export those records as a Microsoft Excel file. |
   | Export to info register | When making a download request for a Third-Party Information Register record, select Export to Info Register to export contract records you want as an Microsoft Excel file. When the export completes, the system runs a batch LEI verification against the GLEIF database for all LEI codes present in the downloaded data. LEIs are processed in batches of 200 per API call. A Level4_LEI_Validation_Report.csv is included in the Consolidated_Reports.zip file alongside the export data. The LEI validation report contains the columns. "Sheet Name \| Row Number \| LEI Code \| Entity Name (Input) \| Country (Input) \| LEI Format Valid \| LEI Checksum Valid. It also contains: LEI Found \| Name Match \| Name (GLEIF) \| Country Match \| Legal Country (GLEIF) \| Entity Status \| Registration Status \| Corroboration Level \| Validation Result \| Validation Messages" After validation completes, the system displays one of the following messages in the export request record. Success: 'Level 4 LEI validation completed successfully. {N} LEIs validated.' - Warnings present: 'Level 4 LEI validation completed with warnings. {X} of {N} LEIs has issues.' where X is the count of invalid or unresolvable LEIs. LEI validation uses a three-phase pipeline: * Phase 1 --- Format check: LEIs that fail the 20-character alphanumeric format check are reported immediately and do not proceed to GLEIF. * Phase 2 --- Checksum check (MOD 97-10): LEIs that pass format but fail the ISO 7064 checksum are reported and do not proceed to GLEIF. * Phase 3 --- GLEIF batch API: Only format- and checksum-valid LEIs are sent to GLEIF. Results are cached in memory for the duration of the download request so that duplicate LEIs are validated only once. If the GLEIF API is unreachable or times out, the download is not blocked; the affected rows are reported as N/A (API_UNAVAILABLE) in the report. {#create-excel-upload-download-request__ul_pkv_jx4_djc} During CSV generation, the system also checks for duplicate rows in the b_02.02 sheet (contractual arrangements). When rows with an identical composite key are detected, a warning is logged to the DORA request record's error message field. (contract reference, entity, provider, country, function, ICT service type, storage, processing are examples of keys.) It indicates the affected row numbers and field values. The duplicate rows are not removed from the generated CSV; they are only warned. The following rules apply when the report is generated for b_05.01 (ICT third-party service provider) data: * Additional identification code (c0030): If a b_05.01 row's additional identification code is empty or is identical to the primary identification code (c0010). It is not validated separately and does not appear as a distinct row in the report. * Country comparison for legal entities acting as service providers: When a legal entity in b_01.02 is also a service provider in b_05.01, the country in b_05.01 (c0080, registered country) is compared against GLEIF's legal address country. It verifies consistent GLEIF country values across both sheets. For third-party-only rows in b_05.01 (LEIs not in b_01.02), the comparison continues to use the GLEIF headquarters country. {#create-excel-upload-download-request__ul_zlf_21p_djc} |
   |-|-|

   {#create-excel-upload-download-request__choicetable_agc_y2k_fdc}  
   For information on Register of information regulatory packages, see the following topics:
   * [Register of Information (ROI) regulatory packages](https://servicenow-prod.fluidtopics.net/~YzoGEPyUElpZ~_PjCkpsw "The Register of Information (RoI) is a regulatory reporting requirement under the Digital Operational Resilience Act (DORA) and is supported by the Digital resilience third-party registers application in the Operational Resilience Workspace.")
   * [Generate a Register of Information package](https://servicenow-prod.fluidtopics.net/UkEOfGeztOlipml7~GrW5g "Generate a register of information package. Use the CSV report option in the download page to generate regulator-ready Register of Information (RoI) packages.")
   * [Validation framework for Register of Information in Operational Resilience](https://servicenow-prod.fluidtopics.net/9u~Rmcgc9NPnVEtiwe0SeA "The validation framework helps to verify that RoI packages meet regulatory requirements defined by the DORA.")
   * [Validate the Register of Information packages](https://servicenow-prod.fluidtopics.net/8~8TzP4z24wfOH9ZAGOr9w "Run real-time validation on Register of Information (RoI) packages to help ensure compliance with DORA requirements.")
   {#create-excel-upload-download-request__ul_mc5_5ww_3hc}
9. Add the name that you want for the Microsoft Excel file and select Save.  
   In releases prior to 21.x.x of Digital resilience third-party registers, downloading the contract created a single sheet with all the contract data. Starting with version 21.x.x of Digital resilience third-party registers, when you generate a report on the contracts, it mirrors the UI. The report provides details, including information on entities, third parties, third-party
   engagements, and specific contract information in the Microsoft Excel sheet.

   It generates a Microsoft Excel sheet that you can submit directly to your regulatory authority. The file strictly adheres to the format of the template issued by the regulatory authority and includes all
   necessary details for reporting your third-party engagements.

   Starting with version 20.x.x of Digital resilience third-party registers, you can see choice or reference values in the downloaded Microsoft Excel files. For example, Departments can be created in the system as 'Research and Development'. When the functions are downloaded, department values are displayed as options in the Microsoft Excel template for selection. The template includes drop-down lists for departments, business units, and other yes or no questions (as seen in the Branch template). Additional drop-downs
   are added for countries, currencies, and so on

   The application also handles translations for meta data, including headers and drop-down options.

   Confirm that no duplicate records are present after downloading data for Legal entities, Functions, and so on. When downloading the template, confirm that there are no duplicate third-party rows. For example, you can
   create one DORA third-party and two DORA entities. You can then create DORA contracts for the same vendor using the same entity. This results in only one third-party row in the downloaded template, not two duplicate
   rows. You can add new entities and enter their LEI (even if not in the drop-down list) in the downloaded contract file. You don't need to download the contract records again. You can upload the modified contract
   records back to the application.
10. Review the LEI validation report.  
    Open the "Consolidated_Reports.zip" file that gets generated with the download and locate Level4_LEI_Validation_Report.csv inside. Review any LEI codes flagged as invalid or unresolvable. Correct the affected records in the system and re-download if required.
11. Convert and aggregate contractual expenses to regulator-required currencies.  
    Beginning with Digital Operational Resilience Management (sn_dora_accel), version 22.x.x, currency conversion and third-party aggregation capabilities are supported for DORA reporting. For more information on conversion and aggregation, see [Convert and aggregate contractual expenses](https://servicenow-prod.fluidtopics.net/7uwah8KcKYLoMbsMmBtyvw "Convert and aggregate contractual expenses to regulator-required currencies and generate consolidated reports for reporting submissions. Beginning with Digital Operational Resilience Management (sn_dora_accel), version 22.x.x, these currency conversion and third-party aggregation capabilities are supported for DORA reporting.").
12. To download third-party information register, select Export info register on the Contractual arrangements tab, add a name, and save it.  
    The dialog box is shown in the example.  
    The example shows a downloaded report with expenses reported in local currencies.
13. To export Excel download/upload requests, select the requests you want and then Export.

    | Step | Description |
    | Select File Type. | File type selected for the export. Available choices are: * Excel * CSV * JSON * PDF {#create-excel-upload-download-request__ul_cvn_3bd_zvb} |
    | Select Delivery Type. | Delivery type selected for the export. Available choices are: * Download * Email {#create-excel-upload-download-request__ul_qgh_5mr_xcc} |
    | Select Export. | Action to export the record. |
    |-|-|

    {#create-excel-upload-download-request__choicetable_zpm_dmr_xcc}
* **[Create Excel download/upload request form](https://servicenow-prod.fluidtopics.net/gfL59ulTc_cf5gfRNP9Ruw)**   
  On the Create Excel download/upload request form, fill in the fields.

*[\>]: and then