Disconnecting QuickBooks Online.

Disconnecting is a single-click action from either side. Records already written into QuickBooks stay in QuickBooks, OAuth tokens are destroyed immediately, and we keep your mapping for 90 days in case you reconnect.

Disconnecting from inside EquipFlow.

Sign in at dashboard.equipflow.app, go to Settings → Integrations → QuickBooks Online, and click Disconnect. We call Intuit’s revoke endpoint, destroy the access and refresh tokens, and email the integration owner a confirmation that includes the timestamp and the user who triggered the disconnect.

The in-app disconnect is the preferred path because it runs both sides of the handshake in one step — the token is revoked at Intuit, the record is cleaned up in EquipFlow, and the audit log captures what happened.

Disconnecting from inside QuickBooks.

If you would rather disconnect from Intuit’s side — for example, because an admin has left and you cannot sign into EquipFlow to trigger the action there — sign in at qbo.intuit.com with the QuickBooks admin account.

Click the gear icon in the top-right corner, choose Apps (or Connected Apps depending on your plan), find EquipFlow in the list, and click Disconnect. Intuit’s help article with the current screenshots lives at quickbooks.intuit.com/learn-support.

When the disconnect happens on the Intuit side, we detect it on the next token refresh attempt and clean up our record to match. It takes slightly longer than the in-app path — usually within an hour — and the audit log will note that the disconnect was initiated at Intuit rather than inside EquipFlow.

What happens to your data.

OAuth tokens.

Access and refresh tokens are destroyed immediately on disconnect. We cannot read from or write to your QuickBooks company file after that moment without a fresh authorization.

Queued but unpushed sync items.

Anything that was queued in EquipFlow but had not yet been posted to QuickBooks at the moment of disconnect is discarded and logged. The underlying EquipFlow invoice, payment, or customer record stays in EquipFlow — only the queued push is dropped. On reconnect, new activity flows as usual; backfilling the dropped queue is not automatic, on purpose, because the accounting period may have changed.

Records already in QuickBooks.

Invoices, payments, customers, and items we had already written into QuickBooks stay in QuickBooks exactly as they were. We do not delete records we did not own; the QuickBooks company file continues to be authoritative for anything we wrote there.

Cached mappings and references.

Your configured mappings — chart-of-accounts, sales tax agencies, items, customer links — are retained for 90 days after disconnect. Reconnecting within that window resumes the existing mapping immediately, so a clean reconnect is fast. To delete the cached mapping sooner, email [email protected] from the account owner address and we will purge it and confirm in writing.

Getting help.

If the disconnect does not proceed cleanly — an email does not arrive, the Intuit-side disconnect is not reflected in EquipFlow after an hour, or a queued sync fails in a way the in-app log does not explain — email [email protected] or see the full support page at /support. Include your QuickBooks company ID (the realmIdon Intuit’s connected-apps screen) and the timestamp of the disconnect.

Last updated: April 20, 2026.