B_01.03 — Branches

Purpose

This template lists branches of financial entities that operate outside their home country. A branch is a place of business that is part of a financial entity but is located in a different member state from the entity's head office.

Each row represents one branch, linked back to its head office entity via LEI. This template is essential for mapping ICT service usage to specific geographic locations, particularly when a branch uses different ICT services than the head office.

The entity's compliance team fills this template during initial register setup and updates it when branches are opened, closed, or relocated.

Fields Reference

CodeField NameTypeReq.Description
c0010Branch identification code*textYes
Unique code identifying the branch
Max length: 255
c0020LEI of the head office*leiYes
LEI of the entity that the branch belongs to
Max length: 20
FK → B_01.02 (c0010)
c0030Name of the branch*textYes
Name of the branch
Max length: 255
c0040Country of the branch*countryYes
Country where the branch is located (ISO 3166-1 alpha-2)

Relationships

Validation Rules

  • Head office LEI must exist in B_01.02. The LEI referencing the head office entity must correspond to an entity listed in the consolidation template (B_01.02).
  • Unique branch codes. Each branch must have a unique identifier within the register. Duplicate branch codes are not allowed.
  • Branch country differs from head office. By definition, a branch operates in a different country than its head office. The branch country should not match the head office entity's country in B_01.02.

Example

FieldValue
Branch CodeLV-BR-001
Head Office LEI529900ABC...
Branch NameLondon Branch
CountryGB

Common Mistakes

  • Branch code not referenced in B_04.01. If a branch uses ICT services, it must be referenced in B_04.01 with nature NE_2. Forgetting to link the branch code leads to incomplete service mapping.
  • Head office LEI not in B_01.02. The branch must reference a valid head office entity. If the head office is missing from B_01.02, the branch record becomes orphaned.
  • Duplicate branch codes. Reusing the same branch code for different branches breaks referential integrity across the register.