Regulatory Alerts2026-04-28 | A 8430Circular RUNOR 1-1958: Prevention of Money Laundering, Terrorist Financing and Other Illicit Activities. Modifications.
The Central Bank of the Argentine Republic issued Communication A 8430 to update Section 8 of its Information Regime (Circular RUNOR 1-1958) by modifying Suspicious Transaction Report designs 2404 and 2405, extending field lengths, adjusting error controls, and introducing new mandatory technical self-assessment and independent auditor reports for non-financial credit providers and payment service providers. Financial entities must now submit updated ROS.TXT and DESCROS.TXT files with corrected typology codes, null-value handling for incomplete fields, and strict correspondence between record designs, while non-financial providers are required to transmit PDF-based risk tolerance declarations and annual auditor reports via the MFT service using specific regime codes. The circular enforces validation error tables, mandates null values (“;;”) for missing typology data, and prohibits the “OPERA=FALSE” option to ensure comprehensive anti-money laundering and counter-terrorist financing compliance across all designated entities.
2026 - YEAR OF ARGENTINE GREATNESS COMMUNICATION “A” 8430 28/04/2026 TO FINANCIAL ENTITIES, TO NON-FINANCIAL CREDIT CARD ISSUERS, TO NON-FINANCIAL PURCHASE CARD ISSUERS, TO OTHER NON-FINANCIAL CREDIT PROVIDERS, TO PAYMENT SERVICE PROVIDERS: Ref.: Circular RUNOR 1-1958: Prevention of Money Laundering, Terrorist Financing and Other Illicit Activities. Modifications.
We address you to provide the pages that should be replaced in the consolidated text of Section 8. of "Submission of Information to the Central Bank" related to the provisions disseminated through Communication A 8429. In this regard, the following modifications are highlighted: 8.1. Suspicious Transaction Report (STR)
- Adjustment of points 8.1.1.1., 8.1.1.3. and 8.1.2.2. and of controls 05, 06, 07, 13, 14 and 15.
- Extension of the length of the "Activity Type" field and adjustment of the denomination of field 7 "Product where the unusualness was recorded" in record design 2405. Additionally, the following sections are incorporated: 8.3. Technical report on risk self-assessment of AML/CFT and its methodology, and risk tolerance declaration - Non-Financial Credit Providers and Payment Service Providers. 8.4. Annual report of the independent external auditor - Non-Financial Credit Providers and Payment Service Providers.
-2- We respectfully greet you. CENTRAL BANK OF THE ARGENTINE REPUBLIC Mariana A. Diaz Rodrigo J. Danessa Signature 2 Manager of Information Regime Senior Manager of Information Regime and Information Centralizations Functional Position ANEXO
8.1. Suspicious Transaction Report (STR) (only Financial Entities). 8.1.1. General instructions. 8.1.1.1. The information will be sent in two files named "ROS.TXT" and “DESCROS.TXT”, which will contain the data according to the record designs as per the models inserted in point 8.1.3, which must be recorded in accordance with what is provided in point 1.2.3.1 of Section 1. Submission of information to the Central Bank. For the identification of this regime, 00005 will be used for the regime code and 00003 for the requirement code. 8.1.1.2. Entities will employ all means within their reach to ensure the quality of the data to be reported. 8.1.1.3. Those entities that have not registered operations in any of the months of the quarter to be reported under the provisions of this Information Regime must proceed as indicated in Section 1. Submission of information to the Central Bank, according to what is provided in point 1.2.3.1. 8.1.1.4. The information will be submitted with the following scheme: • Design 2404: In one record, the data corresponding to "Total reports submitted" and "Total amount reported" (header record) will be reported, and in the remaining ones, the Typology codes that have been reported in the quarter under report. Consequently, the header record will be integrated as follows: field 4 will be completed with zero, and fields 5 and 6 with the data corresponding to the reported totals. In the subsequent records (as many as Typology codes need to be reported), fields 5 and 6 will not be integrated, and field 4 with the reported categorization codes. • Design 2405: At least one record will be reported for each of the typologies informed in field 4 of design 2404, containing the data required in the PN. B.C.R.A. SUBMISSION OF INFORMATION TO THE CENTRAL BANK Section 8. Prevention of Money Laundering, Terrorist Financing and Other Illicit Activities. Version: 7th COMMUNICATION “A” 8430 Validity: 31/03/2026 Page 1
8.1.2. Particular instructions. 8.1.2.1. Design 2404. When applicable, according to what is indicated in point 8.1.1.4., the "Reported Typology" field will be completed as indicated in 3.7. of the PN. 8.1.2.2. Design 2405. The data will be grouped in the same record when there is a match in all requested attributes. Up to three typology codes will be allowed when the characteristics of the operation so require. In cases where not all fields provided to report a code corresponding to the Reported Typology Table (fields 9 to 11) are completed, it will be reported with a null value (“;;”). B.C.R.A. SUBMISSION OF INFORMATION TO THE CENTRAL BANK Section 8. Prevention of Money Laundering, Terrorist Financing and Other Illicit Activities. Version: 7th COMMUNICATION “A” 8430 Validity: 31/03/2026 Page 2
B.C.R.A. SUBMISSION OF INFORMATION TO THE CENTRAL BANK Section 8. Prevention of Money Laundering, Terrorist Financing and Other Illicit Activities. Title: Detail of suspicious transactions - Description of typologies. Sheet 1 of 1 No. Field Name Max Length (1) Observations 1 Design Code Numeric 4 Constant 2405. 2 Entity Code Numeric 5 (2) 3 Information Date Numeric 6 YYYYMM. 4 Person Type Numeric 4 According to point 3.2. of the PN. 5 PEP Status Numeric 1 1 = Not a PEP. 2 = Is a PEP. Point 3.3. of the PN. 6 Activity Type Numeric 6 According to point 3.4. of the PN. 7 Product where the unusualness was recorded Numeric 2 According to point 3.5. of the PN. 8 Geographic Region Numeric 2 According to point 3.6. of the PN. 9 Reported Typology 1 Numeric 2 According to point 3.7. of the PN. 10 Reported Typology 2 Numeric 2 According to point 3.7. of the PN. 11 Reported Typology 3 Numeric 2 According to point 3.7. of the PN. 12 Rectification Character 1 Enter "R" in case of rectification; otherwise enter "N". (1) The delimiter ";" must be used as a field separator. (2) The entity code will be that of the peso current account opened at the Central Bank. PN: Procedural Norms of this regime. Version: 9th COMMUNICATION “A” 8430 Validity: 31/03/2026 Page 4
8.1.5. Error legends/messages. 8.1.5.1. Applicable to all record designs. B.C.R.A. SUBMISSION OF INFORMATION TO THE CENTRAL BANK Section 8. Prevention of Money Laundering, Terrorist Financing and Other Illicit Activities. Code Legend/Message Cause 01 FILE "ROS.TXT" NOT FOUND The reference file was omitted from recording, or its design does not correspond to 2404, or it is empty. 02 INCORRECT RECORD LENGTH The recording of records was not carried out according to the corresponding designs. 03 INCORRECTLY REPORTED ENTITY The reported entity code is incorrect. 04 INCORRECT INFORMATION DATE It is an existing date (e.g., 200113), contains non-numeric characters, or the information corresponds to a period not enabled for processing. 05 DUPLICATE RECORD Design 2404: - More than one record was reported with identical data in the "Reported Typology" field, or - More than one record was reported with data in fields "Total reports submitted" and/or "Total amount reported". Design 2405: - More than one record was reported with identical data in fields 4 to 11. 08 INCORRECTLY FORMED BATCH Only one record was sent in design 2404. Version: 8th COMMUNICATION “A” 8430 Validity: 31/03/2026 Page 6
B.C.R.A. SUBMISSION OF INFORMATION TO THE CENTRAL BANK Section 8. Prevention of Money Laundering, Terrorist Financing and Other Illicit Activities. Code Legend/Message Cause 09 INCORRECTLY ENTERED RECTIFICATION FIELD The Rectification field of the mentioned design only accepts the characters "N" and "R". 10 INCORRECTLY SUBMITTED RECTIFICATION Rectification information was submitted corresponding to an unvalidated period. 11 INFORMATION ALREADY SUBMITTED AND ACCEPTED Information already validated was submitted, having completed the Rectification field with "N". 12 FILE "DESCROS.TXT" NOT FOUND The reference file was omitted from recording, or its design does not correspond to 2405, or it is empty. 13 LACK OF CORRESPONDENCE BETWEEN DESIGNS 2404 and 2405 - Having reported a "typology" code in the "Reported Typology" field of design 2404, at least one record with the same code was omitted from recording in any of fields 9 to 11 of design 2405, or - A record was recorded in design 2405 (fields 9 to 11), for a typology code not reported in the "Reported Typology" field of design 2404. 14 INCORRECT CODE FIELD The reported code does not correspond to any of the existing ones (applicable to the "Reported Typology" field of design 2404 and to fields 4 to 11 of design 2405). Version: 7th COMMUNICATION “A” 8430 Validity: 31/03/2026 Page 7
8.1.5.2. Applicable to design 2404. B.C.R.A. SUBMISSION OF INFORMATION TO THE CENTRAL BANK Section 8. Prevention of Money Laundering, Terrorist Financing and Other Illicit Activities. Code Legend/Message Cause 06 INCORRECTLY REPORTED "TOTAL REPORTS SUBMITTED" AND/OR "TOTAL AMOUNT REPORTED" FIELDS - Header record: the mentioned field/s contains/contain blanks, non-numeric characters, or all zeros. - Remaining records: in the mentioned field/s, the procedure was not followed according to what is indicated in the penultimate item of point 8.1.1.4. 07 INCORRECTLY REPORTED "REPORTED TYPOLOGY" FIELD - Header record: the mentioned field was not integrated with zeros. - Remaining records: the "Reported Typology" field was not completed with a planned code, as established in point 3.7. of the PN. Version: 7th COMMUNICATION “A” 8430 Validity: 31/03/2026 Page 8
8.1.5.3