A Jurisdiction identifies a taxation locality for state, provincial or local taxation purposes.
This section explains the Define Tax Jurisdictions (IDTX) screen and its associated fields.
For U.S. installations only - Jurisdictions define all of the state, county and city localities which have state and local taxation requirements.
’Jurisdiction Name’ must be unique within a state/province in the application.
For Canadian installations only - Each Canadian province is defined with a tax jurisdiction for Canadian taxation purposes. If you have an out-of-country operation that requires withholding of Canadian taxation, you can define a tax jurisdiction for that country and link to the Canada province on the IDTX form.
A starter script is provided to load all Canadian tax jurisdictions by Province. Any other tax jurisdictions you may require must be entered manually.
State or local taxation codes (GEO Codes) are maintained centrally within the jurisdiction definition. If a city or county tax jurisdiction boundary changes, it can affect many employees. However, by changing the GEO code within the jurisdiction definition, the change will be applied automatically to all employees in that locality.
Tax jurisdictions must be defined by GEO type for the different taxation levels required by the organization. Only the required levels of taxation need to be defined.
For example, Ohio needs to be defined by state, county and city tax jurisdiction but Texas only needs to be defined by state.
The FIPS code (Federal Information Processing Standard Code) is a U.S. Government code assigned to geographical locations and may be defined as required. This field is mandatory if your company is going to be filing 941s.
A starter script is provided to load all the state GEO codes and a sample city and county GEO code for each state.
Tax Jurisdiction data is stored in the P2K_CM_TAX_JURISDICTIONS table.
State | 01-000-0000 | or |
County | 01-073-0000 | or |
City | 01-073-2051 |
Screen captures are meant to be indicative of the concept being presented and may not reflect the current screen design.
If you have any comments or questions please email the Wiki Editor
All content © High Line Corporation