FAQ and common errors when using the Tagger

The Tagger displays an error message when loading a taxonomy.

Please activate the license by adding an license key and clicking on Activate License (menu Info → License).

When activating a license with license key, the error "The LicenseSpot server cannot be reached at this time" appears:

The Tagger does not seem to have internet access, and can't activate and download the license via internet. The connected server URL is https://app.licensespot.com. To solve this issue, whitelist the above mentioned URL or contact xbrl-support@amana.de to get an offline license file.

Please try out the following:

go to Settings -> XBRL Processor Settings

If you have a proxy server, please add the settings or select "Use system proxy (Internet Explorer)".

Now try to activate again.

When validating the document, the warning "Please set the XBRL Identifier in the Report Settings" is displayed:

When validating with the Tagger, the error "Table element" is displayed:

It is necessary to tag an abstract element to the table. Every tagged table needs an abstract element from the basic taxonomy. It can be added per drag & drop in the Table Tag are above every table.

When validating with the Tagger, the error "Duplicate" is displayed:

Click on the error message to jump to the table, where the error occurred. Several table cells are tagged to the same taxonomy element but with different values (inconsistency). This might also happen, when the Tagger is unable to identify the correct reporting date for a column. Please make sure that the reporting date for any tagged cell is correct by checking the Table Cell Properties of a selected range of cells:

Tags can only appear twice in a document if the context is different or the value is equal.

When validating with the Tagger, the error "Tagging element missing" is displayed:

When generating XBRL, the error "Your report is not valid" is displayed:

This message is displayed, if the report is missing some mandatory mappings or has mapping inconsistencies (to be seen Status button in the left bottom corner). Please correct all errors (those having  before the message) and then generate iXBRL. However, it is possible to generate an XBRL file - but generation may fail with errors.

It is not possible to create Taxonomy extensions, button is deactivated:

Make sure that taxonomy extensions are enabled in the Document Settings:

It is necessary to remove the old license before activating the new one,

To do so, go to Info → License → Open License Folder and remove the license files displayed in the folder, or click on the "Remove License" button

Restart the Tagger and activate the License with your new license key again.

After converting an Word Document to iXBRL some pages are missing and there are no page breaks. 

