Skip to main content
A simple guide to how rate changes cascade between projects, orders, jobs, invoices, and settlements.

​
The big picture

In Tread, rates flow downhill: Project → Order → Job → Invoice → Settlement. You set rates once at the top, and they automatically carry through to everything below. Three rules explain almost all of the behavior:
  1. Rates flow down automatically. A change at a higher level updates everything below it that’s still active.
  2. Connected items stay in sync. Referenced orders, jobs, and unapproved invoices all receive rate changes.
  3. Disconnected items are locked. De-referenced orders and approved invoices keep the rates they had — later changes won’t touch them automatically.
Clean Shot 2026 08 03 At 10 26 43@2x

​
Projects and orders

Every order starts out referenced — linked to its project. While referenced, rates sync both ways: project rate changes flow down to all referenced orders, and rate changes on a referenced order push back up to the project (and out to its other referenced orders). Whenever you change rates on the project or an order, you choose which orders the change applies to. Order status doesn’t matter — active or completed orders can both receive changes. Orders you select stay referenced; orders you skip become de-referenced. De-referenced orders keep their own rates and stop syncing. You can edit their rates individually without affecting the project. You can still push project rates to a de-referenced order later, but that’s a one-time update that restamps its rates — it doesn’t re-link the order. Duplicating or copy-and-editing any order always pulls the latest rates from its project.

​
Orders and jobs

Order rates always flow down to jobs — every job stays current with its order. You can manually adjust rates on an individual job, and that override sticks. However, if the order’s rates, material, pickup site, dropoff site, or equipment type change, rates are re-matched across all jobs and any manual overrides are replaced.

​
Jobs and invoices

Job rate changes flow down to unapproved invoices, and rate changes made on an unapproved invoice push back up to the job. Add-ons flow down from the job to the invoice, but add-on changes made on the invoice stay on the invoice. Approving an invoice locks its rates. No further changes reach it while it’s approved. If you unapprove an invoice, it immediately catches up with any changes made to the job in the meantime.

​
Invoices and settlements

A settlement mirrors its approved invoice — line items and rates can’t be edited directly on the settlement. You can add settlement add-ons, which stay on the settlement only. To change a line item that’s already on a settlement:
  1. Void the settlement
  2. Unapprove the invoice
  3. Make your changes (on the invoice, job, order, or project — as far upstream as needed)
  4. Re-approve the invoice
  5. Regenerate the settlement

​
Quick reference

​
Common pitfalls

The order pulled no rate? It was probably skipped when the rate was set. When you change a project rate, Tread asks which orders to apply it to. Skip an order and it goes independent — it stops syncing with the project. Open the order and set the rate on it directly, or re-apply the project rate as a one-time push.
A manual job rate vanished after an edit. Changing an order’s material, pickup site, dropoff site, or equipment type re-matches rates across every job. The re-match replaces any manual rate you set on a job. Re-enter the override after the change, not before.
No rate at all usually means no rate matches. A rate matches on a material and a route. If the project has no rate for that material, or for that pickup-and-dropoff pair, the order has nothing to pull. Add the rate to the project, then re-apply it to the order.