> ## 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.

# Spectrum

> Export billing and settlements to Spectrum.

Move approved billing from Tread into Spectrum without re-keying. Tread exports approved invoices and [Vendor](/concepts/connected-ecosystem) 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](/concepts/connected-ecosystem) 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 approvals land. See [Settlements & Driver Pay](/concepts/settlements-driver-pay).
2. **Generate export** — Pick a date range from the Settlements page and export to Spectrum format.
3. **Map external IDs** — Customers and Vendors carry the Spectrum customer or vendor code as an external ID.
4. **Import to Spectrum** — Your accounting team imports the CSV into Spectrum AR and AP.
5. **Track exported settlements** — Tread marks each exported settlement so it can't be re-included.

## What flows where

| Data                   | Direction        | Frequency |
| ---------------------- | ---------------- | --------- |
| Customer invoices (AR) | Tread → Spectrum | On export |
| Vendor bills (AP)      | Tread → Spectrum | On export |
| Driver pay             | Tread → Spectrum | On export |

## Setup

<Steps>
  <Step title="Open Integrations settings">
    Go to **Settings → Integrations → Spectrum**.
  </Step>

  <Step title="Confirm your Spectrum import schema">
    Have your accounting team share the AR and AP templates in use.
  </Step>

  <Step title="Tag Customers and Vendors">
    Enter the matching Spectrum customer and vendor codes in each Tread record's **External ID** field.
  </Step>

  <Step title="Run a test export">
    Export one approved settlement and verify it imports cleanly into Spectrum.
  </Step>

  <Step title="Set the cadence">
    Pick a recurring cadence with your accounting team. Tread does not auto-push.
  </Step>
</Steps>

## 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.