A clear connection process
- Choose Connect QuickBooks in Ledger Workbench. An authorized Ledger user starts the connection from the desktop application.
- Sign in and consent through Intuit. Your browser takes you to Intuit. Ledger Workbench does not request or store your QuickBooks password.
- Return to Ledger to finish connecting. The public HTTPS callback helps return authorization to your local Ledger Host. Confirm the QuickBooks company in Ledger when prompted.
What the connection supports
Ledger uses authorized QuickBooks accounting access for supported company, vendor, account, Product/Service, bill and expense workflows. Source documents and proposed changes stay visible for review; QuickBooks remains the accounting authority.
Available operations depend on the release, permissions and connection configuration. The current implementation supports one connected QuickBooks company per Ledger Host. Accounting writes in the current release are restricted to the QuickBooks sandbox; this site does not promise general production write availability.
Where authorization is handled
The local Ledger Host owns the QuickBooks connection, protects its access and refresh tokens, and performs authorized QuickBooks operations. Cloudflare provides a limited public callback bridge; it is not the accounting server or the long-term token store.
Disconnecting QuickBooks
You can disconnect QuickBooks authorization from Ledger Workbench. Disconnecting stops use of that connection; it does not automatically delete local accounting records, evidence, mappings or audit history. See the retention and deletion information.
Independent software
Ledger Workbench is independently developed and operated by Elvin Stauffer. It is not owned by Intuit. QuickBooks and Intuit are trademarks of Intuit Inc. Intuit services are subject to Intuit’s applicable terms and privacy statement.