> For the complete documentation index, see [llms.txt](https://docs.rillet.com/EjmEP4KZ9BVp9j2ho4Mh/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rillet.com/EjmEP4KZ9BVp9j2ho4Mh/integrations/payroll/gusto.md).
# Gusto
The **Gusto** integration automatically imports payroll data into **Rillet**, without manual uploads or spreadsheets. It keeps payroll entries accurate and up to date, reducing errors and saving time after every payroll run.
### Connect Your Gusto Account
Connect your Gusto account using either of these methods:
| Method | How to Access |
| ------------------------- | ------------------------------------------------------------------------------------------------------------------------ |
| **Launchpad** | Access the Gusto integration through the **Browse Integration** section from the Launchpad. |
| **Organization Settings** | Click your **company logo** in the lower-left corner of the screen, then go to **Organization Settings > Integrations**. |
Once you reach the integrations page, continue with the steps in **Complete the Gusto Connection** below.
### Complete the Gusto Connection
Follow these steps once you reach the integrations page:
1. Select **Gusto > Not Connected** under **Payroll**.
2. Click **Continue** in the secure Finch window that opens to proceed.
3. Confirm **Continue** to authorize data access and proceed with the setup.
4. Choose **Connect** to begin the integration process.
5. Begin with the **General** step and fill in the following fields once authenticated:
* **Sync data from:** Select the effective start date for syncing payroll data from Gusto.
* **(Optional):** Record the last successful sync date in **Last successful sync** for tracking purposes.
6. Select **Next Step** to continue.
7. Map the departments from Gusto to the departments in Rillet.
* **Payroll Departments (left):** Departments pulled from Gusto.
* **Rillet Field Mapping (right):** Select a corresponding Rillet department for each Gusto department.
8. Select **Next Step** to proceed.
9. Map pay types to default GL accounts for accounting purposes.
* **Pay Types (left):** Earnings, Salary, Wage, Reimbursement, etc., pulled from Gusto.
* **Liability Default Account:** Choose the GL account to record the payroll liability (i.e., the amount owed to fund the payroll).
* **Expense Default Account:** Select the account used to recognize the payroll expense for each pay type.
* **(Optional):** Override the default expense or liability account for specific departments in **Department-specific accounts**.
* **Taxes and Benefits Mapping (bottom of the screen):** Map Employee Taxes, Employer Taxes, Employee Deductions, and Employer Contributions to appropriate accounts.
10. Click **Finish Setup** to save your integration and enable automated payroll syncing once you have completed all allocations.
{% hint style="info" %} **Note:**
Payroll runs before **Sync data from** are ignored. Map every department, using **Department-specific accounts** for exceptions like routing engineering to COGS, and set **Taxes and Benefits Mapping** entries to a payroll liability or clearing account.
{% endhint %}
Once setup is complete, Rillet is ready to generate payroll journal entries automatically from each finalized Gusto payroll run.
### Create Payroll Journal Entries
Rillet will automatically create payroll journal entries once a payroll run is finalized in Gusto, based on your mapping setup.
Example (summarized):
| **Account** | **Debit** | **Credit** |
| ---------------------- | --------- | ---------- |
| Earnings | 1,000,000 | |
| Employer Taxes | 90,000 | |
| Employer Contributions | 50,000 | |
| Employee Taxes | | 100,000 |
| Employee Contribution | | 14,000 |
| Payroll Liability | | 1,026,000 |
This entry keeps your payroll expense, tax, and liability accounts aligned with each Gusto payroll run.
### Match Payroll Payments in Your Bank Feed
Once payroll expenses are recorded and the liability is established:
1. Match cash payments to Gusto (and providers like 401k) against the Payroll Liability account.
2. Use Quick Entry to reduce the liability balance as payments are made.
{% hint style="success" %} **Success:**
Confirm the net impact of the Payroll Liability through the Account Register.
{% endhint %}
Once fully configured, the Gusto integration keeps payroll journal entries and bank reconciliation aligned in Rillet, with minimal manual effort required after each payroll run.
### See Also
To learn more about the Gusto integration in **Rillet**, review these articles:
* [**JustWorks**](/EjmEP4KZ9BVp9j2ho4Mh/integrations/payroll/justworks.md)
* [**Brex Integration**](/EjmEP4KZ9BVp9j2ho4Mh/integrations/expense-management/brex-integration.md)
* [**Connect Your Bank Accounts**](/EjmEP4KZ9BVp9j2ho4Mh/getting-started/getting-started/connect-your-bank-accounts.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.rillet.com/EjmEP4KZ9BVp9j2ho4Mh/integrations/payroll/gusto.md?ask=&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.
