QA2025-29- Different definition of similar data fields
- SRB Services
| Attribute | Detail |
|---|---|
| Unique Identifier | QA2025-29 |
| Document | MBDT Guidance |
| MBDT Guidance | B02.00 |
| Title | Different definition of similar data fields |
Question
Data points B02.00:c0530 and B02.00:c0550 include the following possible drop-down options: * T2 in phase-out, * Grandfathered T2, * Fully Compliant T2, * Partially (A)T1 and T2, * Grandfathered AT1, * Fully Compliant AT1, * CET1, * No. According to the validation rules, if the data point is not applicable, Not applicable should be reported. Level 2 validation rules state that drop-down values must be respected. That being said, we have the following questions: * What is the rationale behind the option “No” compared to “Not applicable”? * Do you see a problem inputting “Not applicable” as a text in combination with the Level 2 validation rule mentioned above (see also next question)? Should “Not applicable” possibly replace “No” in the drop-down list? * Why did you chose a different approach as for e.g. B02.00:c0460 (Central securities depository), where “not applicable” is part of the code list and the field should be left empty in case it is not applicable (see also QA2025-14)? A uniform approach should be chosen for clarity and ease of technical implementation.
Response
In response to industry feedback during the MBDT public consultation, the SRB aimed to align dropdown values with other reporting collections. To this end, the rational to maintain the option No in field B02.00;c0530 and B02.00;c0550 instead of adopting the standard Not applicable value was to align with the LDR field c0310 ( Qualifying as Own Funds ) in T04.00. The mapping tables provided in the MBDT facilitating annex (see section 2.3, Mapping for tab B02.00 ) clarify this aspects. Hence, the input of either No or Not applicable for these fields will be accepted, with the same meaning. For the field c0460 (Central securities depository) in B02.00, as clarified in QA2025-14, if the field is not applicable, please input Not applicable .