reglab/statecodes huggingface dataset:
Indiana Administrative Code › Title 50 - DEPARTMENT OF LOCAL GOVERNMENT FINANCE › Article 26 - COMPUTER STANDARDS FOR A UNIFORM AND COMMON PROPERTY TAX MANAGEMENT SYSTEM › Rule 18 - Certification › Section 18-3 - Phase II system and integration demonstrations

Current through July 10, 2024
Authority: IC
				  6-1.1-31-1;
				  IC
				  6-1.1-31.5-3.5
Affected: IC 6-1.1-31.5
Sec. 3.
(a) As used
				in this section, "phase II testing" refers to the testing of the integrative
				functionality of the individual components of a property tax management system
				for certification under this article.
(b) Property tax management systems subject
				to certification under section 1 of this rule that utilize assessment and tax
				and billing systems that have been software certified by the department must
				initially be tested and integration validated under this section. Only those
				systems that have been phase I certified during the same certification cycle
				may be eligible for phase II testing. The systems will be tested by the
				department or its designee on a stand-alone PC or a larger system. Combinations
				of vendors or data processing departments shall schedule a testing date with
				the department at least thirty (30) days before submitting the property tax
				management system for test. The department reserves the right to proactively
				coordinate testing dates per the department prescribed time frame allotted for
				phase II testing and reserves the right to conduct the testing session either
				in person or via a virtual environment (e.g., webinar). The test shall include,
				but will not be limited to, the following:
(1)
				Validation that the system incorporates all general system
				requirements.
(2) Generation of
				required reports.
(3) Demonstration
				of the system's ability to perform the annual interface of gross assessed
				values, including the acceptance of state assessed utility and railroad values.
(ii) A successful appeal determination and
				the subsequent recalculation of taxes from the change in value
[sic]
.
(4) Demonstration of the system's ability to
				integrate applicable data from one (1) software to the other, including, but
				not limited to, property transfers, splits, combinations, annexations,
				homestead deduction application, and updated sales prices for ratio study
				purposes.
Indiana Administrative Code › Title 50 - DEPARTMENT OF LOCAL GOVERNMENT FINANCE › Article 26 - COMPUTER STANDARDS FOR A UNIFORM AND COMMON PROPERTY TAX MANAGEMENT SYSTEM › Rule 18 - Certification › Section 18-4 - Phase III initial property tax management system verification and local certification of county installation

Current through July 10, 2024
Authority: IC
				  6-1.1-31-1;
				  IC
				  6-1.1-31.5-3.5
Affected: IC 6-1.1-31.5
Sec. 4.
(a) As used
				in this section, "phase III testing" refers to the testing of the overall
				functionality of a property tax management system that has been installed by a
				county.
(b) Property tax management
				systems subject to certification under section 1 of this rule that utilize
				software that has been software certified by the department and have
				demonstrated successful integration with other software as necessary must
				initially be certified under this section. A county shall submit its proposed
				property tax management system to the department. The department or its
				designee shall consider the proposed system and confirm that all requirements
				and scenarios tested under section 3 of this rule are accomplished by the
				proposed system using the recorded results prescribed under section 3(e) of
				this rule.
(c) If the department or
				its designee finds that a county's proposed system meets all requirements and
				accomplished all scenarios tested under section 3 of this rule, the department
				will verify that a county's proposed property tax management system is eligible
				for phase III testing.
(d) After
				the department has verified that a county's proposed system is eligible for
				phase III testing under subsection (c), a county shall engage an independent,
				private, or a public entity approved by the department, or a member of the
				department, to validate that the installed property tax management system
				complies with the standards and requirements of this article. The department
				reserves the right to proactively coordinate testing dates per the department
				prescribed time frame allotted for phase III testing and reserves the right to
				conduct the testing session either in person or via a virtual environment
				(e.g., webinar).
(e) Once the
				entity conducting the phase III testing finds that the installed property tax
				management system meets the standards and requirements of this article, the
				county shall notify the department in writing that the installed system is in
				compliance. In the event that phase III testing was conducted directly by a
				member of the department and that member finds that the installed property tax
				management system meets the standards and requirements of this article, the
				county is not required to notify the department that the installed system is in
				compliance. The department shall then declare the computer system as locally
				certified for the county where it was independently validated.
Indiana Administrative Code › Title 50 - DEPARTMENT OF LOCAL GOVERNMENT FINANCE › Article 26 - COMPUTER STANDARDS FOR A UNIFORM AND COMMON PROPERTY TAX MANAGEMENT SYSTEM › Rule 18 - Certification › Section 18-6 - Changes in certified systems, rule, or test scenarios; recertification

Current through July 10, 2024
Authority: IC 6-1.1-31-1; IC 6-1.1-31.5-3.5
Affected: IC 6-1.1-4; IC 6-1.1-31.5
Sec. 6
(a) If
				initial certification of a property tax management system is within twenty-four
				(24) months before July 1, 2015, or within twenty-four (24) months before every
				fifth year after July 1, 2015, recertification of that system is not
				required.
(b) Property tax
				management systems not subject to subsection (a) that have been initially
				certified must be recertified within the twenty-four (24) month period before
				July 1, 2015, and within the twenty-four (24) month period before every fifth
				year after July 1, 2015. If any major change is made to a certified system at
				any other time, the system shall be considered a new system subject to the same
				certification requirements of sections 2, 3, and 4 of this rule. As used in
				this section, "major change" has the meaning set forth in
				50 IAC
				26-17-1. In the event that the major change pertains
				exclusively to a county's conversion of its software system, the system will be
				subject to the same certification requirements of just section 4 of this
				rule.
