Steps to an ESEF reporting package Steps to an ESEF reporting package

Steps to an ESEF reporting package

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

Enter XBRL general data

Start by completing the general XBRL settings in the root section of the document.

Add or verify the following information:

  • Reporting period
  • LEI code
  • Currency
  • Document language

The document language is important because it affects the report setup and should be checked before continuing with tagging.

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.

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.

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.

Tag financial facts

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.

Set XBRL properties

Review the XBRL properties for tagged facts. Make sure the monetary precision and sign usage are correct.

These settings can be reviewed and adjusted in the table row or cell properties panel.

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.

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.

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.

Was this article helpful?

0 out of 0 found this helpful