> 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/reports/check-and-deposit-detail.md).

# Check and Deposit Detail

List recorded checks and deposits by bank account for a date range, with counterparty, source, and reconciliation status.

The Check and Deposit Detail report lists the checks and deposits recorded on your client's bank accounts over a date range, so you can see what's outstanding and what's reconciled.

***

### Accessing the report

Go to **Reports** → **All reports** and select **Check and Deposit Detail**. Use the entity selector to cover one client or several.

***

### Structure

The report has a **Checks** section and a **Deposits** section, each with a total. Within each section, rows are grouped by the grouping menu at the top, which shows **By bank account** by default. With the default grouping, each section has a sub-group and subtotal for each bank account.

<figure><img src="https://290614220-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiOfJtU5BnOhuPqTiOHth%2Fuploads%2Fgit-blob-70d2696cddd182fe053f4b636e4c5f3147315f9b%2Fcheck-and-deposit-detail-grouping-menu.png?alt=media" alt="Grouping menu opened from the By bank account button, with Bank account, Reconciliation status, Counterparty, and None"><figcaption></figcaption></figure>

| Grouping option                     | Groups                      |
| ----------------------------------- | --------------------------- |
| **Bank account** (default)          | One group per bank account  |
| **Reconciliation status**           | Reconciled and unreconciled |
| **Counterparty**                    | One group per counterparty  |
| **None** (shows as **No grouping**) | No groups                   |

Use the expand button (**Expand all** / **Collapse all**) to open or close every group.

When nothing matches, the report shows "No checks or deposits for this selection".

***

### Columns

Shown by default:

* **Date**. The check or deposit date. Group titles share this column.
* **Reference no.** The reference number entered on the check or deposit, such as the check number.
* **Source**. Where the entry came from. A check recorded in Kick shows **Transaction**.
* **Counterparty**. Who the check was written to or the deposit came from.
* **Description**. The bank description, for example "Check #1001".
* **Memo**. The memo entered on it.
* **Reconciled**. Whether it's part of a completed reconciliation.
* **Amount**. The check or deposit amount.

Available from column settings:

* **Entities**. Only when the report covers more than one entity.
* **Cleared date**. The date of the bank transaction that cleared it.

***

### Filters

At the top of the report:

* The date range. A date range is required.
* The search box (**Search...**).
* **Filter**, to narrow by **Account** (checking accounts only), **Counterparty**, **Amount**, or **1099**.
* The entity selector.

***

### Export

Click **Download report**, then **.xlsx** or **.pdf**.

### Related articles

* [Checks and deposits](https://docs.kick.co/accountants/bookkeeping/checks-and-deposits.md)


---

# 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/reports/check-and-deposit-detail.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.
