> For the complete documentation index, see [llms.txt](https://integrations.drivetrain.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://integrations.drivetrain.ai/integration-guide/readme/accounting-and-erp/integrating-with-quickbooks/re-authentication-of-quickbooks.md).

# Re-authentication of QuickBooks

QuickBooks session expired in Drivetrain? Re-authenticate with this guide. Covers the OAuth re-authorization flow.

Reconnect QuickBooks when its syncs fail because the sign-in expired or was revoked. This happens after about 100 days without a successful sync, at QuickBooks' 5-year limit or if someone disconnected Drivetrain in QuickBooks. Once you reconnect, syncing resumes.

## Before you start

* You're a Drivetrain admin.
* You're the QuickBooks **primary admin** or a **Company admin** of the same company the data source is connected to.

## Step 1: Open Edit credentials in Drivetrain

1. On the **Data** page, click the **⋮** menu next to the QuickBooks data source and select **Edit credentials**. (It's disabled while a sync is running.)
2. Click **Connect to QuickBooks** in the window that appears.

<figure><img src="https://4220329029-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmBZR0D9lq6jrI895OuOU%2Fuploads%2Fgit-blob-3f23e43f06ccbf6846273b3315150cf7ea511e9a%2Fimage.png?alt=media" alt=""><figcaption></figcaption></figure>

<figure><img src="https://4220329029-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmBZR0D9lq6jrI895OuOU%2Fuploads%2Fgit-blob-6d23e790956f0a36c19bf480307fd7a0e3b7f443%2Fimage.png?alt=media" alt=""><figcaption></figcaption></figure>

## Step 2: Sign in to QuickBooks as an admin

1. Sign in with the primary admin or a Company admin account, and complete any verification QuickBooks asks for.

<figure><img src="https://4220329029-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmBZR0D9lq6jrI895OuOU%2Fuploads%2Fgit-blob-f5d9e0bda0a4e98d40b5af2b10bf8bc083e7bc53%2Fimage.png?alt=media" alt=""><figcaption></figcaption></figure>

2. If asked, select the **same company** this data source was connected to. Drivetrain rejects a different company.

<figure><img src="https://4220329029-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmBZR0D9lq6jrI895OuOU%2Fuploads%2Fgit-blob-1d495e5519c7f4a00b1a1c77893bddc0bab09182%2Fimage.png?alt=media" alt=""><figcaption></figcaption></figure>

## Step 3: Check that it worked

You return to Drivetrain with **Credentials updated for QuickBooks. A full sync has been initiated.**

## Troubleshooting

<details>

<summary>"The new credentials connect to a different QuickBooks account …"</summary>

You picked a different company. Repeat the steps and select the company this data source was created for. To connect a different company, add a new QuickBooks data source instead.

</details>

<details>

<summary>QuickBooks won't let me authorize.</summary>

Sign in as the primary admin or a Company admin.

</details>

<details>

<summary>Still stuck?</summary>

Contact your Drivetrain onboarding partner or customer success manager with the step where the flow stopped and a screenshot of any error.

</details>


---

# 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://integrations.drivetrain.ai/integration-guide/readme/accounting-and-erp/integrating-with-quickbooks/re-authentication-of-quickbooks.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.
