> For the complete documentation index, see [llms.txt](https://docs.kernel.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kernel.ai/platform/actioning/create.md).

# Create accounts

Create missing accounts in your write source using the Kernel data you have reviewed

Create accounts lets you review the accounts Kernel recommends adding to your [**write source**](/integrations/write-source.md), then create them with your configured account data. Your write source is the connection Kernel writes changes to. Kernel links each new record to its existing Kernel account so you can follow the same entity across both systems.

[Open Create accounts in Kernel](https://app.kernel.ai/cleaning/create)

If you have multiple connections, **Connections → Write back to** shows the selected **Write source**. There is one write source per environment. The app uses its name in Create confirmations and results.

Kernel connections can include Salesforce and Amazon S3. **Create accounts currently supports Salesforce as the write source.** The Salesforce setup and examples below reflect that support.

## Before you begin

Confirm that your workspace has:

* A connected write source with permission to create account records.
* Saved **New accounts** field mappings covering the write source's required fields.
* **Create accounts that are missing from your write source** turned on under **Data actions > Rules > Creations**.
* The account data you want to include, ready to use in Kernel.

The Creations rule is **off by default**. After turning it on, click **Save** and [refresh the recommendations](/platform/data-setup/cleaning-rules.md#refresh-recommendations). This enables Create recommendations; it does not automatically create accounts in your write source. Review and confirm the recommendations in **Create accounts**.

Check the selected write source and whether you are working in sandbox or production before applying an action.

## Choose the data to create with

Your **New accounts** mappings determine which values are written when Kernel creates a record in your write source. Map a Kernel field to a destination field, or supply a fixed value.

For Salesforce, open **Connections → Salesforce → Advanced → New accounts** to configure these mappings.

You can populate new accounts with Kernel data such as:

| Data              | Examples                                                     |
| ----------------- | ------------------------------------------------------------ |
| Identity          | Account name, legal name, website, legal country and KERN ID |
| Firmographics     | Headcount, revenue in USD and operational status             |
| Operating address | Street, city, state, postcode and country                    |

For example, in Salesforce, map account name to **Name**, website to **Website**, and KERN ID to your designated Account text field. A fixed value can set your account source. Use your organisation's actual field names and requirements.

{% hint style="info" %}
Include **KERN ID** in your mappings so the entity's identity is visible in your write source and available for reconciliation. Use the account's own KERN ID, stored as text.
{% endhint %}

Create uses the data already available on the Kernel account. Complete any required enrichment first and check the values you want to include. Your saved mappings determine what is written to your write source.

When mapping firmographics, confirm the entity or group scope and the destination currency. Revenue is supplied in USD. Keep legal country and operating country distinct, and use operating addresses for billing fields only if that matches your organisation's policy.

## Review and create an account

1. Open **Create accounts** and select **Actionable**.
2. Review the name, website, legal name where shown, and KERN ID. Open **Why this account will be created** to see the explanation.
3. Use search and **Filter** to find the accounts you want to review.
4. Select **Create**, check the account and write source named in the confirmation, then confirm.
5. Look for **Create action queued** and follow the result in **Actioned**.

Choose **Reject** if you do not want to create a recommended account; you can optionally record a reason.

{% hint style="info" %}
A queued notification confirms that processing has been requested. Check the final outcome before treating the record as created in your write source. Kernel refreshes the affected account data in the background after completion.
{% endhint %}

### How duplicates and missing parents are handled

An account can be present in Kernel without appearing in **Create accounts**. Kernel checks whether it is a duplicate or belongs in a hierarchy action before recommending a new record in your write source.

**Duplicates**

Kernel identifies a primary record within a duplicate group. The primary record can be considered for creation if it is missing from your write source and meets the other Create criteria. The additional records marked as duplicates are not offered as separate creations.

For example, if the same company appears twice in your Kernel accounts, you should not expect two Create recommendations. Kernel considers the primary record for creation. If duplicate records already exist in your write source and Kernel recommends consolidating them, review that recommendation in **Merge accounts**. A duplicate does not automatically result in a merge; the recommendation depends on your duplicate-handling rules and the records involved.

**Missing parents**

When a missing account is the parent of other accounts in your workspace, review the recommendation in [**Associate accounts**](/platform/actioning/associate.md). This workflow can create the parent and link its child accounts in one action, so the parent is not offered as a separate recommendation in **Create accounts**.

For example, two subsidiary accounts may already exist in Salesforce while their shared parent is missing. In **Associate accounts**, you can review the proposed parent and its children together. Accepting the recommendation creates the parent once and links both subsidiaries to it using Salesforce's Parent Account field.

## Create several accounts

Select the recommendations you have reviewed, then choose **Create \[count] accounts**. Review the write source and count, enter the confirmation phrase shown, and confirm.

{% hint style="warning" %}
With no individual rows selected, the bulk action uses the matching actionable accounts in the current filtered scope. This can include accounts beyond the visible page. Check the confirmation count before proceeding.
{% endhint %}

Some recommendations may be excluded when they are out of date or would reverse an earlier action. Review those items separately. After processing, check the individual outcomes because a batch can contain different results.

## Check the result

| Outcome                       | What to do                                                                                                               |
| ----------------------------- | ------------------------------------------------------------------------------------------------------------------------ |
| **Processing**                | Wait for the final outcome.                                                                                              |
| **Created**                   | Check the new record in your write source and confirm the mapped values. For Salesforce, use the record link.            |
| **Already in \[source name]** | Kernel found the candidate's existing record in your write source and linked it. Check the record to confirm the entity. |
| **Rejected**                  | Your decision is recorded and this recommendation has not created an account in your write source.                       |
| **Failed**                    | Review the message and the checks below. Check your write source before retrying if the result is uncertain.             |

The app replaces **\[source name]** with the write source's name, for example **Already in Salesforce**.

For your first batch, compare a small sample of records in your write source with the saved mappings, including required fields, KERN ID and fixed values.

## CSV uploads, inbound and tracked usage

If you upload an account through **Add accounts** and Kernel successfully links it to an entity, that record consumes one tracked-account slot attributed to **CSV upload**. Creating its Salesforce Account and later processing that same record through [inbound](/developer/inbound-api.md) keeps the total at **one tracked account within the same contract term**.

1. **CSV upload and linking:** Kernel records one tracked account with CSV upload as its usage source.
2. **Create in Salesforce:** Kernel saves the returned Salesforce Account ID on the existing account and updates its existing usage entry to that ID. The original CSV upload attribution and KERN identity are retained. This adds no tracked-account consumption.
3. **Inbound from Salesforce:** Kernel finds the saved Salesforce-to-Kernel link and reuses the existing identity. The configured inbound workflow can still run, without counting the same record as another tracked account.

### Understand the source and record ID

After creation, the source describes two different things:

| Record                     | Source                                   | Record ID             |
| -------------------------- | ---------------------------------------- | --------------------- |
| Tracked usage entry        | CSV upload, where consumption originated | Salesforce Account ID |
| Current account connection | Salesforce, where the account now lives  | Salesforce Account ID |

The KERN ID continues to identify the matched entity. These sources describe Kernel's usage history and account connection; values written to Salesforce fields such as **Account Source** follow your **New accounts** mappings.

The inbound run appears separately in inbound processing history. Tracked-account consumption is counted per source record and contract term, so separate source records can count separately even when they share a KERN ID.

## FAQs and troubleshooting

<details>

<summary>Why is an account missing from Actionable?</summary>

Check that **Create accounts that are missing from your write source** is turned on under **Data actions > Rules > Creations**, and that your **New accounts** mappings are saved. After changing the rule, click **Save** and [refresh the recommendations](/platform/data-setup/cleaning-rules.md#refresh-recommendations).

Clear search and filters, check **Actioned**, and review the account's current recommendation. It may already be in your write source, be identified as a duplicate, or be a missing parent handled through **Associate accounts**. See [How duplicates and missing parents are handled](#how-duplicates-and-missing-parents-are-handled) for examples. If you still expect a Create recommendation, share the account's KERN ID with your Kernel contact.

</details>

<details>

<summary>Why can I not map a field?</summary>

Check that you are using the intended write source and environment, and that the connection has permission to write to the destination field. For Salesforce, check the connected user's Account field permissions. Your administrator or Kernel contact can help confirm which Kernel data can be mapped to it.

</details>

<details>

<summary>Why is a mapped field blank, including KERN ID?</summary>

Check the saved mapping and the value on the Kernel account. Confirm that any required enrichment was complete before creation. Fields without a source value may remain blank. Automation in your write source, such as a Salesforce flow, may also change a value after creation.

For KERN ID, map the account's KERN ID to a writable text field in your write source. In Salesforce, use an Account text field. Use your normal update workflow to populate later values on the existing record.

</details>

<details>

<summary>What should I check if creation fails or stays Processing?</summary>

Check **Actioned** and your write source before retrying. Review required field values and connection permissions. For Salesforce, also check validation and duplicate rules, record type, and picklists.

If you need help, retain the account name, KERN ID, write source, environment, action time and visible message. These help your administrator or Kernel contact locate the run and confirm whether a record was created.

</details>

## Related pages

* [Write source](/integrations/write-source.md)
* [Data actions](/platform/actioning.md)
* [Associate accounts and create missing parents](/platform/actioning/associate.md)
* [KERN ID](/concepts/kern-id.md)
* [Salesforce Search and create accounts](/integrations/salesforce-integration/search-and-create-accounts.md), for the separate workflow inside Salesforce.