If a stop has a contingency assignment and there is no Postal Code Override for its ZIP, what happens to an extended postal code outside the intended CSA boundary?

If a stop has a contingency assignment and there is no Postal Code Override for its ZIP, what happens to an extended postal code outside the intended CSA boundary?

• A. It remains unassigned
• B. It triggers an error
• C. It uses its original extension
• D. It receives the CSA assignment of the geography it falls in

Answer: (D)

When a stop has a contingency assignment, that fallback path is used unless a specific override is provided. If there’s no Postal Code Override for the ZIP, the system relies on the actual geographic CSA boundaries to determine the mapping. So, if the extended postal code lies outside the intended CSA boundary, it gets the CSA assignment of the geography it falls in. This keeps routing consistent with where the location physically sits when there isn’t an override to force a different CSA.

When a stop has a contingency assignment, that fallback path is used unless a specific override is provided. If there’s no Postal Code Override for the ZIP, the system relies on the actual geographic CSA boundaries to determine the mapping. So, if the extended postal code lies outside the intended CSA boundary, it gets the CSA assignment of the geography it falls in. This keeps routing consistent with where the location physically sits when there isn’t an override to force a different CSA.