2025-10-13 | A 8340

Circular RUNOR 1-1926 Informational Regime – Rejected and Reported Checks

The Central Bank of the Argentine Republic (BCRA) issues Circular RUNOR 1-1926 to mandate financial entities implement an automated informational regime for rejected and reported checks, effective for data corresponding to October 15, 2025. The circular establishes precise field mappings, mandatory validation rules, and operational cost structures for new registrations, modifications, corrections, and deregistrations. It further defines specific automation protocols for linkage, unlinkage, review status updates, and fine/interest collection mechanisms within the .txt reporting files.

Banco Central de la Republica Argentina logo

Argentina

Banco Central de la Republica Argentina

Click to view thumbnail

"Year of the Reconstruction of the Argentine Nation" COMMUNICATION “A” 8340 13/10/2025 TO FINANCIAL ENTITIES: Ref.: Circular RUNOR 1-1926: Informational Regime – Rejected and Reported Checks.


We address you regarding the aforementioned informational regime in light of the issuance of Communication A 8299. In this regard, we provide the sheets to be replaced in the consolidated text regarding Section 41. Submission of Information to the Central Bank. These instructions shall apply starting from the information corresponding to October 15, 2025. Yours faithfully, CENTRAL BANK OF THE ARGENTINE REPUBLIC Gustavo O. Bricchi Estela M. del Pino Suárez Manager of Information Management Deputy General Manager of Informational Regime and Protection of Financial Services Users ANNEX: 8 Sheets

  1. Particular Instructions 2.1. Automation of new registrations, modifications, and corrections for rejected or reported checks (according to the design inserted in point 3.1 of these instructions): 2.1.1. A rejected or reported check will be initially registered (new registrations), and subsequently, specific data may be incorporated into it only once (modification). This latter alternative is restricted exclusively to the following items for rejected checks: check payment date, fine payment date, and account closure date. For reported checks, only the presentation for collection or registration date may be modified. 2.1.2. When it is necessary to correct a previously reported data point via an initial registration, modification, or prior correction for rejected and reported checks, the design must be completed by filling field 6 with R for rejected checks and N for reported checks. This alternative is restricted to the following items for rejected checks: notice year, notice number, notification date, cause, original currency amount, rejection date, registration date, check payment date, fine payment date, and account closure date. For reported checks, it is restricted to the following items: notice year, notice number, reporting date, cause, presentation for collection or registration date. These movements generate operational expenses exclusively for rejected checks (point 6.4.7.3 of the Bank Current Account Regulations). 2.1.3. It should be clarified that the system does not allow modifying or correcting fields related to check identification (Entity Code, Branch Number, Account Number and/or Check Number), nor the Currency Code field, nor the Check Type field. Therefore, if correction is necessary, the record of the incorrectly identified check must be deregistered using reason code B 33, followed by a new registration with the correct data. 2.1.4. New registrations must necessarily include the following data: i) Rejected checks: Entity Code, Branch Number, Account Number, Check Number, notice year and number, movement code, registration class, notification date, cause (1, 2 or 3), currency code, original currency amount, rejection date, check type, CUIT, CUIL, or CDI number. At least one individual tax identification key must always be registered. ii) Reported checks: Entity Code, Branch Number, Account Number, Check Number, notice year and number, movement code, registration class, reporting date, cause (6, 7 or 8), CUIT, CUIL, or CDI number. At least one individual tax identification key must always be registered.

B.C.R.A. SUBMISSION OF INFORMATION TO THE CENTRAL BANK Section 41. Rejected and Reported Checks. Operational Guide Version: 4th COMMUNICATION “A” 8340 Validity: 15/10/2025 Page 5

2.1.9. Notification date / Reporting date (Field No. 8) It is mandatory to integrate when entering new registrations. For rejected checks, the notification date will be used to calculate the deadline for paying the fine and subsequent disqualification for non-payment. For reported checks, the reporting date established in points 7.2.2 or 7.2.3 of the Bank Current Account Regulations will be used as the reporting date. 2.1.10. Cause (Field No. 9) Enter 1 when it refers to rejection due to lack of funds. Enter 2 when it refers to rejection due to formal reasons. Enter 3 when it refers to rejection due to lack of funds and formal reasons. Enter 6 when it refers to a check reported by the holder. Enter 7 when it refers to a check reported by the bank. Enter 8 when it refers to a check reported by a third party. 2.1.11. Currency Code (Field No. 10) Enter the currency code corresponding to pesos (80) or US dollar (02). When reporting reported checks, it will be integrated with zeros. 2.1.12. Original currency amount (Field No. 11) It will be reported in pesos without including periods or commas to separate thousands and/or decimals. It will be reported in dollars without including periods or commas to separate thousands and/or decimals in the case of ECHEQ in US dollars. 2.1.13. Rejection date / Presentation for collection or registration date (Field No. 12) Must be integrated in new registrations with the check rejection date. In the case of reported checks, complete with the presentation for collection or registration date when entering a new registration, modification, or correction. 2.1.14. Registration date (Field No. 13) Integrate exclusively for deferred rejected checks; if not applicable, integrate with zeros. 2.1.15. Absorbed entity code (Field No. 14) In the case of mergers, field 14 will be completed with the code of the absorbed entity; otherwise, it will be completed with zeros. 2.1.16. Check payment date (Field No. 15) Integrate in those cases where the drawer has paid the amount of the rejected check.

B.C.R.A. SUBMISSION OF INFORMATION TO THE CENTRAL BANK Section 41. Rejected and Reported Checks. Operational Guide Version: 5th COMMUNICATION “A” 8340 Validity: 15/10/2025 Page 7

2.1.17. Check type (Field No. 16) Complete with 00000001 in the case of rejected ECHEQ and with 00000000 in the remaining cases. 2.1.18. Fine payment date (Field No. 17) Integrate the date on which the corresponding fine amount was debited from the current account, regardless of whether funds were deposited by the client or provided by the bank through a transitional agreement, or if payment was verified by any other freely agreed means. 2.1.19. Account closure date (Field No. 18 of the design) Integrate in those cases where the entity has decided to close the account of the drawer of the rejected check. 2.