> 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/api/webhooks/financial-account-moved.md).

# financial\_account.moved

One of your financial accounts moved to another entity of the same workspace, taking its transactions and accounting data with it.

Moving a financial account takes its transactions, documents, and accounting data to another entity of the same workspace. Anything your integration keyed by entity, such as synced transactions or cached reports, now belongs to a different set of books.

This event tells your integration which entity the account left and which one it joined.

### When it fires

The event is sent once each time an account moves from one entity to another entity of the same workspace. It fires the same way whether the move was made in Kick or through [Financial Accounts](https://docs.kick.co/api/api-reference/financial-accounts.md), so a move your own integration makes reaches your endpoint too.

It is held back in these cases:

* Moving an account to the entity it already belongs to changes nothing, and sends no event.
* Assigning an account that had no entity sends [`financial_account.created`](https://docs.kick.co/api/webhooks/financial-account-created.md) instead, because the account wasn't visible on the Platform API before.

The event is sent after the move is saved, to every organization with Platform API access that the account's workspace belongs to.

### Payload

```json
{
  "event": "financial_account.moved",
  "version": 1,
  "occurredAt": 1761645600,
  "payload": {
    "financialAccountId": "3f9c2a71-5d8e-4b6a-9c1f-7e2d4a6b8c90",
    "workspaceId": "8d3a1b52-9f1d-4a7e-b0a1-2c5d6e7f8a90",
    "entityId": "c2a7e9f4-1b3d-4e6a-8f0c-5d7b9a1e3c24",
    "previousEntityId": "b6c4d2e1-7a3f-4c8b-9e0d-1f2a3b4c5d6e"
  }
}
```

`payload` carries:

| Field                | Type | Notes                                                                                                    |
| -------------------- | ---- | -------------------------------------------------------------------------------------------------------- |
| `financialAccountId` | uuid | The account's `id` on [Financial Accounts](https://docs.kick.co/api/api-reference/financial-accounts.md) |
| `workspaceId`        | uuid | Workspace the account and both entities belong to                                                        |
| `entityId`           | uuid | Entity the account moved to                                                                              |
| `previousEntityId`   | uuid | Entity the account moved from                                                                            |

The fields around it are the same on every event. See [The event envelope](https://docs.kick.co/api/webhooks.md#the-event-envelope).

### Handling it

Re-file whatever you hold for the account under `entityId`. Transactions and journal entries that belonged to `previousEntityId` through this account now belong to the new entity, so refresh reports and balances you cached for both entities.

An account can move more than once in a short time, and a retried delivery can arrive after a newer one. Compare `occurredAt` with the last event you applied for the account, or read the account's current `entityId` from [Financial Accounts](https://docs.kick.co/api/api-reference/financial-accounts.md), rather than applying events in arrival order.


---

# 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/api/webhooks/financial-account-moved.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.
