Skip links
Regulation and Compliance

Document 5050 (DRO): what is changing in the Operational Risk Statement and how your institution can prepare

25 de September de 2026
|
Por Time Better Now
Compartilhe
|

Over the past few months, the Central Bank of Brazil (BCB) has stepped up updates to the rules governing Document 5050, the Operational Risk Statement (Demonstrativo de Risco Operacional, or DRO). For financial institutions in segments S1, S2 and S3, understanding these changes is no longer a task for the compliance team alone: it has become a matter of data governance, systems integration and the operational capacity to meet increasingly tight deadlines.

In this article, we explain what Document 5050 is, who is required to submit it, what has changed recently, and why technical readiness is just as important as regulatory readiness.

What Document 5050 (DRO) is

The DRO is a standardized report that consolidates, on a semiannual basis, the operational losses of financial institutions authorized to operate by the Central Bank. It gives the regulator a detailed view of operational risk exposure across the Brazilian financial system and supports the calculation of regulatory capital, in line with the pillars of the Basel III Accord.

In practice, the document organizes loss events by risk category (the Basel II Level 1 and Level 2 categories), business unit and internal accounting sub-account, and it is transmitted in XML format through the Central Bank’s File Transmission System (Sistema de Transmissão de Arquivos, or STA).

Who must submit the DRO

The submission requirement follows the segmentation of institutions defined by CMN Resolution No. 4,553/2017 and BCB Resolution No. 436/2024:

  • Institutions in segments S1 and S2 have been submitting the document for several years
  • Type 3 institutions classified in S2 have been submitting it since the June 2024 reference date
  • Institutions in segment S3, including Type 3 institutions classified in S3, become subject to the requirement as of the June 2026 reference date

This expansion in scope is one of the most significant aspects of the recent changes: it extends the requirement to a much broader group of institutions, many of which do not yet have mature processes for collecting and consolidating operational loss data.

Updates introduced by Normative Instructions 700 and 744

Two regulations published in 2026 significantly revised the completion instructions and the layout of Document 5050:

BCB Normative Instruction No. 700 (January 2026)
Extended the requirement to institutions in segment S3, changed the review period for data disposal from 30 to 90 days, and established a schedule for newly included institutions to submit events from prior periods.

BCB Normative Instruction No. 744 (June 2026)
Introduced a new round of adjustments to the layout and completion instructions, effective as of the June 2026 reference date, including changes to the chapters on general information and the document’s time coverage.

For the December 2026 reference date, the changes are even more structural: the new XML layout adds Block 5 (Excluded Individualized Events), intended to report events that are no longer disclosed on an individualized basis, as well as new fields related to loss provisions and recoveries, such as provisaoTotalCIV, provisaoTotalTRA and recuperacaoTotalConsol, among others.

Why this matters beyond compliance

It is tempting to treat the DRO as a one-off regulatory exercise, handled every six months with a spreadsheet and a concentrated effort from the risk team. But the nature of the document points to something deeper: it requires the institution to have continuous, reliable visibility into its own operational events, including incidents, process failures, fraud losses and contingencies.

This ties directly to a challenge many institutions still handle manually: how to capture, classify and consolidate operational events consistently, auditably and traceably over time, without relying on manual reconciliations on the eve of submission to the Central Bank.

Institutions that treat operational risk management as part of their reliability engineering, rather than merely as a regulatory obligation, reach each new reference date with less rework and a lower risk of inconsistency between what is reported and what actually happened.

How Better Now can help

For years, Better Now has worked alongside financial institutions, fintechs, insurers and payment operations to build reliable processes for data and critical operations. This includes supporting risk and compliance teams in organizing workflows for collecting and consolidating operational events, integrating internal systems with regulatory requirements such as Document 5050, and preparing for new compliance cycles, such as the one now reaching segment S3 institutions.

If your institution is preparing for the new DRO schedule, or reviewing internal processes to accommodate the layout that takes effect in December 2026, our team can help you map the points of attention before they become urgent.

Talk to Better Now and learn how to turn Document 5050 compliance into a more predictable, less operationally costly process.

    *Your data is handled safely and in compliance with the LGPD.
    For more information, see our Privacy Policy.

    Other articles

    Contact Us

    Doubts? Talk to us using the form below