Tread connects to QuickBooks through Rutter, an accounting API bridge. The integration pushes customer records, invoices, and vendor bills from Tread into QuickBooks so your accounting team works from a single ledger.Documentation Index
Fetch the complete documentation index at: https://docs.tread.ai/llms.txt
Use this file to discover all available pages before exploring further.
Prerequisites
- A QuickBooks Online or QuickBooks Desktop account with admin access.
- A Tread admin user with the Integrations permission.
- Customers and vendors already in QuickBooks. Tread matches by name on first sync.
- Chart of accounts and tax codes set up in QuickBooks.
How it works
- Connect via Rutter — Tread uses Rutter as the bridge to QuickBooks. You authorize Tread once through Rutter’s OAuth flow.
- Match master data — On first sync, Tread maps Tread customers and vendors to QuickBooks counterparts by name.
- Push invoices — Approved settlements generate QuickBooks invoices with ticket reference, material, and quantity per line.
- Push bills — Vendor and owner-operator settlements generate QuickBooks bills.
- Surface errors — If QuickBooks rejects an invoice (missing customer, locked period), the error appears on the settlement in Tread.
What flows where
| Data | Direction | Frequency |
|---|---|---|
| Customers | Tread → QuickBooks | On settlement push |
| Invoices | Tread → QuickBooks | On settlement approval |
| Vendor bills | Tread → QuickBooks | On settlement approval |
| Chart of accounts | QuickBooks → Tread | On connect, then daily |
| Tax codes | QuickBooks → Tread | On connect, then daily |
Setup
Map your accounts
Pick the QuickBooks income account for invoices, the expense account for bills, and the default tax code.
Limitations
- One QuickBooks company per Tread company. Parent/child Tread hierarchies need one connection per child.
- Tread does not pull invoices created directly in QuickBooks back into Tread.
- QuickBooks Desktop syncs through Rutter’s local agent. Your machine must be online when Tread pushes.
- Customer or vendor name mismatches block the sync. Fix the name in QuickBooks or Tread, then retry.
- Tread does not push journal entries or payments.
Troubleshooting
Customer not found in QuickBooks- Open the failed settlement in Tread.
- Compare the customer name to QuickBooks.
- Rename one side to match exactly, then click Retry sync.
- Confirm the QuickBooks period is open.
- If closed, unlock it in QuickBooks or change the invoice date in Tread.
- Retry the sync.
- Go to Settings → Integrations → QuickBooks.
- Click Reconnect and complete the Rutter flow again.