(c) Property tax management
				system installations not subject to subsection (a) that have been initially
				certified must be locally recertified within the twenty-four (24) month period
				before July 1, 2015, and within the twenty-four (24) month period before every
				fifth year after July 1, 2015.
(d)
				If any other change is made to a certified system, the vendor must submit
				revised copies of documentation, revised source code, and other materials to
				the following:
(1) The escrow agent.
(2) The department.
Indiana Administrative Code › Title 50 - DEPARTMENT OF LOCAL GOVERNMENT FINANCE › Article 26 - COMPUTER STANDARDS FOR A UNIFORM AND COMMON PROPERTY TAX MANAGEMENT SYSTEM › Rule 18 - Certification › Section 18-7 - Penalty for noncompliance

Current through July 10, 2024
Authority: IC 6-1.1-31-1; IC 6-1.1-31.5-3.5
Affected: IC 6-1.1-31.5
Sec. 7.
The department may elect not to certify the budget order or
				  impose other sanctions allowed by law for a county that fails to comply with
				  this rule.
Indiana Administrative Code › Title 50 - DEPARTMENT OF LOCAL GOVERNMENT FINANCE › Article 26 - COMPUTER STANDARDS FOR A UNIFORM AND COMMON PROPERTY TAX MANAGEMENT SYSTEM › Rule 19 - Contract Provisions › Section 19-1 - Vendors

Current through July 10, 2024
Authority: IC 6-1.1-31-1; IC 6-1.1-31.5-3.5
Affected: IC 6-1.1-31.5
Sec. 1.
(a) This
				section applies to all vendors.
(b)
				A contract between a vendor and a county must include the following provisions:
(1) An agreement to submit disputes regarding
				the standards required under this article to the designated authority for
				resolution as provided under this article.
(2) An agreement that all disputes not
				covered under subdivision (1) shall be resolved under the laws of
				Indiana.
(3) A guarantee or
				warranty by the vendor that the product covered by the contract meets the
				provisions of this article, and an agreement that any subsequently discovered
				failure to meet the provisions of this article will be corrected at the
				vendor's expense.
(4) An agreement
				that all of the contract provisions shall be binding on all parties to the
				contract and their successors or assigns.
(5) An agreement that the vendor will make
				any product or service change that may be required as a consequence of a change
				in any law, rule, or state board policy statement relating to the computer
				system, provided the vendor is compensated equitably, based on common industry
				rates, as are reasonably agreed to by the parties.
(6) An agreement that all data that is
				entered into, stored, or generated by the property tax management system is the
				sole property of the county operating the property tax management system. The
				vendor retains no ownership or other interest in the data entered into, stored,
				or generated by the property tax management system.
Indiana Administrative Code › Title 50 - DEPARTMENT OF LOCAL GOVERNMENT FINANCE › Article 26 - COMPUTER STANDARDS FOR A UNIFORM AND COMMON PROPERTY TAX MANAGEMENT SYSTEM › Rule 19 - Contract Provisions › Section 19-2 - Assessment software and tax and billing software vendors

Current through July 10, 2024
Authority: IC 6-1.1-31-1; IC 6-1.1-31.5-3.5
Affected: IC 6-1.1-31.5
Sec. 2.
(a) This
				section applies to all assessment software vendors and all tax and billing
				software vendors.
(b) A contract
				between an assessment software vendor and a county or a tax and billing
				software vendor and a county must include the following provisions:
(1) An agreement that the vendor will provide
				a software maintenance agreement that meets the standards prescribed in this
				article.
(2) An agreement that the
				vendor will provide assistance to the county as may be required to modify the
				property tax management system to comply with changes in state law, department
				rules, department policy statements, or this article within the time period
				prescribed by the law, rule, or department.
(3) Should for any reason a county change the
				assessment or tax and billing software or any other part of the computer system
				at:
(A) the end of a contractual
				period;
(B) contract
				termination;
(C) decertification;
				or
(D) failure of recertification;
the vendor of the software shall in no way impede or delay
				  the smooth, orderly, and timely transfer of the county's data from the current
				  database to a new database.
(4) An agreement that the vendor will
				reimburse the county for all costs incurred as a result of the vendor's failure
				to continue to support the assessment software or tax and billing software
				during the life of the maintenance agreement.
(5) An agreement that the contract and the
				escrow agreement both provide for the vendor's documentation and source code to
				be released by the escrow agent to the county when the department, an
				arbitrator, or a court rules that the vendor:
(A) has ceased to provide continued support;
				and
(B) is incapable of resuming
				support.
(6) An
				agreement that, unless the total system installation is:
(A) confirmed by an independent entity;
				and
(B) locally certified by the
				department; the contract is void.
(7) An agreement that, unless the property
				tax management system is recertified and the total system installation is:
(A) confirmed by an independent entity;
				and
(B) locally recertified by the
				department; the contract is void.
(8) An agreement that the contract is void if
				the property tax management system certification is:
(A) denied;
(B) decertified; or
(C) revoked.
(9) An agreement that the contract is void if
				the local certification of the county installation is:
(A) denied;
(B) decertified; or
(C) revoked.
Indiana Administrative Code › Title 50 - DEPARTMENT OF LOCAL GOVERNMENT FINANCE › Article 26 - COMPUTER STANDARDS FOR A UNIFORM AND COMMON PROPERTY TAX MANAGEMENT SYSTEM › Rule 19 - Contract Provisions › Section 19-3 - System maintenance

