ESMA ESEF Taxonomy 2025: What Changes for 2026 IFRS Filings

ByOfficer

Last updated: April 2026

If your team files IFRS consolidated statements in ESEF format, the taxonomy you tag against just changed. On 21 April 2026, ESMA published the 2025 ESEF XBRL taxonomy files and an updated ESEF Conformance Suite. These are the files issuers and software vendors need for 2026 reporting periods. Get the wrong taxonomy loaded into your tagging tool and your entire Inline XBRL output is non-compliant before a single number is tagged.

The headline change: the 2025 ESEF taxonomy now includes IFRS 18 (Presentation and Disclosure in Financial Statements), which takes mandatory effect from 1 January 2027 but permits early adoption. That means the taxonomy ships with two entry points, one for IAS 1 and one for IFRS 18, and your choice of entry point determines the structure of your tagged report.

I have been through several ESEF taxonomy transitions on the production side, and the pattern is always the same. The taxonomy files appear months before filing season, teams assume “we will deal with it later,” and then Q4 arrives with a scramble to update mappings. This time there is an extra wrinkle: IFRS 18 readiness.

Related reading: CSRD Sustainability Reporting

What ESMA Actually Published

ESMA released two packages on 21 April 2026:

First, the 2025 ESEF XBRL taxonomy files. These are the machine-readable taxonomy schemas and linkbases that define which XBRL elements are available for tagging IFRS consolidated financial statements in ESEF format. The “2025” label refers to the taxonomy vintage, not the filing year. You use the 2025 taxonomy for your 2026 annual filings.

The legal underpinning was already in place. Commission Delegated Regulation (EU) 2026/283 of 12 December 2025, published in the Official Journal on 18 March 2026, amended the ESEF RTS (Commission Delegated Regulation (EU) 2019/815) to incorporate the 2025 IFRS taxonomy. The 21 April 2026 ESMA publication provides the operational files supporting that amended legal framework, not a new legal change.

Second, the updated ESEF Conformance Suite. This is the validation test package that software vendors use to verify their tools produce compliant Inline XBRL output. If your vendor has not run their tool against the 2025 Conformance Suite, their output is untested against the current rules.

One important clarification: ESMA explicitly stated it does not plan to amend the ESEF Regulatory Technical Standards (RTS) or the taxonomy again in 2026. The IFRS Foundation also decided not to issue a separate 2026 IFRS Accounting Taxonomy. So the 2025 files are it. There is no further update coming this cycle.

The IFRS 18 Dual Entry Point

This is where reporting teams need to pay close attention. The 2025 ESEF taxonomy includes two entry points:

Entry point 1: IAS 1 (Presentation of Financial Statements). This is the current standard most issuers use. If you are not early-adopting IFRS 18, you continue with this entry point. Your existing mappings carry forward, subject to any element updates in the 2025 vintage.

Entry point 2: IFRS 18 (Presentation and Disclosure in Financial Statements). IFRS 18 replaces IAS 1 and restructures how entities present their income statement and cash flow statement. If your entity decides to early-adopt IFRS 18 for 2026 financial statements (permitted under the standard), you must use this entry point.

I have already seen confusion on this in practice. The entry point choice is not cosmetic. IFRS 18 introduces new required line items in the statement of profit or loss, including operating profit and categories of income and expenses. The XBRL elements for these line items exist only in the IFRS 18 entry point. Tag against the wrong entry point and your report will either fail validation or contain structurally incorrect markup.

For most issuers filing 2026 annual reports, the IAS 1 entry point remains the default. IFRS 18 mandatory application is 1 January 2027. But if your group is considering early adoption, the ESEF decision must be coordinated with the accounting policy decision. These are not separate workstreams.

