XBRL
Space shortcuts
Page tree
Skip to end of metadata
Go to start of metadata

#IssueSolution
1

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).

2

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.

If this does not work either, contact us about manually activating the license, as described in Installation and Update.

3

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

A valid ESEF document needs the proper LEI of the filer: www.gleif.org

Please go to Document → Settings and enter the LEI under "Reporting Entity Identifier (e.g. LEI)"

4

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.

5

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.

6

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

This error message is displayed if a dimension element is tagged (member), but there is no corresponding line item tagged.


7

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.

8

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

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

9

You receive a new license key after the old license expired, but it is not possible to activate the new license.

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.

10

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).

Fix Pagebreaks MS Word Macro 
Sub tryUnlinkFields()
On Error GoTo fehler:
ActiveDocument.Fields.Unlink
Exit Sub
fehler:
'Einzeln versuchen
Dim i As Integer
For i = ActiveDocument.Fields.Count To 1 Step -1
ActiveDocument.Fields(i).Unlink
Next
End Sub



Sub edgarizingPreProcessing()
Debug.Print "Start: " & Now

'Wichtig, weil sonst Seitenumbrüche innerhalb von Feldern schief sein können.
tryUnlinkFields

Dim lastPage As Range
Selection.GoTo wdGoToPage, wdGoToLast
Set lastPage = Selection.Range

Dim r As Range
Selection.GoTo what:=WdGoToItem.wdGoToPage, which:=WdGoToDirection.wdGoToFirst
Set r = Selection.Range

'r.Comments.Add r, "Das ist Seite 1!" 'Debugging-Code
ActiveDocument.Bookmarks.Add "SN_PAGEBREAK_1", r

Dim counter As Integer
counter = 2

While r.Start < lastPage.Start
Selection.GoTo what:=WdGoToItem.wdGoToPage, which:=wdGoToNext
Set r = Selection.Range

'r.Comments.Add r, "Das ist Seite " & counter & "!"

ActiveDocument.Bookmarks.Add "SN_PAGEBREAK_" & counter, r
counter = counter + 1
Wend

Debug.Print "End: " & Now
End Sub
11

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

Check the affected cells and set the status to final:

12

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

A cell in a table with table tag has no mapping. All cells in the report need to be tagged.

13

When validating the document, the following warnings is displayed:

All tagged cells in the report have to be part of a calculation relationship.
14

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.

15

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

The rounded total of a calculation relationship does not equal the rounded calculated total. Does not need to be valid!

16

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

A wrong base format has been applied, e.g. a date format for a monetary value. Please check the tag.
17

When validating the document, the error "The value is not valid for the format" is displayed:

The value is not valid for the format

The selected format cannot be applied to the value of the tag.

18

When validating the document, the error "Tagging element not found in taxonomy" is displayed:

Tagging element not found in taxonomy

The tagged element was not found in the taxonomy. Please check if you have a different version of the taxonomy, which does not contain the tagged element.

19

When validating the document, the error "Dimensionally invalid" is displayed:

Dimensionally invalid

Each mapping in a table has to contain the same dimensions

20

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.

21

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

 

instead of defined in Word:

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:

22

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

Before tables form PDF documents can be tagged, please perform the steps documented here.

23

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:
    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.

24

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.

25

The Tagger update disappears: it has to be updated every time after the system restart

This happens, when BOTH Tagger versions are installed, the click-once installer Setup.exe and the MSI Installer. To solve this issue, just deinstall both versions, and install the Setup.exe (click-once installer) again. The MSI Installer does not support the integrated update functionality.
26

Why does the XBRL Tagger ask me to download pdf2htmlEx?

In order convert a PDF document to XHTML and keeping all formats, AMANA recommends to use a third-party XHTML converter, called pdf2htmlEx. This converter is published under GPL v3 and free to use. However, it can't be distributed with the XBRL Tagger, so users are requested to install it themself. AMANA forked the converter and published a version under the GPL v3 version here:

https://github.com/amanaconsulting/pdf2htmlEX

In order to install the pdf2htmlEx converter, please download pdf2htmlEx ZIP file under "Releases" and extract it to %appdata%\AMANAconsulting folder, like in this sample:

C:\Users\user.name\AppData\Roaming\AmanaConsulting\pdfToHTMLEx\{version}\

With {version} being the current release tag from github, i.e. "0.14.7-win" 

The XBRL Tagger does not link this binary in the source code, but rather calls the converter via command line and returns the resulting XHTML to the XBRL Tagger for tagging purposes.

You can find additional information on the installation process here.

27

How can I go back to an old version of the XBRL Tagger after updating it?