Current through July 10, 2024
Authority: IC 6-1.1-31-1; IC 6-1.1-31.5-3.5
Affected: IC 6-1.1-31.5
Sec. 3.
Assessment software and tax and billing software vendors must
				  offer a maintenance contract for ongoing maintenance services of the property
				  tax management system that include the following:
(1) Telephone support.
(2) Problem diagnostic support from vendor
				personnel, by any necessary combination of remote and on-site
				services.
(3) System modification
				initiated by the vendor.
(4)
				Services to correct defects in software that are provided at vendor's expense.
All other support shall be provided on terms included in the
				  maintenance contract or other contract between the vendor and the county. No
				  vendor may require a county to accept vendor initiated changes unless those
				  changes are included in the cost of a maintenance contract.
Indiana Administrative Code › Title 50 - DEPARTMENT OF LOCAL GOVERNMENT FINANCE › Article 26 - COMPUTER STANDARDS FOR A UNIFORM AND COMMON PROPERTY TAX MANAGEMENT SYSTEM › Rule 19 - Contract Provisions › Section 19-4 - Disputes

Current through July 10, 2024
Authority: IC 6-1.1-31-1; IC 6-1.1-31.5-3.5
Affected: IC 6-1.1-31.5
Sec. 4.
(a) This
				section applies to all vendors. Disputes between vendors and counties
				concerning whether the assessment software or tax and billing software meets
				the standards established in this article shall be resolved by the department
				in accordance with this section. Disputes concerning other contractual matters
				shall be resolved through arbitration. Nothing in this article shall be
				construed as limiting the rights of disputing parties to pursue action in the
				courts of the state after the procedures of this article have been
				exhausted.
(b) A party to a dispute
				shall file with the department a written petition for conflict resolution. This
				petition shall include the following:
(1) A
				statement that the petitioner is a party to a contract with a vendor for
				assessment software or tax and billing software subject to the provisions of
				this article.
(2) The identity of
				the vendor and the:
(A) property tax
				management system;
(B) assessment
				software; or
(C) tax and billing
				software;
about which the complaint is filed.
(3) An allegation that the:
(A) property tax management system;
(B) assessment software; or
(C) tax and billing software;
fails to meet requirements of this article, stating
				  specifically the ways in which the system is alleged to violate specified
				  provisions.
(4)
				Written proof that a copy of the petition has been delivered to the vendor
				whose system or software is the subject of the dispute.
Indiana Administrative Code › Title 50 - DEPARTMENT OF LOCAL GOVERNMENT FINANCE › Article 26 - COMPUTER STANDARDS FOR A UNIFORM AND COMMON PROPERTY TAX MANAGEMENT SYSTEM › Rule 20 - Property Tax File Format Requirements for 2011-Pay-2012 Data and Forward › Section 20-1 - Purpose of rule

Current through July 10, 2024
Authority: IC 6-1.1-31-1; IC 6-1.1-31.5-3.5
Affected: IC 6-1.1-31.5
Sec. 1.
The purpose of this rule is to prescribe standardized
				  property tax data file formats to enable local government to be able to
				  collect, analyze, store, and share property tax data with the state and to
				  facilitate integration required between all components of a property tax
				  management system. The prescribed file formats must be able to be generated by
				  local officials at any time without vendor intervention or cost to the county.
				  The formats under this rule apply to 2011-pay-2012 and forward.
Indiana Administrative Code › Title 50 - DEPARTMENT OF LOCAL GOVERNMENT FINANCE › Article 26 - COMPUTER STANDARDS FOR A UNIFORM AND COMMON PROPERTY TAX MANAGEMENT SYSTEM › Rule 20 - Property Tax File Format Requirements for 2011-Pay-2012 Data and Forward › Section 20-2 - Instructions

Current through July 10, 2024
Authority: IC
				  6-1.1-31-1;
				  IC
				  6-1.1-31.5-3.5
Affected: IC 6-1.1-31.5
Sec. 2.
(a) Data
				format instructions are as follows:
(1) Each
				file must have a header record and a trailer record in the exact specified
				format with designated "FILENAME" and the word "TRAILER" in
				uppercase.
(2) All fields are fixed
				length.
(3) Left justify all
				alphanumeric fields.
(4) All
				numeric fields must have leading zeros if field value does not utilize all
				available spaces.
(5) Assume no
				decimal precision for all numeric fields without format
				clarification.
(6) All decimal
				precision is implied. For example, for format 3.2, send 12345. It will be read
				as "123.45".
(7) Yes/No fields must
				have "Y" or "N".
(8) All date
				fields must be in mm/dd/yyyy format, and entries must contain a valid
				date.
(9) All fields that reference
				a code list should contain a value from the lists provided in the Property Tax
				Management System Code List Manual. This document is available on the
				department's website located at
www.in.gov/dlgf/
(10) Place a negative sign "-" at the far
				left of the field for all negative numbers.
(11) Note all format requirements specified
				at the field level.
(12) When
				capturing data as designated by a code list, the item must adhere to the
				designated code list. If a county needs a code list to be modified, it must
				notify the department and the legislative services agency for
				consideration.
(13) Phone number
				extensions may be replaced with spaces if no extension exists. Format required
				is ###-###-#### ##### (e.g., 317-555-5555 44444).
(14) ZIP code format is expected to be
				xxxxx-xxxx. However, the space allocated should accommodate international ZIP
				codes. If no + 4 for the ZIP code is available, fill with 0000.
Indiana Administrative Code › Title 50 - DEPARTMENT OF LOCAL GOVERNMENT FINANCE › Article 26 - COMPUTER STANDARDS FOR A UNIFORM AND COMMON PROPERTY TAX MANAGEMENT SYSTEM › Rule 20 - Property Tax File Format Requirements for 2011-Pay-2012 Data and Forward › Section 20-3 - Code lists for required data

