The Matching Process - GeoTAX_Premium - 7 - 7.7

GeoTAX Premium for Windows, UNIX/Linux, and z/OS

Product type
Product family
Geo Addressing
GeoTAX Premium
Product name
GeoTAX Premium
GeoTAX Premium for Windows, UNIX/Linux, and z/OS
First publish date

The following instructions explain each step in the matching process.

  1. (Optional) Some features of GeoTAX require you to build certain files before executing your batch job. GeoTAX provides utilities for building these files into a format it can read. The type of file you need depends on what you are trying to accomplish:

    • To cross-reference GeoTAX output with a tax program such as Sovos or Vertex, install a cross-reference file.

    • To match to customized address information and non-address locations such as well heads, transmission towers or any other descriptive location, create and install a Landmark Auxiliary file.

    • To match your input records to your own street address data, create and install a User Auxiliary file.

    • To make sure to use the most up-to-date data available, install the GeoTAX Auxiliary file

    • To match your input records to a state-supplied listing, download and install a state-supplied street address database.

    • To determine if an address is within a district that is defined in a file you have, and not one of the available Precisely boundary files, create a user-defined boundary file.

    • To determine the payroll code for a district, create the Payroll Tax Correspondence (PTC) file.

    • To return sales and/or use tax rate data for a selected industry (general, automotive, construction or medical) in your GeoTAX output records, install the Precisely Sales and Use Tax Rate file.

  2. Run your input file through GeoTAX using the batch driver or calling GeoTAX's matcher. GeoTAX first attempts a match to the Landmark Auxiliary file, if one exists. Then, based on the settings you chose in your parameter records, GeoTAX will match to the User Auxiliary file, the state-supplied file, or the GeoTAX Auxiliary file prior to matching to the Points and/or Streets file. If a street-level match is not possible, GeoTAX attempts postal matching at the ZIP+4 level, and so on, depending on the parameters you specify and the available data. Matched FIPS geocodes and names are appended to your input records.

  3. You can tailor your GeoTAX output using the following options:

  • For PB Vertex system users, jurisdiction geocodes can match to PB Vertex geocodes by using the Cross Reference file (built in Step 1). This jurisdiction-to-Vertex geocode conversion, referred to as the GeoTAX key, outputs a nine-digit Vertex jurisdiction code (comprised of a two-digit Vertex state code, three-digit FIPS county code, and four-digit Vertex city code) for each matched record. The GeoTAX key is then used to match these codes to the PB Vertex tax tables, which tell you the tax rate for each jurisdiction.

  • For Sovos users, a process similar to that described above is available. After building the Sovos data files, you can have GeoTAX return a GeoTAX key. This key is used to convert the jurisdiction codes from GeoTAX to the proprietary Sovos codes used in their software. You can then use that data in your Sovos application to find out the tax rate for each jurisdiction.

  • For users of GIS mapping systems such as those provided by MapInfo, you can tell GeoTAX to produce a file called GTBMARC. This output file contains fixed-length, comma-delimited data. By default, latitude and longitude are provided for each record. The remaining fields are user-defined. The GTBMARC file can then be imported to your mapping program so you can view geocoded records on a map.