---
sourceDocument: Australia Governance, Risk, and Compliance
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/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 New Branch form

# Create New Branch form {#ariaid-title1}

Release version: Australia  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Create New Branch form

The Create New Branch form allows ServiceNow customers to add or update branch records within their instance.
It captures essential branch information, including identification details and organizational associations, facilitating accurate management of branch data aligned with financial entity requirements.
Show full answer Show less  

## Key Features

* **SysID:** Use a unique 32-character GUID to update an existing branch record, or enter -1 to create a new branch record.
* **Name and Description:** Specify the branch name and description for clear identification.
* **Number:** Auto-generated unique identification number (e.g., BRN0001005) assigned to each branch.
* **Organizational Fields:** Associate the branch with a Department, Owner, and Business Unit (e.g., Customer Support, HR).
* **Digital Resilience Information:** Indicate if the branch is different from the financial entity's head office using a Yes/No option.
* **Identification Codes:** If the branch differs from the head office, specify the Identification code type (LEI or Other) and enter the corresponding Identification code.
* **LEI Validation and Auto-population:** When entering the Legal Entity Identifier (LEI) of the financial entity head office, the system validates it against the GLEIF database. Upon validation, it auto-fills the branch's Name and Country fields. If these auto-filled fields are manually altered and no longer match GLEIF data, an inline warning appears to maintain data accuracy.
* **Country Code:** Uses a two-letter country code to represent the branch location, auto-filled based on LEI input if available.

## Practical Use

ServiceNow customers can use this form to accurately create or update branch information tied to financial entities, ensuring compliance with DORA reporting requirements and alignment with official LEI data. The form's validation features help maintain data integrity and simplify management of branch identifiers and organizational relationships.  
On the Create New Branch form, fill in the fields.
{#tprm-create-new-branch-form__table_aqy_k2x_rvb__entry__2}

| Field | Description |
|-|-|
| SysID | 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. |
| Name | Name of the branch. |
| Description | Description for the branch. |
| Number | Unique identification number for the branch that will be generated by the application, for example, BRN0001005. This field is auto-filled. |
| Department | Department that the branch belongs to, for example, Customer Support, Product Management. |
| Owner | Name of the owner of the branch. |
| Business unit | Name of the business unit that is associated with the branch, for example, HR, IT, Legal. |
| Digital resilience information ||
| Is Branch different from Financial Entity head office of the branch | 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 {#tprm-create-new-branch-form__ul_gj2_1v4_ddc} |
| Identification code type | Type of identification code used for the branch. Available options are: * LEI * Other {#tprm-create-new-branch-form__ul_fh5_gl5_ddc} |
| Identification code of the branch | 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. |
| LEI of the financial entity head office of the branch | 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://www.servicenow.com/docs/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."). |
| Name of the branch | 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. |
| Country of the branch | 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. |
[Table 1. Create New Branch form]

{#tprm-create-new-branch-form__table_aqy_k2x_rvb}