Troubleshoot a third-party app that stopped syncing with QuickBooks Online

Creation date: 10/30/2026 1:38 PM    Updated: 10/30/2026 1:38 PM

Symptoms and responsibility boundaries

Use this guide when a connected app stops sending or receiving data, shows an authorization error, reports that access expired, syncs only some objects, or no longer appears to run on schedule. QuickBooks provides the connection platform, but the third-party developer controls the app's sync engine, field mappings, queues, and error logs. A successful connection does not prove that every record synced.

Safe troubleshooting steps

  1. Identify the exact integration. Record the app name, developer, company name, affected direction such as app to QuickBooks, last known successful sync time, first failure time, and exact error text. Confirm that the user selected the intended QuickBooks company. Do not include customer records, payroll data, tax IDs, or transaction exports.

  2. Check service notices on both sides. Review Intuit's status information and the developer's official status or support page. Note any outage, maintenance, version change, or announced API incident. If the app shows Intuit's message that it no longer meets platform guidelines, Intuit says it cannot be connected until the developer supplies the required information. Contact the developer for status.

  3. Test access without editing data. Confirm that an authorized administrator can open QuickBooks Online and that the app account itself is active. In QuickBooks, open Integrations and locate the app. Record whether it is connected and which user owns the connection. Do not change settings yet.

  4. Review the app's own sync log. Use the developer's dashboard to find failed job IDs, timestamps, object types, and sanitized error messages. Retry only if the developer documents that retry as idempotent, meaning it will not create duplicates. Otherwise, preserve the failed job and escalate.

  5. Rule out a browser authorization issue. If reauthorization is explicitly requested, first try the connection page in a supported private or incognito window with pop-ups allowed for the official Intuit and app domains. Confirm the company selection before approving access. Never send an OAuth authorization link, password, MFA code, client secret, or access token through a ticket.

  6. Treat reconnecting as a controlled change. Before reconnecting, ask the app developer what happens to unsynced jobs, mappings, historical date ranges, and duplicate detection. Obtain approval from the integration owner and authorized bookkeeper. Reconnect only through the official app flow, then test with the smallest non-financial or otherwise approved sample the developer supports.

  7. Verify the outcome on both sides. Confirm the connection status, job result, timestamp, and object identifier without modifying the accounting treatment. If the test could create or update accounting records, it must be designed and approved by the authorized bookkeeper before execution.

What not to do

Do not disconnect the app as a first troubleshooting step. Intuit warns that apps may separately retain data after a transfer or disconnection, and the developer controls those data rights. Do not transfer ownership, change mappings, replay a batch, import data, delete records, or create adjustments without explicit approval. Do not categorize, match, exclude, reconcile, change opening balances, or otherwise modify accounting records. This is technical guidance, not tax or legal advice.

When to escalate

Send the developer a ticket when its job log contains the failure or only that app is affected. Send QuickBooks support a ticket when the Intuit authorization page fails, the app cannot be found in Integrations, company selection is wrong despite correct admin access, or several unrelated apps fail at once. Include app and developer names, company name, connection owner role, sync direction, affected object type, first and last failure times with time zone, last success, sanitized error text, job or correlation ID, browser and version, outage checks, and whether reauthorization was attempted. Never include secrets or financial records.

Official Intuit sources