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 Foundation Software’s construction accounting system. The export is file-based — Tread generates a CSV in Foundation’s import format.

​
Prerequisites

  • A Foundation instance with import access.
  • A Tread admin user with the Settlements and Exports permissions.
  • Customer and vendor records already in Foundation. Tread maps by external ID.
  • A Foundation 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 from the Settlements page and export to Foundation format.
  3. Map external IDs — Customers and vendors in Tread carry the Foundation customer or vendor code.
  4. Import to Foundation — Your accounting team imports the CSV into Foundation’s AR or AP module.
  5. Track exported settlements — Tread flags each exported settlement to prevent re-export.

​
What flows where

DataDirectionFrequency
Customer invoicesTread → FoundationOn export
Vendor billsTread → FoundationOn export
Driver payTread → FoundationOn export
Job and cost code dataFoundation → TreadTODO: confirm with engineering

​
Setup

1

Open Integrations settings

Go to Settings → Integrations → Foundation.
2

Confirm your Foundation import schema

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

Tag customers and vendors

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

Run a test export

Export one approved settlement and confirm the import succeeds in Foundation.
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 Foundation.
  • CSV-based, not API-based. No live two-way sync.
  • Customer and vendor records must exist in Foundation before import. Tread does not create them.
  • Foundation import errors surface in Foundation, not Tread.
  • Custom configurations may need a one-time mapping review with the Tread team.

​
Troubleshooting

Foundation rejects rows on import
  1. Read the Foundation import log to find rejected rows.
  2. Match each row to the Tread settlement using the invoice number.
  3. Fix the missing field (often a job code or external ID) and re-export.
Duplicate invoice in Foundation
  1. Tread’s export log shows which settlements were in each file.
  2. Avoid overlapping date ranges on subsequent exports.
  3. Delete the duplicate in Foundation if needed.
External ID mismatch
  1. Pull the Foundation customer or vendor list.
  2. Reconcile against Tread external IDs and update Tread to match.
  3. Re-export.