Florida Administrative Code
12 - DEPARTMENT OF REVENUE
12 - Departmental
Chapter 12-24 - PAYMENT OF TAXES AND SUBMISSION OF RETURNS BY ELECTRONIC MEANS; TAXPAYER RECORDKEEPING AND RETENTION REQUIREMENTS
Part II - TAXPAYER RECORDKEEPING AND RETENTION REQUIREMENTS
Section 12-24.024 - Recordkeeping Requirements - Machine-Sensible Records
Universal Citation: FL Admin Code R 12-24.024
Current through Reg. 51, No. 058, March 25, 2025
(1) General Requirements.
(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 Department upon request. A taxpayer has
discretion to discard duplicated records and redundant information provided his
or her responsibilities under these rules are met.
(b) At the time of an examination by the
Department, the taxpayer's retained records must be capable of being retrieved
and converted to a standard record format.
(c) Taxpayers are not required to construct
machine-sensible records other than those created in the ordinary course of
business. A taxpayer who 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.
(2) Electronic Data Interchange Requirements.
(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. For example, the retained
records should contain information including vendor name, invoice date, product
description, quantity purchased, price, amount of tax, indication of tax
status, and shipping detail. Codes may be used to identify some or all of the
data elements, provided that the taxpayer provides a method which allows the
Department to interpret the coded information.
(b) The taxpayer may capture the information
necessary to satisfy these rules 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. For
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 must retain
other records, such as his or her vendor master file and product code
description lists and make them available to the Department. In this example,
the taxpayer need not retain its EDI transaction for tax
purposes.
(3) Electronic Data Processing Systems Requirements. The requirements for an electronic data processing accounting system should be similar to those of a manual accounting system, in that an adequately designed accounting system should incorporate methods and records that will satisfy the requirements of this chapter.
(4) Business Process Information.
(a) Upon the request of the
Department, the taxpayer shall provide a description of the business process
that created the retained records. Such description shall include the
relationship between the records and the tax documents prepared by the taxpayer
and the measures employed to ensure the integrity of the records.
(b) The taxpayer shall be capable of
demonstrating:
1. The functions being
performed as they relate to the flow of data through the system;
2. The internal controls used to ensure
accurate and reliable processing; and,
3. The internal controls used to prevent
unauthorized addition, alteration, or deletion of retained
records.
(c) The
following specific documentation is required for machine-sensible records
retained pursuant to this rule:
1. Record
formats or layouts;
2. Field
definitions (including the meaning of all codes used to represent
information);
3. File descriptions
(e.g., data set name); and,
4.
Detailed charts of accounts and account
descriptions.
Rulemaking Authority 213.06(1) FS. Law Implemented 213.34, 213.35 FS.
New 10-24-96, Amended 4-30-02.
Disclaimer: These regulations may not be the most recent version. Florida may have more current or accurate information. We make no warranties or guarantees about the accuracy, completeness, or adequacy of the information contained on this site or the information linked to on the state site. Please check official sources.
This site is protected by reCAPTCHA and the Google
Privacy Policy and
Terms of Service apply.