Can related records have different KERN IDs?
Last updated: June 21, 2026
Short answer
Yes. Related records can and often should have different KERN IDs. A parent and child are related entities, but they are not the same entity. Each should have its own KERN ID, with hierarchy fields linking them together.
Do not use different KERN IDs alone as evidence that Kernel missed a match. First decide whether the expected relationship is duplicate identity or parent-child hierarchy.
What to check
- Are the records supposed to represent the same legal or operating entity?
- Or are they different entities in the same corporate family?
- Does one record show the other as parent, ultimate parent, or hierarchy relation?
- Are the KERN IDs different but the parent KERN ID or ultimate parent KERN ID aligned?
- Is the customer asking for a merge, an association, or hierarchy reporting?
Common examples
- Parent and subsidiary: different KERN IDs, linked through hierarchy fields.
- Global parent and regional entity: different KERN IDs, often linked through parent or ultimate parent fields.
- Brand or business unit and legal entity: may be different identities depending on how the entity resolved.
- Lead and Account: matching requires the same KERN ID when the workflow expects exact entity matching.
What to send support
- Both Salesforce Account IDs.
- KERN ID for each record.
- Parent KERN ID and ultimate parent KERN ID, if available.
- The expected relationship: same entity, parent-child, regional, brand, business unit, or unknown.
- Any current merge or associate recommendation.