Salesforce matching rules and duplicate rules work together, but they are not the same setting. A matching rule defines how Salesforce compares records. A duplicate rule uses one or more matching rules and determines what happens when a potential match is found. Separating those jobs makes duplicate management easier to test and tune.
Matching rules define the comparison
A matching rule specifies the fields and comparison methods used to identify similar records. Depending on the object and configuration, a rule can use exact or fuzzy comparisons for fields such as name, email, or address. Salesforce standard rules can provide a starting point; custom matching rules support business-specific data patterns.
The rule answers: “Which existing records count as a possible match?” A strict email match may reduce false positives for contacts, while company-name matching may need to account for punctuation, abbreviations, or legal suffixes. Matching quality depends on the completeness and consistency of the underlying data.
Duplicate rules define the response
A duplicate rule applies matching logic during record creation or editing and controls the response. Depending on configuration, Salesforce can display an alert, allow the save, block the save, or report the possible duplicate. The choice affects user friction and data quality, so it should reflect the cost of a missed duplicate and of a false match.
A warning is useful when users need discretion, while a block is appropriate only when the matching criteria are reliable enough for the records in scope. Permissions, user workflows, imports, APIs, and rule order can affect what people experience, so validate each relevant entry path.
How the two rules work together
A useful test set includes obvious duplicates, near matches, legitimate people with similar names, records missing key fields, and records with inconsistent formatting. Test both creation and update paths.
- Matching rule: compare incoming or edited data with records that may already exist.
- Duplicate rule: decide whether to warn, allow, block, or report when the matching rule finds a candidate.
- Review: measure false positives and missed duplicates, then refine field selection and thresholds.
Tune without disrupting users
Start with a report or alert when criteria are new, review real matches, and document exceptions. If the rule later blocks saves, communicate the reason and provide a clear path for resolving a valid record. Do not rely on a single broad name match if it regularly confuses different people or companies.
After deployment, monitor duplicate reports and user feedback. The goal is not simply fewer records; it is a repeatable process that catches likely duplicates while allowing legitimate records to be created and maintained.
How did this article land?
Choose one reaction. You can change it anytime.