Learning Objectives

By the end of this section, readers will be able to:

  • Understand the evolving nature of taxonomies and the reporting ecosystem
  • Recognise the importance of effective update management to maintain a stable, compliant, and efficient reporting ecosystem
  • Identify structured versioning and timing strategies based on different circumstances that drive changes or updates
  • Understand the role of stakeholder coordination in managing taxonomy revisions and ensuring smooth adoption of updates
  • Explore communication and integration strategies to ensure reporting entities and system users are prepared for taxonomy modifications

Introduction

Taxonomies are not static — they grow, adapt, and evolve like the regulatory frameworks they support. As accounting standards, legal requirements, and business environments change, taxonomies must be updated to reflect these developments. Effective management of these updates is not just a technical concern but essential to maintaining a reliable, transparent, and functional reporting system.

When a taxonomy is updated without a clear strategy, the result can be confusion for preparers, software readiness delays, data mismatches, and even non-compliance. Conversely, a well-managed update cycle provides clarity and predictability. It ensures that stakeholders can plan ahead, adjust their systems, and remain aligned.

Managing taxonomy updates involves several elements: determining the reasons and timing for changes, applying clear versioning strategies, coordinating with all stakeholders, and effectively communicating the updates. Each step helps minimise disruption while enabling the reporting ecosystem to grow and improve over time.

This section explores the key aspects of managing updates and revisions, from identifying the need for change to implementing those changes within real-world systems. Special attention is given to ensuring that no stakeholder is left behind, allowing sufficient time to explore, understand, prepare for, and undertake the necessary activities.

The Need for Taxonomy Updates

Taxonomies are designed to reflect the structure and rules of a given reporting framework. However, those frameworks are subject to continuous evolution. New laws may be enacted, standards refined, or new reporting needs identified. As a result, taxonomies must evolve alongside them.

There are several drivers for taxonomy updates. Some are regulatory changes, such as the adoption of new financial reporting standards or sustainability disclosure frameworks. Others emerge from operational feedback. Preparers may identify inconsistencies, gaps, or ambiguities in the taxonomy structure that need correction. In other cases, updates may be required to align with changes in technology, such as support for new data formats or analytical tools.

Failing to update taxonomies can introduce risks. Outdated taxonomies may lead to inaccurate data, difficulty comparing data across time periods or jurisdictions, or inconsistencies in reporting, such as using deprecated elements or omitting newly required disclosures.

For instance, if a taxonomy has not been updated to reflect new climate-related disclosures introduced in recent regulations, reporting entities may lack the appropriate elements to tag this information. This could lead to incomplete reports or inconsistent filings where some entities provide disclosures and others do not, simply due to the limitations of the taxonomy version they used.

On the other hand, unmanaged or overly frequent updates can also create problems. If taxonomy changes are not clearly communicated or are introduced without sufficient transition periods, preparers may struggle to comply, and software vendors may face delays in adapting their systems. This is why effective update management, including thoughtful timing, version control, and communication, is essential.

Successful taxonomy maintenance is rarely the task of a single institution. Regulators, preparers, software vendors, auditors, and data users play a role. Regulators, in particular, must coordinate with these stakeholders to understand how changes affect the broader ecosystem and ensure that the updates are meaningful, timely, and actionable.

For example, when the European Banking Authority (EBA) introduced updated disclosure requirements under the Pillar 3 framework, it significantly revised the related XBRL taxonomy. These updates involved structural changes, new concepts, and revised definitions to support enhanced transparency. In such cases, regulators should provide early drafts, clear documentation, and reasonable implementation timelines so that reporting institutions and software vendors have time to understand the scope, test changes, and update their systems accordingly.

In EBA’s case, the draft technical package for reporting framework 4.1 was published in late March 2025, with a public consultation period open until mid-April. The final version was scheduled for release in late May, and implementation expected by the end of the year, giving stakeholders approximately six months to prepare for the new requirements. This structured process illustrates how early communication and phased implementation reduce disruption and support effective adoption of taxonomy changes.

