Commencing work before the AFS is finalised

Usually that there is very little time available to perform the conversion of the AFSs to ESEF format.  Any delay in the finalisation of the AFSs can put tremendous pressure on the user responsible for converting the AFSs to ESEF format.

Whilst the actual conversion can only take place once the document is finalised, there is a lot of work that can be done in advance to reduce the amount of time it will take to convert the finalised document.  

This preparation work can be done on either the previous year's AFS, or an early draft of the current year's AFS.  

The work that can be done in advance is:

1. Creating the extended taxonomy
2. Completing the Enhanced Auto-Tag table to map core and extended tags to the labels expected to be used in the final reports.

Creating the extended taxonomy

This process is explained in detail in the next articles.  If Report Authority was used in the previous period's AFS, you can re-use the extended taxonomy.  If this is the first time Report Authority is to be used, you can prepare the extended taxonomy in advance using last year's AFSs or an early draft of the current periods' AFS.  For this purpose, you need only the primary statements.

The following tasks can be prepared in advance to be imported into the finalised AFS document:

• The list of core ESEF tags to be included in the extension taxonomy.
• Extended tags and their anchoring.
• The arrangement of the extended taxonomy's presentation hierarchy.
• The calculation hierarchy.

Enhanced Auto-Tag

The Auto-Tag process can be enhanced by mapping the report label to the appropriate core or extended tag.  This process is described in a subsequent article, but all enhancements of the auto-tag can be imported into the document for the finalised AFSs.