Why does a new account not have a KERN ID yet?
Last updated: June 21, 2026
Short answer
A new Salesforce Account may not have a KERN ID yet because it has not reached Kernel's enrichment workflow, has not been linked to a Kernel Account record, or does not have enough usable evidence for confident resolution.
Missing KERN ID does not automatically mean the account is broken. It means the identity lifecycle needs to be checked.
What to check
- Was the Account included in the relevant sync, backfill, inbound, or refresh scope?
- Does a Kernel Account record exist for the Account?
- Is the KERN ID populated on the Kernel object, Account, or neither?
- Does the Account have enough identity evidence: name, website, country, legal name, LinkedIn URL, address, or parent context?
- Was the Account created after the latest sync or enrichment job?
- Is the customer expecting the value on Account when it currently only lives on the Kernel object?
Common causes
- The record is too new and has not been processed yet.
- The customer has a scheduled refresh cadence rather than immediate enrichment.
- The Account is missing enough usable identity signals.
- The Account was excluded from the workflow scope.
- The KERN ID exists on the Kernel object but is not mapped to Account.
- The record is stuck in an inbound or enrichment workflow that needs support review.
What to send support
- Salesforce Account ID.
- Kernel Account record ID, if present.
- Account name, website, country, and any known parent.
- When the Account was created or updated.
- Where the customer expected to see the KERN ID.
- Whether this affects one account or a broader cohort.