Why is Kernel suggesting merging two accounts with different Salesforce names?
Last updated: June 22, 2026
Kernel may suggest a merge even when two Salesforce records have different Account.Name values because the merge recommendation is based on the resolved entity, not only the Salesforce display name.
In the merge review UI, the name Kernel shows can be Kernel's resolved entity name or legal name. That may differ from the name stored on the Salesforce Account. If both records resolve to the same entity, they may share the same KERN ID and appear in the same merge group.
Why the names can look different
Salesforce account names are CRM labels. They can include shorthand, regional names, legacy names, parent-company names, local-market names, or sales-owned naming conventions.
Kernel compares the evidence behind the records, including website, legal name, company identity, hierarchy context, and duplicate reasoning. If that evidence points to the same resolved entity, Kernel may recommend merging the records even if the Salesforce names do not match exactly.
Example
One Salesforce Account may be named Manulife Financial with website www.manulife.com, while another is named Manulife Canada with website www.manulife.ca.
The Salesforce names are different, but Kernel may still resolve both records to the same underlying entity. In that case, Kernel can show its resolved or legal entity name in the merge review UI and assign both records the same KERN ID.
What to check
Compare the Salesforce IDs so you know which CRM records are being reviewed.
Compare website, legal name, KERN ID, and merge reasoning.
Check whether both records resolve to the same real-world entity.
Review owner, activity, opportunities, segment, and safeguards before approving.
Use the original Salesforce
Account.Nameas a review signal, not as the only decision point.
When to reject or escalate
Reject the merge if the records are genuinely different entities that should stay separate.
Escalate the example if the displayed Kernel name, website, legal name, or KERN ID looks wrong for one of the records. That is a resolution issue, separate from the Salesforce naming mismatch.
Good to know
Same KERN ID means Kernel has resolved the records to the same entity.
Different Salesforce names do not automatically mean the records are different entities.
A merge recommendation still needs review unless your workflow is configured for auto-merge.
The Salesforce account that survives the merge is controlled by the primary or source record shown in the merge group.