One additional point on entry points: the 2025 taxonomy also includes a separate entry point for IFRS 19 (Subsidiaries Without Public Accountability). IFRS 19 is intended for non-listed subsidiaries that elect to apply reduced disclosure requirements, and is not used in standard ESEF filings by listed issuers. Most reporting teams will not engage with the IFRS 19 entry point, but it exists in the 2025 taxonomy package alongside IAS 1 and IFRS 18.

What Issuers Need to Do

The action list for issuer reporting teams is straightforward but time-sensitive:

Confirm your entry point. Speak with your group accounting team about IFRS 18 early adoption plans. If no early adoption, you stay on IAS 1. Document this decision. Your ESEF service provider or in-house tagging team needs a clear answer before they start mapping.

Update your taxonomy mappings. Even if you stay on IAS 1, the 2025 taxonomy vintage may include updated or deprecated elements compared to the 2024 files you used last year. Every taxonomy transition introduces minor changes to element labels, hierarchies, or calculation linkbases. Review the diff. I have seen teams miss deprecations that caused silent validation issues in prior years.

Test early. Do not wait for your external auditor’s ESEF review in December. Load the 2025 taxonomy into your tagging environment now and run a test conversion on last year’s report. This surfaces mapping breaks early, when there is time to fix them without deadline pressure.

Contact your software vendor. Ask whether they have integrated the 2025 ESEF Conformance Suite. If they have not, escalate. An ESEF tool that has not been tested against the current conformance suite is a risk to your filing.

What Software Vendors Need to Change for ESEF 2026

Vendors have a different but equally pressing checklist:

Integrate the 2025 taxonomy files. Replace the 2024 taxonomy schemas and linkbases in your product with the 2025 versions. Ensure both entry points (IAS 1 and IFRS 18) are available to users. Some vendors hardcode a single entry point. That approach breaks this year.

Update to the XBRL Calculations 1.1 specification. The 2025 ESEF taxonomy moves from Calculations 1.0 to Calculations 1.1. This change materially reduces validation inconsistencies associated with rounding for tagged subtotals and aggregations. Tagging tools that still implement Calculations 1.0 will produce filings that may pass syntactic validation but flag inconsistencies during NCA review. Test your output against the Conformance Suite test cases that specifically exercise Calculations 1.1 rules.

Run the updated Conformance Suite. ESMA provides this specifically so vendors can self-test. Every test case in the suite must pass. Publish your conformance results to clients. In my experience, issuers increasingly ask for this documentation during vendor selection and annual reviews.

Support the dual entry point workflow. Your UI needs to let issuers select their entry point at report creation time and prevent mixing elements across entry points. This is a new requirement compared to prior years where there was only one entry point.

Communicate the timeline. Your issuer clients need to know when the 2025 taxonomy will be available in your product. “Q3 2026” is too vague. A common mistake I see: vendors announce support in September, but issuers start their ESEF tagging in July. Close that gap.

Why ESMA Is Not Updating the RTS in 2026

ESMA’s decision not to amend the ESEF RTS this year is deliberate. The IFRS Foundation chose not to publish a 2026 IFRS Accounting Taxonomy, so there is no new base taxonomy to incorporate. ESMA described this as providing “greater regulatory stability and more time for implementation.”

In practical terms, this means the legal framework (the RTS) stays the same. Only the taxonomy files change vintage. That is good news for compliance teams because it means no new legal obligations, no new article references to track, and no consultation process to monitor. The work is purely technical: swap the taxonomy files, verify your mappings, test your output.

It also means ESMA’s attention is shifting toward sustainability reporting under CSRD and the ESEF RTS amendments for ESRS taxonomy integration. If you work on CSRD sustainability reporting, expect that to be the next major ESEF change cycle, likely in 2027.

Common Mistakes Teams Make During Taxonomy Transitions

Having been through these cycles, three errors come up repeatedly.

First, using the old taxonomy for new filings. This sounds obvious, but it happens. An issuer’s ESEF tool is configured with the 2024 taxonomy, no one updates it, and the annual report is tagged against outdated files. The consequences vary by NCA, but typically include a request for remediation and a deficiency finding that appears in the next annual transparency review. ESMA publishes findings from these reviews each year, and patterns of taxonomy non-compliance are flagged at sector level.

