Agave is an accounting integration platform. One Agave connection links Tread to a list of accounting backends — QuickBooks Online, Sage Intacct, NetSuite, Xero, and others — through a single auth flow. Use Agave when your customer’s accounting system is on the supported list and you want one path instead of separate file-based exports.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
- An Agave-supported accounting system with admin access. Confirm support with your Tread implementation lead.
- A Tread admin user with the manage_accounting_integration permission.
- Customers, vendors, and a chart of accounts already in your accounting system. Tread maps to existing records — it does not create them.
- Settlements you want to export are approved in Tread. See Settlements & Driver Pay.
How it works
- Create a link token — Tread requests a one-time token from Agave for the connection.
- Authorize through Agave — A modal opens. The customer picks their accounting system and approves access.
- Import master data — Tread pulls customers, vendors, items (services, add-ons, line item types), and ledger accounts from the connected system.
- Map records — Match each Agave customer to a Tread customer account, each Agave vendor to a Tread vendor, and each Agave item to a Tread service or add-on.
- Export settlements — Approved customer settlements push as AR invoices. Vendor settlements push as AP bills.
What flows where
| Data | Direction | Frequency |
|---|---|---|
| Customers | Agave → Tread | On import |
| Vendors | Agave → Tread | On import |
| Items (services, add-ons) | Agave → Tread | On import |
| Ledger accounts | Agave → Tread | On import |
| Customer invoices (AR) | Tread → Agave | On settlement export |
| Vendor bills (AP) | Tread → Agave | On settlement export |
Setup
Pick your accounting system
Choose your platform (QuickBooks Online, Sage Intacct, NetSuite, etc.) inside the Agave modal and approve access with admin credentials.
Run the import
Click Import. Tread queues a job that pulls customers, vendors, items, and ledger accounts. Large datasets can take several minutes.
Map customers and vendors
Open the Agave settings page. Match each imported customer and vendor to its Tread counterpart.
Map items and ledger accounts
Match Agave items to Tread services and add-ons. Designate one ledger account as AR and one as AP.
When to use Agave vs a direct integration
| Use Agave when | Use direct integration when |
|---|---|
| Your accounting system is on the Agave list | You’re on Sage 300, Vista, Foundation, or Spectrum |
| You want a live API connection | A file-based CSV export is enough |
| You manage multiple accounting backends | You’re locked to one ERP |
Limitations
- One Agave connection per Tread company. Parent/child Tread hierarchies need one connection per child.
- Tread does not push driver settlements through Agave — only customer (AR) and vendor (AP) settlements.
- Tread does not pull invoices created directly in the accounting system back into Tread.
- Customers and vendors must exist in the accounting system first. Tread maps to them; it does not create them.
- A settlement that has already been exported cannot be re-exported. Create a new settlement instead.
Troubleshooting
Account token expired (401)- Go to Settings → Integrations → Agave.
- Click Reconnect and re-authorize through the Agave modal.
- Open the failed settlement.
- Find the unmapped account in the error.
- Map it on the Agave settings page, then click Retry export.
- The error names the line item type or add-on (for example,
Fuel Surcharge). - Map it to an Agave item.
- Re-export.
- On the Agave settings page, set one ledger account to AccountsReceivable and one to AccountsPayable.
- Re-export.