Skip to main content

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.

Tread exports approved invoices and vendor settlements to Trimble Spectrum (formerly Dexter + Chaney). The export is file-based — Tread generates a CSV that maps to Spectrum’s AR and AP import templates.

​
Prerequisites

  • A Spectrum instance with import access for AR and AP.
  • A Tread admin user with the Settlements and Exports permissions.
  • Customer and vendor records already in Spectrum. Tread maps by external ID.
  • A Spectrum import template confirmed with your accounting team.

​
How it works

  1. Approve in Tread — Settlements close once both sides approve. See Settlements & Driver Pay.
  2. Generate export — Pick a date range and export to Spectrum format from the Settlements page.
  3. Map external IDs — Customers and vendors in Tread carry the Spectrum customer or vendor code.
  4. Import to Spectrum — Your accounting team imports the CSV into Spectrum AR and AP.
  5. Track exported settlements — Tread flags each exported settlement so it cannot be re-included.

​
What flows where

DataDirectionFrequency
Customer invoices (AR)Tread → SpectrumOn export
Vendor bills (AP)Tread → SpectrumOn export
Driver payTread → SpectrumOn export
Job and cost code dataSpectrum → TreadTODO: confirm with engineering

​
Setup

1

Open Integrations settings

Go to Settings → Integrations → Spectrum.
2

Confirm your Spectrum import schema

Have your accounting team share the AR and AP templates in use.
3

Tag customers and vendors

Enter the matching Spectrum customer and vendor codes in each Tread record’s External ID field.
4

Run a test export

Export one approved settlement and verify it imports cleanly into Spectrum.
5

Set the cadence

Pick a recurring cadence with your accounting team. Tread does not auto-push.

​
Limitations

  • Export only. Tread does not pull data back from Spectrum.
  • CSV-based, not API-based. No live two-way sync.
  • Customer and vendor records must exist in Spectrum before import. Tread does not create them.
  • Spectrum import errors surface in Spectrum, not Tread.
  • Custom configurations may require a one-time mapping review with the Tread team.

​
Troubleshooting

Spectrum import errors out
  1. Open the Spectrum import log to find the failing row.
  2. Match the row to the Tread settlement using the invoice number.
  3. Fix the missing field and re-export.
GL account mismatch
  1. Confirm Spectrum’s chart of accounts matches the GL map in Tread.
  2. Update the GL map in Settings → Integrations → Spectrum.
  3. Re-export affected settlements.
Duplicate invoice
  1. Check Tread’s export log for overlapping date ranges.
  2. Skip duplicates in Spectrum or re-export with a corrected range.