Rule · BCRA · 16 Jan 1998 · A 2654
Financial entities and clearing houses must achieve "year 2000" compatibility in critical systems by 31.12.98 and complete final tests by 30.6.99; their Commissions must inventory hardware and software, plan, test, prepare contingency plans, report monthly to the board, and ensure internal and external audits report, with the external audit's plan opinion due 31.3.98 and final evaluation 31.8.99. Monthly reports to the Systems Audit Management of Financial Entities become quarterly, next due 10 April 1998, signed by the Commission President and Systems Manager; entities must notify BCRA of Commission members within ten calendar days.
CENTRAL BANK OF THE ARGENTINE REPUBLIC
__________________________________________________________________ COMMUNICATION " A " 2654 16/01/98 __________________________________________________________________
TO FINANCIAL INSTITUTIONS:
Ref.: Circular
RUNOR 1 - 257.
Adaptation of computer sys- tems for their use as of the year 2000 (Communication "A" 2564)
We address you in relation to the subject of the reference and with the purpose that the financial system be duly prepared to face the challenge imposed by the arrival of the year 2000.
With respect to the vision of this problem, it is highlighted that through Communication "A" 2564 the financial system has been alerted about the need to analyze the impact of the "year 2000" on its computer systems and associated technologies, and to adopt the measures conducive to making them "Year 2000 compliant".
Through this communication the scope of the approach is broadened and aspects that may require special attention are specified. It also describes the supervision strategy that the Superintendency of Financial and Exchange Institutions (SEFyC) will follow to verify the planning and execution process of this project, which involves both third-party data processing service providers and "software" and "hardware" providers.
In that order, it is reiterated that the Central Bank's concern responds to the need to fully understand the implications of this situation that places the technology industry before the greatest crisis it has experienced in its 50-year history, which has already shown that systems have begun to fail when operations go beyond the year 1999.
This is because many of those systems store the year in a two-digit format instead of four, which means that, as the end of 1999 approaches, virtually all systems will have the impact of the problem, given that computer data are normally defined in databases, files and programs with a Year/Month/Day format (YYMMDD), or with some other variation of that format.
In this regard, it is recalled that, when most computer systems were created, their designers defined date-related data in two-digit years, instead of four, to save the costly storage space that this implied at that time, which determines that, in most computer systems existing today, the year "1997" is stored as "97".
Consequently, as of "31 December 1999", when a program compares one date with another, the concept of time management in the computer will be distorted, since the year "00" (2000) will be interpreted as earlier than the year "99" (1999) and, moreover, it will deduce that there is a difference of 99 years between one and the other.
On the other hand, we stress to you that the problem is not only oriented to computer systems but also affects many devices that contain electronic "chips" with internal programming, as is the case of automatic controls for opening vaults (treasuries), personnel access controllers, "fax" machines, telex machines, telephone exchanges, etc.
In turn, it can also cause effects in the administrative support tasks of banking activity, for example: forms that have pre-printed the digits of the century "19..", as is the case of many checks and other instruments.
Likewise, we point out to you that despite the risks that this issue implies, a series of erroneous assessments are usually made when facing it, such as for example:
"It is only a technical problem, which is solved with insignificant fixes"
"We still have plenty of time"
"The systems will be replaced before 2000"
"It complies with 2000, since all applications are new"
"An automatic program conversion solution will be used and everything will be solved"
"The entire conversion process will be given to an external provider"
In that sense, awareness must be raised that the "year 2000" problem is real and affects the entire financial system, since it can cause effects before it arrives and, even more, before the solution processes have been completed, regarding which many experts believe that even the best-prepared organizations will encounter some implementation problems.
In that context, the SEFyC wants to ensure that the entities and clearing houses that make up the financial system can avoid serious disruptions and will work together with the financial system to achieve that goal.
To that end, a plan designed to:
increase awareness in the financial system about the "year 2000" problem;
carry out an evaluation of the efforts made by the entities to plan its solution, and
carry out supervision of the execution of said planning.
In annexes, the strategy for project management and for the Commission referred to in Communication "A" 2564 is detailed, as well as the review mechanisms that, at a minimum, the entities must apply.
In another order, regarding the intervention of the external Audit in this matter, it has been resolved to replace the certification requirement provided in the Annex to Communication "A" 2564 with the requirement of reports in accordance with the provisions of "Evaluation by the external audit" (Point 2.9. of Annex I to this Communication).
Likewise, we reiterate to you that the deadline to achieve "year 2000" compatibility in systems and associated technologies is 31.12.98 and, for final tests on the adaptation of systems to the new requirements, 30.6.99.
Finally, we inform you that shortly you will be sent -through the CONAU ordering- complementary information about the scope of the tests that the internal and external audits must carry out.
We greet you very attentively.
CENTRAL BANK OF THE ARGENTINE REPUBLIC
Alfredo A. Besio
Ruben A. Escobar
Manager of Standards for
Manager of Systems Audit
Financial Entities of Financial Entities
(WITH COPY TO EXCHANGE HOUSES, AGENCIES, OFFICES AND BROKERS AND FUND CLEARING HOUSES)
+----------+---------------------------------------+-------------+ I B.C.R.A. I COMPUTER SYSTEMS FROM YEAR IAnnex I to I I I
2000. PROJECT STRATEGY ICom. "A" 2654I
+----------+---------------------------------------+-------------+
The "year 2000" problem presents important challenges for the managements of the entities and clearing houses that make up the financial system. The computer systems and technologies associated with the operations of the banking industry are often complex and have been developed over many years, based on a variety of programming languages and "hardware" platforms.
The project will require the commitment and participation of the executives, as well as an effective management process. It should begin with a deep and clear awareness of the issue at all levels of the organization and continue with an adequate evaluation involving the following items:
Inventory of "hardware" and "software".
Conversion analysis.
Detailed project planning.
Tests and verifications.
Contingency actions.
External interrelations with the entity, such as:
Suppliers of "software", "hardware" and services.
Data exchange with other organizations and companies.
"Year 2000 compatible" project of client companies.
Monthly report to the Board of Directors.
Evaluation by internal audit.
Evaluation by external audit.
All these activities must be supervised by the internal/external audit and by the responsible Commission, which must keep a "book of minutes", in which, in addition to listing its members, the content of all meetings must be recorded (the topics discussed; the participants in them; the decisions taken or to be taken that affect the project in general; the progress, modifications and/or deviations of the project, etc.) and the reports of the internal and external audits, the information received and/or delivered to the SEFyC and any other information that affects the project will be transcribed.
In the event that the recording of some topics requires supporting annexes, these must be recorded and be available upon request.
The reports that must be made and sent to the Systems Audit Management of Financial Entities on a monthly basis, according to Communication "A" 2564, will become quarterly. The due date for the next submission is 10 April 1998. These reports, like all other information issued to the BCRA related to the topic, must be signed by the President of the Commission (a member of the Board of Directors) and the Systems Manager.
The entities and clearing houses must inform the BCRA of the names, functions and hierarchy of the members of the Commission, as well as any modifications that take place, within ten (10) calendar days of its constitution and/or modification, as applicable.
At a minimum, all "hardware", "software", networks, automatic teller machines and any other processing support must be identified and documented. This inventory must go beyond computer systems and include those elements whose operation depends on incorporated "microchips", such as security systems, telex, vaults (treasuries), etc.
Once the inventory is constituted, a priority analysis must be developed based on the critical status presented by each of the components.
Once the impact of this problem on each component is determined, the different feasible solution options for each of the components must be analyzed and documented (adaptation, replacement thereof, etc.)
The Commission must formally document and plan all aspects of the project, taking into account the effects of the problem on other strategic business initiatives. The following must be considered: the potential effect on existing systems, which may arise in mergers with other entities and/or acquisitions; systems under development; system interrelations and acquired systems.
They must also establish the resource needs, the schedule and the sequence of efforts to apply to the project.
The necessary resources must include properly trained personnel, contractors, supplier support, budget allocation and "hardware" capacity.
This phase must clearly determine the responsibility and scope of third parties within the project, defining requirements for reports, controls and notifications. The deadline to achieve "year 2000" compatibility in critical systems and associated technologies, such as: current accounts, savings accounts, fixed-term deposits, information to the BCRA, accounting, loans, etc. and in the "hardware" and "software" base for their processing, is 31.12.98 and, for the final tests on the adaptation of the systems to the new requirements, 30.6.99.
It must be verified that the changes or replacements in the "hardware" and "software" components have been made. In addition, it must be tested with the participation of the users and the internal audit, that these changes have not affected the original functionality.
The Commission must establish controls to ensure that the effective and timely verification of all "hardware" and "software" has been completed before the final implementation.
All levels of testing are required to ensure the correct functioning of the computer system and technologies associated with the "year 2000" compliance, from the individual testing of each component, to ensure that date processing is performed correctly within each program, up to the integration of programs, subroutines, files and interrelations with other applications and/or systems.
These tests must consider different dates in their processes, such as: current, boundary, as well as those of the "year 2000", in order to proceed with verification and final acceptance. They must also consider the possible effects of the day 9.9.99 since the integration with 9 of a field is usually used as a special indicator.
The Commission must develop contingency plans for all critical operations that could register failures in the processes once the "year 2000" has begun.
a) Suppliers of "software", "hardware" and services.
The SEFyC has observed that some entities and clearing houses that make up the financial system, relying on third parties that provide them with data processing services or on the "software" of applications they have acquired, have not taken any measures to verify that their suppliers can satisfactorily face the "year 2000" problem.
The Commission must:
Evaluate the supplier's plans and actively monitor the project's deadlines.
Determine whether the terms of the contract with its suppliers mention "year 2000" compatibility, and if necessary, renegotiate said contracts in order to have this point covered.
Analyze the responsibilities of the suppliers and the vulnerability of its own entity, in case they cannot fulfill their contractual obligations.
Consider alternative services in case the suppliers' solutions or their deadlines are inadequate.
b) Data exchange with other organizations and companies.
The entities must know and coordinate with companies, institutions and regulatory bodies, the different methods of data exchange. Therefore, planning for the "year 2000" must provide sufficient time to verify the effects that the adopted solutions have on data transfers.
c) "Year 2000" project of client companies.
Many client companies depend on computer systems that must be adapted to the "year 2000". Those that have not considered this problem may suffer a disruption in their businesses that leads to significant financial difficulties, even affecting the fulfillment of their obligations.
Financial entities and clearing houses must implement processes to periodically verify the efforts made by their large clients regarding "year 2000" compliance. They must also take this issue into account in the risk analysis they perform on large companies, as well as consider the possibility of including clauses in this regard in their loan documentation.
Monthly, the Commission must submit a report to the board of directors or equivalent authority, keeping it well informed about the degree of progress of the "year 2000" project and the possibility of completing it in a timely and proper manner, indicating the necessary corrective actions and implementation deadlines. These reports must be transcribed in the minute book of the board of directors or equivalent authority.
The Commission must ensure that the entity's internal audit performs the following tasks, in addition to evaluating its reports and taking the corresponding corrective measures, if necessary:
Monthly report, with an opinion on the degree of compliance with BCRA communications related to the "year 2000".
Monthly report, with an opinion on the degree of compliance with the "year 2000" plan.
Performance of adequate substantive and compliance tests, until "year 2000" compatibility is achieved for critical computer systems and associated technologies.
Report with final evaluation on the "year 2000" compatibility of critical computer systems and associated technologies, due no later than 31.7.98.
The Commission must require and pay special attention to the reports of the external audit and take the corresponding corrective measures, if necessary, namely:
Report with an opinion on the "Year 2000" Plan and its deadlines (due no later than 31.3.98).
Quarterly report, with an opinion on the degree of compliance with BCRA communications related to the "year 2000", within 30 (thirty) calendar days of the close of each quarter.
Quarterly report, with an opinion on the degree of compliance with the "year 2000" plan, within 30 (thirty) calendar days of the close of each quarter.
Adequate substantive and compliance tests, until "year 2000" compatibility is achieved for critical computer systems and associated technologies.
Report with final evaluation on the "year 2000" compatibility of critical computer systems and associated technologies, due no later than 31.8.99.
+---------+--------------------------------------+--------------+ I B.C.R.A.I COMPUTER SYSTEMS AS OF I
Annex II
I
I
I YEAR 2000.
REVIEW MECHANISMS.
I to the
I
I
I GENERAL REVIEW QUESTIONNAIRE ICom. "A " 2654I I---------+--------------------------------------+--------------+
This questionnaire is intended to gather macro-level information regarding preparations for the "year 2000" by financial institutions and clearing houses and their computer system providers, which must be answered and sent to the Systems Audit Management of Financial Institutions of the SEFyC, within 10 (ten) calendar days from the issuance of this communication.
The questions are presented for "yes" or "no" answers. However, open-ended answers may be provided to obtain a greater understanding of the capacity of the institution or provider regarding the "year 2000" problem.
1. Are the data processing systems ("hardware", "software" and associated technologies) and telecommunications systems of the institution and/or external providers capable and ready to handle processing in the "year 2000"?
2. Do the institution and/or external providers have a process to solve the "year 2000" problem that includes these basic points?:
Inventory of "hardware" and "software".
Conversion analysis.
Detailed project planning.
Tests and verifications.
Contingency actions.
External interrelations with the institution, such as:
Providers of "software", "hardware" and services.
Data exchange with other organizations and companies.
"Year 2000" project of client companies.
Monthly report to the board of directors or equivalent authority.
Evaluation by internal audit.
Evaluation by external audit.
3. Have the institution and/or external providers given maximum priority to this problem over other computer projects?
4. Has the institution considered the impact that the "year 2000" will have on internal and surrounding systems that depend on embedded "microchips", such as vaults (treasuries), alarm and security systems, telephones, "fax" machines and heating, ventilation and air conditioning systems?
5. Have the institution and/or external providers established a budget for the "year 2000" problem?
6. Have the institution and/or external providers determined whether they have sufficient necessary resources ("hardware", personnel, money, etc.) to ensure the feasibility of the "year 2000" project?
7. Have the institution and/or external providers assigned overall responsibility for the project efforts to the Commission?
8. Have the institution and/or external providers set deadlines, goals and deliverables regarding the tasks for the "year 2000"?
9. Does the project include regular reports and supervision by the "year 2000" Commission?
10. Does the plan of the institution and/or external providers require that the renovation of all critical elements be fully completed before 31.12.98?
11. Do the institution and/or external providers plan to carry out verifications on renovations in progress for critical applications, before 31.12.98?
+---------+--------------------------------------+--------------+ I B.C.R.A.I COMPUTER SYSTEMS FROM I Annex III I I I YEAR 2000. REVIEW MECHANISMS.
I to the
I
I
I DETAILED REVIEW QUESTIONNAIRE I Com. "A" 2564I +---------+--------------------------------------+--------------+
The following review procedures are for general use in all institutions and clearing houses that make up the financial system, and for the data processing centers that provide services to them.
These procedures will make it possible to determine whether the institution has adequately addressed the "year 2000" problem related to computer systems, "hardware", "software" and associated technologies.
The "Part I" procedures are intended for all institutions.
The "Part II" procedures are broader and are intended particularly for those institutions with the capacity to develop their own "software".
Small institutions, especially those that purchase or lease their "hardware" and/or "software" systems from an external provider, could conclude the review procedures at the end of "Part I".
1.1. Determine the degree of compliance with Communication "A" 2564 and complementary communications.
1.2. Determine whether the organization has an effective plan to identify, evaluate and implement solutions for the "year 2000" problem.
1.3. Evaluate the effects of the efforts related to the "year 2000" on the strategic and operational plans of the institution.
1.4. Determine whether the institution has effectively coordinated its capabilities with clients, providers and companies or entities with which it exchanges data, with a view to the "year 2000".
1.5. Verify the soundness of internal controls for the "year 2000" process.
1.6. Determine whether corrective actions are necessary to ensure adequate treatment of the "year 2000" problem.
2.1. Determine the sources of the organization's computer systems (IS), support for "hardware" ("main-frame", "midrange", networks, personal computers) and the corresponding applications, operating "software" system and associated technologies. Highlight whether computer processing is provided internally, externally, or in a combined manner.
2.2. Review prior inspections, audits or consultant opinions regarding the "year 2000" problem.
2.3. Review the Commission's responses to any significant opinion regarding the "year 2000".
2.4. Review the responses to the General Review questionnaire (Annex II).
2.5. Review the monthly memorandum on the degree of progress regarding compliance with the project, according to the last paragraph of Communication "A" 2564 and complementary communications, prepared by the institution.
2.6. Review the supervision strategies.
2.7. Determine the scope of the review on "year 2000", based on the results of the previous steps.
3.1. Determine whether the board of directors or equivalent authority of the organization and its main management levels have full awareness and understanding of the risks and complexity of the "year 2000" problem, through:
a) obtaining and reviewing the minutes of the board of directors or equivalent authority in which the "year 2000" issues have been discussed;
b) obtaining and reviewing the minutes of the Committee.
3.2. Determine whether the Committee has developed a plan to ensure that the organization's computer system is suitable for "year 2000".
3.3. Determine whether the organization's assessment of the "year 2000" problem includes computer-controlled systems, such as: telecommunications systems, automated teller machines, audio response systems and other complementary systems with built-in "microchips", such as vaults (treasuries), alarm and security systems, telephones, "fax" machines and environmental devices.
3.4. Determine whether the entity's Committee maintains continuous communication with its supplier(s), in order to be informed about the progress in the implementation of solutions for "year 2000".
3.5. Determine whether the organization has:
a) Reviewed third-party "software" contracts, in order to identify the risks associated with authorization and with the guarantees in maintenance contracts for "year 2000" processing.
b) Reviewed all external data processing contracts, to determine whether the supplier has obligations regarding "year 2000".
c) Established a certification process to verify that the products or vendors are suitable for "year 2000". If so, describe it.
3.6. Determine whether the Committee has evaluated the financial and operational capacity of its "hardware" and "software" suppliers, regarding providing processing capacity for "year 2000". Highlight the results of said evaluation.
3.7. Determine the current status of the entity's "year 2000" project, including any foreseeable obstacle and the manner in which the Committee plans to address it.
3.8. If it is evident that the entity's systems or those of the supplier or service provider are not fully suitable for "year 2000", determine:
a) Whether all affected applications will have been completely renovated, with tests underway, for critical systems, before 31.12.98.
b) Which are the applications whose renovation will not be complete by 31.12.98.
c) Whether the Committee has anticipated the effects that the non-suitability for "year 2000" before 31.12.98 will cause, both in the organization's strategic and operational plans, and in all systems.
d) The entity's contingency plans to modify the planning in the event of non-compliance with the deadlines established to adapt the "hardware" or "software" systems, in case they are not suitable for "year 2000", by 31.12.98.
e) Whether the entity has contingency plans in case the "hardware" and/or "software" systems do not function correctly on 1.1.2000.
3.9. Determine whether the Committee has discussed with its large client companies the effect of the "year 2000" issues, in order to ensure the capacity that said clients have to fulfill their obligations.
3.10. Determine whether the entity has evaluated with its payment system suppliers the effect of processing capabilities for "year 2000", including:
a) Data transmission systems.
b) Electronic clearing houses
c) Credit card companies and issuance systems.
d) Automated teller machine networks.
e) Electronic data interchange systems.
f) Electronic funds transfer systems.
3.11. Determine whether the Committee has resorted to internal or external audits to verify the soundness of internal controls, in relation to the efforts towards "year 2000".
3.12. Determine whether the Committee is aware of and contemplates the possibility of litigation arising from the "year 2000" problem.
4.1.1. Verify the functional independence of the personnel performing the internal audit, as well as their commitment regarding the review of the efforts made by the organization on the "year 2000" problem.
4.1.2. Review the audit plans and budgets up to 1999 and determine whether the necessary resources are allocated for specific audits related to the "year 2000" problem. Likewise, determine whether the resources allocated to said audits are adequate.
4.1.3. Determine whether the audit is actively involved in the efforts directed towards "year 2000", in order to verify and monitor the effectiveness of the project management process, and whether the Audit Committee communicates this information to the board of directors or equivalent authority.
4.1.4. Review the internal and external audit reports on the "year 2000" project and determine the timeliness and adequacy of their scopes regarding management responses. Likewise, verify whether the audit's follow-up on the actions carried out, in response to its own conclusions of the "year 2000" project, is appropriate.
4.2.1. Based on the discussions and reviews of the minutes of the Committee formed to address the "year 2000" problem, evaluate compliance with the project management process to ensure the adequacy of the entity's computer systems and associated technologies for "year 2000". Highlight whether management has:
a) Conducted an inventory of all "hardware" and "software" systems, including branches abroad.
b) Identified the "hardware" and "software" systems that require modifications for "year 2000".
c) Evaluated the different alternatives for addressing the "year 2000" problem.
d) Identified priorities in "hardware" and "software" systems, in order to ensure that the most critical applications are addressed first.
e) Considered all "software" systems, emphasizing operations and records related to financial intermediation activity, management information, and operating systems.
f) Considered the effects of the "year 2000" problem on mergers and acquisitions of other entities.
g) Reviewed and approved the stages that guarantee completion of the tasks for the "year 2000" in a timely manner.
h) Developed a strategy for verifying the modifications for the "year 2000".
i) Verified that every new system is compliant with the "year 2000".
j) Addressed the establishment and review of an effective internal control system with respect to the "year 2000" efforts.
k) Determined the grouping of systems for their conversion.
l) Considered the role of the "quality assurance" function.
m) Determined the role of end users.
n) Required adequate monitoring of the project, including periodic updates by the Commission.
4.2.2. Determine whether the Commission considered the availability of adequate resources for the "year 2000" initiative, indicating:
a) The type of technical expertise required.
b) The time required to carry out corrective actions.
c) The type and magnitude of the financial resources required, to make all "hardware" ("main-frame", "midrange", networks, personal computers), the corresponding applications and the operating "software" compliant with the "year 2000".
d) Any other resource that is necessary.
4.2.3. Determine whether the organization has people, or can access people, who have sufficient technical capability to make all "hardware" and "software" compliant with the "year 2000", and:
a) in the case of using external resources, whether they have been contracted;
b) if not, what assurance the Commission provides that such resources will be obtained if necessary.
4.2.4. Determine how the board of directors or equivalent authority and the Commission are informed about the progress of the efforts carried out for the "year 2000".
4.2.5. Determine whether the board of directors or equivalent authority and/or the Commission have established clear lines of authority and responsibility for the "year 2000" tasks.
4.2.6. Determine whether the personnel assigned to the "year 2000" project receive sufficient support from the board of directors or equivalent authority and from the Commission.
4.2.7. Review, if applicable, the selection process of every service provider for the "year 2000" and its degree of suitability.
4.2.8. Evaluate the management process of the entity's "year 2000" conversion.
4.3.1. Determine whether the organization has evaluated the capacity of its computer systems ("hardware") to handle all necessary "software" changes.
4.3.2. Determine the method(s) to be used by the organization to resolve the "year 2000" date calculations (for example, conversion to four-position year fields, creation of windows -"windowing"- and others).
4.3.3. Evaluate whether the organization has allocated or will allocate adequate time for the search and verification of errors in all changes made to the "software".
4.3.4. Determine the tools and programming languages that the entity will use.
4.3.5. Indicate whether a common application development platform will be required.
4.3.6. Describe how the organization will maintain effective internal controls over the "software" change processes for the "year 2000" problem.
4.3.7. Determine whether the organization is coordinating modifications and verifying activities with suppliers, service providers and organizations to which it sends, or from which it receives, data.
4.4.1. Review the Commission's evaluations of the forecast of additional resources that are required in operating systems, telecommunications networks (including automated teller machines), and security "software", to handle "year 2000" processing. Describe the results of the evaluations.
4.4.2. Review the evaluation carried out by the organization of the computer resources necessary to test the "year 2000" changes, while daily processing activities are carried out.
4.4.3. Detail the Commission's evaluations regarding the effect of all changes in operating practices, as a consequence of the "year 2000" tasks.
4.4.4. Review and describe the organization's evaluation regarding the "year 2000" compatibility efforts and contingency plans.
4.4.5. Determine whether the organization has committed solid internal controls over operations, as a result of addressing the "year 2000" issues.
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.
RegAlert holds no document that amends or replaces this one. This is not a check that it is in force: confirm with the regulator.
“it has resolved to replace the certification requirement provided in the Annex to Communication "A" 2564 with the requirement of reports in accordance with the provisions of "Evaluation by the external audit" (Point 2.9. of Annex I to this…”
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