When updating the XBRL Tagger, one old version will always be preserved. For instance, if updating from version 1.7.1 to 1.7.2, the version 1.7.1 is still installed. It can be started manually, by running the AMANA.XBRL.Tagger.exe in the users local AppData folder, which can usually be found here:

C:\Users\user.name\AppData\Local\AMANA\app-1.7.1\AMANA.XBRL.Tagger.exe

28

The Tagger user interface looks ugly, fonts and controls (boxes) are not at the right place

This happens due to scaling issues when activating scaling of the Windows Desktop and usually when working with multiple monitors. The issue usually can be solved by:

  1. Activating Windows display setting "Fix blurry apps" https://support.microsoft.com/en-gb/help/4091364/windows-10-fix-blurry-apps
  2. Restart the computer (real restart, no sleep mode).
29

The Tagger main windows is empty when starting the Tagger

This happens, when a custom scaling is defined in the display settings of the Windows operating system. To fix this issue:

  1. Please disable the custom scale rate in the display settings like described here: https://support.microsoft.com/en-us/windows/view-display-settings-in-windows-10-37f0e05e-98a9-474c-317a-e85422daa8bb
  2. Log off and log on again
  3. Start the Tagger, the issue should be resolved.
30

The taxonomy is only available in English/cannot be loaded

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
31

How to load the taxonomy version 2020?

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.

32

I have tagged one language version of my report, how can I transfer my tags to another language version?

When transferring the tags from one language version to the other, a few things have to be considered:

  1. Open the tagged report in the Tagger and open a second Tagger windows with the translation report.
  2. Enter the same basic settings under Document Settings, but adjust the report language drop down.
  3. Copy & paste the tags from the original report to the translation version using the Clipboard manager.
  4. Make sure, all extensions have at least one standard label in the report language.
  5. Ensure, that all number formats are correct.
  6. Apply the Packaging and Publishing of ESEF iXBRL Reports checklist, and review if all numbers are converted properly in the preview.
33

The tagged tables are not displayed in the Table Preview/are displayed under one role

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:

34

Presentation Linkbase: order of the individual items within a statement does not match the order in the pdf/Word file

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.
35

Switch Word to HTML converter

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:

36

How can I convert an PDF or Word Document to XHTML without tagging?

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

37

What does the warning message "Reported values for alternative tagging of same economic concept are not equal" mean?

The "Reported values for alternative tagging of same economic concept are not equal" warning should be investigated. It is part of the Formula validation of the ESEF/IFRS taxonomy. If it appears you should be able to right click the message, then select “More information” and get a list of the cells involved. As for the meaning of the warning:

This checks if values that are equal in meaning but different in tagging have the same value, e.g.

Non-Dimensional Concept: Cash flows from (used in) investing activities, discontinued operations

Should be equal to

Concept: Cash flows from (used in) investing activities

Used with Dimension: Continuing and discontinued operations [axis] and Member: Discontinued operations [member]

38

What does the warning message "Reported value below zero" mean?

The "Reported values below zero" warning should be investigated. It is part of the Formula validation of the ESEF/IFRS taxonomy. If it appears you should be able to right click the message, then select “More information” and get a list of the cells involved. As for the meaning of the warning:

By default, the ESEF/IFRS XBRL taxonomy elements are defined in a positive way. For instance, the item "Cost of sales" should be reported as a positive number, even if it is usually reported with a negative sign on the face of the financial statements. Use the Sign-Logic in the XBRL Tagger to invert the sign of negative numbers and subtract it from the totals via the weight attribute of the calculation (e.g. from Revenue).

Find more information on reporting of negative numbers, debit/credit attributes and calculations in the IFRS Taxonomy Preparers Guide, Page 46ff.

39

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.

40

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

This type of position is not supported by the converter and has to changed in the Word file. The text from the free floating box should be added as normal text to the footer, so that it just contains to lines. 
41

When using the Word converter, sometimes text from the footer and the page number are not positioned correctly. 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:

42

Why does my iXBRL report have hidden facts?

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 .

43

How can I reduce or avoid hidden facts in my iXBRL reports?

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.
44

How do I update the Taxonomy Cache?

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
45

Why are some calculation inconsistencies WARNINGS and some are ERRORS?

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.

if "Disable" is selected, all calculation messages are disabled

if "Enable" is selected and the threshold is not activated, all calculation messages are displayed as warnings

if "Auto" is selected, the messages are not displayed if EBA or EIOPA reports are created

46

How can I use any other taxonomy then ESEF the XBRL Tagger?

  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.
47

How can I compare my ESEF XHTML report with my audited financial statements in PDF?

  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.


#IssueSolution
1

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).

2

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.

If this does not work either, contact us about manually activating the license, as described in Installation and Update.

3

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

A valid ESEF document needs the proper LEI of the filer: www.gleif.org

