> ## Documentation Index
> Fetch the complete documentation index at: https://zenskar.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Customers reference

> [!NOTE]
>
> This page is a field-level lookup. For task steps, see [how to add customers](https://zenskar.com/docs/20260301/product-modules/customers/how-to-guides/add-customers.md) and [how to manage customers](https://zenskar.com/docs/20260301/product-modules/customers/how-to-guides/manage-customers.md). For the reasoning behind these fields, see [customers: concepts](https://zenskar.com/docs/20260301/product-modules/customers/concepts/customers.md).

## Add/edit customer form reference

### Customer information

| Field | Required | Description |
| - | - | - |
| Customer name | Yes | The full name of the customer. |
| External ID | No | An identifier from an external system (e.g. your CRM). Must be unique within your organization. Used to match records during imports or syncs. |
| Email | No | The primary email address for the customer. Must be unique within your organization. |
| Phone number | No | The customer's contact phone number. |

### Business entity

| Field | Required | Description |
| - | - | - |
| Business entity | No | The Zenskar business entity associated with this customer. Defaults to your organization's default business entity if left unset. **Cannot be changed after creation.** |

### Billing address

| Field | Required | Description |
| - | - | - |
| Address line 1 | Yes | First line of the billing address. |
| Address line 2 | No | Second line of the billing address. |
| Address line 3 | No | Third line of the billing address. |
| Zip code | Yes | Postal or ZIP code. |
| City | Yes | City. |
| State | Yes | State or province. |
| Country | Yes | Country. |

### Shipping address

| Field | Required | Description |
| - | - | - |
| Shipping address is same as billing address | No | When checked (default), the shipping address mirrors the billing address. Uncheck to enter a separate shipping address using the same fields as above. |

### Tax information

| Field | Required | Description |
| - | - | - |
| Tax ID (country) | No | Choosing the country determines which tax ID type is shown next, for example GST, VAT, or TIN. Zenskar supports a wide range of countries. |
| Tax ID | No | The tax identifier for the selected country. |
| Exempt tax | Depends | Not a standard field. Only shown if your organization has defined an exempt tax custom attribute under **Settings → Custom attributes → Customers**. |

### Custom attributes

Custom attributes are defined in **Settings → Custom attributes → Customers**. They appear here as individual fields. Empty fields are pre-filled with their configured default values, if any.

### Other settings

| Field | Default | Description |
| - | - | - |
| Charge invoices | On | Enables auto-charge on invoices via the configured payment gateway. Requires a fully configured payment gateway. |
| Email communications | On | Allows Zenskar to send emails to this customer via configured senders. |
| Add as a child | Off | Redirects billing for this customer to another customer you designate as the parent. Only shown for organizations on the earlier contract experience, not for organizations with Contracts V3 turned on. See [consolidated billing](https://zenskar.com/docs/20260301/product-modules/customers/concepts/customers.md#consolidated-billing-across-related-customers) for how this differs from consolidating invoices. |

## Ways to add customers

| Method | Best for |
| - | - |
| Manual form | Adding a single customer directly in the UI. |
| CSV upload | Bulk-importing many customers at once. The file needs at least an email column or a Stripe reference ID column somewhere in it, this is checked once for the whole file, not row by row. |
| REST API | Programmatic integration with external systems. |
| Connector | Ongoing two-way sync with a CRM, CPQ, or ERP. |

## Contacts

| Field | Description |
| - | - |
| Name | The contact's name. |
| Email | The contact's email address. |
| Send invoice | Whether this contact receives invoice communications. |

There is no separate "primary contact" record. The customer's own email field is the closest equivalent; every contact added through **Manage Secondary Contacts** is a peer record with its own send invoice setting.

> [!NOTE]
>
> Contract communications are a separate setting in the underlying data model, but there's currently no control for it in the dashboard, so it can't actually be turned on from the UI.

## Wallet

Each customer can hold one wallet per currency. Credits in a wallet are applied automatically when an invoice is approved, unless wallet application has been turned off for that invoice. Use **Adjust balance** to add credits (for promotional purposes) or deduct them (to settle a balance).

> [!NOTE]
>
> The wallet tab is only available for organizations on the earlier contract experience, not for organizations with Contracts V3 turned on.

## What you can view on a customer record

From the **View customer** page, you can access:

* Invoices
* Contracts
* Entitlements
* Payments
* Journal entries
* Monitoring
* Email logs
* Integrations
* Wallet details
* Child customers

## Deletion behavior

A customer cannot be deleted while any contract still references them. Deleting a customer soft-deletes the record.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.