---
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 a branch and enhance digital resilience data

# Create a branch and enhance digital resilience data {#ariaid-title1}

* Release version: Australia
* 
* Updated May 15, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Create a branch record in Digital resilience third-party registers using Third-party Risk Management. You can then enhance its digital resilience information for compliance with DORA regulation.

## Before you begin

Role required: sn_vdr_risk_asmt.vendor_assessor

## About this task

A legal entity can operate multiple branches across various cities or countries, all of which can be documented on the form. If a new branch is launched, its information is also required for regulatory reporting.

## Procedure

1. Navigate to WorkspacesVendor Management Workspace, select the list icon ![]() and then navigate to Digital resilience third-party registers.
2. Select Branches and then create a branch by selecting New.
3. On the form, fill in the fields.  
   For descriptions of all these fields, see [Create New Branch form](https://servicenow-prod.fluidtopics.net/bmswxzRN6DGXsf6l_NyVNw "On the Create New Branch form, fill in the fields.").  
   Users typically fill in the following details of the branch:
   * Branch name and its description
   * Owner's details
   * Tagging of business units and departments for reporting purpose
   * Specifying the branch as a head office or as a different branch other than the head office
   * ID of the branch and its originating country
   {#tprm-drtp-reg-branch__ul_kdv_kv2_ddc}The number for the branch is auto-generated. Once the branch details are complete, the information is ready to be captured in the information register.  
   Note:  
   When you enter or update an LEI code field on the branch form, the system validates it against the GLEIF database and auto-populates the name and country fields. If you then edit the name or country to a value that no longer matches GLEIF data, an inline warning is displayed on the edited field. You can still save the record. For more information, see [Validate Legal Entity Identifier codes for DORA reporting](https://servicenow-prod.fluidtopics.net/PQXkTi5bEbCNKzjDx9WUgg "Review and resolve Legal Entity Identifier (LEI) validation results for DORA Register of Information reporting. LEI validation runs automatically during Plain-CSV Reporting Package generation and Microsoft Excel upload to verify that LEI codes in the digital resilience registers exist in the GLEIF database and have an active and issued status.").
4. Select Save.
5. To edit a Legal entity record, navigate to the legal entity tab of a company record, select the legal entity you want and select Save after making your edits.
6. To edit the branch record, select it from the list and select Save after making your edits.
7. To export the branch records, select Export.
{#tprm-drtp-reg-branch__steps_jky_zbn_ycc}

## What to do next

Specify the functions that are associated with a branch. For more information, see [Create a function and enhance digital resilience data](https://servicenow-prod.fluidtopics.net/GslS18DhI6~lL3e_keVhPg "Create a function record in Digital resilience third-party registers using Third-party Risk Management where you can configure details of the function such as function identifier, license activity, function name, criticality, or importance assessment details. You can then enhance its digital resilience information for compliance with DORA regulation.").

*[\>]: and then