Disconnecting QuickBooks Online.

Disconnecting inside EquipFlow marks the connection disconnected, records the action, and attempts to revoke the Intuit credential. Accounting documents already posted stay in QuickBooks. Mapping and linked-record references remain available for review or reconnect until they are deleted with the account or through a data request.

Disconnecting from inside EquipFlow.

Sign in at dashboard.equipflow.app, open Settings → Accounting, and click Disconnect. EquipFlow calls Intuit’s revoke endpoint when a refresh credential is available, marks the local connection disconnected, and records the user and revocation result in the audit log.

The in-app disconnect is the preferred path because it attempts the Intuit revocation and updates EquipFlow in one action. If Intuit’s revoke request fails, EquipFlow still stops the local connection and records that outcome for follow-up.

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.

Disconnecting on Intuit’s side prevents the authorization from being used there, but it does not run EquipFlow’s in-app disconnect action. A later connection attempt may instead show that the authorization expired. Use the in-app disconnect as well, or contact support, when you want both systems to show the same state.

What happens to your data.

OAuth tokens.

EquipFlow stops using a connection after it is marked disconnected and attempts to revoke its Intuit refresh credential. The encrypted connection record is retained for audit and recovery; disconnect is not represented as immediate deletion of all locally stored integration data. A fresh authorization is required before posting can resume.

Queued but unpushed sync items.

Queued accounting documents are not deleted by disconnecting. They remain recorded in EquipFlow and can move to a connection-expired or needs-review state. After reconnecting, review and retry the affected documents deliberately; reconnecting does not silently declare old queue work complete. The underlying EquipFlow invoice, payment, credit, deposit, or refund remains in place throughout.

Records already in QuickBooks.

Invoices, payments, credit memos, customer deposits, and deposit refunds that EquipFlow successfully posted remain in QuickBooks. Disconnecting does not issue delete requests for those accounting documents.

Cached mappings and references.

Configured account, item, tax-code, and customer mappings remain in the EquipFlow integration record after disconnect. The current product does not run an automatic 90-day purge. Reconnecting the same QuickBooks company can reuse those references, although any blocked document still needs review. To request deletion of retained integration data, email [email protected] from the account owner address. We will confirm the scope of the request and any records that must be retained for legal, tax, or audit obligations.

Getting help.

If Intuit revocation fails, the connection shows expired instead of disconnected, or a queued document needs recovery after reconnect, 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: July 11, 2026.