> 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/common-workflows/classes.md).

# Classes

Track performance by location, department, project, or any other dimension that matters to your business.

Classes let you tag transactions with a dimension beyond category, so you can see your P\&L broken down by location, department, project, or any other segment that matters to your business. Available on the Plus plan.

***

### What classes are for

By default, your reports show totals across your entire business. Classes let you slice those totals any way you want.

A few examples of how business owners use them:

* **Location** - see revenue and expenses for each store, office, or market separately
* **Department** - break out spending by team (sales, operations, marketing)
* **Project** - track profit and cost for individual client engagements or initiatives
* **Property** - for real estate, see income and expenses per property

Once you assign classes to transactions, every report in Kick - P\&L, Balance Sheet, General Ledger - can be filtered by class.

***

### Classes and subclasses

Classes work in two levels:

* A **class** is the grouping (e.g., Location)
* A **subclass** is the specific item within it (e.g., New York, Los Angeles, Chicago)

You can have as many classes and subclasses as you need. Subclasses can be reordered or moved between parent classes at any time.

***

### How to set up classes

1. Go to **Accounting** -> **Classes**
2. Click **Add class** and enter a name
3. To add subclasses, click the **+** icon next to a class and enter the subclass name

{% embed url="<https://player.mux.com/lRGxqcCYQYK2FBevXlbkNso7wvPspSiYGRzSc02tMsfs>" %}

Classes and subclasses can be reordered by dragging, and subclasses can be moved between parent classes at any time.

{% embed url="<https://player.mux.com/ekOjoRT02jizpF3HvgVnEyK7G3aP3R5hbNsai3NONPEc>" %}

***

### Assigning classes to transactions

**One at a time:** Open any transaction and select a class from the Class column dropdown.

**In bulk:** Select multiple transactions in the Transactions tab, click **Actions** (⌘K), and choose **Set class**.

{% embed url="<https://player.mux.com/n6YpPR1SwWijBSUhcOhrlE68wr74iIa2enmAYB29yrI>" %}

**Automatically with Rules:** Set up a [Rule](/common-workflows/rules.md) to assign a class based on conditions like bank description, account, counterparty, or amount. Once configured, matching transactions are classified automatically when they sync - no manual work needed.

{% embed url="<https://player.mux.com/tdi2v2npwAv19hHKU3ZcyRGk8761HI7iZ9bPvLIj7bo>" %}

***

### Gusto and Ramp

If you use [Gusto](/integrations/gusto.md) or [Ramp](/integrations/ramp.md), departments from those platforms sync into Kick as classes automatically. You don't need to set these up manually.

***

### Viewing class reports

Go to any report - [Profit & Loss](/reports/profit-and-loss.md), Balance Sheet, or General Ledger - and use the Class filter to view results for a specific class or subclass. This gives you a full financial picture for each segment of your business without maintaining separate books.


---

# 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/common-workflows/classes.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.