Circular CONAU 1-1679 RUNOR 1-1903: Modifications to the Monthly Accounting Information Regime for Forward Operations (R.I. - O.T.)

"Year of the Reconstruction of the Argentine Nation" COMMUNICATION “A” 8258 12/06/2025 TO FINANCIAL ENTITIES:
Ref.: Circular CONAU 1-1679, RUNOR 1-1903:
Monthly Accounting Information Regime for "Forward Operations" (R.I. - O.T.) Modifications.
___________________________________________________________________________ We address you to inform you of the adjustments made to the aforementioned Information Regime as a result of the merger of entities Mercado Abierto Electrónico S.A. and Matba Rofex S.A. into the continuing company A3 Mercados S.A. In this regard, the entities Rofex, MAE, and Matba were removed, and entity A3 Mercados was incorporated into the "Trading Venue or Counterparty" data field. The incorporated modifications will be effective for information corresponding to the statistical week from June 8 to 15 inclusive, with a due date of 17/06/25. The sheets to be replaced in the respective Ordered Texts are attached. We salute you attentively. CENTRAL BANK OF THE ARGENTINE REPUBLIC Rodrigo J. Danessa Estela M. del Pino Suárez Chief Manager of Information Regime and Information Centers Deputy General Manager of Information Regime and Protection for Users of Financial Services
APPENDIX

Particular Instructions
Forward purchases and sales, as well as foreign currency options, shall be reported by identifying the execution date of each operation, the trading venue or counterparty, and the maturity of the operation. Movements shall be reported by aggregating the operations of each day of the statistical week that share the requested attributes. As the quantity of underlying asset, the amount in the currency corresponding to that asset shall be reported. Operations terminated or exercised prior to the maturity date shall be reported as Reductions (Bajas). For operations without a fixed maturity, their Reduction shall always be reported upon cancellation. Currency swap operations shall be reported by disaggregating the transaction into as many forward operations as payments have been agreed upon. In cases where the trading venue in which the operation is executed is BCBA-INDOL, DOMAY, BYMA and A3 Mercados, the counterparty tax identification and denomination fields shall not be reported. B.C.R.A. MONTHLY ACCOUNTING INFORMATION REGIME 15 – FORWARD OPERATIONS Version: 8th COMMUNICATION “A” 8258 Validity:
13/06/2025 Page 2

Requested Data

1. Execution date of the operation
2. Type of operation
   2.1. Forward operation with maturity
   2.2. Call option
   2.3. Put option
   2.4. Forward operation without maturity
3. Trading Venue or Counterparty
   3.1. BCBA - INDOL
   3.4. DOMAY
   3.5. Residents in the Country – Financial Sector
   3.6. Residents in the Country – Non-Financial Sector
   3.7. Residents abroad – Self-regulated markets
   3.8. Residents abroad – Others
   3.10. BYMA
   3.11. A3 Mercados
4. Tax identification of the operation's counterparty
   4.1. Unique Tax Identification Key Number (C.U.I.T.)
5. Name of the operation's counterparty
   5.1. Surname and first name or corporate name or designation, in full, as applicable.
6. Underlying Asset
   6.1. Foreign Currency
7. Underlying Asset Currency: SWIFT code
8. Settlement Currency: SWIFT code
9. Maturity date
10. Quantity of underlying asset
    B.C.R.A. MONTHLY ACCOUNTING INFORMATION REGIME 15 – FORWARD OPERATIONS Version: 8th COMMUNICATION “A” 8258 Validity:
    13/06/2025 Page 3

22.2. Particular instructions.
22.2.1.Field 4 “Type of operation” shall be completed with the following codes:
1: Forward operation with maturity.
2: Call option.
3: Put option.
4: Forward operation without maturity.
22.2.2.Field 5 “Trading venue or counterparty” shall be completed with the following codes:
01: BCBA – INDOL
04: DOMAY
05: Residents in the country – Financial sector 06: Residents in the country – Non-financial sector 07: Residents abroad – Self-regulated markets 08: Residents abroad – Others 10: BYMA 11: A3 Mercados
22.2.3. Field 6 “Underlying asset” shall be completed in all cases with code 1 (Foreign currency).
22.2.4. Field 10 “Settlement” shall be completed with the following codes:
1: Daily in cash (differences)
2: At maturity in cash (differences)
3: With delivery
9: Other
22.2.5. Field 11 “Concept” shall be completed with the following codes:
1: Purchase increase (Addition)
2: Purchase decrease (Reduction)
3: Sale increase (Addition)
4: Sale decrease (Reduction)
22.2.6. The date to be recorded in field 14 “Execution date of the operation” must correspond to a date within the reported statistical week, according to the date recorded in field 3.
B.C.R.A. SUBMISSION OF INFORMATION TO THE CENTRAL BANK
Section 22. Forward Operations.
Version: 8th COMMUNICATION “A” 8258 Validity:
13/06/2025 Page 2

