Register setup, reporting metadata, and form state issues
Fix setup, metadata, entity, group, branch, and form-state issues that block progress before provider, contract, or service troubleshooting.
What this issue group covers
This page covers issues that usually block progress before you get into provider, contract, or service-level troubleshooting. These problems tend to come from register ownership, reporting metadata, entity-level reporting values, group structure fields, or required form selections.
It also covers form-state issues that can stop you from continuing or cause unsaved changes to be lost when you change a high-impact setting such as registry type or language.
Issues covered on this page
I am not sure which entity should maintain this register
What this usually means
You need to work out which financial entity must maintain the register, and the uncertainty usually comes from mixing up entity-level, sub-consolidated, and consolidated obligations. The key point is to separate who is in scope, which level the register covers, and whether another entity is only maintaining it on behalf of the financial entity.
What to check and how to fix it
Check whether the register you are assessing is at entity level, sub-consolidated level, or consolidated level.
If you use the wrong level, you will assign ownership to the wrong entity.
Check whether the entity in question is the financial entity in scope, a parent undertaking, or another group entity.
If it is not the financial entity with the obligation, do not treat it as having its own separate duty to maintain the register.
Check whether the financial entity is part of a group.
If it is not, the register should be maintained at that entity level.
Check whether a parent undertaking is determining the scope of a sub-consolidated or consolidated register.
If it is, use that group scope for that level, but do not treat it as removing the financial entity’s own entity-level obligation.
Check whether one group register is being used across several levels.
If it is, make sure that setup still allows each financial entity to meet its obligation to maintain and update the register at entity level and, where relevant, sub-consolidated level.
Check whether another entity is acting on behalf of the financial entity for all activities, including ICT services.
If so, keep the obligation with the financial entity and treat the other entity only as maintaining the register on that financial entity’s behalf.
Related issues
My reporting date is being rejected
What this usually means
The value in Date of the reporting does not match the field requirement. This field identifies the date of reporting and must be entered as an ISO 8601 date.
What to check and how to fix it
Check the field labelled Date of the reporting.
If a different date field is being reviewed, move to the correct field first.
Check the format of the value.
If it is not entered as yyyy-mm-dd, replace it with the full ISO 8601 date.
Check that the value is the date of reporting for the register.
If you entered another date used elsewhere in the register process, replace it with the reporting date.
Check the full value for partial entries or local date formats.
If the date includes slashes, month names, or missing digits, re-enter it in the required format.
Check nearby reporting metadata only after the field itself is correct.
If the correct date is still being flagged, review the surrounding reporting metadata for another mismatch in the same block.
Related issues
My competent authority value is being rejected
What this usually means
The value in Competent authority does not match the authority to which the register is reported. This field is for the competent authority referred to in Article 46 of DORA.
What to check and how to fix it
Check the field labelled Competent authority.
If you are reviewing another reporting field, move to the correct field first.
Check whether the register is being prepared for reporting.
If it is, this field is mandatory and cannot be left incomplete.
Check which financial entity and reporting level the register covers.
If those are wrong, the competent authority value will also be wrong.
Check whether the selected value identifies the competent authority referred to in Article 46 of DORA for the register being reported.
If it does not, replace it with the correct authority.
Check the rest of the reporting metadata only after the authority, reporting entity, and reporting level are aligned.
If one of those is wrong, the field can still be flagged even when the authority name looks plausible.
Related issues
My entity integration or deletion date is being flagged
What this usually means
One of the lifecycle dates does not match the field requirement. The issue is usually in Date of integration in the register of information or Date of deletion in the register of information.
What to check and how to fix it
Check which field is being flagged: Date of integration in the register of information or Date of deletion in the register of information.
Fix the flagged field first.
Check the format of the date.
If it is not entered as yyyy-mm-dd, replace it with the full ISO 8601 date.
Check that Date of integration in the register of information is the date the financial entity was integrated into the register.
If you entered another date, replace it with the integration date.
Check whether the financial entity has been deleted from the register.
If it has not, report 9999-12-31 in Date of deletion in the register of information.
Check whether the financial entity has been deleted from the register.
If it has, replace 9999-12-31 or any placeholder value with the actual deletion date in ISO 8601 format.
Check nearby date fields only after both lifecycle dates are correct.
If the issue remains, compare them with the other dates recorded for the same entity so the values are not being confused.
Related issues
My total assets value is being rejected
What this usually means
The value in Value of total assets of the financial entity does not match the reporting rule for that field. That value must come from the financial entity’s annual financial statements for the year before the date of the last update of the register, and it must be reported in units.
What to check and how to fix it
Check the field labelled Value of total assets of the financial entity.
If another nearby field is being flagged, fix that field first.
Check the source of the amount.
If it does not come from the annual financial statements for the year before the date of the last update of the register, replace it with the correct value.
Check how the amount has been entered.
If it has been entered in thousands, millions, or another shorthand, convert it and report it in units.
Check the linked Currency field.
If Value of total assets of the financial entity is reported, Currency must also be reported using the ISO 4217 alphabetic code.
Check that the currency matches the financial statements used for the same reporting level.
If the register is at entity, sub-consolidated, or consolidated level, the amount and currency must come from that same level.
Related issues
My group hierarchy value is being rejected
What this usually means
The value in Hierarchy of the financial entity within the group (where applicable) does not match the entity’s place in the consolidation. The fix is to use the option that matches the entity’s actual position in the group.
What to check and how to fix it
Check the Hierarchy of the financial entity within the group (where applicable) field.
If you are reviewing another entity field, move to the correct one first.
Check whether the financial entity is the ultimate parent undertaking in the consolidation.
If it is, use that option.
Check whether the financial entity is the parent undertaking of a sub-consolidated part in the consolidation.
If it is, use that option instead of a lower-level one.
Check whether the financial entity is a subsidiary in the consolidation and not a parent undertaking of a sub-consolidated part.
If that is the case, use the subsidiary option.
Check whether the financial entity is not part of a group.
If it is not, use the option for an entity that is not part of a group.
Check whether the financial entity is a service provider to which the financial entity, or a third-party service provider acting on its behalf, outsources all operational activities.
If that specific case applies, use that option.
Check whether more than one option could apply.
f it could, use the higher-level applicable option from the closed list.
Related issues
My branch identification code is being rejected
What this usually means
The value in Identification code of the branch does not match the rule for reporting a branch outside the financial entity’s home country. The problem is usually that the code is not unique for that branch, or the rest of the branch row does not match it.
What to check and how to fix it
Check the Identification code of the branch field in the branch row that is being flagged.
If you are looking at the wrong row, move to the flagged one first.
Check whether the branch belongs in this template at all.
Template B_01.03 is only for branches of financial entities located outside their home country.
Check whether the code is unique for that branch.
If the same code is being used for another branch, replace it with a unique code.
Check whether you are using the branch LEI as the identification code.
If you are, make sure it is unique for that branch and different from the value in LEI of the financial entity head office of the branch.
Check the LEI of the financial entity head office of the branch field.
If it does not identify the head office financial entity correctly, fix that field and then re-check the row.
Check the rest of the same branch row, including the branch name and country.
If those do not match the branch identification code, correct the row so all branch details refer to the same branch.
I cannot continue because the form has errors
What this usually means
Something on the current form still needs attention. Start with what is visible on the page rather than assuming the problem is elsewhere.
What to check and how to fix it
Check the current form for any field that is visibly marked as required, incomplete, or invalid.
If you find one, fix that field first.
Check the field you changed most recently.
If the issue appeared straight after an edit, review that value before checking the rest of the form.
Check whether every visible selector on the current form has a value where one is expected.
If a selector is still empty or incomplete, choose the correct value and make sure the form now shows it.
Check the rest of the same form, not just the area you were editing.
If one field now looks correct but the problem remains, another field on the page may still need attention.
Check the form again after each correction.
If a visible issue remains, resolve that before trying the same action again.
Related issues
I cannot continue because no provider is selected
What this usually means
The current form still does not show a provider selection. The issue is usually on the provider selector for that record.
What to check and how to fix it
Check the provider field or selector on the current form.
If it is empty, choose the correct provider.
Check whether the field shows typed text rather than a selected provider record.
If it does, select the provider properly so the form shows the chosen provider.
Check whether you are on the correct record before selecting the provider.
If not, move to the right record first and then make the selection there.
Check the rest of the same form after selecting the provider.
If another visible issue remains, fix that as well.
Related issues
I cannot continue because no registry type is selected
What this usually means
The current form still does not show a value in Registry type. The issue is usually on that field.
What to check and how to fix it
Check the Registry type field on the current form.
If it is empty, choose the correct value.
Check whether the field was opened or changed without the value being kept in the form.
If so, select the value again and confirm the form now shows it in Registry type.
Check whether you are editing the correct record before changing Registry type.
If not, move to the right record first.
Check the rest of the same form after updating Registry type.
If another visible issue remains, fix that as well.
Related issues
I cannot continue because no contract is selected
What this usually means
The current record still does not show the contract selection it needs. The issue is usually in the part of the form where this record links to a contract record.
What to check and how to fix it
Check the part of the current form where this record links to a contract.
If no contract is selected there, choose the correct contract record.
Check whether the form shows text or a partial entry instead of a selected contract record.
If it does, complete the selection so the chosen contract is shown on the record.
Check whether you are on the correct record before linking the contract.
If not, move to the right record first and then select the contract there.
Check the rest of the same form after linking the contract.
If another visible issue remains, fix that as well.
Related issues