From experience of the previous reporting seasons, one of the biggest indicators of confusion and stress within an ESEF project is not taking the time to understand and plan the general process. The steps outlined below are our current understanding of the most effective procedure to help minimise problems before they become apparent.
- Start by activating the ESEF Reporting functionality for the project on the server as an admin.
- Manage the ESEF settings for the project. Some of the biggest issues that have arisen are from teams that have not paid attention to their settings. Settings are applied to new tags that are implemented in the report. Please stress that managing the project settings should be done before any tagging takes place.
- Upload the chapters from InDesign and make sure that a new chapter version is created so that the chapter can be opened in the Tagger.
- Tagging can be carried out on the project. As this is completed a mapping file that has the tagging saved is created. This file can then be used to load tags on a chapter quickly in the event of the layout changing enough to “lose” the table. If the line items are in the same order, then it should be a fairly straightforward process even if layout has changed, such as going to a landscape visualisation. If line item order has changed, tags can be imported, and then moved around using the cut and paste functionality.
- Tagging should be validated to ensure that the report fulfils the required criteria to be submitted to the relevant authority. The Tagger does carry out ESEF Validation, and we can assist with resolving some of these. There is other validation that may occur by the portal where submissions are conducted. Validation messages can be either Information, Warning and Error messages. Information and warnings will not affect the validity of the report on submission. Errors need to be corrected before submission or the report will not be accepted.
- The report can now be sent to ESEF advisors by exporting the report from the server. The file is downloaded as a zip file from the CtrlPrint server. The file that needs to be sent for validation is the zip file that resides within the file that is downloaded. Depending on the jurisdiction that the report is being submitted in, different naming conventions can apply. This should be checked and known by the reporting company and should not rely on CtrlPrint for this.
- Once the advisors sign off on the report package, it can be submitted to whatever authority is relevant.
- The XHTML Preview file with the inline viewer can now be made available for download on the companies website if they wish. This is the best way for someone to view the report if they wish to.