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.

​
What it is

A Settlement is a finalized batch of approved tickets and timesheets, ready to bill or pay. Tread runs two surfaces: Receivables (customer invoices) and Payables (driver and vendor pay). Both pull from the same approved data, but they apply different rules.

​
Why it matters

This is where Tread turns operations into money. Get the rules right and invoices and pay statements generate themselves. Get them wrong and you spend the next three days reconciling spreadsheets.

​
How Tread models it

  • Approve, then settle. Tickets and timesheets must be approved before they can land in a Settlement. Unapproved data does not appear.
  • Receivables — invoices to Customers. Apply customer rates, add-ons, fuel surcharge, sales tax.
  • Payables — pay to Drivers and Vendors. Apply pay rates, commissions, deductions.
  • Export — Settlements push to QuickBooks, Sage, Vista, Foundation, or Spectrum. PDF statements available for non-portal partners.
Tickets → Approvals → Settlement → Export
Timesheets ↗
SidePullsPays / bills
ReceivablesApproved tickets + timesheetsCustomer
PayablesApproved tickets + timesheetsDriver, Vendor, O&O

​
Common pitfalls

Commission applies to the line item, not the total. A trucking customer expected a 20% truck commission on the full invoice. Tread applied it per line. Always test commissions on a sample settlement before the first cycle.
Tickets “missing” from a Settlement were never approved. If a load does not appear in a Settlement, check approvals first. Approve, then re-pull the Settlement.
Void-and-redo is the only correction path. You cannot edit an approved Settlement in place. To fix a rate or quantity, void the Settlement, correct the underlying ticket, then re-settle.