A structured approach is essential to ensuring that taxonomy updates are smoothly adopted across the ecosystem. It reduces the risk of delays, inconsistencies, or compliance issues, and provides a model that other regulators can follow when planning future updates.

Planning Taxonomy Updates: Strategies and Timing

Effective update management starts with a plan. Rather than making ad-hoc adjustments, regulators should define clear strategies that guide when and how taxonomies are updated. This structured approach brings stability and allows stakeholders to anticipate and prepare for changes in a coordinated way.

In this section, we explore two key components of update planning: establishing clear update cycles and making well-timed decisions on when changes should occur.

Planning Taxonomy Updates

Defining Update Cycles

A clear taxonomy update cycle is fundamental to maintaining order and predictability within the reporting system. Without it, stakeholders may be caught off guard, leading to rushed adaptations and potential reporting inconsistencies.

To support a stable reporting ecosystem, it is essential to distinguish between different types of updates.

  • Regular updates: These are typically scheduled to incorporate planned modifications, such as enhancements reflecting new reporting requirements, sector-specific extensions, or improvements based on user feedback. For example, a regulator may introduce a yearly update to add new reporting elements for digital assets following changes in financial policy.

  • Bug fixes and minor adjustments: These address corrections or clarifications that improve accuracy or usability. Although these are generally less disruptive, they must be carefully managed to avoid overwhelming reporting entities or system implementers. For example, a data type may need to be adjusted — from a generic numeric type to a positive numeric type — or a label may be updated to clarify its meaning without changing the underlying structure.

  • Major structural changes: These involve substantial revisions to the taxonomy’s architecture or core design. These require careful planning, early communication, and coordinated implementation across the ecosystem. For example, the introduction of IFRS 18, a new international standard on the presentation of financial statements that replaces IAS 1 and mandates substantial changes to the presentation of the statement of profit or loss, including new required subtotals and disclosures. Such a shift requires significant restructuring of the taxonomy to reflect the revised reporting model and ensure that all entities can comply with the updated standard.

Each type of update should follow a predictable pattern, including advance announcements, clear supporting documentation, and appropriate transition periods. This level of transparency allows reporting entities to prepare processes and data accordingly while giving software vendors time to update and validate their tools in alignment with the changes.

Understanding the types of updates is only part of the equation; knowing when to implement them is just as important to ensure a smooth and coordinated adoption.

Timing Considerations

Once the scope and type of a taxonomy update have been defined, the next critical question is when it should be implemented. Timing can distinguish between a smooth transition and a disruptive reporting cycle. Poorly timed updates may catch reporting entities unprepared, result in misaligned software deployments, or even compromise the quality of submitted data.

Planned updates should be aligned with the reporting calendar of the regulated entities. Annual or biennial updates are common practice and help stakeholders anticipate changes, schedule internal adjustments, and allocate resources accordingly. When updates coincide with the start of a new reporting cycle, organisations have a natural window for adaptation, minimising disruption to ongoing processes.

For example, the release of IFRS 18 by the International Accounting Standards Board (IASB) offers a clear case of a periodic update with a structural impact managed through transparent planning. The IASB published drafts for public comment, hosted advisory group meetings, and issued supporting materials well before the standard’s effective date. This process included a corresponding taxonomy update proposal published and discussed with the IFRS Taxonomy Consultative Group, helping ensure that preparers, software vendors, and regulators had time to review and adapt before the standard’s implementation. Such practices exemplify how good timing and communication reduce disruption and foster trust across the reporting ecosystem.

In some cases, taxonomy updates are triggered by external events, such as adopting new legislation or publishing revised accounting standards. These changes may require urgent updates, but regulators should consider allowing a reasonable lead time for implementation. Doing so ensures that preparers and software vendors are not forced to react hastily, which could result in errors or delays.

