New EU 2026 Financial Reporting Requirements: What Entities Must Change

Key data

Financial entities subject to Implementing Regulation (EU) 2021/622 face a new and urgent obligation: to adapt their reporting systems to the changes introduced by the Implementing Regulation (EU) 2026/519, in force from 10 March 2026. This is not a minor adjustment: both the frequency of reports and the specific content that must be communicated to supervisory authorities are changing.

The impact is twofold: operational and technological. Reporting schedules must be reviewed, and information formats and fields must be updated to comply with the new technical specifications. Failure to do so exposes the entity to sanctions from competent supervisors, both at national and European level.

What does this regulation establish?

Regulation 2026/519 modifies the technical standards for implementation of Implementing Regulation (EU) 2021/622. The two axes of change are:

The regulation does not introduce a reporting system from scratch: it modifies the one that already existed under Regulation 2021/622. This means that entities already reporting under that framework must specifically review what has changed in frequency and content, not reimplements the entire system.

The changes directly affect internal processes for data collection and submission, with implications for both compliance teams and technology departments managing reporting systems.

Economic and operational impact

The impact of this regulation is not primarily economic in terms of direct fees or payments, but rather operational and regulatory risk. The real costs for entities are concentrated in three areas:

• Technological adaptation: The systems that generate and send reports to supervisors must be updated to reflect new fields, formats and frequency. Depending on each entity's degree of automation, this may involve anything from configuration adjustments to software development.
• Review of internal processes: Reporting schedules must be updated. If frequency increases, compliance teams need more resources or greater automation to meet deadlines.
• Risk of sanctions for non-compliance: The Regulation explicitly establishes that non-compliance may result in supervisory sanctions from national and European competent authorities. Although the regulation does not detail specific penalty amounts, the reputational and regulatory risk is significant for any supervised entity.

The cost of non-adaptation systematically exceeds the cost of adaptation in the European financial supervision sphere. Competent authorities have direct sanctioning capacity over entities that fail to meet reporting requirements.

Who does it affect?

The regulation directly affects:

• Financial entities subject to Implementing Regulation (EU) 2021/622 and required to submit periodic information to supervisory authorities.
• Financial supervisors who receive and process information reported under Regulation 2021/622.
• Compliance departments of affected entities, responsible for ensuring that reports are submitted on time and in proper form.
• Technology departments of affected entities, responsible for adapting reporting systems to new technical specifications.
• CFOs and financial directors of financial entities, who must ensure that resources necessary for adaptation are available.

If your entity already reported under Regulation (EU) 2021/622, this regulation affects you directly and immediately.

Practical example

A medium-sized financial entity that reported quarterly under Regulation 2021/622 faces the following scenario with the entry into force of Regulation 2026/519:

Its technology department receives instructions to review the data fields that are automatically sent to the supervisor. Some fields have changed definition or new ones have been added according to updated technical specifications. If the system is not updated, reports will be sent in incorrect format or with obsolete fields, which may result in a supervisor request or, in case of recurrence, a formal sanction.

At the same time, if the new frequency requires more frequent reports (for example, monthly instead of quarterly), the compliance team must reorganize its work schedule and ensure that source data is available with sufficient notice to meet the new deadlines.

The first practical step is to compare the text of Regulation 2026/519 with 2021/622 to identify exactly which fields and frequencies have changed, and communicate that information to the technical team with an implementation plan.

What should companies do now?

1. Identify if your entity is subject to Regulation (EU) 2021/622. If you already reported under that framework, Regulation 2026/519 applies to you from 10 March 2026.
2. Compare Regulation 2026/519 with 2021/622 to identify exactly what has changed in reporting frequency and required information fields. This comparison should be done by the compliance team with legal support if necessary.
3. Communicate the changes to the technology department with a specific list of new, modified or deleted fields, and new submission deadlines, so they can update the reporting systems.
4. Review and update the internal reporting schedule to adjust it to the new required frequency, assigning responsible parties and deadlines that guarantee compliance.
5. Document the adaptation process to be able to demonstrate to the supervisor that the entity has taken diligent measures since the regulation came into force.
6. Verify compliance before the next reporting cycle by testing the reports generated under the new format before sending them to the supervisor.