---
schema_version: "1"
id: 9e54d4d2cef45812327ebd32abfcdd055ec61134cc8a20dfb655afb1633a22d1
title: Match Rules for Accounts
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/data/264-0-0/c360_a_identity_resolution_match_rules_accounts.md
canonical_url: https://help.salesforce.com/s/articleView?id=data.c360_a_identity_resolution_match_rules_accounts.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 432942e12d71ba5dca64f32b8966197ca99e3451615889ac27e649dec60ae69f
description: Identity resolution provides two preconfigured default match rules based on Account Name combined with other common data. Default match rules allow you to quickly select one of the four common match rule configurations. You can combine default and custom rules in a ruleset to create multiple ways for records to match. To get the best results from account matching, we recommend using match rules that match by account name and geographical location. The specific address data you select impacts the quality and precision of your matches.
products:
  - Data 360
release: "264"
---
# Match Rules for Accounts

Identity resolution provides two preconfigured default match rules based on Account Name combined with other common data. Default match rules allow you to quickly select one of the four common match rule configurations. You can combine default and custom rules in a ruleset to create multiple ways for records to match. To get the best results from account matching, we recommend using match rules that match by account name and geographical location. The specific address data you select impacts the quality and precision of your matches.

## Match Accounts with Default Match Rules

Default match rules are pre-configured rules that you can opt to include in your ruleset. We offer two default match rules for matching accounts.

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
        <colgroup>
          <col style="width:50%">
          <col style="width:50%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d176667e44">Match Rule Name</th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d176667e47">Match Criteria</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="Match Rule Name" class="slds-cell-wrap" style="vertical-align:top;" headers="d176667e44 ">Exact Name and Normalized Address</td>

            <td data-label="Match Criteria" class="slds-cell-wrap" style="vertical-align:top;" headers="d176667e47 ">
              <ul>
                <li>Account Name (Exact)</li>

                <li>Contact Point Address - Address-Line-1 (Exact Normalized)</li>

                <li>Contact Point Address - City (Exact)</li>

                <li>Contact Point Address - Country (Exact Normalized)</li>

              </ul>
            </td>

          </tr>
          <tr class="">
            <td data-label="Match Rule Name" class="slds-cell-wrap" style="vertical-align:top;" headers="d176667e44 ">Exact Name and Normalized Address and Normalized Phone</td>

            <td data-label="Match Criteria" class="slds-cell-wrap" style="vertical-align:top;" headers="d176667e47 ">
              <ul>
                <li>Account Name (Exact)</li>

                <li>Contact Point Address - Address-Line-1 (Exact Normalized)</li>

                <li>Contact Point Address - City (Exact)</li>

                <li>Contact Point Address - Country (Exact Normalized)</li>

                <li>Contact Point Phone - Formatted E164 Phone Number (Exact Normalized)</li>

              </ul>
            </td>

          </tr>
        </tbody>
      </table>

## Match Account on Party Identifier

If your source data includes strong account identifiers, consider creating a match rule based on party identifiers. The following can be good account identifiers and create efficient matches.

- DUNS Number
- Government tax identifier
- An account ID created by an master data management system

Before using party identifier to match accounts, create a relationship with N:1 cardinality between the Party field in the Party Identification object and the Account ID field in the Account object.

## Match Accounts on Name and Location

These two match rules use geographical data to confirm name matches, which balances precision, correctness, and thoroughness of matches without being overly restrictive. While similar to the default match rules for account matching, these rules use fuzzy matching to increase matching across variations on an account’s name and address.

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
        <colgroup>
          <col style="width:50%">
          <col style="width:50%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d176667e145">Match Rule Name</th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d176667e148">Match Criteria</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="Match Rule Name" class="slds-cell-wrap" style="vertical-align:top;" headers="d176667e145 ">
              <p><strong>Name and Address</strong></p>
              <p style="margin-bottom:0;">When your source data includes good address data, a
                match rule with these criteria generates highly comprehensive matches with
                excellent geographical confirmation.</p>
            </td>

            <td data-label="Match Criteria" class="slds-cell-wrap" style="vertical-align:top;" headers="d176667e148 ">
              <ul>
                <li>(Fuzzy Match - Medium Precision) Account Name AND</li>

                <li>(Normalized) Address-Line-1 </li>

                <li>(Fuzzy Match - Medium Precision) City</li>

                <li>(Normalized) Country</li>

              </ul>
            </td>

          </tr>
          <tr class="">
            <td data-label="Match Rule Name" class="slds-cell-wrap" style="vertical-align:top;" headers="d176667e145 ">
              <p><strong>Name and City</strong></p>
              <p style="margin-bottom:0;">If street address details are inconsistent or
                unavailable, a match rule with these criteria generates good matches with strong
                geographical confirmation.</p>
            </td>

            <td data-label="Match Criteria" class="slds-cell-wrap" style="vertical-align:top;" headers="d176667e148 ">
              <ul>
                <li>(Fuzzy Match - High Precision) Account Name</li>

                <li>(Fuzzy Match - Medium Precision) City</li>

                <li>(Normalized) Country</li>

              </ul>
            </td>

          </tr>
        </tbody>
      </table>

- **[Tips for Improving Account Matching](https://help.salesforce.com/s/articleView?id=data.c360_a_identity_resolution_match_rules_accounts_tips.htm&release=264.0.0&type=5)**  
    Creating rules with overly broad criteria can result in poor account matching. Consider these guidelines when setting up identity resolution match rules for unifying accounts.

#### See Also

- [_Salesforce Help_: Tips for Improving Account Matching](https://help.salesforce.com/s/articleView?id=data.c360_a_identity_resolution_match_rules_accounts_tips.htm&release=264.0.0&type=5 "Creating rules with overly broad criteria can result in poor account matching. Consider these guidelines when setting up identity resolution match rules for unifying accounts.")