B_99.01 — Entity definitions
Purpose
This is an optional template that allows financial entities to provide their own definitions for indicators or closed-set field values used throughout the register. It serves as a glossary or interpretation guide for how the entity applies specific field values in its context.
Each row maps an entity LEI and a field reference (e.g., B_02.02.0170) to the entity's definition or interpretation of that field. This is particularly useful when regulatory field values have room for interpretation or when the entity uses a specific methodology.
The compliance or ICT risk management team completes this template when the entity needs to clarify its interpretation of specific register fields.
Fields Reference
| Code | Field Name | Type | Req. | Description |
|---|---|---|---|---|
| c0010 | LEI of the financial entity* | lei | Yes | LEI of the entity providing the definitions Max length: 20 |
| c0020 | Indicator/closed-set field reference* | text | Yes | Reference to the field for which the entity provides a definition Max length: 255 |
| c0030 | Definition* | text | Yes | Definition text for the referenced field value Max length: 1000 |
Relationships
This template has no foreign key relationships with other templates.
Validation Rules
- Entity LEI must be valid. The LEI must pass ISO 17442 checksum validation and reference an entity in the register (B_01.01 or B_01.02).
- Field reference must be valid. The field reference should follow the standard naming convention (e.g.,
B_02.02.0170) and correspond to an actual field in the register schema. - Definition must be non-empty. If a row is provided, it must contain a meaningful definition text.
Example
| Field | Value |
|---|---|
| Entity LEI | 529900T8B... |
| Field Reference | B_02.02.0170 |
| Definition | We classify data sensitivity as High when the data includes personally identifiable information (PII) of more than 10,000 customers or financial transaction data. |
Common Mistakes
- Not providing definitions when using custom interpretations. If the entity interprets a field value differently from the standard definition, failing to document that interpretation here creates ambiguity for auditors and regulators.
- Invalid field references. Using incorrect field reference codes that do not correspond to actual register fields. Always verify the field code against the register schema.
- Overly vague definitions. Definitions should be specific and actionable. Writing "as per internal policy" without elaboration does not provide meaningful context for regulators.