Skip to content
  • There are no suggestions because the search field is empty.

Validating Your XBRL Report - Validation Messages

Introduction

Below is an explanation of validation messages, and their possible solutions, that you might see while using the tagger and creating an XBRL report. We recommend you to use the search function (Ctrl + F on Windows, Command + F on a Mac) to help navigating the list. The validation messages are split between Inline Validations (that you can see in the tagger) and Report Generation Validations (that you can see in the validation report).

Inline Validations

  • Duplicate mapping detected (or Duplicate mapping error) - For each period, a tag can only be used once unless the reported value is the same. If the same tag would appear a second time with a different value you will get a Duplicate mapping error, see our dedicated page for further troubleshooting.
  • Duplicate Label - Appears if you have the same tag in two different places where the Label of the Element is different. You find the setting for the Label of the Element in the Properties tab, it needs to be the same on every instance of the tag.
    Please note that if you are using the Extension Labels Only as your Label Handling Option in your XBRL project settings, then you can discard these validations (unless it is an extension) as the official labels from the taxonomy will be used.
  • DimensionallyInvalid (please see the two different versions below):
    1. Tagging is dimensionally invalid due to missing parenthetical - This error message typically appears when you apply a monetary tag without an abstract. Follow the instructions on our support page to clear this message.
    2. Dimensional inconsistency between hierarchy and tagged elements in table - Each column mapping in the Statement of Changes in Equity table has to contain the same dimension. 
  • DocumentValidation - Please check the continuation order for element [NameOfTag] on layer ['NameOfLayer'] - This message is related to Textblock tags. As per requirement from ESMA, the Textblock tags should appear in a human readable order. To clear this message from your validation, right click on the Textblock tag in the "Text Tagging" tab and select "Continuation Administration". A new window will pop up which shows a list of content this tag has been applied to. To ensure the ordering is correct, click on the blue arrow on the bottom left, then click "Save". Read more about continuation errors here.
  • Invalid anchors (extension element has no anchors) - Every custom extension to the taxonomy needs at least one anchor to the original XBRL taxonomy, unless it is the total of a calculation relationship, see our dedicated page for further instructions.
  • Invalid Calculation, the reported total does not match the calculated total - Your calculated total is incorrect. To try and fix the calculation, please click the Properties tab and check that:
    • The cells have the correct Number or Date Format.
    • The cells have the correct Decimals (if your numbers are being rounded incorrectly, try increasing the number by 1 (e.g. from -6 to -5)).
    • The cells have the correct SignLogic.
    • If the above criteria are met and you still get an Invalid Calculation, it could be due to a mismatch in the Calculation Linkbase. See Report Wide Calculations for more details.

    Please be aware that you cannot have calculations with both Instant and Duration Period types. You will need to delete this calculation.

  • Invalid Calculation, for at least one calculated element the selected period type or date does not match the total element - The date or period type (i.e. instant or duration) of the tag is incorrect. Please click the Properties tab in the bottom left hand pane and check the Instant/End Date and Period Start Date value. If you have created an extension, please use the Taxonomy Extension Properties tab to change the period type if necessary.
  • Invalid Format, the selected format is incompatible with tag - An incorrect base format has been applied, e.g. a date format for a monetary value. Please check that you have used the correct tag.
    • Select the tag in the right hand pane.
    • In the Tags tab in the bottom left hand pane, click the name of the tag.
    • Click on the Properties tab in the bottom right hand pane.
    • Scroll down to the end where it says Type and see what type of data is required and if it matches the cell's value.
  • Invalid Value, the value '–' is not valid for selected XBRL format '123 456.78 | 123,456.78 (ixt:num-dot-decimal)' (or num-comma-decimal) - Please select the cell with the value '-', click the Properties tab and change the Number or Date Format to fixed-zero.
  • An adjacent cell has a different tag, please check if this is intended - A Warning that are for information purposes only and as such can be ignored. Please check so that the tags that are applied to the row is correct. If you have tagged a split table (see more information on this page), make sure you set the correct Table Split Column ID according to the instructions at the bottom of the page above.
  • The mapping for a duration type element has a StartDate that is later than the EndDate. Please set a correct StartDate - Please select the tag, click the Properties tab and change the Instant/End Date value to be later than the Period Start Date value.
  • Unresolved mapping - This error message indicates that tags you applied in a previous version cannot be reapplied in the version you just opened. We recommend that you take note of the tags mentioned and re-apply the tags. Read more about this here.
  • Document Validation, cell still in Review pending status - To clear this message, right click on the yellow cells in your financial statement(s), select Set status, then Final.
  • Element Missing, line item missing - A cell in the statement of changes in equity table has dimension members tagged, but no line item tags. This can be corrected by applying line item tags to the cells.
  • Table (Table Name) has no table element mapped - Every table containing tags needs to be tagged with a table (abstract) tag.
    • Click and select the table in the top-left hand pane.
    • Drag a table (abstract) tag from the taxonomy in the top right-hand pane to the link next to the row called Table Tag.
  • Error, A loop has been detected between "...." - This validation error usually occurs if the wrong abstract tag has been used. As a general rule the first Abstract in the folder is the one to start with. If you’ve split one statement into two tables, both tables must be tagged with this same abstract tag. Correcting the tag will clear the error message.

