# Location priority and matching

Source: https://developer.avalara.com/products/excise/integration-guides/excise/olp7236399877072/

Guide: AvaTax Excise

# Location priority and matching

Understand how location matching works and its impact on transactions.

Matching is simply a selection process, or the process by which an element of your master data is selected from the location table for use in a transaction. For example, when creating a transaction, ATE will review the origin, destination, sale, and counter location information included in the transaction to see if that information matches any in the location table. At this point, behavior changes depending on whether ATE finds that match.

-   If there's a match, and any information about the location differs between the location table and the transaction, then ATE will follow your business practices to determine what to do (for example, update the location table, do nothing, and so on).

-   If there isn't a match, then based on your business practices, ATE may attempt to create a new location record if there’s enough information.

Note When a match is made, the values in the location table override any values provided in the transaction data.

**Parent topic:** [Locations](/excise/qto2786123074507/ "Understand how ATE stores and manages location data for reporting and functional requirements.")