> 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/integrations/gusto.md).

# Gusto

Connect Gusto to sync your payroll runs into Kick automatically, broken out by expense type.

When you connect Gusto, every payroll run syncs into Kick as a split transaction - automatically broken out into wages, payroll taxes, employee benefits, and reimbursements. No manual entry, no spreadsheets.

{% hint style="info" %}
You must be an **admin** on your Gusto account to connect the integration.
{% endhint %}

***

### Connect Gusto

1. Go to the **Accounts** tab
2. Click **Add account** and select **Gusto**
3. Authenticate with your Gusto credentials and follow the prompts

Once connected, Kick begins syncing payroll data automatically.

***

### What syncs

* **Payroll runs** - each run syncs as a split transaction broken out by: wages, payroll taxes, employee benefits, and other payroll expenses
* **Contractor payments** - domestic contractor payments sync alongside payroll runs
* **Reimbursements** - employee expense reimbursements sync automatically
* **Departments** - if you use departments in Gusto, they sync as Classes in Kick for department-level reporting

{% hint style="info" %}
International contractor payments don't sync through the Gusto integration. Categorize those directly from your connected bank account.
{% endhint %}

***

### Departments and Classes

If you track departments in Gusto, those sync automatically as Classes in Kick - so you can see payroll costs broken out by department on your [P\&L](/reports/profit-and-loss.md) without any extra setup.

→ [Reports](/reports/profit-and-loss.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/integrations/gusto.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.