Do not teach “there is no grant to disconnect.” If a connection card is not already disconnected, it shows Disconnect. That includes sandbox fixtures created because no PayBlah app is registered at Xero, Intuit, or Sage. Production vendor OAuth is still not launched.
Disconnect a package (Admin)
- Sign in as an Admin → Settings → Connections.
- Find the accounting card (name, provider, scope, interval, last synced or never synced, status badge, optional sandbox — fixture data).
- Click Disconnect.
- Expect the flash Disconnected. Invoices already imported stay where they are. Credentials are removed. Automatic pull stops.
Existing invoices and customers remain. Archive or edit them on Invoices / Customers if you need to. You can still import CSV or XLSX (not .xls). Re-import will not update existing invoice numbers — duplicates are skipped.
Reconnect instead, when you only need a refresh
If the badge is Needs reconnecting, prefer Reconnect on the catalogue card so the same package can sync again. Unconfigured Reconnect still points at sample data, not your live organisation.
Expected result
The card no longer behaves as a healthy scheduled source. Invoices already in PayBlah stay. Workflows, Templates, mailbox, Stripe, and your PayBlah subscription are untouched. Chasing already in flight is not cancelled by disconnect alone — use pause, mark paid, dispute, or other invoice actions.
If something goes wrong
- Non-Admin → “Only an Admin can disconnect accounting software.”
- No such connection — the row is already gone; refresh Connections.
- You still see fixture invoices — expected. Disconnect does not delete the register.
What this does not do
- It does not cancel your PayBlah trial or paid plan (that is Billing, a different Stripe).
- It does not email customers.
- It does not delete Templates or Workflows.
- It does not disconnect FreeAgent, MYOB, or Google Sheets — those are not launched here.
- It does not mark invoices paid and does not update them from a later spreadsheet.