Rule · BCB · 16 Nov 2026 · Instrução Normativa BCB 788
IOSMFs requesting authorization for changes to an SMF or its regulations must, in Phase 1, file an application (Annex VII) with extensive motivation and a Sisorf 8.24.20.11 declaration of compliance with Resolution No. 304 requirements and updated Annex IX documents; in Phase 2, within 180 days of the Central Bank of Brazil's favorable manifestation, they must submit a Sisorf 8.24.20.8 readiness declaration with business continuity, availability, cybersecurity and functional testing reports ensured by Internal Audit, a production deployment plan and a certification plan.
The heads of the Departments of Financial System Organization - Deorf and of Banking Operations and Payment System - Deban, using the attributions conferred upon them by arts. 23, item I, subitem "a", 98, item VI, and 112, item II, subitem "a", of the Internal Regulations of the Central Bank of Brazil, annexed to BCB Resolution No. 340, of 21 September 2023, based on arts. 4, § 1, and 6 of BCB Resolution No. 304, of 20 March 2023,
R E S O L V E M :
Art. 1 BCB Normative Instruction No. 374, of 26 April 2023, published in the Official Gazette of the Union of 27 April 2023, shall come into force with the following amendments:
"Art. 6 ............................................................
........................................................................................................................." (NR)
"Art. 8 ......................................................................................................................
..................................................................................................................................
........................................................................................................................." (NR)
"Art. 10. ....................................................................................................................
..................................................................................................................................
........................................................................................................................." (NR)
"Art. 12. ....................................................................................................................
..................................................................................................................................
........................................................................................................................." (NR)
"Art. 21. ..................................................................................................................
.................................................................................................................................
§ 1 ..........................................................................................................................
........................................................................................................................." (NR)
"Art. 23 . In Phase 1, of the Proposal Analysis, the request for authorization of changes in the SMF and in their regulations dealt with in items IV to XXV of art. 21 must be accompanied by the following documents and information:
I - application, in the form of Annex VII;
II - ...........................................................................................................................
........................................................................................................................" (NR)
"Art. 23-A. In Phase 1, of the Proposal Analysis, the request for authorization of changes in the SMF and in their regulations dealt with in item I of art. 21 must be accompanied by the following documents and information:
I - application, in the form of the Sisorf 8.24.10.7 model;
II - explanatory document containing the motivation, which may be market-related, financial, prudential or other, presented extensively;
III - declaration, in the form of the Sisorf 8.24.20.11 model, signed by the requesting IOSMF, regarding:
a) compliance with the requirements provided for in items I, II and III of art. 3 of the Regulation Annexed to Resolution No. 304, of 20 March 2023;
b) possession of updated versions of the documents listed in Annex IX, contemplating changes eventually necessary to the authorization request.
Sole paragraph. The documents provided for in Annex IX:
a) must be prepared prior to the filing of the request and must be kept under the custody of the institution;
b) may be required by the Central Bank of Brazil at any time, before or after the issuance of the authorization of the request dealt with in the caput; and
c) must only be forwarded to the Central Bank of Brazil upon specific request." (NR)
"Art. 24. ............................................................................................
................................................................................................................................
.........................................................................................................................” (NR)
“Art. 24-A. In Phase 2, of the Analysis of Proposal Implementation, the authorization request must be accompanied, within 180 (one hundred and eighty) days counted from the favorable manifestation of the Central Bank of Brazil to the proposal referred to in art. 23-A, by the following documents and information:
I - application, in the form of the Sisorf 8.24.10.8 model;
II - readiness declaration, in the form of the Sisorf 8.24.20.8 model, accompanied by, at minimum:
a) business continuity testing report, when this is to some extent impacted, to be prepared or ensured by Internal Audit, respecting the provisions of Section V of Chapter VI of Title IV and Chapter I of Title V of the Regulation annexed to BCB Resolution No. 304, of 2023;
b) report evidencing the availability, capacity and performance of the SMF, when these disciplines are to some extent impacted, to be prepared or ensured by Internal Audit, respecting the provisions of Section V and Section VI of Chapter VI of Title IV and Chapter I of Title V of the Regulation annexed to BCB Resolution No. 304, of 2023;
c) cybersecurity testing report, when this is to some extent impacted, to be prepared or ensured by Internal Audit, respecting the provisions of Section VII of Chapter VI of Title IV of the Regulation annexed to BCB Resolution No. 304, of 2023; and
d) list of active system change requests (evolutionary and corrective maintenance and the like), as well as a list with the backlog of defects identified during testing of the systems that will support the activity performed;
III - production deployment plan, including a description of the strategy for deploying the systems, including preliminary procedures, change to the production environment, rollback forecast, support for participants and other information that may be necessary;
IV - functional testing report, ensured by Internal Audit, in compliance with the provisions of Annex VI; and
V - certification or homologation plan with the participants.
§ 1º The term referred to in the caput may be extended, at the discretion of the Central Bank of Brazil, upon a justified request by the interested party.
§ 2º The Central Bank may waive the presentation of one or more documents provided for Phase 2 when there is sufficient evidence of compliance with the authorization requirements.” (NR)
Art. 2º Annex I to BCB Normative Instruction No. 374, of 26 April 2023, published in the Official Gazette of the Union of 27 April 2023, shall come into force with the following amendment:
“Art. 1º.....................................................................................................................
I - .............................................................................................................................
.................................................................................................................................
- 11. Exposure of interconnections with other SMF;
.........................................................................................................................” (NR)
Art. 3º Annex V to BCB Normative Instruction No. 374, of 26 April 2023, published in the Official Gazette of the Union of 27 April 2023, shall come into force with the following wording:
Art. 1º The functional testing script must be prepared considering the following premises:
I - functional tests must comprehensively, completely and traceably cover the functionalities, business rules and controls that will be implemented in the System;
II - scenarios must be prepared and tested that cover both routine and non-routine situations, aiming to validate the functional, logical and control behavior of the System;
III - the scenarios must reflect the different applicable operational conditions, and must include, but not be limited to, the following aspects:
a) System time schedules, considering the different operational states, such as opening and closing periods, as well as any specific operating windows;
b) status of the participant and its users, covering states such as active, inactive, suspended or any others provided for in the System's rules;
c) permissions by category of participant and its users, including authorization, authentication, access control mechanisms and verification of the functionalities effectively permitted for each profile;
d) transaction control, focusing on the validation and correct application of the established business rules, ensuring that only valid transactions are processed;
e) conflicting transactions, evaluating scenarios that contradict the System's rules in relation to the activities performed and/or the specific characteristics of the financial asset;
f) traceability of operations, ensuring the recording, storage and auditability of the complete history of transactions carried out in the System; and
g) integrity of information, ensuring the accuracy, consistency, completeness and reliability of data throughout the entire processing cycle;
IV - the scope of the scenarios must be defined in accordance with the applicable regulatory framework and with the functional and operational requirements of the Settlement System. By way of example, a non-exhaustive list of topics and aspects that must be considered and evaluated in the definition and execution of test scenarios is presented below:
a) Requirements and the moment of acceptance of an operation;
b) Situations that evidence the different statuses of the obligation settlement process, as well as the conditions that allow some of these statuses to be reversed;
c) Example with calculation of the multilateral net balance of operations accepted by the System, when applicable;
d) Detailed description of the steps followed in the different settlement modalities offered to participants, as well as change of modality upon request by the participant or due to settlement failure;
e) Settlement schedules, evidencing important moments such as, for example, the opening and closing of multilateral windows;
f) Final settlement and recalculation of obligations in the event of settlement failures, when applicable;
g) Interactions with depositories and registrars of financial assets and securities, with irrefutable evidence of the link between assignment of contractual position or transfer of ownership of financial assets, securities or commodities (delivery versus payment), which may include the prior blocking of financial assets, securities and commodities to be delivered in the settlement window;
h) Participant default;
i) Treatment of participant default, with possible allocation of losses and replenishment of resources;
j) Measurement, monitoring and response to credit and liquidity exposures, when applicable;
k) Use and effectiveness of credit and liquidity risk controls, such as limits, blocks, rejections and intraday credit, when applicable;
l) Collateral management, covering acceptance, rejection, monitoring, concentration and mitigation of unfavorable correlation risk; and
m) Liquidity management, with identification of resource needs and testing of procedures for accessing liquid resources, ensuring timeliness and traceability;
V - the test script shall prioritize negative scenarios (controlled failure), in order to induce and validate the effectiveness of internal controls, aiming to ensure that the System responds adequately to exceptional situations and rule violations, in addition to testing the mechanisms for preventing improper use. For this purpose, the tests must include the use of valid and invalid data, as well as attempts to execute functionalities not compliant with the System's rules, with the objective of verifying whether:
a) the criticisms and validations performed by the System are consistent and compliant with the defined rules;
b) the error messages are clear, appropriate and informative and are correctly displayed when using invalid data or executing operations not permitted;
c) the business rules are correctly applied in all tested scenarios; and
d) the expected results are effectively achieved, both in cases of processing valid data and in cases of rejection of invalid data;
VI - in tests referring to the use of invalid data, it is recommended that preference be given to the use of data that respects the expected format and structure for the fields, but whose content is incompatible with the rule of the tested transaction, so as to allow more precise verification of the semantic validations and business rules of the System.
Art. 2 The functional test script shall be prepared with the following structure:
I - identification of the IOSMF, the SMF, the technical managers, the SMF version, the location and the dates on which the tests were performed;
II - executive summary presenting an objective general opinion about the System, covering:
a) the main findings;
b) the level of reliability of the controls;
c) the number of scenarios tested;
d) the number of scenarios with unexpected results;
e) the period of execution of the scenarios;
f) the area responsible for executing the tests;
g) the assessment regarding compliance with the rules set forth in the applicable regulations and normative acts; and
h) any recommendations for improvement;
III - index with the identifier, the respective tested scenario and the page in the document;
IV - detailed description of the tested scenarios.
Art. 3 The detailed description of the scenarios must be prepared in a standardized manner, observing the following structure:
I - Scenario Identifier: unique and standardized code that individualizes the test scenario, with the objective of ensuring uniqueness, traceability and standardization of the test scenarios, composed of four elements, separated by a hyphen, interpreted in the following order:
a) Test Type: Acronym that identifies the nature of the test;
b) Main System: Indicates the system in which the process originates;
c) Main Participant: Identifies the participant that initiates or conducts the execution of the scenario; and
d) Sequential Number: Incremental numerical code that individualizes the scenario within the same combination of the previous elements;
II - Scenario: synthetic and direct denomination of the process or situation to be tested and that considers, preferably, the perspective of the System participant, with the objective of facilitating the rapid identification of the test and its classification within the business process as a whole;
III - Scenario Objective: statement of the central purpose of the test execution, explaining the functionality, business rule, functional requirement or systemic integration being validated, with the objective of making explicit the focus of the assessment in the scenario, facilitating the measurement of success and the delimitation of the scope of evidence;
IV - Test Type: classification of the test regarding the nature of the business flow to be validated, with the objective of ensuring that both normal paths and the expected rejection conditions are covered in the tests, and may take the following modalities:
a) Expected Flow (Success): Process executed according to the regular and expected path; and
b) Expected Error Flow (Controlled Failure): Process conducted in order to reproduce rejection or blocking conditions provided for in the business rules;
V - Profile of participants involved: list of all participants who interact with or are impacted by the scenario, with the objective of demonstrating the scope of the scenario within the ecosystem among different profiles of participants;
VI - Assumptions: pre-existing conditions that must be satisfied for the valid execution of the scenario, with the objective of establishing the initial state necessary for execution, avoiding failures arising from inadequate preparations;
VII - Form of access: description of the form of access used in the scenario, with the objective of testing the different forms of access to the System offered to the participant, such as system screens, APIs (Application Programming Interface), messages, files, among others;
VIII - Systems involved: indicates whether the scenario requires interconnection tests, listing the systems impacted directly or indirectly, with the objective of demonstrating the technical scope of the scenario in relation to the systems architecture;
IX - Processes: business processes correlated with the scenario, in line with the regulations presented within the scope of the authorization process, with the objective of ensuring traceability between the test scenario and the business process provided for in the regulations;
X - Minimum standard informational content: minimum set of mandatory data necessary for the valid execution of the process, with the objective of ensuring that the test validates the completeness and compliance of the information exchanged;
XI - Procedures / Stages of the scenario: ordered sequence of actions for executing the test, with the objective of verifying the logical structure of the process and monitoring execution;
XII - Success situations: conditions that characterize successful execution of the scenario, with the objective of providing clear criteria to determine test approval;
XIII - Failure situations: expected conditions of rejection or blocking of a process, with the objective of ensuring that the system reacts adequately to the expected error conditions;
XIV - Approval criteria: list of objective conditions for formal approval of the scenario, with the objective of providing a clear basis for the auditor to issue an opinion on approval.” (NR)
Art. 4º Annex VI to Normative Instruction BCB nº 374, of 26 April 2023, published in the Official Gazette of the Union of 27 April 2023, shall enter into force with the following wording:
Art. 1º The functional test report shall be prepared considering the following assumptions:
I - the functional tests must comprehensively, completely and traceably cover the functionalities, business rules and controls that will be implemented in the System;
II - scenarios must be prepared and tested that cover both routine and non-routine situations, aiming to validate the functional, logical and control behavior of the System;
III - the scenarios must reflect the different applicable operational conditions, and must include, but not be limited to, the following aspects:
a) System time schedules, considering the different operational states, such as opening and closing periods, as well as any specific operating windows;
b) status of the participant and its users, covering states such as active, inactive, suspended or any others provided for in the System rules;
c) permissions by category of participant and its users, including authorization mechanisms, authentication, access control and verification of the functionalities effectively permitted for each profile;
d) transaction control, focusing on the validation and correct application of the established business rules, ensuring that only valid transactions are processed;
e) conflicting transactions, evaluating scenarios that contravene the System rules in relation to the activities performed and/or the specific characteristics of the financial asset;
f) traceability of operations, ensuring the recording, storage and possibility of auditing the complete history of transactions carried out in the System; and
g) integrity of information, ensuring the accuracy, consistency, completeness and reliability of data throughout the entire processing cycle;
IV - the scope of the scenarios must be defined in accordance with the applicable regulatory framework and with the functional and operational requirements of the Financial Market System. By way of example, a non-exhaustive list of topics and aspects that must be considered and evaluated in the definition and execution of test scenarios is presented below:
a) In the case of a settlement system:
1. Requirements and the moment of acceptance of an operation;
2. Situations that evidence the different statuses of the obligation settlement process, as well as the conditions that allow some of these statuses to be reversed;
3. Example with calculation of the multilateral net balance of operations accepted by the System, when applicable;
4. Detailed description of the steps followed in the different settlement modalities offered to participants, as well as change of modality at the request of the participant or due to settlement failure;
5. Settlement schedules, evidencing important moments such as, for example, the opening and closing of multilateral windows;
6. Final settlement and recalculation of obligations in the event of settlement failures, when applicable;
7. Interactions with depositories and registrars of financial assets and securities, with irrefutable evidence of the link between assignment of contractual position or transfer of ownership of financial assets, securities or commodities (delivery versus payment), which may include the prior blocking of financial assets, securities and commodities to be delivered in the settlement window;
8. Participant default;
9. Treatment of participant default, with possible allocation of losses and replenishment of resources;
10. Measurement, monitoring and response to credit and liquidity exposures, when applicable;
11. Use and effectiveness of credit and liquidity risk controls, such as limits, blocks, rejections and intraday credit, when applicable;
12. Collateral management, covering acceptance, rejection, monitoring, concentration and mitigation of unfavorable correlation risk; and
13. Liquidity management, with identification of resource needs and testing of procedures for accessing liquid resources, ensuring timeliness and traceability;
b) In the case of centralized deposit of financial assets:
1. Inclusion, suspension or exclusion of a participant;
2. Account structure, access and participation;
3. Deposit of the financial asset;
4. Updates to the financial asset;
5. Deregistration of the deposit of the financial asset;
6. System for controlling fiduciary ownership;
7. Handling of events;
8. Creation, amendment and release of encumbrances and liens, if applicable;
9. Treatment of effects applicable to financial assets subject to encumbrances and liens;
10. Underlying assets and receivables – registration, updating, exclusion, linking, amendment;
11. Consultation of information;
12. Statements and reports;
13. Reconciliation;
14. Certificates;
15. Monitoring – behavioral fluctuations, atypicalities, non-standard operations, non-compliance with rules and procedures by participants;
16. Specific rules for financial assets eligible for deposit;
17. Portability;
c) In the case of registration of financial asset:
1. Inclusion, suspension or exclusion of a participant;
2. Account, access and participation structure;
3. Registration of the financial asset;
4. Registry of the financial asset;
5. Updates to the financial asset;
6. Deregistration of the financial asset;
7. Creation, amendment and release of encumbrances and liens, if applicable;
8. Treatment of effects applicable to financial assets subject to encumbrances and liens;
9. Underlying assets and receivables – registration, updating, exclusion, linking, amendment;
10. Consultation of information;
11. Statements and reports;
12. Reconciliation;
13. Certificates;
14. Monitoring – behavioral fluctuation, atypicality, non-standard operations, non-compliance with rules and procedures, failure to perform daily reconciliation by the participant, etc.;
15. Specific rules for financial assets eligible for registration; and
16. Portability;
V - the report should prioritize negative scenarios (controlled failure), in order to induce and validate the effectiveness of internal controls, aiming to ensure that the System responds adequately to exceptional situations and rule violations, in addition to testing the mechanisms for preventing improper uses. For this purpose, the tests must include the use of valid and invalid data, as well as attempts to execute functionalities not compliant with the System's rules, with the objective of verifying whether:
a) the criticisms and validations performed by the System are consistent and compliant with the defined rules;
b) the error messages are clear, appropriate and informative and are correctly displayed when invalid data is used or operations that are not permitted are executed;
c) the business rules are correctly applied in all tested scenarios; and
d) the expected results are effectively achieved, both in cases of processing valid data and in cases of rejecting invalid data;
VI - in tests concerning the use of invalid data, it is recommended that preference be given to the use of data that respects the expected format and structure for the fields, but whose content is incompatible with the rule of the transaction being tested, so as to allow more precise verification of the semantic validations and business rules of the System.
Art. 2 The functional testing report must be prepared with the following structure:
I - identification of the IOSMF, the SMF, the technical managers, the SMF version, the location and the dates on which the tests were performed;
II - executive summary presenting an objective general opinion about the System, covering:
a) the main findings;
b) the level of reliability of the controls;
c) the number of scenarios tested;
d) the number of scenarios with an unexpected result;
e) the period of execution of the scenarios;
f) the area responsible for executing the tests;
g) the assessment regarding compliance with the rules set forth in the applicable regulations and normative acts; and
h) any recommendations for improvement;
III - index with the identifier, the respective scenario tested and the page in the document;
IV - detailed description of the scenarios tested.
Art. 3 The detailed description of the scenarios must be prepared in a standardized manner, observing the following structure:
I - Scenario Identifier: unique and standardized code that individualizes the test scenario, with the objective of ensuring uniqueness, traceability and standardization of test scenarios, composed of four elements, separated by a hyphen, interpreted in the following order:
a) Test Type: Acronym that identifies the nature of the test;
b) Main System: Indicates the system in which the process originates;
c) Main Participant: Identifies the participant who initiates or conducts the execution of the scenario; and
d) Sequential Number: incremental numeric code that individualizes the scenario within the same combination of the previous elements;
II - Scenario: synthetic and direct denomination of the process or situation to be tested and which considers, preferably, the perspective of the System participant, with the objective of facilitating the rapid identification of the test and its framing within the business process as a whole;
III - Scenario Objective: declaration of the central purpose of the test execution, explaining the functionality, business rule, functional requirement or systemic integration being validated, with the objective of making explicit the focus of the assessment in the scenario, facilitating the verification of success and the delimitation of the scope of evidence;
IV - Test Type: classification of the test as to the nature of the business flow to be validated, with the objective of ensuring that both normal paths and expected rejection conditions are contemplated in the tests, and may take the following modalities:
a) Expected Flow (Success): Process executed according to the regular and expected path; and
b) Expected Error Flow (Controlled Failure): Process conducted in order to reproduce rejection or blocking conditions provided for in the business rules;
V - Profile of participants involved: list of all participants who interact with or are impacted by the scenario, with the objective of demonstrating the reach of the scenario within the ecosystem among different participant profiles;
VI - Assumptions: pre-existing conditions that must be satisfied for the valid execution of the scenario, with the objective of establishing the initial state necessary for execution, avoiding failures resulting from inadequate preparations;
VII - Form of access: description of the form of access used in the scenario, with the objective of testing the different forms of access to the System offered to the participant such as the system screens, the APIs (Application Programming Interface), the messages, the files, among others;
VIII - Systems involved: indicates whether the scenario requires interconnection tests, listing the systems impacted directly or indirectly, with the objective of demonstrating the technical scope of the scenario in relation to the systems architecture;
IX - Processes: business processes correlated to the scenario, in line with the regulations presented within the scope of the authorization process, with the objective of ensuring traceability between the test scenario and the business process provided for in the regulations;
X - Minimum standard informational content: minimum set of mandatory data necessary for the valid execution of the process, with the objective of ensuring that the test validates the completeness and conformity of the information exchanged;
XI - Procedures / Scenario steps: ordered sequence of actions for executing the test, with the objective of verifying the logical structure of the process and monitoring the execution;
XII - Success situations: conditions that characterize successful execution of the scenario, with the objective of providing clear criteria to determine approval of the test;
XIII - Failure situations: expected conditions of rejection or blocking of a process, with the objective of ensuring that the system reacts adequately to the expected error conditions;
XIV - Approval criteria: list of objective conditions for formal approval of the scenario, with the objective of providing a clear basis for the auditor to issue an opinion on approval;
XV - Opinion regarding the result: Internal Audit's assessment regarding the achievement of the expected results, in accordance with the defined approval criteria, with the objective of recording the interested party's perception regarding the result obtained;
XVI - Evidence of execution: screen prints, logs or files necessary to prove execution, with the objective of ensuring sufficient evidentiary material for subsequent analysis; and
XVII – Observations: field for recording additional relevant information, with the objective of allowing the recording of details not captured in the previous fields.” (NR)
Art. 5º Annex VII to Normative Instruction BCB no. 374, of 26 April 2023, published in the Official Gazette of the Union of 27 April 2023, shall enter into force with the following wording:
1. IDENTIFICATION
Corporate name:
CNPJ:
Acronym:
Full address:
Person responsible for conducting the request: provide name, CPF, telephone and email.
2. FORMALIZATION OF THE REQUEST
The institution qualified above, in accordance with the provisions of articles 4, item XI, and 5, item I, of the Regulation Annex to BCB Resolution no. 304, of 20 March 2023, hereby requests the Central Bank of Brazil – Department of Banking Operations and Payment System (Deban), a favorable manifestation to the proposal with a view to authorization for alteration (in the financial market system(s) and/or in its/their regulation(s)), classified under item(s) ..... of art. 21 of Normative Instruction BCB no. 374, of 26 April 2023.
3. INFORMATION RELATING TO THE REQUEST
System Name:
Short System Name:
Alterations:
4. INSTRUCTION OF THE PROCESS
4.1. Attaches, in compliance with the provisions of art. 23 of Normative Instruction BCB no. 374, of 26 April 2023, the following documents and information:
explanatory document covering the main aspects related to the intended alteration:
a) motivation (market, financial, prudential), presented extensively, for the intended alteration;
b) comparison of the current process vis-à-vis the intended one, containing flowcharts (where applicable) and concrete examples;
c) list of all IOSMF documents that must be amended due to the amendment request, followed by a brief summary of the amendments;
d) for each intended amendment classified by the IOSMF as strategic for the authorization request, an extract of the document containing that amendment and indication of the document name, except for the documents referred to in item VI of art. 23 of BCB Normative Instruction No. 374, of 26 April 2023;
e) assessment, prepared by the 2nd line of defense, of the risks associated with the amendments arising from the authorization request, also covering controls and contingencies established or intended to be established for each of the mapped risks;
f) expected schedule, focusing on the planned stages and their execution time;
analysis prepared by the IOSMF on the potential effect of the authorization request on the security and efficiency of the SMF and of the IOSMF and on the soundness and normal operation of the Brazilian Payment System or the National Financial System referred to in § 2 of art. 4 of the Regulation annexed to BCB Resolution No. 304, of 20 March 2023;
draft, with indication of the amended passages, of the SMF regulation, as set forth in Chapter II of Title V of the Regulation annexed to BCB Resolution No. 304, of 20 March 2023, with indication of the amended passages, except for documents that exclusively govern the aspects provided for: in items III, XVI and XVIII of art. 102; in item XV of art. 102 with regard to non-financial risks; and in item III of art. 104;
document attesting compliance with the provisions of art. 141 of the Regulation annexed to Resolution No. 304, of 20 March 2023 (in the case of the request referred to in item XXI of art. 21 of BCB Normative Instruction No. 374, of 26 April 2023);
other documents:(specify, if applicable)
4.2. Other information/observations:
Place and date
Name and CPF of the signatories
Note: the application must be digitally signed by administrators whose representativeness is recognized by the institution's articles of association or social contract.
When filing the authorization request with the Central Bank of Brazil, through the digital protocol, choose the Subject “SPB/IMF – Authorization and Supervision of Financial Market System” and in the "Subsubject" or "Destination" choose “Documents related to the authorization and supervision of financial risks of SMF (Deban)”.” (NR)
Art. 6 The Annex VIII to BCB Normative Instruction No. 374, of 26 April 2023, published in the Official Gazette of the Union of 27 April 2023, shall enter into force with the following wording:
1. IDENTIFICATION
Corporate name:
CNPJ:
Acronym:
Full address:
Person responsible for conducting the request: provide name, CPF, telephone and email.
2. FORMALIZATION OF THE REQUEST
The institution qualified above, in accordance with the provisions of articles 4, item XI, and 5, item II, of the Regulation Annexed to BCB Resolution No. 304, of 20 March 2023, hereby requests the Central Bank of Brazil – Department of Banking Operations and Payment System (Deban), authorization for amendment (in the financial market system(s) and/or in its/their regulation(s)), considering that the proposal approved in Phase 1 has already been implemented.
3. INFORMATION RELATING TO THE REQUEST
System Name:
Short System Name:
Amendments:
4.1. Attached, in compliance with the provisions of art. 24 of BCB Normative Instruction No. 374, of 26 April 2023, the following documents and information:
production implementation plan, including description of the strategy for implementing the systems (preliminary procedures, change to production environment, rollback forecast, support to participants, etc.);
functional test report, assured by Internal Audit, in accordance with the provisions of Annex VI of BCB Normative Instruction No. 374, of 26 April 2023;
certification or homologation plan with the participants;
other documents:(specify, if applicable)
4.2. Other information/observations:
Place and date
Name and CPF of the signatories
Note: the application must be digitally signed by administrators whose representativeness is recognized by the institution's articles of association or social contract.” (NR)
Art. 7 Annex IX to BCB Normative Instruction No. 374, of 26 April 2023, published in the Official Gazette of the Union of 27 April 2023, shall enter into force with the following wording:
THESE DOCUMENTS SHALL ONLY BE SENT UPON SPECIFIC REQUEST FROM THE CENTRAL BANK OF BRAZIL
1. explanatory document covering the main aspects related to the intended amendment:
1.1. comparison of the current process with the intended one, containing flowcharts (where applicable) and concrete examples;
1.2. list of all IOSMF documents that must be amended due to the authorization request, followed by a brief summary of the amendments;
1.3. for each intended amendment classified by the IOSMF as strategic for the authorization request, an extract of the document containing that amendment and indication of the document name, except for the documents referred to in item 5;
1.4. assessment, to be prepared by the second line of defense, of the risks associated with the amendments arising from the authorization request, also covering controls and contingencies established or intended to be established for each of the mapped risks; and
1.5. expected schedule, focusing on the planned stages and their execution time;
2. analysis prepared by the IOSMF on the potential effect of the authorization request on the safety and efficiency of the SMF and the IOSMF and on the soundness and normal operation of the Brazilian Payment System (SPB) or the National Financial System (SFN) referred to in § 2 of art. 4 of the Regulation annexed to BCB Resolution No. 304, of 2023;
3. documentation that extensively presents the intended interconnection model;
4. contractual instruments or equivalents signed between the IOSMF and other IOSMF, foreign central counterparties, entities administering organized markets or settlement institutions;
5. draft, with indication of the amended sections, of the new SMF regulation, as set forth in Chapter II of Title V of the Regulation annexed to BCB Resolution No. 304, of 2023.” (NR)
Art. 8 The following provisions of BCB Normative Instruction No. 374, of 26 April 2023, published in the Official Gazette of the Union of 27 April 2023, are revoked:
I - art. 5, caput, item VII;
II - art. 5, sole paragraph, item III;
III - art. 6, § 3;
IV - art. 7, caput, item VIII;
V - art. 7, sole paragraph, item III;
VI - art. 9, caput, item VIII;
VII - art. 9, sole paragraph, item III;
VIII - art. 21, caput, items II and III;
IX - art. 23, caput, items IV, V and VIII;
X - art. 24, caput, item II;
XI - Annex IV.
Art. 9 The provisions of this Normative Instruction apply to requests filed with the Central Bank of Brazil as from the entry into force of this Normative Instruction.
Art. 10 This Normative Instruction enters into force on the date of its publication. Carolina Pancotto Bohrer Fábio Martins Trajano de Arruda Head of Deorf Head of Deban
This BCB Normative Instruction (IN BCB) aims to amend BCB Normative Instruction No. 374, of 26 April 2023, in order to simplify and provide greater transparency to the processing of requests, with emphasis on:
a) simplified processing for authorization requests for new interconnections, without prejudice to additional documents being requested, if necessary;
b) detailing of the minimum content of documents as annexes to the IN for better clarity of what must be submitted by interested parties in the processing of the request;
c) separation of the processing of authorization requests within the exclusive competence of Deban or Deorf into different articles;
d) separation of the processing of the authorization request for contracting relevant processing, storage and cloud computing services provided abroad, which will be the subject of a specific IN, within the exclusive competence of Desuc.
2. Decree No. 10.411, of 30 June 2020, regulates the carrying out of regulatory impact analysis (RIA) as a prerequisite for the issuance of a normative act. However, in its article 4, the aforementioned decree establishes the hypotheses for waiving the carrying out of RIA. This BCB IN falls within the hypothesis provided for in item II, as it does not bring any additional requirement to that contained in the current regulation and is intended to clarify the manner of complying with obligations defined in a hierarchically superior norm. Thus, based on item II of art. 4 of Decree No. 10.411, of 2020, we understand that the issuance of this BCB IN waives the carrying out of RIA. Carolina Pancotto Bohrer Fábio Martins Trajano de Arruda Head of Deorf Head of Deban
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.
RegAlert holds no document that amends or replaces this one. This is not a check that it is in force: confirm with the regulator.
“Art. 1 BCB Normative Instruction No. 374, of 26 April 2023, published in the Official Gazette of the Union of 27 April 2023, shall come into force with the following amendments”
“based on arts. 4, § 1, and 6 of BCB Resolution No. 304, of 20 March 2023”
“annexed to BCB Resolution No. 340, of 21 September 2023”
This document amends: Normative Instruction BCB No. 374 of April 26, 2023
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 checked by an AI reviewer before publication; the authoritative text is the regulator's original document. How RegAlert works
In RegAlert: added