Same-Name Account Duplicate Rule Checklist
Use this short record when same-name business Accounts save without a duplicate warning. Work in a sandbox or other non-production org, with fictional or approved test data.
1. Describe one duplicate pair
| Question | Your answer |
|---|---|
| Account names (as entered) | |
| How was each record created? (manual, edit, import, integration, automation) | |
| Which fields were filled at save? (City, ZIP, Phone, Website, Street) | |
| Business Account or Person Account? | |
| Who needs the duplicate caught? (sales, service, finance, operations) |
2. Check the configuration
- [ ] The duplicate rule is for the Account object and is active.
- [ ] I know which matching rule it uses, and that matching rule is active.
- [ ] I have read the matching rule's fields and methods (for example, whether name alone can produce a match).
- [ ] Rule conditions do not exclude the records I am testing.
- [ ] I have checked rule order. The first rule that finds a match causes later rules to skip that record.
- [ ] I know whether the rule enforces or bypasses sharing, and whether users can see the existing record.
3. Test the actual outcome
| Test | Input | Expected | Actual (allowed / alerted / blocked) | Screenshot or note |
|---|---|---|---|---|
| Baseline same name | ||||
| Same name after change | ||||
| Different name (control) | ||||
| Same name, legitimately separate business | ||||
| Your real entry path (edit, import or integration) |
4. Decide the response
- [ ] Alert when a match is a reason to check, not proof of a duplicate.
- [ ] Report when someone will actually review the reported duplicates.
- [ ] Block only when the matching evidence is strong and the affected teams agree on what happens next.
- [ ] Dependent processes (Cases, calls, integrations, automation) have been tested with the new setting.
5. Record what is still untested
List any entry paths, record types or volumes you did not test before relying on the rule.