Current through July 10, 2024
Authority: IC 6-1.1-31-1; IC 6-1.1-31.5-3.5
Affected: IC 6-1.1-31.5
Sec. 3.
The Property Tax Management System Code List Manual contains
				  the complete list of codes required for data collection and submission. Data
				  submissions must contain valid codes for specified fields based on this manual.
				  The lists required for data submission include:
(1) Code List 1 - Property Class
				Codes;
(2) Code List 2 - Street
				Codes;
(3) Code List 3 -
				Neighborhood Codes;
(4) Code List 4
				- Data Codes;
(5) Code List 5 -
				Reason for Change Codes;
(6) Code
				List 6 - Land Type Codes;
(7) Code
				List 7 - Influence Factor Codes;
(8) Code List 8 - Occupancy Codes;
(9) Code List 9 - Story Configuration
				Codes;
(10) Code List 10 - Attic
				Codes;
(11) Code List 11 --
				Basement Codes;
(12) Code List 12 -
				Crawl Space Codes;
(13) Code List
				13 - Roofing Codes;
(14) Code List
				15 - Heating Codes;
(15) Code List
				17 - Quality Grade and Design Factor Codes;
(16) Code List 18 - Construction Type
				Codes;
(17) Code List 21A - Summary
				of Improvements (Residential and Agricultural Use Codes);
(18) Code List 21B - Summary of Improvements
				(Commercial Industrial Use Codes);
(19) Code List 22 - Condition
				Codes;
(20) Code List 23 -
				Neighborhood Improvement Codes;
(21) Code List 29 - Wall Type
				Codes;
(22) Code List 30 - Frame
				Type Codes;
(23) Code List 31 -
				Pricing Key Codes;
(24) Code List
				32 - Commercial/Industrial Improvement Use Type Codes;
(25) Code List 33 - Hotel/Motel Configuration
				Codes;
(26) Code List 37 -
				Adjustment Codes (Deductions, Exemptions, and Credits);
(27) Code List 38 - Taxpayer Type
				Codes;
(28) Code List 45 - Grounds
				for Appeal Codes;
(29) Code List 57
				- Taxing Unit Type Codes;
(30) Code
				List 59 - County Name and Numeric Codes;
(31) Code List 60 - State Assigned Taxing
				District Name and Numeric Codes;
(32) Code List 61 - State Assigned Township
				Name and Numeric Codes;
(33) Code
				List 62 - Country Name and 3-digit Alpha Codes;
(34) Code List 63 - Return Type
				Codes;
(35) Code List 64 - Property
				Type Codes;
(36) Code List 65 -
				Adjustment Type Codes;
(37) Code
				List 66 - Waterfront Property Type Codes;
(38) Code List 70 - Personal Property Number
				Type Codes;
(39) Code List 71 Sales
				Disclosure Contact Person Codes;
or other code lists as determined by the department and the
				  legislative services agency, and provided in the Property Tax Management System
				  Code List Manual. This document is available on the department's website
				  located at
www.in.gov/dlgf/
Indiana Administrative Code › Title 50 - DEPARTMENT OF LOCAL GOVERNMENT FINANCE › Article 26 - COMPUTER STANDARDS FOR A UNIFORM AND COMMON PROPERTY TAX MANAGEMENT SYSTEM › Rule 20 - Property Tax File Format Requirements for 2011-Pay-2012 Data and Forward › Section 20-5 - Personal property data

Current through July 10, 2024
Authority: IC 6-1.1-31-1; IC 6-1.1-31.5-3.5
Affected: IC 6-1.1-4-25; IC 6-1.1-31.5; IC 36-1-8.5
Sec. 5.
(a) HEADER
				RECORD (appears once per file):
(1) The HEADER
				RECORD must be placed as the first record in each personal property assessment
				file including the PERSPROP, POOLDATA, and APPEALPP files.
(2) The format of the HEADER RECORD must be
				consistent with the following data format:
Column
Start
End
Length
Type
Comments/Format
Filename
1
10
10
A
Name of data file (e.g., PERSPROP or POOLDATA).
County Number
11
12
2
A
State designated county ID (e.g., 23). See code list
						  59.
County Description
13
32
20
A
State designated county name (e.g., LAKE). See code list
						  59.
File Format ID
33
37
5
A
Constant value of 2017A. This communicates the version
						  of the structure used to create the data.
County Contact Name
38
77
40
A
Full name of the individual at the county who can answer
						  questions specific to this data extract (e.g., Robert Smith).
County Contact Phone
78
95
18
A
Complete telephone number of individual at the county
						  who can answer questions specific to this data extract - format required is
						  ###-###-#### ##### (e.g., 219-555-5555 44444).
File Create Date
96
105
10
D
Date the file was created - format required is
						  mm/dd/yyyy format (e.g., 10/01/2010).
File Create Time
106
109
4
A
Time the file was created - format required is #### in
						  military time (e.g., 1400).
Assessment Year
110
113
4
A
The assessment year specific to the data submission -
						  format required is yyyy (e.g., 2009).
Pay Year
114
117
4
A
The tax payment year specific to the data submission -
						  format required is yyyy (e.g., 2010).
Software Vendor Company
118
177
60
A
Full name of the vendor company preparing the data
						  extract.
Software Package Name and Version
178
237
60
A
Complete name of the software package along with the
						  version of the software used to build this data extract (e.g., ABC Assessor
						  System Version 1.5).