For instance, a validation rule may have passed testing but, once in production, begins rejecting technically correct and compliant data. In such cases, a rapid update to the rule is necessary to avoid reporting disruptions. This scenario highlights the importance of active monitoring after release and maintaining agile mechanisms to respond to urgent feedback from preparers or vendors.

It is also important to avoid overlapping major updates. If regulators introduce taxonomy changes simultaneously with other system upgrades or regulatory shifts, stakeholders may face an excessive implementation burden. A well-coordinated update calendar allows changes to be spaced appropriately and communicated well in advance.

Good timing allows each stakeholder to fulfil their role effectively, whether that means updating software tools, adjusting internal workflows, training staff, or testing data outputs. As highlighted in Communicating Taxonomy Changes, proactive and transparent planning gives preparers, vendors, and regulators the shared visibility needed to manage transitions without unnecessary disruption.

Choosing Versioning Strategies

Establishing a clear versioning strategy is key to managing taxonomy updates in a structured, predictable, and transparent way. It allows all stakeholders — regulators, preparers, vendors, and data users — to understand the scope of changes, determine their impact, and plan implementations accordingly.

Structured Versioning Schemes

Versioning schemes differentiate between major releases, minor updates, and corrective fixes. While the specific structure may vary, the objective is always to provide clarity and consistency across updates. Taxonomy owners can adapt according to their update cycles and communication needs. Choosing the right versioning model, and applying it consistently, helps build trust and predictability across the reporting ecosystem.

Regulatory-Specific Models

Regulators often design custom versioning systems tailored to their own regulatory frameworks. These models may incorporate elements such as regulatory references, dates of publication, or updated identifiers that reflect the jurisdiction’s legislative environment. While such customisations can add contextual value, they should aim for clarity, avoiding overly complex codes that could create confusion or misalignment in implementation. The taxonomy versioning guidance discusses different versioning schemes and provides considerations for choosing versioning schemes.

Supporting Compatibility and Transitions

Versioning is closely tied to how changes are introduced. A well-managed versioning approach includes mechanisms to maintain backward compatibility, allowing previous versions to remain valid for a defined period while new versions are adopted. This may involve retaining deprecated elements, publishing mapping guides to clarify changes, and defining transition periods in which multiple versions are accepted. These strategies reduce the risk of disruption and support gradual adoption by preparers and software providers.

Responding to Unexpected Changes

Even with strong planning, unanticipated issues can arise, such as technical errors discovered after a taxonomy release or urgent regulatory changes that require immediate updates. In such cases, the versioning model must be flexible enough to accommodate quick corrections or emergency releases without undermining clarity. Having predefined processes for issuing such updates and transparent communication is essential to protect the reliability and integrity of the reporting process.

Communicating Taxonomy Updates Effectively

The effectiveness of a taxonomy update depends not only on its technical soundness but also on how clearly and proactively it is communicated. Without timely and accessible communication, even well-planned changes can lead to confusion, misinterpretation, or delays in implementation. Regulators and taxonomy owners should, therefore, establish structured communication strategies that anticipate the needs of different stakeholder groups and provide information in an understandable and actionable way.

Establishing a Structured Communication Plan

A consistent communication plan should be in place for all taxonomy updates, whether scheduled or urgent. The plan should define how updates will be announced, what types of information will be provided, and through which channels. This includes timelines, the scope of changes, and any required actions from reporting entities or vendors. As noted in the XBRL International guidance on communicating taxonomy changes, having a predefined approach ensures transparency and reduces uncertainty across the ecosystem.

Regular vs. Urgent Modifications

While regular updates can be communicated through routine channels and advance notice, urgent or unplanned changes require a more agile response. Even in these cases, clarity is essential. Communications should explain not only the change itself but also the reason for its urgency, impact, and any temporary mitigation measures. The communication strategy must be flexible enough to accommodate both scenarios without compromising reliability or stakeholder confidence.

Stakeholder Involvement

