Enterprise Tax Databases

The Enterprise Tax Module provides you with several different databases along with the ability to include additional databases to match against your input addresses or geographic coordinates.

Database Name and Description Required or Optional Supplier

GeoTAX/Enterprise Tax Premium Master Files

The master files are the main data files used by the Enterprise Tax Module. They identify all geographic components associated with a street address, such as the tax jurisdictions, latitude/longitude coordinates, census tract, and block group. These files, at over two gigabytes of data, are significantly larger than the postal file, but provide the greatest coding accuracy.

Note: The GeoTAX/Enterprise Tax Premium Database is a required data set and is the master file for the Enterprise Tax Premium Module software. This data is not compatible with versions of the Enterprise Tax Module prior to version 9.0 SP3.

The master files are available for download from the technical support web site: www.g1.com/support.

Required

Pitney Bowes monthly/quarterly subscription

Point Data Files

Point data products include Master Location Data (MLD), Centrus Points, HERE Points, and TomTom Points. The point data provides point-level geocoding for the most accurate placement of addresses throughout the U.S. The Master Location Data database provides the best available address point location for every mailable and deliverable address in the United States.

Optional

Pitney Bowes monthly subscription

State-Supplied Files

State-supplied files are provided by individual state governments that the Enterprise Tax Module uses to override results from the master files.

The Enterprise Tax Module provides you with the ability to override, at the state level, match results based upon information supplied by the states. By matching to the state-supplied files, you can remain compliant with tax jurisdiction assignment requirements mandated by new federal and state laws, such as the Mobile Telecommunications Sourcing Act and the Florida state Communications Services Tax Simplification Law.

Currently, there are two file formats supported in the Enterprise Tax Module: the Florida-native format, and the national TS-158 format (ANSI Transaction Set No. 158). The state of Florida provides address files in both the TS-158 and its own native format.

Note: This database option may not be available to all Enterprise Tax Module users. Individual states may restrict the use of state-supplied address files to licensed communications carriers or other business entities registered with the individual state.

The Enterprise Tax Module first attempts to match to the state database. If the Enterprise Tax Module cannot find a state match, it attempts a match to the GeoTAX Auxiliary file, if loaded, then to the master files.

Optional

State Governments

GeoTAX Auxiliary File

The GeoTAX Auxiliary file contains new addresses that have not yet been added to the master files. It provides the most up-to-date address data possible.

Optional

Pitney Bowes monthly subscription

Landmark Auxiliary File

The Landmark Auxiliary File is a user-defined file that allows you to specify customized address information in your input records. The recommended primary use of this file is to match to your company’s non-address locations such as well heads, transmission towers or any other descriptive location. The latitude/longitude coordinates that is part of the input needed to build this file allows companies to automatically keep track of any jurisdictional changes that affect these unique locations. Matching to this file requires that the input record information match exactly to the Landmark Auxiliary file contents. This also applies to street records if you choose to enter them in the Landmark Auxiliary file.

Note: For more information, see Creating a Landmark Auxiliary File.

Optional

User-defined

User Auxiliary File

User Auxiliary files are user-defined files that the Enterprise Tax Module uses to override results from the master files in street-level matching. If you have data that is more current than that in the master files, you can enter the new data into the auxiliary file and use it for your address matching. The Enterprise Tax Module returns matches made with a code that signifies the answer came from the auxiliary file. You can also return user-defined data from the auxiliary file with the match.

Note: For more information, see Creating a User-Defined Auxiliary File.

Optional

User-defined

Boundary Files

Boundary files provide additional data about locations of special tax districts: Special Purpose Tax Districts (SPD), Insurance Premium Tax Districts (IPD), Payroll Tax Districts (PAY), and User-Defined Boundary (USR) .

  • The Special Purpose Districts file (SPD.txb) provides you with return data on special purpose tax districts. Special purpose tax districts include such districts as Regional Transit Areas and Metropolitan Football districts.
  • The Insurance Premium Districts file (IPD.txb) is used by the insurance industry to determine sales tax on insurance premiums written in some states. This file allows insurers to correctly determine the rate due on each insurance policy. Boundaries vary by state and are based on fire and police district and municipal boundaries.
  • The Payroll Tax Districts file (PAY.txb) can help your company comply with state legislation that requires employers to deduct taxes from employee paychecks for special districts, such as taxes for emergency municipal services districts.

Pitney Bowes provides you with the appropriate boundary file on separate media if you license any of the optional files.

Important: The Enterprise Tax Module only uses one boundary file at a time. For more information, see the configuration options in Assign GeoTAX Info.

Optional

Pitney Bowes

User-Defined Boundary File

A user-defined boundary file (usr.txb) is a file that you create to represent polygons that you want to match against, such as sales territories, insurance rating territories, or any geographic areas that are of interest to you.

Note: For more information, see Creating a User-Defined Boundary File.

Optional

User-created

Pitney Bowes Sales and Use Tax Rate File

You can optionally license the Pitney Bowes Sales and Use Tax Rate file to supply sales and/or use tax rate data for the general, automotive, construction or medical industries. Sales and use tax rates can be returned for each of the assigned tax jurisdictions as well as the total tax rate for the assigned locations.

Optional

Pitney Bowes

Sales Tax Cross-Reference Files

Sales tax cross-reference files allow you to use the Enterprise Tax Module to determine tax jurisdictions for a given address, then use third-party software to determine the sales tax rates for those jurisdictions. The cross-reference files combine the U.S. Government Federal Information Processing Standards (FIPS) codes with the proprietary geocodes used by tax software from third parties.

Important: When using a cross-reference file, the SPD file must also be loaded.
  • PBS Vertex FileThe PBS Vertex file enables you to integrate the Enterprise Tax Module with tax compliance software from Vertex, Inc. With this file, the Enterprise Tax Module component AssignGeoTAXInfo can return the nine-digit Vertex jurisdiction code for an address. You can then match these codes to the Vertex tax tables, which tell you the tax rate for each jurisdiction. To use the PBS Vertex file you must have the PBS Vertex file from Pitney Bowes to build the cross reference.
  • Sovos FilesThe Sovos files enable you to integrate the Enterprise Tax Module with tax compliance software from Sovos. With this file, the Enterprise Tax Module component AssignGeoTAXInfo can return the Sovos jurisdiction code for an address. You can then match these codes to the Sovos tax tables, which tell you the tax rate for each jurisdiction. The Sovos files are supplied by Pitney Bowes and support both the SUT and TWE Sovos versions.

Optional

Pitney Bowes

Payroll Tax Cross-Reference Files

Payroll tax cross-reference files allow you to use third-party software to determine the payroll tax rates. The cross-reference files combine the U.S. Government Federal Information Processing Standards (FIPS) codes with the proprietary geocodes used by tax software from third parties. The Payroll System Tax Code file is a customized file that you build to return the payroll tax codes used by your payroll system.

Note: For more information, see Using a Payroll Tax Correspondence File.

Optional

Pitney Bowes