Software Vendor Contact Name
238
287
50
A
Full name of the individual at the vendor who can answer
						  questions specific to this data extract (e.g., Robert Smith).
Software Vendor Phone Number
288
305
18
A
Complete telephone number of the individual at the
						  vendor's company who can answer questions specific to this data extract -
						  format required is ###-###-#### ##### (e.g., 317-555-5555 44444).
Software Vendor Contact Email
306
353
48
A
Email of the individual at the vendor's company who can
						  answer questions specific to this data extract (e.g., Help@ABCVendor.com).
Transmission Description
354
453
100
A
Description of transmission. Comment field, free
						  text.
Indiana Administrative Code › Title 50 - DEPARTMENT OF LOCAL GOVERNMENT FINANCE › Article 26 - COMPUTER STANDARDS FOR A UNIFORM AND COMMON PROPERTY TAX MANAGEMENT SYSTEM › Rule 20 - Property Tax File Format Requirements for 2011-Pay-2012 Data and Forward › Section 20-6 - Annually assessed mobile homes

Current through July 10, 2024
Authority: IC 6-1.1-31-1; IC 6-1.1-31.5-3.5
Affected: IC 6-1.1-31.5; IC 36-1-8.5
Sec. 6.
(a) HEADER
				RECORD (appears once per file):
(1) The HEADER
				RECORD must be placed as the first record in each annually assessed mobile home
				file including the MOBILE and APPEALMH files.
(2) The format of the HEADER RECORD must be
				consistent with the following data format:
Column
Start
End
Length
Type
Comments/Format
Filename
1
10
10
A
Name of data file (e.g., MOBILE or APPEALMH).
County Number
11
12
2
A
State designated county ID (e.g., 23). See code list
						  59.
County Description
13
32
20
A
State designated county name (e.g., LAKE). See code list
						  59.
File Format ID
33
37
5
A
Constant value of 2017A. This communicates the version
						  of the structure used to create the data.
County Contact Name
38
77
40
A
Full name of the individual at the county who can answer
						  questions specific to this data extract (e.g., Robert Smith).
County Contact Phone
78
95
18
A
Complete telephone number of individual at the county
						  who can answer questions specific to this data extract - format required is
						  ###-###-#### ##### (e.g., 219-555-5555 44444).
File Create Date
96
105
10
D
Date the file was created - format required is
						  mm/dd/yyyy format (e.g., 10/01/2010).
File Create Time
106
109
4
A
Time the file was created - format required is #### in
						  military time (e.g., 1400).
Assessment Year
110
113
4
A
The assessment year and pay year specific to the data
						  submission - format required is yyyy (e.g., 2010).
Pay Year
114
117
4
A
The tax payment year and assessment year specific to the
						  data submission - format required is yyyy (e.g., 2010).
Software Vendor Company
118
177
60
A
Full name of the vendor company preparing the data
						  extract.
Software Package Name and Version
178
237
60
A
Complete name of the software package along with the
						  version of the software used to build this data extract (e.g., ABC Assessor
						  System Version 1.5).
Software Vendor Contact Name
238
287
50
A
Full name of the individual at the vendor who can answer
						  questions specific to this data extract (e.g., Robert Smith).
Software Vendor Phone Number
288
305
18
A
Complete telephone number of the individual at the
						  vendor's company who can answer questions specific to this data extract -
						  format required is ###-###-#### ##### (e.g., 317-555-5555 44444).
Software Vendor Contact Email
306
353
48
A
Email of the individual at the vendor's company who can
						  answer questions specific to this data extract (e.g., Help@ABCVendor.com).
Transmission Description
354
453
100
A
Description of transmission. Comment field, free
						  text.
Indiana Administrative Code › Title 50 - DEPARTMENT OF LOCAL GOVERNMENT FINANCE › Article 26 - COMPUTER STANDARDS FOR A UNIFORM AND COMMON PROPERTY TAX MANAGEMENT SYSTEM › Rule 20 - Property Tax File Format Requirements for 2011-Pay-2012 Data and Forward › Section 20-7 - Oil and gas assessments

Current through July 10, 2024
Authority: IC 6-1.1-31-1; IC 6-1.1-31.5-3.5
Affected: IC 6-1.1-31.5; IC 36-1-8.5
Sec. 7.
(a) HEADER
				RECORD (appears once per file):
(1) The HEADER
				RECORD must be placed as the first record in each oil and gas assessment file
				including the OILGAS and OILGASALL files.
(2) The format of the HEADER RECORD must be
				consistent with the following data format:
Column
Start
End
Length
Type
Comments/Format
Filename
1
10
10
A
Name of data file (e.g., OILGAS or OILGASALL).
County Number
11
12
2
A
State designated county ID (e.g., 23). See code list
							 59.
County Description
13
32
20
A
State designated county name (e.g., LAKE). See code list
							 59.
File Format ID
33
37
5
A
Constant value of 2021A. This communicates the version of
							 the structure used to create the data.
County Contact Name
38
77
40
A
Full name of the individual at the county who can answer
							 questions specific to this data extract (e.g., Robert Smith).
County Contact Phone
78
95
18
A
Complete telephone number of individual at
							 the county who can answer questions specific to this data extract -format
							 required is ###-###-#### ##### (e.g., 219-5555555 44444).
File Create Date
96
105
10
D
Date the file was created - format required is
							 mm/dd/yyyy format (e.g., 10/01/2010).
File Create Time
106
109
4
A
Time the file was created - format required is #### in
							 military time (e.g., 1400).
Assessment Year
110
113
4
A
The assessment year specific to the data submission
							 -format required is yyyy (e.g., 2009).