Please go to Document → Settings and enter the LEI under "Reporting Entity Identifier (e.g. LEI)"

4

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.

5

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.

6

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

This error message is displayed if a dimension element is tagged (member), but there is no corresponding line item tagged.


7

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.

8

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

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

9

You receive a new license key after the old license expired, but it is not possible to activate the new license.

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.

10

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).

Fix Pagebreaks MS Word Macro 
Sub tryUnlinkFields()
On Error GoTo fehler:
ActiveDocument.Fields.Unlink
Exit Sub
fehler:
'Einzeln versuchen
Dim i As Integer
For i = ActiveDocument.Fields.Count To 1 Step -1
ActiveDocument.Fields(i).Unlink
Next
End Sub



Sub edgarizingPreProcessing()
Debug.Print "Start: " & Now

'Wichtig, weil sonst Seitenumbrüche innerhalb von Feldern schief sein können.
tryUnlinkFields

Dim lastPage As Range
Selection.GoTo wdGoToPage, wdGoToLast
Set lastPage = Selection.Range

Dim r As Range
Selection.GoTo what:=WdGoToItem.wdGoToPage, which:=WdGoToDirection.wdGoToFirst
Set r = Selection.Range

'r.Comments.Add r, "Das ist Seite 1!" 'Debugging-Code
ActiveDocument.Bookmarks.Add "SN_PAGEBREAK_1", r

Dim counter As Integer
counter = 2

While r.Start < lastPage.Start
Selection.GoTo what:=WdGoToItem.wdGoToPage, which:=wdGoToNext
Set r = Selection.Range

'r.Comments.Add r, "Das ist Seite " & counter & "!"

ActiveDocument.Bookmarks.Add "SN_PAGEBREAK_" & counter, r
counter = counter + 1
Wend

Debug.Print "End: " & Now
End Sub
11

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

Check the affected cells and set the status to final:

12

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

A cell in a table with table tag has no mapping. All cells in the report need to be tagged.

13

When validating the document, the following warnings is displayed:

All tagged cells in the report have to be part of a calculation relationship.
14

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.

15

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

The rounded total of a calculation relationship does not equal the rounded calculated total. Does not need to be valid!

16

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

A wrong base format has been applied, e.g. a date format for a monetary value. Please check the tag.
17

When validating the document, the error "The value is not valid for the format" is displayed:

The value is not valid for the format

The selected format cannot be applied to the value of the tag.

18

When validating the document, the error "Tagging element not found in taxonomy" is displayed:

Tagging element not found in taxonomy

The tagged element was not found in the taxonomy. Please check if you have a different version of the taxonomy, which does not contain the tagged element.

19

When validating the document, the error "Dimensionally invalid" is displayed:

Dimensionally invalid

Each mapping in a table has to contain the same dimensions

20

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.

21

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

 

instead of defined in Word:

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:

22

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

Before tables form PDF documents can be tagged, please perform the steps documented here.

23

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:
    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.

24

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.

25

The Tagger update disappears: it has to be updated every time after the system restart

This happens, when BOTH Tagger versions are installed, the click-once installer Setup.exe and the MSI Installer. To solve this issue, just deinstall both versions, and install the Setup.exe (click-once installer) again. The MSI Installer does not support the integrated update functionality.
26

Why does the XBRL Tagger ask me to download pdf2htmlEx?

In order convert a PDF document to XHTML and keeping all formats, AMANA recommends to use a third-party XHTML converter, called pdf2htmlEx. This converter is published under GPL v3 and free to use. However, it can't be distributed with the XBRL Tagger, so users are requested to install it themself. AMANA forked the converter and published a version under the GPL v3 version here:

https://github.com/amanaconsulting/pdf2htmlEX

In order to install the pdf2htmlEx converter, please download pdf2htmlEx ZIP file under "Releases" and extract it to %appdata%\AMANAconsulting folder, like in this sample:

C:\Users\user.name\AppData\Roaming\AmanaConsulting\pdfToHTMLEx\{version}\

With {version} being the current release tag from github, i.e. "0.14.7-win" 

The XBRL Tagger does not link this binary in the source code, but rather calls the converter via command line and returns the resulting XHTML to the XBRL Tagger for tagging purposes.

You can find additional information on the installation process here.

27

How can I go back to an old version of the XBRL Tagger after updating it?

When updating the XBRL Tagger, one old version will always be preserved. For instance, if updating from version 1.7.1 to 1.7.2, the version 1.7.1 is still installed. It can be started manually, by running the AMANA.XBRL.Tagger.exe in the users local AppData folder, which can usually be found here:

C:\Users\user.name\AppData\Local\AMANA\app-1.7.1\AMANA.XBRL.Tagger.exe

28

The Tagger user interface looks ugly, fonts and controls (boxes) are not at the right place

