Rule · BCB · 16 Oct 2023 · Instrução Normativa BCB 414
This instruction updates the layout and filling instructions for SCR Document 3040 to align with Resolution CMN No. 4,966/2021, removing obsolete risk classification attributes and introducing new fields for expected loss provisions, financial instrument accounting stages, and loss reasons. Modifications effective from the January 2025 data base include adding XML header attributes for provision methodologies and replacing old annexes with new ones detailing accounting classifications and minimum provisions. Additional changes effective from the January 2026 data base require reporting monthly income and specific allocation reasons for financial instruments into different stages.
The Head of the Financial System Monitoring Department (Desig), in use of the attribution conferred by him by art. 23, item I, letter “a”, of the Internal Regulations of the Central Bank of Brazil, annexed to Resolution BCB No. 340, of September 21, 2023, based on art. 85, item I, letter “b”, of said Regulations, having in view the provision in Resolutions CMN Nos. 4,966, of November 25, 2021, and 5,037, of September 29, 2022, in Circular No. 3,870, of December 19, 2017, and in Circular Letter No. 3,869, of March 19, 2018,
RESOLVES:
Art. 1º The new versions of the Layout and the Filling Instructions for document 3040 - Credit Risk Data, available on the Central Bank of Brazil’s internet page, at the electronic address https://www.bcb.gov.br/estabilidadefinanceira/scrdoc3040, enter into force, from the specified data bases.
Art. 2º The following modifications were made to the Layout of document 3040, with effect from the data base of January 2025:
I - in the header of the XML document, in the field “Attributes of document 3040”, inclusion of the attributes:
II – in the block “For each client (Cli)”, in the field: “Element for demarcation of Client information”, Element (tag) Cli, exclusion of the attribute:
III - in the block “For each client operation (Op) – a. BASIC information of the operation”, in the field “Element for demarcation of Operation information”, Element (tag) Op, exclusion of the attribute:
IV - in the block “Value of Maturities (Venc)”, in the field “Value of Maturities”, Element (tag) Venc, alteration of the field description;
V - exclusion of the block “f. Financial Instrument Accounting Information (ContInstFin)”;
VI - inclusion of the block “h. Financial Instrument Accounting Information - CMN Resolution 4,966/2021 (ContInstFinRes4966)” with the element (tag) ContInstFinRes4966 and its attributes;
VII – inclusion of the block “j. Information on recognition of losses” with the element (tag) Perda and its attributes;
VIII – in the block “For each aggregation - a. Aggregator Fields (Agreg)”, in the Element (tag) Agreg, exclusion of the attributes:
IX - exclusion of Annex 16, “Risk Classification - ClassCli”;
X - exclusion of Annex 17, ”Risk Classification - ClassOp”;
XI - exclusion of Annex 19, “Double Term for Provisioning”;
XII - exclusion of Annex 38, “Accounting category”;
XIII - inclusion of Annex 39, with description “Methodology for Calculating the Provision for Expected Losses”;
XIV - inclusion of Annex 40, with the description “Accounting Classification of the Financial Instrument”;
XV - inclusion of Annex 41, with the description “Stage of the Financial Instrument”;
XVI - inclusion of Annex 43, with the description “Portfolio - Minimum Provision”; and
XVII - inclusion of Annex 44, with the description “Reason for Loss”.
Art. 3º The following modifications were made to the Layout of document 3040, with effect from the data base of January 2026:
I – in the block “h. Financial Instrument Accounting Information - CMN Resolution 4,966/2021 (ContInstFinRes4966)”, in the Element (tag) ContInstFinRes4966, inclusion of the following attribute:
II – inclusion of the block “i. Information on reasons for allocation of the financial instrument in Stages (Arts. 37 to 39)”, with the Element (tag) Estagio and its attributes.
III - inclusion of Annex 42, with the description “Reason for allocation of the financial instrument in the Stage”;
Art. 4º The following modifications were made to the Filling Instructions for document 3040, with effect from the data base of January 2025:
I - in item "B. Header of the XML document - (tag) xml":
II - in item "C. Client Information - (tag Cli)":
III - in item “D. Operation Information”:
V - inclusion of item "H. Financial Instruments - (tag ContInstFin)";
VI - inclusion of item "I. Financial Instruments– (new tags ContInstFinRes4966 Estagio Perda )".
Art. 5º The following modifications were made to the Filling Instructions for document 3040, with effect from the data base of January 2026:
I - in item "I. Financial Instruments– (new tags ContInstFinRes4966 Estagio Perda )":
Art. 6º This Normative Instruction enters into force on November 1, 2023.
GILNEU FRANCISCO ASTOLFI VIVAN
NOTE
The Credit Information System (SCR) is a system in which credit operations of clients whose direct risk in the financial institution (sum of credit operations, interbank transfers, co-obligations, limits, and credits to be released) is equal to or greater than R$ 200.00 (two hundred reais) are registered. The SCR is managed by the Central Bank and fed monthly by financial institutions, being continuously updated in order to fulfill the functions provided for in art. 2º of CMN Resolution No. 5,037, of September 29, 2022, and under the terms of Circular No. 3,870, of 2017.
CMN Resolution No. 4,966, of November 25, 2021, whose validity will begin on January 1, 2025, provides for the concepts and accounting criteria applicable to financial instruments, as well as for the designation and recognition of hedging relationships (hedge accounting) by financial institutions and other institutions authorized to operate by the Central Bank of Brazil.
Said Resolution significantly alters the way credit operations are accounted for, aiming to adapt our accounting to international standards and with the consequent reduction of asymmetries currently existing.
Consequently, it is necessary to alter the layout of code 3040 document - Credit Risk Data of the SCR, which was phased in two stages, with a view to its best implementation.
Decree No. 10,411, of June 30, 2020, regulates the carrying out of regulatory impact analysis (RIA) as a prerequisite to the issuance of normative acts. However, as provided in art. 22 of the aforementioned Decree, the obligation to prepare an RIA does not apply to proposals for normative acts that have already been submitted to public consultation on the date of production of effects of the Decree, a situation in which the devices of CMN Resolution No. 4,966, of 2021, fall. Thus, as this Normative Instruction only adapts Code 3040 Document to the provision in CMN Resolution No. 4,966, of 2021, I understand that the issuance of this normative is exempt from carrying out an RIA.
GILNEU FRANCISCO ASTOLFI VIVAN
Head of the Monitoring Department of the Financial System (Desig)
Note from RegAlert. AI assistants can read this document in full, and search 70,000+ more, through the RegAlert MCP connector (https://mcp.regalert.today/mcp). Free with an account. How to connect ChatGPT, Claude or Cursor.
A newer document in RegAlert amends this one; it applies as amended.
“continuing the adjustments that began with BCB Normative Instruction No. 414, of October 16, 2023”
“and 5,037, of September 29, 2022”
“having in view the provision in Resolutions CMN Nos. 4,966, of November 25, 2021”
“in Circular No. 3,870, of December 19, 2017”
“attribution conferred by him by art. 23, item I, letter “a”, of the Internal Regulations of the Central Bank of Brazil, annexed to Resolution BCB No. 340, of September 21, 2023”
“and in Circular Letter No. 3,869, of March 19, 2018”
Amended 1 time · last 2024-10-18
More like this from BCB
BCB published 10 documents in the last 30 days. We email you each new one the day it's published.
Source: Banco Central do Brasil — original document · Summary generated with machine assistance and reviewed before publication; the authoritative text is the regulator's original document. How RegAlert works
In RegAlert: added · updated