> 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/setting-up/integrations/mercury.md).

# Mercury

Connect Mercury to sync transactions, bank statements, and treasury activity directly.

### Connecting Mercury

1. Go to the **Accounts** tab.
2. Click **Add account** and select **Mercury**.
3. Authorize the connection through Mercury's login flow.
4. Select the entity your Mercury integration relates to
5. Click **Continue**.

Kick connects to all Mercury accounts associated with the login used during authorization. This includes checking, savings, credit card, and treasury accounts.

If you authorize with a personal Mercury login, the connection is assigned to the workspace's Personal entity.

***

### What syncs

| Account type | Transactions | Bank statements | Invoices |
| ------------ | ------------ | --------------- | -------- |
| Checking     | ✅            | ✅               | ✅        |
| Savings      | ✅            | ✅               | ✅        |
| Credit card  | ✅            | ❌               | ❌        |
| Treasury     | ✅            | ❌               | ❌        |

Transactions sync automatically once the connection is authorized. Bank statements for checking and savings accounts sync into the Documents tab and are available for reconciliation. Invoices sync from business checking and savings accounts only (not from personal Mercury logins).

***

### Treasury accounts

Mercury treasury accounts include investment activity beyond standard banking. Kick syncs the following treasury transaction types:

* Deposits and withdrawals
* Dividends
* Interest
* Fees

{% hint style="info" %}
Bank statements are not yet available via the API for treasury and credit card accounts. Upload these manually from Mercury if needed for reconciliation.
{% endhint %}

***

### Direct integration vs. Plaid

Mercury accounts can be connected via Plaid, but the direct integration offers richer data and broader account coverage. For the best experience, we recommend using the direct integration.


---

# 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/setting-up/integrations/mercury.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.