> 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/bookkeeping-workflows/counterparties.md).

# Counterparties

Counterparties are a consolidated list of your client's vendors and customers. Each counterparty can act as a vendor, a customer, or both.

***

### The Counterparties tab

Go to **Accounting →** [**Counterparties**](https://use.kick.co/counterparties) to see a grouped directory of vendors and customers. The table shows:

* **Name** — Counterparty name, with per-account child rows underneath
* **Accounts** — GL accounts used by that counterparty
* **Created by** — Where the counterparty came from (manual entry, integration, and so on)
* **Journal entries** — Count of journal entry lines
* **Debit** and **Credit** — Totals for the selected period
* **1099 eligible** — Whether the counterparty is flagged for 1099 reporting

A **No counterparty** row captures activity without an assigned counterparty. Click any counterparty row to open a details panel on the right.

Set a date range and use the **entity** selector at the top to scope the view. Click **Filter** to narrow by **Account**, **General ledger**, **Amount**, **1099** (Eligible or Not eligible), **Entry source**, **Ledger type**, or **Created by**.

Built-in views include **1099 review** lists for the current and prior tax years. Selecting one scopes the page to a single entity and replaces the date range with a **year** selector.

The row **⋯** menu offers **Edit**, **View transactions**, **View GL**, **Merge**, and **Delete**. Download the list as CSV from the download button in the header.

{% hint style="info" icon="lightbulb" %}
Counterparties are not entity-specific. A counterparty created in one entity is available across all entities.
{% endhint %}

***

### How counterparties are created

Kick automatically generates and assigns counterparties when transactions sync from connected integrations or are imported. Kick also syncs counterparties directly from certain integrations:

* **Ramp** — vendors created in Ramp are synced if you're using their bill pay product
* **BILL** — vendors and customers created in BILL are synced
* **Stripe and PayPal** — customers are synced if you're using either platform to collect payments

You can also create counterparties manually. Click **Add new** in the top right corner of the Counterparties tab. The only required field is the name. You can also add an email address, phone number, website, and address.

***

### Updating counterparties

To change the counterparty on a transaction, go to **Transactions** and use the dropdown in the **Counterparty** column.

To assign a counterparty in bulk, select multiple transactions (shift + click), click **Actions** (⌘K), and choose **Set counterparty**.

Select counterparties in the directory to bulk **Mark 1099 eligible** or **Unmark 1099 eligible** from the Actions menu.

***

### Automating counterparty assignment

You can create [Rules](/accountants/bookkeeping-workflows/rules.md) to automate counterparty assignment based on any combination of: entity, category, amount, bank description, account, date, or class.

***

### Reviewing counterparties at close

The **Insights** tab lets you drill into each category to see all the counterparties included in it — a useful way to spot miscategorized transactions before closing a period.

For a detailed view of vendor spend over time, use the [**Expenses by Vendor**](/accountants/reports/expenses-by-vendor.md) report on the **Accounting** tab.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.kick.co/accountants/bookkeeping-workflows/counterparties.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.