Skip to main content

Legal

Tax & Accounting

Trade & Supply

Risk & Fraud

News & Media

Books

Developers

Authorities

Zone alias mapping

Zone names in Determination may not always match the names used by your ERP (enterprise resource platform) system.

Examples

Examples of differences between Determination and your ERP system.
  • You may use non-English spellings (Roma, Deutschland, etc.).
  • You may use common abbreviations (Ft Worth, N Orleans, etc.).
  • You may use alternate names (Prince Edward Isle, PEI, etc.).

Zone alias tasks

The
Zone Alias
 page lists many common aliases you can use. If you're a custom data provider, you can also use this page to set up alternate names required by your ERP system but not provided as part of Determination.

Match a zone alias

When Determination encounters a zone name it doesn't recognize, it attempts to find an alias match with these rules:
  • The
    lowest level zone
     in the zone tree's checked first for aliases; then the tree's traversed up to the top-level (World).
  • Within each level,
    custom aliases get tested first, then tax data provider aliases
    . For example, if a U.S. city zone isn't recognized, the system checks for city alias records in this order:
    • Custom at the county level
    • Tax data provider at the county level
    • Custom at the country level
    • Tax data provider at the country level
    • Custom at the world level
    • Tax data provider at the world level
  • Valid levels for which aliases can be set
     are:
    • For U.S. tax data, county, and city zones.
    • For International tax data, country, state, province, county, and city zones.
  • The
    1st matching alias text gets tested if a valid zone name can be generated
    .
    • Matches are case-sensitive.
    • Full match aliases get tested 1st, then prefix matches, then suffix matches.
    • Within the prefix and suffix types, aliases get tested from longest to shortest. For example, NORTH_ gets tested before NOR_, which gets tested before NO_, which gets tested before N_.
    • If the alias results in a single valid zone name, the zone name's applied and an informational message (ZONE_ALIAS_APPLIED) gets returned with the transaction.
    • If the alias results in a non-valid zone name or multiple matches outside the U.S., additional matches get tested in the order previously mentioned.
    • If the alias results in a partial zone tree match but improves the zone accuracy of the transaction, the match gets applied. For example, if transaction data results in a partial match at the country level, but an alias results in a partial match at the province level, the alias gets applied.
    • If no valid zone names can be created, a partial zone tree or no zone tree message gets raised, depending on other transaction values.
  • If a U.S. alias results in multiple matches at the city level, the (default) zone for that city gets applied. This scenario's encountered when a city spans multiple counties.

Zone alias matches

If you're using zone aliases and submit a +4 zip code in address data, but no matching zip code is in the Determination tax data, the product returns the city zone that's marked as default in the tax data.

This article applies to:

  • Product: ONESOURCE Determination, ONESOURCE Indirect Tax
  • Subject: Authorities

Related content

  • Zones
    Format: Article, 1 min read