> For the complete documentation index, see [llms.txt](https://docs.kick.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kick.co/accountants/managing-clients/entity-management/editing-entity-start-and-end-dates.md).

# Editing Entity Start and End Dates

Update the start and end dates that control which transactions sync into Kick, for a whole client, one entity, or one account.

Start and end dates control which transactions sync into Kick. You set them at three levels: the client's default sync date, each entity's start date, and an optional start and end date on each account.

| Level   | Where                                                  | What it changes                                          |
| ------- | ------------------------------------------------------ | -------------------------------------------------------- |
| Client  | **Edit client** → **Default Sync date**                | The start date of every entity in the client's workspace |
| Entity  | **Start date** column on the Clients page              | The start date of one entity                             |
| Account | Account **Settings** → **Start date** and **End date** | The date range of one account, inside its entity's range |

***

### Update the default sync date for a client

The default sync date is set when you add the client. Updating it changes the start date of every entity in the workspace at once.

1. On the Clients page, hover over the client row and click the **Client actions** menu (⋯).
2. Select **Edit client**.
3. Pick a new date in **Default Sync date**.
4. Click **Save**.

{% hint style="warning" %}
Saving a new default sync date replaces every entity's start date with the new date, including entities you had set to a different date. To change one entity, update its start date instead.
{% endhint %}

**Edit client** is available to firm members who can manage clients.

***

### Update an entity's start date

1. On the Clients page, expand the client to show its entities.
2. Click the entity's date in the **Start date** column, or **Add start date** if it's empty.
3. Pick the new date. It saves as soon as you pick it.

If the **Start date** column isn't visible, click **Configure columns** in the toolbar and turn it on.

***

### What happens when a start date changes

These apply whether you change the date for the whole client or for one entity:

* **Transactions**. Moving the start date earlier brings in older transactions. Transactions dated before the new start date no longer appear on the Transactions page.
* **Journal entries**. Kick regenerates the entity's journal entries for the new range.

Adjust with care if categorization work has already been done.

#### When a start date can't be changed

Kick doesn't save the new date in these cases:

| Situation                                                                                                        | What to do                                                                           |
| ---------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------ |
| An account in the entity has opening balances or reconciliations                                                 | Remove the opening balances and reconciliations, change the date, then add them back |
| The entity has an accounting migration, and the new date is on or before the last date imported by the migration | Pick a date after the migration's end date                                           |

When you move the start date earlier on an entity with an accounting migration, Kick deletes the imported migration journal entries dated on or after the new start date and moves the opening balance date back to the day before it.

***

### Update an account's start or end date

Set a start or end date on one account when its transactions should begin later or stop earlier than the rest of the entity, for example when an account was closed.

1. In the client's workspace, go to **Accounts**.
2. Hover over the account and click its options menu (⋯).
3. Select **Update start date** or **Update end date**. The account's **Settings** open.
4. Pick a date in **Start date** or **End date**. It saves as soon as you pick it.

Limits on each date:

* **Start date**. Shows the entity's start date until you set one. It can't be earlier than the entity's start date, or later than the account's or the client's end date.
* **End date**. Shows **Not set** until you set one. It can't be earlier than the account's start date or the entity's start date. Transactions after the end date don't appear in Kick.

To remove an account date, clear it in the date picker. A cleared start date falls back to the entity's start date.

***

### End dates Kick sets for you

Kick sets or clears the end date on every entity in a client's workspace in these cases:

* **Your firm's subscription is canceled**. Every client your firm pays for gets an end date of the cancellation date. Kick clears those end dates when the subscription is reactivated.
* **The client moves to a paid plan**. Changing the client's plan to a paid plan in **Edit client** clears an existing end date.

If an end date appears unexpectedly, check the client's subscription status.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.kick.co/accountants/managing-clients/entity-management/editing-entity-start-and-end-dates.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.