Use this procedure to specify the minimum import year and the import field mappings for an appraisal district. You need to carry out this procedure for each county appraisal district (CAD) from which you import data.
Important Once this data is entered for the year, PACS Collections stores the entries, and it is not necessary for you to reenter the data. The data should be entered only once per CAD, and you should not change the data unless either an error occurred on the original mapping, or a new entity needs to be imported and mapped.
The Appraisal Import List is displayed.
The Appraisal Import Configuration Selection dialog box is displayed.
The Appraisal Import CAD Configuration dialog box is displayed.
Noneor select the earliest year available in the drop-down list so that prior years can be imported for supplemental changes.
Note For most offices, the first year to import from external CADs originated with the advent of HB1010 in 2008.
Property IDfrom the following drop-down lists:
If you import for multiple CAD's who are not your home CAD, then we recommend matching using Geo IDs. Using Property IDs in this case may result in mismatches.
If you import for only one CAD, you can match by Property ID as the default. However, you may run the import again using Geo ID to correct mismatches.
If this is your first time importing and you are unsure of the mapping to use, please contact TA Support.
Important Except for the BPP entities and CAD entities, entities that are mapped here are entities that you would like to add to properties. (BPP entities are not mapped here because they are managed separately within levy processing. CAD entities are not mapped because they are assigned based on the external CAD selected when importing appraisal data.)
The following two options are available for mapping entities:
- Map only to entities that your office collects for. This is the most common option.
- Map to entities in addition to the ones you collect for.
Keep in mind that any entities mapped here are added to your database and could result in an increase in the number of properties. Consider the following examples:
Example 1: If you are a city and only collect city bills, adding the county entity could create numerous properties that are not associated with the city entity.
Example 2: If you are the Tax Assessor Collector for the County and you collect special inventory for all entities, but normally do not collect 'all' taxes for all entities, we highly suggest you import 'all' entities to see all changes. This will also insure the accuracy of the UPTVF factor assigned to these properties as a multiplier for the sales inventory tax calculation. Special inventory entities can be marked to 'collect special inventory only' so bills on these entities do not create on any other properties except for special inventory properties.
Example 3: You choose to map to entities in addition to the ones you collect for because you want to include properties associated with those entities in order to share this information with taxpayers.
To add a new entity:
Note The importing CADS' entity code can be found on the Certified Totals report received from the CAD. The importing CAD may have a different coding system set up.
Note The entity you select should have a code matching the code displayed in the Imported Entity Code field. Only one entity code should appear in the selected Entities box.
Repeat steps 1-4 to add each entity.
To delete an entity code mapping: