Section 50 IAC 26-9-1 - Histories and transaction logsAuthority: IC 6-1.1-31-1; IC 6-1.1-31.5-3.5
Affected: IC 6-1.1-31.5
Sec. 1.
(a) The database system shall be able to generate a historical transaction log for managerial and audit purposes. Reports using history data must do the following: (1) Include the following: (A) The username or user identification.(C) Terminal identification.(2) Accept the following parameters to be specified by the user: (A) User or user identification.(E) Starting and ending dates and times. All transaction logs must allow for generation of totals and summary level information.
(b) Reports using history data must be retrievable from the online database system for a period dating back to the beginning of the assessment year that immediately precedes the last date of the general reassessment. Older transactions and history data must be retained offline in an electronic format if the property tax management system is not capable of maintaining all data online.(c) Historical transaction log data relating to dates not specified in subsection (b), that is purged from the online system, shall be stored offline in a flat ASCII file in machine-readable form. Field and file definitions must also be included with the data in machine-readable form.Department of Local Government Finance; 50 IAC 26-9-1; filed Jan 28, 2011, 3:07 p.m.: 20110223-IR-050100165FRAReadopted filed 10/4/2024, 4:04 p.m.: 20241030-IR-050230833RFA