Create New Branch form

---
title: Create New Branch form
description: On the Create New Branch form, fill in the fields.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/australia/governance-risk-compliance/third-party-risk-management/tprm-create-new-branch-form.html
release: australia
product: Third-party Risk Management
classification: third-party-risk-management
topic_type: reference
last_updated: "2026-09-10"
reading_time_minutes: 2
breadcrumb: [Create a branch and enhance digital resilience data, Use digital resilience third-party registers, Third-party Risk Management, Governance, Risk, and Compliance]
---

# Create New Branch form

On the Create New Branch form, fill in the fields.

<table id="table_aqy_k2x_rvb"><thead><tr><th>

Field

</th><th>

Description

</th></tr></thead><tbody><tr><td>

SysID

</td><td>

Unique 32-character GUID \(Globally Unique ID\) that identifies each branch record in an instance. Provide this value if you want to update an existing record. Provide a value of -1 if you want to create a new record in the system.

</td></tr><tr><td>

Name

</td><td>

Name of the branch.

</td></tr><tr><td>

Description

</td><td>

Description for the branch.

</td></tr><tr><td>

Number

</td><td>

Unique identification number for the branch that will be generated by the application, for example, BRN0001005. This field is auto-filled.

</td></tr><tr><td>

Department

</td><td>

Department that the branch belongs to, for example, Customer Support, Product Management.

</td></tr><tr><td>

Owner

</td><td>

Name of the owner of the branch.

</td></tr><tr><td>

Business unit

</td><td>

Name of the business unit that is associated with the branch, for example, HR, IT, Legal.

</td></tr><tr><td class="sub-head" colspan="2">

Digital resilience information

</td></tr><tr><td>

Is Branch different from Financial Entity head office of the branch

</td><td>

Option to confirm if the branch is different from the head office. Available options are:-   **Yes**: When you select the **Yes** option, the **Identification code type** and **Identification code of the branch** fields are displayed.
-   **No**

</td></tr><tr><td>

Identification code type

</td><td>

Type of identification code used for the branch. Available options are:-   **LEI**
-   **Other**

</td></tr><tr><td>

Identification code of the branch

</td><td>

An overseas branch of the financial entity, uniquely identified by a specific code, for example, FB97521. The financial entity uses the branch's Legal Entity Identifier \(LEI\) or another identification code to distinguish it.

</td></tr><tr><td>

LEI of the financial entity head office of the branch

</td><td>

Legal Entity Identifier \(LEI\) of the head office of the financial entity to which the branch belongs, for example, LEIACMEGermany001 or LEIACMEAmericas001.**Note:** When you enter or update this field, the system validates the code against the GLEIF database and auto-populates the Name of the branch and Country of the branch fields. If you then edit those fields to values that no longer match GLEIF data, an inline warning is displayed on the edited field. For more information, see [Validate Legal Entity Identifier codes for DORA reporting](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/governance-risk-compliance/third-party-risk-management/tprm-valid-lei.md).

</td></tr><tr><td>

Name of the branch

</td><td>

Name of the branch that is used for identification. When the LEI of the financial entity head office of the branch is entered, this field is auto-filled, for example, Frankfurt branch office.

</td></tr><tr><td>

Country of the branch

</td><td>

Two-letter country code where the branch is located. When the LEI of the financial entity head office of the branch is entered, this field is auto-filled, for example, Germany.

</td></tr></tbody>
</table>