Pay Year
114
117
4
A
The tax payment year specific to the data submission
							 -format required is yyyy (e.g., 2010).
Software Vendor Company
118
177
60
A
Full name of the vendor company preparing
							 the data extract.
Software Package Name and Version
178
237
60
A
Complete name of the software
							 package along with the version of the software used to build this data extract
							 (e.g., ABC Assessor System Version 1.5).
Software Vendor Contact Name
238
287
50
A
Full name of the individual at the vendor
							 who can answer questions specific to this data extract (e.g., Robert
							 Smith).
Software Vendor Phone Number
288
305
18
A
Complete telephone number of the individual
							 at the vendor's company who can answer questions specific to this data extract
							 - format required is ###-###-#### ##### (e.g., 317-555-5555 44444).
Software Vendor Contact Email
306
353
48
A
Email of the individual at the vendor's
							 company who can answer questions specific to this data extract (e.g.,
							 Help@ABCVendor.com).
Transmission Description
354
453
100
A
Description of transmission. Comment
							 field, free text.
Indiana Administrative Code › Title 50 - DEPARTMENT OF LOCAL GOVERNMENT FINANCE › Article 26 - COMPUTER STANDARDS FOR A UNIFORM AND COMMON PROPERTY TAX MANAGEMENT SYSTEM › Rule 20 - Property Tax File Format Requirements for 2011-Pay-2012 Data and Forward › Section 20-8 - Real and personal tax data

Current through July 10, 2024
Authority: IC 6-1.1-31-1; IC 6-1.1-31.5-3.5
Affected: IC 6-1.1-11-9; IC 6-1.1-31.5; IC 36-1-8.5; IC
				  36-2-9-20
Sec. 8.
(a) HEADER
				RECORD (first record in each file):
(1) The
				HEADER RECORD must be placed as the first record in each real and personal tax
				data file including the TAXDATA and ADJMENTS files.
(2) The format of the HEADER RECORD must be
				consistent with the following data format:
Column
Start
End
Length
Type
Comments/Format
Filename
1
10
10
A
Name of data file (e.g., TAXDATA or ADJMENTS).
County Number
11
12
2
A
State designated county ID (e.g., 23). See code list
						  59.
County Description
13
32
20
A
State designated county name (e.g., LAKE). See code list
						  59.
File Format ID
33
37
5
A
Constant value of 2017A. This communicates the version
						  of the structure used to create the data.
County Contact Name
38
77
40
A
Full name of the individual at the county who can answer
						  questions specific to this data extract (e.g., Robert Smith).
County Contact Phone
78
95
18
A
Complete telephone number of individual at the county
						  who can answer questions specific to this data extract - format required is
						  ###-###-#### ##### (e.g., 219-555-5555 44444).
File Create Date
96
105
10
D
Date the file was created - format required is
						  mm/dd/yyyy format (e.g., 10/01/2010).
File Create Time
106
109
4
A
Time the file was created - format required is #### in
						  military time (e.g., 1400).
Assessment Year
110
113
4
A
The assessment year specific to the data submission -
						  format required is yyyy (e.g., 2009).
Pay Year
114
117
4
A
The tax payment year specific to the data submission -
						  format required is yyyy (e.g., 2010).
Software Vendor Company
118
177
60
A
Full name of the vendor company preparing the data
						  extract.
Software Package Name and Version
178
237
60
A
Complete name of the software package along with the
						  version of the software used to build this data extract (e.g., ABC Assessor
						  System Version 1.5).
Software Vendor Contact Name
238
287
50
A
Full name of the individual at the vendor who can answer
						  questions specific to this data extract (e.g., Robert Smith).
Software Vendor Phone Number
288
305
18
A
Complete telephone number of the individual at the
						  vendor's company who can answer questions specific to this data extract -
						  format required is ###-###-#### ##### (e.g., 317-555-5555 44444).
Software Vendor Contact Email
306
353
48
A
Email of the individual at the vendor's company who can
						  answer questions specific to this data extract (e.g., Help@ABCVendor.com).
Transmission Description
354
453
100
A
Description of transmission. Comment field, free
						  text.
Indiana Administrative Code › Title 50 - DEPARTMENT OF LOCAL GOVERNMENT FINANCE › Article 26 - COMPUTER STANDARDS FOR A UNIFORM AND COMMON PROPERTY TAX MANAGEMENT SYSTEM › Rule 21 - Property Tax Input-Output File Format Requirements › Section 21-1 - Purpose of rule

Current through July 10, 2024
Authority: IC 6-1.1-31-1; IC 6-1.1-31.5-3.5
Affected: IC 6-1.1-31.5
Sec. 1.
The purpose of this rule is to prescribe standardized data
				  file formats for the import and export of tax rate data between state and local
				  government.
Indiana Administrative Code › Title 50 - DEPARTMENT OF LOCAL GOVERNMENT FINANCE › Article 26 - COMPUTER STANDARDS FOR A UNIFORM AND COMMON PROPERTY TAX MANAGEMENT SYSTEM › Rule 21 - Property Tax Input-Output File Format Requirements › Section 21-2 - Instructions

Current through July 10, 2024
Authority: IC
				  6-1.1-31-1;
				  IC
				  6-1.1-31.5-3.5
Affected: IC 6-1.1-31.5; IC
				  36-2-9-20
Sec. 2.
Data format instructions are as follows:
(1) Each file must have a header record and a
				trailer record in the exact specified format with designated "FILENAME" and the
				word "TRAILER" in uppercase.
(2)
				All fields are fixed length.
(3)
				Left justify all alphanumeric fields.
(4) All numeric fields must have leading
				zeros if field value does not utilize all available spaces.
