StartArticle bankRecording: Learnings from the recent ESEF Season and updated Best Practices

Recording: Learnings from the recent ESEF Season and updated Best Practices

Join us when we dive into ESEF and conducting a comprehensive review and learnings from the recent reporting season.

ESEFRecording

Navigating ESEF: Insights, updated Best Practices and learnings from the past season

During our last webinar we explored the updated Best Practices with key highlights and discovered workflow strategies to enhance your reporting process. The following is a summary of the questions asked and answered during the seminar:

How to see last year's tagging?

You can open another tagging window (E.g last years tagging) and have it side by side as your current one.

Is there a list available with compatible fonts, or can this be found out only by testing the document via the test functionality?

No, we want you to have the full flexibility when designing your report. Therefore we won’t recommend any specific fonts that you should use. When deciding fonts, you always have the possibility to test the document in CtrlPrint before using it. Read more about it here.

Are there any plans to add functionality that enables report comparison (two different versions of the tagged document)? Such functionality is available currently in Amana XBRL tagger.

This has been added to CtrlPrint tagger. Please see our latest release notes for pictures and instructions.

When creating the ESEF report the disclosure chapter was not translated to Swedish (our reporting language) and you helped us adjust this manually, after the ESEF report was downloaded. Is this still an issue for 2024?

You can do this in your ESEF project settings. Please see our latest release notes for pictures and instructions.

So when does the ESRS taxonomy need to be approved so that it would be compulsory to tag 2024 reporting in 2025? Or we already know that this will not be the case?

We will have to wait for the regulators.

Is there a update in the possibility to see if we are missing on properties of "escape attribute value to True" currently we get to know about it only from Auditors validation report, as we dont see it in Ctrl print?

In the validation results, and in the tab “presentation linkbase” you can see a full list of all textblock tag as well as the XBRL Escape which can be found in column S.

You can also change it for all tags inside the tagger under Toolbox. Instructions can be found here by following step 8.

Let's get in touch!