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 Vista by Viewpoint (Trimble Viewpoint Vista). The export is file-based — Tread generates a CSV that maps to Vista’s AP and AR import templates.

​
Prerequisites

  • A Vista Viewpoint instance with import access for AP and AR.
  • A Tread admin user with the Settlements and Exports permissions.
  • Customer and vendor records already in Vista. Tread maps by external ID.
  • A Vista import schema confirmed with your accounting team — formats vary by configuration.

​
How it works

  1. Approve in Tread — Settlements close once approvals land. See Settlements & Driver Pay.
  2. Generate export — Pick a date range from the Settlements page and export to Vista format.
  3. Map external IDs — Customers and vendors carry a Vista external ID set during onboarding.
  4. Import to Vista — Your accounting team imports the CSV into Vista AR and AP.
  5. Track exported settlements — Tread marks each exported settlement so it can’t be re-included.

​
What flows where

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

​
Setup

1

Open Integrations settings

Go to Settings → Integrations → Vista Viewpoint.
2

Confirm your Vista import schema

Vista templates differ by company. Have your accounting team share the AR and AP templates they use.
3

Tag customers and vendors

Enter the matching Vista IDs in each Tread record’s External ID field.
4

Run a test export

Export one approved settlement and confirm it imports cleanly into Vista.
5

Set the cadence

Most operators export weekly or by billing period. Tread does not auto-push.

​
Limitations

  • Export only. Tread does not pull data back from Vista.
  • CSV-based, not API-based. No live two-way sync.
  • Vista’s import format depends on configuration. Custom field mappings may need a one-time setup with the Tread team.
  • Customer and vendor records must exist in Vista before import. Tread does not create them.
  • Mid-import edits in Vista do not flow back to Tread.

​
Troubleshooting

Vista rejects the import file
  1. Open the rejection log in Vista — it lists the offending row.
  2. Match the row to the Tread settlement and fix the missing field.
  3. Re-export.
Wrong GL distribution
  1. Confirm the Tread GL map matches Vista’s chart of accounts.
  2. Update the map in Settings → Integrations → Vista Viewpoint.
  3. Re-export the affected settlements.
Customer or vendor mismatch
  1. Pull the Vista customer/vendor list and reconcile against Tread external IDs.
  2. Update Tread to match and re-export.