(5) Assume no decimal precision for all
				numeric fields without format clarification.
(6) All decimal precision is implied. For
				example, for format 3.2, send 12345. It will be read as "123.45".
(7) Yes/No fields must have "Y" or
				"N".
(8) All date fields must be in
				mm/dd/yyyy format, and entries must contain a valid date.
(9) All fields that reference a code list
				should contain a value from the lists provided in the Property Tax Management
				System Code List Manual. This document is available on the department's website
				located at
www.in.gov/dlgf/
(10) Place a negative sign "-" at the far
				left of the field for all negative numbers.
(11) Note all format requirements specified
				at the field level.
(12) When
				capturing data as designated by a code list, the item must adhere to the
				designated code list. If a county needs a code list to be modified, it must
				notify the department and the legislative services agency for
				consideration.
(13) Phone number
				extensions may be replaced with spaces if no extension exists. Format required
				is ###-###-#### ##### (e.g., 317-555-5555 44444)
(14) Postal code format is expected to be
				xxxxx-xxxx. However, the space allocated should accommodate international
				postal codes. If no + 4 for the postal code is available fill with
				0000.
Indiana Administrative Code › Title 50 - DEPARTMENT OF LOCAL GOVERNMENT FINANCE › Article 26 - COMPUTER STANDARDS FOR A UNIFORM AND COMMON PROPERTY TAX MANAGEMENT SYSTEM › Rule 21 - Property Tax Input-Output File Format Requirements › Section 21-3 - Code lists for required data

Current through July 10, 2024
Authority: IC 6-1.1-31-1; IC 6-1.1-31.5-3.5
Affected: IC 6-1.1-31.5
Sec. 3.
The Property Tax Management System Code List Manual contains
				  the complete list of codes required for data collection and submission. Data
				  submissions must contain valid codes for specified fields based on this manual.
				  The lists required for data submission include:
(a) Code List 57 - Taxing Unit Type Codes; or
				other code lists as determined by the department and the legislative services
				agency, and provided in the Property Tax Management System Code List Manual.
				This document is available on the department's website located at
www.in.gov/dlgf/
Indiana Administrative Code › Title 50 - DEPARTMENT OF LOCAL GOVERNMENT FINANCE › Article 26 - COMPUTER STANDARDS FOR A UNIFORM AND COMMON PROPERTY TAX MANAGEMENT SYSTEM › Rule 21 - Property Tax Input-Output File Format Requirements › Section 21-4 - Budget order

Current through July 10, 2024
Authority: IC
				  6-1.1-31-1;
				  IC
				  6-1.1-31.5-3.5
Affected: IC 6-1.1-31.5
Sec. 4.
(a) HEADER
				RECORD (the first record in each file):
(1)
				The HEADER RECORD must be placed as the first record in each CERT RATES and
				ALLCERRATE file.
(2) The format of
				the HEADER RECORD must be consistent with the following data format:
Column
Start
End
Length
Type
Comments/Format
FileName
1
10
10
A
Name of data file (e.g., CERTDRATES or ALLCERRATE).
County Number
11
12
2
A
State designated county ID (e.g., 23). See code list
							 59.
County Description
13
32
20
A
State designated county name (e.g., LAKE). See code
							 list 59.
File Format ID
33
37
5
A
Constant value of 2017A. This communicates the version
							 of the structure used to create the data.
County Contact Name
38
77
40
A
Full name of the individual at the county who can
							 answer questions specific to this data extract (e.g., Robert Smith).
County Contact Phone
78
95
18
A
Complete telephone number of individual at the county
							 who can answer questions specific to this data extract - format required is
							 ###-###-#### ##### (e.g., 219-555-5555 44444).
File Create Date
96
105
10
D
Date the file was created - format required is
							 mm/dd/yyyy format (e.g., 10/01/2010).
File Create Time
106
109
4
A
Time the file was created - format required is #### in
							 military time (e.g., 1400).
Assessment Year
110
113
4
A
The assessment year specific to the data submission -
							 format required is yyyy (e.g., 2009).
Pay Year
114
117
4
A
The tax payment year specific to the data submission -
							 format required is yyyy (e.g., 2010).
Software Vendor Company
118
177
60
A
Full name of the vendor company preparing the data
							 extract.
Software Package Name and Version
178
237
60
A
Complete name of the software package along with the
							 version of the software used to build this data extract (e.g., ABC Assessor
							 System Version 1.5).
Software Vendor Contact Name
238
287
50
A
Full name of the individual at the vendor who can
							 answer questions specific to this data extract (e.g., Robert Smith).
Software Vendor Phone Number
288
305
18
A
Complete telephone number of the individual at the
							 vendor's company who can answer questions specific to this data extract -
							 format required is ###-###-#### ##### (e.g., 317-555-5555 44444).
Software Vendor Contact E-mail
306
353
48
A
E-mail of the individual at the vendor's company who
							 can answer questions specific to this data extract (e.g., Help@ABCVendor.com).
Transmission Description
354
453
100
A
Description of transmission. Comment field, free text.
Indiana Administrative Code › Title 50 - DEPARTMENT OF LOCAL GOVERNMENT FINANCE › Article 26 - COMPUTER STANDARDS FOR A UNIFORM AND COMMON PROPERTY TAX MANAGEMENT SYSTEM › Rule 21 - Property Tax Input-Output File Format Requirements › Section 21-5 - State-assessed utility assessments

Current through July 10, 2024
Authority: IC
				  6-1.1-31-1;
				  IC
				  6-1.1-31.5-3.5
