> 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
The entity start and end dates control the range of transaction data that syncs in Kick.
### Start date
The start date determines when transaction data begins syncing for all accounts on the entity. It's set during client onboarding and can be updated at any time.
To change the start date:
1. Go to the **Clients** tab.
2. Find the entity row and edit the **Start date** inline.
If the **Start date** column isn't visible, click the **Gear icon** (⚙) in the top right to expose it.
{% hint style="info" %}
**Important:** Changing the start date can pull in additional historical transactions or remove transactions that fall outside the new range. Adjust with care if categorization work has already been done.
{% endhint %}
***
### End date
The end date determines when transaction syncing stops. Transactions after the end date will not appear in Kick.
End date can only be set at the account level.
To change the end date:
1. Go to the **Accounts** tab in your client's workspace
2. Hover over the account where you'd like to change the end date and click the options menu
3. Select **Update end date**
4. Edit the end date and click **Set date** to save
{% hint style="info" %}
**Note:** Kick may automatically set an end date when a subscription is canceled or a plan limit is reached. If an end date appears unexpectedly, check the client's subscription status.
{% endhint %}
***
### Account-level overrides
Individual accounts can override the entity's start dates. Account-level dates are managed from the Accounts tab under each account's settings.
---
# 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=&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.
