Source: https://www.irs.gov/businesses/automated-records
Timestamp: 2019-04-19 02:31:18+00:00

Document:
The purpose of this revenue procedure is to specify the basic requirements that the Internal Revenue Service considers to be essential in cases where a taxpayer's records are maintained within an Automatic Data Processing system (ADP). This revenue procedure updates and supersedes Rev. Proc. 91-59, 1991-2 C.B. 841.
to income, must keep such books or records, including inventories, as are sufficient to establish the amount of gross income, deductions, credits, or other matters required to be shown by that person in any return of such tax or information.
.03 Section 1.6001-1 (e) provides that the books or records required by § 6001 must be kept available at all times for inspection by authorized internal revenue officers or employees, and must be retained so long as the contents thereof may become material in the administration of any internal revenue law.
.04 Rev. Rul. 71-20, 1971-1 C.B. 392, establishes that all machine-sensible data media used for recording, consolidating, and summarizing accounting transactions and records within a taxpayer's ADP system are records within the meaning of § 6001 and § 1.6001-1, and are required to be retained so long as the contents may become material in the administration of any internal revenue law.
(1) The requirements of this revenue procedure pertain to all matters under the jurisdiction of the Commissioner of Internal Revenue including, but not limited to, income, excise, employment, and estate and gift taxes, as well as employee plans and exempt organizations.
(2) The requirements of this revenue procedure are applicable to any sections of the Code that have unique or specific recordkeeping requirements. For example, machine-sensible records maintained by the taxpayer to meet the requirements of § 274 (d) relating to the amount, time, place, and business purpose of a business expense must meet the requirements of this revenue procedure.
(3) Except as otherwise provided in this revenue procedure, all requirements of § 6001 that apply to hardcopy books and records apply as well to machine-sensible books and records that are maintained within an ADP system.
(1) A taxpayer with assets of $10 million or more at the end of its taxable year must comply with the record retention requirements of Rev. Rul. 71-20 and the provisions of this revenue procedure. For purposes of this revenue procedure, a controlled group of corporations, as defined in § 1563, is considered to be one corporation and all assets of all members of the group are aggregated.
• (c) the taxpayer is notified by the District Director that machine-sensible records must be retained to meet the requirements of § 6001.
(3) A Controlled Foreign Corporation (CFC), a domestic corporation that is 25 percent foreign-owned, and a foreign corporation engaged in a trade or business within the United States at any time during a taxable year that maintains machine-sensible records within an ADP system must comply with the requirements of this revenue procedure to satisfy the record-keeping requirements of §§ 964 (c), 982 (d), 6038A(c) (4), and 6038C (and the regulations thereunder).
(4) An insurance company that maintains machine-sensible records within an ADP system to determine losses incurred under § 832 (b) (5) must comply with the requirements of this revenue procedure and Rev. Proc. 75-56, 1975-2 C.B. 596. For this purpose, the machine-sensible records for a particular taxable year include the records for that year and the seven preceding years, all of which must be retained so long as they may become material to the examination of an insurance company's federal tax return.
(5) A taxpayer's use of a third party (such as a service bureau, time-sharing service, value-added network, or other third party service) to provide services (e.g., custodial or management services) in respect of machine-sensible records does not relieve the taxpayer of its recordkeeping obligations and responsibilities under § 6001 and this revenue procedure.
.01 An "ADP system" consists of an accounting and/or financial system (and subsystems) that processes all or part of a taxpayer's transactions, records, or data by other than manual methods. An ADP system includes, but is not limited to, a mainframe computer system, stand-alone or networked microcomputer system, Data Base Management System (DBMS), and a system that uses or incorporates Electronic Data Interchange (EDI) technology or an electronic storage system.
• (2) the retrieval of data (e.g., some data base systems processes where the taxpayer chooses not to create a sequential extract (see section 5.02 of this revenue procedure)).
.03 A "DBMS" is a software system that creates, controls, relates, retrieves, and provides accessibility to data stored in a data base.
.04 "EDI technology" is the computer-to-computer exchange of business information.
transferring computerized books and records to an electronic storage media using a technique such as "COLD" (computer output to laser disk), which allows books and records to be viewed or reproduced without the use of the original program. See Rev. Proc. 97-22, 1997-13 I.R.B. 9, for electronic storage system requirements.
.06 A "machine-sensible record" is data in an electronic format that is intended for use by a computer. Machine-sensible records do not include paper records or paper records that have been converted to an electronic storage medium such as microfilm, microfiche, optical disk, or laser disk.
.01 General. (1) The taxpayer must retain machine-sensible records so long as their contents may become material to the administration of the internal revenue laws under § 1.6001-1 (e). At a minimum, this materiality continues until the expiration of the period of limitation for assessment, including extensions, for each tax year. In certain situations, records should be kept for a longer period of time. For example, records that pertain to fixed assets, losses incurred under § 832 (b) (5), and LIFO inventories should be kept for longer periods of time.
• (b) between the total of the amounts in the taxpayer's machine-sensible records by account and the taxpayer's return.
(3) The taxpayer must ensure that its machine-sensible records contain sufficient transaction-level detail so that the information and the source documents underlying the machine-sensible records can be identified.
(4) Ail machine-sensible records required to be retained by this revenue procedure must be made available to the Service upon request and must be capable of being processed.
(5) Except as otherwise required by sections 5.01 (2) or (3) of this revenue procedure, a taxpayer is not required to create any machine-sensible record other than that created either in the ordinary course of its business or to establish return entries. For example, a taxpayer who does not create, in the ordinary course of its business, the electronic equivalent of a traditional paper document (such as an invoice) is not required by this revenue procedure to construct such a record, provided that the requirements of sections 5.01 (2) and (3) are met. For requirements relating to hardcopy records, see section 11 of this revenue procedure.
retained for the Service by, or for, a disposed subsidiary must be retained as otherwise required by this revenue procedure.
.02 DBMS. " (1) A taxpayer has the discretion to create files solely for the use of the Service. For example, a taxpayer that uses a DBMS may satisfy the provisions of this revenue procedure by creating and retaining a sequential file that contains the transaction-level detail from the DBMS and otherwise meets the requirements of this revenue procedure.
(2) A taxpayer that creates a file described in section 5.02 (1) of this revenue procedure must document the process that created the sequential file in order to establish the relationship between the file created and the original DBMS records.
(1) A taxpayer that uses EDI technology must retain machine-sensible records that alone, or in combination with any other records (e.g., underlying contracts, price lists, and price changes), contain all the information that § 6001 requires of hardcopy books and records. For example, a taxpayer that uses EDI technology receives electronic invoices from its suppliers. The taxpayer decides to retain the invoice data from completed and verified EDI transactions in its accounts payable system rather than retain the incoming EDI transactions. Neither the EDI transactions, nor the accounts payable system, contain product descriptions or vendor names. To satisfy the requirements of § 6001, the taxpayer must supplement its EDI records with product code description lists and a vendor master file.
(2) A taxpayer may capture the required detail for an EDI transaction at any level within its accounting system. However, the taxpayer must establish audit trails between the retained records and the taxpayer's books, and between the retained records and the tax return.
(3) Section 11.02 of this revenue procedure provides additional guidance concerning hardcopy requirements related to EDI transactions.
• (4) evidence the authenticity and integrity of the taxpayer's records.
• (4) the charts of accounts and detailed account descriptions.
• (6) evidence that the retained records reconcile to the taxpayer's tax return.
.04 The system documentation must include any changes to the items specified in sections 6.01, 6.02, and 6.03 of this revenue procedure and the dates these changes are implemented.
(4) allow the taxpayer to provide the Service with third-party equipment.
.02 An ADP system must not be subject, in whole or in part, to any agreement (such as a contract or license) that would limit or restrict the Service's access to and use of the ADP system on the taxpayer's premises (or any other place where the ADP system is maintained), including personnel, hardware, software, files, indexes, and software documentation.
.02 The taxpayer's notice must identify the affected records and include a plan that describes how, and in what timeframe, the taxpayer proposes to replace or restore the affected records in a way that assures that they will be capable of being processed. The plan must demonstrate that all of the requirements of this revenue procedure will continue to be met with respect to the affected records.
.03 The District Director will notify the taxpayer of any objection(s) to the taxpayer's plan.
.04 A District Director may consider, whenever warranted by the facts and circumstances, the possibility of requiring less than a total restoration of missing data.
(1) Taxpayer A replaces its general ledger software system with a new general ledger software system with which the original system's records are incompatible. However, A's original records are retrievable and capable of being processed on A's hardware system. A is not required to notify its District Director of the change in its software system because A's records remain capable of being processed.
(2) Taxpayer B replaces its original ADP hardware system with a new system that cannot process the machine-sensible records created and maintained by B's original system. B must notify its District Director of this hardware system change and propose a plan for assuring that the machine-sensible records created and maintained by the original ADP hardware system are capable of being processed. To that end, B considers the following options: (1) having all records in the taxpayer's original system immediately reformatted so that the new system can retrieve and process those records; (2) having all records in its original system reformatted by a designated future date; or (3) having an arrangement with a third - party to process all records in its original system on a compatible system. Any of these options may be acceptable provided the option selected enables the taxpayer to meet the requirements of this revenue procedure with respect to those records. The taxpayer must be able to demonstrate that any third party reformatting or processing is done with the quality controls in place that will ensure the continued integrity, accuracy, and reliability of the taxpayer's records.
(1) The implementation of records management practices is a business decision that is solely within the discretion of the taxpayer. Recommended records management practices include the labeling of records, providing a secure storage environment, creating back-up copies, selecting an offsite storage location, and testing to confirm records integrity.
(3) The NARA standard in 36 C.F.R. § 1234.30 (g) (4) (1996) requires an annual reading of a statistical sampling of magnetic computer tape reels to identify any loss of data and to discover and correct the causes of data loss. In libraries with 1,800 or fewer storage units (e.g., magnetic tape reels), a 20 percent random sampling or a sample size of 50 units, whichever is larger, should be read. In libraries with more than 1,800 units, a sample of 384 units should be read. Although this NARA sampling standard is specifically for magnetic computer tape, the Service recommends that all retained machine-sensible records be sampled and tested as described in the NARA standard.
.02 Partial Loss of Data. A taxpayer that loses only a portion of the data from a particular storage unit will not be subject to the penalties described in section 12 of this revenue procedure if the taxpayer can demonstrate to the satisfaction of the District Director that the taxpayer's data maintenance practices conform with 36 C.F.R. § 1234.30 (g) (4) (1996) (the NARA sampling standard). However, the taxpayer remains responsible for substantiating the information on its return as required by § 6001.
.01 Record Retention Limitation Agreement.
(1) A taxpayer who maintains machine-sensible records may request to enter into a Record Retention Limitation Agreement (RRLA) with its District Director. This agreement provides for the establishment and maintenance of records as agreed upon by the District Director and the taxpayer.
(2) The taxpayer's request must identify and describe those records the taxpayer proposes not to retain and explain why those records will not become material to the administration of any internal revenue law. The District Director will notify the taxpayer whether or not the District Director will enter into an RRLA.
(3) In an RRLA, the District Director may waive all or any of the specific requirements in this revenue procedure. A taxpayer remains subject to all the requirements in this revenue procedure that are not specifically modified or waived by an RRLA.
(4) Unless an RRLA otherwise specifies, an RRLA shall not apply to accounting and tax systems added subsequent to the completion of the record evaluation upon which the agreement is based. All machine-sensible records produced by a subsequently added accounting and tax system, the contents of which may be or may become material in the administration of the Code must be retained by the taxpayer signing the RRLA until a new evaluation is conducted by the District Director.
the acquired subsidiary until the District Director either revokes the former RRLA (in whole or in part) or enters into a new RRLA that applies to the acquired subsidiary.
(6) Upon the disposition of a subsidiary, the files being retained for the Service pursuant to an RRLA by, or for, the disposed subsidiary must be retained by the taxpayer until a new evaluation is conducted by the District Director.
(7) A District Director's decision to revoke an RRLA, or not to enter into an RRLA, does not relieve the taxpayer of its recordkeeping obligations under § 6001 or its responsibilities described in this revenue procedure.
(1) The District Director may conduct a records evaluation at any time the District Director deems it appropriate to review the taxpayer's record retention practices, including the taxpayer's relevant data processing and accounting systems.
(2) The records evaluation described in section 10.02 (1) of this revenue procedure is not an "examination", "investigation," or "inspection" of the books and records within the meaning of § 7605 (b) of the Code, or a prior audit for purposes of § 530 of the Revenue Act of 1978, 1978-3 (Vol. 1) C.B. 119, as amended by § 1122 of the Small Business Job Protection Act of 1996, because this evaluation is not directly related to the determination of the tax liability of a taxpayer for a particular taxable period.
(3) The District Director will inform the taxpayer of the results of a records evaluation.
1) The District Director may periodically initiate tests to establish the authenticity, readability, completeness, and integrity of a taxpayer's machine-sensible records retained in conformity with this revenue procedure.
(2) These tests may include a review of integrated systems such as EDI or an electronic storage system, and a review of the internal controls and security procedures associated with the creation and maintenance of the taxpayer's records.
(3) The tests described in section 10.03 (1) of this revenue procedure are not an "examination", "investigation," or "inspection" of the books and records within the meaning of § 7605 (b) of the Code, or a prior audit for purposes of § 530 of the Revenue Act of 1978, 1978-3 (Vol. 1) C.B. 119, as amended by § 1122 of the Small Business Job Protection Act of 1996, because these tests are not directly related to the determination of the tax liability of a taxpayer for a particular taxable period.
(4) The District Director will inform the taxpayer of the results of these tests.
46, 1981-2 C.B. 621. Hardcopy records may also be retained in an electronic storage system in conformity with Rev. Proc. 97-22. These records are not a substitute for the machine-sensible records required to be retained by this revenue procedure.
• (3) all the details relating to the transaction are subsequently received by the taxpayer in an EDI transaction and are retained as machine-sensible records by the taxpayer in conformity with this revenue procedure. For example, a taxpayer need not retain credit card receipts generated at the time of a transaction if all pertinent information on the receipts is subsequently received in an EDI transaction and retained as a machine-sensible record. See section 5.03 of this revenue procedure for requirements relating to EDI.
.03 A taxpayer need not create hardcopy printouts of its machine-sensible records unless requested to do so by the Service. The Service may request such hardcopy printouts either at the time of an examination or in conjunction with the tests described in section 10.03 (1) of this revenue procedure.
The District Director may issue a Notice of Inadequate Records pursuant to § 1.6001-1 (d) if a taxpayer fails to comply with this revenue procedure (including a failure to satisfy the resource requirements of section 7 of this revenue procedure). Failure to comply with this revenue procedure may also result in the imposition of the applicable penalties under subtitle F of the Code, including the § 6662 (a) accuracy related civil penalty and the § 7203 willful failure criminal penalty.
Rev. Proc. 91-59 is modified and superseded for machine-sensible records relating to taxable years beginning after December 31, 1997. However, a taxpayer that complies with this revenue procedure for taxable years beginning prior to that date is treated as having complied with Rev. Proc. 91-59 for those years.
This revenue procedure is effective for machine-sensible records relating to taxable years beginning after December 31, 1997.
.02 Questions regarding the application of this revenue procedure to a specific factual situation should be directed to the appropriate District Director's office.
The collections of information contained in this revenue procedure have been reviewed and approved by the Office of Management and Budget in accordance with the Paperwork Reduction Act (44 U.S.C. 3507) under control number 1545-1595.
The collections of information in this revenue procedure are in sections 8 and 10 of this revenue procedure. This information is required to ensure that machine-sensible records will constitute records within the meaning of § 6001. The collections of information are mandatory for a taxpayer whose machine-sensible records are kept within an ADP system. The likely respondents are individuals, state or local governments, farms, business or other for-profit institutions, federal agencies or employees, nonprofit institutions, and small businesses or organizations.
The estimated total annual recordkeeping burden is 120,000 hours.
The estimated annual burden per recordkeeper will vary from 20 hours to 60 hours, depending on individual circumstances, with an estimated average of 40 hours. The estimated number of recordkeepers is 3,000.

References: § 6001
 § 6001
 § 1
 § 274
 § 6001
 § 1563
 § 6001
 § 832
 § 6001
 § 1
 § 832
 § 6001
 § 6001
 § 1234
 § 1234
 § 6001
 § 6001
 § 7605
 § 530
 § 1122
 § 7605
 § 530
 § 1122
 § 1
 § 6662
 § 7203
 § 6001