Affected: IC 6-1.1-31.5
Sec. 5.
(a) HEADER
				RECORD (the first record in each file):
(1)
				The HEADER RECORD must be placed as the first record in each UTILITYAV
				file.
(2) The format of the HEADER
				RECORD must be consistent with the following data format:
Column
Start
End
Length
Type
Comments/Format
FileName
1
18
18
A
Filename (e.g. "FILENAME: UTILITYAV")
County Number
19
35
17
A
2 digit County Number (e.g. "County Number: 09")
County Description
36
75
40
A
County Name (e.g. "County Description: CASS COUNTY")
File Format ID
76
96
21
A
"File Format ID: 2017A"
File Create Date
97
126
30
A
mm/dd/yyyy format (e.g. "File Create Date:
							 03/03/2005")
File Create Time
127
148
22
A
e.g. "File Create Time: 1400"
Pay Year
149
162
14
A
e.g. "Pay Year: 2006"
Transmission Description
163
262
100
A
e.g. "Transmission Description: Preliminary Data
							 Submission - Test"
Indiana Administrative Code › Title 50 - DEPARTMENT OF LOCAL GOVERNMENT FINANCE › Article 26 - COMPUTER STANDARDS FOR A UNIFORM AND COMMON PROPERTY TAX MANAGEMENT SYSTEM › Rule 21 - Property Tax Input-Output File Format Requirements › Section 21-6 - State-assessed railcar assessments

Current through July 10, 2024
Authority: IC
				  6-1.1-31-1;
				  IC
				  6-1.1-31.5-3.5
Affected: IC 6-1.1-31.5
Sec. 6.
(a) HEADER
				RECORD (the first record in each file):
(1)
				The HEADER RECORD must be placed as the first record in each RAILAV
				file.
(2) The format of the HEADER
				RECORD must be consistent with the following data format:
Column
Start
End
Length
Type
Comments/Format
FileName
1
18
18
A
Filename (e.g. "FILENAME: RAILAV")
County Number
19
35
17
A
2 digit County Number (e.g. "County Number: 09")
County Description
36
75
40
A
County Name (e.g. "County Description: CASS COUNTY")
File Format ID
76
96
21
A
"File Format ID: 2017A"
File Create Date
97
126
30
A
mm/dd/yyyy format (e.g. "File Create Date:
							 03/03/2005")
File Create Time
127
148
22
A
e.g. "File Create Time: 1400"
Pay Year
149
162
14
A
e.g. "Pay Year: 2006"
Transmission Description
163
262
100
A
e.g. "Transmission Description: Preliminary Data
							 Submission - Test"
Indiana Administrative Code › Title 50 - DEPARTMENT OF LOCAL GOVERNMENT FINANCE › Article 26 - COMPUTER STANDARDS FOR A UNIFORM AND COMMON PROPERTY TAX MANAGEMENT SYSTEM › Rule 22 - Property Tax File Format Requirements for 2010-Pay-2011 Data and Earlier › Section 22-1 - Purpose of rule

Current through July 10, 2024
Authority: IC 6-1.1-31-1; IC 6-1.1-31.5-3.5
Affected: IC 6-1.1-31.5
Sec. 1.
The purpose of this rule is to prescribe standardized
				  property tax data file formats to enable local government to be able to
				  collect, analyze, store, and share property tax data with the state and to
				  facilitate integration required between all components of a property tax
				  management system. The prescribed file formats must be able to be generated by
				  local officials at any time without vendor intervention or cost to the county.
				  The formats under this rule apply to 2010-pay-2011 and prior years.
Indiana Administrative Code › Title 50 - DEPARTMENT OF LOCAL GOVERNMENT FINANCE › Article 26 - COMPUTER STANDARDS FOR A UNIFORM AND COMMON PROPERTY TAX MANAGEMENT SYSTEM › Rule 22 - Property Tax File Format Requirements for 2010-Pay-2011 Data and Earlier › Section 22-2 - Instructions

Current through July 10, 2024
Authority: IC
				  6-1.1-31-1;
				  IC
				  6-1.1-31.5-3.5
Affected: IC 6-1.1-31.5
Sec. 2.
(a) Data
				format instructions are as follows:
(1) Each
				file must have a header record and a trailer record in the exact specified
				format with designated "FILENAME" and the word "TRAILER" in
				uppercase.
(2) All fields are fixed
				length.
(3) Left justify all
				alphanumeric fields.
(4) All
				numeric fields must have leading zeros if field value does not utilize all
				available spaces.
(5) Assume no
				decimal precision for all numeric fields without format
				clarification.
(6) All decimal
				precision is implied. For example, for format 3.2, send 12345. It will be read
				as "123.45".
(7) Yes/No fields must
				have "Y" or "N".
(8) All date
				fields must be in mm/dd/yyyy format, and entries must contain a valid
				date.
(9) All fields that reference
				a code list should contain a value from the lists provided in the Property Tax
				Management System Code List Manual. This document is available on the
				department's website located at www.in.gov/dlgf/
(10) Place a negative sign "-" at the far
				left of the field for all negative numbers.
(11) Note all format requirements specified
				at the field level.
(12) When
				capturing data as designated by a code list, the item must adhere to the
				designated code list. If a county needs a code list to be modified, it must
				notify the department and the legislative services agency for
				consideration.
(13) Phone number
				extensions may be replaced with spaces if no extension exists. Format required
				is ###-###-#### ##### (e.g., 317-555-5555 44444).
(14) ZIP code format is expected to be
				xxxxx-xxxx. However, the space allocated should accommodate international ZIP
				codes. If no + 4 for the ZIP code is available, fill with 0000.