Rule · BCRA · 14 Jan 2005 · A 4281
Participating financial entities must operate check clearing in accordance with defined standards, transmitting electronic files to Electronic Clearing Chambers (CECs) during two daily sessions. Depositing entities must present truncated checks and adjustments by defined deadlines, while drawee entities must execute electronic controls and debit client accounts based exclusively on received electronic data. Rejections must be processed within one business day, with specific protocols for emergency situations and physical document returns. Entities must adhere to local holiday schedules and maintain records of certified checks, ensuring compliance with BCRA regulations for all electronic exchanges.
BANCO CENTRAL DE LA REPÚBLICA ARGENTINA
COMUNICACIÓN “A“ 4281 14/01/2005
TO FINANCIAL ENTITIES:
Ref.: Circular
SINAP 1 - 4
Organized Text on the National Payments System - Operational Instructions - Checks ______ We address you to accompany you, in attachments, the organized text corresponding to the operational instructions that must be observed in order to electronically compensate, through the Clearing Chambers referred to in Communication "A" 2557 and complementary ones, the instrument CHECK. We salute you very attentively. BANCO CENTRAL DE LA REPUBLICA ARGENTINA Nicolás Delle Grazie Julio C. Siri Submanager of Payment Systems Manager of Payment System and Operations
ANEXO
B.C.R.A.
Annex to
Com. “A”
4281
-1-
Section 1: Introduction.
Section 2: Definition and characteristics of the system.
2.1. Objectives.
2.2. Participating entities.
2.3. Documents.
2.4. Scope of application.
Section 3: Operational instructions.
3.1. Electronic clearing of checks.
3.2. Particular aspects of truncated check clearing.
3.3. Particular aspects of non-truncated check clearing.
Section 4: Responsibilities of participants.
4.1. Of the depositing entity.
4.2. Of the Electronic Chambers.
4.3. Of the drawee entity.
Section 5: Controls to be performed.
5.1. By the Electronic Chambers.
5.2. By the entities.
Section 6: Transactions and messages.
6.1. Introduction.
6.2. File structure.
Section 7: Record design.
7.1. File header.
7.2. Batch header.
7.3. Individual record of check presentation and adjustments.
7.4. Additional record of rejections and adjustments.
7.5. Individual record of presentation and rejection of claims
7.6. Individual record of presentation control and rejection of images.
7.7. Individual record of out-of-exchange rejections, responses to out-of-exchange rejections.
7.8. Additional record of responses to out-of-exchange rejections.
7.9. End of batch control.
7.10. End of file control.
7.11. Encoding of transactions and check messages.
NATIONAL PAYMENTS SYSTEM - CHECKS
B.C.R.A.
Section 1 - Introduction
Version: 1 COMMUNICATION “A“ 4281
Validity:
14/01/2005
NATIONAL PAYMENTS SYSTEM - CHECKS
B.C.R.A.
Section 2 - Definition and characteristics of the system
Version: 1 COMMUNICATION “A“ 4281
Validity:
14/01/2005
2. DEFINITION AND CHARACTERISTICS OF THE SYSTEM.
The system is based on the electronic clearing of information corresponding to checks, which implies the electronic exchange of transactions between originating (or depositing) and receiving (or drawee) entities through the CEC, so that:
NATIONAL PAYMENTS SYSTEM - CHECKS
B.C.R.A.
Section 2 - Definition and characteristics of the system
Version: 1 COMMUNICATION “A“ 4281
Validity:
14/01/2005 tities, direct as a full member of one or more chambers or indirect through the designation of another member entity as its representative. In the settlement phase in BCRA accounts, only the full members of each chamber will intervene. The representative entity must identify in the exchange process the documents it presents on behalf of its represented party. It will be the responsibility of participating entities to operate in accordance with the standards and formats defined by these norms for the electronic exchange of check information.
2.2.2. Participating Actors.
Electronic check clearing in general implies the participation of the following actors:
NATIONAL PAYMENTS SYSTEM - CHECKS
B.C.R.A.
Section 2 - Definition and characteristics of the system
Version: 1 COMMUNICATION “A“ 4281
Validity:
14/01/2005
They are the telecommunications elements with which participating entities carry out the emission and reception of electronic information to and from a CEC. Entities may install a Transmission Center in one or more branches, at their headquarters and/or in one or more external centers belonging to a third party that provides them with this service through an agreement. Each entity may use as many Transmission Centers as necessary to cover its entire network of branches. In the CEC that provides them service, each of these branches must be assigned to a Transmission Center, both for the emission and for the reception of information. Transmission Centers will have no effect on clearing, but will act only as points of sending and receiving files. In case the entity uses more than one Transmission Center to receive information from the CEC, the reception of the resulting net positions from the clearing coming from the latter can be carried out in the same predetermined Transmission Center.
2.2.2.4. Electronic Chambers:
They are the institutions that administer the electronic clearing of payment instruments originated by operations of clients or third parties unrelated to the financial entities. They work in free competition providing the services of clearing defined in these norms. They communicate with each other to exchange cross transactions, which allows entities to communicate only with their electronic chamber, and this one to take charge of the transactions of all entities, regardless of whether they are clients of it or not. The main functions they will perform are the following:
NATIONAL PAYMENTS SYSTEM - CHECKS
B.C.R.A.
Section 2 - Definition and characteristics of the system
Version: 1 COMMUNICATION “A“ 4281
Validity:
14/01/2005
It is the service of delivery of non-truncated checks at the established exchange point when the depositing entity does not have a branch in the place of drawee.
2.2.2.6. Exchange Point:
It is the place where the physical exchange of non-truncated checks takes place.
These exchange centers differ from the current clearing chambers in the following points:
NATIONAL PAYMENTS SYSTEM - CHECKS
B.C.R.A.
Section 2 - Definition and characteristics of the system
Version: 1 COMMUNICATION “A“ 4281
Validity:
14/01/2005
Deposited Bank Drawee Bank
NATIONAL PAYMENTS SYSTEM - CHECKS
B.C.R.A.
Section 2 - Definition and characteristics of the system
Version: 1 COMMUNICATION “A“ 4281
Validity:
14/01/2005 in electronic form. These data constitute all the information that the depositing entity makes available to the drawee entity so that it confirms/rejects its payment, without it being necessary to resort to the sending of the original document. The truncation amount will be informed through communication from the BCRA, as it increases over time.
2.3.2. Non-truncated Checks.
They are those that, by exceeding the defined truncation amount limit, in addition to being included in the information sent electronically in files, are subject to delivery of the original documents, or in the future their image, to the drawee entity. They will also be non-truncated checks the types of documents that are expressly included in the Truncation Agreement between entities.
2.3.3. Deferred Payment Checks.
Deferred payment checks (CPD) have two distinct cycles, the registration cycle and the payment cycle.
The registration cycle will not be contemplated in the clearing system, given that it is an exchange of documents between entities without money settlement. The payment cycle begins when the CPD matures. This cycle is similar to the clearing of a check, so the same rules and instructions that will govern common checks will apply.
2.3.4. Certified Checks.
These checks will be cleared in the same way as common checks, applying the same instructions and sending the same information as for these. Each drawee entity will keep a record of the checks it has certified, to be able to identify them from the electronic information it receives.
2.4. Scope of application.
Through this system, checks can be electronically cleared, regardless of their origin and destination, within the national territory. If the depositing and drawee entities operate in different CECs, it will be the responsibility of the latter to exchange transactions to ensure the complete interconnection of the system.
NATIONAL PAYMENTS SYSTEM - CHECKS
B.C.R.A.
Section 3 - Operational Instructions
Version: 1 COMMUNICATION “A“ 4281
Validity:
14/01/2005
3. OPERATIONAL INSTRUCTIONS.
In the first part of this chapter (point 3.1.) the mechanisms of presentation, clearing, communication sessions and other relevant aspects to consider are developed. In the second part (points 3.2 and 3.3) the particular aspects to consider in the clearing of truncated checks and non-truncated checks are detailed.
3.1 Electronic clearing of checks.
3.1.1 Presentation.
Entities will transmit to the CEC(s) files containing the information corresponding to the checks that said entity presents for its electronic clearing.
3.1.1.1. Transmission sessions and transactions to be presented.
Daily, two sessions will operate in which the chamber will receive files from entities:
NATIONAL PAYMENTS SYSTEM - CHECKS
B.C.R.A.
Section 3 - Operational Instructions
Version: 1 COMMUNICATION “A“ 4281
Validity:
14/01/2005
NATIONAL PAYMENTS SYSTEM - CHECKS
B.C.R.A.
Section 3 - Operational Instructions
Version: 1 COMMUNICATION “A“ 4281
Validity:
14/01/2005
NATIONAL PAYMENTS SYSTEM - CHECKS
B.C.R.A.
Section 3 - Operational Instructions
Version: 1 COMMUNICATION “A“ 4281
Validity:
14/01/2005
The Electronic Chamber (1) that receives the information from the origin entity, will calculate in the first instance the bilateral clearing movements between it and all its destination entities. Secondly, it will retransmit the detail information to the Electronic Chamber (2) of the destination entities. The Electronic Chamber (2) of the destination entities, will calculate the bilateral clearing movements between its adhering entities and the origin entity making the detail of the transactions available to each destination entity. Each Electronic Chamber will communicate the resulting bilateral movements from the clearing to its respective entities. The chambers will calculate their final inter-chamber position. The chamber that has remained in a debtor balance will pay the creditor chamber and, to finish, both Chambers must effect the settlement of the Creditor Entities Example Assuming the case where two entities were adhered to each of the chambers, these would be the net positions of the system participants:
Chamber X Chamber Y
Entity A Entity C Entity B Entity D
B +80 A(50) A(80) A(20)
C +50
D +20
Where Entity A would collect from Entities B, C and D.
The chambers will inform the BCRA as follows:
Chamber X
Debit Credit
Entity C 50
Chamber Y 100
Entity A 150
Where the 100 of Chamber Y are the sum of its entities (B=80 and D=20)
NATIONAL PAYMENTS SYSTEM - CHECKS
B.C.R.A.
Section 3 - Operational Instructions
Version: 1 COMMUNICATION “A“ 4281
Validity:
14/01/2005
Chamber Y
Debit Credit
Entity B 80
Entity D 20
Chambers X 100
The following graph presents the inter-chamber clearing scheme:
1 2 3 3
5 5
The structure, content and format of the files to be exchanged electronically between the chambers must comply with the same specifications and standards defined in the chapter of Transactions and messages and in the Record design chapter. iii) Deadlines and schedules. In order to avoid delays in the sending of the information resulting from the clearing to entities and to the BCRA, deadline schedules will be defined for information transactions between chambers.
3.1.3. Sending to entities.
3.1.3.1. Communication of movements.
Deposited
Electronic Chamber
(1)
Electronic Chamber
(2)
Drawee
B.C.R.A.
4 4
NATIONAL PAYMENTS SYSTEM - CHECKS
B.C.R.A.
Section 3 - Operational Instructions
Version: 1 COMMUNICATION “A” 4281
Validity:
14/01/2005
After the clearing process, all participating entities will receive from the CEC the files with:
In the case where the entity receiving the information uses several Transmission Centers for the reception of files from the chamber, a specific one will be designated where the balances resulting from the clearing will always be received. This information will be received separately for each type of currency or species, for each product (checks, debits, transfers) and for each clearing term.
3.1.3.2. Processing of received information.
The entities will receive from the CEC the files resulting from the clearing, up to the reception hours defined by each chamber. The entities may impute the movements in their clients' accounts based on the files received from the CEC, being able to perform rejections, in accordance with current regulations, based on these records or physical returns, if applicable. If a rejection occurs based on electronic information, the drawee entities will reject based on said information and proceed with the return of the physical document. The reasons for rejection and return of checks, as well as the rejections of electronic transactions, are included in detail in Section 7 "Design of records" in the additional rejection record, field 3 "First reason for rejection".
In cases of reasons for rejection and return of documents, as well as in the case of chamber unwinding (“Unwinding”), it is necessary to return the physical document to the depositing client. For other rejections of transactions, it corresponds to the return of the document (non-truncated) by the drawee entity to the depositing entity for new presentation. If validations are not exceeded, the entities reserve the right to request the retransmission of the file in whole or in part.
NATIONAL PAYMENTS SYSTEM - CHECKS
B.C.R.A.
Section 3 - Operational Instructions
Version: 1 COMMUNICATION “A” 4281
Validity:
14/01/2005
3.1.4. Other operational aspects.
3.1.4.1. Business days for clearing.
All days defined by the BCRA as such will be considered business days for clearing.
3.1.4.2. Local holidays.
i) Definition.
A planned local holiday is considered any declared by the competent authority (national, provincial, municipal, or Autonomous City of Buenos Aires), which can be included in advance in a calendar of local holidays. This calendar will be administered by the CEC, and will include the dates of the planned holidays for the different exchange points. It will be duly disseminated through the publication of a CIMPRA bulletin and will be prepared with the information that the entities must provide to the CEC. An unplanned local holiday is considered any declared by the competent authority (national, provincial, municipal, or Autonomous City of Buenos Aires), which cannot be included in advance in the calendar administered by the CEC, but which is known to them through information provided formally by the person in charge of the exchange point, before 10:00 on the day the holiday occurs.
ii) Operational instructions. a) Planned local holidays:
Upon receiving the notice of holiday, in a reliable manner, from the person in charge of the exchange point with a local holiday, the CEC will identify the movements with the clearing date of the holiday day, reject them in the rejection session of that same day for the reason of “local holiday”, and in the next immediate session of presented items, they will be presented again with the date of the next business day, distributing to the entities the information of the transactions corresponding to the exchange point with the local holiday.
The tasks and their sequence that the different intervening actors must perform are described below:
Day D
NATIONAL PAYMENTS SYSTEM - CHECKS
B.C.R.A.
Section 3 - Operational Instructions
Version: 1 COMMUNICATION “A” 4281
Validity:
14/01/2005
Before 10:00.
Entities and Electronic Chambers:
Rejection Session
Depositing Entity:
To achieve reconciliation of the final position of debits and credits, the entities must consider the following information:
Depositing Entity: reconciliation of final position: Debits
Electronic Chambers:
Drawee Entity: reconciliation of the final position: Credits
Session of presented items.
Electronic Chambers:
NATIONAL PAYMENTS SYSTEM - CHECKS
B.C.R.A.
Section 3 - Operational Instructions
Version: 1 COMMUNICATION “A” 4281
Validity:
14/01/2005
Electronic Chambers:
Drawee Entity: reconciliation of the presented position: Debits
Day D + 1
The Entities may present the rejections as depositing entities and drawee entities that should not have presented the previous day, corresponding to the movements deferred due to local holiday.
b) Interruption of activities after their start:
In case that the entities belonging to the same Exchange Point must interrupt their regular activities, after they have started, for some extraordinary or unforeseen reason, the procedure to be applied is the following:
Each entity belonging to the Exchange Point must inform its respective Electronic Chamber if it is or is not in conditions to transmit the presentation of the day. Based on the information received, the Electronic Chambers may decide coordinately to suspend that day the session of presented items for that particular Exchange Point. In this last case, the steps to be followed by the entities are the following:
The entities must make the presentation to the next business day. For those entities that have made the presentation, the CEC will apply to the next business day the procedure that governs for planned local holidays.
NATIONAL PAYMENTS SYSTEM - CHECKS
B.C.R.A.
Section 3 - Operational Instructions
Version: 1 COMMUNICATION “A” 4281
Validity:
14/01/2005
The rejection session will be carried out, therefore the entities must transmit the rejections of the day.
Those entities that could not transmit the rejections must deposit the money equivalent to the total of the presentation and send the rejections as an adjustment to the next business day. Likewise, they must inform the involved entities which are the documents that should have been rejected, to avoid that the crediting is made in the clients' accounts.
3.1.4.3. Exception procedure for communication failure.
In the eventuality of a failure in the communication between the Transmission Centers and the CEC, an exception procedure is foreseen based on the exchange of information by magnetic support with physical delivery of the same in the plaza where the CEC provides the service of reading magnetic supports. The entities will be responsible for the delivery or withdrawal of said support to the CEC. Nevertheless, if the communication problem had not extended to all entities, those affected will have the option to resort to the Transmission Center of another entity that manages the transmission of the information to the CEC.
3.1.4.4 Emergency situations.
i) Definition.
These are all those of external origin to the financial entities and of serious effects, (for example: flood, tornado, road cuts, etc.) that affect one or several plazas and some or most of the entities that participate in electronic clearing. Internal situations registered by the entities (for example: labor actions taken by the entity's staff, computer center problems, etc.) are not included in this procedure, their resolution corresponding through the application of the “Force Majeure” scheme and norms. Non-participation in clearing comprises both the impossibility of carrying out the physical exchange of documents, as well as the transmission of files.
ii) Operational instructions.
The persons in charge of the Exchange Points will communicate to the CEC, on the day it occurs, the inconveniences caused by emergency situations. The CEC and the entities will proceed as follows:
Rejection Session:
NATIONAL PAYMENTS SYSTEM - CHECKS
B.C.R.A.
Section 3 - Operational Instructions
Version: 1 COMMUNICATION “A” 4281
Validity:
14/01/2005
The corresponding one for the presented items of the previous business day will be carried out, with the usual procedure for normal days. The headquarters of the affected branches will reject the entirety of the records presented, on the previous business day, using the rejection code for the transaction: R 34 “Emergency situation”. The transmission of the electronic files of the rejections will be carried out in the usual hour of sending the information to the CEC. Depositing Entity: must clear again the documents rejected due to emergency situation in the session of presented items of the same day or the next business day. In the case of non-truncated documents, it will present only the electronic data, without proceeding to the physical exchange, since it will not have the respective values. Given this situation, it is observed the need to identify the depositors through the checks; for this, it is convenient that identification procedures for the deposits are developed, such as establishing a relationship between the check and the deposit slip. In case that in the second presentation, some truncated value is rejected for a cause that generates a fine, the obtaining of the image to be delivered to the drawee entity must be obtained from the files of the original presentation. Affected Branches: will retain the documents, waiting for the second presentation, to carry out the payment tasks and the physical exchange of non-truncated checks.
Session of presented items of that date:
The CEC will be available to carry out the processing in the established hours.
The person in charge of the Exchange Point will have the responsibility to:
3.2. Particular aspects of the clearing of truncated checks.
3.2.1. Definition of truncated checks.
Those are those that remain in the possession of the depositing entity, after capturing their representative data, reaching the drawee entity only the information about them in electronic form. These data constitute all the information that the depositing entity sends to the drawee entity so that it decides to make the payment or the rejection, without it being necessary to resort to the sending of the original document. Nevertheless, the original document must remain available to the drawee entity, who may require the original or a copy of it, in case of claims. The movement of original documents will be minimized using a differential tariff. The original documents, once delivered by the depositing entity to the drawee entity, will not be returned, losing their condition of truncated.
3.2.2. Clearing Terms.
All truncated checks will have a clearing term between entities of 48 hours.
Day D Day D + 1 Day D + 2
Presentation Claims
Availability of funds to the client
Clearing Clearing Settlement
Presented Rejected B.C.R.A.
3.2.3. Presentation.
The depositing entities will transmit to a CEC, in the session of presented items, the files with the information on the checks to be cleared and adjustments up to the defined deadline, in files whose structure, content, and format are detailed in the chapter of Messages and Design of records.
3.2.4. Processing by Electronic Chambers.
The chambers will receive and clear the checks to then inform the drawee entities of the movements resulting from the clearing, according to the defined hours.
3.2.5. Processes to be executed by the depositing entity.
On the business day following the presentation, the depositing entity will execute the following processes:
§ Preparation of the rejection file, with all those checks regarding which it had detected any of the reasons for formal defects established by the BCRA regulations. § Crediting of the amount of the non-rejected checks in the accounts of the depositing clients, once the movements are settled in the BCRA.
3.2.6. Reception by the drawee entity.
NATIONAL PAYMENTS SYSTEM - CHECKS
B.C.R.A.
Section 3 - Operational Instructions
Version: 1 COMMUNICATION “A” 4281
Validity:
14/01/2005
The drawee entities will receive from the Electronic Chamber the files with the detail of the movements and the bilateral balances cleared in the defined hours.
3.2.6.1. Processes to be executed by the drawee entity.
Once the information is received and its validity is assured, the drawee entities will execute the following processes:
3.2.7. Rejections.
3.2.7.1. Rejections of the depositing entity.
i) Definition.
These are the rejections that the depositing entity performs when it verifies, in the physical checks received, the existence of any of the defects foreseen in the current legislation and regulations.
ii) Operational instructions. a) Transmission of rejected checks.
The depositing entity will transmit to the CEC, up to the deadline hour of the rejection session, the file with the information corresponding to the checks it rejected, taking into account the rejection causes defined in current regulations. In case of truncation, in accordance with current regulations, it will transmit for the following reasons for rejection of checks and/or transactions:
NATIONAL PAYMENTS SYSTEM - CHECKS
B.C.R.A.
Section 3 - Operational Instructions
Version: 1 COMMUNICATION “A” 4281
Validity:
14/01/2005
b) Processing by the Electronic Chamber.
The CEC will receive and clear the rejected checks, according to the defined hours.
c) Reception of the rejections by the drawee entity.
The drawee entity will receive from the CEC the file with the information of the rejections observed by the depositing entity. With this information, the drawee entity:
3.2.7.2. Rejections of the drawee entity.
i) Definition.
These are the rejections that the drawee entity performs when it verifies, in the information of checks received in electronic form, the existence of any of the rejection or document return causes, or rejection causes of transactions, foreseen in current regulations.
ii) Operational instructions. a) Transmission of rejected checks and transactions.
The drawee entity will transmit to the CEC, up to the deadline hour of the rejection session, the information corresponding to the checks/transactions it rejected. In case of truncation, in accordance with current regulations, it will transmit for the following reasons for rejection of checks and/or transactions:
NATIONAL PAYMENTS SYSTEM - CHECKS
B.C.R.A.
Section 3 - Operational Instructions
Version: 1 COMMUNICATION “A” 4281
Validity:
14/01/2005
b) Processing by the Electronic Chamber.
The chamber will receive and clear the information corresponding to the rejected checks, according to the defined hours.
c) Reception of the rejections by the depositing entity.
The depositing entity will receive from the CEC the file with the information corresponding to the rejected checks.
d) Transitional file until rejections from the drawee entity arrive.
It is necessary that the depositing entities temporarily archive the truncated checks not yet confirmed, to be able to return them to the depositing client in case they are rejected by the drawee entity.
e) Stamp and delivery to the depositing client.
The depositing entity will stamp the rejected check, including in said stamp the information established by the BCRA, and deliver the check to the client who made the deposit.
f) Treatment of rejections due to order not to pay, forgery and alteration of the check.
For the case of truncated checks that are rejected by “order not to pay” by the drawee entity and by “forgery and alteration of the check” by the depositing entity, the original documents must be sent physically by the depositing entity to the drawee entity in the session of physical exchange of rejected checks on the day following the rejection. The physical exchange of said checks will be operated through the same Exchange Center that is used to exchange non-truncated checks.
iii) Management of rejections by the CEC.
The CEC must manage the validity of the rejections of the entities regarding the term. The normal term for rejecting a check will be 1 business day. In case that the depositing entity transmits to the CEC the rejection of a check for any of the foreseen causes, and said check is also rejected by the drawee entity for any of the foreseen causes, a duplication of rejections on the same document in the same clearing cycle (collision of rejections) would occur. The CEC processes the information received from both entities in the rejection session and, in case it detects records that correspond to the same document, it must administer the collision as follows:
NATIONAL PAYMENTS SYSTEM - CHECKS
B.C.R.A.
Section 3 - Operational Instructions
Version: 1 COMMUNICATION “A” 4281
Validity:
14/01/2005
Identification of the signatory in the Entity drawn upon at the request of the holder of the rejected check.
Proceed according to the regulations issued by the BCRA for this purpose.
3.2.7.3. Rejections outside of exchange.
Values rejected outside of exchange are those presented by the drawn entity within a maximum period of 120 days, after the corresponding period for the presentation of rejections. In a first stage, the circuit of rejections outside of exchange applies within the scope of the Capital Federal Chamber, while the rest of the locations continue with their usual procedures. i) Description of the rejection circuit outside of exchange. This circuit allows the drawn entity to present the rejection outside of exchange to the depository entity, both for truncated and non-truncated checks, through a non-monetary transaction using the Individual Register of Rejections Outside of Exchange. The admitted rejections are those originating from the reasons for check rejection used by the drawn entity, such as: insufficient available funds, order of non-payment, account closed by judicial order, etc. The presentation of a rejection outside of exchange is carried out in the session of presented checks, in batches separate from the documents to be compensated. In the case of non-truncated checks, the drawn entity must additionally deliver the original document on the same day it transmits the rejection outside of exchange transaction, except when it concerns a rejection for any of the reasons that imply that the document remains in its possession, such as:
NATIONAL PAYMENTS SYSTEM - CHECKS
B.C.R.A.
Section 3 - Operational Instructions
Version: 1 COMMUNICATION “A” 4281
Validity:
14/01/2005
The deadline for the depository entity to give a response regarding the acceptance or non-acceptance of the rejection outside of exchange is 15 business days from the presentation thereof by the drawn entity. Likewise, the CECs will carry out a statistical control of the breaches incurred by the entities in order to analyze, in a future stage, the possibility of establishing a specific deadline for the “non-acceptance” of the rejection outside of exchange. From the day following the receipt of the outside of exchange transaction, the depository entity may carry out the following actions:
NATIONAL PAYMENTS SYSTEM - CHECKS
B.C.R.A.
Section 3 - Operational Instructions
Version: 1 COMMUNICATION “A” 4281
Validity:
14/01/2005 despite this, after that deadline has passed, the claim will also be admitted through the system, being subject to the application of a differentiated interbank commission. Likewise, the possible collection of differences by the drawn entity that could be verified by viewing the received document (reproduction or original) will be admitted for documents compensated with an age of less than one (1) year; while those adjustments derived from the observation of documents compensated with an age greater than that period will have a bilateral treatment between the intervening entities.
3.2.8.2. Receipt of the claim at the CECs.
The CECs, upon receiving the claims sent by the drawn entities, will carry out the corresponding format and resolution deadline controls before processing them. Nevertheless, they will not control that the data of the claim corresponds to the data sent in the presentation of the check for its compensation.
3.2.8.3. Response to the received claim.
The depository entity, upon receiving the claim message, will carry out the necessary checks, essentially verifying that the claimed check was presented by it on the date informed in the claim. The sending of the claimed image or the possible rejection of the request for not corresponding, will be sent through the same system.
3.2.8.4. Rejection of the claim.
The reasons why a claim may be rejected are mentioned below:
Non-existent Account The affected account cannot be identified Invalid account number The affected account has a format error Check already delivered Truncated check that has already been delivered to the drawn bank or to the depositing client Incorrect presentation date When an incorrect presentation date of the original check is informed, including an inactive day or an incorrect date Incorrect amount When the depository entity proceeds to reject a claim in which the amount does not match the amount of the requested document or because it was made on a non-truncated document Duplicate transaction When duplicate transactions are received Non-existent check When claims are received on non-existent checks (Cimpra 118). If any of the specified reasons are verified, the depository entity may reject the claim on its due date, 8 business days counted from the date of pre-
NATIONAL PAYMENTS SYSTEM - CHECKS
B.C.R.A.
Section 3 - Operational Instructions
Version: 1 COMMUNICATION “A” 4281
Validity:
14/01/2005 sentation thereof. For this, a control record without associated image will be used, using the rejection codes detailed in the annex that describes the design of records.
3.2.8.5. Transmission of the image.
In case what was requested was a reproduction, the depository entity must send the images of the front and back of the claimed check, both in a single image file, which will be associated with a control record containing the data of the check that were sent in the electronic transaction of the claim. For this, the following scheme of exchange sessions will exist, similar to that used for the images of rejected truncated checks:
NATIONAL PAYMENTS SYSTEM - CHECKS
B.C.R.A.
Section 3 - Operational Instructions
Version: 1 COMMUNICATION “A” 4281
Validity:
14/01/2005
3.2.8.6. Receipt of the images at the CECs.
The CECs will control the fulfillment of the sending of the images, pairing the data indexed to it with the data of the electronic transaction of the claim sent through the same system.
3.2.8.7. Receipt by the drawn entity.
The drawn entity may reject the received image, in case of deficiencies that do not allow it to carry out the pertinent checks. Such rejection must be sent under the same modalities used for the rejection of images of rejected truncated checks, that is, by sending a control record with the design described in the annex, without the associated image file. Upon receiving the rejection of the image due to deficiencies in it or for incorrect image, the CECs must unmark the fulfillment, passing to include it within the pending sending and reception.
3.2.8.8. Exchange of claimed originals.
The delivery of the claimed originals must be carried out at the Physical Exchange Center on the thirteenth (13) business day counted from the date of presentation of the claim, while the depository entity may reject the request for claim of an original document on the eighth business day following the presentation thereof. At the time of delivery, the intervention of the person in charge of the Exchange Center will be available, who will verify it through the capture of the physical check data, using a technological means that allows the reading of the CMC7 characters, and the manual entry of the amount, pairing then the obtained data with a database of claimed originals provided by the CECs. The latter will determine the procedure through which, from the data of the delivered original, the fulfillment of the claim will be marked, generating at the same time the information related to the unanswered claims.
3.2.9. Adjustments.
3.2.9.1. Definition.
In the presented session, depository entities may inform as “adjustments” the eventual differences found by their control processes, between the amounts of the checks presented electronically and the amounts of the physical checks.
3.2.9.2. Operational Instructions.
NATIONAL PAYMENTS SYSTEM - CHECKS
B.C.R.A.
Section 3 - Operational Instructions
Version: 1 COMMUNICATION “A” 4281
Validity:
14/01/2005
When the Depository Entity recognizes a difference in the amount of a check already presented and compensated, it will proceed as follows:
NATIONAL PAYMENTS SYSTEM - CHECKS
B.C.R.A.
Section 3 - Operational Instructions
Version: 1 COMMUNICATION “A” 4281
Validity:
14/01/2005
Day D Day D + 1 Day D + 2
Presentation Rejected Presented
Compensation Settlement
B.C.R.A.
3.3.3. Presentation.
3.3.3.1. Sending of electronic information.
The depository entity will present the documents electronically on the day of its deposit in the presented session, until the defined deadline. The electronic information sent to the chamber will include, in each batch, a field with the compensation period.
3.3.4. Processing by the CECs.
The electronic record will be compensated in the normal compensation cycle once the presented session has ended.
3.3.5. Receipt by the drawn entity.
The CECs will send the information of the non-truncated checks to the entities.
If a deferral order arrives, defined later, the chamber will debit the check to the depository on the next business day in the rejected session, to then present it automatically in the presented session of that same day.
3.3.5.1. Processes to be executed by the drawn entity.
The drawn entities, once received the compensated movements on the date agreed with the depository, must carry out:
NATIONAL PAYMENTS SYSTEM - CHECKS
B.C.R.A.
Section 3 - Operational Instructions
Version: 1 COMMUNICATION “A” 4281
Validity:
14/01/2005
NATIONAL PAYMENTS SYSTEM - CHECKS
B.C.R.A.
Section 3 - Operational Instructions
Version: 1 COMMUNICATION “A” 4281
Validity:
14/01/2005
The rejection causes are those established in the current regulations.
3.3.7.3. Operational Instructions.
The physical exchange of the rejected documents will be carried out at the same exchange points where the original checks had been previously presented. The electronic compensation of rejections will be carried out according to the operation previously described in the electronic compensation of checks in general. The drawn entity, in the same way as it does with truncated checks, must:
NATIONAL PAYMENTS SYSTEM - CHECKS
B.C.R.A.
Section 3 - Operational Instructions
Version: 1 COMMUNICATION “A” 4281
Validity:
14/01/2005
NATIONAL PAYMENTS SYSTEM - CHECKS
B.C.R.A.
Section 3 - Operational Instructions
Version: 1 COMMUNICATION “A” 4281
Validity:
14/01/2005
NATIONAL PAYMENTS SYSTEM - CHECKS
B.C.R.A.
Section 4 - Responsibilities of the participants.
Version: 1 COMMUNICATION “A” 4281
Validity:
14/01/2005
4. RESPONSIBILITIES OF THE PARTICIPANTS.
The system implies a series of responsibilities that the participating entities must assume:
NATIONAL PAYMENTS SYSTEM - CHEQUES
BCRA
Section 4 - Responsibilities of Participants.
Version: 1 COMMUNICATION "A" 4281
Validity:
14/01/2005
4.2. Of the Electronic Clearing Houses.
With respect to the processing of data, the ECHs must:
NATIONAL PAYMENTS SYSTEM - CHEQUES
BCRA
Section 4 - Responsibilities of Participants.
Version: 1 COMMUNICATION "A" 4281
Validity:
14/01/2005
4.3. Of the Drawee Entity.
NATIONAL PAYMENTS SYSTEM - CHEQUES
BCRA
Section 4 - Responsibilities of Participants.
Version: 1 COMMUNICATION "A" 4281
Validity:
14/01/2005
NATIONAL PAYMENTS SYSTEM - CHEQUES
BCRA
Section 5 - Controls to be Performed.
Version: 1 COMMUNICATION "A" 4281
Validity:
14/01/2005
5.1. By the Electronic Clearing Houses.
5.1.1. Basic.
5.1.2. Specific.
5.2. By the entities.
5.2.1 Entities receiving electronic information.
The entities that receive information from the ECH ("recipient entities"), whether in the capacity of drawee in the case of the presented session, or in the capacity of depositary in the case of the rejected session, must perform at least the following controls:
5.2.1.1. Basic
5.2.1.2. Specific.
5.2.2. Entities sending electronic information.
The entities that send information to the ECH ("originating entities"), whether in the capacity of depositary in the case of the presented session, or in the capacity of drawee in the case of the rejected session, must perform at least the following controls:
5.2.3. Basic.
NATIONAL PAYMENTS SYSTEM - CHEQUES
BCRA
Section 5 - Controls to be Performed.
Version: 1 COMMUNICATION "A" 4281
Validity:
14/01/2005
5.2.4. Specific.
NATIONAL PAYMENTS SYSTEM - CHEQUES
BCRA
Section 6 - Transactions and Messages.
Version: 1 COMMUNICATION "A" 4281
Validity:
14/01/2005
6.2. File Structure.
The structure of the files has been developed considering the standards of NACHA ("National Automated Clearing House Association"). The files to be exchanged electronically will have the following structure:
NATIONAL PAYMENTS SYSTEM - CHEQUES
BCRA
Section 6 - Transactions and Messages.
Version: 1 COMMUNICATION "A" 4281
Validity:
14/01/2005
Structure of the cheque file.
Sequence of files in NACHA format.
1 per file
1 per batch
1 per batch
1 per batch
1 per file
The File Header, Batch Header, Batch Control, File Control, and Individual Transaction Records are the same in all files, for any type of transaction related to cheques.
6.2.1. File Header.
The File Header identifies the immediate origin of the information, which includes the Transmission Center and the originating entity or entity sending the information (which will be the depositary in the case of the presented session and the drawee in the rejected session). It also includes the Electronic Clearing House. In turn, this record includes the presentation date, presentation time, and file identifier fields, in such a way as to identify it uniquely.
6.2.2. Batch Header.
File Header
Batch Header
Individual Transaction Record
Individual Transaction Record
.
.
.
Individual Transaction Record
End of Batch Control
Batch Header
Individual Transaction Record
Individual Transaction Record
.
.
.
Individual Transaction Record
End of Batch Control
End of File Control
NATIONAL PAYMENTS SYSTEM - CHEQUES
BCRA
Section 6 - Transactions and Messages.
Version: 1 COMMUNICATION "A" 4281
Validity:
14/01/2005
The Batch Header identifies the originating entity and the destination entity of the transaction.
This record also indicates the clearing date of the transactions included in the batch.
The information contained in the batch header applies to all individual records contained therein.
6.2.3. Individual Transaction Record.
The Individual Transaction Record contains the information necessary to route the transaction to the destination entity (drawee entity and branch) and the corresponding account. This record includes the number and amount of the cheque to be compensated.
6.2.4. Additional Record.
The Additional Record is used to provide additional information about the transaction included in the individual record.
The inclusion of an additional record is optional, used only in the case that there are multiple reasons for rejection of a cheque.
6.2.5. End of Batch Control.
The End of Batch Control contains the sum of the amounts, records (individual and additional), and control totals of the individual records contained in the batch.
6.2.6. End of File Control.
The End of File Control contains the sum of the amounts, records (individual and additional), and control totals of the batches contained in the file.
NATIONAL PAYMENTS SYSTEM - CHEQUES BCRA
Section 7 - Record Design.
Version: 1 COMMUNICATION "A" 4281 Validity: 14/01/2005 Page 1
NATIONAL PAYMENTS SYSTEM - CHEQUES BCRA
Section 7 - Record Design.
Version: 1 COMMUNICATION "A" 4281 Validity: 14/01/2005 Page 2
7.1. File Header.
Field 1 2 3 4 5 6 7 8 9 10 11 12 13
Name Record Identifier
Priority Code
Immediate
Destination
Immediate
Origin
Presentation
Date
Presentation
Time
File
Identifier
Record
Size
Factor
Block
Format
Code
Name of Immediate
Destination
Name of Immediate
Origin
Reference
Code
Field
Requirement
M O M O
Type '1' '01' Numeric Numeric AAMMDD HHMM Alphanumeric '094 '10' 1 Alphanumeric Alphanumeric Alphanumeric Length 1 2 10 10 6 4 1 3 2 1 23 23 8 Position 01-01 02-03 04-13 14-23 24-29 30-33 34-34 35-37 38-39 40-40 41-63 64-86 87-94 Description of fields:
NATIONAL PAYMENTS SYSTEM - CHEQUES BCRA
Section 7 - Record Design.
Version: 1 COMMUNICATION "A" 4281 Validity: 14/01/2005 Page 3
Immediate Destination.
Identifies the destination of the file. When the entity transmits to the clearing house, this field contains:
a) A blank space b) The Electronic Clearing House identifying number in 8 positions c) A zero In the case of the clearing house transmitting, this identifying number will be composed of:
a) A blank space. b) The destination entity number in 4 positions. c) The entity branch number acting as Transmission Center in 4 positions. d) A zero.
Immediate Origin.
Identifies the origin of the file. When the clearing house transmits to the entity, this field contains:
a) A blank space. b) The Electronic Clearing House identifying number in 8 positions. c) A zero.
In the case of the entity transmitting to the Electronic Clearing House, this identifying number will be composed of:
a) A blank space. b) The originating entity number in 4 positions. c) The entity branch number acting as Transmission Center in 4 positions. d) A zero.
NATIONAL PAYMENTS SYSTEM - CHEQUES BCRA
Section 7 - Record Design.
Version: 1 COMMUNICATION "A" 4281 Validity: 14/01/2005 Page 4
Presentation Date.
This field contains the date on which the file was created.
Presentation Time.
This field contains the time at which the file was created.
File Identifier.
This field allows identifying the different files sent during the day, with letters or numbers (A-Z or 1-9) of a specific entity.
Record Size.
This field would indicate the number of characters contained in each record. Currently, the number '094' is used.
Block Factor.
This field defines the number of physical records that exist in a block (a block is composed of 940 characters). All transmissions between the entities and the clearing house must use the number '10'.
Format Code.
This field is reserved for future use. It must be completed with the value '1'.
Name of Immediate Destination.
This field contains the name of the file destination (Electronic Clearing House/Transmission Center depending on the case).
Name of Immediate Origin.
This field contains the name of the message originator. (Electronic Clearing House/Transmission Center depending on the case).
NATIONAL PAYMENTS SYSTEM - CHEQUES BCRA
Section 7 - Record Design.
Version: 1 COMMUNICATION "A" 4281 Validity: 14/01/2005 Page 5
Additional Comments.
When a field has more characters than required for the information to be completed, they must be filled with zeros starting from the left margin, in the case of numeric fields, and with right blanks in the case of alphanumeric fields. The alphabetic characters of the alphanumeric fields must always be reported in uppercase.
NATIONAL PAYMENTS SYSTEM - CHEQUES BCRA
Section 7 - Record Design.
Version: 1 COMMUNICATION "A" 4281 Validity: 14/01/2005 Page 6
7.2. Batch Header.
Field 1 2 3 4 5 6 7 8 9 10 11 12 13
Name
Record Identifier Transaction Class Code Reserved Reserved Reserved Standard Record Type Code Description of the Transaction Presentation Date Maturity Date Reserved Origin Code Identification of the Originating Entity Batch Number Field Requirement M M N/A M Type '5' '200' Alphanumeric Alphanumeric Alphanumeric 'TRC Alphanumeric Numeric AAMM DD '000' Alphanumeric Numeric Numeric Length 1 3 16 20 10 3 10 6 6 3 1 8 7 Position 01-01 02-04 05-20 21-40 41-50 51-53 54-63 64-69 70-75 76-78 79-79 80-87 88-94 Description of fields:
Record Identifier.
5 Batch Header.
Transaction Class Code.
This code identifies a general classification of the type of transactions included in the batch:
200 Debit and credit transactions.
Reserved.
This field is reserved for future uses.
NATIONAL PAYMENTS SYSTEM - CHEQUES BCRA
Section 7 - Record Design.
Version: 1 COMMUNICATION "A" 4281 Validity: 14/01/2005 Page 7
Reserved.
This field is reserved for future uses.
Reserved.
This field is reserved for future uses.
Standard Record Type Code.
This code allows distinguishing the type of record:
TRC Cheque batches.
Transaction Description:
The originator defines the value of this field to describe the purpose of the transaction. In the case of rejections by the depositary, this field must contain the value "REVERSAL". Code Description. REVERSAL Rejection by the depositary entity. CHEQUES Cheque operations.
Presentation Date.
This field contains the date corresponding to the session in which the file must be transmitted in AAMMDD format.
Maturity Date.
This field contains the clearing date in AAMMDD format.
NATIONAL PAYMENTS SYSTEM - CHEQUES BCRA
Section 7 - Record Design.
Version: 1 COMMUNICATION "A" 4281 Validity: 14/01/2005 Page 8
Reserved.
This field is reserved for future uses. Currently, it will be completed with '000'.
Origin Code.
This field contains the origin code:
1 Financial entity.
Identification of the Originating Entity:
This field contains the identifying number of the entity generating the transaction (The entity number with 4 characters and the branch number with 4 characters are included). In the case that an entity represents another for the presentation of cheques, this field will be completed with the number of the represented entity in the format previously described.
Batch Number.
This field contains the batch number, determined by the originating entity.
Additional Comments:
When a field has more characters than required for the information to be completed, they must be filled with zeros starting from the left margin, in the case of numeric fields, and with right blanks in the case of alphanumeric fields. The alphabetic characters must always be reported in uppercase.
NATIONAL PAYMENTS SYSTEM - CHEQUES BCRA
Section 7 - Record Design.
Version: 1 COMMUNICATION "A" 4281 Validity: 14/01/2005 Page 9
7.3. Individual Record of Presentation of Cheques and Adjustments.
Cheque 1 2 3 4 5 6 7 8 9 10 11 12
Name
Record Identifier
Transaction Code Entity to Debit Reserved Account to Debit Amount Document Type/ Cheque Number Postal Code Exchange Point/Depositary Rejection Additional Transaction Information Additional Records Record Counter Field Requirement M Type 6 Numeric Numeric "0" Numeric $$$$$$$$cc Numeric Alphanumeric Alphanumeric Alphanumeric Numeric Numeric Length 1 2 8 1 17 10 15 6 16 2 1 15 Position 01-01 02-03 04-11 12-12 13-29 30-39 40-54 55-60 61-76 77-78 79-79 80-94 Description of fields:
Record Identification.
6 Individual Record.
Transaction Code.
This code indicates the type of transaction.
Presentation and other compensable documents 27 Depositary Entity Rejection 22 Adjustment 27 Drawee Entity Rejections 26 Adjustment Rejections 26
NATIONAL PAYMENTS SYSTEM - CHEQUES BCRA
Section 7 - Record Design.
Version: 1 COMMUNICATION "A" 4281 Validity: 14/01/2005 Page 10
This field contains the identifying number of the destination entity of the transaction. (The entity number with 4 characters and the branch number with 4 characters are included). The branch will be completed with 0000 when it is a time deposit certificate.
Reserved.
This field is reserved for future uses. It must be completed with zeros ("0").
Account to Debit.
This field indicates the account to be debited and must contain the exact data thereof. It includes numbers from 0 to 9, aligned to the right. It will be completed with 88888888888 when it is an adjustment related to a cheque that exceeds eight integer digits. It will be completed with 77777777777 when it is a time deposit certificate. It will be completed with 99999999999 when it is a certified cheque, drafts, or payment orders.
Amount.
This field indicates the amount to be debited from the account detailed above. When said amount exceeds eight integer digits, transactions similar to adjustments will be sent.
Document Type/Cheque Number.
This field identifies the document type in the first two positions and the cheque number to which the transaction refers in the following positions. 00 Cheques.
Postal Code.
NATIONAL PAYMENTS SYSTEM - CHECKS B.C.R.A.
Section 7 - Record Design.
Version: 1 COMMUNICATION "A" 4281 Validity: 14/01/2005 Page 11
This field indicates the postal code of the destination entity and shall be completed as follows: with two zeros ("0") on the left and with the code by which the destination plaza of the check is identified in the last 4 positions.
9. Depositary exchange/rejection point.
This field contains the identification of the exchange point where the physical document is presented, and shall be completed as follows: the first 4 positions shall be completed with the identification code of the exchange point (case 1: with two zeros and the chamber code - two positions-; case 2: in the postal code of the exchange point - four positions-). In the event of a rejection by the depositary entity, the following 4 (four) positions shall be completed with the rejection reasons –two positions for each one without the "R"-, the remaining 8 positions to the right shall be completed with spaces.
10. Additional transaction information:
This field allows identifying the currency of the affected account and the type of transaction being reported.
The first position of this field will contain the type of currency of the affected account:
0. Pesos.
The second position will indicate the type of transaction being reported or rejected:
0. Check and other compensable documents.
1. Adjustment.
11. Additional records.
This field indicates whether there are additional records ('1' or '0' respectively).
12. Record counter ("Trace number").
NATIONAL PAYMENTS SYSTEM - CHECKS B.C.R.A.
Section 7 - Record Design.
Version: 1 COMMUNICATION "A" 4281 Validity: 14/01/2005 Page 12
This field includes the identification number of the origin entity in 8 positions (4 for the entity and 4 for the branch) and then in positions 9 to 15 a unique ascending sequential number in all sessions of the day for each record sent. This implies that the record counter number cannot be repeated in different files transmitted throughout the day. These 15 positions shall be ordered sequentially within each batch.
In the event that an entity represents another for the presentation of checks, the branch number shall be replaced by a "9" in the fifth position and the number of the represented entity in the following positions.
Additional comments:
When a field has more characters than required for the information to be completed, they shall be filled with zeros starting from the left margin, in the case of numeric fields, and with spaces to the right in the case of alphanumeric fields. Alphabetic characters shall always be reported in uppercase.
NATIONAL PAYMENTS SYSTEM - CHECKS B.C.R.A.
Section 7 - Record Design.
Version: 1 COMMUNICATION "A" 4281 Validity: 14/01/2005 Page 13
7.4. Additional record of check rejections and adjustments.
| Field | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 |
|---|---|---|---|---|---|---|---|---|
| Name | Record Identifier | Additional Record Type Code | First Rejection Reason | Counter of Original Transaction Record | Communication Number | Entity of the Original Transaction | Other Rejection Reasons | Record Counter |
| Field Requirement | M | O | M | O | M | |||
| Type | 7 | 99 | Alphanumeric | Numeric | Alphanumeric | Numeric | Alphanumeric | Numeric |
| Length | 1 | 2 | 3 | 15 | 6 | 8 | 44 | 15 |
| Position | 01-01 | 02-03 | 04-06 | 07-21 | 22-27 | 28-35 | 36-79 | 80-94 |
Description of fields:
1. Record Identifier.
7. Additional record.
2. Additional Record Type Code.
This code indicates the type of additional record. In this case, the code '99' is used.
NATIONAL PAYMENTS SYSTEM - CHECKS B.C.R.A.
Section 7 - Record Design.
Version: 1 COMMUNICATION "A" 4281 Validity: 14/01/2005 Page 14
First Rejection Reason.
The following table contains the reasons (identified by using a code) for which a document or its payment is rejected, in accordance with the provisions of current regulations:
| Code | Description | Explanation |
|---|---|---|
| R06 | Formal defects | This code will be used when formal vices are verified in the check, i.e., those incurred in the creation of the document such as: the drawer's signature differs manifestly from that recorded in the drawee entity's records; signer without valid power of attorney valid at the time of issuance; lack of additional signatures to the existing one(s) when the signature of more than one person is required; signer disqualified at the time of issuance; draw on the drawer unless it is a check drawn between different establishments of the same drawer and the social contract expired at the time of issuance. In the case of non-conformity in the receipt of checkbooks, code R35 will be used. |
| R10 | Insufficient available funds | This code will be used when the account on which the transaction falls does not have sufficient funds to cover it. |
| R16 | Titles that lack value as checks | This code will be used when any of the specifications contained in articles 2, items 1 to 6, 4th, 23 and 54, items 1 to 9, of the Check Law are not included. Likewise, it will be used when: 1) there are strikethroughs, or amendments not saved by the drawer, in the case that the drawer's signature does not match that of who saves it on the back, code R38 will be used; 2) when not drafted in the national language; 3) contain advertising inscriptions; 4) CPD maturity date prior to or equal to the issuance date. |
| RXX | Rejection of CPD registration | As established in current regulations. |
NATIONAL PAYMENTS SYSTEM - CHECKS B.C.R.A.
Section 7 - Record Design.
Version: 1 COMMUNICATION "A" 4281 Validity: 14/01/2005 Page 15
The following table contains other reasons for document return, in accordance with current regulations:
| Code | Description | Explanation |
|---|---|---|
| R01 | Account seized by judicial order | This code will be used in the case that the account is seized by judicial order and as long as this circumstance has been ignored by the drawer at the time of issuing the check and it would have been possible to attend to it with the existing balance in the account if the precautionary measure had not been ordered. |
| R02 | Account closed by judicial order | This code will be used in the case that the account is closed by judicial order, with funds, to return checks issued prior to the closure and within the legal validity period. For the case of truncation, this code will be used for the rejection of the corresponding transaction. |
| R08 | Report of loss, theft, or adulteration of check (order not to pay) | This code will be used by banks when a check or debit has an order not to pay given by the client receiving the debit in their account, according to current regulations. |
| R11 | Containing endorsements exceeding the established limit | This code will be used in the case that checks contain endorsements that exceed the limit established in point 5.1.1 of the regulations on Bank Current Account Regulation, with the established exceptions. |
| R21 | Preventive bankruptcy of the drawer | This code will be used in cases where the preventive bankruptcy of the drawer is declared judicially and only with respect to deferred payment checks that meet the conditions mentioned in point 6.4.6.5 of the regulations on Bank Current Account Regulation. |
| R33 | Check drawn on formulas from notebooks not delivered by the drawee bank (check forgery) | This code will be used when the check is not paid or registered because it is drawn on formulas from notebooks not delivered by the bank for the drawee account. |
| R36 | Adulteration of the check | This code will be used when the pre-printed data and/or original written texts of the check have been modified. |
| R37 | Legal validity period expired | This code will be used when the presentation date of a check has expired. |
| R38 | Signature does not match | This code will be used when the drawer's signature does not match that of who saves it on the back. |
NATIONAL PAYMENTS SYSTEM - CHECKS B.C.R.A.
Section 7 - Record Design.
Version: 1 COMMUNICATION "A" 4281 Validity: 14/01/2005 Page 16
| Code | Description | Explanation |
|---|---|---|
| R44 | Stolen document | This code will be used for values stolen or lost from checkbooks not delivered to clients. |
| R81 | Force majeure | This code will be used by banks when there are force majeure causes at the time of presenting the check that prevent its payment. For the case of truncation, this code will be used for the rejection of the corresponding transaction. |
| R83 | Irregularity in the endorsement chain | This code will be used when an irregularity is verified in the endorsement chain of the check due to: endorsements do not succeed, missing first endorsement, missing signature for deposit, check not to order with more than one endorsement. |
| R97 | Advance presentation date (CPD) | This code will be used in the case that the depositary bank presents for payment a CPD with a maturity date subsequent to the presentation. |
The following table contains the reasons for rejection of transactions presented for compensation:
| Code | Description | Explanation |
|---|---|---|
| R03 | Non-existent account | This code will be used by the drawee entity in the case that the account on which the transaction falls cannot be identified. |
| R04 | Invalid account number | This code will be used by the drawee entity in the case that the account on which the transaction falls has a format error. |
| R11 | Non-compliance with truncated check claim | This code will be used by the drawee entity when the depositary entity has not complied in time with the claim for delivery of truncated checks from the drawee. |
| R12 | Rejection of claim for check already delivered | This code will be used by depositary banks to reject a claim for a truncated check that has already been delivered to the drawee bank. |
| R13 | Non-existent destination branch/entity | This code will be used by the drawee entity when it is impossible to identify the entities to which transactions are sent or from which they are received. |
| R17 | Format error | This code will be used by the chambers to reflect format errors. It applies to errors in mandatory, fixed, or determined type fields (numeric or alphanumeric). |
| R18 | Incorrect compensation date | This code will be used by the chambers when the compensation date does not coincide with the deadlines defined for each product. |
| R19 | Incorrect amount | This code will be used by the drawee entity when the amount of a rejection does not coincide with the amount of the original transaction. |
| R24 | Duplicate transaction | This code will be used by the drawee entity when they receive duplicate transactions. |
| R25 | Error in additional record | This code will be used by the chambers when there is a problem with the additional records, for example when an additional record is missing when it is mandatory, when the presence of the additional record is indicated and it does not exist, etc. |
NATIONAL PAYMENTS SYSTEM - CHECKS B.C.R.A.
Section 7 - Record Design.
Version: 1 COMMUNICATION "A" 4281 Validity: 14/01/2005 Page 17
R26 Error for mandatory field
This code will be used by the chambers when a mandatory field is blank or with invalid characters.
R27 Error in record counter
This error will be used by the chambers when there is a problem in the sequence of the record counter.
R31 Chamber unwind (Unwinding)
This code will be used by the chambers when documents must be rejected due to the need to reprocess the chamber, given that a bank did not cover the debtor position. For the case of truncation, this code will be used for the rejection of the corresponding transaction.
R34 Emergency situations
This code will be used by the drawee entity when they reject documents due to the occurrence of all those situations of external origin to the financial entities and of grave effects such as: Flood, tornado, route cuts, etc.
R35 Lack of conformity
This code will be used by the drawee entity when there is a lack of conformity in the receipt of checkbooks.
R39 Amount does not match the one registered by the drawee bank This code will be used by the drawee entity in the case of truncated CPDs registered.
R75 Date error
This code will be used by the chambers when there are format errors in the date.
R76 Error in field 11 Batch Header
This code will be used by the chambers when there is an error in the origin code.
R77 Error in field 4 Individual Record
This code will be used by the chambers when in field 4 (Reserved) of the Individual Record contains a value different from "0" (zero).
R78 Error field 5 Individual Record
This code will be used by the chambers when there is a format error in the account number.
R79 Error in field 7 Individual Record
This code will be used by the drawee entity and by the chambers when this field contains a format error or by the Banks when the reported check number is erroneous.
R80 Error field 3 of the Additional Record
This code will be used by the chambers when the information included in this field has been standardized and does not match the necessary data or by the chambers when no information is included in this field.
R82 Missing check
This code will be used by the drawee entity when the physical document is missing.
R87 Invalid currency
This code will be used by the chambers when in field 10 1st byte a data different from "0" or "1" is reported.
R88 Error field 2 Individual Record
This code will be used by the chambers when an erroneous transaction code is reported.
R90 Transaction does not correspond due to non-existence of original transaction This code will be used by the chambers when they receive claims on non-existent checks or by the chambers when they receive rejections on non-existent transactions.
R91 Bank code incompatible with transaction currency This code will be used by the chambers when the entity numbers are not expressed in all cases in the same currency. Example: Originator Entity No + 500 and entity to debit/credit Entity No without adding 500.
R92 Maximum number of deferral orders exceeded This code will be used by the chambers when a drawee entity exceeds the maximum number of deferral orders of checks.
NATIONAL PAYMENTS SYSTEM - CHECKS B.C.R.A.
Section 7 - Record Design.
Version: 1 COMMUNICATION "A" 4281 Validity: 14/01/2005 Page 18
R93 Non-working day
This code will be used by those drawee banks that cannot process the documents received for any branch, in whose plaza there is a local holiday. For the case of truncation, this code will be used for the rejection of the corresponding transaction.
R94 Incorrect postal code
This code will be used by the drawee entity when the postal code (field 8 of the individual record) is incorrect.
R96 Depositary entity errors
This code will be used by the entities in the case that the bank stamp is missing, the banking responsibility signature is missing, and when a second presentation does not correspond.
New rejection reasons for transactions will be added to this list.
Counter of original transaction record.
This field carries the record counter of the transaction that is being rejected.
Communication Number.
This field will include the communication number of the entity's rejection to the BCRA in its 6 positions.
Communication Number
This field will include the Communication Number of the Entity's rejection to the BCRA in its 6 positions.
Entity of the original transaction.
It is completed with the entity and branch code in four positions of who generates the rejection.
Other rejection reasons.
Other rejection reasons may be indicated, which must be left-aligned respecting the following rule:
NATIONAL PAYMENTS SYSTEM - CHECKS B.C.R.A.
Section 7 - Record Design.
Version: 1 COMMUNICATION "A" 4281 Validity: 14/01/2005 Page 19
7.5. Individual record of claim presentation and claim rejection.
| Field | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Name | Record Type | Depositary Bank | Drawee Bank | Drawee Branch | Postal Code | Check Number | Account Number | Amount | Comp. Date | Check Date | Reserved | Transaction Type | Reserved | Exchange Point | Claim Data | Reserved |
| Field Requirement | M | |||||||||||||||
| Type | Numeric | Alphan. | Numeric | |||||||||||||
| Length | 1 | 3 | 4 | 8 | 11 | 10 | 6 | 6 | 15 | 1 | 53 | 4 | 1 | 3 | ||
| Position | 01-01 | 02-04 | 05-07 | 08-10 | 11-14 | 15-22 | 23-33 | 34-43 | 44-49 | 50-55 | 56-70 | 71-71 | 72-124 | 125-128 | 129-129 | 130-132 |
Identification of record type:
0 Claim Presentation
9 Claim Rejection
Depositary Bank:
It will be completed with the depositary bank code in 3 positions included in positions 81 to 83 of the NACHA individual record of the check in its presentation.
Drawee Bank:
It will be completed with the drawee bank code in 3 positions included in positions 5 to 7 of the NACHA individual record of the check in its presentation.
Drawee Branch:
It will be completed with the drawee branch code in 3 positions included in positions 8 to 11 of the NACHA individual record of the check in its presentation.
Postal Code:
Positions 57 to 60 of the NACHA individual record of the check in its presentation will be used.
NATIONAL PAYMENTS SYSTEM - CHECKS B.C.R.A.
Section 7 - Record Design.
Version: 1 COMMUNICATION "A" 4281 Validity: 14/01/2005 Page 20
Check Number:
It will be completed with the check number in 8 positions included in positions 47 to 54 of the NACHA individual record of the check in its presentation.
Account Number:
It will be completed with the account number in 11 positions included in positions 19 to 29 of the NACHA individual record of the check in its presentation.
Amount:
Positions 30 to 39 of the NACHA individual record of the check in its presentation will be used.
Compensation Date:
It is the maturity or compensation date of the claim. Eighth business day of the claim presentation. Format YYMMDD.
Check Date:
It is the presentation date of the document being claimed. Format YYMMDD.
Reserved:
It will be completed with 15 zeros.
Transaction Type:
0 Claim Presentation
1 Non-existent account
2 Invalid account number
3 Check already delivered
4 Incorrect amount
5 Duplicate transaction
6 Incorrect presentation date
7 Non-existent check.
NATIONAL PAYMENTS SYSTEM - CHECKS B.C.R.A.
Section 7 - Record Design.
Version: 1 COMMUNICATION "A" 4281 Validity: 14/01/2005 Page 21
Reserved:
For both the presentation and the rejection of the claim, it shall be completed with spaces to the right to cover the 53 positions of that field.
Exchange Point:
It will be completed with the exchange point code in 4 positions included in positions 61 to 64 of the NACHA individual record of the check in its presentation.
Claim Data:
0 Original
1 Image
Reserved:
It will be completed with zeros.
NATIONAL PAYMENTS SYSTEM - CHECKS B.C.R.A.
Section 7 - Record Design.
Version: 1 COMMUNICATION "A" 4281 Validity: 14/01/2005 Page 22
7.6. Individual record of image presentation control and image rejection.
| Field | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Name | Record Type | Depositary Bank | Drawee Bank | Drawee Branch | Postal Code | Check Number | Account Number | Amount | Comp. Date | Check Date | Reserved | Transaction Type | Reserved | Exchange Point | Claim Data | Reserved |
| Field Requirement | M | |||||||||||||||
| Type | Numeric | Alphan. | Numeric | |||||||||||||
| Length | 1 | 3 | 4 | 8 | 11 | 10 | 6 | 6 | 15 | 1 | 53 | 4 | 1 | 3 | ||
| Position | 01-01 | 02-04 | 05-07 | 08-10 | 11-14 | 15-22 | 23-33 | 34-43 | 44-49 | 50-55 | 56-70 | 71-71 | 72-124 | 125-128 | 129-129 | 130-132 |
Record Type:
1 Presentation of the claimed image
2 Rejection of image
Depositary Bank:
It will be completed with the depositary bank code in 3 positions included in positions 2 to 4 of the claim presentation record.
Drawee Bank:
It will be completed with the drawee bank code in 3 positions included in positions 5 to 7 of the claim presentation record.
Drawee Branch:
It will be completed with the drawee branch code in 3 positions included in positions 8 to 10 of the claim presentation record.
Postal Code:
Positions 11 to 14 of the claim presentation record will be used.
NATIONAL PAYMENTS SYSTEM - CHECKS B.C.R.A.
Section 7 - Record Design.
Version: 1 COMMUNICATION "A" 4281 Validity: 14/01/2005 Page 23
Check Number:
It will be completed with the check number in 8 positions included in positions 15 to 22 of the claim presentation record.
Account Number:
It will be completed with the account number in 11 positions included in positions 23 to 33 of the claim presentation record.
Amount:
Positions 34 to 43 of the claim presentation record will be used.
Compensation Date:
Date of the claim compensation. Positions 44 to 49 of the claim presentation record will be used.
Check Date:
Date of presentation of the document being claimed. Positions 50 to 55 of the claim presentation record will be used.
Reserved:
It will be completed with 15 zeros.
Transaction Type:
It will be used
0 For the presentation of the claimed image.
1 For the rejection of the image because the front and back of the same check do not correspond.
2 For the rejection of an image because it is illegible.
3 For the rejection of an image that does not correspond.
4 For the rejection of an image because it is incomplete.
Image Name/Reserved
-For the presentation of the claimed image, it will be completed with the name of the same or pointer associated with the control record, with the format Line-of-scan.TIF (29 characters of the CMC7, without the document type nor the amount). -For the rejection of the image, it will be completed with spaces to the right to cover the positions of this field.
NATIONAL PAYMENTS SYSTEM - CHECKS B.C.R.A.
Section 7 - Record Design.
Version: 1 COMMUNICATION "A" 4281 Validity: 14/01/2005 Page 24
Exchange Point:
It will be completed with the exchange point code in 4 positions included in positions 125 to 128 of the claim presentation record.
Claim Data:
Fixed "1"
Reserved:
It will be completed with zeros.
Section 7 - Record Design.
Version: 1 COMMUNICATION "A" 4281 Validity: 14/01/2005 Page 25
| Field | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | ||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Name | Record Identifier | Transaction Code | Destination Entity | Reserved | Affected Account | Amount | Check Number / Date of original transaction presentation | Rejection Data / Postal Code | Exchange Point | Additional Transaction Information | Additional Records | Record Counter | ||
| Field Requirement | M | |||||||||||||
| Type | '6' | Numeric | Numeric | '0' | Numeric | Numeric | $$$$$$$ | $cc | Numeric | Numeric | Alphanumeric | Alphanumeric | Numeric | Numeric |
| Length | 1 | 2 | 8 | 1 | 17 | 10 | 15 | 6 | 16 | 2 | 1 | 15 | ||
| Position | 01-01 | 02-03 | 04-11 | 12-12 | 13-29 | 30-39 | 40-54 | 55-60 | 61-76 | 77-78 | 79-79 | 80-94 |
Field Descriptions:
Record Identifier.
6 Individual Record
Transaction Code.
This code indicates the type of transaction.
Section 7 - Record Design.
Version: 1 COMMUNICATION "A" 4281 Validity: 14/01/2005 Page 26
Destination Entity.
This field contains the identifying number of the entity receiving the record.
Reserved
This field is reserved for future use. This field is filled with zeros ("0").
Affected Account
This field indicates the affected account and must contain the exact data thereof. It includes numbers from 0 to 9, aligned to the right.
Amount.
This field indicates the amount of the check being rejected.
Check Number / Date of original transaction presentation.
This field contains the check number and the date of presentation of the original transaction and will be completed as follows:
Rejection Data / Postal Code.
This field will be completed with the rejection data and the postal code according to the following description:
The first two positions will be arranged as indicated below:
It will be completed with any of the available rejection reasons for the drawn entity, excluding the letter "R".
Section 7 - Record Design.
Version: 1 COMMUNICATION "A" 4281 Validity: 14/01/2005 Page 27
In the last 4 (four) positions, the postal code of the receiving entity is indicated, through which the destination location is identified.
Exchange Point.
This field contains the identification of the exchange point where the physical document is presented, and will be completed as follows: the first 4 positions will be filled with the identifying code of the exchange point (case 1: with two zeros and the exchange code -two positions-, case 2: with the postal code of the exchange point -four positions-). When out-of-exchange rejections are reported, it will be filled with "0000" and spaces to the right.
Additional Transaction Information.
This field allows identifying the currency of the affected account and the type of transaction being reported.
The first position of this field will contain the type of currency of the affected account:
Additional Records.
This field indicates whether there are additional records ('1' or '0' respectively).
Record Counter ("Trace number")
This field includes the origin entity's identification number in 8 positions (4 for the entity and 4 for the branch) and then in positions 9 to 15 a unique ascending sequential number for each record sent in a file. This implies that the record counter number cannot be repeated in different files. These 15 positions must be ordered sequentially within each batch. In the event that an entity represents another for the presentation of checks, the branch number will be replaced by a "9" in the fifth position and the number of the represented entity in the following positions.
Section 7 - Record Design.
Version: 1 COMMUNICATION "A" 4281 Validity: 14/01/2005 Page 28
Additional Comments:
When a field has more characters than required to complete the information, they must be filled with zeros starting from the left margin, in the case of numeric fields, and with blanks to the right in the case of alphanumeric fields. Alphabetic characters must always be reported in uppercase.
Section 7 - Record Design.
Version: 1 COMMUNICATION "A" 4281 Validity: 14/01/2005 Page 29
| Field | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 |
|---|---|---|---|---|---|---|---|---|
| Name | Record Identifier | Additional Record Type Code | First Rejection Reason | Original Transaction Record Counter | Reserved | Entity of the Original Transaction | Other Rejection Reasons | Record Counter |
| Field Requirement | M | N/A | M | O | M | |||
| Type | '7' | '99' | Alphanumeric | Numeric | Alphanumeric | Numeric | Alphanumeric | Numeric |
| Length | 1 | 2 | 3 | 15 | 6 | 8 | 44 | 15 |
| Position | 01-01 | 02-03 | 04-06 | 07-21 | 22-27 | 28-35 | 36-79 | 80-94 |
Field Descriptions:
Record Identifier.
7 Additional Record.
Additional Record Type Code.
This code indicates the type of additional record. In this case, the code '99' is used.
Rejection Reason.
This field describes the reason why a transaction is rejected by means of using a code:
Section 7 - Record Design.
Version: 1 COMMUNICATION "A" 4281 Validity: 14/01/2005 Page 30
| Code | Transaction | Description | Explanation |
|---|---|---|---|
| R41 | Out-of-exchange Rejections | Non-existent Check | This code will be used when the indicated check does not exist. |
| R42 | Out-of-exchange Rejections | Acceptance of out-of-exchange rejection | This code will be used when the out-of-exchange rejection is accepted. |
| R43 | Out-of-exchange Rejections | Non-acceptance of out-of-exchange rejection | This code will be used when the out-of-exchange rejection is not accepted. |
| R82 | Out-of-exchange Rejections | Missing Check | This code will be used when the check for the rejection is missing. |
Original Transaction Record Counter.
This field carries the record counter of the original transaction (Record Counter of the claim).
Reserved
This field is reserved for future use. It is completed with blank spaces.
Entity of the Original Transaction.
This field contains the identification of the entity originating the rejection/response.
Other Rejection Reasons.
This field describes other reasons, in addition to the main one, for which a transaction is rejected. The codes to be used are the same detailed above.
Section 7 - Record Design.
Version: 1 COMMUNICATION "A" 4281 Validity: 14/01/2005 Page 31
Additional Comments:
When a field has more characters than required to complete the information, they must be filled with zeros starting from the left margin, in the case of numeric fields, and with blanks to the right in the case of alphanumeric fields. Alphabetic characters must always be reported in uppercase.
Section 7 - Record Design.
Version: 1 COMMUNICATION "A" 4281 Validity: 14/01/2005 Page 32
| Field | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| Name | Record Identifier | Transaction Class Code | Total Number of Individual / Additional Records | Control Totals | Total Sum of Batch Debits | Total Sum of Batch Credits | Reserved | Reserved | Reserved | Origin Identification | Batch Number |
| Field Requirement | M | N/A | M | M | |||||||
| Type | '8' | '200' | Numeric | Numeric | $$$$$$$$ $$cc | $$$$$$$$ $$cc | Alphanumeric | Alphanumeric | Blank | Numeric | Numeric |
| Length | 1 | 3 | 6 | 10 | 12 | 12 | 10 | 19 | 6 | 8 | 7 |
| Position | 01-01 | 02-04 | 05-10 | 11-20 | 21-32 | 33-44 | 45-54 | 55-73 | 74-79 | 80-87 | 88-94 |
Field Descriptions:
Record Identifier.
8 Batch End Control
Transaction Class Code.
This code identifies a general classification of the type of transactions included in the batch:
Number of Individual and Additional Records.
This field contains the total number of individual and additional records that exist in the batch.
Section 7 - Record Design.
Version: 1 COMMUNICATION "A" 4281 Validity: 14/01/2005 Page 33
Control Totals.
This field contains the sum of the "Entity to be debited/credited" field of the individual records of the batch.
Total Sum of Batch Debits.
This field contains the sum of the amounts of the debits included in the batch. In the event that the sum exceeds the number of available characters, another batch must be generated.
Total Sum of Batch Credits.
This field contains the sum of the amounts of the credits included in the batch. In the event that the sum exceeds the number of available characters, another batch must be generated.
Reserved.
This field is reserved for future use.
Reserved.
This field is reserved for future use.
Reserved.
This field is reserved for future use.
Identification of the Origin Entity.
This field contains the identifying number of the origin entity of the record (The entity number is included with 4 characters and the branch number with 4 characters).
Batch Number
This field contains the batch number, determined by the origin entity, which must be ascending.
Additional Comments:
Section 7 - Record Design.
Version: 1 COMMUNICATION "A" 4281 Validity: 14/01/2005 Page 34
When a field has more characters than required to complete the information, they must be filled with zeros starting from the left margin, in the case of numeric fields, and with blanks to the right in the case of alphanumeric fields. Alphabetic characters must always be reported in uppercase.
Section 7 - Record Design.
Version: 1 COMMUNICATION "A" 4281 Validity: 14/01/2005 Page 35
| Field | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 |
|---|---|---|---|---|---|---|---|---|
| Name | Record Identifier | Number of Batches | Number of Blocks | Total Number of Individual and Additional Records | Control Totals | Total Sum of File Debits | Total Sum of File Credits | Reserved |
| Field Requirement | M | N/A | ||||||
| Type | '9' | Numeric | $$$$$$$$$$ cc | $$$$$$$$$$ cc | Blank | |||
| Length | 1 | 6 | 6 | 8 | 10 | 12 | 12 | 39 |
| Position | 01-01 | 02-07 | 08-13 | 14-21 | 22-31 | 32-43 | 44-55 | 56-94 |
Field Descriptions:
Record Identifier.
This code is assigned to identify the type of record:
Number of Batches.
This field contains the total number of batches contained in the file.
Number of Blocks.
Section 7 - Record Design.
Version: 1 COMMUNICATION "A" 4281 Validity: 14/01/2005 Page 36
This field contains a total of blocks of the file. A block is composed of 940 characters, that is, 10 records would form a block. For this count, all records are considered, from the file header to the file end control. When the number of records is not a multiple of 10, this total will be calculated as follows:
Number of Individual and Additional Records. This field contains the total number of individual and additional records that exist in the file.
Control Totals.
This field contains the sum of the "Control Totals" field of the control records of all batches.
Total Sum of File Debits.
This field contains the sum of the amounts of the debits included in the file. In the event that the sum exceeds the number of available characters, another file must be generated.
Total Sum of File Credits.
This field contains the sum of the amounts of the credits included in the file. In the event that the sum exceeds the number of available characters, another file must be generated.
Reserved
This field is reserved for future use.
Additional Comments:
When a field has more characters than required to complete the information, they must be filled with zeros starting from the left margin, in the case of numeric fields, and with blanks to the right in the case of alphanumeric fields. Alphabetic characters of the alphanumeric fields must always be reported in uppercase.
Section 7 - Record Design.
Version: 1 COMMUNICATION "A" 4281 Validity: 14/01/2005 Page 37
| Transaction | File Header | Batch Header | Batch Header | Check Field 3 (2 byte) | Check Field 6 | Check Field 7 | Check Field 2 | Check Field 10 |
|---|---|---|---|---|---|---|---|---|
| Presentation of checks and other compensable documents. | ||||||||
| Drawee entity rejection. | ||||||||
| Depositary entity rejection. | ||||||||
| Adjustment. | ||||||||
| Adjustment rejection. | ||||||||
| Out-of-exchange rejection. | ||||||||
| Out-of-exchange rejection response. | ||||||||
| TRC | 27 | 0 | ||||||
| REVERSAL | 26 | 1 | ||||||
| 22 | 4 | |||||||
| 27 | 4 | |||||||
| 26 | ||||||||
| 28 | ||||||||
| 26 |
B.C.R.A.
Version: COMMUNICATION "A" 4281
Validity: 14/01/2005
Page
ORDERED TEXT ORIGIN STANDARD Observations
| Point | Paragraph | Com. | Annex or Chapter | Point | Paragraph |
|---|---|---|---|---|---|
| 1.1 | "A" 2559 | Checks | |||
| 2.1. | "A" 2559 | " | |||
| 2.2. | "A" 2559 | " | |||
| 2.3 | "A" 2559 | " | 2.3.1. S/Com. 4281 | ||
| 2.4 | "A" 2559 | " | |||
| 3.1 | "A" 2559 | " | 3.1.3 S/Com. "A" 2795 | ||
| "A" 2559 | " | 3.1.4 S/Com. "A" 2795 and 4281 | |||
| 3.2. | "A" 2559 | " | 3.2.7 S/Com. "A" 4281 | ||
| "A" 2559 | " | 3.2.8. S/Com. "A" 4281 | |||
| 3.3. | "A" 2559 | " | 3.3.7 S/Com "A" 4281 | ||
| 4.1 | "A" 2559 | " | S/Com. "A" 4281 | ||
| 4.2. | "A" 2559 | " | |||
| 4.3. | "A" 2559 | " | S/Com. "A" 4281 | ||
| 5.1. | "A" 2559 | " | |||
| 5.2. | "A" 2559 | " | |||
| 6.1. | A" 2559 | " | |||
| 6.2. | A" 2559 | " | |||
| 7.1. | "A" 2559 | " | |||
| 7.2. | "A" 2559 | " | S/Com. "A" 2723 | ||
| 7.3. | "A" 2559 | " | S/Com. ”A” 2795 and 2857 | ||
| 7.4. | "A" 2559 | " | S/Com. "A" 2819 and 4281 | ||
| 7.5 | "A" 2559 | " | S/Com. "A" 4281 | ||
| 7.6. | "A" 2559 | " | S/Com. "A" 4281 | ||
| 7.7. | "A" 2559 | " | |||
| 7.8. | "A" 2559 | " | |||
| 7.9. | "A" 2559 | " | |||
| 7.10. | "A" 2559 | " |
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.
A newer document in RegAlert amends this one; it applies as amended.
“2.3.1. S/Com. “A” 4281.”
Amended 1 time · last 2005-08-22
More like this from BCRA
BCRA published 13 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 reviewed before publication; the authoritative text is the regulator's original document. How RegAlert works
In RegAlert: added · updated