These are settings for every chapter in the project. Make sure the default settings (currency, scale, date format, decimals, digit separators) are correct as they will affect any new tags you create. Please also make sure that the Reporting Entity Identifier (LEI) is set to avoid an error occurring when saving to server.
For Package settings, please check the requirements of the National Competent Authority (NCA)/ Officially Appointed Mechanism (OAM) receiving the report. We also have a tutorial video with more information.
|Report Entity Ticker Symbol/Name||Short company name, which will be part of the reporting entity URL. Please write the name without spaces or special characters in lower case letters. This name will be used as file name, when extensions are created.|
|Reporting Entity Identifier
(e.g. LEI)/LEI Search
|The ID of the reporting entity regarding the Context Identifier Schema. If you click the "LEI Search" link, it will forward you to gleif.org where you can search for the LEI. Copy the LEI from that page to the settings.|
|Reporting Entity URL
|Is generated automatically (includes the value from "Reporting Entity Ticket Symbol/Name" added above). Please write the URL without spaces or special characters in lower case letters.|
|Primary Taxonomy||Some jurisdictions have a requirement to use a local taxonomy in addition to the ESEF taxonomy (e.g. Denmark will be using both ESEF and DK-GAAP). Alternatively, users may want to use different unrelated taxonomies to tag both Annual Report-data as well as Sustainability Reporting-data in the same report. Users can now choose one Primary Taxonomy and one or more Additional Taxonomies.|
|Additional Taxonomies||Any additional taxonomies to be used in the report (see Primary Taxonomy, above).|
|Reporting Period||The start and end date of the reporting period.|
|Auto SignLogic||If ticked, the Tagger will automatically apply a SignLogic setting for each tagged cell - please be aware each cell still needs to be checked to confirm the Auto SignLogic is correct. Otherwise, each cell's SignLogic will be set to None and will need to be manually changed in the Tagging Properties tab.|
|Elimination of Hidden Facts for PDF||Hidden facts are tags that are included in the file but are not attached to the related human-readable item. If this option is ticked, this will remove the Hidden Facts section, if it exists, from the final XBRL report - this is correct for most reports. If unticked, the Hidden Facts section may be created in the XBRL report - this may be required in some jurisdictions (e.g. DKGAAP). Click here for more information about how to set up your InDesign file to minimise Hidden Fact issues.|
|Hide Note Column||Hides the Notes column in the Table Tagging tab after the table has been defined.|
|Report Language||The language the report is published in. Number format and date format will be affected by this.|
|Report Default Monetary Currency (ISO)||The default currency. All new tags created in the document will be set to this currency. You can always set the scale for individual cells in the tagger should they differ.|
|Report Default Monetary Number Scale||The default scale for numbers. All new tags created will be set to this scale. The scale indicates the number of zeroes to be added to a value to represent its real number. There are four options available: none, thousand, million and billion.|
Number of Decimal Places Used
|Defines the accuracy of the tagged element if it is a monetary value. A value of 4 states that the tagged value is accurate to 3 places after the decimal separator (e.g. 0.246). The default setting of 0 is correct for most users but some reports may use 1 or 2 decimal place throughout. All new tags created will be set to this format.|
|Sample Date Format Representation||Shows an example of how dates are represented.|
|Default Percentage Decimals||Defines the accuracy of the tagged element if it is a percentage value. A value of 2 states that the tagged value is accurate to 2 places after the decimal separator (e.g. 24.67%). All new tags created will be set to this format.|
|Default Date format||If the tagged value represents a date, the format specifies the exact format of that date. All new tags created will be set to this format.|
|Default Monetary Format||If the tagged value represents a monetary value, the format specifies the exact format of that value. All new tags created will be set to this format.|
|Label Handling Option||
Each line item in your table has an automatically created human-readable label taken from its row text. This may be different from the human-readable label of the corresponding tag in the taxonomy. For example, your line item may be Revenues, but the taxonomy label for this taxonomy element is Revenue.
XBRL label roles are used to assign a specific meaning to a label. The default label role is "Standard". The below options tell the Tagger what role your custom labels should have in the linkbase files associated with your final report.
Standard Role with Priority: Use report-specific labels and create those as labels with the Standard label role and a higher priority than the base taxonomy labels (i.e. Revenues (the name of the line item in the table) will appear above Revenue (the pre-set taxonomy label) and both will have the Standard role).
Verbose role: Use report-specific labels and create those as labels with the Verbose label role (i.e. Revenues (the name of the line item in the table) will appear above Revenue (the pre-set taxonomy label) but Revenues will have the Verbose role instead of the Standard role.
Extension labels only: Use only base taxonomy labels (except for extensions) (i.e. Revenues will not be used and only the pre-set taxonomy label, Revenue, will be listed with the Standard role. Extensions work as usual with a custom label created from your line item text).
|Use Taxonomy Table Order||Normally, the table order in the extension taxonomy should resemble the order of tables in the actual report. In some jurisdictions, or auditors' opinions, it has to exactly resemble the order in the original taxonomy. Set to True to reflect this.|
|Use Hidden Elements||The default setting of False is correct for most users but is necessary for some jurisdictions (e.g. DKGAAP). If set to True, it shows the hidden elements section.|
|PDF Unicode CMaps Handling||The default setting of Ignore is correct for most users. Set to Force if you have issues with certain characters in the Preview tab looking different to how you expect.|
|Use AutoHint on Focus Without Hint||The default setting of Default is correct for most users. Set to Use AutoHint if you have issues with vertical alignment in columns.|
|Converter Fallback Mode||The default setting of False is correct for most users. Set to True if the Preview tab looks correct but the figures in the Table Tagging tab are not being interpreted correctly.|
|Exclude Hyperlinks||By default, reports will include support for hyperlinks and the PDF Preset field (see row below) for your ESEF Report will show if it supports including hyperlinks. Set to True to exclude all hyperlinks from your report. Click here for more information about creating your own PDF Preset.|
|PDF Preset||The PDF preset used for the creation of the ESEF report. ESEF report PDFs are created using the default CtrlPrint 72dpi PDF preset. You can change this if an admin has added a custom PDF preset on the project page.|
|Taxonomy Package Name||Your company name followed by XBRL Taxonomy <YEAR>. For example, CtrlPrint AB XBRL Taxonomy 2020. Please be aware that this advice comes from one of the Conformance Suite tests and not the regulatory documents. You should discuss this further with your auditors as part of your due diligence.|
|Taxonomy Package Description||A brief description of the taxonomy package. In the example from ESMA, they have added "Taxonomy for ESEF Reporting".|
|Taxonomy Package Version||If this is the version you are intending to publish you can write "Final".|
|Publisher||Your company name.|
|Publisher URL||Your company website.|
|Publisher Country||Your country.|
|Publication Date||Report publication date.|