For companies preparing annual financial reports in 2027, ESEF readiness should start well before final tagging and validation.
The 2025 ESEF taxonomy applies to annual financial reports containing financial statements for financial years beginning on or after 1 January 2026. Reporting teams also need to prepare for IFRS 18, which becomes effective for annual reporting periods beginning on or after 1 January 2027.
But ESEF readiness is not simply a year-end tagging exercise.
Financial statements, notes, narrative disclosures, reviews, approvals, changes and structured reporting all form part of the same annual reporting process. If these activities are managed separately, issues can surface late—when there is less time to resolve inconsistencies or rerun validation.
This is why ESEF should be considered within the broader financial disclosure management process, rather than treated only as a technical filing activity.
Here are seven areas reporting teams should review ahead of their next ESEF annual report.
1. Confirm the Reporting Framework, Taxonomy and Reporting Period
Start by confirming the financial period being reported and the ESEF taxonomy and accounting-standard entry point that apply.
The 2025 ESEF taxonomy applies to financial years beginning on or after 1 January 2026. ESMA‘s taxonomy provides entry points reflecting both IAS 1 and IFRS 18, supporting the transition between the two presentation frameworks.
This distinction is particularly important for reports published in 2027.
A calendar-year company publishing its 2026 annual report during 2027 would generally still report under IAS 1 unless it has adopted IFRS 18 early. IFRS 18 becomes mandatory for annual reporting periods beginning on or after 1 January 2027.
Review before reporting:
- Financial year covered by the report
- Applicable ESEF taxonomy
- IAS 1 or IFRS 18 taxonomy entry point
- Changes from the taxonomy used in the previous filing
- Reporting requirements that may affect the annual report structure
Establishing these requirements early gives finance and reporting teams a clearer foundation for the rest of the disclosure process.
2. Prepare the Disclosure Process for IFRS 18
Even where IFRS 18 is not yet mandatory for the annual report being prepared, 2027 readiness should include the transition.
IFRS 18 Presentation and Disclosure in Financial Statements replaces IAS 1 and introduces changes including defined categories within the statement of profit or loss, the required subtotals operating profit and profit before financing and income taxes, requirements relating to management-defined performance measures, and strengthened aggregation and disaggregation principles.
These changes can affect more than ESEF mappings.
Reporting teams may need to reassess:
- Financial statement structures
- Related notes and disclosures
- Management-defined performance measure information
- Reporting templates
- Review and approval processes
- Existing structured-reporting mappings
The IFRS Foundation has also incorporated IFRS 18-related changes into the IFRS Accounting Taxonomy. Read more about the IFRS 18 taxonomy update.
For teams preparing 2026 financial statements, the immediate objective may not be to apply IFRS 18, but to understand which parts of the reporting process will need to change when it becomes applicable.
Preparing early also reduces the risk of treating IFRS 18 as a last-stage taxonomy or tagging adjustment.
3. Review Financial Statements, Notes and Narrative Together
Annual reports are built from connected information.
A change to a financial statement line item may affect a related note. A revised note may require changes elsewhere in the report. Narrative explanations may also need to remain consistent with the underlying financial information.
Yet these components are often prepared and reviewed in different documents or systems.
Before the reporting cycle accelerates, teams should review how information moves across the annual report and whether dependencies can be identified when something changes.
Key questions include:
- Are financial statements, notes and related narrative disclosures aligned?
- Can reviewers see where information originates?
- Are comparative-period disclosures being managed consistently?
- Can teams identify which parts of the report are affected when underlying information changes?
- Are different versions of the same disclosure circulating between contributors?
This becomes particularly important during audit and management review, when multiple parts of the annual report may continue to change simultaneously.
The objective is to maintain consistency throughout report preparation rather than discover discrepancies during final ESEF validation. A connected financial and regulatory reporting process can help keep data, disclosures, review and approval activities within the same governed reporting environment.
4. Reassess ESEF Mapping and Structured Reporting
Previous-year tagging can provide a useful starting point, but it should not simply be rolled forward without review.
ESMA continues to provide detailed guidance for preparing annual financial reports in ESEF through its ESEF Reporting Manual, including guidance relevant to taxonomy concepts, extensions, anchoring, block tagging and technical construction.
Reporting teams should reassess mappings where:
- The underlying disclosure has changed
- The financial statement structure has changed
- A new taxonomy element is available
- An existing extension may no longer be necessary
- The previous anchor no longer accurately represents the accounting meaning
- Comparative-period information has changed
The statement of cash flows also deserves particular attention. Concept selection, completeness, calculation relationships, signs, scaling and consistency across reporting periods should all be reviewed.
Note disclosures should be assessed against the current annual report. Where a note has been rewritten, expanded, reorganized or moved, existing block tagging may need to be reassessed.
Structured reporting should therefore reflect the current disclosure, not simply reproduce the previous year’s tagging approach.
This is also where integrated iXBRL reporting can help connect structured reporting with the underlying disclosure, review and validation process instead of treating tagging as a separate conversion exercise.
5. Strengthen Review, Approval and Change Control
One of the biggest challenges in annual reporting is controlling what happens after a disclosure has already been reviewed or tagged.
Financial reports continue to change during audit, finance review, management review and final approval. A number may be corrected, a table restructured or a note rewritten after earlier stages of the reporting process are complete.
Every material change should trigger an assessment of the related disclosures and structured reporting elements.
Reporting teams should be able to determine:
- What changed
- Who made the change
- Which disclosures may be affected
- Whether the change has been reviewed
- Whether related structured data needs to be updated
- Whether validation needs to be rerun
- Whether the final version has been approved
This is where ESEF readiness becomes a disclosure management issue, rather than only a technical filing issue.
A controlled disclosure process should not stop at recording that something changed. The impact of that change needs to move through the reporting process. Affected work may need to reopen, relevant controls may need to be rerun, supporting evidence should remain linked, approvals may need to be revisited, and structured reporting should update where required.
For reporting teams, the key question is therefore not simply whether the final document has been tagged correctly. It is whether every change can be identified, assessed and governed across the disclosure lifecycle—from source information through preparation, review, approval, validation, structured reporting and final filing.
6. Build Validation Into the Reporting Workflow
Technical validation is essential, but it should not be left until the final stage of filing preparation.
Commission Delegated Regulation (EU) 2026/283 amends the ESEF regulatory technical standards to incorporate the 2025 taxonomy update. ESMA’s current ESEF guidance also addresses technical requirements such as calculation relationships and the use of XBRL Calculations 1.1.
Validation should therefore become part of the reporting workflow as information develops.
Checks may include:
- Calculation relationships
- Presentation structures
- Contexts and units
- Decimals and scaling
- Extension-taxonomy construction
- Reporting-package structure
- XBRL Calculations 1.1
- Consistency between the annual report and structured data
A report can appear correct visually while still containing errors in its machine-readable representation.
Running checks earlier gives reporting teams more time to investigate issues and reduces the concentration of technical corrections immediately before filing.
More importantly, validation should be connected to the reporting process itself. When a disclosure changes, the relevant checks should be reconsidered rather than relying solely on one final validation exercise before submission.
7. Maintain an Audit-Ready Reporting Trail
ESEF reporting does not end with producing a technically valid package.
Teams also need evidence of how the annual report was prepared, reviewed, changed and approved.
A controlled reporting process should maintain visibility into:
- Disclosure ownership
- Review responsibilities
- Version history
- Changes made during the reporting cycle
- Approval status
- Validation results
- Supporting evidence
- Final reporting decisions
This provides greater traceability when questions arise during internal review, external audit or final filing preparation.
More importantly, the reporting history should remain intact as information changes. Evidence, reviews, validation results, approvals and reporting decisions should stay connected to the disclosures they support rather than being reconstructed from spreadsheets, emails and separate document versions at year-end.
For organizations managing multiple reporting obligations, this broader approach to financial disclosure management can help keep the reporting process controlled and traceable from source through disclosure, validation, approval, structured reporting and filing.
What Should ESEF Reporting Teams Prioritize for 2027?
For most reporting teams, 2027 readiness should extend across the entire financial disclosure process.
Teams need to confirm the correct reporting framework, prepare for IFRS 18, maintain consistency across financial statements and narrative disclosures, reassess structured-reporting mappings, strengthen change control, validate throughout preparation and retain a clear reporting trail.
Tagging remains an essential part of ESEF compliance. But it works best when it is connected to the disclosure being prepared rather than handled as a separate exercise at the end of the reporting cycle.
Starting these activities earlier can help reduce issues discovered during final validation and provide greater control over the annual reporting process.
How EcoActive Supports the Reporting Process
EcoActive shows what disclosure management looks like when the platform runs the reporting process end to end—with every change, control, approval, AI action and disclosure governed from source to filing.
When source information changes, the impact can be identified and the reporting process can respond accordingly:
This brings financial statements, notes, narrative disclosures, workflows, controls, validations, approvals and structured reporting into one governed reporting environment rather than managing them as separate activities.
Integrated iXBRL capabilities, powered by Ez-XBRL, connect structured reporting with the underlying disclosure process so tagging and validation do not have to operate as a disconnected year-end activity.
Explore EcoActive Financial Disclosure Management and Integrated iXBRL to learn more.
Get ESEF and IFRS 18 Ready — With Disclosure Management and iXBRL in One Connected Process
Frequently Asked Questions
What should companies review when preparing for ESEF reporting in 2027?
Companies should review the applicable ESEF taxonomy and reporting framework, IFRS 18 readiness, financial statement and disclosure changes, review and approval workflows, change control, structured reporting requirements, validation and reporting traceability.
Is ESEF readiness only about iXBRL tagging?
No. iXBRL tagging is an important part of ESEF compliance, but the broader process includes preparing financial statements and notes, managing narrative disclosures, coordinating reviews and approvals, controlling changes, validating the report and maintaining alignment between the human-readable and machine-readable versions.
How does IFRS 18 affect ESEF reporting preparation?
IFRS 18 can affect financial statement presentation, required subtotals, management-defined performance measure disclosures, aggregation and disaggregation, and related notes. These changes may also require reporting teams to reassess existing ESEF mappings and structured-reporting processes.
Why is change management important during annual report preparation?
Annual reports frequently change during finance review, audit and management approval. When a number, table, note or narrative disclosure changes, teams need to understand which related disclosures and structured reporting elements may also require updates.
Why should financial statements, notes and narrative disclosures be managed together?
These parts of the annual report are interconnected. Managing them within a coordinated disclosure process helps teams identify dependencies, maintain consistency and reduce the risk of conflicting information appearing in different parts of the final report.
When should ESEF validation begin?
Validation should begin during report preparation rather than only at the end of the filing process. Earlier validation helps teams identify calculation, consistency, taxonomy and technical issues while there is still time to investigate and resolve them.
What does an audit-ready ESEF reporting process require?
An audit-ready process should provide clear ownership, review and approval history, change tracking, supporting evidence, validation results and traceability from the underlying disclosure through to the final structured report.
