Rule · BCRA · 22 Sep 1999 · A 2994
Financial institutions must, from 01/10/99, obtain reliable account-holder authorization for direct debits, with the current adhesion procedure remaining until that date. Originating Companies send the first debit order to adhere the account holder; Receiving Entities may reverse it within 30 days of clearing, after which debits are firm, and must update master files. Receiving Entities must send adhesion information via the Electronic Chamber in the presented session by the defined deadline, and originating Entities must report adhesion rejections within 10 business days. Entities must report change rejections within 10 business days.
1999 - Year of Export
COMMUNICATION "A" 2994
22/09/99
TO THE FINANCIAL INSTITUTIONS:
Ref: Circular
CAMCO 1 - 132
National Payment System. Instructions for the electronic clearing of Direct De- bits. Modifications.
We address you to inform you of the following modifications to the operating instructions for the electronic clearing of Direct Debits, incorporated into Communication "A" 2559:
Point 3.1.2.1.1 "Adhesion through the Originating Company"
Point 3.1.8.4.1. "Definition of Adhesion Registrations"
Point 3.1.8.5.1. "Definition of Adhesion Rejection"
Point 3.1.8.5.2. "Operating instructions for Adhesion Rejection"
We greet you very attentively.
CENTRAL BANK OF THE ARGENTINE REPUBLIC
Héctor O. Biondo
Deputy General Manager of
Operations
Alejandro L. Saravia
Deputy General Manager of
Information Technology and Organization
• .
B.C.R.A. DIRECT DEBITS
Section 3. Operating Instructions
-
Name of the Holder of the account to be debited
Identity Document of the account holder
Complete Uniform Banking Code (CBU)
Account number to be debited
Customer identification code defined by the company
When adhesions to the service occur at the Company or Customer, the procedure will be as follows:
The company must obtain reliable authorization from the account holder for direct debits to be executed against it.
The company must obtain the above-mentioned data
The company will send the Originating Entity the first debit order with which the account holder will automatically be adhered to the system.
The Receiving Entity may reverse, at the customer's request, the first debit order sent by the Originating Entity, within 30 days from the date of its clearing. If the first debit order is not reversed within said period, this and subsequent debits will be considered firm.
The Receiving Entity will update its master files upon receipt of the debit order.
The Originating Company or Customer must ensure that customer authorizations are available in the event that they are required.
This procedure will be in effect from 01/10/99, with the current system adhesion procedure remaining in effect until that date.
When adhesions to the service occur at the Receiving Entity, the procedure will be as follows:
The Receiving Entity must obtain authorization from the account holder for direct debits to be executed against it.
The Receiving Entity must obtain the aforementioned data
B.C.R.A. DIRECT DEBITS
Section 3. Operating Instructions
If the Receiving Entity sends said reversals outside the term just indicated, the Originating Entity may reject said transmissions alleging the corresponding reason.
The Adhesion Registration is a message that will be used between the Originating Companies or Customers and the Receiving Entities to communicate to each other the adhesion of customers to the direct debit system. These messages will be transported through the clearing system as follows:
From the Receiving Entity to the Electronic Chamber, which processes it and sends it to the Originating Entity who, in turn, forwards it to the Originating Company or Customer.
In case of adhesion through the Originating Company, there is no adhesion registration message, taking as such the sending of the first debit order to the Receiving Entity.
The receiving Entity shall send this information to the originating Entity, via the Electronic Chamber, in the presented session, by the defined deadline, and in files whose structure, content and format are detailed in the chapters "Messages" and "Record Design". These messages shall be of an informative type, and shall have no accounting effect in the Chamber's processing.
In the case of registration of adhesion through the receiving Entity, the Rejection of Adhesion is a message that shall be used by the originating Entity to communicate to the receiving Entity those Adhesion Registrations that the originating Company or Customer has rejected. These messages are transported through the clearing system, starting from the originating Entity, being processed by the Chamber and received by the receiving Entity.
In the case of registration of adhesion through the receiving Entity, the originating Entity shall send to the receiving Entity the rejections of adhesions of the originating Company, via the Electronic Chamber, in the rejected session, by the defined deadline, and in files whose structure, content and format are detailed in the chapters "Messages" and "Record Design". The originating Entity shall report a rejection of adhesion to the receiving Entity within 10 business days of the adhesion being reported.
These messages shall be of an informative type, and shall have no accounting effect in the Chamber's processing.
B.C.R.A. DIRECT DEBITS
Section 3. Operating Instructions
When changes occur in the identification key of any customer adhered to direct debits in an originating Company, it shall inform the affected originating Entities of said modifications so that they inform the receiving Entities, so that the latter updates its master file of adherents, and thus, thereafter, correctly charges the debits received and minimizes the number of rejections that could occur.
This communication shall occur by means of the sending by the originating Entity of a file to the Electronic Chamber in the presented session. These messages shall be of an informative type, so the Chamber shall not take them into account in the clearing. The receiving Entity shall proceed, upon receipt of said message, to update its master files of adherents.
The changes (Change notifications and Cancellations) may be rejected by the Entities in case said messages have erroneous data or other reasons that do not allow their proper processing.
The Entities shall send the information of rejections of changes, via the electronic Chamber, in the presented session, by the defined deadline, and in files whose structure, content and format are detailed in the chapters "Messages" and "Record Design". These messages shall be of an informative type, and shall have no accounting effect in the Chamber's processing.
The Entities shall report the rejections of changes within 10 business days of the original change or cancellation notifications being reported.
| Code | Description | Explanation |
|---|---|---|
| R18 | Erroneous clearing date | This rejection code shall be used by the Banks when the clearing date does not match the deadlines defined for each product. This rejection code shall be used by the Chamber associated with the following reasons: Rejection date does not match original transaction date, Batch clearing date exceeds allowed limit, rejection date different from process date, clearing date prior to allowed |
| R19 | Erroneous amount | This code shall be used by the Banks when a reversal falls on a debit whose amount does not match. This rejection code shall be used by the Chamber associated with the following reasons: Transaction amount must be equal to zero, non-numeric amount, invalid transaction amount, amount other than zero "0" for messages |
| R20 | Currency different from the debit account | This code shall be used by the Banks that do not accept cross transactions, when the transactions ($ or U$S) fall on accounts of a different currency. |
| R23 | Branch not enabled | This code shall be used by the Banks, when they decide to sequentially include their branches in the electronic clearing system and receive debits on any of the non-enabled branches |
| R24 | Duplicate transaction | This code shall be used by the Banks when they receive duplicate transactions |
| R25 | Error in additional record | This code shall be used by the Banks and the Chambers when a problem arises with the additional records when it is mandatory, when the presence of the additional record is indicated and it does not exist, etc. This rejection code shall be used by the Chamber associated with the following reasons: Additional record out of sequence, erroneous combination of additional records, additional record exists and is not included, required additional record not present, transaction other than rejection has additional "99" |
| R26 | Error due to mandatory field | This code shall be used by the Banks when a mandatory field is blank or has invalid characters |
| R28 | Rejection 1st. Due date | This code shall be used by the receiving Banks at the time the second due date payment modality is adopted, when a customer decides payment on the second due date or does not have funds to make the debit on the first |
| R29 | Reversal already made | This code will be used by the originating Banks when the company reports that the reversal received on a debit has already been made by it. This code will be used by the Clearing House associated with the following reason: Original transaction was rejected or reversed |
| R76 | Error in field 11 Batch header (CUIT Check Digit) | This code will be used by the Banks or the Clearing Houses when the data contained in this field is erroneous. |
| R80 | Error in field 3 additional record (Date – Record counter of the Original Debit order – Reversals) | This code will be used by the Bank when the information included in this field has been standardized and does not match the necessary data or by the Clearing Houses when no information is included in this field |
| R86 | Erroneous Company Identification | This code will be used by the Banks or by the Clearing Houses when the CUIT number reported does not match those reported in the tables |
| R90 | Transaction does not correspond, the original transaction does not exist. | This code will be used by the Banks when they receive reversals or rejections on non-existent transactions. This rejection code will be used by the Clearing House associated with the following reasons: Reversal out of time (reversal), original transaction non-existent for the rejection |
| R91 | Bank Code incompatible with transaction currency | This code will be used by the Banks when the Entity numbers are not expressed in all cases in the same currency. This rejection code will be used by the Clearing House associated with the following reason: Bank Code incompatible with transaction currency |
| R93 | Non-working day | This code will be used by those Banks that cannot process the information received for a certain branch, in whose locality there is a local holiday |
| R95 | Reversal of Receiving Entity presented out of term | This code may be used by the originating Bank in the event that the Receiving Entity presents a reversal of Receiving Bank out of the corresponding term |
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.
More like this from BCRA
BCRA published 18 documents in the last 30 days. We email you each new one the day it's published.
Source: Banco Central de la Republica Argentina — 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