This happens due to scaling issues when activating scaling of the Windows Desktop and usually when working with multiple monitors. The issue usually can be solved by:

  1. Activating Windows display setting "Fix blurry apps" https://support.microsoft.com/en-gb/help/4091364/windows-10-fix-blurry-apps
  2. Restart the computer (real restart, no sleep mode).
29

The Tagger main windows is empty when starting the Tagger

This happens, when a custom scaling is defined in the display settings of the Windows operating system. To fix this issue:

  1. Please disable the custom scale rate in the display settings like described here: https://support.microsoft.com/en-us/windows/view-display-settings-in-windows-10-37f0e05e-98a9-474c-317a-e85422daa8bb
  2. Log off and log on again
  3. Start the Tagger, the issue should be resolved.
30

The taxonomy is only available in English/cannot be loaded

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
31

How to load the taxonomy version 2020?

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.

32

I have tagged one language version of my report, how can I transfer my tags to another language version?

When transferring the tags from one language version to the other, a few things have to be considered:

  1. Open the tagged report in the Tagger and open a second Tagger windows with the translation report.
  2. Enter the same basic settings under Document Settings, but adjust the report language drop down.
  3. Copy & paste the tags from the original report to the translation version using the Clipboard manager.
  4. Make sure, all extensions have at least one standard label in the report language.
  5. Ensure, that all number formats are correct.
  6. Apply the Packaging and Publishing of ESEF iXBRL Reports checklist, and review if all numbers are converted properly in the preview.
33

The tagged tables are not displayed in the Table Preview/are displayed under one role

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:

34

Presentation Linkbase: order of the individual items within a statement does not match the order in the pdf/Word file

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.
35

Switch Word to HTML converter

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:

36

How can I convert an PDF or Word Document to XHTML without tagging?

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

37

What does the warning message "Reported values for alternative tagging of same economic concept are not equal" mean?

The "Reported values for alternative tagging of same economic concept are not equal" warning should be investigated. It is part of the Formula validation of the ESEF/IFRS taxonomy. If it appears you should be able to right click the message, then select “More information” and get a list of the cells involved. As for the meaning of the warning:

This checks if values that are equal in meaning but different in tagging have the same value, e.g.

Non-Dimensional Concept: Cash flows from (used in) investing activities, discontinued operations

Should be equal to

Concept: Cash flows from (used in) investing activities

Used with Dimension: Continuing and discontinued operations [axis] and Member: Discontinued operations [member]

38

What does the warning message "Reported value below zero" mean?

The "Reported values below zero" warning should be investigated. It is part of the Formula validation of the ESEF/IFRS taxonomy. If it appears you should be able to right click the message, then select “More information” and get a list of the cells involved. As for the meaning of the warning:

By default, the ESEF/IFRS XBRL taxonomy elements are defined in a positive way. For instance, the item "Cost of sales" should be reported as a positive number, even if it is usually reported with a negative sign on the face of the financial statements. Use the Sign-Logic in the XBRL Tagger to invert the sign of negative numbers and subtract it from the totals via the weight attribute of the calculation (e.g. from Revenue).

Find more information on reporting of negative numbers, debit/credit attributes and calculations in the IFRS Taxonomy Preparers Guide, Page 46ff.

39

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.

40

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

This type of position is not supported by the converter and has to changed in the Word file. The text from the free floating box should be added as normal text to the footer, so that it just contains to lines. 
41

When using the Word converter, sometimes text from the footer and the page number are not positioned correctly. 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:

42

Why does my iXBRL report have hidden facts?

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 .

43

How can I reduce or avoid hidden facts in my iXBRL reports?

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.
44

How do I update the Taxonomy Cache?

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
45

Why are some calculation inconsistencies WARNINGS and some are ERRORS?

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.

if "Disable" is selected, all calculation messages are disabled

if "Enable" is selected and the threshold is not activated, all calculation messages are displayed as warnings

if "Auto" is selected, the messages are not displayed if EBA or EIOPA reports are created

46

How can I use any other taxonomy then ESEF the XBRL Tagger?

  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.
47

How can I compare my ESEF XHTML report with my audited financial statements in PDF?

  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.
48

My auditor is complaining about an missing DOCTYPE in my pure XHTML file with no tagging

Individual financial statements have not to be tagged but converted to XHTML files, according to the ESEF regulation. However, ESMA does not define exactly how those reports must be validated. This leads to the fact that many audit firms use the free W3C Validator webpage to upload the XHTML file and check it there. If the XHTML file is validated the Doctype must be set to XHTML 1.1, which makes sense to those reports. However, it might display some WARNINGs that can savely being ignored, because its still a valid file and even official ESMA Conformance Suite files don't have BOM or DOCTYPE declarations.



  • No labels