Effective communication is not one-way. Engaging stakeholders throughout the update process helps to anticipate concerns, detect potential misunderstandings, and encourage adoption. This may involve consulting key preparers and software vendors before finalising changes or gathering feedback during implementation to identify issues early. Stakeholder feedback loops are particularly important when updates affect critical reporting processes or require system adaptations.

Communication Methods and Supporting Materials

Different types of users require different formats and levels of detail. Communication materials should be provided for both technical and business audiences. The following communication methods are commonly used in practice and represent effective strategies for helping stakeholders understand and apply taxonomy changes:

  • Business-oriented documentation can explain the rationale and implications of changes in accessible language, highlighting what matters most to decision-makers and preparers.

  • Interactive tools — such as comparison viewers or change visualisation platforms — can help users efficiently explore differences between taxonomy versions.

  • Training sessions, webinars, or brief guidance notes may be necessary for more significant updates, especially when new reporting requirements or structures are introduced.

Combining these methods ensures that all stakeholders, not just the technically proficient, can understand and respond appropriately to taxonomy changes.

Clear communication lays the groundwork for effective implementation, which must also be supported by technical integration into existing systems.

Integrating Taxonomy Updates into Reporting Systems

Implementing a taxonomy update involves publishing new files and ensuring that those updates are correctly and consistently reflected across reporting systems. From preparers and software vendors to regulators and data analysts, each stakeholder relies on robust integration to maintain the integrity and usability of reported information. Proper integration helps prevent misreporting, technical errors, and misalignment between expected and submitted data.

Testing and Validation Before Deployment

Before a new taxonomy version is adopted, it must be thoroughly tested in the technical environment in which it will operate. This includes validating the taxonomy structure itself, testing it against existing reporting software, and ensuring that validation rules behave as expected. Pre-deployment testing helps detect potential compatibility issues or unexpected behaviour early, reducing the risk of disruptions once reporting begins.

Some regulators also provide public testing environments or pre-release packages to allow vendors and preparers to test their own tools and workflows. These practices improve technical readiness and build confidence among reporting entities.

Coordinating Taxonomy Updates with System Changes

Changes to reporting platforms, portals, or back-end systems often accompany taxonomy updates. Coordinating these technical updates is essential to avoid delays or mismatches. For example, if a taxonomy includes a new data point but the platform does not yet support its entry or validation, preparers may encounter system errors or confusion.

Establishing coordination between the teams managing taxonomy content and those responsible for IT infrastructure or software development ensures that updates are implemented holistically. In some jurisdictions, governance structures or working groups support this alignment by bringing together technical and regulatory actors.

Long-Term Planning for Sustainable Taxonomy Evolution

Integration should not be treated as a one-off event. Instead, it should be part of a long-term strategy to ensure taxonomy updates align with system capabilities, stakeholder needs, and broader regulatory developments. This includes forecasting future changes, planning release cycles well in advance, and maintaining historical support for prior versions when needed.

Sustainable taxonomy management also involves documenting lessons learned from each update cycle, gathering user feedback, and adjusting integration processes over time. This forward-looking approach strengthens the reporting system’s resilience and enables continuous improvement.

Summary

Taxonomy updates are inevitable in any dynamic regulatory environment. However, the success of these updates depends not only on the taxonomy’s technical quality but also on how they are planned, versioned, communicated, and integrated. A thoughtful and well-coordinated approach that anticipates stakeholder needs, allows for smooth transitions, and provides clarity throughout the process can minimise disruption and enhance the effectiveness of the reporting system.

Regulators and taxonomy owners should see taxonomy maintenance as an ongoing responsibility rather than a reactive task. This includes establishing predictable update cycles, adopting consistent versioning strategies, planning realistic timelines, and building transparent communication channels. It also requires collaboration across technical and regulatory teams and active engagement with preparers and software vendors.

Ultimately, managing taxonomy updates is not just about keeping up with change but about enabling better, more reliable, and more future-ready digital reporting.