MS Word does not always save all page breaks to the DOCX file, so the Tagger does not know where a page ends and starts. To fix this, a Macro in Words developer tools can be run, which will make sure that all page breaks are properly included. To run a Macro, open the Word Document and see open the Macro Editor (either hit ALT+F11 or go to the developers tab end click on "Visual Basic".

In the Visual Basic editor window, copy&paste the macro from below and click "Run" (for more information on see MS Word Macro Documentation).

When validating the document, the warnings "Status" are displayed:

Check the affected cells and set the status to final:

When validating the document, the warnings "Without mapping" is displayed:

When validating the document, the following warnings is displayed:

When validating the document, the error "No anchors" is displayed:

Every extension needs at least one anchor, unless it is the total of a calculation relationship.

When validating the document, the warning "reported/calculated total" is displayed:

When validating the document, the error "format is incompatible" is displayed:

The Tagger displays the following error message when loading a Word file:

Please go to the Word file and add at least one headline (work with Styles):

Please make sure that the headline style is defined correctly:

go to Styles → Modify

select Format → Paragraph:

Make sure you work with levels: the outline level is not Body Text:

After that save and load the document again.

The Tagger does not display the headlines defined in the Word file:

Please make sure that the headline style is defined correctly:

go to Styles → Modify

select Format → Paragraph:

Make sure you work with levels: the outline level is not Body Text:

Save the changes and load the document again. The correct headlines are displayed:

Why can’t I tag a a table in a PDF document (table selection is grey)?

Why does my converted PDF file not look good?

The limitations of the PDF converter:

1. CID (identity H) fonts embedded to the source document.
   1. In this case, the converted document can contain unreadable (weird looking) text. To resolve this it is recommended to save the source document as PDF/X format in the Adobe Acrobat DC "Print Production" tool. 
2. If the converted document has wrong a color palette see step 1.
3. The converter does not support PDF hidden text layers.
   1. If so, you should remove hidden text layers in the Adobe Acrobat DC "Redact" tool.
4. The converter has fine tuning options helping to resolve the issues:
   
   1. 
   2. Please change the option "PDF unicode CMaps handling" to "Auto" and "Use autohint on fonts without hint"to "Use AutoHint" if the converted document does not look good.

If the conversion still doesn't meet the expectations or some tables cannot be tagged properly, the source file might need corrections. 

The following cases are known:

1. The converted PDF looks good, but the imported table is unreadable.
2. Converted PDF contains unreadable fragments.
3. PDF document has not converted at all in the Tagger
4. Converted PDF shows wrong colors, visual artifacts or extra
   text fragments or pages.

For case 1-3 there are two methods to repair the document in Adobe:

1. Export the PDF to postscript and create a new file from it in Adobe Acrobat Distiller DC,
2. Convert PDF to the stadard PDF 1/A with Adobe Preflight in the "PDF standards" tool.

For case 4 use "Sanitize Document" in the "Redact" tool and convert the document to PDF/X for correct colors.

If the document after all processing still has artifacts the "fallback mode" option in the Tagger can be used.

The Tagger raises InvalidCalculation issues, even if the values are adding up exactly

The reason is, that the XBRL report will have an accurrancy setting. In the example on the left, the values are reported in millions, but with one decimal place. It is required to incease the accurracy of the XBRL facts by setting the decimal attribute to -5 (millions with one decimal place) instead of minus -6 (millions). To change the decimals settings, please open "Document" menu and click on "Settings" and then "Advanced settings" tab.

The Tagger main windows is empty when starting the Tagger

The taxonomy might have to be updated to the version that is deployed with the Tagger. ESMA does not include all languages by default in the entry point. Our package fixes that issue.

1. Download the complete taxonomy:
   https://downloads.amana-consulting.de/xbrl/tagger/Cache/XBRLCache.zip
2. Select "Import Taxonomy ZIP file"
   
3. Select the downloaded taxonomy file
4. The taxonomy will be updated.
5. The taxonomy needs to be reloaded

After the update to the version 1.6.8, the current taxonomy version is loaded automatically after clicking on "Load Taxonomy"

In case your file is tagged with an older taxonomy version, when it is opened in the XBRL Tagger, the tool asks you, if you want to update to the latest version:

Please confirm, if you want to work with the latest ESEF taxonomy version or click on "No" to continue with the old one.

When you generate the Table Preview, the XBRL Tagger displays every tagged table in the dropdown.

If this is not the case and your tables (Income Statament; Cashflow Statement etc.) are not to be found, please make sure that every tagged table has a corresponding name under Table Properties:

• go to Table Tagging tab

• click on Table Settings 
• Add the name of the table:

When you generate the Table Preview, the XBRL Tagger displays every tagged table in the dropdown.

Here you can check, if the order of individual items within a statement is correct and matches the order in the pdf/Word file:

If this is not the case, please make sure that:

• the abstract items are added to existing tags in order to create a structure in your presentation linkbase (more here: User Manual#Taggingofabstracthierarchies)
• every tagged table has a corresponding name under Table Properties (see issue # 33). If the Statement of Financial Position consists of 2 tables, please make sure that both tables have the same name and are displayed under 1 chapter in Table Preview.

Sometimes loaded Word files do not look good after conversion to HTML, for this purpose there are 2 convertors, which can be used for Word files: please switch here:

Start the Tagger and click on "Convert to XHTML" in the "Tools" menu. Select the file and click on "Create XHTML Document".

Why do I get an error message (code FormulaAssertion) when submitting my report to the Bundesanzeiger?

This error message means, that there are warnings or errors left that are based on the XBRL Instance Formula 1.0 validation. Please review those messages that are displayed by the XBRL Tagger when generating the XBRL report. If harmless warnings are left, just continue to submit the file.

When using the Word converter, some text is jumping between the page breaks. How can I fix this?

The issue is the same as #40, with free floating text not being able to be converted correctly. In these cases, try to use tables with invisible borders to position items correctly in the footer:

When converting and tagging a PDF report with special font face in the XBRL Tagger, some facts (tags) might become hidden. The reason is, that the Inline XBRL Specification does not allow individually formatted numbers to be tagged. E.g. when the font requires a special spacing between single characters by using HTML tags like <span>, the number is no longer taggable. In the screenshot below, the number 24,540 is not taggable. In order to preserve the spacing and formatting of the PDF in the XHTML report, the XBRL Tagger moves the tag to an unformatted hidden section of the document and includes a link to the visual original number.

However, hiding facts is an official mechanism of the Inline XBRL specification, as well as allowed by ESMA in the ESEF Reporting Manual, page 23:

From AMANAs point of view, untaggable items like the numbers in the example above are not eligible for transformation and can be hidden. The XBRL International standard setter working group is aware of the issue and will probably publish and update Inline XBRL specification, which will make those numbers taggable in the future.

Please continue reading about how to reduce the number of hidden facts in FAQ .

There are multiple ways to avoid or reduce hidden facts in iXBRL reports:

• Tag Microsoft Word files instead of PDFs
• Do not use special non-web fonts in PDF reports, that provide a special spacing between characters.
• Set the XBRL Tagger CMaps option to "Ignore" when opening a PDF file (might lead to uglier reports).
  
• Use the latest XBRL Tagger version 1.7, which includes some new options to reduce/avoid hidden facts.
  
• All numbers that are tagged needs to have the OpenType setting “Default figure Style” to avoid “Hidden facts”. This setting only effects the digits in the report.
  To apply this setting you can manually choose “Default Figure Style” in the number columns or you can apply the setting in the Paragraph Style under “OpenType features”. Use 0 kerning in the tagged cells for best result.
  
• Other problems that can occur when you convert the PDF to XHTML is:
  • Text opacity If you have a text with opacity in the document the opacity will go back to default 100% after the conversion to XHTML. It will work if you create outlines of the text.
  • Text behind If you have text hidden behind something in InDesign the text will be visible when you convert to XHTML.

The taxonomy might have to be updated to the version that is deployed with the Tagger.

1. Download the complete taxonomy:
   https://downloads.amana-consulting.de/xbrl/tagger/Cache/XBRLCache.zip
2. Select "Import Taxonomy ZIP file" in the XBRL menu.
   
3. Select the downloaded taxonomy file
4. The taxonomy will be updated.
5. The taxonomy needs to be reloaded

XBRL reports (like ESEF) usually come with an entity specific Calculation Linkbase, that defines how totals in tables are calculated. If calculation inconsistencies are signalled, it means that the calculated value of a total differs from the actual reported value. However, some calculation inconsistencies are often unavoidable: Due to reporting of rounded values (e.g. to millions), small rounding differences are “common practice”. In order to distinguish rounding inconsistencies from real calculation issues (that usually indicate tagging issues), the AMANA XBRL Engine allows to enable a Calculation Linkbase Validation Severity Error Threshold, which must be configured in the XBRL (user based) settings. If the threshold is activated and set to e.g. 1%, it means that the all calculation inconsistencies where the delta is smaller than 1% of the rounded reported value are deemed to be WARNINGS, while all inconsistencies with differences bigger then the threshold are deemed to be ERRORS. If the threshold is not set, all calculation inconsistencies are signalled with a WARNING severity.

Further reading:

https://www.xbrl.org/esef-errors-and-common-pitfalls-8-rounding-and-calculations/

To activate this threshold you have to click on Settings>XBRL Processor Settings.

In the window you can mark the first option.

1. Just download ony of the taxonomies that you would like to report, e.g. the HMRC Taxonomy:
   https://www.gov.uk/government/publications/taxonomies-accepted-by-hm-revenue-and-customs/taxonomies-accepted-by-hmrc
2. Click “Open/Load” taxonomy in the “XBRL” menu in Tagger 1.8.4.
3. Select “Load Taxonomy Package” and import the ZIP file via the “Add” button, then close the Taxonomy Package Manager
   
4. Then load the corresponding entry point and start tagging.
   

1. The XHTML must be converted into a PDF, for this purpose the XBRL Auditor can be used or also a web browser like Chrome. Using the scale function it should be ensured that the page breaks do not differ.
   
2. Using a PDF comparison tool, you can then make the differences between the contents visible. Various third-party tools are available for this purpose:
   1. PDiff Pro - is a lightweight PDF comparison tool that can easily compare only the content (even of tables), without taking into account the different formats.
      https://www.csci.de/en/pdiff/
   2. Adobe Acrobat - is also suitable, but it is slower and more sensitive to different formats. When comparing, the option "Compare text only" should be enabled.
      https://helpx.adobe.com/acrobat/using/compare-documents.html
3. In the last step, a manual visual inspection of the formatting can be carried out:
   a.    Are the page breaks correct
   b.    Have headers and footnotes been transferred correctly.
   c.    Are graphics displayed correctly in the ESEF report.

1. You can download the taxonomy here: https://www.efrag.org/Lab4
   After downloading the taxonomy you have to unzip the downloaded file.
2. Copy the efrag.org folder from the original folder.
   
3. Go to you cache folder. You can find it using this path: C:\Users\USERNAME\AppData\Roaming\AMANAconsulting\xbrlcache
4. Paste the copied folder into your cache folder:
   
5. Open your Tagger and click on Open/Load Taxonomy.
   
6. Choose the Option Define Custom EntryPoint:
   
7. Enter the EFRAG EntryPoint: http://efrag.org/xbrl/esrs/2022/esrs-all.xsd
   
8. You are done.
   

How can I change the layout setting for Word?

Document View Type:

It is now possible to define the view type for converted Word documents. The available options are FullScreen, Manuscript and Pages. Just try them out to see what fits your report best.

• FullScreen: corresponds to the old setting WITHOUT activated "Use A4 layout for Word" (unpaginated layout).
• Manuscript: this is the new mode. It is also unpaginated, but the text is limited to the page width set in the WORD file.
• Pages: the same as WITH the checkmark "Use A4 layout for Word" set.

Why are the following messages displayed? "This Word document contains embedded charts." / "The Word document has shapes/images as embedded Office objects."

@escaped attribute: True/False

All text block tags can be given an @escaped attribute that controls whether the XHTML tags should be included in the XBRL instance document or not. By default, the escaped attribute is set to False, according to Guidance 2.2.6 of the ESEF Reporting Manual (page 33). Changing it to True is not necessary, but is recommended by some auditors. 

When the escaped attribute is set to True, some iXBRL viewers display the tag contents with more spaces. However, this depends on the iXBRL viewer used and is by no means standardised. For example: 

Should you wish to change all escaped attributes for already tagged elements already set to False to True (or vice versa), this can be done by editing every individual tag. 

After generating iXBRL, the error message "No linkRole found for filter" is displayed:

Two or more versions of the same taxonomy are loaded.

How to remove the additional taxonomies:

1. Select "XBRL" > "Manage Additional Taxonomies".
   
   
   
2. Click on next to all additional versions of the currently used taxonomy to remove them. The currently used taxonomy can be found in the bottom left corner next to the status icon.
   
3. Save document (via "File" > "Save", CTRL+S or ).
4. Reload document (via "File" > "Open", CTRL+O or ).

How to switch to a newer version of a taxonomy:

After generating iXBRL, the error message "Unable to find XHTML_td cell for mapping ifrs-full:..." is displayed:

This error appears because you have two tables with the same id in the table properties.

1. Open the document in Word
2. Identifiy the tables,
3. Right click on the second table

 4. Removed duplicate id in the description of the second table

  5. Load the document again into the Tagger

Cannot create grouping for "ifrs-full....", loop detected. Ignoring group.

For example:

In addition you should make sure, that you do not use the same abstract twice in the same table:

If your report looks like this, you will receive an error message.

After creating the ESEF report, the numbering in the xHTML file is different to the orginial Word file.

Why do I get the error "DimensionallyInvalid" for an element, that should be in the Text Block section?

How to use a local copy of the Taxonomy?