(a) General requirements.

1. (1)

   1. (A) Machine-sensible records used to establish tax compliance shall contain sufficient transaction-level detail information so that the details underlying the machine-sensible records can be identified and made available to the Secretary of the Department of Finance and Administration upon request.
   2. (B) A taxpayer has discretion to discard duplicated records and redundant information provided its responsibilities under this part are met.
2. (2) At the time of an examination, the retained records must be capable of being retrieved and converted to a standard record format.

3. (3)

   1. (A) Taxpayers are not required to construct machine-sensible records other than those created in the ordinary course of business.
   2. (B) A taxpayer that does not create the electronic equivalent of a traditional paper document in the ordinary course of business is not required to construct such a record for tax purposes.

(b) Electronic data interchange requirements.

1. (1)

   1. (A) Where a taxpayer uses electronic data interchange processes and technology, the level of record detail, in combination with other records related to the transactions, must be equivalent to that contained in an acceptable paper record.
   2. (B) For example, the retained records should contain such information as vendor name, invoice date, product description, quantity purchased, price, amount of tax, indication of tax status, shipping detail, etc.
   3. (C) Codes may be used to identify some or all of the data elements, provided that the taxpayer provides a method which allows the secretary to interpret the coded information.
2. (2) The taxpayer may capture the information necessary to satisfy subdivision (b)(1) of this section at any level within the accounting system and need not retain the original EDI transaction records provided the audit trail, authenticity, and integrity of the retained records can be established. Example: A taxpayer using electronic data interchange 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 to retain the EDI transactions themselves. Since neither the EDI transaction nor the accounts payable system captures information from the invoice pertaining to product description and vendor name (i.e., they contain only codes for that information), the taxpayer also retains other records, such as its vendor master file and product code description lists and makes them available to the secretary. In this example, the taxpayer need not retain its EDI transaction for tax purposes.

(d) Business process information.

1. (1)

   1. (A) Upon the request of the secretary, the taxpayer shall provide a description of the business process that created the retained records.
   2. (B) Such description shall include the:

(i) Relationship between the records and the tax documents prepared by the taxpayer; and

1. (ii) Measures employed to ensure the integrity of the records.

2. (2) The taxpayer shall be capable of demonstrating the:

   1. (A) Functions being performed as they relate to the flow of data through the system;
   2. (B) Internal controls used to ensure accurate and reliable processing; and
   3. (C) Internal controls used to prevent unauthorized addition, alteration, or deletion of retained records.

3. (3) The following specific documentation is required for machine-sensible records retained pursuant to this part:

   1. (A) Record formats or layouts;
   2. (B) Field definitions (including the meaning of all codes used to represent information);
   3. (C) File descriptions (e.g., data set name); and
   4. (D) Detailed charts of accounts and account descriptions.