The Challenge
When the European Single Electronic Format (ESEF) regulation took effect for fiscal years starting January 1, 2020, around 5,300 companies faced a seemingly simple task: tag your IFRS consolidated financial statements using inline eXtensible Business Reporting Language (iXBRL). The regulation seemed straightforward: convert financial statements to XHTML format, apply standardized tags from the ESEF taxonomy, and ensure machine readability.
However, the complexity lay in execution. Unlike traditional PDF-based reports, ESEF required embedding structured data directly into financial statements. Each figure in key financial documents needed a standardized tag for IT systems to process semi-automatically. By January 1, 2022, the scope expanded to include 234 additional items from the notes to consolidated financial statements.
This wasn't a one-time project. The ESEF taxonomy, based on the IFRS Foundation's taxonomy, reflects standards approved by the European Commission. Frequent changes and additions are expected, requiring sustainable processes to maintain current taxonomy versions and incorporate updates across accounting systems.
The Environment and Constraints
The decision-making environment varied by company size and structure. Smaller issuers, with limited resources, questioned whether the benefits justified the implementation burden.
Larger issuers faced different challenges. Many were part of groups where the parent company had already decided on ESEF implementation. Subsidiaries needed to align with group-level infrastructure, especially when parent companies created taxonomy extensions.
All issuers faced regulatory ambiguity. The German implementation positioned ESEF requirements at the preparation stage of financial statements. This meant auditors and supervisory boards needed to assess tagging accuracy as part of the audit. The Institut der Wirtschaftsprüfer criticized this approach, arguing it disrupted established processes for financial statement preparation and audit.
The German Accounting Standards Committee raised concerns about automated checking mechanisms for errors. Without systematic validation, the benefits of XHTML files could be undermined by tagging errors that escaped manual review.
The Approach Taken
Companies split into two camps based on their build-versus-buy decision.
In-house implementation required significant investment in tagging software and system adaptations. Companies expanded their teams to manage the workload, built processes to monitor taxonomy updates, and aimed for semi-automated tagging to reduce manual effort.
This approach offered direct control over the tagging process and integration with digital transformation initiatives but demanded sustained internal capability. Accounting teams needed to understand IFRS standards and iXBRL tagging, while IT teams maintained software and managed system interdependencies.
External service providers offered a different tradeoff. They required lower initial investment and minimal internal burden, handling the conversion to ESEF format for each reporting period for a fee.
This approach kept internal effort low but reduced control over the process. Companies still needed to validate that providers correctly interpreted their financial statements and applied tags accurately, ensuring the final report met regulatory requirements.
Results and Metrics
While specific cost figures aren't available, a pattern emerged: in-house implementation had higher upfront costs but anticipated lower running costs once processes matured. External providers had lower upfront costs but ongoing fees.
Both approaches required attention to taxonomy updates. Companies using service providers needed internal expertise to communicate changes and validate accuracy. In-house software users needed to monitor vendor releases and incorporate updates.
The Institut der Wirtschaftsprüfer highlighted an unintended consequence: positioning ESEF requirements at the preparation stage expanded the audit scope, requiring auditors to assess both financial statement accuracy and iXBRL tag accuracy.
What They Would Do Differently
Regulatory commentary suggests several lessons:
Group coordination is crucial. Companies that made independent decisions without considering group alignment faced incompatibilities. Implementation decisions should occur at the group level.
Automated validation is essential. Companies relying solely on manual review discovered errors after publication. Automated checking mechanisms should be integrated from the start.
The taxonomy is dynamic. Companies treating ESEF as a one-time project underestimated ongoing maintenance. Whether using internal software or external providers, processes for monitoring and updating taxonomy are necessary.
Early auditor involvement is key. Positioning tagging accuracy as part of the audit meant auditors needed to understand the technical implementation. Early engagement could prevent rework.
Takeaways for Your Team
If you're implementing structured data reporting requirements:
Decide at the group level. Analyze total cost of ownership across the consolidation scope. High initial investment in internal capability may be justified for multiple entities. External providers may be more cost-effective for standalone issuers.
Design for ongoing taxonomy maintenance. Your processes need to accommodate frequent updates. Build review cycles that catch changes before deadlines. If using external providers, define how they'll notify you of updates.
Implement automated validation early. Manual review doesn't scale. Invest in validation tools that check accuracy and compliance. Run validation as part of your financial close process.
Engage auditors during implementation. If your framework includes structured data accuracy in audits, auditors need to understand your tagging process. Document control procedures and give auditors visibility into how you handle updates.
Plan for human capital needs. Whether you build or buy, someone on your team needs to understand both accounting and technical mechanics. Budget for training and headcount accordingly.
The ESEF experience shows that structured data mandates are accounting process transformations requiring strategic decisions about capability development, vendor relationships, and group coordination. Make those decisions deliberately.