22.2.7. Field 15 “Counterparty identification number” shall be mandatory for integration when dealing with futures operations executed in unregulated markets, and shall be completed according to the following scheme:

• If reported in field 5, codes 05, 06 or 11, the CUIT number shall be recorded in this field.
• If reported in field 5, codes 07 or 08, the identification number shall be reported as follows:
• The first five digits will record the reporting entity's code, which is the number of the current account opened at this Institution;
• The next two will include the characters corresponding to the residence country code of individuals or legal entities based abroad, according to SWIFT Country Codes codification;
• The remaining four digits will use a single sequential number for each of them, whose last three positions must match those assigned when the three-digit numeric country code was used as provided in the countries and territories codification disseminated by Communication “A” 3147.
• In the remaining cases, it shall be integrated with zeros.
  22.2.8. Field 16 “Counterparty name” shall only be integrated when codes 05 to 08 or 11 have been recorded in field 5.
  It shall not contain tab characters or quotation marks. It shall be generated in uppercase letters without accents. The newline character (Enter) used as a record separator and the semicolon (;) representing the field delimiter shall not be used in these fields.
  22.2.9. Movements shall be reported by aggregating, in Quantity of underlying asset (field 12) and Agreed amount of the operation in settlement currency (field 13), the operations of each day (field 14) that share the following attributes: Type of operation (field 4), Trading venue or counterparty (field 5) or Counterparty identification number (field 15), Underlying asset (field 6), Underlying asset currency (field 7), Settlement currency (field 8), Maturity date (field 9), Settlement (field 10) and Concept (field 11).
  22.3. Information validation.
  The lists corresponding to the results of the validation processes will be available on the secure site https://www3.bcra.gob.ar.
  22.4. Record design
  B.C.R.A. SUBMISSION OF INFORMATION TO THE CENTRAL BANK
  Section 22. Forward Operations.
  Code Legend Cause
  11 INFORMATION ALREADY SUBMITTED AND ACCEPTED | Information submitted corresponds to an information date already validated. 12 CORRECTION FIELD INCORRECTLY REPORTED | The Correction field only accepts the characters “N” and “R”. 13 INCORRECTLY ENTERED CORRECTION | Corrective information submitted corresponds to an unvalidated period. 14 DUPLICATE RECORD | More than one record reported for the same execution date of the operation (field 14) with identical combination of fields: Type of operation (field 4), Trading venue or counterparty (field 5), Counterparty identification number (field 15), underlying asset (field 6), Underlying asset currency (field 7), Settlement currency (field 8), Maturity date (field 9), Settlement (field 10) and Concept (field 11). 15 INCORRECT EXECUTION DATE OF THE OPERATION (FIELD 14) | It is a date:
• non-existent (e.g., 2002-13-35),
• contains non-numeric characters,
• completed with all zeros,
• does not correspond to a date within the reported statistical week, or
• does not respect the format YYYY-MM-DD)
  16 INCORRECTLY REPORTED IDENTIFICATION NUMBER (FIELD 15) | - Having reported in field 5 codes 05, 06 or 11, the identification number reported in this field does not correspond to a valid Unique Tax Identification Key (CUIT), or
• Having reported in field 5 codes 07 or 08, this field was integrated with zeros, or
• For the remaining codes of field 5, this field was not integrated with zeros.
  17 INCORRECTLY REPORTED COUNTERPARTY NAME (FIELD 16) | Having reported in field 5 codes 05 to 08 or 11:
• the reported name contains one or more non-allowed characters, or
• this field was integrated with blanks.
  Version: 3rd COMMUNICATION “A” 8258 Validity:
  13/06/2025 Page 7