ESEF validation errors can delay your filing and require costly corrections. This guide covers the most common validation errors encountered by issuers, explains their root causes, and provides clear solutions. Understanding these errors before you file can save significant time and effort.
Key Takeaways
- Most ESEF errors stem from extension taxonomy issues
- Anchoring problems are the #1 cause of validation failures
- Report package structure errors are easy to prevent
- Pre-validation catches 90% of issues before filing
- Keep detailed audit trails for error resolution
Extension Taxonomy Errors
Extension taxonomy errors occur when custom elements don't meet ESEF requirements:
• Missing or invalid element declarations
• Incorrect namespace definitions
• Invalid label linkbase references
• Duplicate element definitions
Solution: Always derive extension elements from the ESEF base taxonomy and validate your extension XSD against the XBRL 2.1 specification.
Anchoring & Wider-Narrower
Anchoring errors (ESEF rule 2.5.1) are the most common validation failures:
• Extension element not anchored to any base element
• Anchoring to deprecated element
• Multiple conflicting anchors
• Invalid wider-narrower relationship
Every extension concept must anchor to at least one base taxonomy element using the 'wider-narrower' arc role. The anchor should represent the closest semantic match in the base taxonomy.
Report Package Errors
Report package structure errors cause immediate rejection. Ensure your ZIP contains: META-INF folder with correct manifest, reports folder with the XHTML document, and any embedded taxonomy files in the correct location. The file encoding must be UTF-8 without BOM.
Calculation Inconsistencies
Calculation inconsistencies trigger warnings that auditors will question:
• Rounding differences exceeding tolerance
• Missing calculation relationships
• Incorrect weight values (+1/-1)
• Cross-context calculation errors
While these are typically warnings, not blocking errors, you should document any intentional inconsistencies with explanations.
Prevention Best Practices
Prevent errors before they occur: 1) Use a validation tool throughout the tagging process, not just at the end. 2) Maintain a mapping document linking your data to taxonomy elements. 3) Test with the official ESEF conformance suite. 4) Keep your taxonomy packages up to date.
Checklist
- Validate extension taxonomy XSD syntax
- Check all extension elements have valid anchors
- Verify report package ZIP structure
- Test calculation linkbase consistency
- Review all warnings, not just errors
- Document any intentional inconsistencies
- Run final pre-submission validation