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

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

5. Record what is still untested

List any entry paths, record types or volumes you did not test before relying on the rule.