---
schema_version: "1"
id: 08c0bf48892411d013c6d4dd36add57711614af88f0da63b384f2fdc087aeb25
title: Boundary Matching Requirements in Live Data Alignments
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/sales/264-0-0/territory_planning_alignments_boundary_units.md
canonical_url: https://help.salesforce.com/s/articleView?id=sales.territory_planning_alignments_boundary_units.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: cce713d06eab77eb1518b95f753766dd8b74f3718a713273a2693f127c6d59d2
description: When you create an alignment with live data, Territory Planning tries to match the country and postal code string values in your data source with your boundary set definitions.
products:
  - Sales Cloud
  - Sales Enablement
release: "264"
---
# Boundary Matching Requirements in Live Data Alignments

When you create an alignment with live data, Territory Planning tries to match the country and postal code string values in your data source with your boundary set definitions.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: both Salesforce Classic (not available in all orgs) and Lightning Experience</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: <strong>Professional</strong>, <strong>Enterprise</strong>, <strong>Performance</strong>, <strong>Unlimited</strong>, and <strong>Developer</strong> Editions with <a href="https://help.salesforce.com/s/articleView?id=sales.territory_planning_api_access.htm&amp;type=5&amp;language=en_US" target="_blank">Web Services API enabled</a></td></tr></tbody></table>

Territory Planning attempts to match values in this priority order.

- First, checks for an exact match of both country code and postal code, such as `USA` and `94105`.
- Next, checks for an exact match on the `countrycode_zipcode` key format.
- Next, checks for an exact match on the postal code only. If two postal codes are matched because the alignment has multiple boundary sets, a postal code value isn’t assigned.
- Next, checks for matching point ZIP codes.

For postal codes, only the important digits for your territory plan are evaluated. For example, if you plan limits US postal codes to five digits but your data source uses a nine-digit US postal code such as 12345-6789, only the first five digits 12345 are evaluated. Postal codes for United Kingdom are excluded from string matching and must be an exact match instead.