This page (revision-9) was last changed on 26-Nov-2021 10:22 by rforbes

This page was created on 26-Nov-2021 10:22 by KHanson

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
9 26-Nov-2021 10:22 1010 bytes rforbes to previous
8 26-Nov-2021 10:22 2 KB rforbes to previous | to last UDTX ==> Vertex.UDTX
7 26-Nov-2021 10:22 2 KB rforbes to previous | to last VERTEX ==> Vertex.VERTEX
6 26-Nov-2021 10:22 2 KB jescott to previous | to last
5 26-Nov-2021 10:22 1 KB jescott to previous | to last
4 26-Nov-2021 10:22 1 KB RForbes to previous | to last
3 26-Nov-2021 10:22 1 KB RForbes to previous | to last
2 26-Nov-2021 10:22 1 KB RForbes to previous | to last
1 26-Nov-2021 10:22 90 bytes KHanson to last

Page References

Incoming links Outgoing links

Version management

Difference between version and

At line 3 added 9 lines
This is a [Vertex] construct that defines the tax jurisdiction for all taxes. It is comprised of three elements, separated by hyphens. __18-025-1296__ is an example of a GEO Code which represents the following structure:
__18__-000-0000 is the state level (in this case Kentucky) which can be used to tax only at state level
__18-025__-0000 is the county level (in this case Breathitt County) which can be used to tax only at county level
__18-025-1296__ is the city level (in this case Jasckson, Kentucky) which would be used to tax at the city level.
You do not need to identify tax jurisdictions down to the finest level, if there is no local (county and city) taxation. For example, __44-281-0241__ is the city level GEO Code for Adamsville, Texas in Lampasas county, but we could simply use __44-000-0000__ (State of Texas) for this location or employee for taxation purposes as there is no county or city level taxation