This happens often during setup. The engine didn’t recognise the label in the first column of the table.
Next to spotting this in the preview using the "Highlight" feature in the top right of the screen, you can also spot these errors in the "Conversion report" section of the error report.
There can be various reasons why labels are not being recognized:
- Some labels always need a custom label to be recognized correctly. This is indicated in the Excel you received when the initial mapping was done. An example is the "Balance at 1 January 20xx" in the Statement of Changes in Equity. For this line you always need to set the ESEF label property on the table cell that contains the text, and set it to "Equity at beginning of period".
- This can be because the text in the table has been changed from what has been mapped before. In most cases the mapping has been done correct earlier but the labels have been changed since. Sometimes to fix a spelling mistake, sometimes because it will look better in the document. Ideally the new spelling is added to the mapping. So if you are still gathering input for mapping changes, please include these cases in the update of what is changed.
If the change in label is minor and you are sure that it is not an indicator that a different tag should be selected for this line item, this situation can also be fixed by adding the original text to the ESEF label property on the table cell that contains the label.
Please note: even adding or removing a space, - or other (on first glance) minor changes, can cause cells to not be recognised by the engine. The engine uses auto-tagging, but only when the exact label is known to the system. - If it is a new label, then this should be mapped. Please note that it will take at least a full week for a mapping change in the engine. It is wise to freeze changes a week prior to publishing the ESEF file.
- A custom label was set while not needed or not removed correctly. Remove the ESEF label property by using the trashcan.
In most cases cells aren’t recognised by the engine due to changes in wording, this is the best way to start your investigation and gives the quickest results.
0
0
Was this article helpful?
0 out of 0 found this helpful
Articles in this section
- I am missing certain block tags
- Cells are not tagged in the viewer (not green or pink)
- message:positive - Reported value is below 0
- xbrl.5.1.1.2:balanceCalcWeightIllegalPositive
- Common ESEF error messages
- Why is the ESEF button not visible for me?
- What taxonomy version is used?
- ESEF.RTS.Annex.III.Par.1.invalidInlineXBRL
- html:syntaxError
- Error: Export of chart[1] failed in section