Introduction
Use this article when you are preparing an ESEF reporting package in Tangelo. It explains the main steps from setting up general ESEF data to tagging, validating, and checking the final xHTML output.
Summary
After following this process, your ESEF report is prepared, tagged, validated, and ready to be exported as a filing package.
Overview
Prepare the source data
Before starting the tagging process, ensure that all financial data has been finalized and imported into the report.
Review the source tables and verify that:
- Financial data is complete and up to date.
- Table structures are correct.
- Comparative figures are available where required.
- Data sources have been synchronized successfully.
Configure the document for tagging
Start by completing the general XBRL settings in the root section of the document.
Review the XBRL settings and ensure that:
- The XBRL General Data is added
- The applicable SBR taxonomy is selected.
- The correct reporting period is selected.
- Organization-specific information has been completed.
- The monetary unit and precision is entered.
Read more about these preparations in these articles:
- Add XBRL general data
- Selecting the correct taxonomy
- Add or edit reporting periods
- Modify the monetary precision
- Modify the monetary unit (currency)
Set XBRL containers
Set the correct ESEF container for the first line item of each financial statement section. Containers define where facts belong in the ESEF structure and are used to generate the correct presentation and calculation linkbases.
Examples of XBRL containers include:
- Statement of Profit and Loss
- Statement of Financial Position
- Statement of Comprehensive Income
- Statement of Cash Flows
- Statement of Changes in Equity
Use the predefined containers available in Tangelo. These containers cannot be customized.
More about setting containers in this article: Add or edit XBRL containers
Assign the identifiers for the periods
For each table, it must be specified which column represents the current reporting period and which represents the comparative (previous) reporting period.
For each of the primary statement tables, indicate which header column contains the current period and which header column contains the previous period.
Read more about this configuration: Add or edit reporting periods
Tag the primary financial statements
Tag all relevant numerical facts in the consolidated financial statements.
This includes facts in:
- Statement of Profit and Loss
- Statement of Financial Position
- Statement of Comprehensive Income
- Statement of Cash Flows
- Statement of Changes in Equity
For each fact, check the taxonomy concept, context, precision, and sign. Pay extra attention to the Statement of Changes in Equity, as this statement often requires dimensions and members to be applied correctly.
Read more about tagging financial facts in these article: Tag the primary statements and Tag the statement of changes in equity
Add required inline tags
Add the required inline tags to the relevant text in the report. Inline tags are used to tag specific textual disclosures, such as the name of the reporting entity, domicile, legal form, activities, or explanations related to IFRS reporting.
Only apply inline tags to text. Do not apply them to tables, images, or other non-text content.
Review the required inline tags with your auditor before finalizing the report, as not every tag applies to every situation.
More about adding inline tags in this article: Tag organization information using inline tags
Tag values in the notes
In addition to the primary financial statements, numerical disclosures in the notes may also require tagging. This is commonly referred to as value tagging and is used to make individual facts within the notes machine-readable. Examples include: Share capital disclosures, Earnings per share etc.
When tagging values in the notes:
- Select the appropriate taxonomy concept.
- Verify that the concept accurately represents the disclosed information.
- Ensure the correct context is applied.
- Review the sign and monetary precision where applicable.
The exact scope of value tagging depends on the applicable ESEF requirements and your organization's reporting approach. Review the tagging scope with your auditor before finalizing the filing.
More about adding value tags in this article: Tag table footnotes and note values
Add block tags to the notes
Apply block tags to the notes where required. Block tags should be applied at section or paragraph level.
Use reverse tagging when more detailed tagging is needed within a larger tagged text block.
Read more about block tagging in this article: Tag notes using block tags
Review the validation report
After the export, review the validation report. Use the reported errors and warnings to identify missing data, incorrect tags, taxonomy issues, or other filing problems.
Resolve validation issues before preparing the final filing package.
You can read more about validating your filing package in this article: Validate your XBRL package
Run the XBRL export
Run the XBRL export when the report has been prepared and tagged.
The export generates the draft ESEF package, including:
- Inline XBRL file
- Extension taxonomy
- Label linkbases
- Reference linkbases
Check the xHTML output
Review the generated xHTML output before finalizing the report.
Check that:
- All required sections are included.
- The report is complete.
- Formatting is correct.
- Internal links work as expected.
- External hyperlinks are not included.
Expected Result
The ESEF report is tagged, validated, and exported as a reporting package that can be reviewed internally, shared with auditors, and prepared for final submission.
Remarks
- Start early, especially when preparing an ESEF report for the first time.
- Work in phases instead of tagging the full report in one session.
- Review inline tags, value tags, block tags, signs, dimensions, and validation results with your auditor.
- Contact your Tangelo consultant if you need support with your report setup or filing process.