Second, ignoring deprecated elements. When ESMA moves to a new taxonomy vintage, certain XBRL elements may be deprecated or replaced. If your prior-year mapping references a deprecated element, your tagging tool may silently substitute a generic element or throw an error, depending on the vendor. Either way, the output is wrong. Always review the taxonomy release notes for deprecations.

Third, treating the IFRS 18 entry point as optional reading. Even if you are not early-adopting IFRS 18, your team should familiarize themselves with the new entry point now. Mandatory application is 1 January 2027, which means your 2027 annual report (filed in 2028) will require it. Starting the mapping analysis now, while 2026 filings are in progress, gives you a 12-month head start.

Frequently Asked Questions

Which taxonomy do I use for my 2026 IFRS annual report?

The 2025 ESEF XBRL taxonomy published by ESMA on 21 April 2026. Despite the naming, the “2025” taxonomy is the current vintage intended for 2026 reporting periods.

Do I have to use the IFRS 18 entry point for 2026 filings?

No. IFRS 18 is mandatory from 1 January 2027, with early adoption permitted. If your entity has not elected early adoption, you continue using the IAS 1 entry point in the 2025 taxonomy.

Will ESMA release another taxonomy update before year-end 2026?

ESMA has stated it does not plan to amend the ESEF RTS or taxonomy in 2026. The 2025 files are the final version for this reporting cycle.

Where do I download the 2025 ESEF taxonomy and conformance suite?

Both packages are available on ESMA’s website under the ESEF news section. Direct access via the announcement page dated 21 April 2026. Stakeholders can also contact esef@esma.europa.eu for questions.

What if my software vendor has not updated to the 2025 taxonomy yet?

Escalate. Ask for a specific date when the 2025 taxonomy and conformance suite will be integrated. If your vendor cannot provide a timeline, consider whether you have a contingency plan for your filing deadline.

Does this affect sustainability reporting under CSRD?

Not directly. The 2025 ESEF taxonomy update covers IFRS financial statements. ESRS sustainability taxonomy integration into ESEF is a separate workstream. ESMA consulted on ESEF RTS amendments for sustainability reporting in December 2024, and those changes are expected in a future cycle.

My entity is listed in Luxembourg. Does the CSSF have additional requirements?

The ESEF taxonomy is EU-wide. The CSSF, as the national competent authority, enforces ESEF compliance for Luxembourg-listed issuers but does not impose additional taxonomy requirements beyond the ESMA RTS. Check the CSSF reporting calendar for relevant filing deadlines.

Related Articles

Key Takeaways

  • ESMA published the 2025 ESEF XBRL taxonomy and conformance suite on 21 April 2026 for use in 2026 IFRS consolidated financial statement filings.
  • The 2025 taxonomy includes two entry points: IAS 1 (current standard) and IFRS 18 (early adoption permitted, mandatory from 1 January 2027).
  • ESMA will not amend the ESEF RTS or release another taxonomy update in 2026. The 2025 files are final for this cycle.
  • Issuers must confirm their entry point choice, update taxonomy mappings, and test conversions well before filing season.
  • Software vendors must integrate both entry points, run the updated conformance suite, and communicate availability timelines to clients.
  • Even issuers staying on IAS 1 should review the IFRS 18 entry point now, as mandatory application is only one reporting cycle away.
  • Common errors include using outdated taxonomy files, ignoring deprecated XBRL elements, and delaying vendor coordination until Q4.

Sources and References

Disclaimer: The information on RegReportingDesk.com is for educational and informational purposes only. It does not constitute legal, regulatory, tax, or compliance advice. Always consult your compliance officer, legal counsel, or the relevant supervisory authority for guidance specific to your institution.

Similar Posts