Report Generation Validations

  • Reported value is below 0 - By default, the XBRL taxonomy elements are defined as a positive value. If the reported value (XBRL Value) is below 0, this warning will be displayed in your validation report.
    As an example, the element ifrs-full:CostOfSales should be reported as a positive number, even if it is usually presented with a negative sign on the face of the financial statements. Therefore, in this example the SignLogic for ifrs-full:CostOfSales would need to be set to Reverse. For more information on SignLogic, please visit this page.
  • Document contains private characters (private character \uE01F was found 1 time in non tagged areas) - This message is related to "hidden data" and can appear if you have used substituted glyphs in your InDesign document. You can correct this in InDesign by following the instructions here. Please note that this warning can refer to untagged text content, which means that you will not be able to identify it with searching for ix:exclude in the XHTML-document (as per the instructions on the page linked to). We recommend consulting CtrlPrint Preflight to help prepare your documents for XHTML compatibility. See our dedicate CtrlPrint Preflight article for more information.
  • The 'x-id' attribute is not declared - This error most often occurs when a table in the notes has been semantically defined more than once. Review the note chapters to identify the chapter containing the issue by checking the validation report at the chapter level. Compare the number of tables defined on each page (see image below) with the number of tables actually visible in the document. If more tables are defined than are visible, that page is likely the source of the problem. Then review all layers on the page and ensure that each semantically parsed table is defined only once.
      
  • Nested continuations, continuation with ID '(number)' is nested in fact (tag) - Relates to continuations that originate from the same tag and intersect the same text content, see our dedicated page for further instructions.
  • According to the IAS 1, comparative information must be disclosed in respect of the previous period for all amounts reported in the financial statements, both on the face of the financial statements and in the notes, unless another standard requires otherwise. Please make sure that XBRL context instant period is provided with at least two unique date values. -If this message appears, it may be because the validation report was generated for a single chapter in which the primary financial statements have not been tagged. In that case, the validation message should disappear once a merged report of all chapter (the whole project) is generated. 
  • The fact with Id fact-[XX] is dimensionally not correctly linked. Either a mandatory dimension is missing or an unneeded dimension is added. - This message appears, with a reference to the tag, if you have applied a monetary or PerShare tag in the preview tab without applying an abstract on top of it. Please see our article on parenthetical tagging for further
  • Guidance 2.2.7: Technical construction of a block tag -  Use Escape Attribute “True” for all textblock tags. For all other tag types, including string elements such as NameOfReportingEntity, use Escape Attribute “False”. The Escape attribute can be set in the properties tab of the text tag or via the Tool box-function under the Options menu in the Tagger.
  • Guidance 2.4.1 XBRL constructs that should be avoided: [transformableElementIncludedInHiddenSection] The ix:hidden section of Inline XBRL document MUST not include elements eligible for transformation - Relates to Hidden Facts that are present in the report. See our article on how to Detect Hidden Facts in Your XBRL Report as well as our article on Recommended Settings to Avoid Font Problems with Hidden Facts.
  • Guidance 2.7.1 Ensuring report validity against XBRL specifications: [targetXBRLDocumentWithFormulaWarnings] Target XBRL document SHOULD be valid against the assertions specified in ESEF taxonomy with severity set to http://www.xbrl.org/2016/severities.xml#WARNING appearing as target of generic arc with http://xbrl.org/arcrole/2016/assertion-unsatisfied-severity arcrole. - The message indicates that your report has some minor issues that don't prevent it from being submitted. These issues are flagged as warnings because they might be due to rounding differences or other minor discrepancies.
  • Guidance 3.1.1 Required components of extension taxonomies: [extensionTaxonomyWrongFilesStructure] Extension taxonomies MUST consist of at least a schema file and presentation, calculation, definition and label linkbases (No calculation linkbase or No label linkbase). - This message indicates that your extension taxonomy is missing a calculation linkbase. This is a crucial component required for proper XBRL reporting. You need to apply calculations where appropriate to ensure it meets the necessary standards. If the message only says No Label Linkbase, it may be because you downloaded a validation report for a single chapter in which the primary financial statements have not been tagged. In that case, the validation message should disappear once you merge the chapters and generate the XBRL report for the full project.
  • Guidance 3.4.6 Restrictions on taxonomy relationships: [UsableConceptsNotAppliedByTaggedFacts] -  This message appears, with a reference to the tag, if you have applied a monetary or PerShare tag in the preview tab without applying an abstract on top of it. Please see our article on parenthetical tagging for further instructions. 
  • Guidance 3.4.2 Defining the dimensional validity of line items in the definition linkbase: [extensionTaxonomyLineItemNotLinkedToAnyHypercube] Line items that do not require any dimensional information to tag data MUST be linked to “Line items not dimensionally qualified” hypercube. -Please refer to the instructions under guidance 3.4.6 to resolve this validation error..
  • RTS Annex II Par 2 Issuers shall mark up all disclosures made in IFRS consolidated financial statements or made by cross-reference therein to other parts of the annual financial reports for financial years beginning on or after 1 January 2020 that correspond to the elements in Table 1 of this Annex: [missingMandatoryMarkups] Missing mandatory markup in the report (ifrs-full:NameOfReportingEntityOrOtherMeansOfIdentification, ifrs-full:ExplanationOfChangeInNameOfReportingEntityOrOtherMeansOfIdentificationFromEndOfPrecedingReportingPeriod, ifrs-full:DomicileOfEntity, ifrs-full:LegalFormOfEntity, ifrs-full:CountryOfIncorporation, ifrs-full:AddressOfRegisteredOfficeOfEntity, ifrs-full:PrincipalPlaceOfBusiness, ifrs-full:DescriptionOfNatureOfEntitysOperationsAndPrincipalActivities, ifrs-full:NameOfParentEntity, ifrs-full:NameOfUltimateParentOfGroup). - There are a few mandatory string tags that must be applied in your ESEF report as defined by ESMA. This message is listing those that are outstanding in your report. However, keep in mind that these are only mandatory if applicable. We advise you consult your auditors regarding this. 
  • RTS Annex II Par 1; RTS Annex IV Par 7 To identify to which part of the financial statements the markups relate, issuers shall use dedicated root taxonomy elements as starting points for the respective parts of the financial statements in their extension taxonomy’s presentation linkbases. The element names, labels and prefixes of these root taxonomy elements shall be as set out in the Table 1: [missingPrimaryFinancialStatement] Missing primary financial statements in the presentation linkbase of the report.- If this message appears, it may be because the validation report was generated for a single chapter in which the primary financial statements have not been tagged. In that case, the validation message should disappear once a merged report of all chapter (the whole project) is generated.
  • RTS Annex III Par 1 Issuers shall ensure that the Inline XBRL instance document is valid with respect to the Inline XBRL 1.1 specification and is conform to the XBRL Units Registry.: [invalidInlineXBRL] Invalid inline XBRL - This validation error indicates that other errors in the report must be resolved before the report can be considered valid. Once those errors have been corrected, this error should disappear as well.